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.

Sign up for GitHub

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

Jump to bottom

Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC #159

Merged
merged 5 commits into from Jun 15, 2018
Merged

Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC #159

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
95339a2
Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC
yoavweiss May 18, 2018
e5f5d19
Added a MAY regarding experimental protocols. Reorganized
yoavweiss Jun 14, 2018
2a9eaa0
Add ALPN-negotiated value and HTTP over QUIC
yoavweiss Jun 14, 2018
a385949
SHOULD use ALPN value
yoavweiss Jun 14, 2018
de148c0
Better registry definition, removed HTTP0.9 and 1.0, made ALPN a MUST
yoavweiss Jun 15, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
31 changes: 20 additions & 11 deletions index.html
View file
Open in desktop
Expand Up @@ -452,18 +452,27 @@ <h3>The <dfn>PerformanceResourceTiming</dfn> Interface</h3>
used to fetch the resource, as identified by the ALPN Protocol ID
[[!RFC7301]]; resources retrieved from <a data-cite=
"!HTML/#relevant-application-cache">relevant application caches</a>
or local resources, return an empty string. The registry for
protocol identifiers lists the possible values for the <a href=
or local resources, return an empty string. When a proxy is
configured, if a tunnel connection is established then this attribute
MUST return the ALPN Protocol ID of the tunneled protocol, otherwise
it MUST return the ALPN Protocol ID of the first hop to the proxy.
In order to have precisely one way to represent any ALPN protocol ID,
the following additional constraints apply: octets in the ALPN
protocol MUST NOT be percent-encoded if they are valid token
characters except "%", and when using percent-encoding, uppercase hex
digits MUST be used.</p>
<p>Formally registered ALPN protocol IDs are documented by <a href=
"https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids">
ALPN Protocol IDs</a>. When a proxy is configured, if a tunnel
connection is established then this attribute MUST return the ALPN
Protocol ID of the tunneled protocol, otherwise it MUST return the
ALPN Protocol ID of the first hop to the proxy. In order to have
precisely one way to represent any ALPN protocol ID, the following
additional constraints apply: octets in the ALPN protocol MUST NOT
be percent-encoded if they are valid token characters except "%",
and when using percent-encoding, uppercase hex digits MUST be
used.</p>
IANA</a>. In case the user agent is using an experimental,
non-registered protocol, the user agent MUST use the ALPN negotiated
value if any. If ALPN was not used for protocol negotiations, the
user agent MAY use another descriptive string.</p>

<p class=note>The "hq" ALPN ID is defined for the final version of
the HTTP over QUIC protocol in the
<a href="https://tools.ietf.org/html/draft-ietf-quic-http-11#section-9.1">
HTTP over QUIC Internet Draft</a>.
</p>
<p>Note that the <a data-link-for=
"PerformanceResourceTiming">nextHopProtocol</a> attribute is
intended to identify the network protocol in use for the fetch
Expand Down