Network Working Group                                          A. Newton
Internet-Draft                                            VeriSign, Inc.
Expires: May 5, 2003                                   November 04, 2002


                      IRIS Address Registry Schema
                     draft-ietf-crisp-iris-areg-01

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   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 May 5, 2003.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document describes an IRIS registry id and schema for registered
   Internet address information.  The schema extends the necessary query
   and result operations of IRIS (draft-ietf-crisp-iris-core-01.txt) to
   provide the functional information service needs for syntaxes and
   results used by Internet address registries.










Newton                     Expires May 5, 2003                  [Page 1]

Internet-Draft                  iris-areg                  November 2002


Table of Contents

   1.    Introduction . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.    Document Terminology . . . . . . . . . . . . . . . . . . . .  4
   3.    Schema Description . . . . . . . . . . . . . . . . . . . . .  5
   3.1   Query Derivatives  . . . . . . . . . . . . . . . . . . . . .  5
   3.1.1 <findContacts> Query . . . . . . . . . . . . . . . . . . . .  5
   3.2   Result Derivatives . . . . . . . . . . . . . . . . . . . . .  5
   3.2.1 <host> Result  . . . . . . . . . . . . . . . . . . . . . . .  5
   3.2.2 <network> Result . . . . . . . . . . . . . . . . . . . . . .  5
   3.2.3 <autonomousSystem> Result  . . . . . . . . . . . . . . . . .  6
   3.2.4 <contact> Result . . . . . . . . . . . . . . . . . . . . . .  6
   3.3   Support for <iris:lookupEntity>  . . . . . . . . . . . . . .  6
   4.    Formal XML Syntax  . . . . . . . . . . . . . . . . . . . . .  8
   5.    BEEP Transport Compliance  . . . . . . . . . . . . . . . . . 14
   5.1   Message Pattern  . . . . . . . . . . . . . . . . . . . . . . 14
   5.2   Authority Resolution . . . . . . . . . . . . . . . . . . . . 14
   5.3   Server Authentication  . . . . . . . . . . . . . . . . . . . 15
   6.    Internationalization Considerations  . . . . . . . . . . . . 16
   7.    IANA Considerations  . . . . . . . . . . . . . . . . . . . . 17
   8.    Security Considerations  . . . . . . . . . . . . . . . . . . 18
         References . . . . . . . . . . . . . . . . . . . . . . . . . 19
         Author's Address . . . . . . . . . . . . . . . . . . . . . . 20
         Full Copyright Statement . . . . . . . . . . . . . . . . . . 21



























Newton                     Expires May 5, 2003                  [Page 2]

Internet-Draft                  iris-areg                  November 2002


1. Introduction

   This document describes an IRIS namespace for Internet address
   registries using an XML Schema [4] derived from and using the IRIS
   [8] schema.  This schema and registry type are provided to
   demonstrate the extensibility of the IRIS framework beyond the use of
   domains, a criteria defined in CRISP [10].

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







































Newton                     Expires May 5, 2003                  [Page 3]

Internet-Draft                  iris-areg                  November 2002


2. Document 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 [7].














































Newton                     Expires May 5, 2003                  [Page 4]

Internet-Draft                  iris-areg                  November 2002


3. Schema Description

   IRIS requires the derivation of both query and result elements by a
   registry schema.  These descriptions follow.

   The descriptions contained within this section refer to XML elements
   and attributes and their relation to the exchange of data within the
   protocol.  These descriptions also contain specifications outside the
   scope of the formal XML syntax.  Therefore, this section will use
   terms defined by RFC 2119 [7] to describe the specification outside
   the scope of the formal XML syntax.  While reading this section,
   please reference Section 4 for needed details on the formal XML
   syntax.

3.1 Query Derivatives

3.1.1 <findContacts> Query

   <findContacts> searches for contacts given search constraints.  The
   <beginsWith> element specifies the beginning of the common name of
   the contact.  The <endsWith> element contains the end of the common
   name of the contact.

3.2 Result Derivatives

3.2.1 <host> Result

   The <host> element represents a name server.  It contains elements
   for the fully qualified host name of the host, the IP address of the
   host, and a reference to the host contact.

   The address elements contain the IP address of the name server,
   either IP v4 or IP v6, and an optional reference to the network which
   contains the given address.

3.2.2 <network> Result

   The <network> element an IP network.  It has the following child
   elements:

   o  <holder> contains an entity URI to the holder of the network.

   o  <contact> contains an entity URI to the technical contact of the
      network.

   o  Either <ipV4> or <ipV6> must be present.  Each element contains
      children representing the start and end of the network in the
      appropriate format.



