RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (1)

RFC 7296, "Internet Key Exchange Protocol Version 2 (IKEv2)", October 2014

Source of RFC: ipsecme (sec)

Errata ID: 4930

Status: Reported
Type: Editorial

Reported By: Nikolai Malykh
Date Reported: 2017-02-08

Section 3.16 says:

   Note that since IKE passes an indication of initiator identity in the
   first message in the IKE_AUTH exchange, the responder SHOULD NOT send
   EAP Identity requests.  The initiator MAY, however, respond to such
   requests if it receives them.

Notes:

The last sentence of this section contains unnecessary repetition written above (the last sentence in description of Type field).

Status: Held for Document Update (1)

RFC 7296, "Internet Key Exchange Protocol Version 2 (IKEv2)", October 2014

Source of RFC: ipsecme (sec)

Errata ID: 4387

Status: Held for Document Update
Type: Editorial

Reported By: Yoav Nir
Date Reported: 2015-06-04
Held for Document Update by: Stephen Farrell
Date Held: 2015-06-04

Section 3.7 says:

   The Certificate Request payload, denoted CERTREQ in this document,
   provides a means to request preferred certificates via IKE and can
   appear in the IKE_INIT_SA response and/or the IKE_AUTH request.
   Certificate Request payloads MAY be included in an exchange when the
   sender needs to get the certificate of the receiver.

It should say:

   The Certificate Request payload, denoted CERTREQ in this document,
   provides a means to request preferred certificates via IKE and can
   appear in the IKE_SA_INIT response and/or the IKE_AUTH request.
   Certificate Request payloads MAY be included in an exchange when the
   sender needs to get the certificate of the receiver.

Notes:

IKE_SA_INIT is mis-spelled as IKE_INIT_SA this one time.

Report New Errata



Search RFCs
Advanced Search
×