RFC Errata
Found 3 records.
Status: Held for Document Update (2)
RFC 4072, "Diameter Extensible Authentication Protocol (EAP) Application", August 2005
Note: This RFC has been updated by RFC 7268, RFC 8044
Source of RFC: aaa (ops)
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.
Errata ID: 1956
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:
In addition, the home Diameter server SHOULD include this AVP in Diameter-EAP-Response only if an empty EAP-Key-Name AVP was present in Diameter-EAP-Request.
It should say:
In addition, the home Diameter server SHOULD include this AVP in the Diameter-EAP-Answer message only if an empty EAP-Key-Name AVP was present in the corresponding Diameter-EAP-Request.
Notes:
There's no such thing as a "Diameter-EAP-Response" message; the rephrasing is for purposes of clarification.
Status: Rejected (1)
RFC 4072, "Diameter Extensible Authentication Protocol (EAP) Application", August 2005
Note: This RFC has been updated by RFC 7268, RFC 8044
Source of RFC: aaa (ops)
Errata ID: 2317
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Souheil Ben Ayed
Date Reported: 2010-06-30
Rejected by: Dan Romascanu
Date Rejected: 2010-11-02
Section 3.2. says:
<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ EAP-Payload ]
[ EAP-Reissued-Payload ]
[ EAP-Master-Session-Key ]
[ EAP-Key-Name ]
[ Multi-Round-Time-Out ]
[ Accounting-EAP-Auth-Method ]
[ Service-Type ]
It should say:
<Diameter-EAP-Answer> ::= < Diameter Header: 268, PXY >
< Session-Id >
{ Auth-Application-Id }
{ Auth-Request-Type }
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ EAP-Payload ]
[ EAP-Reissued-Payload ]
[ EAP-Master-Session-Key ]
[ EAP-Key-Name ]
[ Multi-Round-Time-Out ]
* [ Accounting-EAP-Auth-Method ]
[ Service-Type ]
Notes:
When one or more EAP methods used for authenticating the user, for each used EAP method an Accounting-EAP-Auth-Method AVP is added in the Diameter-EAP-Answer with a successful result code. In the message format of Diameter-EAP-Answer, one or more Accounting-EAP-Auth-Method AVPs can be included.
--VERIFIER NOTES--
This erratum if verified would create an non-backward-compatible change. The submiter is kindly requested to consider the discussions with the author on the WG list and if he still thinks that the change is needed to resubmit the erratum as Technical.