RFC Errata
Found 7 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)