…applications using the Extensible Messaging and Presence Protocol (XMPP) (see [ RFC6120 ] and [ RFC6121 ]) on the Web have made use of Bidirectional-streams Over Synchronous HTTP (BOSH) (see [ XEP-0124 ] and [ XEP-0206 ]), an XMPP binding to HTTP. BOSH is based on the HTTP "long …

…applications using the Extensible Messaging and Presence Protocol (XMPP) (see [ RFC6120 ] and [ RFC6121 ]) on the Web have made use of Bidirectional-streams Over Synchronous HTTP (BOSH) (see XEP-0124 ] and [ XEP-0206 ]), an XMPP binding to HTTP. BOSH is based on the HTTP "long po…

… applications using the Extensible Messaging and Presence Protocol (XMPP) (see [RFC6120] and [RFC6121]) on the Web have made use of Bidirectional-streams Over Synchronous HTTP (BOSH) (see [XEP-0124] and [XEP-0206]), an XMPP binding to HTTP. BOSH is based on the HTTP "long polling…

…... 27 1 . Introduction The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] is an application profile of the Extensible Markup Language [ XML ] for streaming XML data in close to real time between any two or more network-aware entities. The address format for XMPP e…

…......27 1. Introduction The Extensible Messaging and Presence Protocol (XMPP) [RFC6120] is an application profile of the Extensible Markup Language [XML] for streaming XML data in close to real time between any two or more network-aware entities. The address format for XMPP enti…

…..... 27 . Introduction The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] is an application profile of the Extensible Markup Language [ XML ] for streaming XML data in close to real time between any two or more network-aware entities. The address format for XMPP e…

…..... 27 . Introduction The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] is an application profile of the Extensible Markup Language [ XML ] for streaming XML data in close to real time between any two or more network-aware entities. The address format for XMPP e…

… . . 9 1 . Introduction The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] (along with its precursor, the so-called "Jabber protocol") has used Transport Layer Security (TLS) [ RFC5246 ] (along with its precursor, Secure Sockets Layer or SSL) since 1999. Both [ RFC…

… . . . . . Introduction The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 (along with its precursor, the so-called "Jabber protocol") has used Transport Layer Security (TLS) [ RFC5246 ] (along with its precursor, Secure Sockets Layer or SSL) since 1999. Both [ RFC61…

… . . . 9 1. Introduction The Extensible Messaging and Presence Protocol (XMPP) [RFC6120] (along with its precursor, the so-called "Jabber protocol") has used Transport Layer Security (TLS) [RFC5246] (along with its precursor, Secure Sockets Layer or SSL) since 1999. Both [RFC6120…

… . . . . . Introduction The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 (along with its precursor, the so-called "Jabber protocol") has used Transport Layer Security (TLS) [ RFC5246 ] (along with its precursor, Secure Sockets Layer or SSL) since 1999. Both [ RFC61…

…ocol (RTP) [ RFC3550 ]. The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] also provides a signaling channel, typically via TCP (although bindings for HTTP [ XEP-0124 ] and WebSocket [ RFC7395 ] also exist). Given the significant differences between XMPP and SIP, t…

…nacRNfYi7SFHauX-Tl0WE/ 2240981 1674584 [xmpp] [Errata Held for Document Update] RFC6120 (4741) [xmpp] [Errata Held for Document Update] RFC6120 (4741) RFC Errata System 2016-07-13 xmpp /arch/msg/xmpp/3HxanDPOV3fLx60JzEcXjGpN3SI/ 2236320 1674585 [xmpp] [Technical Errata Reported] …

…ol (POP) [ RFC1939 ], and the Extensible Message and Presence Protocol (XMPP) [ RFC6120 ]. The effect is to make modular authentication, so that newer authentication mechanisms can be added as needed. This memo specifies just such a mechanism. The Generic Security Service Applica…

…as IMAP [ RFC3501 ] and the Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ]) and that directly reuse this profile MUST specify whether or not case mapping is to be applied to authorization identifiers. Such "SASL application protocols" SHOULD delay any case-mapping …