RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Reported (1)

RFC 5580, "Carrying Location Objects in RADIUS and Diameter", August 2009

Note: This RFC has been updated by RFC 8559

Source of RFC: geopriv (rai)

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

Reported By: Alan DeKok
Date Reported: 2018-08-15

Section 5 says:

 0-1     0-1    0      0         0+         126  Operator-Name

It should say:

 0+     0      0      0         0+         126  Operator-Name


Section 4.1 says:

The Operator-Name Attribute SHOULD be sent in Access-Request and
Accounting-Request messages where the Acc-Status-Type is set to
Start, Interim, or Stop.

The table in Section 5 does not appear to match this.

- Access-Request is marked 0-1. It should be marked 0+, to allow packets to contain both E212 and REALM values for Operator-Name

- there is no discussion of Operator-Name in Access-Accept. So it's not clear why the table lists 0-1 for that packet

- The table allows 0+ for Accounting-Request, so it's not clear why it's 0-1 for Access-Request

Report New Errata

Advanced Search