RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 6 records.

Status: Verified (1)

RFC 4307, "Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)", December 2005

Note: This RFC has been obsoleted by RFC 8247

Source of RFC: ipsec (sec)

Errata ID: 1937
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Tero Kivinen
Date Reported: 2009-11-02
Verifier Name: Pasi Eronen
Date Verified: 2010-03-01

Section 3.1.3. says: 

      ENCR_NULL                11        [RFC2410]       MAY

It should say:

      ENCR_NULL                11        [RFC2410]       MUST NOT

Notes:

ENCR_NULL is MUST NOT for IKEv2, as RFC4306 specifies that ENCR_NULL MUST NOT be used as IKE encryption algorithm (RFC4306 section 5).

Status: Held for Document Update (5)

RFC 4307, "Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)", December 2005

Note: This RFC has been obsoleted by RFC 8247

Source of RFC: ipsec (sec)

Errata ID: 131
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-02-03
Held for Document Update by: Pasi Eronen

Section 3.1.3 says: 

   IKEv2 defines several possible algorithms for Transfer Type 1
   (encryption).  These are defined below with their implementation
   status.

It should say:

   IKEv2 defines several possible algorithms for Transform Type 1
   (encryption).  These are defined below with their implementation
   status.

Errata ID: 685
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-02-03
Held for Document Update by: Pasi Eronen

Section 3.1.4 says: 

Transfer Type 2 Algorithms are pseudo-random functions used to
generate random values when needed.

It should say:

Transform Type 2 Algorithms are pseudo-random functions used to
generate random values when needed.

Notes:

from pending

Errata ID: 687
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-02-03
Held for Document Update by: Pasi Eronen

Section 3.1.5 says: 

Transfer Type 3 Algorithms are Integrity algorithms used to protect
data against tampering.

It should say:

Transform Type 3 Algorithms are Integrity algorithms used to protect
data against tampering.

Notes:

from pending

Errata ID: 688
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-02-03
Held for Document Update by: Pasi Eronen

 

Like other contemporary RFCs, RFC 4307 seems to have been infected
by a common 'virus'. In the case or RFC 4307, the first sentence of the Introduction has been inadvertantly split by a spurious blank line.

Notes:

from pending

Errata ID: 690
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-02-03
Held for Document Update by: Pasi Eronen

 

On pages 3 and 4 of RFC 4307, the text in Section 3.1.3 through
Section 3.1.5 contains three instances of the same typo,
talking about    [algorithms of] "Transfer Type <n>"  , where it
should refer to  [algorithms of] "Transform Type <n>".

Notes:

typo breaking IPsec terminology

from pending

Report New Errata



Advanced Search