RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Verified (3)

RFC 7155, "Diameter Network Access Server Application", April 2014

Source of RFC: dime (ops)

Errata ID: 5993
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Michal Liptak
Date Reported: 2020-02-27
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2020-03-04

Throughout the document, when it says:

Redirected-Host*

It should say:

Redirect-Host*

Notes:

I did not find AVP Redirected-Host defined anywhere, however there is Redirect-Host in RFC 6733 (same with Redirected-Host-Usage)

[WK: Note that Errata 5993, 5994, 5995 are all related / similar. Readers are encouraged to read all 3 ]

Errata ID: 5994
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Michal Liptak
Date Reported: 2020-02-27
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2020-03-04

Section 3.4 says:

Redirected-Host-Cache-Time

It should say:

Redirect-Max-Cache-Time

Notes:

As per RFC 6733 section 8.3.2

[WK: Note that Errata 5993, 5994, 5995 are all related / similar. Readers are encouraged to read all 3 ]

Errata ID: 5995
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Michal Liptak
Date Reported: 2020-02-27
Verifier Name: Warren Kumari (Ops AD)
Date Verified: 2020-03-04

Throughout the document, when it says:

Connection-Info

It should say:

Connect-Info

Notes:

typo in AVP name

[WK: Note that Errata 5993, 5994, 5995 are all related / similar. Readers are encouraged to read all 3 ]

Status: Reported (2)

RFC 7155, "Diameter Network Access Server Application", April 2014

Source of RFC: dime (ops)

Errata ID: 6029
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Luke Mewburn
Date Reported: 2020-03-25

Section 4.4 says:

   QoS-Filter-Rule             4.4.9        |    |     |

It should say:

   QoS-Filter-Rule             4.4.9        | M  |  V  |

Notes:

The row "QoS-Filter-Rule" does not define AVP Flag Rules for "M" or "V":
- The V Flag MUST NOT be used for this AVP.
- There may be some debate whether the M Flag can be retrospectively added to the MUST column, versus leaving it out (implied "MAY" ?).

The changes are consistent with all other AVPs in this RFC.

Errata ID: 6119
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Luke Mewburn
Date Reported: 2020-04-24

Throughout the document, when it says:

[Missing sections when RFC 4005 was obsoleted by RFC 7155]

It should say:

4.7 AVPs Used Only for Compatibility

   The AVPs defined in this section SHOULD only be used for backwards
   compatibility when a Diameter/RADIUS translation function is invoked
   and are not typically originated by Diameter systems during normal
   operations.

                                            +----------+
                                            | AVP Flag |
                                            |  Rules   |
                                            |----+-----|
                                            |MUST| MUST|
   Attribute Name           Section Defined |    |  NOT|
   -----------------------------------------|----+-----|
   Origin-AAA-Protocol      4.7.1           | M  |  V  |
   -----------------------------------------|----+-----|

4.7.1.  Origin-AAA-Protocol

   The Origin-AAA-Protocol AVP (AVP Code 408) is of the type Enumerated
   and should be inserted in a Diameter message translated by a gateway
   system from another AAA protocol, such as RADIUS.  It identifies the
   source protocol of the message to the Diameter system receiving the
   message.

   The supported values are:

         1       RADIUS

Notes:

The description of Origin-AAA-Protocol (AVP Code 408) is missing from RFC 7155. The AVP is documented in RFC 4005 section 9.3.6.

The proposed corrected text contains RFC 4005 section 9.3 as RFC 7155 section 4.7, and RFC 4005 section 9.3.6 as RFC 7155 section 4.7.1. All other AVPs in RFC 4005 section 9.3.x are not listed because they are documented in their relevant standards already.

RFC 7155 is listed as the Reference for Origin-AAA-Protocol in multiple locations in https://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml

It appears that there may be an accidental omission of Origin-AAA-Protocol when RFC 7155 obsoleted RFC 4005.

The Origin-AAA-Protocol AVP is referenced in other sections in RFC 7155:
- 3.1. AA-Request (AAR) Command
- 3.2. AA-Answer (AAA) Command
- 3.3. Re-Auth-Request (RAR) Command
- 3.4. Re-Auth-Answer (RAA) Command
- 3.5. Session-Termination-Request (STR) Command
- 3.6. Session-Termination-Answer (STA) Command
- 3.7. Abort-Session-Request (ASR) Command
- 3.8. Abort-Session-Answer (ASA) Command
- 3.9. Accounting-Request (ACR) Command
- 3.10. Accounting-Answer (ACA) Command
- 5.1. AA-Request / AA-Answer AVP Table
- 5.2.1. Framed Access Accounting AVP Table
- 5.2.2. Non-Framed Access Accounting AVP Table

Report New Errata