%% You should probably cite draft-iana-charset-reg-procedure-01 instead of this revision.
@techreport{iana-charset-reg-procedure-00,
    number =    {draft-iana-charset-reg-procedure-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-iana-charset-reg-procedure/00/},
    author =    {Mark McFadden and Alexey Melnikov},
    title =     {{IANA Charset Registration Procedures}},
    pagetotal = 13,
    year =      2014,
    month =     oct,
    day =       21,
    abstract =  {Multipurpose Internet Mail Extensions (MIME) (RFC-2045, RFC-2046, RFC-2047, RFC-2231) and various other Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This draft updates the IANA Charset Registration Procedures originally defined in {[}RFC2978{]}. Specifically, this document completely revises the registration procedures and the charset registries. The charset registry is now divided into three parts with separate registration procedures for each. Note: The charset registration procedure exists solely to associate a specific name or names with a given charset and to give an indication of whether or not a given charset can be used in MIME text objects. In particular, the general applicability and appropriateness of a given registered charset to a particular application is a protocol issue, not a registration issue, and is not dealt with by this registration procedure.},
}