RFC Errata
RFC 5454, "Dual-Stack Mobile IPv4", March 2009
Source of RFC: mip4 (int)
Errata ID: 1720
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-03-15
Held for Document Update by: Brian Haberman
Section 3.6,pp.13/14 says:
When IPv6 runs over an IPv4 tunnel, the IPv6 tunnel endpoints can treat the IPv4 tunnel as a single hop link as defined in [RFC4213]. The two tunnel endpoints, e.g., mobile node and home agent, MUST configure link-local IPv6 addresses as defined in Section 3.7 of [RFC4213], while they MUST also adhere to the neighbor discovery requirements of the same specification, Section 3.8, and the hop | limit requirements of Section 3.3.
It should say:
When IPv6 runs over an IPv4 tunnel, the IPv6 tunnel endpoints can treat the IPv4 tunnel as a single hop link as defined in [RFC4213]. The two tunnel endpoints, e.g., mobile node and home agent, MUST configure link-local IPv6 addresses as defined in Section 3.7 of [RFC4213], while they MUST also adhere to the neighbor discovery requirements of the same specification, Section 3.8, and the hop | limit requirements of Section 3.3 in [RFC4213].
Notes:
Rationale: The text should also make clear to which document
(this RFC or RFC 4213) the last section number given refers.
Pointing to RFC 4213 twice (but not in the final case) could be
misunderstood, in particular due to the presence of the comma in
front of the "and" in a two-item list.