Re: [Idr] Part 3 of CAR/CT Adoption call (7/14/2022 to 7/27/2022) - Operational Differences

[Robert Raszuk <[e-mail]>]

Hi Jeff,

> The stability dynamics and impact of service route re-resolution are
largely the same as BGP labeled unicast.

I would quite not agree with the above.

Reason being that labeled unicast is about reachability.

Here we are talking about real promises of data plane "performance" hence
we are dealing with completely different set of triggers for various data
plane issues.

Many thx,
R.





On Mon, Jul 25, 2022 at 1:10 AM Jeffrey Haas <[e-mail]> wrote:

> Robert,
>
> A partial comment from my mobile device.
>
> Withdraw encoding will pack much denser. On a total withdraw you likely
> could pack 200 or more prefixes per update.
>
> Implicit withdraw via replacement is clearly same speed as initial
> advertisement.
>
> The stability dynamics and impact of service route re-resolution are
> largely the same as BGP labeled unicast. Thus, beware churning your
> transport routes.
>
>
>
> Jeff
>
> On Jul 24, 2022, at 12:28 PM, Robert Raszuk <[e-mail]> wrote:
>
> 
> Hi Jeff,
>
> Sure 300k times 5 colors makes it 1.5M ...
>
> So I have a few different questions here.
>
> Assume in CAR/CT enabled domain one color has transport problems ... say
> low latency is becoming not so low due to interface queuing is transiently
> congesting for whatever reason between P1 and P2 nodes (not even running
> any BGP).
>
> Q1 - How (by what exact protocol) and how fast such issue with
> forwarding a given color via this domain will be visible at the CAR/CT
> layer ?
>
> Q2 - Assume Q1 is done - do we now need to withdraw 300K routes based on
> one color brownout ?
>
> Q3 - According to your math such CAR/CT reaction will take 30 sec. What if
> transport problem is transient and occurs for say 5-10 sec every 40 sec ?
>
> Q4 - Is there in any document an analysis on dynamics of CAR/CT signalling
> needed to make this at all practical in real deployments vs ppts ?
>
> We keep burning energy on encoding, but apologies if I missed it but I am
> not seeing the full picture here.
>
> Why not advertise just 5 colors between those domains in 5 NLRIs and
> define a new attribute to carry all the interdomain color mappings in it ?
>
> 5 being an example from the section 6.3.2 ... but realistically we could
> perhaps vastly simplify this if we define day one set of well-known colors
> instead of each domain inventing their own definition :)
>
> Maybe I am just too practical here - but your math inspired those
> questions :)
>
> Many thx,
> R.
>
>
> On Sun, Jul 24, 2022 at 4:47 PM Jeffrey Haas <[e-mail]> wrote:
>
>> On Sun, Jul 24, 2022 at 10:44:49AM +0530, Ketan Talaulikar wrote:
>> > The scalability requirements are captured here:
>> >
>> https://datatracker.ietf.org/doc/html/draft-hr-spring-intentaware-routing-using-color-00#section-6.3.2
>> >
>> > This is the merged document that, I believe, captures the consensus that
>> > both the CAR and CT solutions aim to address.
>>
>> Thanks, Ketan.
>>
>> Roughly 1.5 million routes.
>>
>> Presuming an example 10k update per second handling, roughly 2.5 minutes
>> of
>> convergence time without packing optimizations.
>>
>> -- Jeff
>>
>