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

"Dongjie (Jimmy)" <jie.dong@huawei.com> Mon, 25 May 2020 02:54 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 BC0193A0945; Sun, 24 May 2020 19:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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 8flm8AH0iff0; Sun, 24 May 2020 19:54:47 -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 04D373A093C; Sun, 24 May 2020 19:54:47 -0700 (PDT)
Received: from lhreml719-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E67C96BE05F69C154F52; Mon, 25 May 2020 03:54:42 +0100 (IST)
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by lhreml719-chm.china.huawei.com (10.201.108.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Mon, 25 May 2020 03:54:42 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme752-chm.china.huawei.com (10.3.19.98) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Mon, 25 May 2020 10:54:40 +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; Mon, 25 May 2020 10:54:40 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>, qinfengwei <qinfengwei@chinamobile.com>, '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: [spring] 答复: Progressing draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource management
Thread-Index: AQHWLxwZUkwzaMUzqEiqJoCp4LvkAqiyQIrA///NnYCABfzdoA==
Date: Mon, 25 May 2020 02:54:39 +0000
Message-ID: <bfab248f87fa4da38a66525e3c71ba45@huawei.com>
References: <6c9e9271a5e64e2faa2f373d871abaa1@huawei.com> <032901d62f1a$1f88c300$5e9a4900$@com> <170e5214-69ff-6d59-afdb-ee18c2a9483f@joelhalpern.com> <faae33acd85c4426acd5a374d40946c7@huawei.com> <9d4042b5-d226-77b7-7225-b510e28ca1b2@joelhalpern.com>
In-Reply-To: <9d4042b5-d226-77b7-7225-b510e28ca1b2@joelhalpern.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="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/XNGrJEvtQEzWMlraKPxyFmy0pjE>
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: Mon, 25 May 2020 02:54:50 -0000

Hi Joel,

Could you provide some reference in IETF to the "existing ways to do resource reservation with SR" you mentioned?

Regarding the term isolation, my suggestion is to keep that generic discussion in TEAS. In the context of this draft, as described in the draft and mails, the meaning is "allocating dedicated network resources", i.e. resource isolation,  the description could be clarified further.

Best regards,
Jie

> -----Original Message-----
> From: Joel Halpern Direct [mailto:jmh.direct@joelhalpern.com]
> Sent: Thursday, May 21, 2020 10:08 PM
> To: Dongjie (Jimmy) <jie.dong@huawei.com>; qinfengwei
> <qinfengwei@chinamobile.com>; 'SPRING WG' <spring@ietf.org>
> Cc: draft-dong-spring-sr-for-enhanced-vpn@ietf.org
> Subject: Re: [spring] 答复: Progressing
> draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource
> management
> 
> Part of my concern is that the document claims that this technique is
> necessary to use resource reservation with segment routing.  Given that we
> know there are existing ways people do use resource reservation with SR, it is
> not necessary.
> 
> The term "isolation" has been extensively debated in the traffic engineering
> working group, and the proponents have not been able to make a clear case
> for it.
> 
> Yours,
> Joel
> 
> On 5/21/2020 9:07 AM, Dongjie (Jimmy) wrote:
> > Hi Joel,
> >
> > Thanks for your comment.
> >
> > In this document, isolation means resource isolation, more specifically, a
> set of dedicated network resources are allocated on a group of network
> nodes and links, and SR SIDs are used to represent the allocated network
> resources. As mentioned by Aijun, this is described in section 5, it could be
> clarified earlier in the draft if needed.
> >
> > As for your statement regarding diffserv, I agree it has been widely used in
> network thanks to its simplicity and scalability. Whether it can address all
> services needs may be questionable. In IETF there have been many efforts to
> meet specific service requirements by reserving network resources, such as
> RSVP-TE, Detnet, etc. This draft aims to enhance SR with such capability.
> >
> > Best regards,
> > Jie
> >
> >> -----Original Message-----
> >> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> >> Sent: Thursday, May 21, 2020 11:01 AM
> >> To: qinfengwei <qinfengwei@chinamobile.com>; Dongjie (Jimmy)
> >> <jie.dong@huawei.com>; 'SPRING WG' <spring@ietf.org>
> >> Cc: draft-dong-spring-sr-for-enhanced-vpn@ietf.org
> >> Subject: Re: [spring] 答复: Progressing
> >> draft-dong-spring-sr-for-enhanced-vpn to enable SR with resource
> >> management
> >>
> >> This email (and the underlying document) asserts a need for "isolation"
> >> without defining isolation, and without recognizing that the service
> >> needs can be met by existing packet technologies.
> >>
> >> The document also asserts that resource management requires packet
> >> based resource reservation.  We have significant evidence that
> >> diffserv treatment coupled with central (PCE or equivalent) resource
> >> management can address these needs.
> >>
> >> At the very least, the discussion of isolation should be removed from
> >> the document before it is evaluated for adoption.
> >>
> >> Yours,
> >> Joel
> >>
> >> On 5/20/2020 10:47 PM, qinfengwei wrote:
> >>> Hi all,
> >>>
> >>> At present, 5G applications have been widely developed, recently,
> >>> many enterprises require dedicated network resources to achieve
> >>> isolation from other services in the network, such as southern power
> >>> grid, Migu live video and Tencent cloud games. This document
> >>> provides the mechanism to enhance SR with resource identification
> >>> capability. This is an important feature to meet different
> >>> customer’s requirement in our network. Thus we believe it is a
> >>> generic and useful enhancement to SR, and hope it could move forward
> quickly in the WG.
> >>>
> >>> Thanks,
> >>>
> >>> Fengwei Qin
> >>>
> >>> *发件人:*spring [mailto:spring-bounces@ietf.org] *代表 *Dongjie
> >> (Jimmy)
> >>> *发送时间:*2020年5月19日18:38
> >>> *收件人:*SPRING WG
> >>> *抄送:*draft-dong-spring-sr-for-enhanced-vpn@ietf.org
> >>> *主题:*[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
> >>>
> >>>
> >>> _______________________________________________
> >>> spring mailing list
> >>> spring@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/spring
> >>>