Re: [Teas] [spring] FW: New Version Notification fordraft-dong-spring-sr-for-enhanced-vpn-07.txt

"Dongjie (Jimmy)" <> Wed, 11 March 2020 08:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 37C573A14DC; Wed, 11 Mar 2020 01:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S0jSJQOPPgzF; Wed, 11 Mar 2020 01:36:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 58BE73A14DB; Wed, 11 Mar 2020 01:36:51 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 78485DD3F9428319BE55; Wed, 11 Mar 2020 08:36:47 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 11 Mar 2020 08:36:46 +0000
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 11 Mar 2020 16:36:44 +0800
Received: from ([]) by ([]) with mapi id 15.01.1713.004; Wed, 11 Mar 2020 16:36:44 +0800
From: "Dongjie (Jimmy)" <>
To: "" <>
CC: "" <>, "" <>, "" <>
Thread-Topic: Re:[spring] FW: New Version Notification fordraft-dong-spring-sr-for-enhanced-vpn-07.txt
Thread-Index: AQHV91rMYhcvH25sH0eXGlzU6ouB6ahDA59Q
Date: Wed, 11 Mar 2020 08:36:44 +0000
Message-ID: <>
References:, <>
In-Reply-To: <>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_1e23e8f7eea24d4189937e39c7179e4dhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [Teas] [spring] FW: New Version Notification fordraft-dong-spring-sr-for-enhanced-vpn-07.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Mar 2020 08:36:54 -0000

Hi Ran,

Thanks for your feedback. Please see my replies inline with [Jie]:

From: []
Sent: Wednesday, March 11, 2020 12:08 PM
To: Dongjie (Jimmy) <>
Subject: Re:[spring] FW: New Version Notification fordraft-dong-spring-sr-for-enhanced-vpn-07.txt

Hi Jie,

I don’t think it’s time to call for adoption. Teas Slice DT is still working on the definition and the framework of the transport slice,which has not been accepted by the teas working group.
[Jie] If you read the latest version or the previous (-06) version of this document, you would find that this draft defines a generic enhancement to SR data plane. Although network slicing is one of the target use cases, this document is relatively independent from the discussion and progress of the NS design team. Thus I don’t see a reason of not progressing this work in SPRING.

For the draft, I have some comments:

1.  Compared with the ietf-teas-enhanced-vpn, It seems like that there is no more new technology. What's the meaning of this draft as standard track?

[Jie] The proposed enhancement to SR data plane is clearly described in the draft. , in short it introduces new semantics to SR SIDs, so that the SIDs could be used to identify the set of resources used for packet processing.

2.  Control plane extensions that you referred in this draft is ietf-dong-lsr-sr-enhanced-vpn, and ietf-dong-idr-bgpls-sr-enhanced-vpn, and we also have a series of control plane drafts:, , satisfying the same requirement. So Control plane extensions are still an open question, and needing further discussing.

[Jie] Normally the SR data plane functions and procedures are defined in SPRING first, then the control plane extensions would be discussed and defined in relevant WGs to support the required SR data plane functions. Do you mean the control plane should be discussed first?

3.  For slice resources, our draft:  induced slice-id(AII) for slice resources management, and our solution can differentiate them (e.g. L2 link or L3 interface), how to compute SR-BE or SR-TE path according to AII combined with other criteria. This isnot very clear in your draft.

[Jie] Again, this document is not for network slicing only, while it seems the draft you mentioned is. Besides, the mechanisms and example of using the resource-aware SIDs for packet forwarding with SR based explicit path and loose path has been described in this document. Please refer to section 2 and section 4.2 for more information.

Best regards,




发件人:Dongjie(Jimmy) <<>>
收件人:'SPRING WG List' <<>>;
抄送人<> <<>>;
日 期 :2020年03月10日 18:00
主 题 :[spring] FW: New Version Notification fordraft-dong-spring-sr-for-enhanced-vpn-07.txt
Hi all,

We've submitted a new revision of draft-dong-spring-sr-for-enhanced-vpn.

This version includes some editorial changes based on the previous -06 version, which have solved the comments received before and during IETF 106 meeting.

The authors believe this document is ready for WG adoption, and thus solicit the WG to consider initiating the adoption poll on it. Thanks.

Best regards,

-----Original Message-----
From:<> []
Sent: Monday, March 9, 2020 4:33 PM
To: Takuya Miyasaka <<>>; Dongjie (Jimmy) <<>>; Stewart Bryant <<>>; Yongqing Zhu <<>>; Fengwei Qin <<>>; Zhenqiang Li <<>>
Subject: New Version Notification for draft-dong-spring-sr-for-enhanced-vpn-07.txt

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

Name:        draft-dong-spring-sr-for-enhanced-vpn
Revision:    07
Title:        Segment Routing for Resource Guaranteed Virtual Networks
Document date:    2020-03-09
Group:        Individual Submission
Pages:        18

   This document describes the mechanism to associate Segment Routing
   Identifiers (SIDs) with network resource attributes.  The resource-
   aware SIDs retain their original functionality, with the additional
   semantics of identifying the set of network resources available for
   the packet processing action.  These SIDs can be used to build SR
   paths with reserved network resources.  In addition, these SID can
   also be used to build SR based virtual networks, which provide the
   network topology and resource attributes required by particular
   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

The IETF Secretariat

spring mailing list<>