RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (1)

RFC 5447, "Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction", February 2009

Source of RFC: dime (ops)

Errata ID: 3034
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Romain Kuntz
Date Reported: 2011-11-22
Verifier Name: ron bonica
Date Verified: 2011-12-06

Section 4.2.5 says: 

The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT
(referred to as LOCAL-bit in the examples) capability and the MIP-
Agent-Info AVP

It should say:

The following examples show how the LOCAL_HOME_AGENT_ASSIGNMENT
(referred to as LOCAL-bit in the examples) capability and the MIP6-
Agent-Info AVP

Notes:

There is no such thing as the "MIP-Agent-Info" AVP, it should be "MIP6-Agent-Info"

Status: Held for Document Update (2)

RFC 5447, "Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction", February 2009

Source of RFC: dime (ops)

Errata ID: 1695
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-02-23
Held for Document Update by: Dan Romascanu

Section 7.1, pg.13 says: 

|  The following new AVPs are to be allocated from RADIUS Attribute Type
   space [RFC2865] so that they are RADIUS backward-compatible (AVP Code
   values between 0-255):

It should say:

                          vvvvvvvvv                vvvv
|  The following new AVPs have been allocated from the RADIUS Attribute
   Type space [RFC2865] so that they are RADIUS backward-compatible (AVP
   Code values between 0-255):

Notes:

Location: second text paragraph in Section 7.1.

Rationale:
Wrong temporal relationship (plus missing article);
as in the first paragraph of the section, the action IANA
_has performed_ in conjunction with the publication of the RFC
should have been recorded in the RFC text.

Errata ID: 1934
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Glen Zorn
Date Reported: 2009-10-26
Held for Document Update by: Dan Romascanu

Section 4.2.4 says: 

   The MIP6-Home-Link-Prefix AVP (AVP Code 125) is of type OctetString
   and contains the Mobile IPv6 home network prefix information in a
   network byte order.

It should say:

   The MIP6-Home-Link-Prefix AVP (AVP Code 125) is of type OctetString
   and contains the Mobile IPv6 home network prefix information in
   network byte order.

Notes:

AFAIK there's only one network byte order.

Report New Errata



Advanced Search