@techreport{kucherawy-rfc3967bis-00,
    number =    {draft-kucherawy-rfc3967bis-00},
    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-rfc3967bis/00/},
    author =    {Murray Kucherawy},
    title =     {{Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level}},
    pagetotal = 6,
    year =      2015,
    month =     jul,
    day =       20,
    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 clarifies and updates the procedure used in these circumstances.},
}