[bess] FW: Last Call: <draft-wu-l3sm-rfc8049bis-04.txt> (YANG Data Model for L3VPN Service Delivery) to Proposed Standard

"Alvaro Retana (aretana)" <aretana@cisco.com> Wed, 13 September 2017 16:29 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86337132C32; Wed, 13 Sep 2017 09:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 R2Yv_QzaELkj; Wed, 13 Sep 2017 09:29:56 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B06D1321B6; Wed, 13 Sep 2017 09:29:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3510; q=dns/txt; s=iport; t=1505320196; x=1506529796; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=7QIYIDMailI3p+oZrQpOaje7NtOdkwDwUELOs8jq3Kg=; b=Bf8TocB46BP7CkQ2/SaraCZ4u11Dp0Pg7DpTejy4u6LSMuJkvEG2JJSK laiBIF4FnCwc0xqLoD14iwxZB/6FAmX4Tzi3TWlHjQBWrOdY6dS/Nt1cB BOMgCCgQDYIALVVplGNNrGLwxh3uBW/CnflUy9/qOc38rV9uqzwmqRcHs I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ArAgABXLlZ/51dJa1dGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1pkgRUHg3CKIZAlgVKWSg6CBAojhRsCGoQ7PxgBAgEBAQEBAQFrHQu?= =?us-ascii?q?FGQYjEToLEAIBCBoCHwcCAgIwFAEGAQYDAgQOBYoxEK0ngieLKwEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBARgFgQ6CHYICgVCBYysLgnKEPBWDOjCCMQWYN4hCAodZg1Q?= =?us-ascii?q?MiRiCE4VoinmVAwIRGQGBOAEfOIENdxVKEgGFCxcZgU52iR6BMoEPAQEB?=
X-IronPort-AV: E=Sophos;i="5.42,389,1500940800"; d="scan'208";a="292760082"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Sep 2017 16:29:48 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v8DGTlFd016016 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Sep 2017 16:29:47 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 13 Sep 2017 11:29:47 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1263.000; Wed, 13 Sep 2017 11:29:47 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "bess@ietf.org" <bess@ietf.org>
CC: "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Thread-Topic: Last Call: <draft-wu-l3sm-rfc8049bis-04.txt> (YANG Data Model for L3VPN Service Delivery) to Proposed Standard
Thread-Index: AQHTLJks7TL0FyWQYU+KeNedY1YxXKKzEpYA
Date: Wed, 13 Sep 2017 16:29:47 +0000
Message-ID: <7C93CABF-7980-4EF5-AB5B-2B17FDE47E25@cisco.com>
References: <150531137507.30405.6179845967838123305.idtracker@ietfa.amsl.com>
In-Reply-To: <150531137507.30405.6179845967838123305.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.25.0.170815
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F623599D759FCF4B9BBA9B72F6BF4C34@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/YLfAPfORgrRjvunr_2lVxSTU-n0>
Subject: [bess] FW: Last Call: <draft-wu-l3sm-rfc8049bis-04.txt> (YANG Data Model for L3VPN Service Delivery) to Proposed Standard
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 16:29:58 -0000

FYI…

Please take a look.  If anyone has comments, please reply to the thread in the ietf@ietf.org list.

Thanks!

Alvaro.

On 9/13/17, 10:04 AM, "IETF-Announce on behalf of The IESG" <ietf-announce-bounces@ietf.org on behalf of iesg-secretary@ietf.org> wrote:


The IESG has received a request from an individual submitter to consider the
following document: - 'YANG Data Model for L3VPN Service Delivery'
  <draft-wu-l3sm-rfc8049bis-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-10-11. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   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.

   If approved, this document obsoletes RFC 8049.  The changes are a
   series of small fixes to the YANG module, and some clarifications to
   the text.

The file can be obtained via
https://datatracker.ietf.org/doc/draft-wu-l3sm-rfc8049bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-wu-l3sm-rfc8049bis/ballot/

No IPR declarations have been submitted directly on this I-D.

Working Group Summary
  RFC 8049 was the product of the L3SM working group, but that WG has been closed.
  No other WG covers this topic.
  However, the L3SM list remains open: changes and revisions were publicised and discussed there

The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc3022: Traditional IP Network Address Translator (Traditional NAT) (Informational - IETF stream)