Note down text of a potential errata report about schema-node-path. - #171
Note down text of a potential errata report about schema-node-path.#171cabo wants to merge 1 commit into
Conversation
|
I wasn't aware of this PR yet, and would like to review! Can I be added as a reviewer? |
|
|
||
| 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"?) |
|
|
||
| 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"?) |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
|
I would also include a definition of the term "NID". I am not sure if we want to rewrite the text to use it, but proper definition might be handy. Even if it put it on some GitHub core-wg Wiki or GitHub Pages. The term is repeatedly used during discussion which may confuse newcomers. |
|
Shouldn't the |
|
Related issue #177, I am not sure how to correct identifier form of |
|
Please, firstly resolve the #181 |
5 participants
No description provided.