RFC 3764 (rfc3764) - Page 2 of 8

enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record

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:'.  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 ()

      Any other information that the author deems interesting: See
      Section 3






Peterson                    Standards Track