[spring] Fwd: Protocol Action: 'SRv6 Network Programming' to Proposed Standard (draft-ietf-spring-srv6-network-programming-28.txt)

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 06 January 2021 17:22 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0157C3A12C0 for <spring@ietfa.amsl.com>; Wed, 6 Jan 2021 09:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level:
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C5y7thy2_kUk for <spring@ietfa.amsl.com>; Wed, 6 Jan 2021 09:22:04 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 031773A1281 for <spring@ietf.org>; Wed, 6 Jan 2021 09:21:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4D9x4C5HNkz1nvY9 for <spring@ietf.org>; Wed, 6 Jan 2021 09:21:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1609953707; bh=tV3DcvVZCgv5jk7VIQWzwJ0lx15DkOcdXkxpbI7WtDc=; h=Subject:References:To:From:Date:In-Reply-To:From; b=SKvtNelMhd/AxxdiGuu4vtTxFZf5d+Oh1mEFL/Mm3Cn/fb89AQSz1XRtpEynu+vdi iJ5QBdonD93WuMVs7GnTqOrSFPy7h18B9cjSNXYkWop4NA2XNhAql68V1Eu2EVINni o1WlTHQvTM8aLuEh4Vu7MvDJMyhhdgWdcB0UhrpI=
X-Quarantine-ID: <ceIeTe2obDSH>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4D9x4C08nlz1nwK4 for <spring@ietf.org>; Wed, 6 Jan 2021 09:21:46 -0800 (PST)
References: <160994616746.20419.12554367019711641427@ietfa.amsl.com>
To: "spring@ietf.org" <spring@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Forwarded-Message-Id: <160994616746.20419.12554367019711641427@ietfa.amsl.com>
Message-ID: <a1e43d55-8dd3-0b48-1dff-7277b651bc59@joelhalpern.com>
Date: Wed, 06 Jan 2021 12:21:45 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <160994616746.20419.12554367019711641427@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/xzHwWaf7XUvlFAQj4H4QNwSBa0o>
Subject: [spring] Fwd: Protocol Action: 'SRv6 Network Programming' to Proposed Standard (draft-ietf-spring-srv6-network-programming-28.txt)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jan 2021 17:22:12 -0000

Congratulations to the working group, and many thanks to the authors for 
their consistent and prompt efforts to address the comments from the IESG.

Yours,
Joel


-------- Forwarded Message --------
Subject: Protocol Action: 'SRv6 Network Programming' to Proposed 
Standard (draft-ietf-spring-srv6-network-programming-28.txt)
Date: Wed, 06 Jan 2021 07:16:07 -0800
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: Bruno Decraene <bruno.decraene@orange.com>, Joel Halpern 
<jmh@joelhalpern.com>, The IESG <iesg@ietf.org>, 
draft-ietf-spring-srv6-network-programming@ietf.org, 
jmh@joelhalpern.com, martin.vigoureux@nokia.com, 
rfc-editor@rfc-editor.org, spring-chairs@ietf.org, spring@ietf.org

The IESG has approved the following document:
- 'SRv6 Network Programming'
   (draft-ietf-spring-srv6-network-programming-28.txt) as Proposed Standard

This document is the product of the Source Packet Routing in Networking
Working Group.

The IESG contact persons are Alvaro Retana, Deborah Brungard and Martin
Vigoureux.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-network-programming/





Technical Summary

    The SRv6 Network Programming framework enables a network operator or
    an application to specify a packet processing program by encoding a
    sequence of instructions in the IPv6 packet header.

    Each instruction is implemented on one or several nodes in the
    network and identified by an SRv6 Segment Identifier in the packet.

    This document defines the SRv6 Network Programming concept and
    specifies the base set of SRv6 behaviors that enables the creation of
    interoperable overlays with underlay optimization (Service Level
    Agreements).

Working Group Summary

This document is a foundation for SRv6. It has been largely reviewed, 
commented and supported.
There is a strong controversy regarding the Penultimate Segment Pop 
(PSP) flavor which allows an IPv6 source node to instruct the 
penultimate SRv6 EndPoint (identified, in the IPv6 header, by its IPv6 
address) to remove the SRH from the IPv6 packet before the packet reach 
the final IPv6 destination (the Ultimate SRv6 EndPoint). The consensus 
to keep that section was particularly rough.

An Appeal to the IESG regarding WGLC of 
draft-ietf-spring-srv6-network-programming was made: 
https://www6.ietf.org/iesg/appeal/gont-2020-04-22.txt

Document Quality

The specification has multiple implementations, deployments and interop 
tests.
In particular: - There are multiple hardware and software 
implementations. Some are reported in 
https://tools.ietf.org/html/draft-matsushima-spring-srv6-deployment-status-06#section-4
- There are multiple deployments. Some are reported in 
https://tools.ietf.org/html/draft-matsushima-spring-srv6-deployment-status-06#section-2
- There have been multiple public interoperability tests 
https://tools.ietf.org/html/draft-matsushima-spring-srv6-deployment-status-06#section-5

Personnel

    The Document Shepherd was first Bruno Decraene and then Joel Halpern
    The Responsible Area Director is Martin Vigoureux.