IETF Logo Mail Archive

[spring] Progressing draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource management

"Dongjie (Jimmy)" <jie.dong@huawei.com> Tue, 19 May 2020 10:38 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 83A193A1368; Tue, 19 May 2020 03:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 sTH9hLlfi6Ci; Tue, 19 May 2020 03:38:08 -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 EF6583A1362; Tue, 19 May 2020 03:38:07 -0700 (PDT)
Received: from lhreml707-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id E82D3B8D42BA9098C463; Tue, 19 May 2020 11:38:02 +0100 (IST)
Received: from dggeme703-chm.china.huawei.com (10.1.199.99) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 19 May 2020 11:38:02 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme703-chm.china.huawei.com (10.1.199.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 19 May 2020 18:38:00 +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, 19 May 2020 18:38:00 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: SPRING WG <spring@ietf.org>
CC: "draft-dong-spring-sr-for-enhanced-vpn@ietf.org" <draft-dong-spring-sr-for-enhanced-vpn@ietf.org>
Thread-Topic: Progressing draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource management
Thread-Index: AdYtyUjIii3UkAvgR0enXZkdrDOJSA==
Date: Tue, 19 May 2020 10:37:59 +0000
Message-ID: <6c9e9271a5e64e2faa2f373d871abaa1@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: multipart/alternative; boundary="_000_6c9e9271a5e64e2faa2f373d871abaa1huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/99ysZMBNxDM_shTLPKqu5K3mCCE>
Subject: [spring] Progressing draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource management
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, 19 May 2020 10:38:10 -0000

Hi all,

The latest version of draft-dong-spring-sr-for-enhanced-vpn was uploaded in March, which describes a generic enhancement to SR to support resource representation and identification, by introducing the resource semantics to SR SIDs. With such enhancement, SR could be used not only for explicit path steering, but could also be used to build resource guaranteed paths or virtual networks. Such SR based resource guaranteed paths or virtual networks can be used as the underlay to support different VPN services. The mechanism introduced in this document is complementary to the existing SR functionalities, and helps to complete the tool set of segment routing.

Based on the discussion on mail list and the presentations on previous IETF meetings, this draft has been revised several times, all the comments received so far has been resolved and reflected in the current version. To move forward, the authors would like to know if there are further comments on this document, and people's opinion on whether it is in the right direction.

Comments and feedbacks are welcome.

Best regards,
Jie

v2.23.0 | Report a Bug | By Email