[MBONED] MBoned: Re: WG Review: L3VPN Service Model (l3sm)
Toerless Eckert <eckert@cisco.com> Fri, 06 March 2015 16:55 UTC
Return-Path: <eckert@cisco.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32E231A1A81; Fri, 6 Mar 2015 08:55:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 jdJ6lhrQFQMz; Fri, 6 Mar 2015 08:55:27 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B2401ACEF9; Fri, 6 Mar 2015 08:54:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3085; q=dns/txt; s=iport; t=1425660898; x=1426870498; h=date:from:to:cc:subject:message-id:mime-version; bh=wSAyg6hxFR5TJEqhrth4T8uVksF4+Ikg/povHv0Lsr0=; b=SOiJuloFn34ats8b9TQ528SiqYXytugxmduWW2+puu0sVJ8SB9NqTjr1 qkNbgT1N7upY2fHFC+unInpY7pSaq5OEs4JERdirEYo+0PFgQOnnvq+4J 1wNVyOeXv4SVUy1b1mSudZ2OnibagPk0hdI63g/LcFZRp1J7s3Uho5eCC w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJBQDO2vlU/4gNJK1SCoMGgSzHYoE7TQEBAQEBAXyEDwEBAT40CzACAQk0BTsPEogvzXABAQEBAQEBAwEBAQEBAQEBGo8pXIQyBYV3hG6ObgGBGoMmi22DQiOEDx0xAQEBgkABAQE
X-IronPort-AV: E=Sophos;i="5.11,353,1422921600"; d="scan'208";a="129606801"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-5.cisco.com with ESMTP; 06 Mar 2015 16:54:57 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t26GsukZ019013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Mar 2015 16:54:57 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t26Gsuhh013904; Fri, 6 Mar 2015 08:54:56 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t26GsuBk013903; Fri, 6 Mar 2015 08:54:56 -0800
Date: Fri, 06 Mar 2015 08:54:56 -0800
From: Toerless Eckert <eckert@cisco.com>
To: mboned@ietf.org, pim@ietf.org
Message-ID: <20150306165456.GT16454@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/mboned/nEvIRSidBqRiRS8SaACnX__rI6w>
Cc: IETF Announcement List <ietf-announce@ietf.org>
Subject: [MBONED] MBoned: Re: WG Review: L3VPN Service Model (l3sm)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2015 16:55:30 -0000
Any thoughts on this ? Anybody from mboned planning to contribute to this work to ensure that L3VPN multicast would be represented in the data model created ? In-Reply-To: <20150306163644.31050.21402.idtracker@ietfa.amsl.com> On Fri, Mar 06, 2015 at 08:36:44AM -0800, The IESG wrote: > From: The IESG <iesg-secretary@ietf.org> > To: IETF-Announce <ietf-announce@ietf.org> > Subject: > > A new IETF working group has been proposed in the Operations and > Management Area. The IESG has not made any determination yet. The > following draft charter was submitted, and is provided for informational > purposes only. Please send your comments to the IESG mailing list (iesg > at ietf.org) by 2015-03-16. > > L3VPN Service Model (l3sm) > ------------------------------------------------ > Current Status: Proposed WG > > Assigned Area Director: > Benoit Claise <bclaise@cisco.com> > > > Charter: > > 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 > point. > > Milestones: > Jan 2016 - L3VPN Service (YANG) Model to the IESG for publication as > Proposed Standard RFC > Jan 2016 - Close the working group
- Re: [MBONED] MBoned: Re: WG Review: L3VPN Service… Benoit Claise
- [MBONED] MBoned: Re: WG Review: L3VPN Service Mod… Toerless Eckert
- Re: [MBONED] MBoned: Re: WG Review: L3VPN Service… Jeffrey Haas