CARVIEW |
Select Language
HTTP/2 200
date: Fri, 10 Oct 2025 07:44:24 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=N3phWTQwLxQ7Aqklo_Q4sgGMPZp_ZU8Xj5UD9deMXrw-1760082264-1.0.1.1-500GSvsY9N9jNxCQfO4jiE3toHkd.tQe0EIarnvSJlXDt3CagxZAyY9F35YSx1IffJEYAUicsyS4NTlOPu7qpZEvAf01h0Tj1X8kbcFxwN8; path=/; expires=Fri, 10-Oct-25 08:14:24 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c47e051a90c172-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6122 » RFC Editor
Search RFCs
RFC 6122
Extensible Messaging and Presence Protocol (XMPP): Address Format, March 2011
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 7622
- Updates:
- RFC 3920
- Author:
- P. Saint-Andre
- Stream:
- IETF
- Source:
- xmpp (rai)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6122
Discuss this RFC: Send questions or comments to the mailing list xmpp@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6122
Abstract
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us