[L3sm] R: [L2sm] Using VPN to offer eMBB, URLLC, mMTC service

Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it> Mon, 02 October 2017 15:18 UTC

Return-Path: <giuseppe.fioccola@telecomitalia.it>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95E07134695; Mon, 2 Oct 2017 08:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 DHcwzYPvHgKr; Mon, 2 Oct 2017 08:18:31 -0700 (PDT)
Received: from mx02.telecomitalia.it (mx02.telecomitalia.it [217.169.121.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DED7134694; Mon, 2 Oct 2017 08:18:30 -0700 (PDT)
X-AuditID: d9a97916-d25ff700000002cc-b7-59d258c49d68
Received: from TELMBXB02RM001.telecomitalia.local ( [10.14.252.27]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx02.telecomitalia.it () with SMTP id 5B.FD.00716.4C852D95; Mon, 2 Oct 2017 17:18:28 +0200 (CEST)
From: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>
To: Aijun Wang <wangaijun@tsinghua.org.cn>, "l3sm@ietf.org" <l3sm@ietf.org>, "l2sm@ietf.org" <l2sm@ietf.org>
Thread-Topic: [L3sm][L2sm] Using VPN to offer eMBB, URLLC, mMTC service
Thread-Index: AdM7jwmvOhRxeqNQTXyc1m2Qg+iqpw==
Date: Mon, 2 Oct 2017 15:18:27 +0000
Message-ID: <38ffa9f963344f7baa746da6fc0edd57@TELMBXB02RM001.telecomitalia.local>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.14.252.250]
x-ti-disclaimer: Disclaimer1
Content-Type: multipart/alternative; boundary="_000_38ffa9f963344f7baa746da6fc0edd57TELMBXB02RM001telecomit_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrDKsWRmVeSWpSXmKPExsXCxfdHWvdIxKVIg6U/JCzuvHzJaPF14kJW iy2df9gdmD2WLPnJ5LGmeS5bAFNUA6NNYl5efkliSapCSmpxsq2SS2Zxck5iZm5qkUJIak5q cn6ukkJmiq2SsZJCQU5icmpual6JrVJiQUFqXoqSHZcCBrABKsvMU0jNS85PycxLt1XyDPbX tbAwtdQ1VLILLE0tLslXyE0tLk5MT8/MV0hNWC+Y8WtSJ0tBxy7GikvH57E1MG5cxtjFyMkh IWAi0XDhKWsXIxeHkMBUJomTZ7+xgyTYBGwkDr46wQZiiwjkSUz7vYYZxBYWcJWYuP8NK0Tc XeLu30WMELaexP9d18F6WQRUJKY9/wJWzysQKPH6zXwmEJtRQFZiwm6IemYBcYkX00+wQxwh ILFkz3lmCFtU4uXjf6wQtoHE1qX7WCBsRYlJp55CxWUkFh6ZzAoxJ19iw/U/LBC7BCVOznzC MoFRaBaSFbOQlM1CUgYR15FYsPsTG4StLbFs4WtmGPvMgcdMyOILGNlXMYrmVhgY6ZVAYi2z JDEnM1Evs2QTIzBJ3FxZKbaDsXWt8yFGAQ5GJR7e236XIoVYE8uKK3MPMUpwMCuJ8B7yAQrx piRWVqUW5ccXleakFh9i9AGG2ERmKdHkfGACyyuJNzSxsDQ0trAwMrQwM8UhrCTOu5QDaJZA OjBZZaemFqQWwYxj4uCUamBUa7E6svejfECK5VJbjepzxY974xbfsZz99HoddyOHsegBM7fl W95dObux/bY/78oK6dltrI8u3ODOv1kll20rbFai8WHD/74Tk+Scv/1XMP3Dw7ouw7KMN+u8 X+YRl1fMV04sXH54hrhoS/szrmj9f1t1VPZqPJhw60LK0zevmKq3PX9Ww8mjxFKckWioxVxU nAgApjPF7j8DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/9YP15b5iaYWhz3XIPqqOGaN-960>
Subject: [L3sm] R: [L2sm] Using VPN to offer eMBB, URLLC, mMTC service
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Oct 2017 15:18:33 -0000

Hi Aijun,
That looks like a reasonable proposal to me. The first thing we can do is to add new qos-profiles for eMBB, URLLC, mMTC services (see below).
Also service-oam  can be useful to verify the resource allocation and the end to end performance.
So, of course, we can use VPN service model to offer these services and, we can consider that the service orchestrator is responsible of the mapping between service characteristics and slicing by using L2SM.

Best Regards,

Giuseppe


    identity customer-application {

     description

      "Base identity for customer application.";

    }

    identity web {

     base customer-application;

     description

      "Identity for Web application (e.g., HTTP, HTTPS).";

    }

    identity mail {

     base customer-application;

     description

      "Identity for mail application.";

    }

    identity file-transfer {

     base customer-application;

     description

      "Identity for file transfer application (e.g., FTP, SFTP).";

    }

    identity embb {

     base customer-application;

     description

     "Identity for eMBB application;";

    }

    identity urllc {

     base customer-application;

     description

     "Identity for URLLC application;";

     }

     identity mmtc {

      base customer-application;

      description

      "Identity for mMTC application;";

     }


Da: L3sm [mailto:l3sm-bounces@ietf.org] Per conto di Aijun Wang
Inviato: sabato 30 settembre 2017 09:52
A: l3sm@ietf.org; l2sm@ietf.org
Oggetto: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service

Hi, All:
IP convergence is continuing to drive new classes of devices to begin communicating via IP.  Examples of such devices could include STB boxes for IP video distribution, cell tower electronics (macro or micro cells), infrastructure Wi-Fi access points, and devices for machine-to-machine (M2M) or Internet of Things (IoT) applications.
In some cases, these classes of devices represent a very large deployment base, on the order of thousands or even millions of devices network-wide. In 5G slicing case, three typical services offered to these devices are
1. Enhanced Mobile Broadband(eMBB)
2. Ultra-Reliable and Low Lantency Communication (URLLC)
3. Massive Machine Type Communications (mMTC)
These services demand the network performance with wide variety of characteristics such as data rate, latency, loss rate, reliability and many other parameters.
My question is the followings:

1.       Can we use VPN service model to offer such kind of new services to customers?

2.       Should we define new services characteristic that is based on the new slicing capabilities provided by network devices?


Best Regards.

Aijun Wang
Network R&D and Operation Support Department
China Telecom Corporation Limited Beijing Research Institute,Beijing, China.




Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. 

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. 

Rispetta l'ambiente. Non stampare questa mail se non รจ necessario.