Re: [netmod] [Technical Errata Reported] RFC6020 (5272)

Kent Watsen <kwatsen@juniper.net> Fri, 02 March 2018 19:50 UTC

Return-Path: <kwatsen@juniper.net>
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 926CB129C6A for <netmod@ietfa.amsl.com>; Fri, 2 Mar 2018 11:50:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 Zct2zCrm2LGn for <netmod@ietfa.amsl.com>; Fri, 2 Mar 2018 11:50:50 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82D63124217 for <netmod@ietf.org>; Fri, 2 Mar 2018 11:50:50 -0800 (PST)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w22Jmj50028225; Fri, 2 Mar 2018 11:50:49 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=R+A2qQHrM8gkzM9IXBFfOBLQr1ej5+sr98hViGROgIE=; b=WnTAootpTX75kg5Wku8Z8JtmYsRHtPuaCJhR88y1CB8Spzb1fBlqI27Gc5tLw47ikTtZ Y0YlNjXIp3CuIwQf9EfqjiJLCni/xQdUpDhPcbImY5NEnkR7Njbql6W5CkfYwQvMFC25 UJStmge7MQg0jCO0GOAj9PQ7kTa55Za4bZlMLXjfZ41fSUdbwKKgwOKeUZmoF4+plBzT a6Oj47b4YMPzYGL0hiimkKO6AQvr9dZKGua2otMiseCfW8iGcAdDtrL0hWJmqQxYHg3r v2rbh2NkjaSamIoyFLMyHXBRlVb9T/Bv3kD3JO0mSppDveglObVYvw1rwrN7dj7aH2IO TQ==
Received: from nam02-cy1-obe.outbound.protection.outlook.com (mail-cys01nam02lp0053.outbound.protection.outlook.com [207.46.163.53]) by mx0a-00273201.pphosted.com with ESMTP id 2gfcvx00xk-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 02 Mar 2018 11:50:49 -0800
Received: from DM5PR05MB3484.namprd05.prod.outlook.com (10.174.240.147) by DM5PR05MB3594.namprd05.prod.outlook.com (10.174.242.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.567.6; Fri, 2 Mar 2018 19:50:47 +0000
Received: from DM5PR05MB3484.namprd05.prod.outlook.com ([fe80::d42c:9ad2:ced3:e377]) by DM5PR05MB3484.namprd05.prod.outlook.com ([fe80::d42c:9ad2:ced3:e377%2]) with mapi id 15.20.0567.006; Fri, 2 Mar 2018 19:50:47 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: RFC Errata System <rfc-editor@rfc-editor.org>, "mbj@tail-f.com" <mbj@tail-f.com>, "bclaise@cisco.com" <bclaise@cisco.com>, "warren@kumari.net" <warren@kumari.net>, "EXT - joelja@bogus.com" <joelja@bogus.com>, "lberger@labn.net" <lberger@labn.net>
CC: "rharolde@umich.edu" <rharolde@umich.edu>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [Technical Errata Reported] RFC6020 (5272)
Thread-Index: AQHTsl1z4G/LfzCjx0ubVKTfZpopyqO9BvmA
Date: Fri, 2 Mar 2018 19:50:47 +0000
Message-ID: <C3DE4066-3888-4112-9DF9-F304EEAD2B58@juniper.net>
References: <20180302193355.F0889B810D3@rfc-editor.org>
In-Reply-To: <20180302193355.F0889B810D3@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR05MB3594; 7:TErN6gSs6Rc/ov77+vPr0ORx9aTiwhBxTBXyLNFqWWITkz9jAIiMFUhVrJz9+Mr4OTdGgTSt14wwc5TJQXa/6CGcLlZdJZ1xa/Wi7MtsuiIfSDzk/pcxSSi1h34KV0fmsms8RjoG4aCXWkyt4Ydqz2OxDWwaCe59w63hEaPW88pqIbP501gAGpoPlAHZFta3qFS7I9E5M4pBKl6nXkb0tgKy3IdO//NBuS9fRqc+/ppoowDKxJ4in0ii1QmFuxjT
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a1b21ca5-2e2a-4ecc-2496-08d58076e4c8
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603307)(7153060)(7193020); SRVR:DM5PR05MB3594;
x-ms-traffictypediagnostic: DM5PR05MB3594:
x-ld-processed: bea78b3c-4cdb-4130-854a-1d193232e5f4,ExtAddr
x-microsoft-antispam-prvs: <DM5PR05MB3594FDAF394FAC2E665F9894A5C50@DM5PR05MB3594.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(177329092695168);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040501)(2401047)(8121501046)(5005006)(10201501046)(3231220)(944501243)(93006095)(93001095)(3002001)(6055026)(6041288)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(6072148)(201708071742011); SRVR:DM5PR05MB3594; BCL:0; PCL:0; RULEID:; SRVR:DM5PR05MB3594;
x-forefront-prvs: 05991796DF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39380400002)(39860400002)(396003)(376002)(346002)(189003)(199004)(3280700002)(53936002)(6512007)(6306002)(6506007)(102836004)(6246003)(97736004)(105586002)(186003)(59450400001)(26005)(305945005)(2950100002)(7736002)(229853002)(106356001)(82746002)(33656002)(2900100001)(66066001)(6436002)(25786009)(4326008)(8936002)(2501003)(478600001)(83716003)(99286004)(3660700001)(5660300001)(2906002)(5250100002)(68736007)(76176011)(36756003)(966005)(6486002)(8656006)(3846002)(575784001)(316002)(54906003)(110136005)(86362001)(58126008)(81156014)(2201001)(8676002)(81166006)(6116002)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3594; H:DM5PR05MB3484.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: PSc+LDlu6tt6hw3KUFLmooRea66MYjQYS+RdujQYfPcc/1+cZD4Zqy6ItM26uzcB0qNdGxzgVb3JOT2TX6SYE38Go7Q3KsxHHxnotHNUxT+V8HK84U6I/UISYUOCfuspwNn6MUW5JnsLtdmBU8XW+WR/+YZvreSsHe2wEwMrZAo=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <BF6B879E2C4EEA4F9FDC276B64E5D35A@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a1b21ca5-2e2a-4ecc-2496-08d58076e4c8
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Mar 2018 19:50:47.5298 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3594
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-03-02_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1803020233
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/NfTr8-gUZvvnVCLUnSGiHyPwT3Q>
Subject: Re: [netmod] [Technical Errata Reported] RFC6020 (5272)
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: Fri, 02 Mar 2018 19:50:52 -0000

