RFC 4763, "Extensible Authentication Protocol Method for Shared-secret Authentication and Key Establishment (EAP-SAKE)", November 2006

Errata ID: 1414
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-02-12
Verifier Name: Nevil Brownlee
Date Verified: 2010-04-05

Section 3.3.1 says:

   Type

      To be assigned

  

It should say:

   Type

     EAP-SAKE (=48)

Notes:

8) The explanation,

AT_ENCR_DATA

This attribute is optional to use in this message. The encrypted
data, if present, may contain an attribute AT_NEXT_TMPID,
containing the NAI the Peer should use in the next EAP
authentication.

should say:

| AT_ENCR_DATA (=128)

| This attribute is optional to use in this message. The cleartext
| form of the encrypted data, if present, may contain an attribute
AT_NEXT_TMPID, containing the NAI the Peer should use in the next
EAP authentication.


(13) Section 4 -- lack of specification

The first paragraph of Section 4 (on page 37) says:

| IANA allocated a new EAP Type for EAP-SAKE.
^
It should say:

| IANA allocated a new EAP Type, 48, for EAP-SAKE.
^^^^^^


(15) Section 8.1 -- outdated Normative Reference

On page 45, the ref. [SHA1] should better point to the current
version, "FIPS 180-2 (with Change Notice)", February 2004.

Report New Errata