CARVIEW |
Select Language
HTTP/2 200
date: Wed, 16 Jul 2025 06:30:56 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=hksdnge6mjcjvbgujc67nsvplh; 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: 95ff7423ff5125c9-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: 4292
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Cesar Crusius
Date Reported: 2015-03-07
Verifier Name: Benoit Claise
Date Verified: 2015-03-10
Section 12 says:
type-stmt = type-keyword sep identifier-ref-arg-str optsep (";" / "{" stmtsep type-body-stmts "}")
It should say:
type-stmt = type-keyword sep identifier-ref-arg-str optsep (";" / "{" stmtsep [ type-body-stmts ] "}")
Notes:
Every statement that can end with a single ';' should also accept ending with '{ stmtsep }' (that is what the 'stmtend' rule implies). This is the only instance I found so far of a statement that does not follow this rule.
The other option would be to replace all ";" in rules like that with 'stmtend'.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us