(Apologies up front. I am about to get on a 10 hr flight and will be unable to respond for at least that period)
Hi all, Picking the last message in the thread to reply to. It looks to me that there are at least two different (but related) issues being discussed here a) Spring SRv6 NP behavior (related to the WGLC of that draft) b) The Header insertion drafts and how to deal with them I really think that a) should preferably stay in the spring ML and a pointer to the discussion sent to the 6man mailing list would be in order b) should preferably stay in the 6man ML I think the communities for the two drafts are different and I think the discussions can be more focused if the issues are addressed by the relevant wgs. As to what happens if the spring draft hits the IESG and contains text in violation of RFC8200, I had already sent my thoughts about this back in September https://mailarchive.ietf.org/arch/msg/spring/uA-WxxgBJeMu65SkrKCTL5BJMcU with the relevant text "If a draft violates RFC8200 and it hits the IESG for evaluation, I will certainly hold a DISCUSS position until the violations are fixed.” *In my view*, the authors of the SRv6 NP draft have made an effort to address these violations by removing the header insertion from the draft. We can continue discussing whether penultimate hop popping constitutes a violation on the spring mailing list (I intend to respond to Fernando’a mail there). Thanks Suresh On Dec 7, 2019, at 11:07 AM, Fernando Gont <fg...@si6networks.com<mailto:fg...@si6networks.com>> wrote: On 6/12/19 23:47, Brian E Carpenter wrote: Again, comment at the end... On 07-Dec-19 14:37, Fernando Gont wrote: On 6/12/19 22:15, Brian E Carpenter wrote: [...] and if such a thing is required, an update to RFC8200 should be done. Why does that follow? Alternatively, draft-ietf-spring-srv6-network-programming could acknowledge that it deviates from RFC8200. You can deviate from s "should", not from a "must". This is an outright violation of a spec, rather than a mere "deviation". Whether that's acceptable would be a question for the IETF Last Call rather than any single WG. I would expect that a WG cannot ship a document that is violating an existing spec, where the wg shipping the document is not in a position of making decisions regarding the spec being violated. That would be like a waste of energy and time for all. At the moment, the draft only mentions RFC8200 in a context that discusses neither insertion nor removal of extension headers, which is beside the point. Like draft-voyer, if it describes a violation of RFC8200, shouldn't that be explicit in the text? There's a lot of jargon in draft-ietf-spring-srv6-network-programming. I can't tell from the jargon whether "insert" means "insert on the fly" and whether "Pop the SRH" means "delete on the fly". Should those terms be clarified before the draft advances? Well, if it's not clear to you, it would seem to me that the simple answer would be "yes". But if "insert" refers to the encapsulating node at the SR domain ingress, it's no problem, and if "pop" simply means doing normal routing header processing, it's no problem. It simply isn't clear in the text, at least not clear to me. The fact that a folk that has been deeply involved with IPv6 cannot unequivocally tell what they talking about should be an indication with respect to how ready the document is to be shipped. (pop when you are the destination but SL!=0 is essentially 'in the network removal') THanks, -- Fernando Gont SI6 Networks e-mail: fg...@si6networks.com<mailto:fg...@si6networks.com> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
