…il to establish a connection with servers of pre-existing protocols like SMTP [ RFC5321 ] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achie…

…ail to establish a connection with servers of pre-existing protocols like SMTP [RFC5321] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if desired. This is achieved by having a strict and elaborate handshake and by limiting the data that can be insert…

… used in this specification are defined in the EAI overview [ RFC4952 ] or in [ RFC5321 ], [ RFC5322 ], or the MIME documents RFC2045 ], [ RFC2047 ], [ RFC2183 ], and [ RFC2231 ]. This document depends on [ RFC5335 ] and [ RFC5504 ]. Key words used in those documents are used in …

…il to establish a connection with servers of pre-existing protocols like SMTP [ RFC5321 ] and HTTP, while allowing HTTP servers to opt-in to supporting this protocol if Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achie…

…locations or becomes disconnected for a long period. To facilitate this, SMTP [ RFC5321 ] defines a specific role for routing users' messages, the Message Transfer Agent (MTA). By allowing anyone to deploy an MTA and defining rules for interconnecting them, the protocol avoids a …

…2020-04-01 Section .6 says: domain-name = sub-domain 1*("." sub-domain) ; from [RFC5321] Domain, ; excluding address-literal It should say: domain-name = sub-domain 1*("." sub-domain) ; from [RFC5321] Domain Notes: In RFC5321 "domain" does not include address-literal. This mistak…

…2020-04-01 Section .6 says: domain-name = sub-domain 1*("." sub-domain) ; from [RFC5321] Domain, ; excluding address-literal It should say: domain-name = sub-domain 1*("." sub-domain) ; from [RFC5321] Domain Notes: In RFC5321 "domain" does not include address-literal. This mistak…