Re: [RAM] Re: the separation of ID/RLOC

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

>> Whether or not long update delays are an issue depends, as you say, on
>> the change frequency and granularity.  However, any assumptions that we
>> make in this regards should be very careful.  Our goal is to give edge
>> networks more freedom in traffic engineering and provider selection.
>> And it would be great if we could reach this goal without restrictions
>> -- such as in terms of change frequency or granularity.
> 
> Isn't this issue easily resolved by advertising more than one locator?

Tony,

if you want to an enable edge network to decide through which provider
ingress packets are received, then the edge network must be able to tell
remote edge networks one specific transit locator to which they should
send packets.

If an edge network advertises more than one transit locator, then it is
up to remote edge networks to select one of those.  This takes away the
ability for edge networks to select an ingress provider.  Additionally,
you still need a locator selection mechanism for the remote edge network
-- which may involve its own signaling overhead, delay, and packet loss.

With Six/One [1], edge networks can select both their ingress and egress
providers, and they can change them within 1 RTT without signaling.
There is also no packet loss if the old provider is still operational at
the time of the change.  And the granularity of provider selection (both
ingress and egress) is on a per-communication-session level.

[1] http://users.piuha.net/chvogt/pub/2007/draft-vogt-rrg-six-one-00.txt

- Christian


_______________________________________________
RAM mailing list
RAM at iab.org
https://www1.ietf.org/mailman/listinfo/ram