Re: [Teas] Status update on draft-ietf-teas-enhanced-vpn-06

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 16 July 2020 12:08 UTC

Return-Path: <jie.dong@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 223B73A0403 for <teas@ietfa.amsl.com>; Thu, 16 Jul 2020 05:08:08 -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 F--FelezBn3z for <teas@ietfa.amsl.com>; Thu, 16 Jul 2020 05:08:06 -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 E7E683A03FC for <teas@ietf.org>; Thu, 16 Jul 2020 05:08:05 -0700 (PDT)
Received: from lhreml703-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 952C98CE04884FF02DED for <teas@ietf.org>; Thu, 16 Jul 2020 13:08:04 +0100 (IST)
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Thu, 16 Jul 2020 13:08:03 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme754-chm.china.huawei.com (10.3.19.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Thu, 16 Jul 2020 20:08:01 +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; Thu, 16 Jul 2020 20:08:01 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] Status update on draft-ietf-teas-enhanced-vpn-06
Thread-Index: AdZadtvikrS8yOwKQeqggsN0MRr5ewAC1APQAAH8IBD//7mTgP/9/NNA
Date: Thu, 16 Jul 2020 12:08:01 +0000
Message-ID: <b567c92f68894fbc95312dad97caf08e@huawei.com>
References: <74e7986f78bb4206879ced1de96462d3@huawei.com> <HE1PR07MB4156E5DE6AA4BC27A2955AE9F07E0@HE1PR07MB4156.eurprd07.prod.outlook.com> <3956b4f7b14143bd82aa049b028694c0@huawei.com> <c659deff-6cc9-d268-0b59-084343c323f6@joelhalpern.com>
In-Reply-To: <c659deff-6cc9-d268-0b59-084343c323f6@joelhalpern.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.191.175]
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/teas/5hJ0WA6HW2piTvgpyYt7NmXs12U>
Subject: Re: [Teas] Status update on draft-ietf-teas-enhanced-vpn-06
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2020 12:08:08 -0000

Hi Joel, 

Thanks for your comment. 

Actually the word "such" in that sentence refers to a set of candidate technologies in the underlay, TSN and FlexE are just two examples. We could rephrase that sentence to make it clear. How about: 

"The usage of such type of underlying technologies... "?

Best regards,
Jie

> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Wednesday, July 15, 2020 9:15 PM
> To: Dongjie (Jimmy) <jie.dong@huawei.com>om>; teas@ietf.org
> Subject: Re: [Teas] Status update on draft-ietf-teas-enhanced-vpn-06
> 
> Given what you say, is the sentence needed?  It leads the reader to think
> these two things are more important.  (I am not objecting to the discussion
> under L2 technologies, just to this one sentence earlier.)
> 
> Yours,
> Joel
> 
> On 7/15/2020 5:32 AM, Dongjie (Jimmy) wrote:
> > Hi Daniele,
> >
> > Thanks for your comment. Please see my reply inline:
> >
> >> -----Original Message-----
> >> From: Daniele Ceccarelli [mailto:daniele.ceccarelli@ericsson.com]
> >> Sent: Wednesday, July 15, 2020 4:33 PM
> >> To: Dongjie (Jimmy) <jie.dong@huawei.com>om>; teas@ietf.org
> >> Subject: RE: Status update on draft-ietf-teas-enhanced-vpn-06
> >>
> >> Hi Jie,
> >>
> >> Just a minor clarification. In section 3.2 there is a statement saying:
> >>
> >> "The usage of such  (referring to TSN and FlexE) underlying
> >> technologies for
> >> VPN+ service needs to be considered."
> >>
> >> This is not mandating the usage of TNS and FlexE as underlaying
> >> technologies right?
> >
> > No, they are just listed as candidate technologies which may help to provide
> the required performance.
> >
> > Best regards,
> > Jie
> >
> >>
> >> Thanks
> >> Daniele
> >>
> >>
> >> -----Original Message-----
> >> From: Teas <teas-bounces@ietf.org> On Behalf Of Dongjie (Jimmy)
> >> Sent: den 15 juli 2020 09:10
> >> To: teas@ietf.org
> >> Subject: [Teas] Status update on draft-ietf-teas-enhanced-vpn-06
> >>
> >> Hi all,
> >>
> >> We've uploaded a new revision of draft-ietf-teas-enhanced-vpn-06. The
> >> changes in this version are:
> >>
> >> 1. Some further clarification about the terms used in this document.
> >>
> >> 2. In section 4.1, the architecture figure is updated to better
> >> reflect the relationship between overlay VPN service and underlay VTN.
> >>
> >> 3. In section 5.4, some further descriptions about SR control plane are
> added.
> >>
> >> 4. In section 5.6, text about the applicability of service data
> >> models is simplified, as the details will be covered in NS-DT,
> >> draft-wd-teas-transport-slice-yang,
> >> draft-king-teas-applicability-actn-slicing,
> >> etc.
> >>
> >> 5. Some editorial changes.
> >>
> >> As always, review comments and feedbacks are appreciated.
> >>
> >> Best regards,
> >> Jie
> >>
> >>> -----Original Message-----
> >>> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of
> >>> internet-drafts@ietf.org
> >>> Sent: Monday, July 13, 2020 4:47 PM
> >>> To: i-d-announce@ietf.org
> >>> Cc: teas@ietf.org
> >>> Subject: [Teas] I-D Action: draft-ietf-teas-enhanced-vpn-06.txt
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >>> This draft is a work item of the Traffic Engineering Architecture
> >>> and Signaling WG of the IETF.
> >>>
> >>>          Title           : A Framework for Enhanced Virtual Private
> >>> Networks (VPN+) Service
> >>>          Authors         : Jie Dong
> >>>                            Stewart Bryant
> >>>                            Zhenqiang Li
> >>>                            Takuya Miyasaka
> >>>                            Young Lee
> >>> 	Filename        : draft-ietf-teas-enhanced-vpn-06.txt
> >>> 	Pages           : 35
> >>> 	Date            : 2020-07-13
> >>>
> >>> Abstract:
> >>>     This document describes the framework for Enhanced Virtual Private
> >>>     Network (VPN+) service.  The purpose is to support the needs of
> new
> >>>     applications, particularly applications that are associated with 5G
> >>>     services, by utilizing an approach that is based on existing VPN and
> >>>     Traffic Engineering (TE) technologies and adds features that specific
> >>>     services require over and above traditional VPNs.
> >>>
> >>>     Typically, VPN+ will be used to form the underpinning of network
> >>>     slicing, but could also be of use in its own right providing enhanced
> >>>     connectivity services between customer sites.
> >>>
> >>>     It is envisaged that enhanced VPNs will be delivered using a
> >>>     combination of existing, modified, and new networking technologies.
> >>>     This document provides an overview of relevant technologies and
> >>>     identifies some areas for potential new work.
> >>>
> >>>     Comparing to traditional VPNs, It is not envisaged that quite large
> >>>     numbers of VPN+ services will be deployed in a network.  In other
> >>>     word, it is not intended that all existing VPNs supported by a
> >>>     network will use VPN+ related techniques.
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>> https://datatracker.ietf.org/doc/draft-ietf-teas-enhanced-vpn/
> >>>
> >>> There are also htmlized versions available at:
> >>> https://tools.ietf.org/html/draft-ietf-teas-enhanced-vpn-06
> >>> https://datatracker.ietf.org/doc/html/draft-ietf-teas-enhanced-vpn-0
> >>> 6
> >>>
> >>> A diff from the previous version is available at:
> >>> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-enhanced-vpn-06
> >>>
> >>>
> >>> 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.
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>>
> >>> _______________________________________________
> >>> Teas mailing list
> >>> Teas@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/teas
> >>
> >> _______________________________________________
> >> Teas mailing list
> >> Teas@ietf.org
> >> https://www.ietf.org/mailman/listinfo/teas
> >
> > _______________________________________________
> > Teas mailing list
> > Teas@ietf.org
> > https://www.ietf.org/mailman/listinfo/teas
> >