RFC Errata
Found 11 records.
Status: Verified (7)
RFC 3588, "Diameter Base Protocol", September 2003
Note: This RFC has been obsoleted by RFC 6733
Note: This RFC has been updated by RFC 5729, RFC 5719, RFC 6408
Source of RFC: aaa (ops)
Errata ID: 773
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Alan McNamee
Date Reported: 2006-04-13
Verifier Name: Dan Romascanu
Date Verified: 2009-09-09
AVP Format
<Vendor-Specific-Application-Id> ::=3D < AVP Header: 260 >
1* [ Vendor-Id ]
0*1{ Auth-Application-Id }
0*1{ Acct-Application-Id }
Notes:
for 1* [ Vendor-Id ], is it required or optional?=20
In my understanding, [ ] represent "optional", which means allowing none =
of=20
this type AVP appear, but 1* means at least one needed, Is it =
inconsistent?
The same problem for 0*1{ Auth-Application-Id } and 0*1{ =
Acct-Application-Id }.
Can it is be issued as RFC bug for RFC errata?
from pending
Errata ID: 1429
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Parveen Verma
Date Reported: 2008-05-25
Verifier Name: Dan Romascanu
Date Verified: 2009-09-09
Section 11.4.1 says:
11.4.1. Result-Code AVP Values As defined in Section 7.1, the Result-Code AVP (AVP Code 268) defines the values 1001, 2001-2002, 3001-3010, 4001-4002 and 5001-5017. All remaining values are available for assignment via IETF Consensus [IANA].
It should say:
11.4.1. Result-Code AVP Values As defined in Section 7.1, the Result-Code AVP (AVP Code 268) defines the values 1001, 2001-2002, 3001-3010, 4001-4003 and 5001-5017. All remaining values are available for assignment via IETF Consensus [IANA].
Notes:
7.1.4. Transient Failures
......
DIAMETER_AUTHENTICATION_REJECTED 4001
......
DIAMETER_OUT_OF_SPACE 4002
......
ELECTION_LOST 4003
The peer has determined that it has lost the election process and
has therefore disconnected the transport connection.
For Transient Failures we have error code 4001-4003 defined but the IANA consideration part says only 4001-4002, which can mean the value 4003 is free, but 4003 is assigned to ELECTION_LOST hence error.
Errata ID: 2817
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Vinay parashar
Date Reported: 2011-05-28
Verifier Name: Dan Romascanu
Date Verified: 2011-08-02
Section 5.5.2 says:
There is no valid avp named[ Original-State-Id ].
in DWA message [ Original-State-Id ] should be replaced by [ Origin-State-Id ]
Message Format
<DWA> ::= < Diameter Header: 280 >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ Error-Message ]
* [ Failed-AVP ]
[ Original-State-Id ]
It should say:
Message Format
<DWA> ::= < Diameter Header: 280 >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ Error-Message ]
* [ Failed-AVP ]
[ Origin-State-Id ]
Errata ID: 3280
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Hans Liu
Date Reported: 2012-07-04
Verifier Name: Benoit Claise
Date Verified: 2012-07-17
Section 5.6 says:
Section 5.6 says for both I- and R-: Open - "Rcv-DPR" - "Snd-DPA,Disc" - "Closed"
It should say:
Per section 5.4, the receiver of the Disconnect-Peer-Answer initiates the transport disconnect, so it should say, for both I- and R-: Open - "Rcv-DPR" - "Snd-DPA" - "Closing"
Notes:
In RFC3588bis-34, section 5.4 states more clearly as below
The receiver of the Disconnect-Peer-Answer initiates the transport disconnect. The sender of the Disconnect-Peer-Answer should be able to detect the transport closure and cleanup the connection.
Errata ID: 250
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alan McNamee
Date Reported: 2004-10-02
Section 8.3.2 says:
Message Format
<RAA> ::= < Diameter Header: 258, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Host-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
It should say:
Message Format
<RAA> ::= < Diameter Header: 258, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
Notes:
Errata ID: 251
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alan McNamee
Date Reported: 2004-10-02
Section 5.5.2 says:
Message Format
<DWA> ::= < Diameter Header: 280 >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ Error-Message ]
* [ Failed-AVP ]
[ Original-State-Id ]
It should say:
Message Format
<DWA> ::= < Diameter Header: 280 >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ Error-Message ]
* [ Failed-AVP ]
[ Origin-State-Id ]
Notes:
Errata ID: 3266
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jack Teng
Date Reported: 2012-06-25
Verifier Name: RonBonica
Date Verified: 2012-06-28
Section 5.4. says:
The Disconnection-Reason AVP contains the reason the Diameter node issued the Disconnect-Peer-Request message.
It should say:
The Disconnect-Cause AVP contains the reason the Diameter node issued the Disconnect-Peer-Request message.
Notes:
(There is no such AVP named Disconnection-Reason)
Status: Held for Document Update (3)
RFC 3588, "Diameter Base Protocol", September 2003
Note: This RFC has been obsoleted by RFC 6733
Note: This RFC has been updated by RFC 5729, RFC 5719, RFC 6408
Source of RFC: aaa (ops)
Errata ID: 2101
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Diego Rosario Brogna
Date Reported: 2010-03-31
Held for Document Update by: Dan Romascanu
Section 3.2 says:
header = "<" Diameter-Header:" command-id
[r-bit] [p-bit] [e-bit] [application-id]">"
It should say:
header = "<Diameter-Header:" command-id
[r-bit] [p-bit] [e-bit] [application-id]">"
Errata ID: 2564
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Hans Liu
Date Reported: 2010-10-14
Held for Document Update by: Dan Romascanu
Section 6.1.8 says:
In figure 6, the contents of some AVPs contains domain name mno.net, but the network realm is example.net.
It should say:
Need to fix the inconsistent domain name, change all example.net to mno.net, which is more differentiable from another domain example.com
Errata ID: 3250
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jack Teng
Date Reported: 2012-06-10
Held for Document Update by: Benoit Claise
Section 1.3 says:
As with proxy agents, redirect agents do not keep state with respect to sessions or NAS resources.
It should say:
As with relay agents, redirect agents do not keep state with respect to sessions or NAS resources.
Status: Rejected (1)
RFC 3588, "Diameter Base Protocol", September 2003
Note: This RFC has been obsoleted by RFC 6733
Note: This RFC has been updated by RFC 5729, RFC 5719, RFC 6408
Source of RFC: aaa (ops)
Errata ID: 3381
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Vinay Parashar
Date Reported: 2012-10-17
Rejected by: RonBonica
Date Rejected: 2012-10-29
Section 8.20. Class says:
8.20. Class AVP As described in section 8.20.Class AVP,that Class AVP is used by server to give state information to accesses device. And Class AVP MUST be present in subsequent re-authorization,STR and accounting messages. Now if application uses the base diameter messages for re-authentication[RAR/RAA] and accounting[ACR/ACA] then these message definition should have Class AVP. But it is not present.
It should say:
Definition of RAR/RAA and ACR/ACA should have Class AVP, As STA message definition have.
<RAR> ::= < Diameter Header: 258, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Auth-Application-Id }
{ Re-Auth-Request-Type }
[ User-Name ]
[ Origin-State-Id ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]//************** should have Class AVP **********//
<RAA> ::= < Diameter Header: 258, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
[ Origin-State-Id ]
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
[ Redirect-Host-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ] //************** should have Class AVP **********//
<ACR> ::= < Diameter Header: 271, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Acct-Interim-Interval ]
[ Accounting-Realtime-Required ]
[ Origin-State-Id ]
[ Event-Timestamp ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]//************** should have Class AVP **********//
<ACA> ::= < Diameter Header: 271, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
{ Accounting-Record-Type }
{ Accounting-Record-Number }
[ Acct-Application-Id ]
[ Vendor-Specific-Application-Id ]
[ User-Name ]
[ Accounting-Sub-Session-Id ]
[ Acct-Session-Id ]
[ Acct-Multi-Session-Id ]
[ Error-Reporting-Host ]
[ Acct-Interim-Interval ]
[ Accounting-Realtime-Required ]
[ Origin-State-Id ]
[ Event-Timestamp ]
* [ Proxy-Info ]
* [ AVP ]//************** should have Class AVP **********//
<STR> ::= < Diameter Header: 275, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Application-Id }
{ Termination-Cause }
[ User-Name ]
[ Destination-Host ]
* [ Class ] //****Class AVP present [correct implementation] ***//
[ Origin-State-Id ]
* [ Proxy-Info ]
* [ Route-Record ]
* [ AVP ]
<STA> ::= < Diameter Header: 275, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
[ User-Name ]
* [ Class ]//****Class AVP present [correct implementation] ***//
[ Error-Message ]
[ Error-Reporting-Host ]
* [ Failed-AVP ]
[ Origin-State-Id ]
* [ Redirect-Host ]
[ Redirect-Host-Usage ]
^
[ Redirect-Max-Cache-Time ]
* [ Proxy-Info ]
* [ AVP ]
Notes:
--VERIFIER NOTES--
I think that there might be some confusion regarding this errata. Section 8.20 does not contain the text that the errata claims that it contains.