IANA Registration for Enumservice 'XMPP'
updated by
- rfc-6118 — Update of Legacy IANA Registrations of Enumservices
Extracted elements (12)
ENUM itself only supports URIs (not IRIs) for Enumservices, necessitating an IRI-to-URI mapping step when provisioning XMPP resources that may be identified by IRIs.
The Authority Component in XMPP IRIs/URIs signals the processing application to authenticate as the user indicated. In ENUM context, arbitrary clients discover these URIs and cannot typically fulfill that authentication, making the Authority Component inappropriate for ENUM-published XMPP URIs.
The ENUM record itself does not need to contain any personal information—it just points to a location where access to personal information could be granted. This allows deployments to publish XMPP reachability without necessarily exposing personal data in the record.
While XMPP supports both IRIs and plain URIs, ENUM Enumservices only support URIs; implementations must perform IRI-to-URI conversion per RFC 3987 Section 3.1 before publishing XMPP identifiers in ENUM.
The IRI-to-URI mapping for XMPP Enumservice records MUST follow the procedures outlined in Section 3.1 of RFC 3987.
URIs/IRIs that result from processing an XMPP Enumservice record SHOULD NOT contain an Authority Component, because arbitrary clients discovering the URI will typically not be able to authenticate as the user indicated in the Authority Component.
XMPP IRIs MUST be mapped to URIs for use in an XMPP Enumservice record, since ENUM supports only URIs for Enumservices.
Information published in ENUM records could reveal associations between E.164 numbers and their owners, especially if IRIs/URIs contain personal identifiers or domain names for which ownership information can be obtained easily.
The XMPP Enumservice has Enumservice Type 'xmpp' with no subtype, and uses 'xmpp' URI schemes as defined in RFC 4622. Intended usage is COMMON.
This document registers a new 'XMPP' Enumservice (type 'xmpp', no subtype) in the IANA 'Enumservice Registrations' registry. The Enumservice indicates that the resource identified is an XMPP entity, using 'xmpp' URI schemes.
ENUM records pointing to third-party resources can be provisioned by the ENUM domain owner, meaning any assumption about the association between a number and an entity could be bogus unless identity verification is in place; such verification is out of scope for this document.
Since ENUM uses DNS—a publicly available database—any information in ENUM records must be considered public. Even after revoking a DNS entry, copies of the information could remain available.