2011
DOI: 10.17487/rfc6121
|View full text |Cite
|
Sign up to set email alerts
|

Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
94
0
1

Year Published

2011
2011
2015
2015

Publication Types

Select...
6
2
1

Relationship

1
8

Authors

Journals

citations
Cited by 141 publications
(95 citation statements)
references
References 1 publication
0
94
0
1
Order By: Relevance
“…CoAP is built on the top of User Datagram Protocol (UDP) and follows a request-response paradigm; -Extensible Messaging and Presence Protocol (XMPP) [18]; -MQ Telemetry Transport (MQTT) protocol [19]: a lightweight publish/subscribe protocol flowing over TCP/IP for remote sensors and control devices through low bandwidth, unreliable, or intermittent communications; -Constrained Session Initiation Protocol (CoSIP) [20,21]: a version of the Session Initiation Protocol (SIP) [22] aiming at allowing constrained devices to instantiate communication sessions in a lightweight and standard fashion. Session instantiation can include a negotiation phase of some parameters which will be used for all subsequent communication.…”
Section: Iot Protocols and Modelsmentioning
confidence: 99%
“…CoAP is built on the top of User Datagram Protocol (UDP) and follows a request-response paradigm; -Extensible Messaging and Presence Protocol (XMPP) [18]; -MQ Telemetry Transport (MQTT) protocol [19]: a lightweight publish/subscribe protocol flowing over TCP/IP for remote sensors and control devices through low bandwidth, unreliable, or intermittent communications; -Constrained Session Initiation Protocol (CoSIP) [20,21]: a version of the Session Initiation Protocol (SIP) [22] aiming at allowing constrained devices to instantiate communication sessions in a lightweight and standard fashion. Session instantiation can include a negotiation phase of some parameters which will be used for all subsequent communication.…”
Section: Iot Protocols and Modelsmentioning
confidence: 99%
“…Thus, an XFormsRTC client can send and receive data to/from an RTC server over HTTP or WebSocket. Furthermore, it is possible to use special application-level protocols, such as XMPP [49][50][51]; defined by the optional subprotocol attribute. Indeed, Pohja [45] proposes that HTTP communication should be complemented with XMPP in order to meet the communication requirements of modern Web Applications.…”
Section: Xformsrtcmentioning
confidence: 99%
“…As defined in the XMPP Multi-User Chat (MUC) specification [XEP-0045], when an XMPP user (say, "juliet@example.com") wants to join a groupchat room (say, "montague@chat.example.org"), she sends a directed <presence/> stanza [RFC6121] to that chat room. In her request she also specifies the nickname she wants to use within the room (say, "JuliC"); in XMPP this room nickname is the resourcepart of an occupant JID (thus "montague@chat.example.org/JuliC").…”
Section: Enter Roommentioning
confidence: 99%