[netmod] [Technical Errata Reported] RFC7950 (5274)
RFC Errata System <rfc-editor@rfc-editor.org> Sun, 04 March 2018 03:38 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 3D959126C2F for <netmod@ietfa.amsl.com>; Sat, 3 Mar 2018 19:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=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 sf_hNUUm7vdb for <netmod@ietfa.amsl.com>; Sat, 3 Mar 2018 19:38:33 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DB991200C1 for <netmod@ietf.org>; Sat, 3 Mar 2018 19:38:33 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5E8EAB8198E; Sat, 3 Mar 2018 19:38:19 -0800 (PST)
To: mbj@tail-f.com, bclaise@cisco.com, warren@kumari.net, joelja@bogus.com, kwatsen@juniper.net, lberger@labn.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: kwatsen@juniper.net, netmod@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180304033819.5E8EAB8198E@rfc-editor.org>
Date: Sat, 03 Mar 2018 19:38:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/sEIngnlFwjk4RocLhSPSOoh7H1s>
Subject: [netmod] [Technical Errata Reported] RFC7950 (5274)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 04 Mar 2018 03:38:34 -0000
The following errata report has been submitted for RFC7950, "The YANG 1.1 Data Modeling Language". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5274 -------------------------------------- Type: Technical Reported by: Kent Watsen <kwatsen@juniper.net> Section: 7.16.3 Original Text ------------- A corresponding XML instance example of the complete notification: <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> <eventTime>2008-07-08T00:01:00Z</eventTime> <event xmlns="urn:example:event"> <event-class>fault</event-class> <reporting-entity> /ex:interface[ex:name='Ethernet0'] </reporting-entity> <severity>major</severity> </event> </notification> Corrected Text -------------- A corresponding XML instance example of the complete notification follows. This example reports an event for an interface from the "example-foo" module defined in Section 13.1.1. <notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> <eventTime>2008-07-08T00:01:00Z</eventTime> <event xmlns="urn:example:event"> <event-class>fault</event-class> <reporting-entity xmlns:ex="urn:example:foo"> /ex:interface[ex:name='Ethernet0'] </reporting-entity> <severity>major</severity> </event> </notification> Notes ----- The "ex" prefix is not declared. The "example-foo" module in 13.1.1 is the only module in the draft that matches the given instance-identifier. An alternative fix would be to use a different module and a matching instance-identifier. Instructions: ------------- This erratum 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 can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7950 (draft-ietf-netmod-rfc6020bis-14) -------------------------------------- Title : The YANG 1.1 Data Modeling Language Publication Date : August 2016 Author(s) : M. Bjorklund, Ed. Category : PROPOSED STANDARD Source : Network Modeling Area : Operations and Management Stream : IETF Verifying Party : IESG
- [netmod] [Technical Errata Reported] RFC7950 (527… RFC Errata System
- Re: [netmod] [Technical Errata Reported] RFC7950 … Martin Bjorklund