[mpls] New Liaison Statement, "Liaison from MEF on IP Service Attributes"

Liaison Statement Management Tool <lsmt@ietf.org> Fri, 26 February 2016 18:05 UTC

Return-Path: <lsmt@ietf.org>
X-Original-To: mpls@ietf.org
Delivered-To: mpls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E469F1B2D0B; Fri, 26 Feb 2016 10:05:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Liaison Statement Management Tool <lsmt@ietf.org>
To: ietf@wjcerveny.com, joelja@bogus.com, bclaise@cisco.com, adrian@olddog.co.uk, rcallon@juniper.net, ietf@trammell.ch, swallow.ietf@gmail.com, bill.wu@huawei.com, loa@pi.nu
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160226180541.18278.30437.idtracker@ietfa.amsl.com>
Date: Fri, 26 Feb 2016 10:05:41 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/EcGlgAjnhpMcRQq6e7qyUgY3Sus>
X-Mailman-Approved-At: Fri, 26 Feb 2016 11:32:21 -0800
Cc: L3VPN Service Model Discussion List <l3sm@ietf.org>, Multiprotocol Label Switching Discussion List <mpls@ietf.org>, IP Performance Metrics Discussion List <ippm@ietf.org>, Bill Cerveny <ietf@wjcerveny.com>, Bill Bjorkman <bill@metroethernetforum.net>, Benoit Claise <bclaise@cisco.com>, Nan Chen <nan@metroethernetforum.org>, Joel Jaeggli <joelja@bogus.com>, Martin Stiemerling <mls.ietf@gmail.com>, The IETF Chair <chair@ietf.org>, Spencer Dawkins <spencerdawkins.ietf@gmail.com>, Raghu Ranganathan <rraghu@ciena.com>, Ross Callon <rcallon@juniper.net>, Brian Trammell <ietf@trammell.ch>
Subject: [mpls] New Liaison Statement, "Liaison from MEF on IP Service Attributes"
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 18:05:42 -0000

Title: Liaison from MEF on IP Service Attributes
Submission Date: 2016-02-26
URL of the IETF Web page: https://datatracker.ietf.org/liaison/1458/

From: "Raghu Ranganathan" <rraghu@ciena.com>
To: bclaise@cisco.com, joelja@bogus.com, ietf@trammell.ch>, ietf@wjcerveny.com, loa@pi.nu, swallow.ietf@gmail.com, rcallon@juniper.net, adrian@olddog.co.uk, bill.wu@huawei.com
Cc: Alvaro Retana <aretana@cisco.com>,Joel Jaeggli <joelja@bogus.com>,Deborah Brungard <db3546@att.com>,IP Performance Metrics Discussion List <ippm@ietf.org>,Multiprotocol Label Switching Discussion List <mpls@ietf.org>,Adrian Farrel <adrian@olddog.co.uk>,Qin Wu <bill.wu@huawei.com>,Bill Cerveny <ietf@wjcerveny.com>,Brian Trammell <ietf@trammell.ch>,Spencer Dawkins <spencerdawkins.ietf@gmail.com>,George Swallow <swallow.ietf@gmail.com>,Alia Atlas <akatlas@gmail.com>,The IETF Chair <chair@ietf.org>,Nan Chen <nan@metroethernetforum.org>,Ross Callon <rcallon@juniper.net>,Loa Andersson <loa@pi.nu>,Benoit Claise <bclaise@cisco.com>,L3VPN Service Model  Discussion List <l3sm@ietf.org>,Bill Bjorkman <bill@metroethernetforum.net>,Martin Stiemerling <mls.ietf@gmail.com>,Raghu Ranganathan <rraghu@ciena.com>,
Response Contacts: rraghu@ciena.com
Technical Contacts: 
Purpose: For information

Body: We would like to inform you that during our 1Q2016 meeting, MEF has approved a new project on IP Service Attributes. We have set out some background and further details below.

MEF is well known for the definition of Carrier Ethernet (CE) services (in MEF 6.2, MEF 33 and MEF 51) based on service attributes (defined in MEF 10.3 and MEF 26.1). In MEF terms, a "service" refers to the set of attributes and their values that are agreed between the provider of a serviceand the customer of that service. These attributes are independent of how the service is implemented; for example a CE service could be
implemented using Provider Backbone Bridging (802.1Q) or using VPLS (RFC 4761/4762) to provide the connectivity across the service provider's network. MEF defines both end-to-end services agreed between a subscriber and a service provider, where the end points are all User-Network Interfaces (UNIs), and inter-provider services supplied by one service provider or operator to another, where the end points may be UNIs or External Network-Network Interfaces (ENNIs).

Note that this differs from how the word "service" is sometimes used in IETF, e.g. to describe a particular technology (as in "Virtual Private LAN Service").

Although IP Services are widely deployed, there is currently no standard definition of the attributes and values used to describe them. Each Service Provider has their own way of describing IP services (including in some cases their own terminology); this makes it hard for customers to compare service offerings from different providers, and in particular makes it hard for providers to interconnect with each other – each Service Provider must form a specific bilateral agreement with each other Service Provider they wish to connect with.

Furthermore, there is a desire among service providers to improve service delivery times by automating the service ordering and configuration process. This is a key aspect of MEF Lifecycle Services Orchestration (LSO). The aim of MEF LSO is to deliver the MEF Third Network vision, to provide Assured, Agile and Orchestrated services. MEF LSO enables automation and orchestration of service ordering and management between service providers ("East/West interfaces") through the creation of standard data models and APIs. However, a pre-requisite for defining those is to have a standard definition of the service that is to be managed.

The new project is intended to address these issues by providing a standard definition of IP Services, including both end-to-end services and inter-provider services, through the definition of a standard set of Service Attributes that can be used in each case. The scope is limited to IP-VPN and Internet Access services  (IP peering/transit for internet traffic is precluded). It is intended that this project is the first step in enabling multi-operator service orchestration of IP Services using MEF LSO, and that later projects will use the Service Attributes to create standard data models and APIs. The intent of LSO is to provide a common framework across different service technologies; MEF is working with TMF and ONF to create common models for services, and the standard data models and APIs for IP Services will tie into this framework.

We have noted that IETF is working on a Yang model for Layer 3 Services in the L3SM working group. Although the scope of that project in IETF is different, it is clear there is some synergy between the L3SM work and this MEF project. We believe that both projects can benefit from input from each other and we hope to work closely with the L3SM working group to ensure our specifications are aligned.

The scope of the initial phase of the IP Service Attributes project includes:
-Definition of attributes for IP-capable UNIs and NNIs, for IP Service connections, and for IP Service End Points at UNIs and ENNIs
-IP address allocations and IP control protocols (e.g. DHCP) etc at UNIs
-OAM across the external interface (by reference to IETF protocols and mechanisms)
-Service Level Specification (SLS) definitions including performance monitoring/constraints (by reference to IETF protocols and metric definitions)
-Redundant links at an external interface (Subscriber/Service provider or between Service Providers), including options for different routing protocols.
-Multi-CoS services (i.e. QoS classification) and classification of Green/Yellow packets including diffserv, Bandwidth profiles, etc.
-IPv4, IPv6 and dual stack services
-Inter-operator IP-VPN services using options A, B or C from RFC4364
-Unicast only (multicast is defered to a future phase).
-Other topics may be added as the project progresses.

It is important to note that we intend to make extensive reference to existing IETF RFCs where applicable; it is not our intent to specify new protocols or mechanisms where there are existing solutions.

Note: further information about MEF LSO can be found in the LSO Reference Architecture. The final verison is expected to be published in March; in the meantime, the latest approved draft is available as below:
Username: mef