Opened 15 years ago

Closed 15 years ago

#34 closed editorial (fixed)

Clean IANA text

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

Description

There's text about IANA considerations scattered around the document, repeating information that's already in the IANA considerations section. Suggested edits:

Section 6:
OLD:
   Any new record types SHOULD allocate type values immediately
   beyond the ContentType values for the four record types
   described here (see Appendix A.1). All such values must be
   defined by RFC 2434 Standards Action.  See section 11 for
   IANA Considerations for ContentType values.
NEW:
   New record type values are assigned by IANA as described in
   Section 11.

Section 7.2.2:
OLD:
   New alerts values MUST be defined by RFC 2434 Standards
   Action. See Section 11 for IANA Considerations for alert
   values.
NEW:
   New Alert values are assigned by IANA as described 
   in Section 11.

Section 7.4:
OLD:
   New Handshake message type values MUST be defined via RFC 
   2434 Standards Action. See Section 11 for IANA Considerations
   for these values.
NEW:
   New Handshake message types are assigned by IANA as
   described in Section 11.

Section 7.4.5
OLD:
   ClientCertificateType values are divided into three groups:

   1. Values from 0 (zero) through 63 decimal (0x3F) inclusive
      are reserved for IETF Standards Track protocols.

   2. Values from 64 decimal (0x40) through 223 decimal (0xDF)
      inclusive are reserved for assignment for non-Standards
      Track methods.

   3. Values from 224 decimal (0xE0) through 255 decimal (0xFF)
      inclusive are reserved for private use.

   Additional information describing the role of IANA in the
   allocation of ClientCertificateType code points is described
   in Section 11.
NEW:
   New ClientCertificateType values are assigned by IANA 
   as described in Section 11.

Appendix A.5:
OLD:
   The cipher suite space is divided into three regions:

   1. Cipher suite values with first byte 0x00 (zero)
      through decimal 191 (0xBF) inclusive are reserved 
      for the IETF Standards Track protocols.

   2. Cipher suite values with first byte decimal 192 (0xC0)
      through decimal 254 (0xFE) inclusive are reserved
      for assignment for non-Standards Track methods.

   3. Cipher suite values with first byte 0xFF are
      reserved for private use.

   Additional information describing the role of IANA in 
   the allocation of cipher suite code points is described 
   in Section 11.
NEW:
   New cipher suite values are assigned by IANA as described
   in Section 11.

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.