Re: [Teas] Enhanced VPN discussions in various WGs

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 14 November 2019 02:07 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 553D31200E3; Wed, 13 Nov 2019 18:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 fDe4tL2GR0kK; Wed, 13 Nov 2019 18:07:04 -0800 (PST)
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 7EA3B120044; Wed, 13 Nov 2019 18:07:04 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 452AA981481BC00EDB72; Thu, 14 Nov 2019 02:07:02 +0000 (GMT)
Received: from lhreml726-chm.china.huawei.com (10.201.108.77) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 14 Nov 2019 02:07:01 +0000
Received: from lhreml726-chm.china.huawei.com (10.201.108.77) by lhreml726-chm.china.huawei.com (10.201.108.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 14 Nov 2019 02:07:01 +0000
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml726-chm.china.huawei.com (10.201.108.77) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 14 Nov 2019 02:07:01 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0439.000; Thu, 14 Nov 2019 10:06:57 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: David Sinicrope <david.sinicrope=40ericsson.com@dmarc.ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "teas@ietf.org" <teas@ietf.org>
CC: "'ccamp@ietf. org'" <ccamp@ietf.org>
Thread-Topic: [Teas] Enhanced VPN discussions in various WGs
Thread-Index: AdWZ8fL6e34ke91DSr6B2EObbFdAKAAQQjEAABaA8sA=
Date: Thu, 14 Nov 2019 02:06:56 +0000
Message-ID: <76CD132C3ADEF848BD84D028D243C927CD38F869@NKGEML515-MBX.china.huawei.com>
References: <039b01d599f3$daffd680$90ff8380$@olddog.co.uk> <FCC23939-AA6C-46DF-B6AB-1E075E1D88A7@ericsson.com>
In-Reply-To: <FCC23939-AA6C-46DF-B6AB-1E075E1D88A7@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.53.134]
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/ry6p7LflytkwmnjOwz3fy8694-Y>
Subject: Re: [Teas] Enhanced VPN discussions in various WGs
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, 14 Nov 2019 02:07:07 -0000

Hi Dave,

Thanks for your comments. 

The VPN+ framework document describes the framework and candidate technologies in different network layers which can be used together to provide VPN+ service. FlexE is listed as one of the candidate technologies in underlay data plane. In VPN+ related drafts, there is no description about exposing detailed information of FlexE. On contrary, abstraction is used to represent different underlay technologies with a unified manner to the network. 

Hope this helps to solve your concerns.

Best regards,
Jie

> -----Original Message-----
> From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of David Sinicrope
> Sent: Wednesday, November 13, 2019 10:00 PM
> To: adrian@olddog.co.uk; teas@ietf.org
> Cc: 'ccamp@ietf. org' <ccamp@ietf.org>
> Subject: Re: [Teas] Enhanced VPN discussions in various WGs
> 
> Hi Adrian,
> Thanks for providing the cross reference, this is very useful.
> 
> How is the VPN+ work below related to GMPLS Routing and Signaling
> Framework for Flexible Ethernet (FlexE) draft-izh-ccamp-flexe-fwk-07?
> There are some serious concerns with the draft above and exposure of FlexE
> constructs that OIF FlexE notes should not be exposed.
> e.g., FlexE Group, FlexE Channel
> OIF FlexE indicates that it should present to the upper layer as Ethernet with no
> indication of FlexE in the dataplane i.e., it looks like any other Ethernet interface
> (with perhaps enhanced QoS capabilities.)
> 
> I see what looks to be exposure of similar FlexE constructs in the TEAS draft and
> other drafts. (e.g., FlexE Channels)
> 
> It would be good for these drafts to align with OIF specification of FlexE such
> that these constructs remain transparent and thereby ensuring they are
> leveraging what OIF specified and not variants.  i.e., present an Ethernet
> interface to the upper layer vs exposing FlexE constructs OIF says remain
> transparent. One exception to this would of course be the management and
> FlexE models which would be required to configure the FlexE links.  These of
> course should be liaised to OIF with an invite for that community to review and
> comment the work ongoing in IETF (CCAMP).
> 
> Thanks,
> Dave
> 
> 
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> on behalf of "Adrian uk>"
> <adrian@olddog.co.uk>
> Organization: Old Dog Consulting
> Reply-To: "Adrian uk>" <adrian@olddog.co.uk>
> Date: Wednesday, November 13, 2019 at 8:28 AM
> To: TEAS WG <teas@ietf.org>
> Subject: [Teas] Enhanced VPN discussions in various WGs
> 
>     Hi,
> 
>     TEAS is the home of draft-ietf-teas-enhanced-vpn, and that provides an
>     anchor for a lot of VPN+ work going on across the IETF in Singapore.
> 
>     It is worth a heads-up on this to help you track what is going on and pull
>     together the pieces in case you are interested in this approach to network
>     slicing. Apologies if I have missed anything.
> 
>     TEAS
>     - A Framework for Enhanced Virtual Private Networks (VPN+) Service
>        draft-ietf-teas-enhanced-vpn-01
>     - Control plane considerations of enhanced VPN
>        draft-dong-teas-enhanced-vpn-control-plane-00
> 
>     LSR
>     - IGP Extensions for Segment Routing Based Enhanced VPN
>       draft-dong-lsr-sr-enhanced-vpn
> 
>     BESS
>     - BGP-LS Filters: A Framework for Network Slicing and Enhanced VPNs
>       draft-drake-bess-enhanced-vpn
> 
>     SPRING
>     - Segment Routing for Enhanced VPN Service
>       draft-dong-spring-sr-for-enhanced-vpn
> 
>     I also note draft-dong-idr-bgpls-sr-enhanced-vpn, but don't see it on any
>     agendas this time around.
> 
>     Cheers,
>     Adrian
>     --
>     Bored with reading Interent-Drafts?
>     Read some fairy stories for adults of all ages instead.
>     .. Tales from the Wood
>     .. More Tales from the Wood
>     .. Tales from Beyond the Wood
>     .. Tales from the Castle
>     Get them on line
> https://protect2.fireeye.com/v1/url?k=2f623436-73e8fef5-2f6274ad-86e1ed
> 4002b1-2fe12d2ac4a7279e&q=1&e=5710c793-d87c-49fb-8382-20dfcc8c29b
> 5&u=https%3A%2F%2Fwww.feedaread.com%2Fprofiles%2F8604%2F
>     Or buy a signed copy from me by post
>     *** Stop me in the corridor at IETF-106 to get a copy ***
> 
> 
> 
>     _______________________________________________
>     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