[Idr] Fwd: Some background on the L3VPN Service YANG Model work

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

Return-Path: <bclaise@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 186D91A032D for <idr@ietfa.amsl.com>; Wed, 4 Mar 2015 05:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
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, HTML_MESSAGE=0.001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id quqni0ROq-6R for <idr@ietfa.amsl.com>; Wed, 4 Mar 2015 05:55:12 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C114C1A0222 for <idr@ietf.org>; Wed, 4 Mar 2015 05:55:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7183; q=dns/txt; s=iport; t=1425477312; x=1426686912; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=URnIOmr+RnOmQShvUdGVSuRVZwmCcy/bMFuIxHRk4o4=; b=FGf+dAiFSK7qSp3Eq+fOKBXG65z7/cqitpZBD7WK+qS2iK84cAFmm0B+ Py81dTnkZVJ5kXY7dv5Ji7lzlR0lYVZkJP2OpWfDqo6hPl8Dl7xEaoNkr DrNGlUM0/YR7vxJWJsGFjtPOdtViucvL7EFmXunUnfu0q/mpQUy3j20IE 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.09,687,1418083200"; d="scan'208,217";a="364792242"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([]) by aer-iport-3.cisco.com with ESMTP; 04 Mar 2015 13:55:10 +0000
Received: from [] (ams-bclaise-8914.cisco.com []) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t24Dt99D028403 for <idr@ietf.org>; Wed, 4 Mar 2015 13:55:09 GMT
Message-ID: <54F70EBD.8060007@cisco.com>
Date: Wed, 04 Mar 2015 14:55:09 +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: idr@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/alternative; boundary="------------010109010203040208020802"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/Q5RVqMDNKu2KVnX_bl2u2ghhC-E>
Subject: [Idr] Fwd: Some background on the L3VPN Service YANG Model work
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2015 13:55:14 -0000

FYI. Sorry for the potential duplicates.

Regards, Benoit

-------- Forwarded Message --------
Subject: 	Some background on the L3VPN Service YANG Model work
Date: 	Wed, 04 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 

That design team created a first draft: 
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 

    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