%% You should probably cite draft-kucherawy-bcp97bis-04 instead of this revision.
@techreport{kucherawy-bcp97bis-01,
    number =    {draft-kucherawy-bcp97bis-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-kucherawy-bcp97bis/01/},
    author =    {Murray Kucherawy},
    title =     {{Procedures for Standards Track Documents to Refer Normatively to Documents at a Lower Level}},
    pagetotal = 10,
    year =      2021,
    month =     oct,
    day =       18,
    abstract =  {IETF procedures generally require that a standards track RFC may not have a normative reference to another standards track document at a lower maturity level or to a non standards track specification (other than specifications from other standards bodies). For example, a standards track document may not have a normative reference to an informational RFC. Exceptions to this rule are sometimes needed as the IETF uses informational RFCs to describe non-IETF standards or IETF-specific modes of use of such standards. This document defines the procedure used in these circumstances. This document merges and updates, and thus obsoletes, RFC 3967, RFC 4897, and RFC 8067.},
}