errata logo graphic

Found 2 records.

Status: Held for Document Update (1)

RFC4005, "Diameter Network Access Server Application", August 2005

Note: This RFC has been obsoleted by RFC7155

Source of RFC: aaa (ops)

Errata ID: 2563

Status: Held for Document Update
Type: Editorial

Reported By: Hans Liu
Date Reported: 2010-10-14
Held for Document Update by: Dan Romascanu

Section 10.1 says:

The occurrence of route-record AVP in AAA is 0+.

It should say:

The occurrence of route-record AVP in AAA should be 0 according to AAA definition of section 3.2.

Notes:

In 3GPP Rx application TS 29.214, AAA command contains no route-record AVP either. So section 10.1 of RFC4005 needs to be corrected.


Status: Rejected (1)

RFC4005, "Diameter Network Access Server Application", August 2005

Note: This RFC has been obsoleted by RFC7155

Source of RFC: aaa (ops)

Errata ID: 1946

Status: Rejected
Type: Technical

Reported By: Avi Lior
Date Reported: 2009-11-25
Rejected by: Dan Romascanu
Date Rejected: 2010-11-02

Section 9.2 says:

If the Accounting-Input-Octets, Accounting-Input-Packets,
   Accounting-Output-Octets, or Accounting-Output-Packets AVPs are
   present, they must be translated to the corresponding RADIUS
   attributes.  If the value of the Diameter AVPs do not fit
   within a 32-bit RADIUS attribute, the RADIUS Acct-Input-
   Gigawords and Acct-Output-Gigawords must be used.

It should say:

If the Accounting-Input-Octets, 
   Accounting-Output-Octets,  AVPs are
   present, they must be translated to the corresponding RADIUS
   attributes.  If the value of the Diameter AVPs do not fit
   within a 32-bit RADIUS attribute, the RADIUS Acct-Input-
   Gigawords and Acct-Output-Gigawords must be used.

Notes:

The last sentence of the original text causes confusion because according to RFC2869, the Acct-Input/Output-Gigawords are only overflows for the Acct-Input/Output-Octet attributes.
THE ABOVE CORRECTION BASICALLY DOES NOT PROVIDE FOR OVERFLOW FOR THE PACKET COUNTERS.
--VERIFIER NOTES--
The working group discussion on this item led to the following text change being recommended:

If the Accounting-Input-Octets, Accounting-Input-Packets, Accounting-Output-Octets, or Accounting-Output-Packets AVPs are present, they SHOULD be translated to the corresponding RADIUS attributes. However, if the value of the Accounting-Input-Octets AVP or Accounting-Output-Octets AVP does not fit within a 32-bit RADIUS attribute, the RADIUS Acct-Input-Gigawords and Acct-Output-Gigawords Attributes must be used.

Care must be taken when interworking Diameter with RADIUS due to the fact that there is no attribute available in RADIUS to record overflows in packet counters. One remedy that can be used is to limit the session time such that packet counter do not overflow. Another remedy would be to ignore the packet counters altogether and just rely on the octet counters.


Report New Errata