Hi Wim, Many thanks for taking part in the discussion. Could you please elaborate? e.g. what do you mean by ”who” and “wrong” on what? I could see multiple interpretations, but it would probably be faster if you elaborate by yourself.
Thanks -- Bruno From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Henderickx, Wim (Wim) Sent: Tuesday, January 05, 2016 7:41 PM To: Martin Horneffer; Les Ginsberg (ginsberg); spring@ietf.org; LITKOWSKI Stephane SCE/OINIS Subject: Re: [spring] draft-ginsberg-spring-conflict-resolution: SRGB INCONSISTENCY My main question on the proposal is how do we tell who is right and who is wrong? From: spring <spring-boun...@ietf.org<mailto:spring-boun...@ietf.org>> on behalf of Martin Horneffer <m...@nic.dtag.de<mailto:m...@nic.dtag.de>> Date: Tuesday 5 January 2016 at 13:05 To: "Les Ginsberg (ginsberg)" <ginsb...@cisco.com<mailto:ginsb...@cisco.com>>, "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, Stephane Litkowski <stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>> Subject: Re: [spring] draft-ginsberg-spring-conflict-resolution: SRGB INCONSISTENCY Hello Les, Acee, Stephane, everyone, happy new year! From an operator's (carrier's) point of view I clearly and strongly support this alternative solution: Treat an inconsistent set of SRGB announcements as broken and ignore it. - It is the simplest solution. - It only affects traffic of the badly configured and implemented router. - It gives a clear indication to the operator where they have to repair something. With respect to Stephane's comments: - I would also support a repetition or clarification that an inconsistent set of SRGB annoucements is broken. - No strong opinion from my side as how to define the offending node as non-SR-capable as I don't see any use case for nodes with only adjacency SIDs. Best regards, Martin Am 04.01.16 um 06:55 schrieb Les Ginsberg (ginsberg): One of the topics discussed in https://datatracker.ietf.org/doc/draft-ginsberg-spring-conflict-resolution/ is how to handle inconsistent SRGB advertisements from a given node. The draft defines one possible solution -from Section 2: " Each range is examined in the order it was advertised. If it does not overlap with any advertised range which preceded it the advertised range is used. If the range overlaps with any preceding range it MUST NOT be used and all ranges advertised after the first encountered overlapping range also MUST NOT be used." This is one instance of a class of solutions which attempt to make use of part of the advertisements even when there is some inconsistency (overlap) in the set of SRGB ranges received. A more complete discussion of this class of solutions can be seen in https://mailarchive.ietf.org/arch/attach/spring/txtk0n56G.txt - many thanx to Bruno for writing this. However, there is an alternative solution which was suggested (notably by Acee Lindem) after the draft was written. This alternative is to ignore the entire set of SRGB advertisements and treat the problematic router as if it were not SR MPLS capable. This alternative was discussed during the presentation in SPRING WG at IETF94 (see https://www.ietf.org/proceedings/94/slides/slides-94-spring-2.pdf slide #3<https://www.ietf.org/proceedings/94/slides/slides-94-spring-2.pdf%20slide%20#3>). It is also discussed in Bruno's post (https://mailarchive.ietf.org/arch/attach/spring/txtk0n56G.txt - see Section 2.2). The basis of the alternative solution is that a correct implementation should never allow inconsistent SRGB ranges to be successfully configured (let alone advertised). So this is not a case of a misconfiguration – it is a case of a defective implementation. It then seems appropriate to put the onus on the originating router to only send valid SRGB advertisements rather than forcing all the receivers to try to "correct" the invalid information in some consistent way. This has a number of advantages: 1. It is by far the simplest to implement 2. It isolates the router which is untrustworthy 3. As the problem can only occur as a result of a defective implementation the behavior of the originating router is unpredictable – it is therefore safer not to use the information It is worth noting that since the invalid advertisement is the result of some sort of defect in the originating router’s implementation, it is not safe to assume that the source will actually be using the advertised SRGB in a manner consistent with the selective choice made by the receiving routers. I therefore propose that the above quoted text from https://datatracker.ietf.org/doc/draft-ginsberg-spring-conflict-resolution/ be replaced with the following: “The set of received ranges is examined . If there is overlap between any two of the advertised ranges the entire SRGB set is considered invalid and is ignored. The originating router is considered to be incapable of supporting the SR-MPLS forwarding plane. Routers which receive an SRGB advertisement with overlapping ranges SHOULD report the occurrence.” Comments? Les _______________________________________________ spring mailing list spring@ietf.org<mailto:spring@ietf.org>https://www.ietf.org/mailman/listinfo/spring _________________________________________________________________________________________________________________________ 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
