Re: Size of CR in CRH

[Nick Hilliard <[e-mail]>]

Ron Bonica wrote on 19/05/2020 19:01:
> So, allocating two Routing types may be the best solution.

yeah, the hardware constraints requirement is troublesome - hey, we're 
all ToR junkies these days - but the more I think about it, the more 
complex this becomes from an operational / implementation point of view, 
for example:

- do you define SID size on a per domain or per node or a per-SID + 
per-node basis?

- if per-domain, how do you implement non-service affecting migration 
from 16-bit to 32-bit?

- without using differentiating CLI syntax, can you manually define a 
mechanism to allow a 16-bit identifier to be configured in a 32-bit SID?

- the distribution protocols needs to become aware of multiple SID sizes

- is (sid16)32768 the same as (sid32)32768. If not, why not? If so, then 
why?  How can this be explained either by or to the TAC agent at 03:00 
over a noisy, laggy phone line in a time-constrained maintenance window 
involving a P1 where neither of you speaks the other's language natively?

- how many segments do you really need to program for actual networks 
(1? 10? 50?), and how deep can you inspect on merchant silicon of today, 
and currently in development? I.e. how badly would your flexibility be 
hobbled if SIDs were one size only?

Nick