…I Standard [ RFC3986 ] and a number of application specifications (e.g., SMTP [ RFC5321 ] and HTTP [ RFC2616 ]) do not permit non-ASCII labels in DNS names used with those protocols, i.e., only the A-label form of IDNs is permitted in those contexts. If only A-labels are used, di…
…rms 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 this document…
…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…
…text of status notifications is specified at the end of this section. An SMTP [ RFC5321 ] server that advertises both the SMTPUTF8 extension RFC6531 ] and the DSN extension [ RFC3461 ] MUST accept a UTF-8 address type in the ORCPT parameter including 8-bit UTF-8 characters. This …
…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 Fette & Melnikov Standards Track [Page 10] RFC 6455 The WebSocket Protocol December 2011 desired. This is achiev…
…text of status notifications is specified at the end of this section. An SMTP [ RFC5321 ] server that advertises both the SMTPUTF8 extension RFC6531 ] and the DSN extension [ RFC3461 ] MUST accept a UTF-8 address type in the ORCPT parameter including 8-bit UTF-8 characters. This …
…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…