[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] [IPR]

Versions: (draft-brandner-enum-voice) 00 01 RFC 4415

ENUM                                                         R. Brandner
Internet-Draft                                                Siemens AG
Expires: March 13, 2006                                        L. Conroy
                                             Siemens Roke Manor Research
                                                              R. Stastny
                                                                   Oefeg
                                                       September 9, 2005


                IANA Registration for Enumservice Voice
                     <draft-ietf-enum-voice-00.txt>

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 13, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document registers the ENUMservice "voice" (which has a defined
   sub-type "tel"), as per the IANA registration process defined in the
   ENUM specification RFC3761.  This service indicates that the contact
   held in the generated URI can be used to initiate an interactive
   voice (audio) call.



Brandner, et al.         Expires March 13, 2006                 [Page 1]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


Table of Contents

   1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Enumservice for Interactive Voice  . . . . . . . . . . . . . .  5
     3.1.  Defined Sub-type "tel" for Interactive Voice . . . . . . .  5
       3.1.1.  Security Considerations for voice:tel  . . . . . . . .  6
       3.1.2.  Intended Use for voice:tel . . . . . . . . . . . . . .  6
       3.1.3.  Authors of voice:tel . . . . . . . . . . . . . . . . .  6
       3.1.4.  Other Information Author Deems Interesting for
               voice:tel  . . . . . . . . . . . . . . . . . . . . . .  6
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
   Intellectual Property and Copyright Statements . . . . . . . . . . 13

































Brandner, et al.         Expires March 13, 2006                 [Page 2]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


1.  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 BCP 14, RFC2119 [1].














































Brandner, et al.         Expires March 13, 2006                 [Page 3]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


2.  Introduction

   ENUM (E.164 Number Mapping, RFC3761 [2]) is a system that transforms
   E.164 numbers [3] into domain names and then uses DNS (Domain Name
   Service, RFC1034 [4]) features like delegation through NS records,
   and the use of NAPTR records, to look up the communication services
   available for a specific domain name.

   This document registers an Enumservice according to the guidelines
   given in RFC3761 to be used for provisioning in the services field of
   a NAPTR [5] resource record to indicate what class of functionality a
   given end point offers.  The registration is defined within the DDDS
   (Dynamic Delegation Discovery System [6][7] [5][8] [9]) hierarchy,
   for use with the "E2U" DDDS Application defined in RFC3761.

   Enumservices have a type and subtype.  This latter is optional, as it
   may be implicit in the service type.  The type defines the kind of
   communication session that can be initiated using the contact
   indicated by the URI generated by the enclosing NAPTR.  In
   telecommunications engineering terms, it reflects the "teleservice".

   The sub-type defines the subsystem that is to be used to initiate the
   communication session.  Note that the sub-type definition is usually
   associated with the URI scheme that is to be used.

   Both the type and subtype (where present) must be supported for the
   NAPTR to be used by a potential correspondent.

   There are a number of DDDS Applications in addition to ENUM (for
   example, see [8] and [9]).  However, an Enumservice indication
   operates only within the context of the "E2U" (ENUM) DDDS
   Application.

   Whilst the protocol elements that make up ENUM are defined in the
   above documents and in this one, further examples of the use to which
   these may be put are given in other documents, for example in ETSI TS
   102 172 [11].

   This document registers the Enumservice "voice" (which has a defined
   sub-type "tel"), as per the IANA registration process defined in the
   ENUM specification RFC3761.  This service indicates that the contact
   held in the generated URI can be used to initiate an interactive
   voice (audio) call.








Brandner, et al.         Expires March 13, 2006                 [Page 4]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


3.  Enumservice for Interactive Voice

   The kind of communication indicated by this Enumservice is
   "Interactive Voice".  From a protocol perspective, this communication
   is expected to involve bidirectional media streams carrying audio
   data.

   A client may imply that the person controlling population of a NAPTR
   holding this Enumservice indicates their capability to engage in an
   interactive voice session when contacted using the URI generated by
   this NAPTR.

