Network Working Group                                          E. Gunduz
Internet-Draft                                                  RIPE NCC
Expires: February 3, 2005                                      A. Newton
                                                          VeriSign, Inc.
                                                          August 5, 2004


    IRIS - An Address Registry (areg) Type for the Internet Registry
                          Information Service
                     draft-ietf-crisp-iris-areg-06

Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and any of which I become aware will be disclosed, in accordance with
   RFC 3668.

   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 February 3, 2005.

Copyright Notice

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

Abstract

   This document describes an IRIS registry schema for IP address and
   Autonomous System Number 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
   Internet Protocol address registries.





Gunduz & Newton         Expires February 3, 2005                [Page 1]

Internet-Draft                 iris-areg                     August 2004


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.1.2   <findOrganizations>  . . . . . . . . . . . . . . . . .  5
       3.1.3   <findAutonomousSystems> and <findNetworks> . . . . . .  5
       3.1.4   <findNetworkByAddress> . . . . . . . . . . . . . . . .  6
     3.2   Result Derivatives . . . . . . . . . . . . . . . . . . . .  6
       3.2.1   <ipv4Network> and <ipv6Network> Results  . . . . . . .  6
       3.2.2   <autonomousSystem> Result  . . . . . . . . . . . . . .  7
       3.2.3   <contact> Result . . . . . . . . . . . . . . . . . . .  7
       3.2.4   <organization> Result  . . . . . . . . . . . . . . . .  8
       3.2.5   Contact References . . . . . . . . . . . . . . . . . .  8
       3.2.6   Common Result Child Elements . . . . . . . . . . . . .  8
     3.3   Support for <iris:lookupEntity>  . . . . . . . . . . . . .  9
   4.  Terminology for Nesting of Networks  . . . . . . . . . . . . . 10
   5.  Formal XML Syntax  . . . . . . . . . . . . . . . . . . . . . . 14
   6.  BEEP Transport Compliance  . . . . . . . . . . . . . . . . . . 26
     6.1   Message Pattern  . . . . . . . . . . . . . . . . . . . . . 26
     6.2   Server Authentication  . . . . . . . . . . . . . . . . . . 26
   7.  URI Resolution . . . . . . . . . . . . . . . . . . . . . . . . 27
     7.1   Application Service Label  . . . . . . . . . . . . . . . . 27
     7.2   Top-Down Resolution  . . . . . . . . . . . . . . . . . . . 27
   8.  Internationalization Considerations  . . . . . . . . . . . . . 28
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 29
   10.   Security Considerations  . . . . . . . . . . . . . . . . . . 30
   11.   References . . . . . . . . . . . . . . . . . . . . . . . . . 30
       Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 31
   A.  Example Requests and Responses . . . . . . . . . . . . . . . . 32
     A.1   Example 1  . . . . . . . . . . . . . . . . . . . . . . . . 32
     A.2   Example 2  . . . . . . . . . . . . . . . . . . . . . . . . 33
   B.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 37
       Intellectual Property and Copyright Statements . . . . . . . . 38















Gunduz & Newton         Expires February 3, 2005                [Page 2]

Internet-Draft                 iris-areg                     August 2004


1.  Introduction

   This document describes an IRIS namespace for Internet address
   registries using an XML Schema [5] derived from and using the IRIS
   [9] 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 [11].

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

   Examples of client/server XML exchanges with this registry type are
   available in Appendix A.




































Gunduz & Newton         Expires February 3, 2005                [Page 3]

Internet-Draft                 iris-areg                     August 2004


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














































Gunduz & Newton         Expires February 3, 2005                [Page 4]

Internet-Draft                 iris-areg                     August 2004


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 [8] to describe the specification outside
   the scope of the formal XML syntax.  While reading this section,
   please reference Section 5 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 child element <commonName> allows the search to be constrained
   against the name of the contact.  This element may have as a child
   the <exactMatch> element.

   <eMail> constrains the query based on the e-mail address of the
   contact.  This may be done by an exact e-mail address using the
   <exactMatch> element or by any e-mail address in a domain using the
   <inDomain> element.  The <inDomain> element MUST only contain a valid
   domain according to RFC 1035 [1] (i.e.  no '@' symbol).

   <findContacts> queries MUST be case insensitive.

3.1.2  <findOrganizations>

   The <findOrganizations> element allows searches by name of
   organisations.

   The child element <name> may have as child the <exactMatch> element.

3.1.3  <findAutonomousSystems> and <findNetworks>

   The <findAutonomousSystems> and <findNetworks> elements allow
   searches by handle of autonomous systems, and networks, respectively.
   Both have the same format.

   The child element <specificity> - determines the ASN range
   specificity for the search (see Section 4).  Valid values are
   "all-less-specifics", "one-level-less-specifics",



Gunduz & Newton         Expires February 3, 2005                [Page 5]

Internet-Draft                 iris-areg                     August 2004


   "all-more-specifics", "one-level-more-specifics" and "closes-match".
   This element may have the optional attribute 'allowEquivalences'.
   When set to "true", the result set should include ASN ranges with
   equivalent starting and ending ASNs.

