% Datatracker information for RFCs on the Legacy Stream is unfortunately often
% incorrect. Please correct the bibtex below based on the information in the
% actual RFC at https://rfc-editor.org/rfc/rfc2278.txt

@misc{rfc2278,
    series =    {Request for Comments},
    number =    2278,
    howpublished =  {RFC 2278},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC2278},
    url =       {https://www.rfc-editor.org/info/rfc2278},
    author =    {Dr. Jon Postel and Ned Freed},
    title =     {{IANA Charset Registration Procedures}},
    pagetotal = 10,
    year =      1998,
    month =     jan,
    abstract =  {MIME {[}RFC-2045, RFC-2046, RFC-2047, RFC-2184{]} and various other modern Internet protocols are capable of using many different charsets. This in turn means that the ability to label different charsets is essential. This 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. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.},
}