[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures



This ambiguity would only be the case if the ETR has only one RLOC.
(Hint - this is a "design implementation" detail that differentiates different LISP proposals, either formally documented or under discussion on the list.)

Only true if the ETR is gleaning a source EID to a source RLOC. But you want to validate the mapping so the ETR sends a Map-Request (with a newly allocated nonce) back to the ITR where the Map-Reply in response has a complete locator-set for the *EID-prefix* (that the original invoking source EID matches to).

This is the mobility feature we prototyped in LISP and are not publicly admitting. ;-)

Dino


--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg