RFC 5555, "Mobile IPv6 Support for Dual Stack Hosts and Routers", June 2009

Note: This RFC has been updated by RFC 8553

Errata ID: 3463
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Romain Kuntz
Date Reported: 2013-01-17
Verifier Name: Éric Vyncke
Date Verified: 2024-01-12

Throughout the document, when it says:

with error code 144

Notes:

Binding acknowledgement error status 144 is referenced in sections 4.4.2 and 4.5 to specify that MN should not use UDP encapsulation. However, there is no mention of this status number in the IANA Considerations section (section 8).

-- Verifier note (EV) ---

The MIPv6 Status code 144 does not appear in https://www.iana.org/assignments/mobility-parameters/mobility-parameters.xhtml#mobility-parameters-6

Even worse, it is actually assigned to MIPV6-ID-MISMATCH by a previous RFC 4285 (and the semantics of MIPV6-ID-MISMATCH probably does not match RFC 5555 semantics).

Report New Errata