yang-ietf123
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| yang-ietf123 [2025/07/20 08:27] – sginoza | yang-ietf123 [2026/02/12 05:44] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| "pyang -f yang --keep-comments --yang-line-length 69" | "pyang -f yang --keep-comments --yang-line-length 69" | ||
| should be used.</ | should be used.</ | ||
| + | |||
| + | |||
| + | **Discussion (7/ | ||
| + | |||
| + | Conclusion: continue to use pyang to format | ||
| + | |||
| + | |||
| + | pyang not being actively maintained - still works but not being updated. | ||
| + | yanglint is more current compared with pyang. | ||
| + | |||
| + | Q: What checkers do YANG docs use? Do they rely on the datatracker? | ||
| + | A: No. They usually run their own checks. | ||
| + | |||
| + | Add link to wiki pointing to YANG template (template for drafting I-D with YANG).\\ | ||
| + | Add pointer from authors.ietf.org. \\ | ||
| + | Mahesh/Med to add pointer from YANG pages (from OPs wiki). \\ | ||
| ------------------------------ | ------------------------------ | ||
| Line 22: | Line 38: | ||
| 143 Version 2 Multicast Listener Report [RFC9777] | 143 Version 2 Multicast Listener Report [RFC9777] | ||
| </ | </ | ||
| + | |||
| + | |||
| + | Ideally, have authors and IANA use the same script to generate the modules of registries. Then do not need to edit or check the references. | ||
| + | |||
| + | Q: are there any IANA-maintained modules that are not of a registry? | ||
| + | A: don't think so. | ||
| Mahesh - a few different issues: | Mahesh - a few different issues: | ||
| Line 43: | Line 65: | ||
| These are some quick examples of possible issues with references in YANG modules for the meeting between RPC and YANG ODs during IETF 123 on 20 July 2025. | These are some quick examples of possible issues with references in YANG modules for the meeting between RPC and YANG ODs during IETF 123 on 20 July 2025. | ||
| + | |||
| + | **Discussion (7/ | ||
| + | |||
| + | Issues: | ||
| + | |||
| + | * Q: What should the intro text cover? | ||
| + | * A: should contain all RFCs that module is referencing, | ||
| + | * format: RFC XXXX: title, section. | ||
| + | |||
| + | need tool to check refs in module match intro text. | ||
| + | no currently defined guidance to authors on how to do intro text. | ||
| + | |||
| + | In addition to references already cited, this module also references/ | ||
| + | |||
| + | intentional: | ||
| + | - not enforcing that intro text be comprehensive | ||
| + | - allowing intro text to refer to IMPORTs and/or references | ||
| + | |||
| + | Need to clarify how it works if YANG modules are removed from RFC before publication. | ||
| + | Consider: if modules removed from the document, then they won't be read by the editor. | ||
| + | |||
| + | |||
| + | Reference format: | ||
| + | - add section number example to 8407bis | ||
| + | should not include " | ||
| + | |||
| ==== RFCs mentioned in introduction sentence - not referenced in YANG module ==== | ==== RFCs mentioned in introduction sentence - not referenced in YANG module ==== | ||
| Line 212: | Line 260: | ||
| RPC still needs check to catch these if author has not addressed the issue. | RPC still needs check to catch these if author has not addressed the issue. | ||
| How to check for this? | How to check for this? | ||
| + | |||
| + | How to actively notify draft authors? | ||
| + | - intended status notifications? | ||
| + | - referenced by notifications? | ||
| + | |||
yang-ietf123.1753000076.txt.gz · Last modified: (external edit)