RFC 4979: IANA Registration for Enumservice 'XMPP'
In plain English — editorial summary, not part of the RFC
This document requests IANA registration of an Enumservice for XMPP, the Extensible Messaging and Presence Protocol. This Enumservice specifically allows the use of 'xmpp' Uniform Resource Identifiers (URIs) in the context of E.164 Number Mapping (ENUM). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4979
- Published
- August 2007
- Authors
- A. Mayrhofer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 7
- Also known as
- —
- Updated by:
- RFC 6118
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 4969IANA Registration for vCard EnumserviceUpdated
August 2007
- RFC 5076ENUM Validation Information Mapping for the Extensible Provisioning ProtocolCurrent
December 2007
- RFC 5105ENUM Validation Token Format DefinitionCurrent
December 2007
- RFC 4759The ENUM Dip Indicator Parameter for the "tel" URICurrent
December 2006
- RFC 4725ENUM Validation ArchitectureCurrent
November 2006
- RFC 5346Operational Requirements for ENUM-Based Softswitch UseCurrent
October 2008
- RFC 5483ENUM Implementation Issues and ExperiencesCurrent
March 2009
- RFC 6116The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Current
March 2011
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?