NAME

CN-2-4-1 - Receiving mobility message - Invalid MH Type


TARGET

Host


TOPOLOGY

       HA----------R2----------R1----------R0
       |           |           |           |
       |           |           |           |
       |----       |----       |----MN     |----CN(NUT)
       |           |           |           |
       |           |           |           |
   Home Link     Link2       Link1       Link0
               (Foreign)   (Foreign)
Link0 3ffe:501:ffff:100::/64  
Link1 3ffe:501:ffff:101::/64 Foreign Link
Link2 3ffe:501:ffff:102::/64 Foreign Link 2
Home Link 3ffe:501:ffff:104::/64 Home Link
CN(NUT) 3ffe:501:ffff:100::X
Auto Configuration (InterfaceID)
 
MN(in Link1) 3ffe:501:ffff:101::Y
Increased in each test (InterfaceID)
MN care-of address
MN(in Home Link) 3ffe:501:ffff:104::Y
Increased in each test (InterfaceID)
MN home address
R0(Link0) 3ffe:501:ffff:100::1  
R1(Link1) 3ffe:501:ffff:101::1  
R2(Link2) 3ffe:501:ffff:102::1  
HA(Home Link) 3ffe:501:ffff:104::1  


INITIALIZATION


Reboot NUT (reboot.rmt)



TEST PROCEDURE

       MN      R1      HA      R0     CN(NUT) 
        |       |       |       |       |
        |       |       |       |------>| 1.RA
        |       |       |       |       |
        |       |       |       |------>| 2.NS
        |       |       |       |       |
        |       |       |       |<------| 3.NA
        |       |       |       |       |
        |-------------->|-------------->| 4.Echo Request
        |       |       |       |       |
        |<--------------|<--------------| 5.Echo Reply
        |       |       |       |       |
        |------------------------------>| 6.Echo Request(Home Address option)
        |       |       |       |       |
        |<------------------------------| 7.BE(Status=1)
        |       |       |       |       |
        |-------------->|-------------->| 8.Invalid Message(MH Type=8, HoTI format)
        |       |       |       |       |
        |<--------------|<--------------| 9.Binding Error(Status=2) (*1)
        |       |       |       |       |
        |-------------->|-------------->| 10.Invalid Message(MH Type=8, HoTI format, Source Address=Multicust address)
        |       |       |       |       |
        |       |       |       |       | (*2)
        |       |       |       |       |
        |------------------------------>| 11.Invalid Message(MH Type=8, BU format with Home Address option)
        |       |       |       |       |
        |<------------------------------| 12.Binding Error(Status=2) (*3)
        |       |       |       |       |
1. Send Router Advertisement.
2. Send Neighbor Solicitation.
3. Receive Neighbor Advertisement.
4. Send ICMP Echo Request.
5. Receive ICMP Echo Reply.
6. Send ICMP Echo Request(Home Address option).
7. Receive Binding Error(Status=1).
8. Send Home Test Init(MH Type=8, HoTI format).
9. Receive Binding Error(Status=2).
10. Send Home Test Init(MH Type=8, HoTI format, Source Address=Multicust address)
   *Expire HoT timer.
11. Send Binding Update(MH Type=8, BU format with Home Address option).
12. Receive Binding Error(Status=2).
Packet Format
8. Home Test Init
9. Binding Error
10. Home Test Init
11. Binding Update
12. Binding Error



JUDGEMENT


(*1) MN receives Binding Error.
  - The Destination Address is set to pseudo Home Test Init (MN home address).
  - The Status field is set to 2.
(*2) MN does not receive Binding Error.
(*3) MN receives Binding Error.
  - The Destination Address is set to pseudo Binding Update (MN care-of address).
  - The Status field is set to 2.
  - The Home Address field is set to the value in the Home Address option in the pseudo Binding Update (MN home address).



REFERENCE

(draft-ietf-mobileip-ipv6-24.txt)

9.2 Processing Mobility Headers
   Mobility Header processing MUST observe the following rules:
      (snip)
   o  The MH Type field MUST have a known value (Section 6.1.1).
      Otherwise, the node MUST discard the message and issue a Binding
      Error message as described in Section 9.3.3, with Status field set
      to 2 (unrecognized MH Type value).
9.3.3 Sending Binding Error Messages
   A Binding Error message is sent directly to the address that appeared
   in the IPv6 Source Address field of the offending packet.  If the
   Source Address field does not contain a unicast address, the Binding
   Error message MUST NOT be sent.
    The Home Address field in the Binding Error message MUST be copied
   from the Home Address field in the Home Address destination option of
   the offending packet, or set to the unspecified address if no such
   option appeared in the packet.