3.1.4  <findNetworkByAddress>

   The <findNetworkByAddress> element is a query for a network given a
   related IP address, IP address range, or network handle.  It has the
   following child elements:
   o  <ipv4Address> - has a child <start> element containing the
      starting IPv4 address of the network and an optional child of
      <end> containing the ending IPv4 address of the network.
   o  <ipv6Address> - same as <ipv4Address> but the child addresses
      contain IPv6 addresses.  Clients MUST convert any short-form
      notation to the fully-qualified notation.
   o  <specificity> - determines the network specificity for the search
      (see Section 4).  Valid values are "all-less-specifics",
      "one-level-less-specifics", "all-more-specifics",
      "one-level-more-specifics" and "closest-match".  This element may
      have the optional attribute 'allowEquivalences'.  When set to
      "true", the result set should include networks with equivalent
      starting and ending addresses.

   The results from this query MUST be either the <ipv4Network> result
   or the <ipv6Network> result.  More than one network result MAY be
   returned.

3.2  Result Derivatives

3.2.1  <ipv4Network> and <ipv6Network> Results

   The <ipv4Network> and <ipv6Network> share a common defintion of
   'ipNetworkType'.  It has the following child elements:
   o  <networkHandle> contains the registry-unique assigned handle for
      this network.
   o  <startAddress> contains the first IP address of the network.
   o  <endAddress> contains the last IP address of the network.
   o  <networkType> contains a string denoting the type of network.
      *  <networkTypeInfoURI> contains a URI where the meanings of the
         values are explained in a plain natural language.
   o  One or more <nameServer> elements, each containing the domain name
      of a nameserver responsible for reverse-DNS mapping for this
      network.
   o  <organization> contains an entity reference to the organization
      assigned this network.  The referent MUST be an <organization>
      (Section 3.2.4) result.




Gunduz & Newton         Expires February 3, 2005                [Page 6]

Internet-Draft                 iris-areg                     August 2004


   o  One of:
      *  <parent> contains an entity reference to the parent network of
         this network.  The referent MUST be an <ipv4Network> (Section
         3.2.1) result if this reference is a child of <ipv4Network>.
         The referent MUST be an <ipv6Network> (Section 3.2.1) result if
         this reference is a child of <ipv6Network>.
      *  <noParent> contains no children and simply signifies that the
         network does not have a parent.
   o  Contact references (see Section 3.2.5).
   o  Common child elements (see Section 3.2.6).

3.2.2  <autonomousSystem> Result

   The <autonomousSystem> element represents an assigned autonomous
   system.  It has the following children:
   o  <asHandle> contains a registry-unique assigned handle for this
      autonomous system.
   o  <asNumberStart> contains an integer indicating the starting number
      for the autonomous system.
   o  <asNumberEnd> contains an integer indicating the ending number for
      the autonomous system.
   o  <organization> contains an entity reference to the organization
      assigned this autonomous system.  The referent MUST be an
      <organization> (Section 3.2.4) result.
   o  One of:
      *  <parent> contains an entity reference to the parent ASN range
         of this ASN range.  The referent MUST be an <autonomousSystem>
         (Section 3.2.2) result.
      *  <noParent> contains no children and simply signifies that the
         network does not have a parent.
   o  Contact references (see Section 3.2.5).
   o  Common child elements (see Section 3.2.6).

3.2.3  <contact> Result

   The <contact> element represents the registration of a point of
   contact.  It has the following child elements:
   o  <contactHandle> contains the registry-unique assigned handle for
      this contact.
   o  Either <firstName>, <middleName>, and <lastName> or <role>.  The
      first three elements specify the name of the contact broken down
      into the common components of a persons name.  The latter element,
      <role>, specifies that the contact is a group of people given the
      responsibility described by this element.
   o  <eMail> contains the email address for this contact.
   o  <sip> contains the sip address for this contact.
   o  <organization> contains an entity reference to the organization
      associated with this contact.  The referent MUST be an



Gunduz & Newton         Expires February 3, 2005                [Page 7]

Internet-Draft                 iris-areg                     August 2004


      <organization> (Section 3.2.4) result.
   o  <phone> contains child elements describing the phone number of the
      contact.  The child elements are <number>, <extension>, and
      <type>.
   o  Common child elements (see Section 3.2.6).

3.2.4  <organization> Result

   The <organization> element represents an organization.  It has the
   following child elements:
   o  <name> contains the name of the organization.
   o  <id> contains a registry-unique identifier for this organization.
   o  <address> contains the address for this organization.
   o  <city> contains the city where this organization is located.
   o  <region> contains the national region where this organization is
      located.
   o  <postalCode> contains the postal code where this organization is
      located.
   o  <country> contains the country code where this organization is
      located.  This MUST be compliant with ISO 3166 [12] two-character
      country codes.
   o  Contact references (see Section 3.2.5).
   o  Common child elements (see Section 3.2.6).

