Re: [Teas] terminology discussion network slicing
Leeyoung <leeyoung@huawei.com> Mon, 15 May 2017 22:02 UTC
Return-Path: <leeyoung@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 0C4E612943B for <teas@ietfa.amsl.com>; Mon, 15 May 2017 15:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 GtG9woctx-SG for <teas@ietfa.amsl.com>; Mon, 15 May 2017 15:02:13 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAA39129329 for <teas@ietf.org>; Mon, 15 May 2017 14:59:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DMZ43710; Mon, 15 May 2017 21:59:03 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 15 May 2017 22:59:02 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.117]) by SJCEML703-CHM.china.huawei.com ([169.254.5.229]) with mapi id 14.03.0235.001; Mon, 15 May 2017 14:58:54 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Igor Bryskin <Igor.Bryskin@huawei.com>, "teas@ietf.org" <teas@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: [Teas] terminology discussion network slicing
Thread-Index: AQHSzY7/1JWHEI0p7UixIBEphRDKtqH1hiPAgACK+oD//94M4A==
Date: Mon, 15 May 2017 21:58:54 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E172B2CA79D@SJCEML702-CHM.china.huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E172B2CA60E@SJCEML702-CHM.china.huawei.com> <0C72C38E7EBC34499E8A9E7DD00786390993A19A@SJCEML702-CHM.china.huawei.com> <7AEB3D6833318045B4AE71C2C87E8E172B2CA69F@SJCEML702-CHM.china.huawei.com> <0C72C38E7EBC34499E8A9E7DD00786390993A20C@SJCEML702-CHM.china.huawei.com>
In-Reply-To: <0C72C38E7EBC34499E8A9E7DD00786390993A20C@SJCEML702-CHM.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.146.202]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.591A24A7.00D0, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.117, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 1ed5454d87f42c48cf97f9697837e7a6
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/9XBUOKPBjzJKoAdCPmsrQgeJoW0>
Subject: Re: [Teas] terminology discussion network slicing
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
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, 15 May 2017 22:02:17 -0000
Hi Igor, I think I share with your view. Please see inline for my comment. Thanks. Young -----Original Message----- From: Igor Bryskin Sent: Monday, May 15, 2017 11:51 AM To: Leeyoung <leeyoung@huawei.com>; teas@ietf.org; adrian@olddog.co.uk Subject: RE: [Teas] terminology discussion network slicing Young, If two VPNs use separate IP/MPLS TE tunnels, one misbehaved VPN can still affect the other (in either control or data planes). This is not good enough fot 5g. YOUNG>> I agree. If the two VPNs use separate wires/lease lines connecting PEs of the two VPNs, they would become PNs, rather than VPNs (in Soviet Union we used to say that if my grandmother would have one thing she would be my grandfather, not grandmother :=). YOUNG>> Yes. I see your point. In 5G c0ntext we need separation of PNs and manageability of VPNs, which could be achieved with network slices - we replace wires/lease lines of PNs with L0/L1 TE tunnels provided by possibly common transport network. YOUNG>> I did not mean VPN to be always shared. If you make some analogy with VTNS (Virtual Transport Network Service, defined by OIF), VTNS does not necessarily allow resources allocated among the customers to be shared as VTNS is defined in L1/L0 environment; however, it uses "virtual" in its term. So I think when we say "virtual network service" we need to make this point clear - we don't necessarily assume it is shared with many customer instances. That is why "isolation" requirement needs to be attached when a VN MUST be isolated physically from other VNs. Of course, some other VNs, this can be relaxed depending on the customer applications. Igoe -----Original Message----- From: Leeyoung Sent: Monday, May 15, 2017 11:50 AM To: Igor Bryskin; teas@ietf.org; adrian@olddog.co.uk Subject: RE: [Teas] terminology discussion network slicing Hi Igor, We don't actually assume that a virtual network given to the customer is always shared resources with other virtual networks. We have specific customer requirement on VN sharing/isolation. Some customers will require a strict isolation of their virtual network from other virtual networks while others would not require such restriction/isolation requirement. I think that is what you have in mind. Thanks. Young -----Original Message----- From: Igor Bryskin Sent: Monday, May 15, 2017 10:22 AM To: Leeyoung <leeyoung@huawei.com>; teas@ietf.org; adrian@olddog.co.uk Subject: RE: [Teas] terminology discussion network slicing Hi Young, The word "virtual" in virtual networks implies a common infrastructure shared by said networks. For example, traditional L3 VPNs share or may share IP/MPLS TE tunnels inter-connecting the VPNs PEs, that's why they are "virtual" private networks (just appear private to the clients, but in fact, they are not). IMHO IP/MPLS slices are genuinely private IP/MPLS networks, because in the IP/MPLS layer they are completely isolated (in both control and data planes). They may share underlying transport layer(s), but they do not share their own layer infrastructure. So, I would define layer network slices as dynamically managed fully isolated in control and data planes private TE layer networks, which may share one or more underlying server layer networks, i.e. I suggest taking the word "virtual" out of the definition. Cheers, Igor -----Original Message----- From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of Leeyoung Sent: Monday, May 15, 2017 10:45 AM To: teas@ietf.org; adrian@olddog.co.uk Subject: [Teas] terminology discussion network slicing Hi Adrian and others, We'd like cross check with you on some terminology we introduced newly. Any comment on these terms will be greatly appreciated. We introduced 'network slicing' as follows: Network slicing is a collection of resources that are used to establish logically dedicated virtual networks over TE networks. It allows a network provider to provide dedicated virtual networks for application/customer over a common network infrastructure. The logically dedicated resources are a part of the larger common network infrastructures that are shared among various network slice instances which are the end-to-end realization of network slicing, consisting of the combination of physically or logically dedicated resources. Thanks. Young and Daniele -----Original Message----- From: Leeyoung Sent: Friday, May 05, 2017 1:41 PM To: teas@ietf.org Subject: RE: [Teas] I-D Action: draft-ietf-teas-actn-framework-05.txt Hi, This update is intended to incorporate the comments from the last WG meeting and any pending issues. We also have taken the global editorial changes to make it consistent through the document. Major changes are: - Inclusion of "network slicing" definition from ACTN perspective (in the terminology section) - Added virtual network service (VNS) section (Section 3) to define types of VNS. - Incorporated "orchestration" (service/network) mapping to ACTN architecture (See Section 5.2) - Created a new section 6 (Topology Abstraction Method) where we imported some texts from ACTN abstraction method https://tools.ietf.org/html/draft-lee-teas-actn-abstraction-01 - Added Appendices A & B to discuss example deployment scenarios such as example of MDSC and PNC functions integrated in Service/Network Orchestrator (Appendix A) and example of IP + Optical network with L3VPN service (Appendix B) In regard to ACTN abstraction method draft, we are going to keep it as a separate draft and use this document to elaborate other aspects not imported to the framework document. The following diff pointer will help you see the changes with this revision: https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-actn-framework-05 The co-authors believe that the document is ready for WG LC. Any changes/comments will be appreciated. Thanks & Best regards, Young & Daniele (on behalf of other co-authors/contributors) -----Original Message----- From: Teas [mailto:teas-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Friday, May 05, 2017 10:41 AM To: i-d-announce@ietf.org Cc: teas@ietf.org Subject: [Teas] I-D Action: draft-ietf-teas-actn-framework-05.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 of the IETF. Title : Framework for Abstraction and Control of Traffic Engineered Networks Authors : Daniele Ceccarelli Young Lee Filename : draft-ietf-teas-actn-framework-05.txt Pages : 41 Date : 2017-05-05 Abstract: Traffic Engineered networks have a variety of mechanisms to facilitate the separation of the data plane and control plane. They also have a range of management and provisioning protocols to configure and activate network resources. These mechanisms represent key technologies for enabling flexible and dynamic networking. Abstraction of network resources is a technique that can be applied to a single network domain or across multiple domains to create a single virtualized network that is under the control of a network operator or the customer of the operator that actually owns the network resources. This document provides a framework for Abstraction and Control of Traffic Engineered Networks (ACTN). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-teas-actn-framework/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-teas-actn-framework-05 https://datatracker.ietf.org/doc/html/draft-ietf-teas-actn-framework-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-actn-framework-05 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] terminology discussion network slicing Leeyoung
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] terminology discussion network slicing Ricard Vilalta
- Re: [Teas] terminology discussion network slicing Leeyoung
- Re: [Teas] terminology discussion network slicing Leeyoung
- Re: [Teas] terminology discussion network slicing Adrian Farrel
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] terminology discussion network slicing Gert Grammel
- Re: [Teas] terminology discussion network slicing Leeyoung
- Re: [Teas] terminology discussion network slicing Leeyoung
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] terminology discussion network slicing Belotti, Sergio (Nokia - IT/Vimercate)
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] terminology discussion network slicing Lou Berger
- Re: [Teas] terminology discussion network slicing Leeyoung
- Re: [Teas] terminology discussion network slicing Kiran.Makhijani
- Re: [Teas] terminology discussion network slicing Leeyoung
- Re: [Teas] [Netslices] terminology discussion net… Adrian Farrel
- Re: [Teas] terminology discussion network slicing Daniele Ceccarelli
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] [Netslices] terminology discussion net… Spencer Dawkins at IETF
- Re: [Teas] [Netslices] terminology discussion net… Greg Mirsky
- Re: [Teas] [Netslices] terminology discussion net… Jeff Tantsura
- [Teas] 答复: terminology discussion network slicing qiangli (D)
- [Teas] 答复: terminology discussion network slicing qiangli (D)
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] 答复: terminology discussion network sli… Daniele Ceccarelli
- Re: [Teas] terminology discussion network slicing Daniele Ceccarelli
- [Teas] 答复: terminology discussion network slicing qiangli (D)
- [Teas] 答复: terminology discussion network slicing qiangli (D)
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] terminology discussion network slicing Jeff Tantsura
- Re: [Teas] [Netslices] terminology discussion net… Greg Mirsky
- Re: [Teas] terminology discussion network slicing Igor Bryskin
- Re: [Teas] terminology discussion network slicing Dongjie (Jimmy)
- Re: [Teas] [Netslices] terminology discussion net… sebastian
- Re: [Teas] [Netslices] terminology discussion net… sebastian
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] terminology discussion network slicing Daniele Ceccarelli
- Re: [Teas] [Netslices] terminology discussion net… Gert Grammel
- Re: [Teas] [Netslices] terminology discussion net… sebastian
- Re: [Teas] [Netslices] terminology discussion net… Flinck, Hannu (Nokia - FI/Espoo)
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] [Netslices] terminology discussion net… Daniele Ceccarelli
- Re: [Teas] [Netslices] terminology discussion net… Gert Grammel
- Re: [Teas] [Netslices] terminology discussion net… sebastian