NAME

BE_UnknownType - BE - Unrecognized MH Type value

TARGET

Host/Router

SYNOPSIS

BE_UnknownType.seq [-tooloption ...] -pkt BE_UnknownType.def

-tooloption: v6eval tool option

TOPOLOGY

                        MN
                        |
        --------+-------+------- LinkX
                |
       NUT      R0
        |       |
--------+-------+--------------- Link0

Link0 global 3ffe:501:ffff:100::/64

LinkX global 3ffe:501:ffff:102::/64 home link

R0(Link0) global 3ffe:501:ffff:100::a0a0

link-local fe80::200:ff:fe00:a0a0

ether 00:00:00:00:a0:a0

MN global 3ffe:501:ffff:102:200:ff:fe00:1 home address

INITIALIZATION

NUT      MN
 |       |
 | <---- | Echo Request
 | ----> | Echo Reply
 |       |

1. Send Echo Request
2. Wait Echo Reply
3. Receive Echo Reply

TEST PROCEDURE

NUT      MN
 |       |
 | <---- | MH (Type 255)
 | ----> | BE
 |       |

1. Send MH (Type 255)
2. Wait BE
3. Receive BE

JUDGEMENT

PASS: MN receives BE
WARN: no response
FAIL: Recv unexpect packets

REFERENCE

<draft-ietf-mobileip-ipv6-19.txt>
9.2. Processing Mobility Headers
----------------------------------------------------------------
    1. The MH Type field MUST have a known value (Section 6.1.1).
       Otherwise, the node MUST discard the message and SHOULD issue a
       Binding Error message as described in Section 9.3.3, with Status
       field set to 2 (unrecognized MH Type value).
----------------------------------------------------------------

`Link0`	`global`	`3ffe:501:ffff:100::/64`
`LinkX`	`global`	`3ffe:501:ffff:102::/64`	`home link`
`R0(Link0)`	`global`	`3ffe:501:ffff:100::a0a0`
	`link-local`	`fe80::200:ff:fe00:a0a0`
	`ether`	`00:00:00:00:a0:a0`
`MN`	`global`	`3ffe:501:ffff:102:200:ff:fe00:1`	`home address`