Basic Standards
|
This section is currently a draft, and is subject to change. |
The Network Protocol is based on the XMPP Protocol (Extensible Messaging and Presence Protocol), which is maintained by the XMPP Standards Foundation (XSF) and Internet Engineering Task Force (IETF).
XMPP Standards
The Network Protocol is defined by the following basic XSF and IETF’s standards (Request for Comments, RFC):
-
RFC 6120 'Extensible Messaging and Presence Protocol (XMPP): Core', which specifies the XMPP Protocol as an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities. This document defines XMPP’s core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ('presence'), and request-response interactions. This document obsoletes RFC 3920.
-
RFC 6121 'Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence', which specifies extensions to core features of the XMPP Protocol that provide basic instant messaging (IM) and presence functionality in conformance with the requirements in RFC 2779. This document obsoletes RFC 3921.
-
RFC 7395 'An Extensible Messaging and Presence Protocol (XMPP) Subprotocol for WebSocket', which specifies a binding for the XMPP Protocol over a WebSocket transport layer. A WebSocket binding for XMPP provides higher performance than the current HTTP binding for XMPP.
-
RFC 7590 'Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)', which specifies the use of Transport Layer Security (TLS) in the XMPP Protocol. This document updates RFC 6120.
-
RFC 7622 'Extensible Messaging and Presence Protocol (XMPP): Address Format', which specifies the address format for the XMPP Protocol, including support for code points outside the ASCII range. This document partially obsoletes RFC 6122.
XMPP Guidelines
The Specification is arranged according to the following XSF’s standard guidelines (XMPP Extension Protocols, XEP):
-
XEP-0001 'XMPP Extension Protocols', which defines the standards process followed by the XMPP Standards Foundation.
-
XEP-0134 'XMPP Design Guidelines', which defines best practices for the intelligent design of Jabber/XMPP protocols and other XMPP extensions.
-
XEP-0143 'Guidelines for Authors of XMPP Extension Protocols', which provides information intended to assist authors of XMPP Extension Protocols.
-
XEP-0045 'Multi-User Chat', which specifies an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc.
-
XEP-0196 'User Gaming', which specifies an XMPP protocol extension for communicating information about the games a user plays.
-
XEP-xxxx 'Multi-User Gaming', which specifies an XMPP protocol extension for multi-user gaming.
XMPP Guidelines Notices
The Specification gives credit to the notices of the following XMPP Extension Protocols the DGA Game XMPP Network Protocol is based on.
XEP-0045: Multi-User Chat
Abstract This specification defines an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc. Authors
Peter Saint-Andre
Copyright
© 2002 – 2024 XMPP Standards Foundation.
Status
Stable
NOTICE: The protocol defined herein is a Stable Standard of the XMPP Standards Foundation. Implementations are encouraged and the protocol is appropriate for deployment in production systems, but some changes to the protocol are possible before it becomes a Final Standard.
Type
Standards Track
Version
1.35.1 (2024-09-17)
XEP-0196: User Gaming
Abstract This document defines an XMPP protocol extension for communicating information about the games a user plays. Authors
Peter Saint-Andre
Copyright
© 2006 – 2008 XMPP Standards Foundation.
Status
Deferred
WARNING: This document has been automatically Deferred after 12 months of inactivity in its previous Experimental state. Implementation of the protocol described herein is not recommended for production systems. However, exploratory implementations are encouraged to resume the standards process.
Type
Standards Track
Version
0.3 (2008-09-25)
XEP-xxxx: Multi-User Gaming
Abstract This document defines an XMPP protocol extension for multi-user gaming. Authors
Torsten Grote, Arne König, Günther Nieß
Copyright
© 2008 – 2009 XMPP Standards Foundation.
Status
ProtoXEP
WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document is not yet an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at https://xmpp.org/extensions/ and announced on the <standards@xmpp.org> mailing list.
Type
Standards Track
Version
0.0.3 (2009-04-20)
Want to help? Learn how to contribute to FLEISSF DGA Docs
