Hi Stephane,
On 8/19/15 10:33 , [email protected] wrote:
Hi Peter,
Inline comments
Stephane
-----Original Message-----
From: Peter Psenak [mailto:[email protected]]
Sent: Wednesday, August 19, 2015 09:53
To: LITKOWSKI Stephane SCE/IBNF; Pushpasis Sarkar; Eric Rosen; SPRING WG
Subject: Re: [spring] SRGBs, indexes, and topologies within a domain
Stephane,
there are two things involved here - configuration and advertisement.
If you look at the SR drafts for both IGPs, both MTID and algorithm is
advertised with Prefix SID, not with SRGB.
[SLI] Agree that this is the way today.
given that multiple vendors have shipping implementation using the
exiting encoding, changing it now may be problematic.
That does not mean you have to manually configure prefix SID for each MTID or
algorithm - there are ways how this can be achieved in an automated way while
advertising a single topology/algorithm agnostic SRGB.
[SLI] Could you precise how you will do it ? Because using an offset as already
proposed causes some collision or unusable indexes within the range. Something
else in mind ?
whether you use offset or a new SRGB both have its challenges. I do not
see a clear advantage of per MTID/algorithm SRGB - definitely not the
one that would justify the change in existing IGP encoding.
thanks,
Peter
thanks,
Peter
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
.
_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
