[Guy Harris <guy@xxxxxxxxxx>]

> Please can you look the attachement ?

I can, because I'm reading this at work, and, although I read my mail
on UNIX, I happen to have Windows 2000 on my desktop machine (using
Exceed as an X server for UNIX GUI applications - including "xterm"),
and have Office 2000 installed as well.

However, not all people reading this mailing list necessarily have
software that can read Word documents (Office, StarOffice, etc.), so I
suspect not everybody can look at the attachment, or, at least, not
everybody can do so conveniently.

So I'll include the message as text; I'l leave it up to any Mobile IPv6
experts on the list to analyze it.  (The only possibilities I can think
of are

	1) the hub knows IPv6 and somehow rewrites the packet;

	2) the network stack on the home agent modified the packet after
	   supplying it to the packet capture mechanism that Ethereal is
	   using (what OS is the home agent running?);

	3) the network stack on the mobile node modified the packet
	   before supplying it to the packet capture mechanism that
	   Ethereal is using (what OS is the mobile node running?)

but I'm *not* a Mobile IPv6 expert, so I may have missed something;
don't send replies only to me.)

We are testing mobile IPv6 in our experimental system; we use the following 
configuration:
o	Mobile Node:	HoA: 3ffe:501:ffff:1::1
			CoA: 3ffe:501:ffff:2::1
			Eth: 00:04:76:11:d3:73

o	Home Agent:	IPv6 address: 3ffe:501:ffff:1:204:76ff:fe91:5040
			Eth : 00:04:76:10:5c:5d

 +------------+                 +-----+                 +-------------+
 | Home Agent +-----------------+ HUB +-----------------+ Mobile Node |
 +------------+                 +-----+                 +-------------+



Binding update caught on Mobile Node's  interface is the following:

Frame 102 (94 on wire, 94 captured)
    Arrival Time: Sep 13, 2001 15:59:46.5098
    Time delta from previous packet: 0.002036 seconds
    Time relative to first packet: 79.521204 seconds
    Frame Number: 102
    Packet Length: 94 bytes
    Capture Length: 94 bytes
Ethernet II
    Destination: 00:04:76:10:5c:5d 
    Source: 00:04:76:11:d3:73 
    Type: IPv6 (0x86dd)
Internet Protocol Version 6
    Version: 6
    Traffic class: 0x00
    Flowlabel: 0x00000
    Payload length: 40
    Next header: IPv6 destination option (0x3c)
    Hop limit: 64
    Source address: 3ffe:501:ffff:2::1
    Destination address: 3ffe:501:ffff:1:204:76ff:fe91:5040
Destination Option Header 
    Next header: IPv6 destination option (0x3c)
    Length: 2 (24 bytes)
    PadN: 4 bytes
    Option Type: 201 (0xc9) - Home Address
    Option Length : 16
    Home Address : 3ffe:501:ffff:1::1 (3ffe:501:ffff:1::1)
Destination Option Header 
    Next header: IPv6 no next header (0x3b)
    Length: 1 (16 bytes)
    Option Type: 198 (0xc6) - Binding Update
    Option Length : 8
    1... .... = Acknowledge (A) : Binding Acknowledgement requested
    .1.. .... = Home Registration (H) : Home Registration
    ..0. .... = Router (R) : Not a Router
    ...0 .... = Duplicate Address Detection (D) : Do not perform Duplicate Address Detection
    .... 0... = MAP Registration (M) : No MAP Registration
    .... .0.. = Bicasting all (B) : Do not request for bicasting
    Prefix Length : 64
    Sequence Number : 1
    Life Time : 3600
    PadN: 4 bytes

This binding update looks O.K.
"„Same" packet caught on Home Agent's  interface is the following:



Frame 166 (94 on wire, 94 captured)
    Arrival Time: Sep 13, 2001 16:00:04.7185
    Time delta from previous packet: 0.002221 seconds
    Time relative to first packet: 144.701465 seconds
    Frame Number: 166
    Packet Length: 94 bytes
    Capture Length: 94 bytes
Ethernet II
    Destination: 00:04:76:10:5c:5d 
    Source: 00:04:76:11:d3:73 
    Type: IPv6 (0x86dd)
Internet Protocol Version 6
    Version: 6
    Traffic class: 0x00
    Flowlabel: 0x00000
    Payload length: 40
    Next header: IPv6 destination option (0x3c)
    Hop limit: 64
    Source address: 3ffe:501:ffff:1::1
    Destination address: 3ffe:501:ffff:1:204:76ff:fe91:5040
Destination Option Header 
    Next header: IPv6 destination option (0x3c)
    Length: 2 (24 bytes)
    PadN: 4 bytes
    Option Type: 201 (0xc9) - Home Address
    Option Length : 16
    Home Address : 3ffe:501:ffff:2::1 (3ffe:501:ffff:2::1)
Destination Option Header 
    Next header: IPv6 no next header (0x3b)
    Length: 1 (16 bytes)
    Option Type: 198 (0xc6) - Binding Update
    Option Length : 8
    1... .... = Acknowledge (A) : Binding Acknowledgement requested
    .1.. .... = Home Registration (H) : Home Registration
    ..0. .... = Router (R) : Not a Router
    ...0 .... = Duplicate Address Detection (D) : Do not perform Duplicate Address Detection
    .... 0... = MAP Registration (M) : No MAP Registration
    .... .0.. = Bicasting all (B) : Do not request for bicasting
    Prefix Length : 64
    Sequence Number : 1
    Life Time : 3600
    PadN: 4 bytes

This binding update looks strange because it is different from the
first.  In particular in the Home address destination option there is
written the Mobile Node's care of address and in the IP source address
the Home address.
Please could you explain us the reasons of this scenario? 
Thanks, best regards
Perta Francesco
Pica Antimo