Newton                     Expires May 5, 2003                  [Page 5]

Internet-Draft                  iris-areg                  November 2002


3.2.3 <autonomousSystem> Result

   The <autonomousSystem> element represents an assigned autonomous
   system.  It has the following children:

   o  <holder> contains an entity URI to the holder of the autonomous
      system.

   o  <contact> contains an entity URI to the technical contact of the
      autonomous system.

   o  <handle> is a registry assigned unique identifier.

   o  <startNumber> is a positive integer representing the starting
      number of the autonomous system.

   o  <endNumber> is a positive integer representing the final number of
      the autonomous system.


3.2.4 <contact> Result

   The <contact> element represents the registration of a point of
   contact.  The children are <handle>, containing a registry assigned
   unique identifier, and <commonName>, which holds the common name of
   the contact.  The other children of this element are optional and
   contain Internet, phone, and postal address information.

3.3 Support for <iris:lookupEntity>

   The following types of named entities are recognized by the
   <lookupEntity> query of IRIS via derivation of the <entityClass>
   element:

   o  host-name - the fully qualified host names of nameservers.
      Queries with these names will yield a <host> result.  A host may
      be multi-homed and therefore known by many host names.

   o  host-handle - a registry unique identifier of a nameserver.
      Yields a <host> result.

   o  ipv4-host - the IPv4 address of a nameserver.  Yields a <host>
      result.

   o  ipv6-host - the IPv6 address of a nameserver.  Yields a <host>
      result.

   o  ipv4-address - a network for which an IPv4 address resides.



Newton                     Expires May 5, 2003                  [Page 6]

Internet-Draft                  iris-areg                  November 2002


      Queries with these names will yield a <network> result.

   o  ipv6-address - a network for which an IPv6 address resides.
      Queries with these names will yield a <network> result.

   o  autonomous-system - the positive integer (ASN) representing
      specifying an autonomous system.  It yields a result of
      <autonomousSystem>.

   o  contact-handle - a registry unique identifier of a contact.
      Yields a result of <contact>.








































Newton                     Expires May 5, 2003                  [Page 7]

Internet-Draft                  iris-areg                  November 2002


4. Formal XML Syntax

   This IP address registry is specified in the XML Schema notation.
   The formal syntax presented here is a complete schema representation
   suitable for automated validation of an XML instance when combined
   with the formal schema syntax of IRIS.



   <?xml version="1.0"?>
   <schema xmlns="http://www.w3.org/2001/XMLSchema"
           xmlns:areg="urn:ietf:params:xml:ns:areg1"
           xmlns:iris="urn:ietf:params:xml:ns:iris1"
           targetNamespace="urn:ietf:params:xml:ns:areg1"
           elementFormDefault="qualified" >

     <annotation>
       <documentation>
         IP address registry schema
         derived from IRIS schema
       </documentation>
     </annotation>

     <!--             -->
     <!-- Query types -->
     <!--             -->

     <complexType name="findContactsType">
       <complexContent>
         <extension base="iris:queryType">
           <sequence>
             <element name="beginsWith"
               minOccurs="1" maxOccurs="1">
               <simpleType>
                 <restriction base="token">
                   <minLength value="3"/>
                 </restriction>
               </simpleType>
             </element>
             <element name="endsWith"
               minOccurs="0" maxOccurs="1" >
               <simpleType>
                 <restriction base="token">
                   <minLength value="2"/>
                 </restriction>
               </simpleType>
             </element>
           </sequence>



Newton                     Expires May 5, 2003                  [Page 8]

Internet-Draft                  iris-areg                  November 2002


         </extension>
       </complexContent>
     </complexType>

     <element name="findContacts"
       type="areg:findContactsType"
       substitutionGroup="iris:query" />

     <!--              -->
     <!-- Result types -->
     <!--              -->

     <complexType name="hostType">
       <complexContent>
         <extension base="iris:resultType">
           <sequence>
             <element name="hostName"
               type="normalizedString" />
             <choice
               minOccurs="1" maxOccurs="unbounded" >
               <element name="ipV4">
                 <complexType>
                   <sequence>
                     <element name="ipV4Address"
                       type="normalizedString" />
                     <element ref="iris:entityURI"
                       minOccurs="0" maxOccurs="1" />
                   </sequence>
                 </complexType>
               </element>
               <element name="ipV6">
                 <complexType>
                   <sequence>
                     <element name="ipV6Address"
                       type="normalizedString" />
                     <element ref="iris:entityURI"
                       minOccurs="0" maxOccurs="1" />
                   </sequence>
                 </complexType>
               </element>
             </choice>
             <element ref="iris:seeAlso" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element name="host"