3.2.5  Contact References

   The registry schema defined in Section 5 normalizes out a group of
   elements used to reference contacts.  This group is used by many of
   the result types for this registry.  The group has the following
   elements, each of which may appear as many times as needed.  The
   referent of each MUST be <contact> (Section 3.2.3) results.
   o  <adminContact>
   o  <techContact>
   o  <nocContact>
   o  <abuseContact>
   o  <otherContact>

3.2.6  Common Result Child Elements

   The registry schema defined in Section 5 normalizes out a group of
   common elements used most of the reult types.  The group has the
   following elements:
   o  <numberResourceRegistry> contains an entity reference to the
      number resource registry of record.  The referent MUST be an
      <organization> (Section 3.2.4) result.
   o  <registrationDate> contains the date of first registration.
   o  <lastUpdatedDate> contains the date when the registration was last
      updated.



Gunduz & Newton         Expires February 3, 2005                [Page 8]

Internet-Draft                 iris-areg                     August 2004


   o  The <iris:seeAlso> element contains an entity reference specifying
      an entity that is indirectly associated with this result object.

3.3  Support for <iris:lookupEntity>

   The following types of entity classes are recognized by the
   <lookupEntity> query of IRIS for this registry:
   o  ipv4-handle - a registry unique identifier specifying an IPv4
      network.  Queries with these names will yield a <ipv4Network>
      result.
   o  ipv6-handle - a registry unique identifier specifying an IPv6
      network.  Queries with these names will yield a <ipv6Network>
      result.
   o  autonomous-system - the positive integer (ASN) specifying an
      autonomous system.  It yields a result of <autonomousSystem>.
   o  as-handle - a registry unique identifier 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>.
   o  organization-id - a registry unique identifier of an organization.
      Yields a result of <organization>.
   o  The entity names of these entity classes are case insensitive.





























Gunduz & Newton         Expires February 3, 2005                [Page 9]

Internet-Draft                 iris-areg                     August 2004


4.  Terminology for Nesting of Networks

   The following terms are defined for describing the nesting of IP
   networks.
   o  More specific: Given two networks, A and B, A is more specific
      than B if network B includes all space of network A, and if
      network B is larger than network A.
   o  Less specific: Opposite of more specific.  The network B is less
      specific than network A if network A's all space is included in
      network B and if network A is smaller than network B.
   o  Most specific: Given a set of networks, the network or networks
      that are more specific than zero or more of other networks in the
      set, and that are not a less specific of any of the networks in
      the set.
   o  Least specific: Given a set of networks, the network or networks
      that are not more specific to any of the other networks in the
      set.

   Examples:

   +-------------------------------------------------------+
   |                                                       |
   | Given the networks A, B, C and D as follows:          |
   |                                                       |
   |    A    |---------------------------------|           |
   |    B                    |-----------------|           |
   |    C                       |---------|                |
   |    D      |-------|                                   |
   |                                                       |
   |                                                       |
   | The network A is less specific than B, C and D.       |
   | The network B is more specific than A.                |
   | Among these four networks, A is the least specific,   |
   |   and C and D are the most specific networks.         |
   |                                                       |
   +-------------------------------------------------------+

                      Figure 1: Nesting Example 1













Gunduz & Newton         Expires February 3, 2005               [Page 10]

Internet-Draft                 iris-areg                     August 2004


   +-------------------------------------------------------+
   |                                                       |
   | Given the networks E, F and G:                        |
   |                                                       |
   |    E   |----------|                                   |
   |    F                |--------------|                  |
   |    G     |---|                                        |
   |                                                       |
   | The networks E and F are least specific networks.     |
   | The networks F and G are most specific networks.      |
   |                                                       |
   +-------------------------------------------------------+

                      Figure 2: Nesting Example 2

   The following definitions assume that there are no overlapping
   networks in the database.  A network overlaps with another one when
   they encompass each other's space partially.  Examples:

     A   |---------------------|
     B       |----------------------------|

                      Figure 3: Nesting Example 3


     C   |------------------|
     D   |---------|

                      Figure 4: Nesting Example 4

   Here, the networks C and D are NOT overlapping networks, because even
   if network D encompasses a part of network C's space, network C does
   not encompass network D's space partially (it encompasses network D
   completely).

   The address directory can contain more than one network with the same
   range.  They are said to be exact match networks.

   Parent/child relationship in the internet address directory is
   unidirectional.  That is, there might also be parent/child
   relationship with exact match networks, but a network cannot be a
   parent and a child of its exact match network at the same time.

   Nested matching searches:

   [1] Given a range, find all the networks that contain that range (ie,
   all less specifics and exact matches).  These networks are the
   networks that fulfill the following condition:



Gunduz & Newton         Expires February 3, 2005               [Page 11]

