Dear OPSAWG and SPRING working group, Based on the feedbacks I received, I updated the document.
Apart from the small editorial changes, the following points have been addressed - updated IANA sections according to RFC 8126 - added ipv6SRHSegmentListSection to facilitate immediate export without data flow manipulation - added Operational Considerations section to described differences between ipv6SRHSegmentBasicList and ipv6SRHSegmentListSection Looking forward for further reviews and comments. Based wishes Thomas -----Original Message----- From: internet-dra...@ietf.org <internet-dra...@ietf.org> Sent: Sunday, March 6, 2022 8:35 AM To: Benoit Claise <benoit.cla...@huawei.com>; Graf Thomas, INI-NET-TCZ-ZH1 <thomas.g...@swisscom.com> Subject: New Version Notification for draft-tgraf-opsawg-ipfix-srv6-srh-02.txt A new version of I-D, draft-tgraf-opsawg-ipfix-srv6-srh-02.txt has been successfully submitted by Thomas Graf and posted to the IETF repository. Name: draft-tgraf-opsawg-ipfix-srv6-srh Revision: 02 Title: Export of Segment Routing IPv6 Information in IP Flow Information Export (IPFIX) Document date: 2022-03-06 Group: Individual Submission Pages: 12 URL: https://www.ietf.org/archive/id/draft-tgraf-opsawg-ipfix-srv6-srh-02.txt Status: https://datatracker.ietf.org/doc/draft-tgraf-opsawg-ipfix-srv6-srh/ Htmlized: https://datatracker.ietf.org/doc/html/draft-tgraf-opsawg-ipfix-srv6-srh Diff: https://www.ietf.org/rfcdiff?url2=draft-tgraf-opsawg-ipfix-srv6-srh-02 Abstract: This document introduces new IP Flow Information Export (IPFIX) information elements to identify the SRv6 Segment Routing Header dimensions and SRv6 Control Plane Protocol that traffic is being forwarded with. The IETF Secretariat
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
