Hi Sue and the WG I support publication of the draft (in its current form) I am aware of implementations of the draft
Thanks Regards … Zafar From: BESS <bess-boun...@ietf.org> on behalf of Susan Hares <sha...@ndzh.com> Date: Wednesday, June 29, 2022 at 6:45 PM To: "spring@ietf.org" <spring@ietf.org>, "b...@ietf.org" <b...@ietf.org>, "i...@ietf.org" <i...@ietf.org> Subject: [bess] FW: Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30) Spring and BESS WGs Just a reminder, if you wish to provide any feedback on IDR publication of draft-ietf-idr-segment-routing-te-policy-18.txt, please do so before Friday 6/30/2022. The mail thread for IDR is at the following link. https://mailarchive.ietf.org/arch/msg/idr/r8aWDJDWyWexgpLZagKaFrTePG8/ At this time, as the IDR shepherd for this draft, the consensus is that the IDR will forward the draft to the IESG on Friday. Please do not reply to this email. You can comment on the original IDR thread or or send email directly (sha...@ndzh.com<mailto:sha...@ndzh.com> or idr-cha...@ietf.org<mailto:idr-cha...@ietf.org>). Cheers, Sue ----------------------------- From: Susan Hares Sent: Friday, June 17, 2022 9:15 AM To: i...@ietf.org<mailto:i...@ietf.org> Subject: Call for publication of draft-ietf-idr-segment-routing-te-policy-18 - with multiple partial implementations (6/17 to 6/30) IDR: This is a 2 week call for approval for publication of draft-ietf-idr-segment-routing-te-policy-18 (https://datatracker.ietf.org/doc/html/draft-ietf-idr-segment-routing-te-policy-18). This draft has past WG LC, and it has been implemented by five separate commercial vendors. (I do not have any implementation reports from open-source vendors.) According to the implementation report, not all features have been implemented. https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-segment-routing-te-policy%20implementations%20 At this point, it appears we do not have 2 implementations Supporting the following TLV codes: - ENLP sub-TLV (code 14) - Priority sub-TLV (code 15) - SRv6 Binding SID (code 20) - Policy Candidate Path Name sub-TLV (code 129), and - Policy Name Sub-TLV (code 130). And only segment types A and B out of types A-K have been implemented. Should the IDR WG: a) publish this draft as is, b) put it in a “awaiting implementations” hold until more features are implemented, c) remove unimplemented features and publish? If you are an implemented (open-source or commercial), please Update your implementation status on the implementation page Or send me a note regarding your implementation. Cheers, Sue
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