Internet-Draft                 iris-areg                     August 2004


   (start(network) <= start(search)) AND (end(network) >= end(search))

   [2] Given a range, find only the most specific network that contains
   that range (could be multiple networks, but usually single); This is
   the set of networks from [1], with the provision that: no network in
   the return set is contained by any other network in the set.  If
   there are exact match networks in the set from [1], they both must
   appear in the result set.  The result set must not contain a network
   that is exact match to the query range.


   A  |-------------------------------|
   B  |---------------------------|
   C            |-------|
   Query  |- - - - - - - - - -|


                      Figure 5: Nesting Example 5

   In the above case, the query must return B.

   A  |-------------------------------|
   B  |---------------------------|
   C  |---------------------------|
   D            |-------|
   Query  |- - - - - - - - - -|

                      Figure 6: Nesting Example 6

   Here, the query must return B and C (they are exact matches of each
   other).

   A  |-------------------------------|
   B  |---------------------------|
   C  |---------------------------|
   D            |-------|
   Query        |- - - -|

                      Figure 7: Nesting Example 7

   Here, the query must return B and C (they are exact matches of each
   other).  D must not be in the result set, as it is exact match to the
   query.

   [3] Given a range, find all the networks that are fully within that
   range.  The set must not contain an exact match:

   (start(network) >= start(search)) AND (end(network) <= end(search))



Gunduz & Newton         Expires February 3, 2005               [Page 12]

Internet-Draft                 iris-areg                     August 2004


   AND NOT ((start(network) = start(search)) AND (end(network) =
   end(search)))

   [4] Given a range, find only the least specific networks that are
   fully within that range.  This is the set of networks from [3], with
   the provision that:

   no network in the return set contains any other network in the return
   set.

   Query   |- - - - - - - - - - - - - - - - - - - - - - -|

   A       |------------------|
   B                           |-------------------------|
   C           |--------|
   D                                      |---------|

                      Figure 8: Nesting Example 8

   [5] Given a range, find the networks that begin and end on the same
   IP addresses as the range ("exact match").

   That is, the networks that fulfill the following condition:

   (start(network) = start(search)) AND (end(network) = end(search))

   [6] Given a range find the exact match network if exists, and if not,
   perform the [2] search.

   For the cases [1]-[6], if a network handle is given as the input,
   then the server must find the network with this handle, and then
   perform the specified search for its range.

   Parent-child relationship searches:

   [7] Given a network handle, find the network that is the direct (one
   level up) parent of the network with the given handle.

   [8] Given a network handle, find the network or networks that are
   direct (one level down) children of the network with the handle
   given.










Gunduz & Newton         Expires February 3, 2005               [Page 13]

Internet-Draft                 iris-areg                     August 2004


5.  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" >

     <import namespace="urn:ietf:params:xml:ns:iris1" />

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

     <!-- ========================================= -->
     <!--                                           -->
     <!-- Query Types                               -->
     <!--                                           -->
     <!-- ========================================= -->

     <!--                                           -->
     <!-- Find Organizations By Name                -->
     <!-- Find Autonomous Systems By Name           -->
     <!-- Find Networks By Name                     -->
     <!--                                           -->

     <complexType
       name="findByNameType" >
       <complexContent>
         <extension
           base="iris:queryType">
           <sequence>
             <element
               name="name"
               type="areg:exactOrPartialMatchParameter" />
           </sequence>
         </extension>
       </complexContent>



Gunduz & Newton         Expires February 3, 2005               [Page 14]

Internet-Draft                 iris-areg                     August 2004


     </complexType>

     <element
       name="findOrganizations"
       type="areg:findByNameType"
       substitutionGroup="iris:query" />

     <element
       name="findNetworks"
       type="areg:findByNameType"
       substitutionGroup="iris:query" />

     <element
       name="findAutonomousSystems"
       type="areg:findByNameType"
       substitutionGroup="iris:query" />

     <!--                                           -->
     <!-- Address/Address Range type for            -->
     <!--   Find Network                            -->
     <!--                                           -->

     <complexType
       name="addressRangeType">
       <sequence>
         <element
           name="start"
           type="token" />
         <element
           name="end"
           type="token"
           minOccurs="0"
           maxOccurs="1" />
       </sequence>
     </complexType>

     <!--                                           -->
     <!-- Find Networks By Address                  -->
     <!--                                           -->

     <complexType
       name="findNetworksByAddressType" >
       <complexContent>
         <extension
           base="iris:queryType">
           <sequence>
             <choice>
               <element



Gunduz & Newton         Expires February 3, 2005               [Page 15]

Internet-Draft                 iris-areg                     August 2004


                 name="networkHandle"
                 type="token" />
               <element
                 name="ipv4Address"
                 type="areg:addressRangeType" />
               <element
                 name="ipv4CIDR"
                 type="token" />
               <element
                 name="ipv6Address"
                 type="areg:addressRangeType" />
               <element
                 name="ipv6CIDR"
                 type="token" />
             </choice>
             <element
               name="specificity">
               <complexType>
                 <simpleContent>
                   <extension
                     base="areg:specificityType" >
                     <attribute
                       name="allowEquivalences"
                       type="boolean"
                       default="false" />
                   </extension>
                 </simpleContent>
               </complexType>
             </element>
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="findNetworksByAddress"
       type="areg:findNetworksByAddressType"
       substitutionGroup="iris:query" />

     <simpleType
       name="specificityType">
       <restriction
         base="string">
           <enumeration
             value="less" />
           <enumeration
             value="least" />
           <enumeration



