enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record
RFC 3764
Document | Type |
RFC - Proposed Standard
(April 2004; No errata)
Updated by RFC 6118
Was draft-ietf-enum-sip (enum WG)
|
|
---|---|---|---|
Last updated | 2015-10-14 | ||
Replaces | draft-peterson-enum-sip | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3764 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Allison Mankin | ||
Send notices to | (None) |
Network Working Group J. Peterson Request for Comments: 3764 NeuStar Category: Standards Track April 2004 enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record 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 Internet Society (2004). All Rights Reserved. Abstract This document registers an Electronic Number (ENUM) service for the Session Initiation Protocol (SIP), pursuant to the guidelines in RFC 3761. Specifically, this document focuses on provisioning SIP addresses-of-record in ENUM. Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. ENUM Service Registration . . . . . . . . . . . . . . . . . . . 2 3. Addresses-of-record in SIP. . . . . . . . . . . . . . . . . . . 3 4. The 'E2U+SIP' enumservice . . . . . . . . . . . . . . . . . . . 5 5. Example of E2U+SIP enumservice. . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 8. References. . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References. . . . . . . . . . . . . . . . . . . 6 8.2. Informative References. . . . . . . . . . . . . . . . . . 7 9. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . 7 10. Author's Address. . . . . . . . . . . . . . . . . . . . . . . . 7 11. Full Copyright Statement. . . . . . . . . . . . . . . . . . . . 8 Peterson Standards Track [Page 1] RFC 3764 SIP enumservice April 2004 1. Introduction ENUM (E.164 Number Mapping, RFC 2916 [6]) is a system that uses DNS (Domain Name Service, STD 13, RFC 1034 [3]) to translate telephone numbers, like '+12025332600', into URIs (Uniform Resource Identifiers, RFC 2396 [4]), like 'sip:egar@example.com'. ENUM exists primarily to facilitate the interconnection of systems that rely on telephone numbers with those that use URIs to route transactions. This document applies to the revised version of ENUM described in RFC 3761. SIP (Session Initiation Protocol, RFC 3261 [2]) is a text-based application protocol that allows endpoints on the Internet to discover one another in order to exchange context information about a session they would like to share. Common forms of communication that are set up by SIP include Internet telephony, instant messaging, video, Internet gaming and other forms of real-time communications. SIP is a multi-service protocol capable of initiating sessions involving different forms of real-time communications simultaneously. SIP is a protocol that finds the best way for parties to communicate. 2. ENUM Service Registration As defined in [1], the following is a template covering information needed for the registration of the enumservice specified in this document. Enumservice Name: "E2U+SIP" Type(s): "SIP" Subtype(s): N/A URI Scheme(s): "sip:", "sips:" Functional Specification: see Section 4 Security considerations: see Section 6 Intended usage: COMMON Author: Jon Peterson (jon.peterson@neustar.biz) Any other information that the author deems interesting: See Section 3 Peterson Standards Track [Page 2] RFC 3764 SIP enumservice April 2004 3. Addresses-of-record in SIP This document specifies an enumservice field that is appropriate for SIP addresses-of-record URIs. Various other types of URIs can be present in SIP requests. A URI that is associated with a particular SIP user agent (for example, a SIP phone) is commonly known as a SIP contact address. The difference between a contact address and an address-of-record is like the difference between a device and its user. While there is no formal distinction in the syntax of these two forms of addresses, contact addresses are associated with a particular device, and may have a very device-specific form (like sip:10.0.0.1, or sip:edgar@ua21.example.com). An address-of-record, however, represents an identity of the user, generally a long-term identity, and it does not have a dependency on any device; users can move between devices or even be associated with multiple devices at oneShow full document text