Re: [Teas] terminology discussion network slicing
Gert Grammel <ggrammel@juniper.net> Mon, 15 May 2017 17:05 UTC
Return-Path: <ggrammel@juniper.net>
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 A013E129432 for <teas@ietfa.amsl.com>; Mon, 15 May 2017 10:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.022
X-Spam-Level:
X-Spam-Status: No, score=-2.022 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 9JWHvI6d3HZZ for <teas@ietfa.amsl.com>; Mon, 15 May 2017 10:05:00 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0100.outbound.protection.outlook.com [104.47.40.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA15212944A for <teas@ietf.org>; Mon, 15 May 2017 10:01:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=UD/s8l1I8ic9u2NNgf4TQkDIVYCML4A/k1Z7vuCF3NA=; b=a+mrrznay7XeCtoO4cHPDJFjZ3To3w76hglzvsEAW4UNMP7a387SJBI3r1rrbZ/LvZSkJ2sVeablZSLzj/jrwMVzmPN2ua1PA7J1/podfTUdSAho/mv6jE56XhawRmO+wWIwegqyeSg1NgQ8GbSkZI2P0iSQATNjnZa815qK5nY=
Received: from CY1PR0501MB1609.namprd05.prod.outlook.com (10.161.162.13) by CY1PR0501MB1611.namprd05.prod.outlook.com (10.161.162.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.7; Mon, 15 May 2017 17:01:50 +0000
Received: from CY1PR0501MB1609.namprd05.prod.outlook.com ([10.161.162.13]) by CY1PR0501MB1609.namprd05.prod.outlook.com ([10.161.162.13]) with mapi id 15.01.1084.029; Mon, 15 May 2017 17:01:50 +0000
From: Gert Grammel <ggrammel@juniper.net>
To: Leeyoung <leeyoung@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: AdLNibwU9LLkPQ+KR4i49jploFvNwAAI/kYA
Date: Mon, 15 May 2017 17:01:50 +0000
Message-ID: <97EE7243-CB44-40AD-B02D-98E07D9C79F2@juniper.net>
References: <7AEB3D6833318045B4AE71C2C87E8E172B2CA60E@SJCEML702-CHM.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E172B2CA60E@SJCEML702-CHM.china.huawei.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.21.0.170409
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [193.110.55.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR0501MB1611; 7:fB09WrJqNyfEDcnDP8oHIPDA643OeRSRgzR8oQaBSEJ+bDxmYo5RFiqcvk430d/H5GJuldnkV6JxCQo88Zoabu3HCdElQ+XBCVHmXRDXK0qacs4Ducbe9CrVkmuuJIp18erClNQ/WkwiW7+RoHDJ+ta6cn0q+kWF75Pa7WTLrcwki3af11zhHKmVdAGo+3gSOCsn9nEc9FQqyGG9BhzPeLote8sOKRVdpqActY1Zzew4BYqg9X0SYE1Zzk/0Ae+kmPt2w51DW51AiU4mUuIkgIQH40K4/A3rg4uFThG9ha0ESQjM10It3i3DbpSPpl60k7WVMdIe92ykl2ZvmI3Hpg==
x-ms-office365-filtering-correlation-id: 7429f29a-944b-4e45-22b0-08d49bb41476
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:CY1PR0501MB1611;
x-microsoft-antispam-prvs: <CY1PR0501MB1611DD4D5332F118989297AACEE10@CY1PR0501MB1611.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(20161123560025)(20161123555025)(20161123558100)(6072148); SRVR:CY1PR0501MB1611; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0501MB1611;
x-forefront-prvs: 0308EE423E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39860400002)(39840400002)(39850400002)(39450400003)(24454002)(377454003)(13464003)(377424004)(25786009)(53546009)(122556002)(2906002)(2950100002)(6486002)(229853002)(77096006)(345774005)(54356999)(76176999)(50986999)(5660300001)(33656002)(2501003)(3660700001)(7736002)(305945005)(3280700002)(82746002)(81166006)(8676002)(8936002)(478600001)(6506006)(38730400002)(86362001)(83716003)(83506001)(36756003)(3846002)(102836003)(189998001)(6116002)(2201001)(66066001)(4001350100001)(2900100001)(6436002)(99286003)(6306002)(6512007)(6246003)(53936002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0501MB1611; H:CY1PR0501MB1609.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <4322CA07FF380242936696B49170639A@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 May 2017 17:01:50.5137 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0501MB1611
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/izehppOVdeFIBw6w3ZObwxETY7s>
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 17:05:03 -0000
Leeyoung, Thank you for taking a stab on this. Usually when getting to a definition, I try to establish what kind of existing constructs would fall under the definition. If my understanding is correct, the following list of constructs would all satisfy the definition somehow. - A TDM network with a p2p TDM connection - A PSC capable network carrying a p2p circuit (such as EPL/EVPL) - An MPLS LSP using a traffic engineered IP network - A L2VPN using a traffic engineered MPLS network - A L3VPN using a traffic engineered IP network - A TCP connection using a traffic engineered IP network - Different QoS classes in an IP network Thinking a bit about it I came to the point where "VPN" and "network slices" seem to describe the same entity or at least a "network slice" being a VPN of VPNs? Gert On 2017-05-17, 16:44, "Teas on behalf of Leeyoung" <teas-bounces@ietf.org on behalf of leeyoung@huawei.com> wrote: 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