Enumservice Registration for 'acct' URI
RFC 7566

 
Document Type RFC - Experimental (June 2015; No errata)
Last updated 2015-06-25
Stream ISE
Formats plain text pdf html
IETF conflict review conflict-review-goix-appsawg-enum-acct-uri
Stream ISE state Published RFC
Document shepherd No shepherd assigned
IESG IESG state RFC 7566 (Experimental)
Telechat date
Responsible AD (None)
Send notices to laurentwalter.goix@telecomitalia.it, likepeng@huawei.com, draft-goix-appsawg-enum-acct-uri@ietf.org, rfc-ise@rfc-editor.org
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Independent Submission                                           L. Goix
Request for Comments: 7566                   Econocom-Osiatis Ingenierie
Category: Experimental                                             K. Li
ISSN: 2070-1721                                               Individual
                                                               June 2015

                Enumservice Registration for 'acct' URI

Abstract

   This document registers an E.164 Number Mapping (ENUM) service for
   'acct' URIs (Uniform Resource Identifiers).

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for examination, experimental implementation, and
   evaluation.

   This document defines an Experimental Protocol for the Internet
   community.  This is a contribution to the RFC Series, independently
   of any other RFC stream.  The RFC Editor has chosen to publish this
   document at its discretion and makes no statement about its value for
   implementation or deployment.  Documents approved for publication by
   the RFC Editor are not a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7566.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Goix & Li                     Experimental                      [Page 1]
RFC 7566           Enumservice 'acct' URI Registration         June 2015

Table of Contents

   1. Introduction ....................................................2
   2. Terminology .....................................................2
   3. Use Cases .......................................................2
      3.1. Reverse Phone Lookup .......................................2
      3.2. Routing of Mobile Social Communications ....................3
   4. IANA Registration ...............................................4
   5. Examples ........................................................5
   6. DNS Considerations ..............................................5
   7. Security Considerations .........................................6
   8. IANA Considerations .............................................7
   9. References ......................................................7
      9.1. Normative References .......................................7
      9.2. Informative References .....................................8
   Acknowledgements ...................................................8
   Authors' Addresses .................................................8

1.  Introduction

   ENUM (E.164 Number Mapping, [RFC6116]) is a system that uses DNS
   (Domain Name Service, [RFC1034]) to translate telephone numbers, such
   as '+44 1632 960123', into URIs (Uniform Resource Identifiers,
   [RFC3986]), such as 'acct:user@example.com'.  ENUM exists primarily
   to facilitate the interconnection of systems that rely on telephone
   numbers with those that use URIs to identify resources.

   [RFC7565] defines the 'acct' URI scheme as a way to identify a user's
   account at a service provider.

   This document registers an Enumservice for advertising 'acct' URI
   information associated with an E.164 number.

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 [RFC2119].

3.  Use Cases

3.1.  Reverse Phone Lookup

   In this example, an address book application could issue ENUM queries
   looking for 'acct' URIs corresponding to phone numbers.  This could
   be used to display the account identifier as well as an icon based on
   the host (domain) portion of that URI.

Goix & Li                     Experimental                      [Page 2]
RFC 7566           Enumservice 'acct' URI Registration         June 2015

   Similarly, an endpoint could trigger this resolution process during
   inbound and/or outbound calls to discover an account associated with
Show full document text