Skip to content

Note down text of a potential errata report about schema-node-path. #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cabo wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Note down text of a potential errata report about schema-node-path. #171

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 43 additions & 0 deletions errata-sid/rfc9595-errata-report-schema-node-path.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
In:
typedef schema-node-path {

OLD:

"A schema-node path is an absolute YANG schema-node
identifier as defined by the YANG ABNF rule
'absolute-schema-nodeid', except that module names are used
instead of prefixes.

NEW:

"A schema-node path is an absolute YANG schema-node
identifier as defined by the YANG ABNF rule
'absolute-schema-nodeid', except that module names are used
instead of prefixes. In addition, choice and case schema nodes
are not represented in a path string.

In:

list item {

OLD:

description
"Each entry within this list defines the mapping between
a YANG item string identifier and a YANG SID. This list
MUST include a mapping entry for each YANG item defined
by the YANG module identified by 'module-name' and
'module-revision'.";

NEW:

description
"Each entry within this list defines the mapping between
a YANG item string identifier and a YANG SID. This list
MUST include a mapping entry for each YANG item defined
by the YANG module identified by 'module-name' and
'module-revision'. YANG choice and case nodes are not included.

Note that both changes simply add a single sentence at the end of the description.

(Should there be a change to "revision 2024-07-31"?)

@cabo cabo Mar 20, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably.

@EskoDijk EskoDijk Mar 20, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, any changes lead to a new YANG module revision. And each revision needs an additional 'revision' statement that's added on top of the existing one. So it would look like e.g.:

revision 2026-03-20 {
    description
      "Updates per errata report NNN.";
    reference
      "Errata report NNN <link>";
 }

revision 2024-07-31 {
    description
      "Initial revision.";
    reference
      "RFC 9595: YANG Schema Item iDentifier (YANG SID)";
  }

Also the new module needs to be manually submitted to the IETF YANG modules repository, in case we don't have a draft from which the YANG module gets auto-extracted by the tools.

@abierman abierman Mar 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

goog catch/

This is a new procedure
IANA will maintain new YANG revisions with Errata.
The link to this new module should be on the RFC page I guess. Not just Errata Exists.
tooling challenge: how to propagate IANA updates like this?