rfc9595v13.txt | rfc9595.txt | |||
---|---|---|---|---|
skipping to change at line 1188 ¶ | skipping to change at line 1188 ¶ | |||
and for the best achievable consistency with the existing draft | and for the best achievable consistency with the existing draft | |||
".sid" file. | ".sid" file. | |||
The designated experts then give the ".sid" file to IANA to publish | The designated experts then give the ".sid" file to IANA to publish | |||
in the "IETF YANG-SID Modules" registry (Section 6.5) along with the | in the "IETF YANG-SID Modules" registry (Section 6.5) along with the | |||
YANG module. | YANG module. | |||
The ".sid" file MUST NOT be published as part of the RFC: the IANA | The ".sid" file MUST NOT be published as part of the RFC: the IANA | |||
registry is authoritative, and a link to it is to be inserted in the | registry is authoritative, and a link to it is to be inserted in the | |||
RFC. (Note that the present RFC is an exception to this rule, as the | RFC. (Note that the present RFC is an exception to this rule, as the | |||
".sid" file also serves as an example for exposition.) RFCs that | ".sid" file also serves as an example for exposition.) Internet- | |||
need SIDs assigned to their new modules for use in the text of the | Drafts that need SIDs assigned to their new modules for use in the | |||
document, e.g., for examples, need to alert the RFC Editor in the | text of the document, e.g., for examples, need to alert the RFC | |||
draft text that this is the case. Such RFCs cannot be produced by | Editor in the draft text that this is the case. Such RFCs cannot be | |||
type-3 (SID-oblivious) developers: the SIDs used in the text need to | produced by type-3 (SID-oblivious) developers: the SIDs used in the | |||
be assigned in the existing draft ".sid" file, and the designated | text need to be assigned in the existing draft ".sid" file, and the | |||
expert team needs to check that the assignments in the final ".sid" | designated expert team needs to check that the assignments in the | |||
file are consistent with the usage in the RFC text or that the | final ".sid" file are consistent with the usage in the RFC text or | |||
approved draft text is changed appropriately. | that the approved draft text is changed appropriately. | |||
6.4.4. Initial Contents of the Registry | 6.4.4. Initial Contents of the Registry | |||
Initial entries in this registry are as follows: | Initial entries in this registry are as follows: | |||
+=============+======+=============================+=============+ | +=============+======+=============================+=============+ | |||
| Entry Point | Size | Module Name | Reference | | | Entry Point | Size | Module Name | Reference | | |||
+=============+======+=============================+=============+ | +=============+======+=============================+=============+ | |||
| 0 | 1 | (Reserved: not a valid SID) | RFC 9595 | | | 0 | 1 | (Reserved: not a valid SID) | RFC 9595 | | |||
+-------------+------+-----------------------------+-------------+ | +-------------+------+-----------------------------+-------------+ | |||
skipping to change at line 1296 ¶ | skipping to change at line 1296 ¶ | |||
Due to the difficulty in changing SID values during IETF document | Due to the difficulty in changing SID values during IETF document | |||
processing, it is expected that most documents will ask for SID range | processing, it is expected that most documents will ask for SID range | |||
allocations using Early Allocations [BCP100]. The details of the | allocations using Early Allocations [BCP100]. The details of the | |||
Early Allocation to be requested, including the timeline envisioned, | Early Allocation to be requested, including the timeline envisioned, | |||
should be included in any working group adoption call. Prior to | should be included in any working group adoption call. Prior to | |||
working group adoption, an Internet-Draft author can use the | working group adoption, an Internet-Draft author can use the | |||
experimental SID range (as per Section 6.4.2) for their SID | experimental SID range (as per Section 6.4.2) for their SID | |||
allocations or other values that do not create ambiguity with other | allocations or other values that do not create ambiguity with other | |||
SID uses (for example, they can use ranges and SIDs registered in a | SID uses (for example, they can use ranges and SIDs registered in a | |||
non-IANA-managed registry that is based on a YANG-SID mega-range | non-IANA-managed registry that is based on a YANG-SID Mega-Range | |||
assignment). | assignment). | |||
After working group adoption, any modification of a ".sid" file is | After working group adoption, any modification of a ".sid" file is | |||
expected to be discussed on the mailing lists of the appropriate | expected to be discussed on the mailing lists of the appropriate | |||
working groups. Specific attention should be paid to implementers' | working groups. Specific attention should be paid to implementers' | |||
opinions after Working Group Last Call if a SID value is to change | opinions after Working Group Last Call if a SID value is to change | |||
its meaning. In all cases, a ".sid" file and the SIDs associated | its meaning. In all cases, a ".sid" file and the SIDs associated | |||
with it are subject to change before the publication of an Internet- | with it are subject to change before the publication of an Internet- | |||
Draft as an RFC. | Draft as an RFC. | |||
End of changes. 2 change blocks. | ||||
10 lines changed or deleted | 10 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |