Opened 15 years ago

Closed 15 years ago

#33 closed editorial (fixed)

Correct IANA considerations

Reported by: pasi.eronen@… Owned by:
Priority: minor Milestone: milestone1
Component: draft-ietf-tls-rfc4346-bis Version: 02
Severity: Keywords:
Cc:

Description

This document doesn't actually require IANA to create new registries (except for cert_hash_types), since they already exist. Suggested rephrasing for Section 11:

This document uses several registries that were originally
created in [RFC4346]. IANA is requested to update (has updated)
these to reference this document. The registries and their
allocation policies (unchanged from [RFC4346]) are listed
below.

o  TLS ClientCertificateType Identifiers Registry: Future
   values in the range 0-63 (decimal) inclusive are assigned
   Standards Action [RFC2434]. Values in the range 64-223
   (decimal) inclusive are assigned Specification Required
   [RFC2434]. Values from 224-255 (decimal) inclusive are
   reserved for Private Use [RFC2434].
   
o  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].
  
o  TLS ContentType Registry: Future values are allocated via
   Standards Action [RFC2434].

o  TLS Alert Registry: Future values are allocated via
   Standards Action [RFC2434].

o  TLS HandshakeType Registry: Future values are allocated via
   Standards Action [RFC2434].

This document also uses a registry originally created in
[RFC4366].  IANA is requested to update (has updated) it to
reference this document.  The registry and its allocation
policy (unchanged from [RFC4366]) is listed below:.

o  TLS ExtensionType Registry: Future values are allocated
   via IETF Consensus [RFC2434]

In addition, this document defines one new registry to
be maintained by IANA:

o  TLS HashType Registry: The registry will be initially
   populated with the values described in Section 7.4.1.4.7.
   Future values in the range 0-63 (decimal) inclusive are
   assigned via Standards Action [RFC2434].  Values in the
   range 64-223 (decimal) inclusive are assigned via
   Specification Required [RFC2434].  Values from 224-255
   (decimal) inclusive are reserved for Private Use [RFC2434].

This document defines one new TLS extension, cert_hash_type,
which is to be (has been) allocated value TBD-BY-IANA in the
TLS ExtensionType registry.

Change History (1)

comment:1 Changed 15 years ago by ekr@…

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.