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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Wed, 17 June 2020 11:32 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 ACF483A09B8 for <spring@ietfa.amsl.com>; Wed, 17 Jun 2020 04:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 G5J8GtPtqRGn for <spring@ietfa.amsl.com>; Wed, 17 Jun 2020 04:32:39 -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 B21B43A09B7 for <spring@ietf.org>; Wed, 17 Jun 2020 04:32:38 -0700 (PDT)
Received: from lhreml718-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 43D57341CB3511A0E6E6 for <spring@ietf.org>; Wed, 17 Jun 2020 12:32:37 +0100 (IST)
Received: from dggeme702-chm.china.huawei.com (10.1.199.98) by lhreml718-chm.china.huawei.com (10.201.108.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Wed, 17 Jun 2020 12:32:36 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme702-chm.china.huawei.com (10.1.199.98) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 17 Jun 2020 19:32:33 +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; Wed, 17 Jun 2020 19:32:33 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: 'SPRING WG' <spring@ietf.org>
Thread-Topic: Progressing draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource management
Thread-Index: AdYtyUjIii3UkAvgR0enXZkdrDOJSAWx5p7w
Date: Wed, 17 Jun 2020 11:32:33 +0000
Message-ID: <7948b50a4870431bb6b634ee125deab0@huawei.com>
References: <6c9e9271a5e64e2faa2f373d871abaa1@huawei.com>
In-Reply-To: <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_7948b50a4870431bb6b634ee125deab0huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/7Re34z0ZuNQ-fEeIVJ4Ra-iTEmE>
Subject: Re: [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: Wed, 17 Jun 2020 11:32:41 -0000

Hi all,

Thanks a lot for the mail discussion on this document in the past month. I summarized the comments received so far, please let me know if I miss anything:

1. Several operators shows their interests in introducing resource reservation/identification capability in SR.

2. There was comments that the meaning of isolation in this draft needs to be further clarified.

3. There was some discussion about whether resource reservation is necessary comparing to Diffserv QoS with centralized resource management. The initial conclusion from the discussion is that both diffserv and resource reservation based mechanisms are tools developed by IETF to meet the customers and operators' requirement, and each can have its application scenarios. Operators can choose to use either one for specific service/customer in their network.

4. There was question about whether per-VPN state will be introduced to SR network, this has been clarified and the brief answer is "no".

5. There was also discussion about whether this document should be informational or standard track, the authors are open to the document type, and would like to leave this for the WG to decide during the progress of adoption.

The next step for the authors is to provide a new revision of the draft based on these received comments. Thanks.

Best regards,
Jie

From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Dongjie (Jimmy)
Sent: Tuesday, May 19, 2020 6:38 PM
To: SPRING WG <spring@ietf.org>
Cc: draft-dong-spring-sr-for-enhanced-vpn@ietf.org
Subject: [spring] Progressing draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource management

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