[netmod] [Editorial Errata Reported] RFC6244 (3356)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 17 September 2012 16:21 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22C821F869A for <netmod@ietfa.amsl.com>; Mon, 17 Sep 2012 09:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.171
X-Spam-Level:
X-Spam-Status: No, score=-102.171 tagged_above=-999 required=5 tests=[AWL=-0.171, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-y02YjsTPMP for <netmod@ietfa.amsl.com>; Mon, 17 Sep 2012 09:21:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 75D8A21F8539 for <netmod@ietf.org>; Mon, 17 Sep 2012 09:21:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 17AE1B1E003; Mon, 17 Sep 2012 09:17:42 -0700 (PDT)
To: phil@juniper.net, rbonica@juniper.net, bclaise@cisco.com, j.schoenwaelder@jacobs-university.de, david.kessens@nsn.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20120917161742.17AE1B1E003@rfc-editor.org>
Date: Mon, 17 Sep 2012 09:17:42 -0700
Cc: netmod@ietf.org, rfc-editor@rfc-editor.org
Subject: [netmod] [Editorial Errata Reported] RFC6244 (3356)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netmod>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Sep 2012 16:21:11 -0000
The following errata report has been submitted for RFC6244, "An Architecture for Network Management Using NETCONF and YANG". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6244&eid=3356 -------------------------------------- Type: Editorial Reported by: Benoit Claise <bclaise@cisco.com> Section: 2.2.3 Original Text ------------- augment /ospf:ospf/ospf:area/ospf:interfaces { leaf no-neighbor-down-notification { type empty; description "Don't inform other protocols about" + " neighbor down events"; Corrected Text -------------- augment /ospf:ospf/ospf:area/ospf:interface { leaf no-neighbor-down-notification { type empty; description "Don't inform other protocols about" + " neighbor down events"; Notes ----- Section 2.2.3 For example, if the above OSPF configuration were the standard, a vendor module may augment this with vendor-specific extensions. module vendorx-ospf { namespace "http://vendorx.example.com/ospf"; prefix vendorx; import example-ospf { prefix ospf; } augment /ospf:ospf/ospf:area/ospf:interfaces { leaf no-neighbor-down-notification { type empty; description "Don't inform other protocols about" + " neighbor down events"; } } } While the "above OSPF configuration" refers to interface and not interfaces module example-ospf { namespace "http://example.org/netconf/ospf"; prefix ospf; import network-types { // Access another module's def'ns prefix nett; } container ospf { // Declare the top-level tag list area { // Declare a list of "area" nodes key name; // The key "name" identifies list members leaf name { type nett:area-id; } list interface { key name; leaf name { type nett:interface-name; } leaf priority { description "Designated router priority"; type uint8; // The type is a constraint on // valid values for "priority". } leaf metric { type uint16 { range 1..65535; } } leaf dead-interval { units seconds; type uint16 { range 1..65535; } } } } } } Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6244 (draft-ietf-netmod-arch-10) -------------------------------------- Title : An Architecture for Network Management Using NETCONF and YANG Publication Date : June 2011 Author(s) : P. Shafer Category : INFORMATIONAL Source : NETCONF Data Modeling Language Area : Operations and Management Stream : IETF Verifying Party : IESG
- [netmod] [Editorial Errata Reported] RFC6244 (335… RFC Errata System