IANA Registration for Enumservice 'XMPP'
RFC 4979
| Document | Type |
RFC - Proposed Standard
(August 2007; No errata)
Updated by RFC 6118
Was draft-ietf-enum-xmpp (enum WG)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Replaces | draft-mayrhofer-enum-xmpp | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 4979 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Jon Peterson | ||
| Send notices to | (None) | ||
Network Working Group A. Mayrhofer
Request for Comments: 4979 enum.at
Category: Standards Track August 2007
IANA Registration for Enumservice 'XMPP'
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
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).
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Enumservice Registration - XMPP . . . . . . . . . . . . . . . . 2
4. XMPP IRI/URI Considerations for ENUM . . . . . . . . . . . . . 3
4.1. Authority Component . . . . . . . . . . . . . . . . . . . . 3
4.2. IRI-to-URI mapping . . . . . . . . . . . . . . . . . . . . 3
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Security and Privacy Considerations . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . . 5
9.2. Informative References . . . . . . . . . . . . . . . . . . 5
Mayrhofer Standards Track [Page 1]
RFC 4979 XMPP Enumservice August 2007
1. Introduction
E.164 Number Mapping (ENUM) [1] uses the Domain Name System (DNS) [6]
to refer from E.164 numbers [7] to Uniform Resource Identifiers
(URIs) [3]. Specific services to be used with ENUM must be
registered with IANA. Section 3 of RFC 3761 describes the process of
such an Enumservice registration.
The Extensible Messaging and Presence Protocol (XMPP) [9] provides
means for streaming Extensible Markup Language (XML) [8] elements
between endpoints in close to real time. The XMPP framework is
mainly used to provide instant messaging, presence, and streaming
media services.
RFC 4622 [5] registers a Uniform Resource Identifier (URI) scheme for
identifying an XMPP entity as a URI or as an Internationalized
Resource Identifier (IRI) [4]. The Enumservice specified in this
document allows the provisioning of such "xmpp" URIs (and the URI
representations of "xmpp" IRIs) in ENUM.
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [2].
3. Enumservice Registration - XMPP
The following template contains information required for the IANA
registrations of the 'XMPP' Enumservice, according to Section 3 of
RFC 3761:
Enumservice Name: "XMPP"
Enumservice Type: "xmpp"
Enumservice Subtype: n/a
URI Schemes: "xmpp"
Functional Specification:
This Enumservice indicates that the resource identified is an XMPP
entity.
Security Considerations: see Section 6
Mayrhofer Standards Track [Page 2]
RFC 4979 XMPP Enumservice August 2007
Intended Usage: COMMON
Author: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
4. XMPP IRI/URI Considerations for ENUM
4.1. Authority Component
XMPP IRIs/URIs optionally contain an "Authority Component" (see
Section 2.3 of RFC 4622). The presence of such an Authority
Component in an IRI/URI signals the processing application to
authenticate as the user indicated in the URI/IRI rather than using
the preconfigured identity.
In the context of this Enumservice, arbitrary clients may discover
and use the XMPP URIs/IRIs associated to an E.164 number. Hence, in
Show full document text