%% You should probably cite rfc8126 instead of this I-D.
@techreport{leiba-cotton-iana-5226bis-01,
    number =    {draft-leiba-cotton-iana-5226bis-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/01/},
    author =    {Michelle Cotton and Barry Leiba and Dr. Thomas Narten},
    title =     {{Guidelines for Writing an IANA Considerations Section in RFCs}},
    pagetotal = 37,
    year =      2012,
    month =     oct,
    day =       2,
    abstract =  {Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (such as for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA. This document obsoletes RFC 5226.},
}