You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLS Cipher Suite Registry: Future values with the first byte in
the range 0-191 (decimal) inclusive are assigned via Standards
Action [RFC2434]. Values with the first byte in the range 192-254
(decimal) are assigned via Specification Required [RFC2434].
Values with the first byte 255 (decimal) are reserved for Private
Use [RFC2434].
The text was updated successfully, but these errors were encountered:
The title here says "extension" but comment 0 says "cipher suite". You meant the latter, correct? Extension ID registry is simply "allocated via IETF Consensus [RFC2434]".
So comment 0, with the "TLS Cipher Suite Registry" policy pasted up there, is what you're suggesting modeling extensions on? e.g. Something like:
0x0000 - 0x0fff : IETF Consensus (almost all current extensions; some standards, some not)
0x1000 - 0x7fff : Specification Required
0x8000 - 0xefff : Private Use
0xf000 - 0xffff : Standards Action (renegotiation_info is in here)
TLS Cipher Suite Registry: Future values with the first byte in
the range 0-191 (decimal) inclusive are assigned via Standards
Action [RFC2434]. Values with the first byte in the range 192-254
(decimal) are assigned via Specification Required [RFC2434].
Values with the first byte 255 (decimal) are reserved for Private
Use [RFC2434].
The text was updated successfully, but these errors were encountered: