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

"Susan Hares" <shares@ndzh.com> Wed, 04 March 2015 14:46 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0C41A1F73 for <idr@ietfa.amsl.com>; Wed, 4 Mar 2015 06:46:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.054
X-Spam-Level:
X-Spam-Status: No, score=-99.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=no
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 trneZX1A2qPK for <idr@ietfa.amsl.com>; Wed, 4 Mar 2015 06:46:37 -0800 (PST)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 979741A1BE7 for <idr@ietf.org>; Wed, 4 Mar 2015 06:46:37 -0800 (PST)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=74.43.47.92;
From: Susan Hares <shares@ndzh.com>
To: 'Benoit Claise' <bclaise@cisco.com>, idr@ietf.org
References: <54F70B64.4010608@cisco.com> <54F70EBD.8060007@cisco.com>
In-Reply-To: <54F70EBD.8060007@cisco.com>
Date: Wed, 04 Mar 2015 09:46:33 -0500
Message-ID: <052b01d0568a$024b0190$06e104b0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_052C_01D05660.19760B00"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQFTDL69ZbbHprq1RUN2ME2I7AvFHwMloeytne3NE1A=
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/5WIQk1DSUGD6hp0-e-X__l8aubU>
Subject: Re: [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 14:46:39 -0000

Benoit:

 

Will there be interaction between the layers of the modules (L3VPN service), and BGP module? 

 

Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Benoit Claise
Sent: Wednesday, March 04, 2015 8:55 AM
To: idr@ietf.org
Subject: [Idr] Fwd: Some background on the L3VPN Service YANG Model work

 

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  <mailto:bclaise@cisco.com> <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