CARVIEW |
Select Language
HTTP/2 200
date: Wed, 16 Jul 2025 14:09:13 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=vl8nvmh3ooo8o9nc095hhnr1en; path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 96021372a972b1e7-BOM
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
See Also: RFC 6020 w/ inline errata
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
RFC 6020, "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", October 2010
Source of RFC: netmod (ops)See Also: RFC 6020 w/ inline errata
Errata ID: 3872
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Jonathan Hansford
Date Reported: 2014-01-23
Verifier Name: Benoit Claise
Date Verified: 2014-02-01
Section 9.7.4.2 says:
If a bit position is not specified, then one will be automatically assigned. If the "bit" substatement is the first one defined, the assigned value is zero (0); otherwise, the assigned value is one greater than the current highest bit position.
It should say:
If a bit position is not specified, then one will be automatically assigned. If the "bit" substatement is the first one defined, the assigned value is zero (0); otherwise, the assigned value is one greater than the current highest bit position (that is, the highest bit position, implicit or explicit, prior to the current "bit" substatement in the parent "type" statement).
Notes:
Clarification that 'current highest' does not refer to all bit positions, implicit or explicit, in the parent "type" statement but only to those that precede the current "bit" substatement.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us