datatracker.ietf.org
Sign in
Version 5.6.2.p2, 2014-07-24
Report a bug

E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)
RFC 4114

Network Working Group                                      S. Hollenbeck
Request for Comments: 4114                                VeriSign, Inc.
Category: Standards Track                                      June 2005

  E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)

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 (2005).

Abstract

   This document describes an Extensible Provisioning Protocol (EPP)
   extension mapping for the provisioning and management of E.164
   numbers that represent domain names stored in a shared central
   repository.  Specified in XML, this mapping extends the EPP domain
   name mapping to provide additional features required for the
   provisioning of E.164 numbers.

Hollenbeck                  Standards Track                     [Page 1]
RFC 4114                   EPP E.164 Mapping                   June 2005

Table of Contents

   1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . .  2
      1.1. Conventions Used in This Document  . . . . . . . . . . . .  3
   2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . .  3
      2.1. E.164 Domain Names . . . . . . . . . . . . . . . . . . . .  3
      2.2. NAPTR Fields . . . . . . . . . . . . . . . . . . . . . . .  3
           2.2.1. Order . . . . . . . . . . . . . . . . . . . . . . .  4
           2.2.2. Preference. . . . . . . . . . . . . . . . . . . . .  4
           2.2.3. Flags . . . . . . . . . . . . . . . . . . . . . . .  4
           2.2.4. Service . . . . . . . . . . . . . . . . . . . . . .  4
           2.2.5. Regular Expression. . . . . . . . . . . . . . . . .  4
           2.2.6. Replacement . . . . . . . . . . . . . . . . . . . .  4
   3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . .  4
      3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . .  5
           3.1.1. EPP <check> Command . . . . . . . . . . . . . . . .  5
           3.1.2. EPP <info> Command. . . . . . . . . . . . . . . . .  5
           3.1.3. EPP <transfer> Command. . . . . . . . . . . . . . .  7
      3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . .  7
           3.2.1. EPP <create> Command. . . . . . . . . . . . . . . .  7
           3.2.2. EPP <delete> Command. . . . . . . . . . . . . . . .  9
           3.2.3. EPP <renew> Command . . . . . . . . . . . . . . . .  9
           3.2.4. EPP <transfer> Command. . . . . . . . . . . . . . .  9
           3.2.5. EPP <update> Command. . . . . . . . . . . . . . . .  9
   4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 11
   5. Internationalization Considerations . . . . . . . . . . . . . . 14
   6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 14
   7. Security Considerations . . . . . . . . . . . . . . . . . . . . 14
   8. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . 15
   9. References. . . . . . . . . . . . . . . . . . . . . . . . . . . 15
      9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
      9.2. Informative References . . . . . . . . . . . . . . . . . . 16

1.  Introduction

   This document describes an E.164 number mapping for version 1.0 of
   the Extensible Provisioning Protocol (EPP).  This mapping, an
   extension of the domain name mapping described in [1], is specified
   using the Extensible Markup Language (XML) 1.0, as described in [2],
   and XML Schema notation, as described in [3] and [4].

   The EPP core protocol specification [5] provides a complete
   description of EPP command and response structures.  A thorough
   understanding of the base protocol specification is necessary to
   understand the mapping described in this document.

Hollenbeck                  Standards Track                     [Page 2]
RFC 4114                   EPP E.164 Mapping                   June 2005

   ENUM [6] describes how the Domain Name System (DNS) can be used to
   identify services associated with an E.164 number.  The EPP mapping
   described in this document specifies a mechanism for the provisioning
   and management of E.164 numbers stored in a shared central
   repository.  Information exchanged via this mapping can be extracted
   from the repository and used to publish DNS resource records as
   described in ENUM [6].  Examples used in this document were chosen
   specifically to illustrate provisioning concepts for the example

[include full document text]