RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Rejected (3)

RFC 3220, "IP Mobility Support for IPv4", January 2002

Note: This RFC has been obsoleted by RFC 3344

Source of RFC: mobileip (int)

Errata ID: 320
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT

Reported By: "Charles E. Perkins"
Date Reported: 2002-04-23
Rejected by: Brian Haberman
Date Rejected: 2012-06-06

In Section 3.6.1.2 (after current page 41), insert the following text:

   The Lifetime field is chosen as follows:

    -  If the mobile node is registering with a foreign agent, the
       Lifetime SHOULD NOT exceed the value in the Registration Lifetime
       field of the Agent Advertisement message received from the
       foreign agent.  When the method by which the care-of address is
       learned does not include a Lifetime, the default ICMP Router
       Advertisement Lifetime (1800 seconds) MAY be used.

    -  The mobile node MAY ask a home agent to delete a particular
       mobility binding, by sending a Registration Request with the
       care-of address for this binding, with the Lifetime field set to
       zero (Section 3.8.2).

    -  Similarly, a Lifetime of zero is used when the mobile node
       deregisters all care-of addresses, such as upon returning home.

   The Home Address field MUST be set to the mobile node's home address,
   if this information is known.  Otherwise, the Home Address MUST be
   set to zeroes.

   The Home Agent field MUST be set to the address of the mobile node's
   home agent, if the mobile node knows this address.  Otherwise, the
   mobile node MAY use dynamic home agent address resolution to learn
   the address of its home agent.  In this case, the mobile node MUST
   set the Home Agent field to the subnet-directed broadcast address
   of the mobile node's home network.  Each home agent receiving such
   a Registration Request with a broadcast destination address MUST
   reject the mobile node's registration and SHOULD return a rejection
   Registration Reply indicating its unicast IP address for use by the
   mobile node in a future registration attempt.

   The Care-of Address field MUST be set to the value of the particular
   care-of address that the mobile node wishes to (de)register.  In the
   special case in which a mobile node wishes to deregister all care-of
   addresses, it MUST set this field to its home address.

   The mobile node chooses the Identification field in accordance with
   the style of replay protection it uses with its home agent.  This is
   part of the mobility security association the mobile node shares with
   its home agent.  See Section 5.7 for the method by which the mobile
   node computes the Identification field.


3.6.1.3. Extensions

   This section describes the ordering of any mandatory and any optional
   Extensions that a mobile node appends to a Registration Request.
   This following ordering MUST be followed:

Notes:


--VERIFIER NOTES--
RFC 3220 has been obsoleted by RFC 3344.

Errata ID: 321
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT

Reported By: "Charles E. Perkins"
Date Reported: 2002-04-23
Rejected by: Brian Haberman
Date Rejected: 2012-06-06

Section 5.7 says:

   Whatever method is used, the low-order 32 bits of the Identification
   MUST be copied unchanged from the Registration Request to the Reply.
   The foreign agent uses those bits (and the mobile node's home
   address) to match Registration Requests with corresponding replies.
   of any Registration Reply are identical to the bits it sent in the
   Registration Request.

It should say:

   Whatever method is used, the low-order 32 bits of the Identification
   MUST be copied unchanged from the Registration Request to the Reply.
   The foreign agent uses those bits (and the mobile node's home
   address) to match Registration Requests with corresponding replies.
   The mobile node MUST verify that the low-order 32 bits of any Registration 
   Reply are identical to the bits it sent in the Registration Request.

Notes:


--VERIFIER NOTES--
RFC 3220 has been obsoleted by RFC 3344.

Errata ID: 842
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT

Reported By: "Charles E. Perkins"
Date Reported: 2002-04-23
Rejected by: Brian Haberman
Date Rejected: 2012-06-06

 

Correction 2: to be inserted before the line on page 74
	starting "of any Registration..."

========================================================================
      The mobile node MUST verify that the low-order 32 bits
========================================================================

It should say:

[see above]

Notes:

from pending
--VERIFIER NOTES--
RFC 3220 has been obsoleted by RFC 3344.

Report New Errata



Advanced Search