Re: I-D ACTION:draft-nordmark-multi6dt-shim-00.txt

marcelo bagnulo braun <[email protected]> Sat, 30 Oct 2004 20:55:37 +0200
Newsgroups gmane.ietf.multi6
Message-ID <496A5E72-2AA5-11D9-AB06-000D93ACD0FE@it>
>> Good news. This is wrong (and I didn't realise it when analyzing 
>> NOID).
>> Flow Labels are not unique on their own and cannot be used for
>> anything on their own. You must always lookup a 3tuple.But if the
>> received  {Flow Label, Source Locator, Dest Locator} is in the set
>> {Flow Label, {Source Locators}, {Dest Locators}} corresponding to
>> a particular {Flow Label, Source ULID, Dest ULID} 3tuple, the shim
>> *knows* that it is a multi6 packet.
>
> If the {flow label, src locator, dst locator} is used to identify the 
> state then you are right. But that prevents a possible optimization 
> with changing locator sets (think mobility) by requiring that multi6 
> signaling be complete to tell the peer of the new locator before that 
> locator can be used as the source.
>

well, but in this case, there is also some security information nneded 
to authenticate the new locator, so the receiver will have additional 
information for the demux of this packet i guess.


regards, marcelo
------------------------------------------
Please note that my former email address
[email protected] is no longer in use
Please send mail to:
marcelo at it dot uc3m dot es
------------------------------------------