[spring] New version update and request for WG adoption of draft-dong-spring-sr-for-enhanced-vpn-09

"Dongjie (Jimmy)" <jie.dong@huawei.com> Tue, 14 July 2020 09:47 UTC

Return-Path: <jie.dong@huawei.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 F0EB03A085A; Tue, 14 Jul 2020 02:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ow_7FWkKF6B4; Tue, 14 Jul 2020 02:47:03 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 5C4DB3A0859; Tue, 14 Jul 2020 02:47:03 -0700 (PDT)
Received: from lhreml720-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 06F2B4FA65CF787A3CC9; Tue, 14 Jul 2020 10:47:02 +0100 (IST)
Received: from dggeme751-chm.china.huawei.com (10.3.19.97) by lhreml720-chm.china.huawei.com (10.201.108.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Tue, 14 Jul 2020 10:47:01 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme751-chm.china.huawei.com (10.3.19.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 14 Jul 2020 17:46:57 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.1913.007; Tue, 14 Jul 2020 17:46:57 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "spring@ietf.org" <spring@ietf.org>
CC: "spring-chairs@ietf.org" <spring-chairs@ietf.org>
Thread-Topic: New version update and request for WG adoption of draft-dong-spring-sr-for-enhanced-vpn-09
Thread-Index: AdZZw7UDMmK5DBufSseMJGiHyOgSOQ==
Date: Tue, 14 Jul 2020 09:46:57 +0000
Message-ID: <a5fa332e0f8e4edf91d6f77bb739fd2e@huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.148.231]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/iW4wi54VSfE9Rn3fAhp2l9rbmF8>
Subject: [spring] New version update and request for WG adoption of draft-dong-spring-sr-for-enhanced-vpn-09
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: Tue, 14 Jul 2020 09:47:06 -0000

Hi all, 

We've submitted a new revision of draft-dong-spring-sr-for-enhanced-vpn. The major changes in this version are: 

1. Francois Clad joined as co-author.

2. Some text is added to clarify the mechanism introduced in this document, and its relationship with the existing work.

3. Solved the recent comment from Joel about reducing the service requirement description in section 4.

4. Some editorial changes

With this update, we believe all the comments received so far have been resolved. Thus the authors would like to request (again) for WG adoption of this document. Thanks.

Best regards,
Jie

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, July 13, 2020 10:46 PM
To: Dongjie (Jimmy) <jie.dong@huawei.com>; Fengwei Qin <qinfengwei@chinamobile.com>; Zhenqiang Li <li_zhenqiang@hotmail.com>; Francois Clad <fclad@cisco.com>; Stewart Bryant <stewart.bryant@gmail.com>; Yongqing Zhu <zhuyq8@chinatelecom.cn>; Takuya Miyasaka <ta-miyasaka@kddi.com>
Subject: New Version Notification for draft-dong-spring-sr-for-enhanced-vpn-09.txt


A new version of I-D, draft-dong-spring-sr-for-enhanced-vpn-09.txt
has been successfully submitted by Jie Dong and posted to the IETF repository.

Name:		draft-dong-spring-sr-for-enhanced-vpn
Revision:	09
Title:		Segment Routing for Resource Guaranteed Virtual Networks
Document date:	2020-07-13
Group:		Individual Submission
Pages:		19
URL:            https://www.ietf.org/internet-drafts/draft-dong-spring-sr-for-enhanced-vpn-09.txt
Status:         https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
Htmlized:       https://tools.ietf.org/html/draft-dong-spring-sr-for-enhanced-vpn-09
Htmlized:       https://datatracker.ietf.org/doc/html/draft-dong-spring-sr-for-enhanced-vpn
Diff:           https://www.ietf.org/rfcdiff?url2=draft-dong-spring-sr-for-enhanced-vpn-09

Abstract:
   This document describes the mechanism to associate network resource
   attributes to Segment Routing Identifiers (SIDs).  Such SIDs are
   referred to as resource-aware SIDs in this document.  The resource-
   aware SIDs retain their original forwarding semantics, but with the
   additional semantics to identify the set of network resources
   available for the packet processing action.  The resource-aware SIDs
   can therefore be used to build SR paths with a set of reserved
   network resources.  In addition, the resource-aware SIDs can also be
   used to build SR based virtual networks, which provide the network
   topology and resource attributes required by customers or services.
   The proposed mechanism is applicable to both segment routing with
   MPLS data plane (SR-MPLS) and segment routing with IPv6 data plane
   (SRv6).


                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat