IETF Logo Mail Archive

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

"Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com> Tue, 02 July 2019 14:06 UTC

Return-Path: <reza.rokui@nokia.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 4D7B1120041; Tue, 2 Jul 2019 07:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 JmFODox4fa8N; Tue, 2 Jul 2019 07:06:36 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30109.outbound.protection.outlook.com [40.107.3.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9EA912011C; Tue, 2 Jul 2019 07:06:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MAysEcHXjpbDI3eGcCByyBi0sVczjceYSnGI0PDJSB4=; b=V0wJ9NuDcufbWOcu/7FYCeF9/VtfS3ZqVmLIrfOsnQbXNrq3i7n4xpWvPAdiiac/HDY8EwSSaEqAz231zNwZhfVw12WX1B3HjaIe8Bye0Jm+626IIQDp9Q2i1rFFO2T8F3uXWLZpepFbgsoGUQ3jmuogk25B0mP10O+BK78cxqM=
Received: from AM0PR07MB6098.eurprd07.prod.outlook.com (20.178.112.202) by AM0PR07MB6099.eurprd07.prod.outlook.com (20.178.113.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.14; Tue, 2 Jul 2019 14:06:33 +0000
Received: from AM0PR07MB6098.eurprd07.prod.outlook.com ([fe80::68ff:d164:b06e:37c]) by AM0PR07MB6098.eurprd07.prod.outlook.com ([fe80::68ff:d164:b06e:37c%7]) with mapi id 15.20.2052.010; Tue, 2 Jul 2019 14:06:33 +0000
From: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
To: "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>
CC: "Rokui, Reza (Nokia - CA/Ottawa)" <reza.rokui@nokia.com>
Thread-Topic: New Version Notification for draft-rokui-5g-transport-slice-00.txt
Thread-Index: AQHVMN9aJcNuZoHSe0aJiDXoSztzgQ==
Date: Tue, 02 Jul 2019 14:06:33 +0000
Message-ID: <936A6DF3-6AE8-4AD7-94C5-12AD68D9E0E4@nokia.com>
References: <156207423989.23780.17141938373911518614.idtracker@ietfa.amsl.com>
In-Reply-To: <156207423989.23780.17141938373911518614.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
authentication-results: spf=none (sender IP is ) smtp.mailfrom=reza.rokui@nokia.com;
x-originating-ip: [131.228.48.77]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 37805f51-6e55-427d-5339-08d6fef67cfb
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:AM0PR07MB6099;
x-ms-traffictypediagnostic: AM0PR07MB6099:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <AM0PR07MB60993122088DD1AC44A7077E9FF80@AM0PR07MB6099.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 008663486A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(366004)(136003)(376002)(396003)(39860400002)(53754006)(189003)(199004)(64756008)(6512007)(6436002)(53936002)(54896002)(6306002)(66556008)(8936002)(66446008)(236005)(229853002)(91956017)(76116006)(110136005)(58126008)(6486002)(66476007)(66946007)(73956011)(66066001)(316002)(71200400001)(486006)(256004)(2501003)(66574012)(33656002)(71190400001)(68736007)(2616005)(99286004)(86362001)(11346002)(450100002)(2201001)(446003)(478600001)(5660300002)(102836004)(7736002)(76176011)(6116002)(4326008)(107886003)(3846002)(25786009)(14454004)(6246003)(606006)(2906002)(8676002)(6506007)(81156014)(81166006)(186003)(26005)(476003)(36756003)(966005); DIR:OUT; SFP:1102; SCL:1; SRVR:AM0PR07MB6099; H:AM0PR07MB6098.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: xTHE/7g7QEyMxPcsS4pbphaOaQ500Wmmq5oTfYPcHroOeep+7jzmdH00/3j89FoKN8LnWpje+PtzVQHSTmV+QzCrRaiir7JJ7P5vT2AcyTw5msmUwMn8FJ4aMo9doG3Gc1eh9JhJfUbodDyZYJ6ItyxxDemtDjAVhPxVThNnREZRUQDJJRliZCD7d4lfrY5AMK8V5NjMKlPXohgTJdHJW+S24rPauEME/QkeIyhw8CkJ/kGFJzlUDvqsvi4JXwbtmf04DwYEEup1iwQcEnWWX4zmYEukCsWlmL7UG58y92kYnYDdh2UU7S/uArh1f+4Ha0PUQRi+A6NtM1ar3U2AtMTDia/EoM6PvLOyoHr0T+gSuPOnIwrThdl0hWtIEJLEMTt2fviLrqiVRCLFPhQtGNQb5rigQG0kj5hnU9KzIaM=
Content-Type: multipart/alternative; boundary="_000_936A6DF36AE84AD794C512AD68D9E0E4nokiacom_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 37805f51-6e55-427d-5339-08d6fef67cfb
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2019 14:06:33.0460 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: reza.rokui@nokia.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB6099
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/zUnhJGXlU6b3h0cA7HmDHr8fwEo>
Subject: Re: [Teas] New Version Notification for draft-rokui-5g-transport-slice-00.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Jul 2019 14:06:43 -0000

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

v2.23.0 | Report a Bug | By Email