Re: [Teas] [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt

Kaippallimalil John <> Wed, 10 July 2019 18:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 410D71202E5; Wed, 10 Jul 2019 11:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rxmAhbcY8Hce; Wed, 10 Jul 2019 11:59:44 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 8438E120727; Wed, 10 Jul 2019 11:59:43 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=KpGiwf/Acp6dRXID5fQqbV1Uus2fGCG7hFjGG+DWYk4+GdsxoGSyfAdxHjvSRPCDBGp58Ks5oXj+hRQmG2fjKAxHG6rQe9tDhgBVWqObjhg1jUXWLeemY084dhWgDgNUQqpmdpS9CSDWkZzgdNrhDSrcju8wG9kkVFqL/Z+fAoCxzf7F13FObNqLbjieS8BQl3JmC3HGb0fjJwViqloLY7v+kWqf+vb/nEOTJCulu2dzubs6CHmV+GpwLgDleZ64NhT1zU0GWxL5ghqyd4V99kBuW6+fO1qt2gq3Dg7l/QO2j0Ve/XQPrylgcXwizBtqVeKq3UJL1rCjIqZLKP8C6Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kuR6TV7HcOwB9C0pfx3CZXVJ4j5V6/RCPbUQXLgTNGs=; b=btoeuA1/0xUE8ff2xd55VgpwYcN8wB22g4hr2KY7o8BqeMCvW8MhpByhKrHS10BHFgtJgRPiImyhZge0pGrSjLI2YfEOtIzG/d//l3tFrUg3HWJfDVJEZSnKDf4wv/D+drGR95LrC50AftnooutE/kQslsP3nArCfqKnpO3os2JuyL5lgPGePQ0SecKxsFGQ7yHGyso5uzSnfRCpWc6NpxmRLBFhhZ4joinQNZfHH9tsc0EfhYGO10o7ZU/6ZZwg1ACffP6ko1L64LtC1tRv4f6j01c/ZBtROFDIlYy6B88fvPbaic7qxzvrth0TeJAxa2Je3TTaXJkP1jmj0SXiYw==
ARC-Authentication-Results: i=1; 1;spf=pass;dmarc=pass action=none;dkim=pass;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kuR6TV7HcOwB9C0pfx3CZXVJ4j5V6/RCPbUQXLgTNGs=; b=A8LtpgbxjjeorWYt/GbebutbByjQPzFy5g5pilwRQXFUoQkKt+QXhpf5j9Z4jyPs7D0psq6xdfWhuItIWq12BN6ZTkfH0iyRlEXbqhEdvdwc/tKdG7CbzzwPUVSQSN8VGO3PwV2M8LG9ysM5uPAJuJdoHSE2IchiTFGmyY5N+h0=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2073.10; Wed, 10 Jul 2019 18:59:40 +0000
Received: from ([fe80::2544:ac2c:c6bf:ef68]) by ([fe80::2544:ac2c:c6bf:ef68%7]) with mapi id 15.20.2073.008; Wed, 10 Jul 2019 18:59:40 +0000
From: Kaippallimalil John <>
To: "Rokui, Reza (Nokia - CA/Ottawa)" <>, Takuya Miyasaka <>, "" <>, "" <>, "" <>, "" <>, "" <>
Thread-Topic: [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt
Thread-Index: AQHVNYXoEFXra9LeKkybZd8yJs+1aabA6V8w
Date: Wed, 10 Jul 2019 18:59:39 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 60e1f7d8-eb09-4d3c-ab99-08d70568c2f8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3343;
x-ms-traffictypediagnostic: MN2PR13MB3343:
x-ms-exchange-purlcount: 9
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0094E3478A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39850400004)(396003)(136003)(346002)(366004)(376002)(189003)(199004)(53754006)(236005)(790700001)(6116002)(3846002)(8676002)(86362001)(66574012)(446003)(2201001)(53946003)(53936002)(54896002)(25786009)(55016002)(6306002)(66946007)(71190400001)(6246003)(81166006)(81156014)(33656002)(486006)(64756008)(66556008)(14454004)(68736007)(71200400001)(11346002)(66476007)(476003)(76116006)(66446008)(7696005)(5024004)(74316002)(229853002)(2420400007)(7110500001)(2906002)(15650500001)(66066001)(6506007)(52536014)(5660300002)(7736002)(478600001)(76176011)(99286004)(6436002)(53546011)(296002)(316002)(9686003)(606006)(102836004)(966005)(110136005)(2501003)(26005)(8936002)(186003)(14444005)(256004)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3343;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 8WnBPPkhGUfTlQKWmM3uMYh6SJud9kjH8HwIqFLSHGnMnZ29pkqIJTDQDnlHtjEggGLiFafTA5zY/crRNwVVIHxHDWCuR3iEmPy3blZPbJyzYLL+ErmJBmejSRi9On8kuifwjH5tYPpYq3NKTL26xG8b14vu+zLYr8dmdRnlsSjheAn+QVkLFDPtiKVL3FxNZrg1eEknc/60A4nUFlkfEWr4NCXPgjfQP3F2+05R6SC1SGQ5mINojwicGf6Y9jQTP8DymjaTaSOAGBpjpg2icCQKrOSy+YABzC6TPqYOm5V5rpPPe0lrtCl7EwnKb8/3yyBjZjqVihF1hYwsdVfWBlMryceLZNQj70j0PlflXxl3OPf/40lwUHFBkUBQim7bOSYgkzyaIsWjd0yfgp9dpGrmcAHLiiAgHRhpOXSQxHM=
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB33095115DD16E461E0FB218DE8F00MN2PR13MB3309namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 60e1f7d8-eb09-4d3c-ab99-08d70568c2f8
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2019 18:59:39.9800 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3343
Archived-At: <>
Subject: Re: [Teas] [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Jul 2019 18:59:49 -0000

Hi, Takuya, Reza,
A couple of drafts that have some details on Takuya’s question on association of RAN and core slices to transport slices.
- (section 2.2) and

The Transport Slice controller functionality in draft-rokui is present in the transport domain SDN-C in these drafts.
The slice controller in the 5G/3GPP domain (functionality identified by TNF, TPM in the drafts) establishes a context that maps between 3GPP/5G and transport slice and path.
The context mapping across 3GPP/ transport network is proportional to number of sites, classes of service, etc. --> much lower than number of PDU sessions, i.e., much less provisioning than per session.

The other related issue is about how to carry this “context” info in PDU /IP packets between 2 mobile network functions (gNB, UPF).
The gNB/UPF may not be part of the transport network (i.e., terminate MPLS, VLAN,..).
The drafts outline a couple of ways to carry this “context” as meta-data – which the transport network PE can inspect/grant the level of service provisioned.


This e-mail and any attachments may contain confidential information from Futurewei, which are intended only for the person or entity whose email address appears above. Any use of the information attached or contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or any unapproved dissemination) by persons other than the intended recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender by phone or response email immediately and delete this original message.

From: OPSAWG <> On Behalf Of Rokui, Reza (Nokia - CA/Ottawa)
Sent: Monday, July 08, 2019 7:06 AM
To: Takuya Miyasaka <>jp>;;;;;
Subject: Re: [OPSAWG] [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt

Sure Takuya I will add them to the new version of the draft.


From: Takuya Miyasaka <<>>
Date: Sunday, July 7, 2019 at 9:07 PM
To: Reza Rokui <<>>, "<>" <<>>, "<>" <<>>, "<>" <<>>, "<>" <<>>, "<>" <<>>
Subject: Re: [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt

Hi Reza,

Thanks for your response and please see my comments below with [Taku].

On 2019/07/04 23:51, Rokui, Reza (Nokia - CA/Ottawa) wrote:
Hi Takuya,
Very good question. The response is inline.


From: Takuya Miyasaka <><>
Date: Wednesday, July 3, 2019 at 7:54 AM
To: Reza Rokui <><>, ""<> <><>, ""<> <><>, ""<> <><>, ""<> <><>, ""<> <><>
Subject: Re: [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt

Hi Reza,

Thanks for sharing this draft. I'm curious about how to bind/associate 3GPP(RAN/Core) slice instance and Transport slice instance and section 5.2 of this draft describes as follows:

      o In order to have the connectivity between RAN1 and UPF1, the RAN
         and Core slices should be associated to Transport slice. This is
         also a by-product of the Transport slice connectivity interface
         when all allocated resources for access points (such as allocated
         VLAN IDs, IP addresses etc) are conveyed to RAN and Core Slices.
         This will be done by cordiantion between transport slice
         controller and E2E network slice controller.

As for this sentences, could you confirm if following procedures will be conducted between controllers in order to associate independent slice instances or not?
 - E2E Network Slice Controller sends a request on transport slice creation to Transport Controller (interface 10 of Fig.2)
 - Transport Controller creates transport slice instance and sends access point information(e.g. VLAN ID) to E2E Network Slice Controller
 - E2E Network Slice Controller sends a request on access point creation/modification to RAN/Core Controller
 - RAN/Core Controller create/modify access point on gNB/UPF respectively, which means gNB/UPF starts to attach adequate access point information(e.g. VLAN ID) on their user plane packet

[Reza] The above procedure is correct but this is one way to implement the binding (aka association) between RAN-Transport slices and Core-Transport slices.

[Taku] OK. If such kinds of procedures are taken at Core/RAN Controller, it might be better to describe such procedures in Section3.
          We also have to check if these access point information can be conveyed at the 3GPP defined interface between E2E Controller and Core/RAN Controller.

There are other ways to implement the binding. For example, the transport slice controller can populate the following two tables dynamically during the transport slice creation, modification or deletion and expose access to this table using open APIs. Then, the RAN/Core network functions or RAN/Core slice controllers can access these APIs to program the VLAN/IP/Labels.

  *   RAN-Transport mapping table: Which maps the RAN VLAN/IP address/MPLS Labels etc to network slice
  *   Core-Transport mapping table: Which maps the Core VLAN/IP address/MPLS Labels etc to network slice

[Taku] That sounds good.


Takuya Miyasaka
KDDI Research
On 2019/07/02 23:06, Rokui, Reza (Nokia - CA/Ottawa) wrote:
Hi all,

This is to inform you that the following new draft has been submitted to ietf.
The goal of this draft is to demonstrate the role of ietf for 5g network slicing in area of transport slices.

Your review and feedback would be greatly appreciated.


Reza Rokui

On 2019-07-02, 9:30 AM, ""<> <><> wrote:

    A new version of I-D, draft-rokui-5g-transport-slice-00.txt

    has been successfully submitted by Reza Rokui and posted to the

    IETF repository.

    Name:           draft-rokui-5g-transport-slice

    Revision: 00

    Title:          5G Transport Slice Connectivity Interface

    Document date:  2019-07-02

    Group:          Individual Submission

    Pages:          28
    URL:  <>


       The 5G Network slicing is an approach to provide separate independent

       E2E logical network from user equipment (UE) to applications where

       each network slice has different SLA requirements.  Each E2E network

       slice consists of multitude of RAN-slice, Core-slice and Transport-

       slices, each with its own controller.  To provide automation,

       assurance and optimization of the network slices, an E2E network

       slice controller is needed which interacts with controller in RAN,

       Core and Transport slices.  The interfaces between the E2E network

       slice controller and RAN and Core controllers are defined in various

       3GPP technical specifications.  However, 3GPP has not defined the

       same interface for transport slices.

       The aim of this document is to provide the clarification of this

       interface and to provide the information model of this interface for

       automation, monitoring and optimization of the transport slices.

    Please note that it may take a couple of minutes from the time of submission

    until the htmlized version and diff are available at

    The IETF Secretariat


dmm mailing list<><>