Re: confusion in mipv6 I-D?

Frank Quick <[email protected]> Thu, 02 Oct 2003 17:56:46 -0700
Newsgroups gmane.ietf.mobileip
Message-ID <[email protected]>
Thanks.  But in section 10.3.1:

"To begin processing the Binding Update, the home agent MUST perform the 
following sequence of tests:

...

   o  A Home Address destination option MUST be present in the message.

..."

11.7.1 says essentially the same thing on page 131:

"   o  The packet MUST contain a Home Address destination option, giving
       the mobile node's home address for the binding."


This seems to moot some of the text in 11.7.1, page 132:

"The mobile node MUST use its home address - either in the Home Address 
destination option or in   the Source Address field of the IPv6 header - in 
Binding Updates sent to the home agent."

Seems this sentence should only refer to the destination option for 
consistency.

At 05:13 PM 10/2/2003 -0700, Vijay Devarapalli wrote:
>the only restriction is that the source address on the BU MUST be a
>topologically correct address (otherwise packet is dropped bu ingress
>filtering).
>
>>I still wonder what happens if both the Alternate Care-of Address and the 
>>Home Address option are present.  In that case can the Source Address 
>>field be either of those addresses,
>
>typically CoA when in visited link and home address when the MN is
>on the home link.
>
>>or perhaps neither?
>
>yes. for example, a MN could have two Care-of addresses, CoA1 and
>CoA2. in the Binding Update, it could set the source address to CoA1,
>include CoA2 in alt CoA option and home address in the Home Address
>option. when the HA processes this Binding Update, the home address is
>bound to CoA2.
>
>Vijay
>


Frank Quick
office   +1-858-658-3608 fax +1-858-651-1940
portable +1-619-890-5749
paging   [email protected]
RSA: 29EA D619 31F2 B4D3  8815 3D59 4340 FA43
D-H: 2A24 131C D38F 12E6 4D6A  46EE 8BBF B50A 754E F63D