Newton                     Expires May 5, 2003                  [Page 9]

Internet-Draft                  iris-areg                  November 2002


       type="areg:hostType"
       substitutionGroup="iris:result" />

     <complexType name="networkType">
       <complexContent>
         <extension base="iris:resultType">
           <sequence>
             <element name="holder"
               minOccurs="0" maxOccurs="1">
               <complexType>
                 <sequence>
                   <element ref="iris:entityURI" />
                 </sequence>
               </complexType>
             </element>
             <element name="contact"
               minOccurs="0" maxOccurs="1">
               <complexType>
                 <sequence>
                   <element ref="iris:entityURI" />
                 </sequence>
               </complexType>
             </element>
             <element name="handle"
               type="normalizedString" />
             <choice>
               <element name="ipV4">
                 <complexType>
                   <sequence>
                     <element name="startIPv4"
                       type="normalizedString" />
                     <element name="endIPv4"
                       type="normalizedString" />
                   </sequence>
                 </complexType>
               </element>
               <element name="ipV6">
                 <complexType>
                   <sequence>
                     <element name="startIPv6"
                       type="normalizedString" />
                     <element name="endIPv6"
                       type="normalizedString" />
                   </sequence>
                 </complexType>
               </element>
             </choice>
           </sequence>



Newton                     Expires May 5, 2003                 [Page 10]

Internet-Draft                  iris-areg                  November 2002


         </extension>
       </complexContent>
     </complexType>

     <element name="network"
       type="areg:networkType"
       substitutionGroup="iris:result" />

     <complexType name="autonomousSystemType">
       <complexContent>
         <extension base="iris:resultType">
           <sequence>
             <element name="holder"
               minOccurs="0" maxOccurs="1">
               <complexType>
                 <sequence>
                   <element ref="iris:entityURI"/>
                 </sequence>
               </complexType>
             </element>
             <element name="contactReference"
               minOccurs="0" maxOccurs="1">
               <complexType>
                 <sequence>
                   <element ref="iris:entityURI"/>
                 </sequence>
               </complexType>
             </element>
             <element name="handle"
               type="normalizedString" />
             <element name="startNumber"
               type="positiveInteger" />
             <element name="endNumber"
               type="positiveInteger" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element name="autonomousSystem"
       type="areg:autonomousSystemType"
       substitutionGroup="iris:result" />

     <complexType name="contactType">
       <complexContent>
         <extension base="iris:resultType">
           <sequence>
             <element name="handle"



Newton                     Expires May 5, 2003                 [Page 11]

Internet-Draft                  iris-areg                  November 2002


               type="areg:handleType"
               minOccurs="0" maxOccurs="1" />
             <element name="commonName"
               type="token" />
             <element name="organization"
               type="normalizedString"
               minOccurs="0" maxOccurs="1" />
             <element name="e-mail"
               type="normalizedString"
               minOccurs="0" maxOccurs="2" />
             <element name="address"
               type="string"
               minOccurs="0" maxOccurs="1" />
             <element name="city"
               type="string"
               minOccurs="0" maxOccurs="1" />
             <element name="region"
               type="string"
               minOccurs="0" maxOccurs="1" />
             <element name="postalCode"
               type="normalizedString"
               minOccurs="0" maxOccurs="1" />
             <element name="country"
               type="token"
               minOccurs="0" maxOccurs="1" />
             <element name="phone"
               type="normalizedString"
               minOccurs="0" maxOccurs="1" />
             <element name="fax"
               type="normalizedString"
               minOccurs="0" maxOccurs="1" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element name="contact"
       type="areg:contactType"
       substitutionGroup="iris:result" />

     <!--              -->
     <!-- Global types -->
     <!--              -->

     <simpleType name="entityClassType">
       <restriction base="iris:entityClassType">
         <enumeration value="host-name" />
         <enumeration value="host-handle" />



Newton                     Expires May 5, 2003                 [Page 12]

Internet-Draft                  iris-areg                  November 2002


         <enumeration value="ipv4-host" />
         <enumeration value="ipv6-host" />
         <enumeration value="contact-handle" />
         <enumeration value="ipv4-address" />
         <enumeration value="ipv6-address" />
         <enumeration value="autonomous-system" />
       </restriction>
     </simpleType>

     <element name="entityClass"
       type="dreg:entityClassType"
       substitutionGroup="iris:entityClass" />

   </schema>





































Newton                     Expires May 5, 2003                 [Page 13]

Internet-Draft                  iris-areg                  November 2002


