[L3sm] Fwd: RFC 8049 on YANG Data Model for L3VPN Service Delivery

Benoit Claise <bclaise@cisco.com> Thu, 23 February 2017 10:59 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7AF1296A3 for <l3sm@ietfa.amsl.com>; Thu, 23 Feb 2017 02:59:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 H8RZmq6-Jnfd for <l3sm@ietfa.amsl.com>; Thu, 23 Feb 2017 02:59:22 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE31A129480 for <l3sm@ietf.org>; Thu, 23 Feb 2017 02:59:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9553; q=dns/txt; s=iport; t=1487847561; x=1489057161; h=subject:references:to:from:message-id:date:mime-version: in-reply-to; bh=+esBM0H+sLOlRst3d1KAtq2m8vYClo0QoK3ziMnJXbg=; b=ZLxjI5/2XGU2ysrZGgTtXUNj60NXpFYAT4rRLngF905DFMPl3iMhLIju C8RbU12+YW8/JQYODfeN3nh/vZgSyRxHH/XzvJ5Tt6X2Qf5TkdOzCo6Vx PqHzBkYb3BJ81xO5bmBcGlZw4f9xZ8Sgzu7v255G7zltiLeHwUc+DMX2T 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DUAwCdv65Y/xbLJq1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBhDEDgQaNY3KQSR+QCIUsgg0fAQqFeAKDVxgBAgEBAQEBAQFiHQuEcAE?= =?us-ascii?q?CBAEBTCAbHAMBAg0iJwocAggGDQYCAQEQBwIEh2cDgVIDFQ6waiuLFwEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEaBYZMggUIgmKBPIEVgV8FP4VFBZwThnSDHAyIB4F7hRy?= =?us-ascii?q?DLoZLiDaCaYgHHziBACEUCBcVGCaEUAgQgWI/NYkJDxeCFwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,197,1484006400"; d="scan'208,217";a="649907410"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Feb 2017 10:59:19 +0000
Received: from [10.61.240.233] ([10.61.240.233]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1NAxISf014512 for <l3sm@ietf.org>; Thu, 23 Feb 2017 10:59:18 GMT
References: <20170223002550.A9449B812DF@rfc-editor.org>
To: "l3sm@ietf.org" <l3sm@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
X-Forwarded-Message-Id: <20170223002550.A9449B812DF@rfc-editor.org>
Message-ID: <9906f790-7763-20e9-88b4-04daa741004f@cisco.com>
Date: Thu, 23 Feb 2017 11:59:18 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170223002550.A9449B812DF@rfc-editor.org>
Content-Type: multipart/alternative; boundary="------------B41E1951F0EC39E98BBBB528"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/pGwNtEsMDnscy5nBoTYBTzZm5Oo>
Subject: [L3sm] Fwd: RFC 8049 on YANG Data Model for L3VPN Service Delivery
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 10:59:24 -0000

Great achievement.
Thanks to operators who drove this, and to everybody who helped.

Regards, Benoit


-------- Forwarded Message --------
Subject: 	[L3sm] RFC 8049 on YANG Data Model for L3VPN Service Delivery
Date: 	Wed, 22 Feb 2017 16:25:50 -0800 (PST)
From: 	rfc-editor@rfc-editor.org
To: 	ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: 	l3sm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org



A new Request for Comments is now available in online RFC libraries.

         
         RFC 8049

         Title:      YANG Data Model for L3VPN
                     Service Delivery
         Author:     S. Litkowski, L. Tomotaki, K. Ogaki
         Status:     Standards Track
         Stream:     IETF
         Date:       February 2017
         Mailbox:    stephane.litkowski@orange.com,
                     luis.tomotaki@verizon.com,
                     ke-oogaki@kddi.com
         Pages:      157
         Characters: 272974
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-ietf-l3sm-l3vpn-service-model-19.txt

         URL:        https://www.rfc-editor.org/info/rfc8049

         DOI:        10.17487/RFC8049

This document defines a YANG data model that can be used for
communication between customers and network operators and to deliver
a Layer 3 provider-provisioned VPN service.  This document is limited
to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364.  This
model is intended to be instantiated at the management system to
deliver the overall service.  It is not a configuration model to be
used directly on network elements.  This model provides an abstracted
view of the Layer 3 IP VPN service configuration components.  It will
be up to the management system to take this model as input and use
specific configuration models to configure the different network
elements to deliver the service.  How the configuration of network
elements is done is out of scope for this document.

This document is a product of the L3VPN Service Model Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
   https://www.ietf.org/mailman/listinfo/ietf-announce
   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
L3sm mailing list
L3sm@ietf.org
https://www.ietf.org/mailman/listinfo/l3sm
.