WG Action: Formed L3VPN Service Model (l3sm)

The IESG <iesg-secretary@ietf.org> Tue, 24 March 2015 22:18 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 003EE1A1B3F; Tue, 24 Mar 2015 15:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id VKVxkD6qOlZD; Tue, 24 Mar 2015 15:18:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A86AA1A1B47; Tue, 24 Mar 2015 15:18:16 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Action: Formed L3VPN Service Model (l3sm)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150324221816.1621.85697.idtracker@ietfa.amsl.com>
Date: Tue, 24 Mar 2015 15:18:16 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/wryN-DUufiCMSXCXiYetrBJ73z8>
Cc: l3sm WG <l3sm@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2015 22:18:19 -0000

A new IETF working group has been formed in the Operations and Management
Area. For additional information please contact the Area Directors or the
WG Chairs.

L3VPN Service Model  (l3sm)
Current Status: Proposed WG

  Adrian Farrel <adrian@olddog.co.uk>
  Qin Wu <bill.wu@huawei.com>

Assigned Area Director:
  Benoit Claise <bclaise@cisco.com>

Mailing list
  Address: l3sm@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/l3sm
  Archive: http://www.ietf.org/mail-archive/web/l3sm/


The IETF and the industry in general is currently specifying a set of
YANG models for network element and protocol configuration. This is an
essential first step, but the end goal is full system configuration that
allows the deployment of services across networks. Services are built
from a combination of network element and protocol configuration, but are
specified to service users in more abstract terms.

The Layer Three Virtual Private Network Service Model (L3SM) working
group is a short-lived WG tasked to create a YANG data model that
describes a L3VPN service (a L3VPN service model) that can be used for
communication between customers and network operators, and to provide
input to automated control and configuration applications.

It needs to be clearly understood that this L3VPN service model is not an
L3VPN configuration model. That is, it does not provide details for
configuring network elements or protocols. Instead it contains the
characteristics of the service, as discussed between the operators and
their customers. A separate process is responsible for mapping this
service model onto the protocols and network elements depending on how
the network operator chooses to realise the service.

The deliverable from this working group will provide information to
evaluate the set of YANG models that have already been developed or are
under development, and will help identify any missing models or details. 
The deliverable can be viewed as driving requirements for protocol
configuration model so that the service parameters can be mapped into
inputs used by the protocol models.

It is hoped that this working group will provide evidence that such
service models can be quickly constructed and agreed upon. If successful,
further service models may be developed in other working groups

The working group should consider draft-l3vpn-service-yang as a starting

  Jan 2016 - L3VPN Service (YANG) Model to the IESG for publication as
Proposed Standard RFC
  Jan 2016 - Close the working group