From nobody Mon Oct 2 08:18:39 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@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 To: Aijun Wang , "l3sm@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: Subject: [L2sm] R: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2017 15:18:33 -0000 --_000_38ffa9f963344f7baa746da6fc0edd57TELMBXB02RM001telecomit_ content-type: text/plain; charset="ISO-8859-1" content-transfer-encoding: quoted-printable 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 en= d 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 be= tween 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 commun= icating via IP. Examples of such devices could include STB boxes for IP vid= eo distribution, cell tower electronics (macro or micro cells), infrastructu= re 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 ba= se, on the order of thousands or even millions of devices network-wide. In 5= G 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 character= istics such as data rate, latency, loss rate, reliability and many other par= ameters. 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 n= ew 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 pers= one indicate. La diffusione, copia o qualsiasi altra azione derivante dalla= conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbia= te ricevuto questo documento per errore siete cortesemente pregati di darne= immediata comunicazione al mittente e di provvedere alla sua distruzione, G= razie. This e-mail and any attachments is confidential and may contain privileged i= nformation intended for the addressee(s) only. Dissemination, copying, print= ing or use by anybody else is unauthorised. If you are not the intended reci= pient, 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 =E8 necessario. --_000_38ffa9f963344f7baa746da6fc0edd57TELMBXB02RM001telecomit_ Content-Type: text/html; charset="us-ascii" content-transfer-encoding: quoted-printable

Hi Aijun,

That looks like a reasonable proposal to me. The fir= st 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 allocat= ion 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 ma= pping between service characteristics and slicing by using L2SM.

 

Best Regards,

 

Giuseppe

 

    identity customer-application=
 {
     description
      "Base identit=
y for customer application.";
    }<=
o:p>
    identity web {
     base customer-applicatio=
n;
     description
      "Identity for=
 Web application (e.g., HTTP, HTTPS).";
    }<=
o:p>
    identity mail {
     base customer-applicatio=
n;
     description
      "Identity for=
 mail application.";

    }<=
o:p>


    identity file-transfer {


     base customer-applicatio=
n;


     description


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


    }<=
