HA_1_1_1 - BE - Unrecognized MH Type value
Router
NUT
|
--------+-------+------- Link0
|
MN0
Link0 global 3ffe:501:ffff:100::/64 home link MN0 global 3ffe:501:ffff:100:200:ff:fe00:a2a2 home address ether 00:00:00:00:a2:a2
Check Link0 routing tableNUT (Link0) MN0 | | | <---- | Echo Request | ----> | Echo Reply | |
1. MN0 sends Echo Request 2. MN0 receives Echo Reply
Check home registrationNUT (Link0) MN0 | | | <---- | BU (type=0xff, A=1, lifetime=0x0010) (SPI=0x101) | ----> | BE | |
1. MN0X sends Echo Request w/ BU packet format is: Binding_Update_message_format_from_MN_to_HA_ESP.gif 2. MN0X receives BE packet format is: IPv6 header (source = home agent, destination = home address) ESP header Mobility header Binding Error
PASS: MN0 receives BE
Mobility Header processing MUST observe the following rules:o The checksum must be verified as per Section 6.1. Otherwise, the node MUST silently discard the message.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).o The Payload Proto field MUST be IPPROTO_NONE (59 decimal). Otherwise, the node MUST discard the message and SHOULD send ICMP Parameter Problem, Code 0, directly to the Source Address of the packet as specified in RFC 2463 [14]. Thus no Binding Cache information is used in sending the ICMP message. The Pointer field in the ICMP message SHOULD point at the Payload Proto field.o The Header Len field in the Mobility Header MUST NOT be less than the length specified for this particular type of message in Section 6.1. Otherwise, the node MUST discard the message and SHOULD send ICMP Parameter Problem, Code 0, directly to the Source Address of the packet as specified in RFC 2463 [14]. (The Binding Cache information is again not used.) The Pointer field in the ICMP message SHOULD point at the Header Len field.Subsequent checks depend on the particular Mobility Header.