Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refining Prior Knowledge #418

Closed
emile22 opened this issue Feb 27, 2014 · 4 comments
Closed

Refining Prior Knowledge #418

emile22 opened this issue Feb 27, 2014 · 4 comments

Comments

@emile22
Copy link

emile22 commented Feb 27, 2014

We need something more granular than the Prior Knowledge approach because a client which does a request without prior knowledge about support for HTTP2 can discover the support of HTTP/2 during the resolution of the domain of the ‘URI’. A client may make a request Without Prior Knowledge and got the information at the time it establishes the TCP connection.

I will propose text to clarify this point.

@martinthomson
Copy link
Collaborator

Sounds reasonable. Marking this editorial.

emile22 added a commit to emile22/http2-spec that referenced this issue Mar 2, 2014
Discovery about the support for HTTP2 during the domain name resolution.
@martinthomson
Copy link
Collaborator

It looks like this is more than editorial. It's a proposal to include specific text on SRV.

@emile22
Copy link
Author

emile22 commented Mar 18, 2014

It's a proposal to include specific text on DNS based discovery.

@mnot
Copy link
Member

mnot commented Jun 5, 2014

Discussed in NYC; closed because we don't want to block on DNS-based discovery (although it is a topic of continuing interest and discussion).

@mnot mnot closed this as completed Jun 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants