IETF Logo Mail Archive

[Rtg-yang-coord] Fwd: [L3sm] Some background on the L3VPN Service YANG Model work

Benoit Claise <bclaise@cisco.com> Wed, 04 March 2015 13:52 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E154A1A19F8 for <rtg-yang-coord@ietfa.amsl.com>; Wed, 4 Mar 2015 05:52:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.91
X-Spam-Level:
X-Spam-Status: No, score=-13.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Dws8aq51nh2X for <rtg-yang-coord@ietfa.amsl.com>; Wed, 4 Mar 2015 05:52:39 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A687F1A1AC7 for <Rtg-yang-coord@ietf.org>; Wed, 4 Mar 2015 05:52:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7699; q=dns/txt; s=iport; t=1425477158; x=1426686758; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=DEAs54TtBtw1s1X8jnLG83kjymQ9lGG/rsd8u51Mjvg=; b=Zi0SMUEe6DtKiSLkku/5CUapF3U4mhI3eJfRBqbn7FMgO0wYCYa8lmXZ t39B2WrIbfxXKjjX495lPmB877jQJBK8UxamRxWR2IEgVhKbu4xTsytle 94kGcxVf/sPBKCfMKVsRnyFPYU+xvEBT0k8BaJkFaQ1X77sQ3wJAnDAzE 4=;
X-Files: Attached Message Part : 124
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CsBABUDfdU/xbLJq1QCoNUWsETAQmFcQKBcwEBAQEBAXyEDwEBAQQBAQFrChEcAwECCgMTDwkDAgECARUmAggGDQYCAQEFC4gbDdcXAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sShAwGCgIBLREYBoQlBY4Ag2OBLlGFaYFThR6MdyODbz0xgkMBAQE
X-IronPort-AV: E=Sophos;i="5.09,687,1418083200"; d="scan'208,217";a="369789397"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 04 Mar 2015 13:52:36 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t24DqaDh012319 for <Rtg-yang-coord@ietf.org>; Wed, 4 Mar 2015 13:52:36 GMT
Message-ID: <54F70E24.5090400@cisco.com>
Date: Wed, 04 Mar 2015 14:52:36 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>
References: <54F70B64.4010608@cisco.com>
In-Reply-To: <54F70B64.4010608@cisco.com>
X-Forwarded-Message-Id: <54F70B64.4010608@cisco.com>
Content-Type: multipart/mixed; boundary="------------000002050707050101010907"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/OwGwM0gkwtAZYOGdodRfdPffuoY>
Subject: [Rtg-yang-coord] Fwd: [L3sm] Some background on the L3VPN Service YANG Model work
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2015 13:52:41 -0000

FYI.

Regards, Benoit


-------- Forwarded Message --------
Subject: 	[L3sm] Some background on the L3VPN Service YANG Model work
Date: 	Wed, 4 Mar 2015 14:40:52 +0100
From: 	Benoit Claise <bclaise@cisco.com>
To: 	l3sm@ietf.org



Dear all,

Let me give you some background on this new piece of work: The Layer 
Three Virtual Private Network Service Model (L3SM)

Three months ago, Adrian Farrel and I set up a design team to create a 
L3VPN _service _YANG model.
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.  Therefore, that design team was composed of operators 
only.

That design team created a first draft: 
http://datatracker.ietf.org/doc/draft-l3vpn-service-yang/
Now that the draft has been posted, the work and discussion should 
continue in a public forum, i.e. this l3sm@ietf.org mailing list.

Next step? we're busy trying to create a new short-lived WG, focusing 
solely on this L3VPN service YANG model.
See the proposal at https://datatracker.ietf.org/doc/charter-ietf-l3sm/
If this WG is created (This proposal is on the IESG telechat this week 
for external review approval), this would be a good test for the IETF 
community: are we ready to standardize a first service YANG model? 
Personally, I believe we are.
IMO, the advantage/driver for this work is explained in the charter 
proposal:

    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.

Don't hesitate to forward this email.
     List address: l3sm@ietf.org
     Archive: http://www.ietf.org/mail-archive/web/l3sm/
     To subscribe: https://www.ietf.org/mailman/listinfo/l3sm

Regards, Benoit

v2.8.7 | Report a Bug | By Email