> On Mar 1, 2017, at 3:39 PM, bruno.decra...@orange.com wrote: > > Hi Stefano, > >> From: Stefano Previdi (sprevidi) [mailto:sprev...@cisco.com] > Sent: >> Tuesday, February 28, 2017 10:16 AM >> >> Hi Bruno, >> >> thanks for the review. I integrated all the comments in the new version I'm >> going to submit >> very soon. > > > Thanks. > > >> One last comment here below: >> >>> On Feb 22, 2017, at 2:00 PM, bruno.decra...@orange.com wrote: >>> >>> 2) For the document write up, are there any known deployment of >>> draft-ietf-spring- >> segment-routing-msdc? >>> >>> >>> 3) § 2.1. Reference design >>> >>> " o Each node is its own AS (Node X has AS X) >>> >>> * For simple and efficient route propagation filtering, Nodes 5, >>> 6, 7 and 8 share the same AS, Nodes 3 and 4 share the same AS, >>> Nodes 9 and 10 share the same AS. >>> >>> * For efficient usage of the scarce 2-byte Private Use AS pool, >>> different Tier-3 nodes might share the same AS. >>> >>> * Without loss of generality, we will simplify these details in >>> this document and assume that each node has its own AS." >>> >>> >>> First 2 bullets are contradicting each other's. >> >> >> why so ? First bullet refers to tier-1 and tier-2. second bullet refers to >> tier-3. > > Bullet 1: "Each node is its own AS" > Bullet 2: "Nodes 5, 6, 7 and 8 share the same AS”
ok sorry, the indent was such that I was confused. > Looks a priori contradicting. > Now thinking more about this, and given that on your 5-stage clos topology > nodes 5, 6, 7 and 8 are not connected to each other's and any flow has no > valid reason to cross two of them, I now see what you mean. > > I would then propose the following change: > OLD: share the same AS > NEW: use the same AS number I agree. I also think that “sharing” has other implications which are not intended here. > It may look the same, but the two nodes are indeed in different ASes. But > they use the same AS number, just like private AS number. > > Or may be it's just me ;-) So up to you. no, it’s me too ;-) s. > > Thanks, > -- Bruno >> >> thanks. >> s. >> > > > _________________________________________________________________________________________________________________________ > > 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 spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