5. BEEP Transport Compliance

   IRIS allows several extensions of the core capabilities.  This
   section outlines those extensions allowable by IRIS-BEEP [9].

5.1 Message Pattern

   This registry type uses the default message pattern as described in
   IRIS-BEEP [9].

5.2 Authority Resolution

   The authority resolution for this registry type is similar to the
   default resolution spelled out in IRIS-BEEP [9].  The default
   authority resolution process allows for the authority to be

   o  a domain name

   o  a domain name accompanied by a port number

   o  an IP address

   o  an IP address accompanied by a port number

   The resolution process for this registry only differs if the
   authority is only an IP address (i.e.  without the port number).  The
   process for this condition is as follows:

   1.  The IP address is converted into a domain name appropriate for
       the reverse DNS tree mapping.  For instance, 64.83.37.226 is
       226.37.83.64.in-addr.arpa.

   2.  The SRV algorithm is used with a service parameter of "iris" and
       a protocol parameter of "tcp" to determine the IP/TCP addressing
       information.

   3.  If no SRV records are found (e.g.  for
       "_iris._tcp.226.37.83.64.in-addr.arpa"), then the left-most
       component of the domain name from step one is removed, and the
       second step is repeated again (e.g.  for "_iris._tcp.37.83.64.in-
       addr.arpa").

   4.  If all the components of the domain name from step one are
       removed and no SRV records are found, then the original IP
       address is used and the port number used is the well-known port
       assigned by the IANA for IRIS using BEEP.





Newton                     Expires May 5, 2003                 [Page 14]

Internet-Draft                  iris-areg                  November 2002


5.3 Server Authentication

   This registry type uses the default server authentication method as
   described in IRIS-BEEP [9].















































Newton                     Expires May 5, 2003                 [Page 15]

Internet-Draft                  iris-areg                  November 2002


6. Internationalization Considerations

   This document lays out no new considerations for internationalization
   beyond that specified in IRIS [8].















































Newton                     Expires May 5, 2003                 [Page 16]

Internet-Draft                  iris-areg                  November 2002


7. IANA Considerations

   The following URN will need to be registered with IANA according to
   the IANA considerations defined in IRIS [8]:

      urn:ietf:params:xml:ns:areg1













































Newton                     Expires May 5, 2003                 [Page 17]

Internet-Draft                  iris-areg                  November 2002


8. Security Considerations

   This document lays out no new considerations for security precautions
   beyond that specified in IRIS [8].















































Newton                     Expires May 5, 2003                 [Page 18]

Internet-Draft                  iris-areg                  November 2002


References

   [1]   World Wide Web Consortium, "Extensible Markup Language (XML)
         1.0", W3C XML, February 1998, <http://www.w3.org/TR/1998/REC-
         xml-19980210>.

   [2]   World Wide Web Consortium, "Namespaces in XML", W3C XML
         Namespaces, January 1999, <http://www.w3.org/TR/1999/REC-xml-
         names-19990114>.

   [3]   World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C
         XML Schema, October 2000, <http://www.w3.org/TR/2001/REC-
         xmlschema-2-20010502/>.

   [4]   World Wide Web Consortium, "XML Schema Part 1: Structures", W3C
         XML Schema, October 2000, <http://www.w3.org/TR/2001/REC-
         xmlschema-1-20010502/>.

   [5]   Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", RFC 1700, STD
         2, October 1994.

   [6]   Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
         Considerations Section in RFCs", RFC 2434, BCP 26, October
         1998.

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

   [8]   Newton, A., "Internet Registry Information Service", draft-
         ietf-crisp-iris-core-01 (work in progress), November 2002.

   [9]   Newton, A., "Internet Registry Information Service (IRIS) over
         the Blocks Extensible Exchange Protocol (BEEP)", draft-ietf-
         crisp-iris-beep-01 (work in progress), November 2002.

   [10]  Newton, A., "Cross Registry Internet Service Protocol (CRISP)
         Requirements", draft-ietf-crisp-requirements-01 (work in
         progress), October 2002.













Newton                     Expires May 5, 2003                 [Page 19]

Internet-Draft                  iris-areg                  November 2002


Author's Address

   Andrew L. Newton
   VeriSign, Inc.
   21345 Ridgetop Circle
   Sterling, VA  20166
   USA

   Phone: +1 703 948 3382
   EMail: anewton@ecotroph.net
   URI:   http://www.verisignlabs.com/








































Newton                     Expires May 5, 2003                 [Page 20]

Internet-Draft                  iris-areg                  November 2002


Full Copyright Statement

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS 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.

Acknowledgement

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



















Newton                     Expires May 5, 2003                 [Page 21]