RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Rejected (1)

RFC 7633, "X.509v3 Transport Layer Security (TLS) Feature Extension", October 2015

Source of RFC: IETF - NON WORKING GROUP

Errata ID: 4571

Status: Rejected
Type: Editorial

Reported By: Anonymous
Date Reported: 2015-12-28
Rejected by: Stephen Farrell
Date Rejected: 2015-12-28

Section 2.2 says:

2.2.  TLS Feature, X.509 Extension

   In order to avoid the confusion that would occur in attempting to
   specify an X.509 extension describing the use of TLS extensions, in
   this document the term "extension" is reserved to refer to X.509v3
   extensions and the term "TLS feature extension" is used to refer to
   what the TLS specification [RFC5246] refers to as an "extension".

It should say:

2.2.  TLS Feature, X.509 Extension

   In order to avoid the confusion that would occur in attempting to
   specify an X.509 extension describing the use of TLS extensions, in
   this document the term "TLS feature extension" is used to refer to
   the X.509 extension specified in this document.

Notes:

(There is no platonically correct version of the text, as the problem is with the entire RFC.)

Virtually every instance of the term "TLS feature extension" in the RFC refers to the X.509 extension. The sole instance of it referring to TLS extensions is the first paragraph of section 3.

Of the uses of the simple term "extension," the first two paragraphs of Section 3 contain the only three uses consistent with 2.2. The other three ("choose to have a certificate issued with this extension","critical extensions MUST reject the certificate","key usage extension") refer to X.509 extensions.
--VERIFIER NOTES--
Issue was discussed during AD eval and IESG eval so this is not an error.
An anonymously submitted erratum is also odd.

Report New Errata



Search RFCs
Advanced Search
×