Protocol Action: 'Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)' to Proposed Standard (draft-ietf-opsawg-ipfix-srv6-srh-14.txt)

The IESG <iesg-secretary@ietf.org> Wed, 07 June 2023 21:33 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Export of Segment Routing over IPv6 Information in IP Flow Information Export (IPFIX)' to Proposed Standard (draft-ietf-opsawg-ipfix-srv6-srh-14.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-opsawg-ipfix-srv6-srh@ietf.org, mohamed.boucadair@orange.com, opsawg-chairs@ietf.org, opsawg@ietf.org, rfc-editor@rfc-editor.org, rwilton@cisco.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <168617360636.33273.10562908834285378485@ietfa.amsl.com>
Date: Wed, 07 Jun 2023 14:33:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/tHXlzXuMeZ5ksoy9k7nh4J__Iro>

The IESG has approved the following document:
- 'Export of Segment Routing over IPv6 Information in IP Flow Information
   Export (IPFIX)'
  (draft-ietf-opsawg-ipfix-srv6-srh-14.txt) as Proposed Standard

This document is the product of the Operations and Management Area Working
Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-srv6-srh/




Technical Summary

   This document introduces new IP Flow Information Export (IPFIX)
   Information Elements to identify a set of Segment Routing over IPv6
   (SRv6) related information such as data contained in a Segment
   Routing Header (SRH), the SRv6 control plane, and the SRv6 endpoint
   behavior that traffic is being forwarded with.

Working Group Summary

  No controversy is to be reported for the draft. The authors were responsive in
  dealing with the comments raised by reviewers. One aspect that required some
  cycles is related to the IANA actions. For example, previous versions of the
  specification requested the creation of new registries that are redundant with
  existing IANA registries. That design was problematic. That issue and similar
  ones were fixed in subsequent iterations of the draft after consulting with the
  IANA.

Document Quality

  Yes. At least, the following implementations were disclosed:

  * open-source flow collector pmacct: [https://github.com/pmacct/pmacct]
  * VPP: [https://github.com/insa-unyte/vpp-srh-onpath-telemetry]
  * Huawei VRP

Personnel

   The Document Shepherd for this document is Mohamed Boucadair.
   The Responsible Area Director is Robert Wilton.

Protocol Action: 'Export of Segment Routing over … The IESG