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

Adrian Farrel <adrian@olddog.co.uk> Mon, 20 July 2020 12:35 UTC

Return-Path: <adrian@olddog.co.uk>
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 890593A08D4 for <teas@ietfa.amsl.com>; Mon, 20 Jul 2020 05:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 9xk28qOvq1hg for <teas@ietfa.amsl.com>; Mon, 20 Jul 2020 05:35:35 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 161F63A08CD for <teas@ietf.org>; Mon, 20 Jul 2020 05:35:34 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id 06KCZO3M020547; Mon, 20 Jul 2020 13:35:24 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BAD6722042; Mon, 20 Jul 2020 13:35:23 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS id A520922048; Mon, 20 Jul 2020 13:35:23 +0100 (BST)
Received: from LAPTOPK7AS653V (91-115-218-159.adsl.highway.telekom.at [91.115.218.159]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 06KCZMFP016722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 Jul 2020 13:35:23 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joel Halpern Direct'" <jmh.direct@joelhalpern.com>, "'Dongjie \(Jimmy\)'" <jie.dong@huawei.com>, <teas@ietf.org>
References: <74e7986f78bb4206879ced1de96462d3@huawei.com> <HE1PR07MB4156E5DE6AA4BC27A2955AE9F07E0@HE1PR07MB4156.eurprd07.prod.outlook.com> <3956b4f7b14143bd82aa049b028694c0@huawei.com> <c659deff-6cc9-d268-0b59-084343c323f6@joelhalpern.com> <b567c92f68894fbc95312dad97caf08e@huawei.com> <ebacb358-98c0-cf71-a4ff-2985f6a7ddab@joelhalpern.com>
In-Reply-To: <ebacb358-98c0-cf71-a4ff-2985f6a7ddab@joelhalpern.com>
Date: Mon, 20 Jul 2020 13:35:22 +0100
Organization: Old Dog Consulting
Message-ID: <00d201d65e92$3d043390$b70c9ab0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQEbW+pYXuNivHSCtkdS/coAyBVmBQHpixw0Ak9k3mAB80U5xgGeMrrxAahuL+SqOtPYAA==
X-Originating-IP: 91.115.218.159
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25552.007
X-TM-AS-Result: No--24.768-10.0-31-10
X-imss-scan-details: No--24.768-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25552.007
X-TMASE-Result: 10--24.768500-10.000000
X-TMASE-MatchedRID: CxmI61mtwh9Rn39sim9+cHFPUrVDm6jtbfVFVoam0SGvloAnGr4qhpLK CWAH8hIa3kxz5ggq43O5m3PB0PUVjojGpFth79Wj+LORUvwlJdsZskwWqoib3Av1OPvvDLzsV0o zYx6Zbm88XbOBuzkIBm2iS34pw25fpEOHRag0ivXrOLyP6vXu3T8HEU7XbMTEDryaTJpWYKqPd1 lLIAtF4v8nv9x3PStaYsBzwcNv7+ovKbWkeTMxciwgwmow2VqdBGwExtNOAA9GM2uNXRqsUklwF e8piRSDexmaZiEJOfLYphbowOaeA6UVO4N7kQfvHch4gZ8olb86En2bnefhoIvFa5XXUMbGjQb0 ZijHcXATTFH0MvwtNaO1fyMo6shC8nnaWPcgDKl8wyiMzq18XlsP0tBwe3qDIlxOowKJvsVI6ii a8EJZLt/nCerSk1DVYTBMuNDTe0dZZoI4ZnCT3TPF07YFM7bTeY9ksPjb7GsUFDkgqWz8DpyUIu m5afhXCeoZGbvEV0sakf/lOKstpZmWQNbliZ0+Th4VSQfkIVyhp756/rM6UlR9dVhdZqn7lkraX 7MOLfb3OF0UjQGrupnd5GvZSlDO4vHanut+JPr8OMEMU7OyZqtcc+AMge0tRqYP52QLif1t+ecV +4jFe59NxqRbsrdJpt3L5VFqVtvF2WYblKxSjMmR5yDJkPg4TLZB6U/YaPoOOOIzzESoE2QdqSH 25CWMCAwTmLDKzqNxLpiUSz2WjAJJvCplxAPmdPuue3cRiRh4Xox68xVlQIblMMKBhOiU2mKpI8 uzzwCWuDQn8z1dtJPfrA/DvkZBwit0Z/2kiE2eAiCmPx4NwLTrdaH1ZWqCpvI8UZOf47gc4WL5J jd88P306Q4zhC4D3QfwsVk0UbslCGssfkpInQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/83if9mIM57AwbUGYY3AB9OVQBIM>
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: Mon, 20 Jul 2020 12:35:38 -0000

Well, are we really trying to say...

"The usage of underlying L2 technologies (such as TSN and FlexE) for VPN+
services needs to be considered"

?

Adrian
-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of Joel Halpern Direct
Sent: 16 July 2020 14:53
To: Dongjie (Jimmy) <jie.dong@huawei.com>om>; teas@ietf.org
Subject: Re: [Teas] Status update on draft-ietf-teas-enhanced-vpn-06

That proposed sentence would be better.  Still, I do not see that the 
sentence adds much value.  While I can live with the replacement, I 
think we would be better off simply removing the sentence.

Yours,
Joel

On 7/16/2020 8:08 AM, Dongjie (Jimmy) wrote:
> 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
>>>

_______________________________________________
Teas mailing list
Teas@ietf.org
https://www.ietf.org/mailman/listinfo/teas