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

Takuya Miyasaka <ta-miyasaka@kddi-research.jp> Mon, 08 July 2019 01:08 UTC

Return-Path: <ta-miyasaka@kddi-research.jp>
X-Original-To: netslices@ietfa.amsl.com
Delivered-To: netslices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D17D1200E3; Sun, 7 Jul 2019 18:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 6yh4nc_fvFgL; Sun, 7 Jul 2019 18:08:11 -0700 (PDT)
Received: from mandala.kddilabs.jp (mandala.kddilabs.jp [IPv6:2001:200:601:12::16]) by ietfa.amsl.com (Postfix) with ESMTP id 6C3E31200D5; Sun, 7 Jul 2019 18:08:10 -0700 (PDT)
Received: from localhost (mandala.kddilabs.jp [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id 49AD0C2EE9EF; Mon, 8 Jul 2019 10:08:03 +0900 (JST)
X-Virus-Scanned: amavisd-new at kddi-research.jp
Received: from mandala.kddilabs.jp ([127.0.0.1]) by localhost (mandala.kddilabs.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZnADDI7JAWM; Mon, 8 Jul 2019 10:08:00 +0900 (JST)
Received: from safeattach.localdomain (unknown [IPv6:2001:200:601:1a00:20c:29ff:fe79:2280]) by mandala.kddilabs.jp (Postfix) with ESMTP id 7FC49C2EE9E0; Mon, 8 Jul 2019 10:08:00 +0900 (JST)
Received: from [172.19.124.101] (dhcp101.west-4f.cn.kddilabs.jp [172.19.124.101]) by safeattach.localdomain with ESMTP id x6817xHF002409; Mon, 8 Jul 2019 10:07:59 +0900
To: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>, "netslices@ietf.org" <netslices@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
References: <156207423989.23780.17141938373911518614.idtracker@ietfa.amsl.com> <936A6DF3-6AE8-4AD7-94C5-12AD68D9E0E4@nokia.com> <f6badc3f-0b2c-f09e-8f97-ab9bd36aaacb@kddi-research.jp> <7ED7381D-AA8B-4C31-AC75-939999730B8F@nokia.com>
From: Takuya Miyasaka <ta-miyasaka@kddi-research.jp>
Message-ID: <f7f0b7e6-21cf-04c6-f0fb-86429a183934@kddi-research.jp>
Date: Mon, 8 Jul 2019 10:07:59 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <7ED7381D-AA8B-4C31-AC75-939999730B8F@nokia.com>
Content-Type: multipart/alternative; boundary="------------6BCC56147CAE2BCAD99BF45B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netslices/KiZN1zbK9gAl0GeN_IhZUlzqs4M>
Subject: Re: [Netslices] [DMM] New Version Notification for draft-rokui-5g-transport-slice-00.txt
X-BeenThere: netslices@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is intended for discussion and review of network slicing at IETF." <netslices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netslices>, <mailto:netslices-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netslices/>
List-Post: <mailto:netslices@ietf.org>
List-Help: <mailto:netslices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netslices>, <mailto:netslices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jul 2019 01:08:15 -0000

Hi Reza,

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

Thanks,
Takuya

On 2019/07/04 23:51, Rokui, Reza (Nokia - CA/Ottawa) wrote:
>
> Hi Takuya,
>
> Very good question. The response is inline.
>
> Reza
>
> *From: *Takuya Miyasaka <ta-miyasaka@kddi-research.jp>;
> *Date: *Wednesday, July 3, 2019 at 7:54 AM
> *To: *Reza Rokui <reza.rokui@nokia.com>;, "netslices@ietf.org"; 
> <netslices@ietf.org>;, "rtgwg@ietf.org"; <rtgwg@ietf.org>;, 
> "opsawg@ietf.org"; <opsawg@ietf.org>;, "teas@ietf.org"; <teas@ietf.org>;, 
> "dmm@ietf.org"; <dmm@ietf.org>;
> *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.

>  *
>
> Thanks,
> 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.
>
>     Thanks,
>
>     Reza Rokui
>
>     On 2019-07-02, 9:30 AM, "internet-drafts@ietf.org";
>     <mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org>;
>     <mailto:internet-drafts@ietf.org> 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:
>     https://www.ietf.org/internet-drafts/draft-rokui-5g-transport-slice-00.txt
>
>         Status:
>     https://datatracker.ietf.org/doc/draft-rokui-5g-transport-slice/
>
>         Htmlized:
>     https://tools.ietf.org/html/draft-rokui-5g-transport-slice-00
>
>         Htmlized:
>     https://datatracker.ietf.org/doc/html/draft-rokui-5g-transport-slice
>
>         Abstract:
>
>     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 tools.ietf.org.
>
>         The IETF Secretariat
>
>
>
>     _______________________________________________
>
>     dmm mailing list
>
>     dmm@ietf.org  <mailto:dmm@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/dmm
>