RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Verified (5)

RFC 5944, "IP Mobility Support for IPv4, Revised", November 2010

Source of RFC: mip4 (int)

Errata ID: 3116
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Pearl Liang
Date Reported: 2012-02-07
Verifier Name: Brian Haberman
Date Verified: 2012-04-17

Section 3.7.2 says:

Section 3.7.2 "Receiving Registration Requests" says:

Otherwise, if the foreign agent does not serve the mobile node as a home
agent,
   the foreign agent rejects the Registration Request with Code 194
   (Invalid Home Agent Address).

Another entry for "Invalid Home Agent Address" is indicated in Section 3.4: 

        194 Invalid Home Agent Address



It should say:

For Section 3.7.2 "Receiving Registration Requests", it should say:

Otherwise, if the foreign agent does not serve the mobile node as a home
agent,
the foreign agent rejects the Registration Request with Code 116
(Invalid Home Agent Address).

For the entry for "Invalid Home Agent Address" in Section 3.4, it should say:

        116 Invalid Home Agent Address

Notes:

The Code 194 was incorrectly registered under the range for Error Codes from the Foreign Agent (64-127). The mobile note (Invalid Home Agent Address) is a registration under denied by the foreign agent, and so the mobile note should be changed to the Code 116 for Invalid Home Agent Address in the range for Error Codes from the Foreign Agent. The Code 194 has been reserved in the range for Error Codes from the Gateway Foreign Agent (194-200).

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

Reported By: Ville Nuorvala
Date Reported: 2012-12-12
Verifier Name: Brian Haberman
Date Verified: 2012-12-12

Section 3.3 says:

      M        Minimal encapsulation.  If the 'M' bit is set, the mobile
               node requests that its home agent use minimal
               encapsulation [16] for datagrams tunneled to the mobile
               node.

It should say:

      M        Minimal encapsulation.  If the 'M' bit is set, the mobile
               node requests that its home agent use minimal
               encapsulation [15] for datagrams tunneled to the mobile
               node.

Notes:

The citation points to the wrong reference:
[16] Plummer, D., "Ethernet Address Resolution Protocol: Or
Converting Network Protocol Addresses to 48.bit Ethernet
Address for Transmission on Ethernet Hardware", STD 37, RFC
826, November 1982.

It should point to:
[15] Perkins, C., "Minimal Encapsulation within IP", RFC 2004,
October 1996.

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

Reported By: Pritish Aherrao
Date Reported: 2012-12-27
Verifier Name: Brian Haberman
Date Verified: 2013-01-03

Section 3.7.3.2 says:

A Registration Reply that satisfies the validity checks of Section
3.8.2.1 is relayed to the mobile node.

It should say:

A Registration Reply that satisfies the validity checks of Section
3.7.3.1 is relayed to the mobile node.

Notes:

Currently, the incorrect cross reference is provided.
The Foreign Agent would perform the validity checks mentioned in Section 3.7.3.1 upon receiving the Registration Reply and would relay the Registration Reply that satisfies the validity checks.

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

Reported By: Jack Martin
Date Reported: 2014-10-17
Verifier Name: Brian Haberman
Date Verified: 2014-10-21

Section 1.10 says:

This format is applicable for non-skippable extensions that carry
information of more that 256 bytes.
.
.
.
Since the Length field is 16 bits wide, the extension data can exceed
256 bytes in length.

It should say:

This format is applicable for non-skippable extensions that carry
information of more that 254 bytes.
.
.
.
Since the Length field is 16 bits wide, the extension data can exceed
254 bytes in length.

Notes:

Since the short extension form defined in section 1.11 can only carry up to 254 bytes of data, all extensions with 255 or more bytes needs to use the long extension.

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

Reported By: Jack Martin
Date Reported: 2014-10-17
Verifier Name: Brian Haberman
Date Verified: 2014-10-21

Section 1.11 says:

This format is compatible with the skippable extensions defined in
Section 1.9. It is not applicable for extensions that require more
than 256 bytes of data; for such extensions, use the format described
in Section 1.10.

It should say:

This format is compatible with the skippable extensions defined in
Section 1.9. It is not applicable for extensions that require more
than 254 bytes of data; for such extensions, use the format described
in Section 1.10.

Notes:

The length field is 8 bits which yields a maximum of 255 data octets.
But the length field must include one octet for the sub-type field,
yielding a maximum of 254 octets of data.

Report New Errata



Advanced Search