RFC 6122: Extensible Messaging and Presence Protocol (XMPP): Address Format
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7622.
Current version: RFC 7622 — Extensible Messaging and Presence Protocol (XMPP): Address Format
In plain English — editorial summary, not part of the RFC
This document defines the format for addresses used in the Extensible Messaging and Presence Protocol (XMPP), including support for non-ASCII characters. This document updates RFC 3920. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6122
- Published
- March 2011
- Authors
- P. Saint-Andre
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 23
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6120Extensible Messaging and Presence Protocol (XMPP): CoreUpdated
March 2011
- RFC 6121Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceCurrent
March 2011
- RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted
May 2014
- RFC 4854A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP)Current
April 2007
- RFC 7590Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)Current
June 2015
- RFC 3923End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)Current
October 2004
- RFC 3922Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)Current
October 2004
- RFC 3921Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceObsoleted
October 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?