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

"Diego R. Lopez" <> Wed, 10 July 2019 17:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C3852120295; Wed, 10 Jul 2019 10:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, 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 sldrTpnOkAjs; Wed, 10 Jul 2019 10:39:59 -0700 (PDT)
Received: from ( [IPv6:2a01:111:f400:fe07::711]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C353C12034B; Wed, 10 Jul 2019 10:39:31 -0700 (PDT)
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=S+nLO01HzYx228hfkm0sl336YXUaOBt8+KD57NEyQaQ=; b=VSO/7r1reYxphphXgae0RnaPSSNb7AlSiVL/mMmPh/A6zhtmTMW7+Wnc/RGslOz/b437YlaSQFcXN3VbKy0BJPv9KuyGYF/5c9cUKZ/3G9ObU6rRQtCkV57rMUVZbTKz7fHVVUShOIZjK+3A4Sjuhxhw22TFe1WeXfD4KwptAXs=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.18; Wed, 10 Jul 2019 17:39:29 +0000
Received: from ([fe80::2941:d402:a2ae:f777]) by ([fe80::2941:d402:a2ae:f777%6]) with mapi id 15.20.2052.020; Wed, 10 Jul 2019 17:39:29 +0000
From: "Diego R. Lopez" <>
To: "Rokui, Reza (Nokia - CA/Ottawa)" <>, Takuya Miyasaka <>, "" <>, "" <>, "" <>, "" <>, "" <>
Thread-Topic: [Netslices] [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt
Thread-Index: AQHVN0Zsy5yrbSrPc0mf3dI8JUaY9A==
Date: Wed, 10 Jul 2019 17:39:28 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.10.b.190609
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b804489c-d033-4e55-7228-08d7055d8f4a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DB3PR0602MB3836;
x-ms-traffictypediagnostic: DB3PR0602MB3836:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0094E3478A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(136003)(39860400002)(346002)(366004)(376002)(189003)(40134004)(53754006)(199004)(53936002)(6512007)(54896002)(2420400007)(15650500001)(33656002)(486006)(53946003)(6306002)(236005)(66446008)(14444005)(256004)(64756008)(66556008)(66476007)(66946007)(6246003)(5024004)(4326008)(606006)(229853002)(6436002)(76116006)(2501003)(107886003)(66066001)(6486002)(91956017)(5660300002)(66574012)(186003)(8936002)(478600001)(6506007)(26005)(45080400002)(3846002)(68736007)(53546011)(6116002)(966005)(81156014)(81166006)(7736002)(8676002)(476003)(790700001)(7110500001)(25786009)(86362001)(110136005)(2906002)(54906003)(316002)(296002)(786003)(71190400001)(71200400001)(58126008)(2616005)(36756003)(2201001)(99286004)(102836004)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR0602MB3836;; 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: w75FOVdE18be7kvjvu9kSFCpKM9sVbEQo3YSy5/+TEcIOLQjfVYu1CGsPwC1KZ0nkWGAZpTSpfPn+uiSlcqIfcPaj6q8hl2WQxdnlJmrQNfyLkSl5SIvejE6FzaIA6ZVA3qfit64sn4fobyUURsX8Gfh3Mo0S2asG3GHo9JO3xu1MUR9fgIOXkbVn5ISdXn5i2ZitAlRNVfgTYvl3ov7Jd45TH3NbMnUX1ul0sciPZ+XJ1U4dVjlGTIPMBJlLViuswYQaP0CQPczrVYNvK+lLB5/iLV/gxUrWmZPasD5hrMsx0KXyHjnECBqCLpPOTktW2/+ANo+Mb+hzGFAxKqWosaMgyvZsn/0qi7a5uk6b2hpIt+sXfk5nmMYcWLAJL/ja4LEz/eaW7azYGyxGXUhhVKVSns+A0M6UZEA7cXOdKE=
Content-Type: multipart/alternative; boundary="_000_FC5E6295ABAD4422A55D232A93C0AABEtelefonicacom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b804489c-d033-4e55-7228-08d7055d8f4a
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2019 17:39:28.8913 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR0602MB3836
Archived-At: <>
Subject: Re: [Teas] [Netslices] [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 17:40:06 -0000


A colleague in the ETSI NFV has remarked to me the fact that the group has created a quite detailed spec, rooted at the ACTN ideas as well, on the interface to manage transport links among sites. I think this spec (IFA032, is a valuable foundation for the goals of this draft.

Be goode,

"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

Tel:         +34 913 129 041
Mobile:  +34 682 051 091

On 08/07/2019, 13:08, "Netslices on behalf of Rokui, Reza (Nokia - CA/Ottawa)" <<> on behalf of<>> wrote:

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 <>om>, "" <>rg>, "" <>rg>, "" <>rg>, "" <>rg>, "" <>
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


       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<>


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição