# NAME

ProcessingBRR - Processing Binding Refresh Requests

# TARGET

    Host

# SYNOPSIS

    ProcessingBRR.seq [-tooloption ...] -pkt MN_Common.def

>     -tooloption: v6eval tool option

# TOPOLOGY

                                          |
                                          R       TN
                                          |       |
                                  --------+-------+--------------- LinkZ

                                          |
                                          R2             NUT2
                                          |               |
                                  --------+---------------+------- LinkY

                                          |       |
                                          HA2     R1     NUT1
                                          |       |       |
                                  --------+-------+-------+------- LinkX

                              |           |
                 NUT0        HA1          HA0
                  |           |           |
    Link0 --------+-----------+-----------+-----------------------

> `Link0` | `3ffe:501:ffff:100::/64` | `home link`
> `LinkX` | `3ffe:501:ffff:102::/64` | ``
> `LinkY` | `3ffe:501:ffff:103::/64` | ``
> `LinkZ` | `3ffe:501:ffff:104::/64` | ``
> `HA0(Link0)` | `3ffe:501:ffff:100:200:ff:fe00:a1a1/64` | ``
> `HA1(Link0)` | `3ffe:501:ffff:100:200:ff:fe00:a2a2/64` | ``
> `HA2(LinkX)` | `3ffe:501:ffff:102:200:ff:fe00:a3a3` | ``
> `R1(LinkX)` | `3ffe:501:ffff:102:200:ff:fe00:a4a4` | ``
> `R2(LinkY)` | `3ffe:501:ffff:103:200:ff:fe00:a5a5` | ``
> `TN(LinkZ)` | `3ffe:501:ffff:104:200:ff:fe00:a6a6` | ``

# TEST PROCEDURE

    Processing Binding Refresh Requests

           HA0     NUT1     R1      TN
            |       |       |       |
            |       | <---- |       | RA
            |       |       |       |
            | <---- |       |       | Binding Update (*1)
            | ----> |       |       | Binding Acknowledgement
            |       |       |       |
            |       | <------------ | Echo Request (out: HA0->NUT1, in: TN->NUT0)
            | <==== |       | ----> | Home Test Init(HoTI)
            |       | ------------> | Care-of Test (CoTI)
            | ====> |       | <---- | Home Test (HoT)
            |       | <------------ | Care-of Test (CoTI)
            | <==== |       | ----> | reversed tunneled Echo Reply (out:NUT1->HA0, in:NUT0->TN)
            |       | ------------> | Binding Update
            |       |       |       |
            |       | <------------ | Binding Refresh Request
            | <==== |       | ----> | Home Test Init(HoTI)
            |       | ------------> | Care-of Test (CoTI)
            | ====> |       | <---- | Home Test (HoT)
            |       | <------------ | Care-of Test (CoTI)
            |       | ------------> | Binding Update
            |       |       |       |

# JUDGEMENT

    (*1) PASS: HA0 receives Binding Update

    (*2) PASS: TN doesn't receive Binding Update

# REFERENCE

    draft-ietf-mobileip-ipv6-20.txt

    11.7.4 Receiving Binding Refresh Requests

       When a mobile node receives a packet containing a Binding Refresh
       Request message and there already exists a Binding Update List entry
       for the source of the Binding Refresh Request, it SHOULD start a
       return routability procedure.  The mobile node MAY also choose to
       ignore the Binding Refresh Request.  Also, the mobile node can at any
       time delete its binding from a correspondent node.