Re: [L2sm] Proposed Liaison to 3GPP SA5

Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it> Tue, 05 June 2018 15:01 UTC

Return-Path: <giuseppe.fioccola@telecomitalia.it>
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 9C3631310CC for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 08:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7ideXA28jEoI for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 08:01:09 -0700 (PDT)
Received: from mx01.telecomitalia.it (mx01.telecomitalia.it [217.169.121.10]) (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 2F1951310CA for <l2sm@ietf.org>; Tue, 5 Jun 2018 08:01:08 -0700 (PDT)
X-AuditID: d9a9790a-1a9ff700000010b3-c0-5b16a5b35256
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 mx01.telecomitalia.it () with SMTP id 0E.99.04275.3B5A61B5; Tue, 5 Jun 2018 17:01:07 +0200 (CEST)
From: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "l2sm@ietf.org" <l2sm@ietf.org>
Thread-Topic: [L2sm] Proposed Liaison to 3GPP SA5
Thread-Index: AdP77mZy+ziBQucgTuOCdr0I0+8PugABou9AADovkiA=
Date: Tue, 5 Jun 2018 15:01:06 +0000
Message-ID: <7ee2d1342bf6403583d834a1ae3f2d7d@TELMBXB02RM001.telecomitalia.local>
References: <000901d3fbf5$5648d790$02da86b0$@olddog.co.uk>
In-Reply-To: <000901d3fbf5$5648d790$02da86b0$@olddog.co.uk>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.14.252.230]
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+NgFlrMKsWRmVeSWpSXmKPExsXCxfdHWnfzUrFog+9z+C1+9Nxgtrjz8iWj A5PHkiU/mTxWbF7JGMAU1cBok5iXl1+SWJKqkJJanGyr5JJZnJyTmJmbWqQQkpqTmpyfq6SQ mWKrZKykUJCTmJyam5pXYquUWFCQmpeiZMelgAFsgMoy8xRS85LzUzLz0m2VPIP9dS0sTC11 DZXsAktTi0vyFXJTi4sT09Mz8xVSE9YLZnzfv5K5YJ5UxcO5R9kbGC+KdjFyckgImEh8enGc rYuRi0NIYCqTxLbJx5lAEmwCNhIHX51gA7FFBIIknrTuYu9i5OAQFjCQeP9DGyJsKLHn5SZW kLCIgJXEinNmIGEWARWJI4efMIPYvAKBEjvvfmUFsYWASp73LGYEsTkFrCUu3GkDm84oICsx YfcisDizgLjErSfzmSBOE5BYsuc8M4QtKvHy8T9WCNtAYuvSfSwQtqLE3h8HoGpkJBYemcwK MUdP4sbUKWwQtrbEsoWvoe4RlDg58wnLBEbRWUjWzULSMgtJyywkLQsYWVYxiuZWGBjqlUBi LLMkMSczUS+zZBMjMCXcXFnJtYPx9SrnQ4wCHIxKPLyhM8SihVgTy4orcw8xSnAwK4nwTp8M FOJNSaysSi3Kjy8qzUktPsToAwyxicxSosn5wHSVVxJvaGJhaWhsYWFkaGFmikNYSZw3bhHQ LIF0YJLKTk0tSC2CGcfEwSnVwGh3xPb0gV9yS12KRKakfQx6xsIk9UEqaM133p7qc/0t06U0 /ydzr7rHPeXTHQGp9yciljSs2LC2nL/4k//HWe1RrPe6MpnaDYQ+X5n4xJ19lvelG0FHnv2Y ZSyj9VXaPSltXpfL2r/pmc+Ewi5efCBQ+7GSgYvNoOtLyNqs3SInooMutJ1MZVFiKc5INNRi LipOBAAkbF1uNgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/QEQEUTa-3Ow3mFFL91TpKC7bjS0>
Subject: Re: [L2sm] Proposed Liaison to 3GPP SA5
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2018 15:01:12 -0000

Hi Adrian, All,
I absolutely agree with the proposed Liaison to 3GPP SA5. I would also suggest to mention RFC8199 on YANG Module Classification.

Best Regards,

Giuseppe

-----Original Message-----
From: L2sm [mailto:l2sm-bounces@ietf.org] On Behalf Of Adrian Farrel
Sent: lunedì 4 giugno 2018 13:15
To: l2sm@ietf.org
Subject: [L2sm] Proposed Liaison to 3GPP SA5

Hi WG,

3GPP SA5 is working on Management and orchestration of 5G networks and network slicing (http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G) and is considering various existing data models as references. 3GPP Release-15 is targeting freeze date of September 2018 and plan two meetings in June and August respectively to meet the deadline of 3GPP Release-15.
 
They seem to have been soliciting input from various SDOs (most recently the BBF) but have not approached the IETF. This may be because they already know what we are working on, or it may be because they didn't realise.

So Qin and I propose to send the following liaison statement to them for information. Since the next meeting is on June 26th, we think the deadline for sending this is should be June 15th.

Any comments or edits would be welcomed.

Thanks for any input or advice.

Qin and Adrian

=== Draft LS ===

To: 3GPP SA5
Cc: Thomas Tovinger, 3GPP SA5 Chairman
       Ignas Bagdonas and Warren Kumari, IETF Operations and Management ADs
From: Qin Wu and Adrian Farrel, IETF L2SM working group co-chairs
For: Information

We note that 3GPP SA5 is working on Management and orchestration of 5G networks and network slicing (http://www.3gpp.org/NEWS-EVENTS/3GPP-NEWS/1951-SA5_5G) and is considering various existing data models as references. 3GPP Release-15 is targeting freeze date of September 2018 and plan two meetings in June and August respectively to meet the deadline of 3GPP Release-15. We would like to take this opportunity to inform you of the status of several pieces of work in the IETF that satisfy the transport support for network slicing on IP services , L2 service, and TE service.

RFC 8299 provides A YANG Data Model for L3VPN Service Delivery.
This document is a published RFC with IETF consensus.
https://www.rfc-editor.org/rfc/rfc8299.txt
 
draft-ietf-l2sm-l2vpn-service-model provides A YANG Data Model for L2VPN Service Delivery.
This document has achieved working group and IETF consensus, and is currently completing approval for publication as an RFC.
https://www.ietf.org/id/draft-ietf-l2sm-l2vpn-service-model-10.txt
 
RFC 8309 sets the previous two documents in context by explaining what the IETF means by the term "Service Model"
https://www.rfc-editor.org/rfc/rfc8309.txt
 
You may also be interested in work in the TEAS working group on Abstraction and Control of Traffic Engineered networks (ACTN).
In particular, there is YANG model for Virtual Network operation in an ACTN context that may be of specific interest to you:
https://www.ietf.org/id/draft-ietf-teas-actn-vn-yang-00.txt
 
Wishing you all success in your work,
Qin Wu and Adrian Farrel
Co-chairs, IETF L2SM working group
===END===

_______________________________________________
L2sm mailing list
L2sm@ietf.org
https://www.ietf.org/mailman/listinfo/l2sm

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.