Re: [Rtg-yang-coord] Fwd: [L3sm] Some background on the L3VPN Service YANG Model work
"Susan Hares" <shares@ndzh.com> Wed, 04 March 2015 14:44 UTC
Return-Path: <shares@ndzh.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 691AF1A1F00
for <rtg-yang-coord@ietfa.amsl.com>; Wed, 4 Mar 2015 06:44:35 -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 yTwgyhOU2bIY for <rtg-yang-coord@ietfa.amsl.com>;
Wed, 4 Mar 2015 06:44:31 -0800 (PST)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com
[64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id B2FC81A2119
for <Rtg-yang-coord@ietf.org>; Wed, 4 Mar 2015 06:44:30 -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>,
<Rtg-yang-coord@ietf.org>
References: <54F70B64.4010608@cisco.com> <54F70E24.5090400@cisco.com>
In-Reply-To: <54F70E24.5090400@cisco.com>
Date: Wed, 4 Mar 2015 09:44:26 -0500
Message-ID: <051101d05689$b6996980$23cc3c80$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0512_01D0565F.CDC6BCE0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQFTDL69ZbbHprq1RUN2ME2I7AvFHwHm1Bs8nffDLdA=
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/Ko1Ckgu8YTz7MfGEJG7MmKPx_Qo>
Subject: Re: [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 14:44:35 -0000
Benoit: Do you consider the L3VPN service a protocol dependent yang module or a protocol independent module? Sue From: Rtg-yang-coord [mailto:rtg-yang-coord-bounces@ietf.org] On Behalf Of Benoit Claise Sent: Wednesday, March 04, 2015 8:53 AM To: Rtg-yang-coord@ietf.org Subject: [Rtg-yang-coord] Fwd: [L3sm] Some background on the L3VPN Service YANG Model work 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 <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
- [Rtg-yang-coord] Fwd: [L3sm] Some background on t… Benoit Claise
- Re: [Rtg-yang-coord] Fwd: [L3sm] Some background … Susan Hares
- Re: [Rtg-yang-coord] Fwd: [L3sm] Some background … Adrian Farrel
- Re: [Rtg-yang-coord] Fwd: [L3sm] Some background … Benoit Claise