rfc9595v15.txt | rfc9595.txt | |||
---|---|---|---|---|
skipping to change at line 1115 ¶ | skipping to change at line 1115 ¶ | |||
3. The range of 60,000 to 99,999 (size 40,000) is reserved for | 3. The range of 60,000 to 99,999 (size 40,000) is reserved for | |||
experimental YANG modules. This range MUST NOT be used in | experimental YANG modules. This range MUST NOT be used in | |||
operational deployments, since these SIDs are not globally unique | operational deployments, since these SIDs are not globally unique | |||
and their interoperability is therefore limited. The IANA policy | and their interoperability is therefore limited. The IANA policy | |||
for this range is "Experimental Use" (Section 4.2 of RFC 8126 | for this range is "Experimental Use" (Section 4.2 of RFC 8126 | |||
[BCP26]). | [BCP26]). | |||
4. The range of 300,000 to 999,999 (size 700,000) is "Reserved" as | 4. The range of 300,000 to 999,999 (size 700,000) is "Reserved" as | |||
defined in Section 6 of RFC 8126 [BCP26]. | defined in Section 6 of RFC 8126 [BCP26]. | |||
+=============+=========+=================================+ | +=============+=========+=============================+ | |||
| Entry Point | Size | IANA Policy | | | Entry Point | Size | IANA Policy | | |||
+=============+=========+=================================+ | +=============+=========+=============================+ | |||
| 0 | 1,000 | IESG Approval | | | 0 | 1,000 | IESG Approval | | |||
+-------------+---------+---------------------------------+ | +-------------+---------+-----------------------------+ | |||
| 1,000 | 59,000 | RFC Required (see item 2 above) | | | 1,000 | 59,000 | RFC and Expert Review | | |||
+-------------+---------+---------------------------------+ | | | | Required (see item 2 above) | | |||
| 60,000 | 40,000 | Reserved for Experimental Use | | +-------------+---------+-----------------------------+ | |||
+-------------+---------+---------------------------------+ | | 60,000 | 40,000 | Reserved for Experimental | | |||
| 100,000 | 200,000 | RFC Required (see item 2 above) | | | | | Use | | |||
+-------------+---------+---------------------------------+ | +-------------+---------+-----------------------------+ | |||
| 300,000 | 700,000 | Reserved | | | 100,000 | 200,000 | RFC and Expert Review | | |||
+-------------+---------+---------------------------------+ | | | | Required (see item 2 above) | | |||
+-------------+---------+-----------------------------+ | ||||
| 300,000 | 700,000 | Reserved | | ||||
+-------------+---------+-----------------------------+ | ||||
Table 3: IETF YANG-SID Ranges Registry: Policies for | Table 3: IETF YANG-SID Ranges Registry: Policies | |||
IETF Ranges | for IETF Ranges | |||
The size of the SID range allocated for a YANG module is recommended | The size of the SID range allocated for a YANG module is recommended | |||
to be a multiple of 50 and to be at least 33% above the current | to be a multiple of 50 and to be at least 33% above the current | |||
number of YANG items. This headroom allows assignments within the | number of YANG items. This headroom allows assignments within the | |||
same range of new YANG items introduced by subsequent revisions. The | same range of new YANG items introduced by subsequent revisions. The | |||
SID range size SHOULD NOT exceed 1,000; a larger size may be | SID range size SHOULD NOT exceed 1,000; a larger size may be | |||
requested by the authors if this recommendation is considered | requested by the authors if this recommendation is considered | |||
insufficient. It is important to note that an additional SID range | insufficient. It is important to note that an additional SID range | |||
can be allocated to an existing YANG module if the initial range is | can be allocated to an existing YANG module if the initial range is | |||
exhausted; this then just leads to a slightly less efficient | exhausted; this then just leads to a slightly less efficient | |||
End of changes. 2 change blocks. | ||||
15 lines changed or deleted | 18 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |