Re: [Teas] Status update on draft-ietf-teas-enhanced-vpn-06
Joel Halpern Direct <jmh.direct@joelhalpern.com> Thu, 16 July 2020 13:53 UTC
Return-Path: <jmh.direct@joelhalpern.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 4C16C3A0819 for <teas@ietfa.amsl.com>; Thu, 16 Jul 2020 06:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 yzGZOo47FwAw for <teas@ietfa.amsl.com>; Thu, 16 Jul 2020 06:53:28 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 02FF83A0812 for <teas@ietf.org>; Thu, 16 Jul 2020 06:53:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4B6wh75dTkz1p5w0; Thu, 16 Jul 2020 06:53:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1594907607; bh=TU1+LuVWsofmOdSb/Wja4KU7lEzm2RJrqD7TCaSUYYU=; h=Subject:To:References:From:Date:In-Reply-To:From; b=OT7B1t0/0LwKMHoDIYkxwYiYZUMlv3uiw5vB1md56ftWnbpHySfvNEAsxnPdz4h0j o+cWxGhnn8+yosBOMyNfEmE0Hgc2VC42XaM5CAc6A9okob0mU84HK9LcjXbAIJ0vY2 Rh+jEbGyiNg1cZDNFh+j04I+Jf8npHAuxzriC5i4=
X-Quarantine-ID: <kcrv-kKtryJu>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4B6wh62Xkzz1p5vm; Thu, 16 Jul 2020 06:53:26 -0700 (PDT)
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "teas@ietf.org" <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>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <ebacb358-98c0-cf71-a4ff-2985f6a7ddab@joelhalpern.com>
Date: Thu, 16 Jul 2020 09:53:24 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <b567c92f68894fbc95312dad97caf08e@huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/GYo-9EVLEbvLyXMCPpz6Bk_BWc0>
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 13:53:30 -0000
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>; 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>; 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] Status update on draft-ietf-teas-enhanced-… Dongjie (Jimmy)
- Re: [Teas] Status update on draft-ietf-teas-enhan… Daniele Ceccarelli
- Re: [Teas] Status update on draft-ietf-teas-enhan… Dongjie (Jimmy)
- Re: [Teas] Status update on draft-ietf-teas-enhan… Joel M. Halpern
- Re: [Teas] Status update on draft-ietf-teas-enhan… Dongjie (Jimmy)
- Re: [Teas] Status update on draft-ietf-teas-enhan… Joel Halpern Direct
- Re: [Teas] Status update on draft-ietf-teas-enhan… Adrian Farrel
- Re: [Teas] Status update on draft-ietf-teas-enhan… Dongjie (Jimmy)