Gunduz & Newton         Expires February 3, 2005               [Page 16]

Internet-Draft                 iris-areg                     August 2004


             value="more" />
           <enumeration
             value="most" />
       </restriction>
     </simpleType>

     <!--                                           -->
     <!-- Find Contacts                             -->
     <!--                                           -->

     <complexType
       name="findContactsType">
       <complexContent>
         <extension
           base="iris:queryType">
           <choice>
             <element
               name="commonName"
               type="areg:exactOrPartialMatchParameter" />
             <element
               name="eMail"
               type="areg:domainResourceParameter" />
           </choice>
         </extension>
       </complexContent>
     </complexType>

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

     <complexType
       name="exactOrPartialMatchParameter">
       <choice>
         <group
           ref="areg:partialMatchGroup" />
         <group
           ref="areg:exactMatchGroup" />
       </choice>
     </complexType>

     <complexType
       name="domainResourceParameter" >
       <choice>
         <group
           ref="areg:exactMatchGroup" />
         <element



Gunduz & Newton         Expires February 3, 2005               [Page 17]

Internet-Draft                 iris-areg                     August 2004


           name="inDomain"
           type="token" />
       </choice>
     </complexType>

     <group
       name="partialMatchGroup">
       <sequence>
         <element
           name="beginsWith"
           minOccurs="1"
           maxOccurs="1" >
           <simpleType>
             <restriction
               base="token">
               <minLength
                 value="1"/>
             </restriction>
           </simpleType>
         </element>
         <element
           name="endsWith"
           minOccurs="0"
           maxOccurs="1" >
           <simpleType>
             <restriction
               base="token">
               <minLength
                 value="1"/>
             </restriction>
           </simpleType>
         </element>
       </sequence>
     </group>

     <group
       name="exactMatchGroup">
       <sequence>
         <element
           name="exactMatch"
           type="normalizedString" />
       </sequence>
     </group>

     <!-- ========================================= -->
     <!--                                           -->
     <!-- Result Types                              -->
     <!--                                           -->



Gunduz & Newton         Expires February 3, 2005               [Page 18]

Internet-Draft                 iris-areg                     August 2004


     <!-- ========================================= -->

     <!--                                           -->
     <!-- IPv4 & IPv6 Network Results               -->
     <!--                                           -->

     <complexType
       name="ipNetworkType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="networkHandle"
               type="token" />
             <element
               name="name"
               minOccurs="0"
               maxOccurs="1"
               type="normalizedString" />
             <element
               name="cidrAddress"
               type="token"
               minOccurs="1"
               maxOccurs="unbounded" />
             <element
               name="startAddress"
               type="token" />
             <element
               name="endAddress"
               type="token" />
             <element
               name="networkType"
               type="normalizedString" />
             <element
               name="nameServer"
               type="normalizedString"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="organization"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <choice
               minOccurs="0"
               maxOccurs="1" >
               <element



Gunduz & Newton         Expires February 3, 2005               [Page 19]

Internet-Draft                 iris-areg                     August 2004


                 name="parent"
                 type="iris:entityType" />
               <element
                 name="noParent">
                 <complexType/>
               </element>
             </choice>
             <group
               ref="areg:contactGroup" />
             <group
               ref="areg:commonGroup" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="ipv4Network"
       type="areg:ipNetworkType"
       substitutionGroup="iris:result" />

     <element
       name="ipv6Network"
       type="areg:ipNetworkType"
       substitutionGroup="iris:result" />

     <!--                                           -->
     <!-- Autonomous System                         -->
     <!--                                           -->

     <complexType
       name="autonomousSystemType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="asHandle"
               type="token" />
             <element
               name="asNumberStart"
               type="integer"
               minOccurs="1"
               maxOccurs="1" />
             <element
               name="asNumberEnd"
               type="integer"
               minOccurs="0"



Gunduz & Newton         Expires February 3, 2005               [Page 20]

Internet-Draft                 iris-areg                     August 2004


               maxOccurs="1" />
             <element
               name="name"
               type="normalizedString"
               minOccurs="0"
               maxOccurs="1" />
             <element
               name="organization"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="1" />
             <group
               ref="areg:contactGroup" />
             <group
               ref="areg:commonGroup" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

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

     <!--                                           -->
     <!-- Contact                                   -->
     <!--                                           -->

     <complexType
       name="contactType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="contactHandle"
               type="token" />
             <choice>
               <sequence>
                 <element
                   name="firstName"
                   type="normalizedString"
                   minOccurs="0"
                   maxOccurs="1" />
                 <element
                   name="middleName"
                   minOccurs="0"



Gunduz & Newton         Expires February 3, 2005               [Page 21]

