RFC 4072, "Diameter Extensible Authentication Protocol (EAP) Application", August 2005

Note: This RFC has been updated by RFC 7268, RFC 8044

Errata ID: 1955
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Glen Zorn
Date Reported: 2009-12-03
Held for Document Update by: Dan Romascanu

Section 4.1.4 says:

   Note that not all link layers use this name, and currently most EAP
   methods do not generate it.  Since the NAS operates in pass-through
   mode, it cannot know the Key-Name before receiving it from the AAA
   server.  As a result, a Key-Name AVP sent in a Diameter-EAP-Request
   MUST NOT contain any data.  A home Diameter server receiving a
   Diameter-EAP-Request with a Key-Name AVP with non-empty data MUST
   silently discard the AVP.  

It should say:

   Note that not all link layers use this name, and currently most EAP
   methods do not generate it.  Since the NAS operates in pass-through
   mode, it cannot know the name of the key before receiving it from the AAA
   server.  As a result, an EAP-Key-Name AVP sent in a Diameter-EAP-Request
   MUST NOT contain any data.  A home Diameter server receiving a
   Diameter-EAP-Request containing an EAP-Key-Name AVP with non-empty data MUST
   silently ignore the AVP.  

Notes:

In the original text, the first occurrence of the string "Key-Name" apparently is meant to refer to the actual name of the key, rather than an AVP identifier, while the next two occurrences are obviously typos, since no Key-Name AVP is defined in the document. Also, the term "silently discard" is typically used in reference to messages; with reference to a single AVP, "silently ignore" seems more appropriate.

Report New Errata