%% You should probably cite draft-ietf-core-yang-sid-pen-06 instead of this revision.
@techreport{ietf-core-yang-sid-pen-05,
    number =    {draft-ietf-core-yang-sid-pen-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-core-yang-sid-pen/05/},
    author =    {Carsten Bormann},
    title =     {{YANG-CBOR: Allocating SID ranges for PEN holders}},
    pagetotal = 8,
    year =      2025,
    month =     dec,
    day =       18,
    abstract =  {YANG-CBOR (RFC 9254, "Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR)") defines YANG Schema Item iDentifiers (YANG SID), globally unique 63-bit unsigned integers used to identify YANG items. RFC 9595 ("YANG Schema Item iDentifier (YANG SID)") defines ways to allocate these SIDs on the basis of IANA registries. The present specification employs these SID allocation mechanisms to allocate ranges with 100 000 SIDs (representation size 64 bits) each for each of the holders of IANA-registered Private Enterprise Numbers (PENs) \textless{} 1 000 000, as well as ranges with 10 000 SIDs (representation size 32 bits) each for each of the holders of PENs \textless{} 100 000. // The present revision \textendash{}05 is intended to address the feedback from // the directorate reviews and early IESG feedback, in time for the // IESG meeting. It also adds cached information to work around the // regression in the bib.ietf.org service (https://github.com/ietf- // tools/bibxml- service/issues/489 (https://github.com/ietf-tools/ // bibxml-service/ issues/489)) that caused the reference // {[}IANA.enterprise-numbers{]} to come out as "*** BROKEN REFERENCE // ***" in some CI systems.},
}