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

[Christian Vogt <christian.vogt@nomadiclab.com>]

Dino -

> 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 a lightweight alternative to the public-key-crypto approach that
Noel is proposing.  Its advantage:  less overhead in terms of processing
and administration.  Its disadvantage:  need to buffer or drop packets
during the mapping validation round-trip (Map-Request/Reply).

Are you buffering or dropping in your current LISP implementation?

- Christian






--
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