Re: [L2sm] Proposed Liaison to 3GPP SA5

"Roque Gagliano (rogaglia)" <rogaglia@cisco.com> Tue, 05 June 2018 17:42 UTC

Return-Path: <rogaglia@cisco.com>
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 9B5071310EC for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 10:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 vQ-to4eVlG6P for <l2sm@ietfa.amsl.com>; Tue, 5 Jun 2018 10:42:05 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC4F9127333 for <l2sm@ietf.org>; Tue, 5 Jun 2018 10:42:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12226; q=dns/txt; s=iport; t=1528220524; x=1529430124; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=DdLFNrsYp/aUGr9X0diUWDGty0P6JPBeqmhIgKaLVDk=; b=WXCQ7NOmF1VbBh0DGbK204SrPftmdUNuIHGiiHHq/awXLkbWjYaDH4RR ZlRwXzYCKAvxsV6WBs/e5RLW/0TO/skjmq9Q53PRbIdvitZV006iJzwHM I8H37XdCow1ucppz9hSBceUOoSDp7TzmlbCemxnbwVNg9CRvgbZtCKXdt A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DFAAD+yhZb/5NdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYMVLmJ/KAqDbogEjG+BWCF1k1aBeAsYC4FUgnUCF4IJITQ?= =?us-ascii?q?YAQIBAQEBAQECbBwMhSgBAQEEAQEhEToXBAIBCBEBAwEBAQICIwMCAgIlCxQ?= =?us-ascii?q?BAgYIAgQBEhQGgwgCgX8PpzmCHIRYg2iBaIELhjKBBYFUPyVqJAyBXkkHLoM?= =?us-ascii?q?RAQGBQAEBHhcVglQwgiQChy4kkRwJAoZaiAeBPIN4h2aQeAIREwGBJB04gVJ?= =?us-ascii?q?wFTsqAYIYCYsHhT5vAY0JgR+BGQEB?=
X-IronPort-AV: E=Sophos;i="5.49,479,1520899200"; d="scan'208";a="124964388"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Jun 2018 17:41:49 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w55HfnR2004796 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 5 Jun 2018 17:41:49 GMT
Received: from xch-rtp-011.cisco.com (64.101.220.151) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 5 Jun 2018 13:41:48 -0400
Received: from xch-rtp-011.cisco.com ([64.101.220.151]) by XCH-RTP-011.cisco.com ([64.101.220.151]) with mapi id 15.00.1320.000; Tue, 5 Jun 2018 13:41:48 -0400
From: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
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+8PugABou9AADovkiAACnVnAAAFuTuA///tvQCAACL1gA==
Date: Tue, 5 Jun 2018 17:41:48 +0000
Message-ID: <D14DDD23-258C-4839-9CF8-4A9E989878F9@cisco.com>
References: <000901d3fbf5$5648d790$02da86b0$@olddog.co.uk> <7ee2d1342bf6403583d834a1ae3f2d7d@TELMBXB02RM001.telecomitalia.local> <01a901d3fce6$00486b20$00d94160$@olddog.co.uk> <2717B04F-A52D-4F07-BCD6-54672978429E@cisco.com> <01c401d3fcf3$c389b230$4a9d1690$@olddog.co.uk>
In-Reply-To: <01c401d3fcf3$c389b230$4a9d1690$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.172.246]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8ECC1F569600A94EBE2AC98AEEAA2ECB@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/wq5JkUV_O-0gJyBurSXQF8kPmzc>
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 17:42:09 -0000

Hi Adrian,

The definition of IETF informational models can be found in RFC 2026 section 4.2.2:

--------
4.2.2  Informational

   An "Informational" specification is published for the general
   information of the Internet community, and does not represent an
   Internet community consensus or recommendation.  The Informational
   designation is intended to provide for the timely publication of a
   very broad range of responsible informational documents from many
   sources, subject only to editorial considerations and to verification
   that there has been adequate coordination with the standards process
   (see section 4.2.3).

   Specifications that have been prepared outside of the Internet
   community and are not incorporated into the Internet Standards
   Process by any of the provisions of section 10 may be published as
   Informational RFCs, with the permission of the owner and the
   concurrence of the RFC Editor.
--------

That is my point, you can't call it consensus as the purpuse of an informational model is not to reach consensus.

Roque

On 05/06/18 19:36, "Adrian Farrel" <adrian@olddog.co.uk>; wrote:

    Hi Roque,
    
    Well, both documents went through IETF last call, and both 8309 and 8199 have IETF consensus. As it says in the boilerplate for both documents.
    
       This document is a product of the Internet Engineering Task Force
       (IETF). It represents the consensus of the IETF community.  It has
       received public review and has been approved for publication by the
       Internet Engineering Steering Group (IESG).
    
    And as 8309 says
    
       This document describes service models as used within the IETF and
       also shows where a service model might fit into a software-defined
       networking architecture.
    
    So can you clarify what your concern is? 
    
    Thanks,
    Adrian
    
    > -----Original Message-----
    > From: Roque Gagliano (rogaglia) [mailto:rogaglia@cisco.com]
    > Sent: 05 June 2018 17:42
    > To: adrian@olddog.co.uk; 'Fioccola Giuseppe'; l2sm@ietf.org
    > Subject: Re: [L2sm] Proposed Liaison to 3GPP SA5
    > 
    > Hi Adrian,
    > 
    > I agree that sending this message is a good idea.
    > 
    > However, I do not think the RFC 8309 is "explaining what the IETF means by the
    > term "Service Model". This is an informational document and as such does not
    > represent consensus or recommendation per RFC 2026. Personally, I agree with
    > Giuseppe that RFC 8199 is a better document but that is also an informational
    > document.
    > 
    > I better text could be:
    > "RFC 8199 and RFC 8309 are informational documents developed by the IETF
    > community to show examples on how service models could be implemented."
    > 
    > Regards,
    > Roque
    > 
    > 
    > On 05/06/18 17:58, "L2sm on behalf of Adrian Farrel" <l2sm-bounces@ietf.org on
    > behalf of adrian@olddog.co.uk>; wrote:
    > 
    >     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 mailing list
    >     L2sm@ietf.org
    >     https://www.ietf.org/mailman/listinfo/l2sm
    >