Subject: [spring] FW: Protocol Action: 'IPv6 Segment Routing Header (SRH)' to Proposed Standard (draft-ietf-6man-segment-routing-header-26.txt)

From: <[email-masked]>
Date: Thu, 24 Oct 2019 13:59:15 +0000

FYI: 'IPv6 Segment Routing Header (SRH)' has been approved by the IESG
https://datatracker.ietf.org/doc/draft-ietf-6man-segment-routing-header/

--Bruno

-----Original Message-----
From: ipv6 [mailto:[email-masked]] On Behalf Of The IESG
Sent: Thursday, October 24, 2019 3:47 PM
To: IETF-Announce
Cc: [email-masked]; [email-masked]; Robert Hinden; The IESG; [email-masked]; [email-masked]; [email-masked]
Subject: Protocol Action: 'IPv6 Segment Routing Header (SRH)' to Proposed Standard (draft-ietf-6man-segment-routing-header-26.txt)

The IESG has approved the following document:
- 'IPv6 Segment Routing Header (SRH)'
  (draft-ietf-6man-segment-routing-header-26.txt) as Proposed Standard

This document is the product of the IPv6 Maintenance Working Group.

The IESG contact persons are Éric Vyncke and Suresh Krishnan.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-segment-routing-header/

Technical Summary

   Segment Routing is designed to be applied to the IPv6 data plane using
   a new type of Routing Extension Header (SRH) in this document.  This
   document describes the Segment Routing Extension Header and how it is
   used by Segment Routing capable nodes.

   The Segment Routing Architecture [RFC8402] describes Segment Routing
   and its instantiation in two data planes MPLS and IPv6.  The encoding
   of IPv6 segments in the Segment Routing Extension Header is defined in
   this document.

Working Group Summary

   The work on SRH has been underway for a long time.  The first working
   group version of the draft was published in December 2015, the first
   working group call started on March 2018.  Given the number of issues
   that were raised the chairs started an issue tracker.  Fifty issues
   were tracked.  After further discussion, many new drafts, and
   confirmation at IETF 104, the chairs started a second working group
   last call in May 2019.  After further discussion two new drafts were
   published and the chairs concluded the last call and declared that
   there is consensus to advance this document on 14 June 2019.  See:

   https://mailarchive.ietf.org/arch/msg/ipv6/_9OrqvZYpDB0lJEE8jxB0a0N44M

   The chairs believe there is a strong consensus to advance this
   document, but it was not unanimous.

   There remains a desire by a few people to add more clarity on
   mutability of segment lists and other fields.  The chairs conclusion
   is that the text added since the last call closes this topic, but a
   few would like to see more.

Document Quality

   Section 9 lists current implementations, these include:

      Linux Kernel v4.14
      Cisco Systems IOS XR and IOS XE
      FD.io  VPP/Segment Routing for IPv6
      Barefoot Networks Tofino NPU

   Detailed reviews were done in the course of review this document in
   the 6man working group.  Several people did extensive reviews, they
   include Joel Halpern, Ron Bonica, Mark Smith, and Tom Herbert.  The
   6man chairs have also reviewed this document.  These reviews resulted
   in many improvements to the document.

   No MIBs or other media types to be reviewed.

Personnel

   Bob Hinden is the Document Shepherd. 
   Suresh Krishnan is the Responsible AD.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email-masked]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.