Re: [spring] Proposed policy on reporting implementation and interoperability

2022-08-13 Thread Robert Raszuk
> Robert, why would we discard information? I view support of all normative MUSTs as something necessary to claim (full or partial) support of a given draft. No support of even a single MUST makes an implementation not something which should be part of a given spec. Discard was about the comment

Re: [spring] Proposed policy on reporting implementation and interoperability

2022-08-13 Thread Joel Halpern
Robert, why would we discard information?  It seems that if folks do report such partial compliance, it is helpful to include it. Whether anyone will make such a report remains to be seen. Yours, Joel On 8/13/2022 1:56 PM, Robert Raszuk wrote: Hi Jeff, > I’d expect to see all and each MUST

Re: [spring] Proposed policy on reporting implementation and interoperability

2022-08-13 Thread Robert Raszuk
Hi Jeff, > I’d expect to see all and each MUST statements implemented for an > implementation to be able to claim to be 100% compliant with the specification. Glad we agree on that. But my point was not so much to claim 100% compliance or 90% compliance. My point was that any report which indica

[spring] I-D Action: draft-ietf-spring-srv6-path-segment-04.txt

2022-08-13 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Packet Routing in Networking WG of the IETF. Title : Path Segment for SRv6 (Segment Routing in IPv6) Authors : Cheng Li