3.1.  Defined Sub-type "tel" for Interactive Voice

      Sub-type:

         "tel"



      Generated URI scheme:

         "tel:" (defined in RFC3966 [10])


   This sub-type indicates that the person responsible for the NAPTR is
   accessible via the PSTN (Public Switched Telephone Network) or PLMN
   (Public Land Mobile Network) using the value of the generated URI.

   The kind of subsystem required to initiate a Voice Enumservice with
   this sub-type is a "Dialler".  This is a subsystem that either
   provides a local connection to the PSTN or PLMN, or that provides an
   indirect connection to those networks.  The subsystem will use the
   telephone number held in the generated URI to place a voice call.
   The voice call is placed to a network that uses E.164 numbers to
   route calls to an appropriate destination.

   Note that the PSTN/PLMN connection may be indirect.  The end user
   receiving this NAPTR may have a relationship with a Communications
   Service Provider that accepts call initiation requests from that
   subsystem using an IP-based protocol such as SIP or H.323, and places
   the call to the PSTN using a remote gateway service.  In this case
   the Provider may either accept requests using "tel:" URIs or has a
   defined mechanism to convert "tel:" URI values into a "protocol-
   native" form.

   The "tel:" URI value SHOULD be fully qualified (using the "global
   phone number" form of RFC3966).  A "local phone number" as defined in



Brandner, et al.         Expires March 13, 2006                 [Page 5]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


   that document SHOULD NOT be used unless the controller of the zone in
   which the NAPTR appears is sure that it can be distinguished
   unambiguously by all clients that can access the resource record and
   that a call from their network access points can be routed to that
   destination.

3.1.1.  Security Considerations for voice:tel

      See main security considerations section of this document.

3.1.2.  Intended Use for voice:tel

      COMMON

3.1.3.  Authors of voice:tel

      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see Authors' Addresses section)

3.1.4.  Other Information Author Deems Interesting for voice:tel

      NONE





























Brandner, et al.         Expires March 13, 2006                 [Page 6]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


4.  Security Considerations

   DNS, as used by ENUM, is a global, distributed database.  Thus any
   information stored there is visible to anyone anonymously.  Whilst
   this is not qualitatively different from publication in a Telephone
   Directory, it does open the data subject to having "their"
   information collected automatically without any indication that this
   has been done or by whom.

   Such data harvesting by third parties is often used to generate lists
   of targets for unrequested information; in short, they are used to
   address "spam".  Anyone who uses a Web-archived mailing list is aware
   that the volume of "spam" email they are sent increases when he or
   she posts to the mailing list; publication of a telephone number in
   ENUM is no different, and may be used for attempts to send "junk
   faxes" or "junk SMS" for example.

   Many mailing list users have more than one email address and use
   "sacrificial" email accounts when posting to such lists to help
   filter out unrequested emails sent to them.  This is not so easy with
   published telephone numbers; the PSTN E.164 number assignment process
   is much more involved and usually a single E.164 number (or a fixed
   range of numbers) is associated with each PSTN access.  Thus
   providing a "sacrificial" phone number in any publication is not
   possible.

   Due to the implications of publishing data on a globally accessible
   database, as a principle the data subject MUST give their explicit
   informed consent to data being published in ENUM.

   In addition, they should be made aware that, due to storage of such
   data during harvesting by third parties, removal of the data from
   publication will not remove any copies that have been taken; in
   effect, any publication may be permanent.

   However, regulations in many regions will require that the data
   subject can at any time request that the data is removed from
   publication, and that their consent for its publication is explicitly
   confirmed at regular intervals.

   When placing a voice call via the PSTN (or from the Public Land
   Mobile Network), the sender may be charged for this action.  In both
   kinds of network, calling some numbers is more expensive than sending
   to others; both kinds of network have "premium rate" services that
   can be charged at a rate considerably more than a "normal" call.  As
   such, it is important that the end user be asked to confirm placing
   the call, and that the destination number be presented to them.  It
   is the originating user's choice on whether or not to place a call to



Brandner, et al.         Expires March 13, 2006                 [Page 7]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


   this destination number, but they SHOULD be shown the destination
   number so that they can make this decision.

   In addition to the specific security considerations given above, all
   security considerations given in RFC3761 apply, as well as the DNS-
   specific threats covered in RFC3833 [12].













































Brandner, et al.         Expires March 13, 2006                 [Page 8]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


5.  IANA Considerations

   This document requests that IANA registers the Enumservice "voice"
   with a single sub-type "tel" according to the framework defined in
   RFC3761.  The current document defines this Enumservice and the
   expected behaviour of clients.













































Brandner, et al.         Expires March 13, 2006                 [Page 9]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


6.  References

6.1.  Normative References

   [1]   Bradner, S., "Key words for use in RFCs to Indicate Requirement
         Levels", RFC 2119, BCP 14, March 1997.

   [2]   Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
         Identifiers (URI) Dynamic Delegation  Discovery System (DDDS)
         Application (ENUM)", RFC 3761, April 2004.

   [3]   ITU-T, "The International Public Telecommunication Number
         Plan", Recommendation E.164, May 1997.

   [4]   Mockapetris, P., "DOMAIN NAMES - CONCEPTS AND FACILITIES",
         RFC 1034, November 1987.

   [5]   Mealling, M., "Dynamic Delegation Discovery System (DDDS)  Part
         Three: The Domain Name System (DNS) Database", RFC 3403,
         October 2002.

   [6]   Mealling, M., "Dynamic Delegation Discovery System (DDDS)  Part
         One: The Comprehensive DDDS", RFC 3401, October 2002.

   [7]   Mealling, M., "Dynamic Delegation Discovery System (DDDS)  Part
         Two: The Algorithm", RFC 3402, October 2002.

   [8]   Mealling, M., "Dynamic Delegation Discovery System (DDDS)  Part
         Four: The Uniform Resource Identifiers (URI)", RFC 3404,
         October 2002.

   [9]   Mealling, M., "Dynamic Delegation Discovery System (DDDS)  Part
         Five: URI.ARPA Assignment Procedures", RFC 3405, October 2002.

   [10]  Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966,
         December 2004.

6.2.  Informative References

   [11]  ETSI, "Minimum Requirements for Interoperability of ENUM
         Implementations", ETSI TS 102 172, January 2005.

   [12]  Atkins, D. and R. Austein, "Threat Analysis of the Domain Name
         System (DNS)", RFC 3833, August 2004.

   [13]  Bradner, S., "The Internet Standards Process -- Revision 3",
         RFC 2026, BCP 9, October 1996.




Brandner, et al.         Expires March 13, 2006                [Page 10]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


   [14]  Bradner, S., "IETF Rights in Contributions", BCP 78, RFC 3978,
         March 2005.

   [15]  Bradner, S., "Intellectual Property Rights in IETF Technology",
         BCP 79, RFC 3979, March 2005.














































Brandner, et al.         Expires March 13, 2006                [Page 11]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


Authors' Addresses

   Rudolf Brandner
   Siemens AG
   Hofmannstr. 51
   81359 Munich
   Germany

   Phone: +49-89-722-51003
   Email: rudolf.brandner@siemens.com


   Lawrence Conroy
   Siemens Roke Manor Research
   Roke Manor
   Romsey
   United Kingdom

   Phone: +44-1794-833666
   Email: lwc@roke.co.uk


   Richard Stastny
   Oefeg
   Postbox 147
   1103 Vienna
   Austria

   Phone: +43-664-420-4100
   Email: Richard.stastny@oefeg.at





















Brandner, et al.         Expires March 13, 2006                [Page 12]

Internet-Draft     IANA Voice Enumservice Registration    September 2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Brandner, et al.         Expires March 13, 2006                [Page 13]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/