From RFC 7950, Section 7.20.2, first sentence:

   The "if-feature" statement makes its parent statement conditional.

Thus:

   feature aaa {
     if-feature bbb;
     ...
   }

means that feature "aaa" depends on feature "bbb".
The current text is correct.

Kent




The following errata report has been submitted for RFC6020,
"YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)".

--------------------------------------
You may review the report below and at:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rfc-2Deditor.org_errata_eid5272&d=DwIBaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=9zkP0xnJUvZGJ9EPoOH7Yhqn2gsBYaGTvjISlaJdcZo&m=m81-POMTB6oNRwO6oCG0H-5zqx1ntFjTc5LvGH3ETOk&s=I5ryVQtWDHP54-T1LaDmrDjZLlw8N1QThO5OoVQM2RI&e=

--------------------------------------
Type: Technical
Reported by: Bob Harold <rharolde@umich.edu>

Section: 7.18.1

Original Text
-------------
   In order for a device to implement a feature that is dependent on any
   other features (i.e., the feature has one or more "if-feature" sub-
   statements), the device MUST also implement all the dependant
   features.

Corrected Text
--------------
   In order for a device to implement a feature that is dependent on any
   other features (i.e. the feature is a sub-statement of another 
   "if-feature" statement), the device MUST also implement all the 
   dependent features.

Notes
-----
The direction of the dependency is stated backwards.
Consider for example:

if-feature aaa;
    statements ...;
    if-feature bbb;

This should allow feature aaa to exist without feature bbb.
bbb should depend on aaa, but aaa should not depend on bbb

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. 

--------------------------------------
RFC6020 (draft-ietf-netmod-yang-13)
--------------------------------------
Title               : YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Publication Date    : October 2010
Author(s)           : M. Bjorklund, Ed.
Category            : PROPOSED STANDARD
Source              : Network Modeling
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG