Re: [L2sm] Proposed Liaison to 3GPP SA5
"Adrian Farrel" <adrian@olddog.co.uk> Tue, 05 June 2018 15:58 UTC
Return-Path: <adrian@olddog.co.uk>
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 0C5D0130FA0 for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 08:58:18 -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, 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 e_dUYCLeSs-Z for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 08:58:15 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 CA8E11310F0 for <l2sm@ietf.org>; Tue, 5 Jun 2018 08:58:14 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id w55FwCaD003966; Tue, 5 Jun 2018 16:58:12 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 83D982204A; Tue, 5 Jun 2018 16:58:12 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS id 771DF22044; Tue, 5 Jun 2018 16:58:12 +0100 (BST)
Received: from 950129200 (243.125.113.87.dyn.plus.net [87.113.125.243]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id w55FwAMV027515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jun 2018 16:58:11 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Fioccola Giuseppe' <giuseppe.fioccola@telecomitalia.it>, l2sm@ietf.org
References: <000901d3fbf5$5648d790$02da86b0$@olddog.co.uk> <7ee2d1342bf6403583d834a1ae3f2d7d@TELMBXB02RM001.telecomitalia.local>
In-Reply-To: <7ee2d1342bf6403583d834a1ae3f2d7d@TELMBXB02RM001.telecomitalia.local>
Date: Tue, 05 Jun 2018 16:58:08 +0100
Message-ID: <01a901d3fce6$00486b20$00d94160$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIOf7qJKx24xl1w/pQ68zsvGbGRtQGs1yWjo89lufA=
Content-Language: en-gb
X-Originating-IP: 87.113.125.243
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-23888.007
X-TM-AS-Result: No--46.855-10.0-31-10
X-imss-scan-details: No--46.855-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-23888.007
X-TMASE-Result: 10--46.854800-10.000000
X-TMASE-MatchedRID: j4nUk6F+aLbMy6K24fisq/HkpkyUphL9t7k6BDMlB1ijlTkwAs5yyded muI9uycYD7mBlq0ezI+o1ACkZzz9VnKzRQDC+n78e2JNgZ9m9T8qrNBE8+zJq0jy8BQTPSF88E1 v7ObMQJvX5X1jP2IVCAp6fqYy9fWaX1yU8dnnJNwFJG8ZmXyKdbebfccgl9iNNwCgQD6pGqYDh5 XrP5wcJ2a0P9zJS9tFmfvwB1x0rl+c2HPYlfRwpuYAh37ZsBDCF4q8hdmZvAhrZC+UxQMOqKOTp rZ30wpIk09tFkQDYUXzWv/Qt+jWIW2Dlh1/RdbgcFEiuPxHjsWYhghbAKu1sBHfiujuTbedstVa mtuFXpn8pMfKP0wTAj71V2NMK439/rLeCVcPyeDwI5EzJETTVBxCcOlDoVfTWltirZ/iPP7hLW+ nuKkjlu5f+SbQ7VhgchJq6fFfv/NjKiftO/PwVZugzdh7v5Niml8OOrQdlPprZQ+zWanMHKpap5 GN867VmRqgu0yNlauJeEU0cKHknEpT9y5eApOQFA2AInDSWYU0tADHYicNMmfF0QmF+vyMgfHaC nKqbi3TZovCU1n1c7KIFE/99KIgYP+rVJqzTJIxPk7GkYCla2LrYrObib8f62LiMTSipzPZcEY7 ZH0iUnGTbL5t8BjXlm4KTdLupFJNlZ1zEcyAYziU1nXLlwv+kLrDv6wzGo/o1+KnG60kJ+Pp9KJ VfkC/w1Q12m9I+XH+CyE/HHLseox1g1lTiexdOxRDwnJbD3OJfoBeqIJIU71R1DzR0wGuo8WMkQ Wv6iW4mGhlpKkDnlZFWWuOwo7w3QfwsVk0Ubv+efAnnZBiLyF6bSSak9kx
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/1Jm_pmWdgh66ErU0vbEf3-Ga_zk>
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:58:19 -0000
Yes, good point. A > -----Original Message----- > From: Fioccola Giuseppe [mailto:giuseppe.fioccola@telecomitalia.it] > Sent: 05 June 2018 16:01 > To: adrian@olddog.co.uk; l2sm@ietf.org > Subject: RE: [L2sm] Proposed Liaison to 3GPP SA5 > > 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.
- [L2sm] Proposed Liaison to 3GPP SA5 Adrian Farrel
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Fioccola Giuseppe
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Adrian Farrel
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Roque Gagliano (rogaglia)
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Adrian Farrel
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Roque Gagliano (rogaglia)
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Adrian Farrel
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Roque Gagliano (rogaglia)
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Adrian Farrel
- Re: [L2sm] Proposed Liaison to 3GPP SA5 Roque Gagliano (rogaglia)