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

Use RFC 8126 for IANA considerations #859

Merged
merged 1 commit into from Oct 12, 2017
Merged

Use RFC 8126 for IANA considerations #859

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions draft-ietf-quic-http.md
View file
Open in desktop
Expand Up @@ -1196,7 +1196,7 @@ This document creates a new registration for version-negotiation hints in the
This document establishes a registry for HTTP/QUIC frame type codes. The
"HTTP/QUIC Frame Type" registry manages an 8-bit space. The "HTTP/QUIC Frame
Type" registry operates under either of the "IETF Review" or "IESG Approval"
policies {{?RFC5226}} for values between 0x00 and 0xef, with values between 0xf0
policies {{?RFC8126}} for values between 0x00 and 0xef, with values between 0xf0
and 0xff being reserved for Experimental Use.

While this registry is separate from the "HTTP/2 Frame Type" registry defined in
Expand Down Expand Up @@ -1239,7 +1239,7 @@ The entries in the following table are registered by this document.

This document establishes a registry for HTTP/QUIC settings. The "HTTP/QUIC
Settings" registry manages a 16-bit space. The "HTTP/QUIC Settings" registry
operates under the "Expert Review" policy {{?RFC5226}} for values in the range
operates under the "Expert Review" policy {{?RFC8126}} for values in the range
from 0x0000 to 0xefff, with values between and 0xf000 and 0xffff being reserved
for Experimental Use. The designated experts are the same as those for the
"HTTP/2 Settings" registry defined in {{RFC7540}}.
Expand Down Expand Up @@ -1279,7 +1279,7 @@ The entries in the following table are registered by this document.
This document establishes a registry for HTTP/QUIC error codes. The
"HTTP/QUIC Error Code" registry manages a 32-bit space. The "HTTP/QUIC
Error Code" registry operates under the "Expert Review" policy
{{?RFC5226}}.
{{?RFC8126}}.

Registrations for error codes are required to include a description
of the error code. An expert reviewer is advised to examine new
Expand Down
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3205,8 +3205,8 @@ IANA \[SHALL add/has added] a registry for "QUIC Transport Parameters" under a
The "QUIC Transport Parameters" registry governs a 16-bit space. This space is
split into two spaces that are governed by different policies. Values with the
first byte in the range 0x00 to 0xfe (in hexadecimal) are assigned via the
Specification Required policy {{!RFC5226}}. Values with the first byte 0xff are
reserved for Private Use {{!RFC5226}}.
Specification Required policy {{!RFC8126}}. Values with the first byte 0xff are
reserved for Private Use {{!RFC8126}}.

Registrations MUST include the following fields:

Expand Down Expand Up @@ -3251,8 +3251,8 @@ IANA \[SHALL add/has added] a registry for "QUIC Transport Error Codes" under a
The "QUIC Transport Error Codes" registry governs a 32-bit space. This space is
split into two spaces that are governed by different policies. Values with the
first byte in the range 0x00 to 0xfe (in hexadecimal) are assigned via the
Specification Required policy {{!RFC5226}}. Values with the first byte 0xff are
reserved for Private Use {{!RFC5226}}.
Specification Required policy {{!RFC8126}}. Values with the first byte 0xff are
reserved for Private Use {{!RFC8126}}.

Registrations MUST include the following fields:

Expand Down