An ENUM Registry Type for the Internet Registry Information Service (IRIS)
RFC 4414

 
Document
Type RFC - Proposed Standard (February 2006; No errata)
Last updated 2013-03-02
Replaces draft-newton-iris-ereg
Stream IETF
Formats plain text pdf html
Stream
WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG
IESG state RFC 4414 (Proposed Standard)
Telechat date
Responsible AD Allison Mankin
Send notices to paf@cisco.com, panic@paf.se, rich.shockey@neustar.biz

Email authors IPR 1 References Referenced by Nits Search lists

Network Working Group                                          A. Newton
Request for Comments: 4414                                VeriSign, Inc.
Category: Standards Track                                  February 2006

                         An ENUM Registry Type
          for the Internet Registry Information Service (IRIS)

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

Abstract

   This document describes an Internet Registry Information Service
   (IRIS) registry schema for registered ENUM information.  The schema
   extends the necessary query and result operations of IRIS to provide
   the functional information service needs for syntaxes and results
   used by ENUM registries.

Newton                      Standards Track                     [Page 1]
RFC 4414              ENUM Registry Type for IRIS          February 2006

Table of Contents

   1. Introduction ....................................................3
   2. Document Terminology ............................................3
   3. Schema Description ..............................................3
      3.1. Query Derivatives ..........................................3
           3.1.1. <findEnumsByE164> Query .............................3
           3.1.2. <findEnumsByContact> Query ..........................4
           3.1.3. <findContacts> Query ................................4
           3.1.4. <findEnumsByHost> Query .............................4
           3.1.5. Contact Search Group ................................5
      3.2. Result Derivatives .........................................5
           3.2.1. Privacy Labels ......................................5
           3.2.2. Contact Group .......................................7
           3.2.3. <enum> Result .......................................8
           3.2.4. <host> Result ......................................12
           3.2.5. <contact> Result ...................................13
           3.2.6. <registrationAuthority> Result .....................15
           3.2.7. <validationEntity> Result ..........................16
           3.2.8. <communicationServiceProvider> Result ..............17
           3.2.9. <validationEvent> Result ...........................18
      3.3. Generic Code Derivatives ..................................19
           3.3.1. <searchTooWide> ....................................19
           3.3.2. <languageNotSupported> .............................19
      3.4. Support for <iris:lookupEntity> ...........................19
   4. Formal XML Syntax ..............................................21
   5. Blocks Extensible Exchange Protocol (BEEP) Transport
      Compliance .....................................................46
      5.1. Message Pattern ...........................................46
      5.2. Server Authentication .....................................46
   6. URI Resolution .................................................46
      6.1. Application Service Label .................................46
   7. Internationalization Considerations ............................46
   8. IANA Considerations ............................................47
      8.1. XML Namespace URN Registration ............................47
      8.2. S-NAPTR Registration ......................................48
      8.3. BEEP Registration .........................................48
   9. Security Considerations ........................................48
   10. Normative References ..........................................48
   A.  Contributions and Acknowledgements ............................50

Newton                      Standards Track                     [Page 2]
RFC 4414              ENUM Registry Type for IRIS          February 2006

1.  Introduction

   This document describes an IRIS registry schema for registries of
   ENUM data using an XML Schema [4] derived from and using the IRIS [5]
   schema.

   The schema given is this document is specified using the Extensible
   Markup Language (XML) 1.0 as described in XML [1], XML Schema
   notation as described in XML_SD [3] and XML_SS [4], and XML
   Namespaces as described in XML_NS [2].

2.  Document Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text