Internet-Draft                 iris-areg                     August 2004


                   maxOccurs="1"
                   type="normalizedString" />
                 <element
                   name="lastName"
                   type="normalizedString" />
               </sequence>
               <element
                 name="role"
                 type="normalizedString" />
             </choice>
             <element
               name="eMail"
               type="normalizedString"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="sip"
               type="normalizedString"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="organization"
               type="iris:entityType"
               minOccurs="0"
               maxOccurs="unbounded" />
             <element
               name="phone"
               minOccurs="0"
               maxOccurs="unbounded" >
               <complexType>
                 <sequence>
                   <element
                     name="number"
                     type="normalizedString" />
                   <element
                     name="extension"
                     type="normalizedString"
                     minOccurs="0"
                     maxOccurs="unbounded" />
                   <element
                     name="type"
                     type="normalizedString" />
                     minOccurs="0"
                     maxOccurs="1" />
                 </sequence>
               </complexType>
             </element>
             <group



Gunduz & Newton         Expires February 3, 2005               [Page 22]

Internet-Draft                 iris-areg                     August 2004


               ref="areg:commonGroup" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

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

     <!--                                           -->
     <!-- Organization                              -->
     <!--                                           -->

     <complexType
       name="organizationType">
       <complexContent>
         <extension
           base="iris:resultType">
           <sequence>
             <element
               name="name"
               type="normalizedString" />
             <element
               name="id"
               type="token" />
             <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"



Gunduz & Newton         Expires February 3, 2005               [Page 23]

Internet-Draft                 iris-areg                     August 2004


               type="token"
               minOccurs="0"
               maxOccurs="1" />
             <group
               ref="areg:contactGroup" />
             <group
               ref="areg:commonGroup" />
           </sequence>
         </extension>
       </complexContent>
     </complexType>

     <element
       name="organization"
       type="areg:organizationType"
       substitutionGroup="iris:result" />

     <group
       name="contactGroup">
       <sequence>
         <element
           name="adminContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="techContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="nocContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="abuseContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
         <element
           name="otherContact"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="unbounded" />
       </sequence>
     </group>




Gunduz & Newton         Expires February 3, 2005               [Page 24]

Internet-Draft                 iris-areg                     August 2004


     <group
       name="commonGroup">
       <sequence>
         <element
           name="numberResourceRegistry"
           type="iris:entityType"
           minOccurs="0"
           maxOccurs="1" />
         <element
           name="registrationDate"
           type="dateTime"
           minOccurs="0"
           maxOccurs="1" />
         <element
           name="lastUpdatedDate"
           type="dateTime"
           minOccurs="0"
           maxOccurs="1" />
         <element
           ref="iris:seeAlso"
           minOccurs="0"
           maxOccurs="unbounded" />
       </sequence>
     </group>

   </schema>

                                Figure 9























Gunduz & Newton         Expires February 3, 2005               [Page 25]

Internet-Draft                 iris-areg                     August 2004


6.  BEEP Transport Compliance

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

6.1  Message Pattern

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

6.2  Server Authentication

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





































Gunduz & Newton         Expires February 3, 2005               [Page 26]

Internet-Draft                 iris-areg                     August 2004


7.  URI Resolution

7.1  Application Service Label

   The application service label associated with this registry type MUST
   be "AREG1".  This is the abbreviated form the URN for this registry
   type, urn:ietf:params:xml:ns:areg1.

7.2  Top-Down Resolution

   The top-down alternative resolution method MUST be identified as
   'top' in IRIS URI's.

   The process for this resolution method differs from the
   direct-resolution method 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 reverse-map domain name is reduced to the appropriate least
       two components (e.g.  "in-addr.arpa").
   3.  The IRIS [9] direct resolution method is tried on this
       reverse-map domain name.
   4.  If no records are found, then the component in the original
       reverse-map domain name to the right of the left-most component
       of this reverse-map domain name is prepended, and the third step
       is repeated (e.g.  if "in-addr.arpa" then "64.in-addr.arpa", if
       "64.in-addr.arpa" then "83.64.in-addr.arpa").
   5.  If all the components of the original reverse-map domain name
       from step one are present and no records are found, then the
       original IP address is used and the port number used is the
       well-known port for the default protocol of IRIS.


















Gunduz & Newton         Expires February 3, 2005               [Page 27]

Internet-Draft                 iris-areg                     August 2004


8.  Internationalization Considerations

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















































Gunduz & Newton         Expires February 3, 2005               [Page 28]

Internet-Draft                 iris-areg                     August 2004


9.  IANA Considerations

   The following URN will need to be registered with IANA according to
   the IANA considerations defined in IRIS [9]:
      urn:ietf:params:xml:ns:areg1

   The following NAPSTR application service label will need to be
   registered with IANA according to the IANA considerations defined in
   IRIS [9]:
      AREG1









































Gunduz & Newton         Expires February 3, 2005               [Page 29]

Internet-Draft                 iris-areg                     August 2004


10.  Security Considerations

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

11  References

   [1]   Mockapetris, P., "Domain names - implementation and
         specification", STD 13, RFC 1035, November 1987.

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

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

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

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

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

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

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

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

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

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



Gunduz & Newton         Expires February 3, 2005               [Page 30]

Internet-Draft                 iris-areg                     August 2004


   [12]  International Organization for Standardization, "Codes for the
         representation of names of countries, 3rd edition", ISO
         Standard 3166, August 1988.


Authors' Addresses

   Engin Gunduz
   RIPE NCC
   Singel 258
   Amsterdam  1016 AB
   The Netherlands

   Phone: +31 20 535 4427
   EMail: engin@ripe.net


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

   Phone: +1 703 948 3382
   EMail: andy@hxr.us; anewton@verisignlabs.com


























Gunduz & Newton         Expires February 3, 2005               [Page 31]

Internet-Draft                 iris-areg                     August 2004


Appendix A.  Example Requests and Responses

   The examples in this section use the string "C:" to denote data sent
   by a client to a server and the string "S:" to denote data sent by a
   server to a client.

A.1  Example 1

   The following is an example of entity lookup for the contact-handle
   of 'JN560-ARIN'.

   C: <?xml version="1.0"?>
   C: <request xmlns="urn:ietf:params:xml:ns:iris1"
   C:   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   C:   xsi:schemaLocation="urn:ietf:params:xml:ns:iris1 iris.xsd" >
   C:
   C:   <searchSet>
   C:
   C:     <lookupEntity
   C:       registryType="urn:ietf:params:xml:ns:areg1"
   C:       entityClass="contact-handle"
   C:       entityName="JN560-ARIN" />
   C:
   C:   </searchSet>
   C:
   C: </request>

   S: <?xml version="1.0"?>
   S: <iris:response
   S:   xmlns:iris="urn:ietf:params:xml:ns:iris1"
   S:   xmlns="urn:ietf:params:xml:ns:areg1"
   S:   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   S:
   S:   <iris:resultSet>
   S:     <iris:answer>
   S:
   S:       <contact
   S:         authority="arin.net"
   S:         registryType="areg1"
   S:         entityClass="contact-handle"
   S:         entityName="JN560-ARIN">
   S:
   S:         <contactHandle>JN560-ARIN</contactHandle>
   S:
   S:         <firstName>John</firstName>
   S:         <lastName>Niland</lastName>
   S:
   S:         <organization



Gunduz & Newton         Expires February 3, 2005               [Page 32]

Internet-Draft                 iris-areg                     August 2004


   S:           iris:referentType="organization"
   S:           authority="arin.net"
   S:           registryType="areg1"
   S:           entityClass="organization-id"
   S:           entityName="VERIS">
   S:           <iris:displayName
   S:             language="en">
   S:             VeriSign, Inc.
   S:           </iris:displayName>
   S:         </organization>
   S:
   S:         <phone>
   S:           <number>+1-703-948-4300</number>
   S:           <type>office</type>
   S:         </phone>
   S:
   S:       </contact>
   S:
   S:     </iris:answer>
   S:   </iris:resultSet>
   S:
   S: </iris:response>

                          Figure 10: Example 1


A.2  Example 2

   The following example shows a query to find the IP networks
   containing a given address.

   C: <?xml version="1.0"?>
   C: <request xmlns="urn:ietf:params:xml:ns:iris1"
   C:          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   C:
   C:   <searchSet>
   C:     <findNetworksByAddress
   C:       xmlns="urn:ietf:params:xml:ns:areg1">
   C:
   C:       <ipv4Address>
   C:         <start>65.201.175.9</start>
   C:       </ipv4Address>
   C:
   C:       <specificity allowEquivalences="true">most</specificity>
   C:
   C:     </findNetworksByAddress>
   C:   </searchSet>
   C:



Gunduz & Newton         Expires February 3, 2005               [Page 33]

Internet-Draft                 iris-areg                     August 2004


   C: </request>

   S: <?xml version="1.0"?>
   S: <iris:response xmlns:iris="urn:ietf:params:xml:ns:iris1"
   S:                xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   S:
   S:   <iris:resultSet>
   S:     <iris:answer>
   S:       <areg:ipv4Network
   S:         xmlns="urn:ietf:params:xml:ns:areg1"
   S:         xmlns:areg="urn:ietf:params:xml:ns:areg1"
   S:         xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
   S:         authority="65.0.0.0" registryType="areg1"
   S:         entityClass="ipv4-handle" entityName="NET-65-201-175-0-1" >
   S:         <networkHandle>
   S:           NET-65-201-175-0-1
   S:         </networkHandle>
   S:         <name>
   S:           UU-65-201-175-D6
   S:         </name>
   S:         <cidrAddress>
   S:           65.201.175.0/24
   S:         </cidrAddress>
   S:         <startAddress>
   S:           65.201.175.0
   S:         </startAddress>
   S:         <endAddress>
   S:           65.201.175.255
   S:         </endAddress>
   S:         <networkType>reassigned</networkType>
   S:         <nameServer>auth03.ns.uu.net</nameServer>
   S:         <nameServer>auth00.ns.uu.net</nameServer>
   S:         <organization
   S:           iris:referentType="areg:organization"
   S:           authority="arin.net" registryType="areg1"
   S:           entityClass="organization-id" entityName="VERIS">
   S:           <iris:displayName language="en">
   S:             VeriSign, Inc.
   S:           </iris:displayName>
   S:         </organization>
   S:         <parent
   S:           iris:referentType="areg:ipv4Network"
   S:           authority="65.0.0.0" registryType="areg1"
   S:           entityClass="ipv4-handle" entityName="NET-65-192-0-0-1"/>
   S:         <techContact
   S:           iris:referentType="areg:contact"
   S:           authority="arin.net" registryType="areg1"
   S:           entityClass="contact-handle" entityName="JN560-ARIN">



