Found 1 record.

Status: Held for Document Update (1)

RFC 5648, "Multiple Care-of Addresses Registration", October 2009

Note: This RFC has been updated by RFC 6089

Errata ID: 1904
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2009-10-08
Held for Document Update by: Brian Haberman

Section 6.2, pg.25 says:

a)
In Section 4.3, the description of the 'Care-of Address' field
in the Binding Identifier Mobility Option specifies:

   Care-of Address

      If a Binding Identifier mobility option is included in a Binding
      Update for the home registration, either IPv4 or IPv6 care-of
      addresses for the corresponding BID can be stored in this field.
      For the binding registration to correspondent nodes (i.e., route
      optimization), only IPv6 care-of addresses can be stored in this
      field.  If no address is specified in this field, the length of
!     this field MUST be zero (i.e., not appear in the option).  If the
!     option is included in any messages other than a Binding Update,
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
!     the length of this field MUST also be zero.
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
b)
Contrary to the "MUST" in the last line, Section 6.2 of the RFC says,
on mid-page 25, where it elaborates on Binding Acknowledgement messages:

   If all the above operations are successfully completed and the 'A'
   flag is set in the Binding Update, a Binding Acknowledgement
   containing the Binding Identifier mobility options MUST be sent to
!  the mobile node.  Whenever a Binding Acknowledgement is sent, all the
                                ^^^^^^^^^^^^^^^^^^^^^^^
!  Binding Identifier mobility options stored in the Binding Update MUST
!  be copied to the Binding Acknowledgement except the Status field.
!  The Care-of Address field in each Binding Identifier mobility option,
|  however, MAY be omitted, because the mobile node can match a
            ^^^
!  corresponding Binding Update List entry using the BID.

It should say:

a)
<< no change >>

b)
   If all the above operations are successfully completed and the 'A'
   flag is set in the Binding Update, a Binding Acknowledgement
   containing the Binding Identifier mobility options MUST be sent to
   the mobile node.  Whenever a Binding Acknowledgement is sent, all the
   Binding Identifier mobility options stored in the Binding Update MUST
   be copied to the Binding Acknowledgement except the Status field.
   The Care-of Address field in each Binding Identifier mobility option,
|  however, MUST be omitted, because the mobile node can match a
   corresponding Binding Update List entry using the BID.

Notes:

Rationale:
The inconsistency is described with the Original Text.
The Corrected Text proposed gives preference to the requirement
from Section 4.3, which seems to be reasonable for efficiency
and consistent with other parts of the specification.

Report New Errata