In RFC-to-be 9595, aka draft-ietf-core-yang-sid, we attempted to populate the SID ranges 2450 and 2500. This was originally done in draft-ietf-anima-constrained-voucher, but in the YANG revision process, we had to move the definition of these ranges to draft-ietf-anima-rfc8366bis.
An email went to chairs and AD, but I think it's better if it shows up on the mailing list. IANA asks: Amanda Baber via RT <[email protected]> wrote: > The RFC Editor has pointed out that RFC-to-be 9595, currently in > AUTH48, made two allocations for draft-ietf-anima-constrained-voucher > from the IETF YANG SID Range registry's "RFC Required" range. > It appears that we need to ask you to approve an RFC 7120 early > allocation for these registrations instead, so that they can be removed > from RFC-to-be 9595: > Entry Point Size Module Name Reference > 2450 50 ietf-constrained-voucher [draft-ietf-anima-constrained-voucher-22] > 2500 50 ietf-constrained-voucher-request [draft-ietf-anima-constrained-voucher-22] > Please see > https://www.iana.org/assignments/yang-sid > We have author Michael Richardson's agreement, but we need confirmation > from the AD and at least one chair to proceed. > If this is approved, we'll mark these assignments "TEMPORARY," set a > 2025 renewal date, and contact you about renewing on a yearly basis > until the document is approved. We would also need the authors to add a > subsection to the IANA Considerations that notes that these > registrations have been made.
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
