…ocol (POP) [ RFC1939 ], and Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ], with the goal of modularizing authentication and security layers, so that newer mechanisms can be added as needed. This memo specifies just such a mechanism. The Generic Security Service Ap…

… like SIP or something like Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ]. +--------------+ +--------------+ | | SIP,XMPP,...| | | Web Server |<----------->| Web Server | | | | | +--------------+ +--------------+ ^ ^ | | HTTP | | HTTP | | v v JS API JS API +------…

…hich defines usage with the Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] ). However, some of the examples in the document use SDP and the Offer/Answer model [ RFC3264 ] to explain the underlying concepts. ¶ The following diagram illustrates a successful Trickle I…

…ting application protocol definition (one example is [TLS-XMPP], which updates [RFC6120]). Designers of new application protocols developed through the Internet Standards Process [RFC2026] are expected at minimum to conform to the best practices recommended here, unless they prov…

…, vCards are currently used in the Extensible Messaging and Presence Protocol [ RFC6120 ] to represent instant messaging servers that are deployed on the network. The properties included in an application's vCard apply to one of the following: o The application itself (e.g., the …

…hich defines usage with the Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] ). However, some of the examples in the document use SDP and the Offer/Answer model [ RFC3264 ] to explain the underlying concepts. ¶ The following diagram illustrates a successful Trickle I…

…e your TLS library doesn't support extracting channel binding information)]." [ RFC6120 . SHOULD CONSIDER The phrase "SHOULD CONSIDER" indicates that the authors of the specification think that implementations should do something, but they're not sure quite what. For example: "Ap…

…he developers of extensions to the Extensible Messaging and Presence Protocol [ RFC6120 ] in the case of the "XMPP" URN namespace [ RFC4854 ]). Because the colon character (":") is used to separate "urn" from the NID and the NID from the NSS, it's tempting to think of the entire …

…he developers of extensions to the Extensible Messaging and Presence Protocol [ RFC6120 ] in the case of the "XMPP" URN namespace [ RFC4854 ]). Because the colon character (":") is used to separate "urn" from the NID and the NID from the NSS, it's tempting to think of the entire …

…he developers of extensions to the Extensible Messaging and Presence Protocol [ RFC6120 ] in the case of the "XMPP" URN namespace [ RFC4854 ]). Because the colon character (":") is used to separate "urn" from the NID and the NID from the NSS, it's tempting to think of the entire …

… and little recourse. ¶ The Extensible Messaging and Presence Protocol (XMPP) [ RFC6120 ] is a chat protocol that demonstrates another issue with federation: the voluntary nature of technical standards. ¶ Like email, XMPP is federated to facilitate the rendezvous of users from di…

…proxy. Likewise, CoAP could equally be proxied to other protocols such as XMPP [RFC6120] or SIP [RFC3264]; the definition of these mechanisms is out of scope for this specification. Shelby, et al. Standards Track [Page 74] RFC 7252 The Constrained Application Protocol (CoAP) June…

… length>N</data length> <meaning>XMPP Servers DHCP Option</meaning> <reference>[RFC6120]</reference> 3.3.2 Multicast DNS (mDNS) and DNS Service Discovery (DNS-SD) An introduction of mDNS/DNS-SD (e.g., how it works and terminology) is described in Link-Local Messaging (XEP-0174) ]…