% 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/rfc2781.txt

@misc{rfc2781,
    series =    {Request for Comments},
    number =    2781,
    howpublished =  {RFC 2781},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC2781},
    url =       {https://www.rfc-editor.org/info/rfc2781},
    author =    {Paul E. Hoffman and François Yergeau},
    title =     {{UTF-16, an encoding of ISO 10646}},
    pagetotal = 14,
    year =      2000,
    month =     feb,
    abstract =  {This document describes the UTF-16 encoding of Unicode/ISO-10646, addresses the issues of serializing UTF-16 as an octet stream for transmission over the Internet, discusses MIME charset naming as described in {[}CHARSET-REG{]}, and contains the registration for three MIME charset parameter values: UTF-16BE (big-endian), UTF-16LE (little- endian), and UTF-16. This memo provides information for the Internet community.},
}