o:p>


    identity embb {


     base customer-=
application;


     description


     “=
Identity for eMBB application;”;


    }


    identity urllc {


     base customer-=
application;


     description


     “=
Identity for URLLC application;”;


     }


     identity mmtc=
 {


      base cus=
tomer-application;


      descript=
ion


      <=
span lang=3D"ZH-CN" style=3D"font-size:7.5pt;font-family:SimSun;color:red">&=
#8220;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






 <=
/o:p>


Hi, All:


IP convergence is continuing to drive new classes of devices to begin c=
ommunicating 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 deployme=
nt 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 char=
acteristics such as data rate, latency, loss rate, reliability and many othe=
r 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 t=
he 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, C=
hina.


 


 


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

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

Rispetta l'ambiente. Non stampare questa mail se non è necessa= rio.
--_000_38ffa9f963344f7baa746da6fc0edd57TELMBXB02RM001telecomit_-- From nobody Thu Oct 5 05:17:01 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EC7F1342C5 for ; Thu, 5 Oct 2017 05:17:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.101 X-Spam-Level: X-Spam-Status: No, score=0.101 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, 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 BbF5tKBcTaso for ; Thu, 5 Oct 2017 05:16:58 -0700 (PDT) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6F98132D79 for ; Thu, 5 Oct 2017 05:16:50 -0700 (PDT) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v95CGlaL022558 for ; Thu, 5 Oct 2017 13:16:47 +0100 Received: from 950129200 (218.122.115.87.dyn.plus.net [87.115.122.218]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v95CGkbM022550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 5 Oct 2017 13:16:47 +0100 Reply-To: From: "Adrian Farrel" To: Date: Thu, 5 Oct 2017 13:16:42 +0100 Message-ID: <010001d33dd3$ceb07160$6c115420$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdM908pf2R8ycSdyQByTA1+v7nyfag== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23372.006 X-TM-AS-Result: No-0.121-10.0-31-10 X-imss-scan-details: No-0.121-10.0-31-10 X-TMASE-MatchedRID: 8vTb4TXfLhH1lGRVqRJJbe0yyL51qL/RfS0Ip2eEHny+qryzYw2E8M4b ajgO0kgvgZK4jdUf7rWxAvNp3ItVysRB0bsfrpPInxMyeYT53RnqQgT2fY1b/dEsxURh8hN4SGV nPLaDxz4nwyNzgVLYx1Lfblmmk6GpfEcdlO4TxYYXtMkVMy3YXanWuzYmgqjf+zv5FLscmLSl1O /WvQ0mLI9NJFPyrFBRLg4B6mj6omcVqi/E4tLe3sPINhwTXBeZ Archived-At: Subject: [L2sm] Virtual interim minutes and meeting materials X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 12:17:00 -0000 I posted the materials and minutes of the interim at https://datatracker.ietf.org/meeting/interim-2017-l2sm-02/session/l2sm I will follow up on the actions shortly. Adrian From nobody Thu Oct 5 07:41:41 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5404A1321BB for ; Thu, 5 Oct 2017 07:41:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.1 X-Spam-Level: X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7] 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 0Ed024YZ3nO8 for ; Thu, 5 Oct 2017 07:41:38 -0700 (PDT) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 731BB1321B6 for ; Thu, 5 Oct 2017 07:41:37 -0700 (PDT) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v95EfZ7g029850 for ; Thu, 5 Oct 2017 15:41:35 +0100 Received: from 950129200 (218.122.115.87.dyn.plus.net [87.115.122.218]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v95EfWig029788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 5 Oct 2017 15:41:34 +0100 Reply-To: From: "Adrian Farrel" To: Date: Thu, 5 Oct 2017 15:41:28 +0100 Message-ID: <015d01d33de8$08d12e70$1a738b50$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdM95rO5De3y6+9pQwaV6PUXVhwW+Q== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23374.000 X-TM-AS-Result: No--1.005-10.0-31-10 X-imss-scan-details: No--1.005-10.0-31-10 X-TMASE-MatchedRID: Z3L4srrNKAt8FFGtK5UwdYGLeiqu1yTKhHz3EzK//HzSYAzZ6KmqWohp c0cNJBVgKKN1cQangWAagCCNzTrLENvJAvCq+wLJ4nbwqqmOd2nTBg/CbgV2T7rfxlRjqBJ3X47 th4T5R3oQPSi1yFcBxiB7yVsihj14V9xWZ+A7xPLlM5hHF9yMby3S35ohUu37ClyrX4tOmxSjxY yRBa/qJX3mXSdV7KK4FAX4EtUi0PgLbigRnpKlKZx+7GyJjhAU71say0jyOFITbhDmBegQMgh1l Cp5WyPOD308+RXB3sUXWeuyVvSh99SxeFhBYHL7pVCFVXGtPoeZtpaI12m+3hlaof+C0tFV9HmA sM11v0u45mjKIIYY3xiCad9aBKWfm9p/RC99TJ5Lhb8xGEnVfg== Archived-At: Subject: [L2sm] Removing EVC and OVC from L2SM X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2017 14:41:39 -0000 Hi, During our interim we discussed the various attributes that support EVC and OVC. They were motivated by attempts to support MEF-defined services. The meeting made some observations: - The primary focus of our work should be to describe IETF work - We should limit this module to describing IETF L2VPN services - We should observe (if it is our opinion) that that mapping from this module to the MEF's EVC service attributes may be possible (but we should state that doing that is out of scope for this document) Considering that, the meeting had no objection to removing the evc and ovc subtrees from the module. Additionally, while we would retain 'metro-networks' as useful for multi-domain, we would drop ovc-id from that part of the module. This email is your chance to object or point out why we were wrong. Silence will mean that the next revision removes evc and ovc. Thanks, Adrian From nobody Tue Oct 10 22:57:43 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BEE813303A; Tue, 10 Oct 2017 22:57:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 tSfZit_yzZkz; Tue, 10 Oct 2017 22:57:36 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 061D81320C9; Tue, 10 Oct 2017 22:57:33 -0700 (PDT) Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQH64345; Wed, 11 Oct 2017 05:57:32 +0000 (GMT) Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 11 Oct 2017 06:57:31 +0100 Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.199]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Wed, 11 Oct 2017 13:57:27 +0800 From: Qin Wu To: Aijun Wang , "l3sm@ietf.org" , "l2sm@ietf.org" Thread-Topic: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service Thread-Index: AdM5wPeX7QC+PzrKQwKPsvwE16mphAIio84w Date: Wed, 11 Oct 2017 05:57:27 +0000 Message-ID: References: <008a01d339c0$f9049ed0$eb0ddc70$@org.cn> In-Reply-To: <008a01d339c0$f9049ed0$eb0ddc70$@org.cn> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.136.79.163] Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9ABA8B08nkgeml513mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.59DDB2CC.00AA, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.199, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: c87f7461fbd5a0ae62c7e11d35d39e9b Archived-At: Subject: Re: [L2sm] [L3sm] Using VPN to offer eMBB, URLLC, mMTC service X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 05:57:37 -0000 --_000_B8F9A780D330094D99AF023C5877DABA9ABA8B08nkgeml513mbxchi_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 VGhhbmsgQWlqdW4gdG8gcmFpc2UgdGhpcyBpbnRlcmVzdGluZyBxdWVzdGlvbiwNCkkgdGhpbmsg dGhlIEwzU00gbW9kZWwgaGFzIGRlZmluZWQgdmFyaW91cyBjdXN0b21lciBhcHBsaWNhdGlvbnMg YnkgdXNpbmcgaWRlbnRpdHksDQpDdXN0b21lciBhcHBsaWNhdGlvbnMgdGhhdCBjYW4gYmUgb2Zm ZXJlZCBieSBWUE4gaW5jbHVkZSB3ZWIsIG1haWwsIHAycCwgdm9pY2UsIHZpZGVvLGV0Yy4NCmJ1 dCBuZXcgYXBwbGljYXRpb24gIGlkZW50aXRpZXMgbWF5IGJlIGFkZGVkIHRocm91Z2ggYXVnbWVu dGF0aW9uLg0KWWVzLCBlTUJCLCBVUkxMQywgbU1UQyBhcmUgbmV3IGVtZXJnaW5nICBzZXJ2aWNl IHRoYXQgY2FuIGJlIG9mZmVyZWQgaWYgNUcgc2xpY2luZyB3YW50IHRvIGxldmVyYWdlIFZQTiB0 ZWNobm9sb2d5Lg0KQnV0IG9uZSB0aGluZyBJIGFtIG5vdCBzdXJlIGlzIHdoZXRoZXIgc2Vydmlj ZSBtb2RlbCBzaG91bGQgYmUgYXdhcmUgb2YgbmV0d29yayBzbGljaW5nLCB0byBtZSwgSSB0aGlu ayBuZXR3b3JrIHNsaWNpbmcgaXMgbW9yZSByZWxhdGVkIHRvDQpob3cgdGhlIHNlcnZpY2UgaXMg ZGVsaXZlcmVkLCBob3cgdGhlIHJlc291cmNlIGlzIGFsbG9jYXRlZC9pc29sYXRlZC9wYXJ0aXRp b25lZC4NCkluIG1hbnkgY2FzZXMsIHdlIGNhbiB0YWtlIGFkdmFudGFnZSBvZiBleGlzdGluZyBt b2RlbHMgZGV2ZWxvcGVkIGJ5IElFVEYgc3VjaCBhcyBJMlJTIHRvcG9sb2d5IG1vZGVsLCBURSB0 b3BvbG9neSBtb2RlbCB0byB1bmRlcnN0YW5kIHVuZGVybHlpbmcNCk5ldHdvcmsgY2FwYWNpdHks IGNhcGFiaWxpdHksIHJlc291cmNlIGRpc3RyaWJ1dGlvbiwgYW5kIHRoZW4gYWxsb2NhdGUgcmVz b3VyY2UgYmFzZWQgb24gY3VzdG9tZXIgc2VydmljZSByZXF1aXJlbWVudHMgcHJvdmlkZWQgYnkg c2VydmljZSBtb2RlbC4NCg0KQW5vdGhlciBwcm9ibGVtIHdlIGhhdmUgdG8gb2ZmZXIgc3VjaCBr aW5kIG9mIHNlcnZpY2UgaXM6DQpXaGF0IGtpbmQgb2YgbmV0d29yayB0ZWNobm9sb2d5IGNhbiBi ZSB1c2VkIHRvIHJlYWxpemUgc3VjaCBzZXJ2aWNlPw0KWWVzLCB3ZSBjYW4gYWRkIG5ldyBhcHBs aWNhdGlvbiBpZGVudGl0eSBmb3IgZU1CQiwgVVJMTEMsIG1NVEMgc2VydmljZSwgYnV0IEkgZG91 YnQgd2Ugc2hvdWxkIGFkZCBhbnkgb3RoZXIgbmV3IHNlcnZpY2UgY2hhcmFjdGVyaXN0aWMgYmVz aWRlcw0KT25lcyB3ZSBoYXZlIGFscmVhZHkgZGVmaW5lZCB1bmRlciBRb1MgcHJvZmlsZSBpbiBz ZXJ2aWNlIG1vZGVsLg0KDQotUWluDQq3orz+yMs6IEwzc20gW21haWx0bzpsM3NtLWJvdW5jZXNA aWV0Zi5vcmddILT6se0gQWlqdW4gV2FuZw0Kt6LLzcqxvOQ6IDIwMTfE6jnUwjMwyNUgMTU6NTIN CsrVvP7IyzogbDNzbUBpZXRmLm9yZzsgbDJzbUBpZXRmLm9yZw0K1vfM4jogW0wzc21dIFVzaW5n IFZQTiB0byBvZmZlciBlTUJCLCBVUkxMQywgbU1UQyBzZXJ2aWNlDQoNCkhpLCBBbGw6DQpJUCBj b252ZXJnZW5jZSBpcyBjb250aW51aW5nIHRvIGRyaXZlIG5ldyBjbGFzc2VzIG9mIGRldmljZXMg dG8gYmVnaW4gY29tbXVuaWNhdGluZyB2aWEgSVAuICBFeGFtcGxlcyBvZiBzdWNoIGRldmljZXMg Y291bGQgaW5jbHVkZSBTVEIgYm94ZXMgZm9yIElQIHZpZGVvIGRpc3RyaWJ1dGlvbiwgY2VsbCB0 b3dlciBlbGVjdHJvbmljcyAobWFjcm8gb3IgbWljcm8gY2VsbHMpLCBpbmZyYXN0cnVjdHVyZSBX aS1GaSBhY2Nlc3MgcG9pbnRzLCBhbmQgZGV2aWNlcyBmb3IgbWFjaGluZS10by1tYWNoaW5lIChN Mk0pIG9yIEludGVybmV0IG9mIFRoaW5ncyAoSW9UKSBhcHBsaWNhdGlvbnMuDQpJbiBzb21lIGNh c2VzLCB0aGVzZSBjbGFzc2VzIG9mIGRldmljZXMgcmVwcmVzZW50IGEgdmVyeSBsYXJnZSBkZXBs b3ltZW50IGJhc2UsIG9uIHRoZSBvcmRlciBvZiB0aG91c2FuZHMgb3IgZXZlbiBtaWxsaW9ucyBv ZiBkZXZpY2VzIG5ldHdvcmstd2lkZS4gSW4gNUcgc2xpY2luZyBjYXNlLCB0aHJlZSB0eXBpY2Fs IHNlcnZpY2VzIG9mZmVyZWQgdG8gdGhlc2UgZGV2aWNlcyBhcmUNCjEuIEVuaGFuY2VkIE1vYmls ZSBCcm9hZGJhbmQoZU1CQikNCjIuIFVsdHJhLVJlbGlhYmxlIGFuZCBMb3cgTGFudGVuY3kgQ29t bXVuaWNhdGlvbiAoVVJMTEMpDQozLiBNYXNzaXZlIE1hY2hpbmUgVHlwZSBDb21tdW5pY2F0aW9u cyAobU1UQykNClRoZXNlIHNlcnZpY2VzIGRlbWFuZCB0aGUgbmV0d29yayBwZXJmb3JtYW5jZSB3 aXRoIHdpZGUgdmFyaWV0eSBvZiBjaGFyYWN0ZXJpc3RpY3Mgc3VjaCBhcyBkYXRhIHJhdGUsIGxh dGVuY3ksIGxvc3MgcmF0ZSwgcmVsaWFiaWxpdHkgYW5kIG1hbnkgb3RoZXIgcGFyYW1ldGVycy4N Ck15IHF1ZXN0aW9uIGlzIHRoZSBmb2xsb3dpbmdzOg0KDQoxLiAgICAgICBDYW4gd2UgdXNlIFZQ TiBzZXJ2aWNlIG1vZGVsIHRvIG9mZmVyIHN1Y2gga2luZCBvZiBuZXcgc2VydmljZXMgdG8gY3Vz dG9tZXJzPw0KDQoyLiAgICAgICBTaG91bGQgd2UgZGVmaW5lIG5ldyBzZXJ2aWNlcyBjaGFyYWN0 ZXJpc3RpYyB0aGF0IGlzIGJhc2VkIG9uIHRoZSBuZXcgc2xpY2luZyBjYXBhYmlsaXRpZXMgcHJv dmlkZWQgYnkgbmV0d29yayBkZXZpY2VzPw0KDQoNCkJlc3QgUmVnYXJkcy4NCg0KQWlqdW4gV2Fu Zw0KTmV0d29yayBSJkQgYW5kIE9wZXJhdGlvbiBTdXBwb3J0IERlcGFydG1lbnQNCkNoaW5hIFRl bGVjb20gQ29ycG9yYXRpb24gTGltaXRlZCBCZWlqaW5nIFJlc2VhcmNoIEluc3RpdHV0ZSxCZWlq aW5nLCBDaGluYS4NCg0KDQoNCg== --_000_B8F9A780D330094D99AF023C5877DABA9ABA8B08nkgeml513mbxchi_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Thank A= ijun to raise this interesting question,

I think= the L3SM model has defined various customer applications by using identity= ,

Custome= r applications that can be offered by VPN include web, mail, p2p, voice, vi= deo,etc.

but new= application  identities may be added through augmentation.=

Yes, eM= BB, URLLC, mMTC are new emerging  service that can be offered if 5G sl= icing want to leverage VPN technology.

But one= thing I am not sure is whether service model should be aware of network sl= icing, to me, I think network slicing is more related to<= /p>

how the= service is delivered, how the resource is allocated/isolated/partitioned.<= o:p>

In many= cases, we can take advantage of existing models developed by IETF such as = I2RS topology model, TE topology model to understand underlying<= /span>

Network= capacity, capability, resource distribution, and then allocate resource ba= sed on customer service requirements provided by service model.<= /span>

&n= bsp;

Another= problem we have to offer such kind of service is:

What ki= nd of network technology can be used to realize such service?

Yes, we= can add new application identity for eMBB, URLLC, mMTC service, but I doub= t we should add any other new service characteristic besides

Ones we= have already defined under QoS profile in service model.=

&n= bsp;

-Qin

=B7=A2=BC=FE=C8=CB: L3sm [mailto:l3sm-bounces@ietf.org] =B4=FA= =B1=ED Aijun Wang
=B7=A2= =CB=CD=CA=B1=BC=E4: 2017=C4=EA9=D4=C230=C8=D5 15:52
=CA=D5=BC=FE=C8=CB: l3sm@ietf.org; l2sm@ietf.org
=D6=F7=CC=E2: [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 to= wer 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(eM= BB)

2. Ultra-Reliable and Low Lante= ncy Communication (URLLC)

3. Massive Machine Type Communi= cations (mMTC)

These services demand the netwo= rk performance with wide variety of characteristics such as data rate, late= ncy, loss rate, reliability and many other parameters.

My question is the followings:<= o:p>

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

2= .   &= nbsp;   Should we define new se= rvices characteristic that is based on the new slicing capabilities provide= d by network devices?

 

 

Best Regards.=

 

Aijun Wang

Network R&D and Operation S= upport Department

China Telecom Corporation Limit= ed Beijing Research Institute,Beijing, China.

 

 

 

--_000_B8F9A780D330094D99AF023C5877DABA9ABA8B08nkgeml513mbxchi_-- From nobody Tue Oct 10 23:00:52 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 005D4132D4B; Tue, 10 Oct 2017 23:00:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 eocW9fSJR2B2; Tue, 10 Oct 2017 23:00:48 -0700 (PDT) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 545491320C9; Tue, 10 Oct 2017 23:00:46 -0700 (PDT) Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQH64746; Wed, 11 Oct 2017 06:00:44 +0000 (GMT) Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 11 Oct 2017 07:00:42 +0100 Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.199]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Wed, 11 Oct 2017 14:00:36 +0800 From: Qin Wu To: Fioccola Giuseppe , Aijun Wang , "l3sm@ietf.org" , "l2sm@ietf.org" Thread-Topic: [L2sm] R: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service Thread-Index: AdM7jwmvOhRxeqNQTXyc1m2Qg+iqpwGxuOjA Date: Wed, 11 Oct 2017 06:00:36 +0000 Message-ID: References: <38ffa9f963344f7baa746da6fc0edd57@TELMBXB02RM001.telecomitalia.local> In-Reply-To: <38ffa9f963344f7baa746da6fc0edd57@TELMBXB02RM001.telecomitalia.local> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.136.79.163] Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9ABA8B25nkgeml513mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.59DDB38C.0139, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.199, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: c9ce9bb04e7955aa5610a0474d9edcd8 Archived-At: Subject: Re: [L2sm] R: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 06:00:51 -0000 --_000_B8F9A780D330094D99AF023C5877DABA9ABA8B25nkgeml513mbxchi_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 VGhhbmtzIEdpdXNlcHBlIGZvciB0aGUgcHJvcG9zZWQgY2hhbmdlLCB0aGlzIGlzIHdoYXQgSSB0 aG91Z2h0IGF0IHRoaXMgbW9tZW50IGFzIHdlbGwuDQoNCi1RaW4NCreivP7IyzogTDJzbSBbbWFp bHRvOmwyc20tYm91bmNlc0BpZXRmLm9yZ10gtPqx7SBGaW9jY29sYSBHaXVzZXBwZQ0Kt6LLzcqx vOQ6IDIwMTfE6jEw1MIyyNUgMjM6MTgNCsrVvP7IyzogQWlqdW4gV2FuZzsgbDNzbUBpZXRmLm9y ZzsgbDJzbUBpZXRmLm9yZw0K1vfM4jogW0wyc21dIFI6IFtMM3NtXSBVc2luZyBWUE4gdG8gb2Zm ZXIgZU1CQiwgVVJMTEMsIG1NVEMgc2VydmljZQ0KDQpIaSBBaWp1biwNClRoYXQgbG9va3MgbGlr ZSBhIHJlYXNvbmFibGUgcHJvcG9zYWwgdG8gbWUuIFRoZSBmaXJzdCB0aGluZyB3ZSBjYW4gZG8g aXMgdG8gYWRkIG5ldyBxb3MtcHJvZmlsZXMgZm9yIGVNQkIsIFVSTExDLCBtTVRDIHNlcnZpY2Vz IChzZWUgYmVsb3cpLg0KQWxzbyBzZXJ2aWNlLW9hbSAgY2FuIGJlIHVzZWZ1bCB0byB2ZXJpZnkg dGhlIHJlc291cmNlIGFsbG9jYXRpb24gYW5kIHRoZSBlbmQgdG8gZW5kIHBlcmZvcm1hbmNlLg0K U28sIG9mIGNvdXJzZSwgd2UgY2FuIHVzZSBWUE4gc2VydmljZSBtb2RlbCB0byBvZmZlciB0aGVz ZSBzZXJ2aWNlcyBhbmQsIHdlIGNhbiBjb25zaWRlciB0aGF0IHRoZSBzZXJ2aWNlIG9yY2hlc3Ry YXRvciBpcyByZXNwb25zaWJsZSBvZiB0aGUgbWFwcGluZyBiZXR3ZWVuIHNlcnZpY2UgY2hhcmFj dGVyaXN0aWNzIGFuZCBzbGljaW5nIGJ5IHVzaW5nIEwyU00uDQoNCkJlc3QgUmVnYXJkcywNCg0K R2l1c2VwcGUNCg0KDQogICAgaWRlbnRpdHkgY3VzdG9tZXItYXBwbGljYXRpb24gew0KDQogICAg IGRlc2NyaXB0aW9uDQoNCiAgICAgICJCYXNlIGlkZW50aXR5IGZvciBjdXN0b21lciBhcHBsaWNh dGlvbi4iOw0KDQogICAgfQ0KDQogICAgaWRlbnRpdHkgd2ViIHsNCg0KICAgICBiYXNlIGN1c3Rv bWVyLWFwcGxpY2F0aW9uOw0KDQogICAgIGRlc2NyaXB0aW9uDQoNCiAgICAgICJJZGVudGl0eSBm b3IgV2ViIGFwcGxpY2F0aW9uIChlLmcuLCBIVFRQLCBIVFRQUykuIjsNCg0KICAgIH0NCg0KICAg IGlkZW50aXR5IG1haWwgew0KDQogICAgIGJhc2UgY3VzdG9tZXItYXBwbGljYXRpb247DQoNCiAg ICAgZGVzY3JpcHRpb24NCg0KICAgICAgIklkZW50aXR5IGZvciBtYWlsIGFwcGxpY2F0aW9uLiI7 DQoNCiAgICB9DQoNCiAgICBpZGVudGl0eSBmaWxlLXRyYW5zZmVyIHsNCg0KICAgICBiYXNlIGN1 c3RvbWVyLWFwcGxpY2F0aW9uOw0KDQogICAgIGRlc2NyaXB0aW9uDQoNCiAgICAgICJJZGVudGl0 eSBmb3IgZmlsZSB0cmFuc2ZlciBhcHBsaWNhdGlvbiAoZS5nLiwgRlRQLCBTRlRQKS4iOw0KDQog ICAgfQ0KDQogICAgaWRlbnRpdHkgZW1iYiB7DQoNCiAgICAgYmFzZSBjdXN0b21lci1hcHBsaWNh dGlvbjsNCg0KICAgICBkZXNjcmlwdGlvbg0KDQogICAgIKGwSWRlbnRpdHkgZm9yIGVNQkIgYXBw bGljYXRpb247obE7DQoNCiAgICB9DQoNCiAgICBpZGVudGl0eSB1cmxsYyB7DQoNCiAgICAgYmFz ZSBjdXN0b21lci1hcHBsaWNhdGlvbjsNCg0KICAgICBkZXNjcmlwdGlvbg0KDQogICAgIKGwSWRl bnRpdHkgZm9yIFVSTExDIGFwcGxpY2F0aW9uO6GxOw0KDQogICAgIH0NCg0KICAgICBpZGVudGl0 eSBtbXRjIHsNCg0KICAgICAgYmFzZSBjdXN0b21lci1hcHBsaWNhdGlvbjsNCg0KICAgICAgZGVz Y3JpcHRpb24NCg0KICAgICAgobBJZGVudGl0eSBmb3IgbU1UQyBhcHBsaWNhdGlvbjuhsTsNCg0K ICAgICB9DQoNCg0KRGE6IEwzc20gW21haWx0bzpsM3NtLWJvdW5jZXNAaWV0Zi5vcmddIFBlciBj b250byBkaSBBaWp1biBXYW5nDQpJbnZpYXRvOiBzYWJhdG8gMzAgc2V0dGVtYnJlIDIwMTcgMDk6 NTINCkE6IGwzc21AaWV0Zi5vcmc8bWFpbHRvOmwzc21AaWV0Zi5vcmc+OyBsMnNtQGlldGYub3Jn PG1haWx0bzpsMnNtQGlldGYub3JnPg0KT2dnZXR0bzogW0wzc21dIFVzaW5nIFZQTiB0byBvZmZl ciBlTUJCLCBVUkxMQywgbU1UQyBzZXJ2aWNlDQoNCkhpLCBBbGw6DQpJUCBjb252ZXJnZW5jZSBp cyBjb250aW51aW5nIHRvIGRyaXZlIG5ldyBjbGFzc2VzIG9mIGRldmljZXMgdG8gYmVnaW4gY29t bXVuaWNhdGluZyB2aWEgSVAuICBFeGFtcGxlcyBvZiBzdWNoIGRldmljZXMgY291bGQgaW5jbHVk ZSBTVEIgYm94ZXMgZm9yIElQIHZpZGVvIGRpc3RyaWJ1dGlvbiwgY2VsbCB0b3dlciBlbGVjdHJv bmljcyAobWFjcm8gb3IgbWljcm8gY2VsbHMpLCBpbmZyYXN0cnVjdHVyZSBXaS1GaSBhY2Nlc3Mg cG9pbnRzLCBhbmQgZGV2aWNlcyBmb3IgbWFjaGluZS10by1tYWNoaW5lIChNMk0pIG9yIEludGVy bmV0IG9mIFRoaW5ncyAoSW9UKSBhcHBsaWNhdGlvbnMuDQpJbiBzb21lIGNhc2VzLCB0aGVzZSBj bGFzc2VzIG9mIGRldmljZXMgcmVwcmVzZW50IGEgdmVyeSBsYXJnZSBkZXBsb3ltZW50IGJhc2Us IG9uIHRoZSBvcmRlciBvZiB0aG91c2FuZHMgb3IgZXZlbiBtaWxsaW9ucyBvZiBkZXZpY2VzIG5l dHdvcmstd2lkZS4gSW4gNUcgc2xpY2luZyBjYXNlLCB0aHJlZSB0eXBpY2FsIHNlcnZpY2VzIG9m ZmVyZWQgdG8gdGhlc2UgZGV2aWNlcyBhcmUNCjEuIEVuaGFuY2VkIE1vYmlsZSBCcm9hZGJhbmQo ZU1CQikNCjIuIFVsdHJhLVJlbGlhYmxlIGFuZCBMb3cgTGFudGVuY3kgQ29tbXVuaWNhdGlvbiAo VVJMTEMpDQozLiBNYXNzaXZlIE1hY2hpbmUgVHlwZSBDb21tdW5pY2F0aW9ucyAobU1UQykNClRo ZXNlIHNlcnZpY2VzIGRlbWFuZCB0aGUgbmV0d29yayBwZXJmb3JtYW5jZSB3aXRoIHdpZGUgdmFy aWV0eSBvZiBjaGFyYWN0ZXJpc3RpY3Mgc3VjaCBhcyBkYXRhIHJhdGUsIGxhdGVuY3ksIGxvc3Mg cmF0ZSwgcmVsaWFiaWxpdHkgYW5kIG1hbnkgb3RoZXIgcGFyYW1ldGVycy4NCk15IHF1ZXN0aW9u IGlzIHRoZSBmb2xsb3dpbmdzOg0KDQoxLiAgICAgICBDYW4gd2UgdXNlIFZQTiBzZXJ2aWNlIG1v ZGVsIHRvIG9mZmVyIHN1Y2gga2luZCBvZiBuZXcgc2VydmljZXMgdG8gY3VzdG9tZXJzPw0KDQoy LiAgICAgICBTaG91bGQgd2UgZGVmaW5lIG5ldyBzZXJ2aWNlcyBjaGFyYWN0ZXJpc3RpYyB0aGF0 IGlzIGJhc2VkIG9uIHRoZSBuZXcgc2xpY2luZyBjYXBhYmlsaXRpZXMgcHJvdmlkZWQgYnkgbmV0 d29yayBkZXZpY2VzPw0KDQoNCkJlc3QgUmVnYXJkcy4NCg0KQWlqdW4gV2FuZw0KTmV0d29yayBS JkQgYW5kIE9wZXJhdGlvbiBTdXBwb3J0IERlcGFydG1lbnQNCkNoaW5hIFRlbGVjb20gQ29ycG9y YXRpb24gTGltaXRlZCBCZWlqaW5nIFJlc2VhcmNoIEluc3RpdHV0ZSxCZWlqaW5nLCBDaGluYS4N Cg0KDQoNClF1ZXN0byBtZXNzYWdnaW8gZSBpIHN1b2kgYWxsZWdhdGkgc29ubyBpbmRpcml6emF0 aSBlc2NsdXNpdmFtZW50ZSBhbGxlIHBlcnNvbmUgaW5kaWNhdGUuIExhIGRpZmZ1c2lvbmUsIGNv cGlhIG8gcXVhbHNpYXNpIGFsdHJhIGF6aW9uZSBkZXJpdmFudGUgZGFsbGEgY29ub3NjZW56YSBk aSBxdWVzdGUgaW5mb3JtYXppb25pIHNvbm8gcmlnb3Jvc2FtZW50ZSB2aWV0YXRlLiBRdWFsb3Jh IGFiYmlhdGUgcmljZXZ1dG8gcXVlc3RvIGRvY3VtZW50byBwZXIgZXJyb3JlIHNpZXRlIGNvcnRl c2VtZW50ZSBwcmVnYXRpIGRpIGRhcm5lIGltbWVkaWF0YSBjb211bmljYXppb25lIGFsIG1pdHRl bnRlIGUgZGkgcHJvdnZlZGVyZSBhbGxhIHN1YSBkaXN0cnV6aW9uZSwgR3JhemllLg0KDQpUaGlz IGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGlzIGNvbmZpZGVudGlhbCBhbmQgbWF5IGNvbnRh aW4gcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiBpbnRlbmRlZCBmb3IgdGhlIGFkZHJlc3NlZShzKSBv bmx5LiBEaXNzZW1pbmF0aW9uLCBjb3B5aW5nLCBwcmludGluZyBvciB1c2UgYnkgYW55Ym9keSBl bHNlIGlzIHVuYXV0aG9yaXNlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVu dCwgcGxlYXNlIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50cyBhbmQgYWR2 aXNlIHRoZSBzZW5kZXIgYnkgcmV0dXJuIGUtbWFpbCwgVGhhbmtzLg0KDQpSaXNwZXR0YSBsJ2Ft YmllbnRlLiBOb24gc3RhbXBhcmUgcXVlc3RhIG1haWwgc2Ugbm9uIKioIG5lY2Vzc2FyaW8uDQoN Cg0K --_000_B8F9A780D330094D99AF023C5877DABA9ABA8B25nkgeml513mbxchi_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Thanks = Giuseppe for the proposed change, this is what I thought at this moment as = well.

&n= bsp;

-Qin

=B7=A2=BC=FE=C8=CB: L2sm [mailto:l2sm-bounces@ietf.org] =B4=FA=B1=ED = Fioccola Giuseppe
=B7=A2=CB=CD= =CA=B1=BC=E4: 2017=C4=EA10=D4=C2= 2=C8=D5 23:18
=CA=D5=BC=FE=C8=CB: Aijun Wang; l3sm@ietf.org; l2sm@ietf.org
=D6=F7=CC=E2: [L2sm] R: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service<= /span>

 

Hi Aijun,

That looks like a reasonable proposal to me. The first thing we c= an do is to add new qos-profiles for eMBB, URLLC, mMTC services (see below)= .

Also service-oam  can be useful to verify the resource alloc= ation and the end to end performance.

So, of course, we can use VPN service model to offer these servic= es 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-applicatio=
n {
     description
      "Base ident=
ity for customer application.";=

    }
    identity web {
     base customer-applicat=
ion;
     description
      "Identity f=
or Web application (e.g., HTTP, HTTPS).";<=
o:p>
    }
    identity mail {
     base customer-applicat=
ion;
     description
      "Identity f=
or mail application.";

    }


    identity file-transfer {


     base customer-applicat=
ion;


     description


      "Identity f=
or file transfer application (e.g., FTP, SFTP).";


    }


    identity embb {


     base custome=
r-application;


     description<=
/span>


     =A1=B0Identity=
 for eMBB application;=A1=B1;

    }


    identity urllc {


     base custome=
r-application;


     description<=
/span>


     =A1=B0Identity=
 for URLLC application;=A1=B1;<=
/pre>

     }


     identity mmt=
c {


      base c=
ustomer-application;


      descri=
ption


      =A1=B0=
Id=
entity for mMTC application;=A1=B1;


     }


 


 






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 to=
wer 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(eM=
BB)


2. Ultra-Reliable and Low Lante=
ncy Communication (URLLC)


3. Massive Machine Type Communi=
cations (mMTC)


These services demand the netwo=
rk performance with wide variety of characteristics such as data rate, late=
ncy, loss rate, reliability and many other parameters.

My question is the followings:<=
o:p>



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




2=
.   &=
nbsp;  
Should we define new se=
rvices characteristic that is based on the new slicing capabilities provide=
d by network devices?



 


 


Best Regards.=



 


Aijun Wang

Network R&D and Operation S=
upport Department


China Telecom Corporation Limit=
ed Beijing Research Institute,Beijing, China.


 


 


 








Questo messag=
gio 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. Qualor=
a abbiate ricevuto questo documento per errore siete cortesemente pregati d=
i darne immediata comunicazione al mittente e di provvedere alla sua distru=
zione, Grazie.




This e-mail and any attachments is confidential and may contain privileg=
ed information intended for the addressee(s) only. Dissemination, copying, =
printing or use by anybody else is unauthorised. If you are not the intende=
d 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 =A8=A8 necessario.<=
/b> 








 
--_000_B8F9A780D330094D99AF023C5877DABA9ABA8B25nkgeml513mbxchi_-- From nobody Wed Oct 11 05:40:50 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4FE134305 for ; Wed, 11 Oct 2017 05:40:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.08 X-Spam-Level: X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 auSxdBLQFpJT for ; Wed, 11 Oct 2017 05:40:47 -0700 (PDT) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4416513430A for ; Wed, 11 Oct 2017 05:40:45 -0700 (PDT) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9BCegB4006806 for ; Wed, 11 Oct 2017 13:40:43 +0100 Received: from 950129200 (62.192.112.87.dyn.plus.net [87.112.192.62]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9BCefJI006775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 11 Oct 2017 13:40:42 +0100 Reply-To: From: "Adrian Farrel" To: Date: Wed, 11 Oct 2017 13:40:43 +0100 Message-ID: <05ab01d3428e$27cfdec0$776f9c40$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdNCjbeq+p5xnUrfQcau7I8eVts+OQ== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23386.006 X-TM-AS-Result: No--2.841-10.0-31-10 X-imss-scan-details: No--2.841-10.0-31-10 X-TMASE-MatchedRID: tcF3I8fd45garBIr98KMDqDH6drx3JPVOhJ9m53n4aC7+NPPxj+R6gOR 3tZA0vji4vM1YF6AJbZcLc3sLtjOt7bmZosI/5Zy3QfwsVk0UbuGrPnef/I+evTCZDzmvFbXB69 F3D4Yb+wCcTs8LdHbfihsjASgWAEpSyDzDHRrD92vcsTuUejg0omQ2vqumwAFVUH85vIcwrl2A/ 3Nl4P8kQ== Archived-At: Subject: [L2sm] LAG and loop avoidance X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 12:40:48 -0000 Hi WG, We had an action item to look at loop avoidance especially with regard to LAGs. The interim discussed this and decided that everything is covered in the existing module. Please speak up now if you still have an issue with this. Otherwise we'll move on. Thanks, Adrian From nobody Wed Oct 11 06:02:49 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C53913318B for ; Wed, 11 Oct 2017 06:02:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.08 X-Spam-Level: X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 JfnDaTYwV77h for ; Wed, 11 Oct 2017 06:02:43 -0700 (PDT) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E260513430F for ; Wed, 11 Oct 2017 06:02:39 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9BD2b2r012465 for ; Wed, 11 Oct 2017 14:02:37 +0100 Received: from 950129200 (62.192.112.87.dyn.plus.net [87.112.192.62]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v9BD2aMv012442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 11 Oct 2017 14:02:37 +0100 Reply-To: From: "Adrian Farrel" To: Date: Wed, 11 Oct 2017 14:02:38 +0100 Message-ID: <05b801d34291$37876e70$a6964b50$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdNCkSmpJ7cPChOgSN2ry5YAuT50cQ== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23386.006 X-TM-AS-Result: No--7.026-10.0-31-10 X-imss-scan-details: No--7.026-10.0-31-10 X-TMASE-MatchedRID: aQCt577mlyRkgQopOf2aEtOEZs/2oH3cW9oi9MZ8/xLvxSNLwtVQB00B k5DM7WKlpzaCfOWoVYptkfvwyItc5S9FtW7XfHueq1ZJZ2z+SbascK/K2DlvjhahL68yPcDbOex 2qLEoLQYjypnGhZoY9YdziXCvHmFESSOWVJeuO1A5f9Xw/xqKXVsKO+9Zlb5Jxq9PbUOwsP9QSF bL1bvQASAHAopEd76v/J6QUQ6MgenKQWrlQuoIgDLHNZLD/CklamwyQ1cv1ip85DxNPaUO5Q== Archived-At: Subject: [L2sm] Support of and interworking with legacy L2VPN types X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 13:02:44 -0000 Another issue on our list was whether we should support legacy VPN services like ATMoMPLS, PPPoMPLS, and FRoMPLS. At the interim we decided that while there is a lot of legacy deployment, there are also four things to consider: 1. Legacy deployments are, erm, already deployed. They are static and don't need more work for operational commissioning. 2. New deployments of legacy services are very, very rare. 3. Migration to new L2VPN services does happen, but is covered by the existing module. 4. Interworking between legacy and new services is something so unusual that we should not work on it. As a result we determined to not support any form of ATM PVC. Again, please shout if you have an issue with this. Thanks, Adrian From nobody Fri Oct 20 17:26:42 2017 Return-Path: X-Original-To: l2sm@ietf.org Delivered-To: l2sm@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FEDD1344BE; Fri, 20 Oct 2017 17:24:17 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: bclaise@cisco.com, l2sm@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150854545764.20809.9774722462996826153.idtracker@ietfa.amsl.com> Date: Fri, 20 Oct 2017 17:24:17 -0700 Archived-At: Subject: [L2sm] l2sm - Requested session has been scheduled for IETF 100 X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2017 00:24:18 -0000 Dear Adrian Farrel, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. l2sm Session 1 (1:00:00) Thursday, Afternoon Session III 1810-1910 Room Name: Canning size: 250 --------------------------------------------- Request Information: --------------------------------------------------------- Working Group Name: L2VPN Service Model Area Name: Operations and Management Area Session Requester: Adrian Farrel Number of Sessions: 1 Length of Session(s): 1 Hour Number of Attendees: 50 Conflicts to Avoid: First Priority: netmod teas pce opsawg mpls bess spring Second Priority: i2rs pals lime Third Priority: rtgarea rtgwg People who must be present: Adrian Farrel Benoit Claise Qin Wu Resources Requested: Special Requests: --------------------------------------------------------- From nobody Mon Oct 30 08:05:32 2017 Return-Path: X-Original-To: l2sm@ietf.org Delivered-To: l2sm@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD5C13FA44; Mon, 30 Oct 2017 08:05:24 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: l2sm@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.63.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <150937592459.3389.9546012941839243384@ietfa.amsl.com> Date: Mon, 30 Oct 2017 08:05:24 -0700 Archived-At: Subject: [L2sm] I-D Action: draft-ietf-l2sm-l2vpn-service-model-04.txt X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 15:05:25 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the L2VPN Service Model WG of the IETF. Title : A YANG Data Model for L2VPN Service Delivery Authors : Bin Wen Giuseppe Fioccola Chongfeng Xie Luay Jalil Filename : draft-ietf-l2sm-l2vpn-service-model-04.txt Pages : 162 Date : 2017-10-30 Abstract: This document defines a YANG data model that can be used to configure a Layer 2 Provider Provisioned VPN service. This model is intended to be instantiated at management system to deliver the overall service. This model is not a configuration model to be used directly on network elements, but provides an abstracted view of the Layer 2 VPN service configuration components. It is up to a management system to take this as an input and generate specific configurations models to configure the different network elements to deliver the service. How configuration of network elements is done is out of scope of the document. The data model in this document includes support for point-to-point Virtual Private Wire Services (VPWS) and multipoint Virtual Private LAN services (VPLS) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFC4761 and RFC6624. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-l2sm-l2vpn-service-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-l2sm-l2vpn-service-model-04 https://datatracker.ietf.org/doc/html/draft-ietf-l2sm-l2vpn-service-model-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-l2sm-l2vpn-service-model-04 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Oct 30 08:16:46 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D9A113FA38; Mon, 30 Oct 2017 08:16:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.62 X-Spam-Level: X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 R_oOIdynn9c4; Mon, 30 Oct 2017 08:16:42 -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 6E1C213FA42; Mon, 30 Oct 2017 08:15:43 -0700 (PDT) X-AuditID: d9a97916-059ff7000000b3a3-b9-59f7421cd637 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 50.6E.45987.C1247F95; Mon, 30 Oct 2017 16:15:40 +0100 (CET) From: Fioccola Giuseppe To: "l2sm@ietf.org" CC: "l2sm-chairs@ietf.org" , "draft-ietf-l2sm-l2vpn-service-model@ietf.org" Thread-Topic: [L2sm] I-D Action: draft-ietf-l2sm-l2vpn-service-model-04.txt Thread-Index: AQHTUZCHRauAUNng0kS8ShKbCxUbbqL8fpdA Date: Mon, 30 Oct 2017 15:15:39 +0000 Message-ID: <2cc80a85392c4949a982a10f30fd30e6@TELMBXB02RM001.telecomitalia.local> References: <150937592459.3389.9546012941839243384@ietfa.amsl.com> In-Reply-To: <150937592459.3389.9546012941839243384@ietfa.amsl.com> 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.248] x-ti-disclaimer: Disclaimer1 Content-Type: text/plain; charset="iso-8859-1" content-transfer-encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrIKsWRmVeSWpSXmKPExsXCxfdHWlfG6Xukwcw7qhY9jxuZLB7svMhm ceflS0YHZo8lS34yBTBGNTDaJObl5ZcklqQqpKQWJ9squWQWJ+ckZuamFimEpOakJufnKilk ptgqGSspFOQkJqfmpuaV2ColFhSk5qUo2XEpYAAboLLMPIXUvOT8lMy8dFslz2B/XQsLU0td QyW7wNLU4pJ8hdzU4uLE9PTMfIXUhPWCGY9PPmUs2CZTcbF5PWMDY7NYFyMnh4SAiUTjvrNs XYxcHEICU5gkjjY9ZgZJsAnYSBx8dYINxBYRUJbY+qyDFcRmFpjCKLH9hAWILSzgKXH1zykW iBpviS9zTzJB2EYSU75OYgSxWQRUJaa0nwabySsQKLHq1DWwOUICThIPGlexg9icAs4Sa9Z9 AtvFKCArMWH3IkaIXeISL6afYIc4VEBiyZ7zzBC2qMTLx/9YIWwDia1L97FA2IoSk1b8hqqX kVh4ZDLUzXoSN6ZOYYOwtSWWLXwNdY+gxMmZT1gmMIrNQrJuFpKWWUhaZiFpWcDIsopRNLfC wEivBBJ/mSWJOZmJepklmxiB6eLmykqxHYyta50PMQpwMCrx8B5y+B4pxJpYVlyZe4hRgoNZ SYR3sQlQiDclsbIqtSg/vqg0J7X4EKMPMMQmMkuJJucDU1leSbyhiYWlobGFhZGhhZkpDmEl cV5za6BZAunABJadmlqQWgQzjomDU6qB0Tt9VY/85ry+hx/2Xb9pMvFf1VGbWLflrSsDMvPE dnzwD7janCDK+OhZ68Sk54Ue3DtenKw3LPl8gWuf0JcEfQ7Zae6eXZ3p3zQuTPSb0dfj+uDl P/8Chz3BimoF17LX7yh2s1Xn1TQQe8SqZd+We2TLxm9vG7Qd474aSm++xSKywn19sfFjJZbi jERDLeai4kQA5XnMREQDAAA= Archived-At: Subject: [L2sm] I: I-D Action: draft-ietf-l2sm-l2vpn-service-model-04.txt X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2017 15:16:44 -0000 Hi All, This is the new version of the draft-ietf-l2sm-l2vpn-service-model. The most significant changes v-(04) were agreed during the interim meeting a= nd include: o Remove EVC and OVC related attributes. o Remove Metro-Network related attributes. o Remove Customer Account Number attributes. o Update L2VPN service Types. o Remove load balancing options since access-priority within availability can be used to support load balancing. o Remove service protection attribute since we have site diversity attributes. o Move SVC-MTU to service level. o Move CVLAN to Service Mapping to Network Access Level. o Add two new parameters under qos-classification-policy. o Remove Security Container. o Remove IPv4/IPv6 prefix filter from VPN policy. o Add Delivery mode support at service level. We can discuss them during IETF100 meeting. Reviews and Comments are always welcome. Best Regards, Giuseppe -----Messaggio originale----- Da: L2sm [mailto:l2sm-bounces@ietf.org] Per conto di internet-drafts@ietf.or= g Inviato: luned=EC 30 ottobre 2017 16:05 A: i-d-announce@ietf.org Cc: l2sm@ietf.org Oggetto: [L2sm] I-D Action: draft-ietf-l2sm-l2vpn-service-model-04.txt A New Internet-Draft is available from the on-line Internet-Drafts directori= es. This draft is a work item of the L2VPN Service Model WG of the IETF. Title : A YANG Data Model for L2VPN Service Delivery Authors : Bin Wen Giuseppe Fioccola Chongfeng Xie Luay Jalil Filename : draft-ietf-l2sm-l2vpn-service-model-04.txt Pages : 162 Date : 2017-10-30 Abstract: This document defines a YANG data model that can be used to configure a Layer 2 Provider Provisioned VPN service. This model is intended to be instantiated at management system to deliver the overall service. This model is not a configuration model to be used directly on network elements, but provides an abstracted view of the Layer 2 VPN service configuration components. It is up to a management system to take this as an input and generate specific configurations models to configure the different network elements to deliver the service. How configuration of network elements is done is out of scope of the document. The data model in this document includes support for point-to-point Virtual Private Wire Services (VPWS) and multipoint Virtual Private LAN services (VPLS) that use Pseudowires signaled using the Label Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as described in RFC4761 and RFC6624. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-l2sm-l2vpn-service-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-l2sm-l2vpn-service-model-04 https://datatracker.ietf.org/doc/html/draft-ietf-l2sm-l2vpn-service-model-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-l2sm-l2vpn-service-model-04 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ L2sm mailing list L2sm@ietf.org https://www.ietf.org/mailman/listinfo/l2sm Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle pers= one indicate. La diffusione, copia o qualsiasi altra azione derivante dalla= conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbia= te ricevuto questo documento per errore siete cortesemente pregati di darne= immediata comunicazione al mittente e di provvedere alla sua distruzione, G= razie. This e-mail and any attachments is confidential and may contain privileged i= nformation intended for the addressee(s) only. Dissemination, copying, print= ing or use by anybody else is unauthorised. If you are not the intended reci= pient, 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 =E8 necessario.