Re: [MEXT] Review of Re: I-D Action:draft-ietf-monami6-multiplecoa-12.txt

[Benjamin Lim <benjamin.limck at sg.panasonic.com>]

Hi Christian,

You are right.  I forgot to consider the case where HA is not the
default router.  The HA would be the one to decide to do ND-proxy or not
based on the topology.

Regards,
Benjamin Lim

Christian Kaas-Petersen wrote:
> The H-bit=1 is not used to turn off neighbor discovery at HA.
> 
> The H-bit=1 is used by the mobile node to tell the home agent
> it has simultaneous connectivity on home link and one or more
> foreign links.  Then the home agent decides who should do neighbor
> discovery on the home link (depending on whether
> the home agent is the only router on the home link, ie topology a
> of Figure 3, or there are other routers on the home link, ie topology b
> of Figure 3), and the home agent reports its decision in the status
> value of the binding acknowledgement.  In topology a the mobile node
> will do neighbor discovery; in topology b the home agent will continue
> doing neighbor discovery.
> 
> Christian
> 
> --- Den ons 18/3/09 skrev Benjamin Lim <benjamin.limck at sg.panasonic.com>:
> 
>> Fra: Benjamin Lim <benjamin.limck at sg.panasonic.com>
>> Emne: Re: [MEXT] Review of Re: I-D Action:draft-ietf-monami6-multiplecoa-12.txt
>> Til: "Christian Kaas-Petersen" <kaaspetersen at yahoo.dk>
>> Cc: "George Tsirtsis" <tsirtsis at googlemail.com>, "mext" <mext at ietf.org>
>> Dato: onsdag 18. marts 2009 08.17
>> Hi Christian, all,
>>
>> Pls see inline for some of my comments.
>>
>> Christian Kaas-Petersen wrote:
>>> The packets I proposed I get from draft 12, section
>> 5.4 second paragraph
>>> (which details a de-registration with lifetime=0 and
>> absence of
>>> care-of address) and section 5.6.3 bullets number 1
>> and 2 (which detail
>>> the presence of the H-bit and the absence of the
>> care-of address).
>>> To me, there is no need to register a binding where
>> CoA=HoA (use of
>>> home link), unless flow binding is used.  
>> [Ben] Agree, being simultaneous connected on a home link
>> and foreign
>> link does not imply that flow binding must be used.
>>
>> For example, MN wants to receive packets from devices on
>> MN's home link
>> through MN's home attached interface.  Rather than
>> having those devices
>> send the packet to HA who will then forward it to MN's
>> foreign attached
>> interface, MN uses the 'H' flag to turn off ND-proxy at HA
>> and advertise
>> MN's home attached interface.  This way, devices in
>> the home link will
>> send packets to MN's home attached interface.  On the
>> other hand, any
>> packets not from the home link (e.g. from the global
>> Internet) will
>> arrive at HA, who in turn forward it to MN's foreign
>> attached interface.
>>
> 
> 
> 
>       Find din nye laptop på kelkoo.dk. Se de gode tilbud her - http://dk.yahoo.com/r/pat/mm
> 
>