Gunduz & Newton         Expires February 3, 2005               [Page 34]

Internet-Draft                 iris-areg                     August 2004


   S:           <iris:displayName language="en">
   S:             Niland, John
   S:           </iris:displayName>
   S:         </techContact>
   S:         <registrationDate>
   S:           2002-11-18T00:00:00-00:00
   S:         </registrationDate>
   S:         <lastUpdatedDate>
   S:           2002-11-18T00:00:00-00:00
   S:         </lastUpdatedDate>
   S:         <iris:seeAlso
   S:           iris:referentType="ANY"
   S:           authority="arin.net" registryType="areg1"
   S:           entityClass="service-defintion" entityName="portability-notice"/>
   S:       </areg:ipv4Network>
   S:       <areg:ipv4Network
   S:         xmlns="urn:ietf:params:xml:ns:areg1"
   S:         xmlns:areg="urn:ietf:params:xml:ns:areg1"
   S:         xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
   S:         authority="65.0.0.0" registryType="areg1"
   S:         entityClass="ipv4-handle" entityName="NET-65-192-0-0-1" >
   S:         <networkHandle>
   S:           NET-65-192-0-0-1
   S:         </networkHandle>
   S:         <name>
   S:           UUNET65
   S:         </name>
   S:         <cidrAddress>
   S:           65.192.0.0/11
   S:         </cidrAddress>
   S:         <startAddress>
   S:           65.192.0.0
   S:         </startAddress>
   S:         <endAddress>
   S:           65.223.255.255
   S:         </endAddress>
   S:         <networkType>direct allocation</networkType>
   S:         <nameServer>auth03.ns.uu.net</nameServer>
   S:         <nameServer>auth00.ns.uu.net</nameServer>
   S:         <organization
   S:           iris:referentType="areg:organization"
   S:           authority="arin.net" registryType="areg1"
   S:           entityClass="organization-id" entityName="UU">
   S:           <iris:displayName language="en">
   S:             UUNET Technologies, Inc.
   S:           </iris:displayName>
   S:         </organization>
   S:         <parent



Gunduz & Newton         Expires February 3, 2005               [Page 35]

Internet-Draft                 iris-areg                     August 2004


   S:           iris:referentType="areg:ipv4Network"
   S:           authority="65.0.0.0" registryType="areg1"
   S:           entityClass="ipv4-handle" entityName="NET-65-0-0-0-1"/>
   S:         <techContact
   S:           iris:referentType="areg:contact"
   S:           authority="arin.net" registryType="areg1"
   S:           entityClass="contact-handle" entityName="OA12-ARIN" />
   S:         <registrationDate>
   S:           2000-10-27T00:00:00-00:00
   S:         </registrationDate>
   S:         <lastUpdatedDate>
   S:           2002-02-13T00:00:00-00:00
   S:         </lastUpdatedDate>
   S:         <iris:seeAlso
   S:           iris:referentType="ANY"
   S:           authority="arin.net" registryType="areg1"
   S:           entityClass="service-defintion" entityName="portability-notice"/>
   S:       </areg:ipv4Network>
   S:     </iris:answer>
   S:     <iris:additional>
   S:       <iris:simpleEntity
   S:         authority="arin.net" registryType="areg1"
   S:         entityClass="service-definition" entityName="portability-notice" >
   S:         <iris:property name="portability" language="en">
   S:           Addresses within this block are non-portable.
   S:         </iris:property>
   S:       </iris:simpleEntity>
   S:     </iris:additional>
   S:   </iris:resultSet>
   S:
   S: </iris:response>

                          Figure 11: Example 2


















Gunduz & Newton         Expires February 3, 2005               [Page 36]

Internet-Draft                 iris-areg                     August 2004


Appendix B.  Acknowledgements

   Many of the concepts concerning the use of SRV records for step-wise
   refinement towards finding authoritative servers and many of the
   details of result objects in this draft were originally created by
   Eric A.  Hall in his memos regarding the use of LDAP to satisfy the
   CRISP requirements.  These concepts have contributed significantly to
   the development of this protocol.











































Gunduz & Newton         Expires February 3, 2005               [Page 37]

Internet-Draft                 iris-areg                     August 2004


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




Gunduz & Newton         Expires February 3, 2005               [Page 38]