Hi, As an individual contributor, please find below some comments:
-- Isn't this document specific to the MPLS dataplane? If so, it could be indicated in the introduction, and possibly in the abstract. Then this indication could be removed from the 1rst sentence of sections 2 & 3. -- §3 "Mapping entries have an explicit context which includes the topology and the SR algorithm." A priori you could add "the routing protocol". -- §3 "When conflicts occur, it is not possible for routers to know which of the conflicting advertisements is "correct". If a router chooses to use one of the conflicting entries forwarding loops and/or blackholes may result unless it can be guaranteed that all other routers in the network make the same choice. Making the same choice requires that all routers have identical sets of advertisements and that they all use the same selection algorithm. » I think we agree on the technical part, but I found the formulation slightly biased. I would propose "When conflicts occur, it is not possible for routers to know which of the conflicting advertisements is "correct". In order to avoid forwarding loops and/or blackholes, there is a need for all nodes to make the same choice. Making the same choice requires that all routers have identical sets of advertisements and that they all use the same selection algorithm. This is the purpose of this document. » -- §3.1 "Various types of conflicts may occur" What about :s/Various/Two -- I agree with Robert's and Uma's comment with regards to making this conflict resolution an inter- protocol/routing_table issue. In particular, between SR domains, there is not requirement to have unique SIDs. Hence between PE and CE, between ASes (both within and across organization), the same SID could be reused independently). > From: Les Ginsberg (ginsberg) [mailto:[email protected]] > Sent: Sunday, May > 01, 2016 7:11 AM > > We are indeed defining conflict resolution across all the SID advertisements > regardless of source (protocol or SRMS) > Why? Because we need consistent use of SIDs in the forwarding plane No: in the forwarding plane, we need a consistent use of MPLS label. Plus only within an SR domain. Actually, even within a domain, this is dependent on whether SRGB is configured on a per node or a per protocol basis. I'm not sure how much the agreement has been reached on that one. -- Typo: §2 OLD : Range 3: (500, 5990 NEW : Range 3: (500, 599) (somewhat significant as otherwise range 3 conflict with range 2) Thanks, Regards, Bruno _________________________________________________________________________________________________________________________ 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
