Search results
Results from the WOW.Com Content Network
It is specified in a series of requests for comments: RFC 2045, RFC 2046, RFC 2047, RFC 4288, RFC 4289 and RFC 2049. The integration with SMTP email is specified in RFC 1521 and RFC 1522 . Although the MIME formalism was designed mainly for SMTP, its content types are also important in other communication protocols .
RFC 2045 RFC 2046 RFC 2047 RFC 2049 Network address translation: RFC 1631, RFC 2663, RFC 2993, RFC 3022, RFC 3027, RFC 3234, RFC 3489, RFC 4787, RFC 5389 Network File System: RFC 1094, RFC 1813 (v.3), RFC 3010 (v.4), RFC 3530 (v.4) Network News Transfer Protocol: RFC 977, RFC 3977 Network Time Protocol
RFC 2047 provides support for encoding non-ASCII values such as real names and subject lines in email headers [4] RFC 5890 provides support for encoding non-ASCII domain names in the Domain Name System [5] RFC 6532 allows the use of UTF-8 in a mail header section [6]
The RFC series contains three sub-series for IETF RFCs: BCP, FYI, and STD. Best Current Practice (BCP) is a sub-series of mandatory IETF RFCs not on standards track. For Your Information (FYI) is a sub-series of informational RFCs promoted by the IETF as specified in RFC 1150 (FYI 1). In 2011, RFC 6360 obsoleted FYI 1 and concluded this sub-series.
When an RFC becomes an Internet Standard (STD), it is assigned an STD number but retains its RFC number. When an Internet Standard is updated, its number is unchanged but refers to a different RFC or set of RFCs. For example, in 2007 RFC 3700 was an Internet Standard (STD 1) and in May 2008 it was replaced with RFC 5000.
RFC 3977 [7] specifies that "NNTP operates over any reliable bi-directional 8-bit-wide data stream channel", and changes the character set for commands to UTF-8. However, RFC 5536 [8] still limits the character set to ASCII, including RFC 2047 [9] and RFC 2231 [10] MIME encoding of non-ASCII data.
The term electronic mail has been in use with its modern meaning since 1975, and variations of the shorter E-mail have been in use since 1979: [2] [3] email is now the common form, and recommended by style guides. [4] [5] [6] It is the form required by IETF Requests for Comments (RFC) and working groups. [7] This spelling also appears in most ...
RFC 792: 0x02 2 IGMP Internet Group Management Protocol: RFC 1112: 0x03 3 GGP Gateway-to-Gateway Protocol: RFC 823: 0x04 4 IP-in-IP IP in IP (encapsulation) RFC 2003: 0x05 5 ST Internet Stream Protocol: RFC 1190, RFC 1819: 0x06 6 TCP Transmission Control Protocol: RFC 793: 0x07 7 CBT Core-based trees: RFC 2189: 0x08 8 EGP Exterior Gateway ...