Re: [RRG] mapping "issues" list from this morning

[dimitri papadimitriou <dpapadimitriou@psg.com>]

hi - a couple of comments/suggestions here below:

"- Whether there will be any delay at all (might even get there
  faster)."

-> differential delay would better translate this issue

-> also consider mapping entries change/variation for ongoing traffic
flows and the side effect with corrupted entries

"- Number of packets that might be delayed, dropped."

-> add "effect on e.g. short elastic and long bulk flows"

"- Effect on transport layer, session."

-> for the transport layer (e.g. flow and congestion control)

in "Push, Poll, Hybrids"

-> distinguish communication between MP and communication between TRs and MP

-> in-band/user-driven trigger impact for mapping resolution (more than
longest match-prefix lookup as performed today)

add in "mapping points"

-> distribution of the mapping points vs modes (push, pull, hybrid)

-> impact of mapping point failure (for LISP 2 and 3 for inst. a there
is no fate sharing this would result in serious impact)

add issue of evolvability

-> EID allocation and structure (noticing that a 1:1 mapping does not
resolve any routing system scalability issue)

-> mapping system scalability and complexity

editorials

"Push, Poll, Hybrids"

-> replace by "Push, Pull, Hybrids"

-- i suppose this list is going to be translated into a document that
proposals making use of mapping system will consider and address.

thanks,
-d.
Scott Brim wrote:
> Attached is the list of criteria from this morning, modulo a little 
> editing.  This is not complete.  Please add *and* delete and clarify.
>
> My own comments will follow.
>
> Scott


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