Registries Included Below
Yoav Nir, Rich Salz, Nick Sullivan
If the "Specification Required" [RFC8126] procedure applies,
registration requests can be sent to iana@iana.org or submitted via
IANA's [application form], per [RFC-ietf-tls-rfc8447bis-14]. IANA
will forward the submission to the expert mailing list described in
[RFC 8447, Section 17] and track its progress. See the registration
procedure table below for more information.
The role of the designated expert is described in [RFC8447].
The designated expert [RFC8126] ensures that the specification is
publicly available. It is sufficient to have an Internet-Draft
(that is posted and never published as an RFC) or a document from
another standards body, industry consortium, university site, etc.
The expert may provide more in-depth reviews, but their approval
should not be taken as an endorsement of the extension.
As specified in [RFC8126], assignments made in the Private Use
space are not generally useful for broad interoperability. It is
the responsibility of those making use of the Private Use range to
ensure that no conflicts occur (within the intended scope of use).
For widespread experiments, temporary reservations are available.
If "Recommended" column is set to "N", it does not necessarily
mean that it is flawed; rather, it indicates that the item either
has not been through the IETF consensus process, has limited
applicability, or is intended only for specific use cases. If the
"Recommended" column is set to "D," the item is discouraged and
SHOULD NOT or MUST NOT be used, depending upon the situation;
consult the item's references for clarity.
Abbreviations that may appear in the "TLS 1.3" field include "CH"
(ClientHello), "SH" (ServerHello), "EE" (EncryptedExtensions), "CT"
(Certificate), "CR" (CertificateRequest), "NST" (NewSessionTicket),
and "HRR" (HelloRetryRequest).
The addition of the "CR" to the "TLS 1.3" column for the
server_name(0) extension only marks the extension as valid in a
ClientCertificateRequest created as part of client-generated
authenticator requests.
Any TLS entry added after the IESG approves publication of [RFC-ietf-tls-tls12-frozen-08]
is intended for TLS 1.3 or later, and makes no similar requirement
on DTLS. Such entries should have an informal indication like "For
TLS 1.3 or later" in that entry, such as the "Comment" column.
Yoav Nir, Rich Salz, Nick Sullivan
If the "Specification Required" [RFC8126] procedure applies,
registration requests can be sent to iana@iana.org or submitted via
IANA's [application form], per [RFC-ietf-tls-rfc8447bis-14]. IANA
will forward the submission to the expert mailing list described in
[RFC 8447, Section 17] and track its progress. See the registration
procedure table below for more information.
The role of the designated expert is described in [RFC8447].
The designated expert [RFC8126] ensures that the specification is
publicly available. It is sufficient to have an Internet-Draft
(that is posted and never published as an RFC) or a document from
another standards body, industry consortium, university site, etc.
The expert may provide more in-depth reviews, but their approval
should not be taken as an endorsement of the certificate type.
If "Recommended" column is set to "N", it does not necessarily
mean that it is flawed; rather, it indicates that the item either
has not been through the IETF consensus process, has limited
applicability, or is intended only for specific use cases. If the
"Recommended" column is set to "D," the item is discouraged and
SHOULD NOT or MUST NOT be used, depending upon the situation;
consult the item's references for clarity.
Any TLS entry added after the IESG approves publication of [RFC-ietf-tls-tls12-frozen-08]
is intended for TLS 1.3 or later, and makes no similar requirement
on DTLS. Such entries should have an informal indication like "For
TLS 1.3 or later" in that entry, such as the "Comment" column.
IETF Review
Any TLS entry added after the IESG approves publication of [RFC-ietf-tls-tls12-frozen-08]
is intended for TLS 1.3 or later, and makes no similar requirement
on DTLS. Such entries should have an informal indication like "For
TLS 1.3 or later" in that entry, such as the "Comment" column.
Expert Review
Yoav Nir, Rich Salz, Nick Sullivan
Registration requests should be sent to iana@iana.org or submitted
via IANA's [application form], per [RFC-ietf-tls-rfc8447bis-14].
IANA will forward the request to the expert mailing list described in
[RFC 8447, Section 17] and track its progress.
Yoav Nir, Rich Salz, Nick Sullivan
Requests for registration in the "Specification Required" [RFC8126]
range should be sent to iana@iana.org or submitted via IANA's
[application form], per [RFC-ietf-tls-rfc8447bis-14]. IANA will
forward the request to the expert mailing list described in
[RFC 8447, Section 17] and track its progress. See the registration
procedure table below for more information.
Any TLS entry added after the IESG approves publication of [RFC-ietf-tls-tls12-frozen-08]
is intended for TLS 1.3 or later, and makes no similar requirement
on DTLS. Such entries should have an informal indication like "For
TLS 1.3 or later" in that entry, such as the "Comment" column.
Yoav Nir, Rich Salz, Nick Sullivan
Requests for registration in the "Specification Required" [RFC8126]
range should be sent to iana@iana.org or submitted via IANA's
[application form], per [RFC-ietf-tls-rfc8447bis-14]. IANA will
forward the request to the expert mailing list described in
[RFC 8447, Section 17] and track its progress. See the registration
procedure table below for more information.
Any TLS entry added after the IESG approves publication of [RFC-ietf-tls-tls12-frozen-08]
is intended for TLS 1.3 or later, and makes no similar requirement
on DTLS. Such entries should have an informal indication like "For
TLS 1.3 or later" in that entry, such as the "Comment" column.
This entry reserves an identifier for use within a cleartext version
of a protocol and is not allowed to appear in a TLS ALPN negotiation.
[2]
Only appears in inner CH.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4