One document matched: draft-ietf-crisp-iris-areg-02.txt
Differences from draft-ietf-crisp-iris-areg-01.txt
Network Working Group A. Newton
Internet-Draft VeriSign, Inc.
Expires: December 5, 2003 June 06, 2003
IRIS - An Address Registry (areg) Type for the Internet Registry
Information Service
draft-ietf-crisp-iris-areg-02
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 December 5, 2003.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document describes an IRIS (draft-ietf-crisp-iris-core-02.txt )
registry schema for IP address 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.
Newton Expires December 5, 2003 [Page 1]
Internet-Draft iris-areg June 2003
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>, <findAutonomousSystems>, and
<findNetworks> . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.3 <findNetworkByAddress> . . . . . . . . . . . . . . . . . . . 5
3.1.4 <findSubNetworksByParent> . . . . . . . . . . . . . . . . . 6
3.2 Result Derivatives . . . . . . . . . . . . . . . . . . . . . 6
3.2.1 <nameServer> Result . . . . . . . . . . . . . . . . . . . . 6
3.2.2 <ipv4Network> Result . . . . . . . . . . . . . . . . . . . . 6
3.2.3 <ipv6Network> Result . . . . . . . . . . . . . . . . . . . . 7
3.2.4 <autonomousSystem> Result . . . . . . . . . . . . . . . . . 8
3.2.5 <contact> Result . . . . . . . . . . . . . . . . . . . . . . 9
3.2.6 <organization> Result . . . . . . . . . . . . . . . . . . . 9
3.3 Support for <iris:lookupEntity> . . . . . . . . . . . . . . 10
4. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . 12
5. BEEP Transport Compliance . . . . . . . . . . . . . . . . . 23
5.1 Message Pattern . . . . . . . . . . . . . . . . . . . . . . 23
5.2 Server Authentication . . . . . . . . . . . . . . . . . . . 23
6. URI Resolution . . . . . . . . . . . . . . . . . . . . . . . 24
7. Internationalization Considerations . . . . . . . . . . . . 25
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 26
9. Security Considerations . . . . . . . . . . . . . . . . . . 27
References . . . . . . . . . . . . . . . . . . . . . . . . . 28
Author's Address . . . . . . . . . . . . . . . . . . . . . . 29
A. An Example Request and Response . . . . . . . . . . . . . . 30
B. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35
Intellectual Property and Copyright Statements . . . . . . . 36
Newton Expires December 5, 2003 [Page 2]
Internet-Draft iris-areg June 2003
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].
Newton Expires December 5, 2003 [Page 3]
Internet-Draft iris-areg June 2003
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].
Newton Expires December 5, 2003 [Page 4]
Internet-Draft iris-areg June 2003
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 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 child elements <firstName>, <middleName>, and <lastName> allow
the search to be constrained against the name of the contact. These
elements may either have as children the <exactMatch> element or the
<beginsWith> and <endsWith> elements.
<eMail> contrains 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).
3.1.2 <findOrganizations>, <findAutonomousSystems>, and <findNetworks>
The <findOrganizations>, <findAutonomousSystesm>, and <findNetworks>
elements allow for searches by name of organizations, autonomous
systems, and networks, respectively. All three have the same format.
The child element <name> may either have as children the <exactMatch>
element or the <beginsWith> and <endsWith> elements.
3.1.3 <findNetworkByAddress>
The <findNetworkByAddress> element is a query for a network given the
IP address. It contains one of the two elements <ipv4Address> and
<ipv6Address>, which contain an IPv4 and IPv6 address, respectively.
The results from this query MUST be either the <ipv4Network> result
or the <ipv6Network> result. More than one network result MAY be
Newton Expires December 5, 2003 [Page 5]
Internet-Draft iris-areg June 2003
returned.
3.1.4 <findSubNetworksByParent>
The <findSubNetworksByParent> element is a query to find the children
of a network, or its subnetworks, given the handle to the parent. It
has a sole child element of <networkHandle> containing the handle of
the parent network.
3.2 Result Derivatives
3.2.1 <nameServer> Result
The <nameServer> element represents a name server. It contains
elements for the fully qualified domain name of the name server, the
IP addresses of the name server, and references to the name server
contacts.
The <nameServerContacts> element contains multiple children. Each
child is an <iris:entity> element as described by IRIS [9]. The
referent of each <iris:entity> element MUST be a <contact> (Section
3.2.5) result.
The <iris:seeAlso> element contains <iris:entity> elements specifying
entities that are indirectly associated with the name server.
3.2.2 <ipv4Network> Result
The <ipv4Network> element is a result representing an IPv4 network.
It has the following child elements:
o <ipv4NetworkHandle> contains the registry-unique assigned handle
for this network.
o <name> contains a human friendly name for the network.
o <cidrAddress> contains the network address of the network in CIDR
notation form.
o <startAddress> contains the first IPv4 address of the network.
o <endAddress> contains the last IPv4 address of the network.
o One of <directAllocation>, <directAssignment>, or <reassigned>
signifying the assignment and allocation status of the network.
o <organization> contains an <iris:entity> reference to the
organization assigned this network. The referent MUST be an
Newton Expires December 5, 2003 [Page 6]
Internet-Draft iris-areg June 2003
<organization> (Section 3.2.6) result.
o <parent> contains an <iris:entity> reference to the parent network
of this network. The referent MUST be an <ipv4Network> (Section
3.2.2) result.
o <nameServers> contains <iris:entity> element references to the
name servers doing reverse DNS resolution for the addresses in
this network. The referents MUST be <nameServer> (Section 3.2.1)
results.
o <netContacts> contains <iris:entity> element references to the
contacts for this network. The referents MUST be <contact>
(Section 3.2.5) results.
o <registrationDate> contains the date when the network was first
registered.
o <lastUpdatedDate> contains the date when information about this
network was last updated.
o The <iris:seeAlso> element contains <iris:entity> elements
specifying entities that are indirectly associated with this
network.
3.2.3 <ipv6Network> Result
The <ipv6Network> element is a result representing an IPv6 network.
It has the following child elements:
o <ipv6NetworkHandle> contains the registry-unique assigned handle
for this network.
o <name> contains a human friendly name for the network.
o <cidrAddress> contains the network address of the network in CIDR
notation form.
o <startAddress> contains the first IPv6 address of the network.
o <endAddress> contains the last IPv6 address of the network.
o One of <directAllocation>, <directAssignment>, or <reassigned>
signifying the assignment and allocation status of the network.
o <organization> contains an <iris:entity> reference to the
organization assigned this network. The referent MUST be an
Newton Expires December 5, 2003 [Page 7]
Internet-Draft iris-areg June 2003
<organization> (Section 3.2.6) result.
o <parent> contains an <iris:entity> reference to the parent network
of this network. The referent MUST be an <ipv6Network> (Section
3.2.3) result.
o <nameServers> contains <iris:entity> element references to the
name servers doing reverse DNS resolution for the addresses in
this network. The referents MUST be <nameServer> (Section 3.2.1)
results.
o <netContacts> contains <iris:entity> element references to the
contacts for this network. The referents MUST be <contact>
(Section 3.2.5) results.
o <registrationDate> contains the date when the network was first
registered.
o <lastUpdatedDate> contains the date when information about this
network was last updated.
o The <iris:seeAlso> element contains <iris:entity> elements
specifying entities that are indirectly associated with this
network.
3.2.4 <autonomousSystem> Result
The <autonomousSystem> element represents an assigned autonomous
system. It has the following children:
o <asHandle> contains a registry-unqiue assigned handle for this
autonomous system.
o <number> contains the globally unique autonomous system number.
o <name> contains a human friendly name of this autonomous system.
o <organization> contains an <iris:entity> reference to the
organization assigned this autonomous system. The referent MUST
be an <organization> (Section 3.2.6) result.
o <asContacts> contains <iris:entity> element references to the
contacts for this autonomous system. The referents MUST be
<contact> (Section 3.2.5) results.
o The <iris:seeAlso> element contains <iris:entity> elements
specifying entities that are indirectly associated with this
Newton Expires December 5, 2003 [Page 8]
Internet-Draft iris-areg June 2003
autonomous system.
3.2.5 <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>, <middelName>, 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 <organization> contains an <iris:entity> reference to the
organization associated with this contact. The referent MUST be
an <organization> (Section 3.2.6) result.
o <phone> contains child elements describing the phone number of the
contact. The child elements are <number>, <extension>, and
<type>.
o The <iris:seeAlso> element contains <iris:entity> elements
specifying entities that are indirectly associated with this
contact.
3.2.6 <organization> Result
The <organization> element represents an organization responsible for
network resources. 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 street 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.
Newton Expires December 5, 2003 [Page 9]
Internet-Draft iris-areg June 2003
o <postalCode> contains the postal code where this organization is
located.
o <country> contains the country code where this organization is
located.
o <adminContacts> contains <iris:entity> element references to the
administrative contacts for this organization. The referents MUST
be <contact> (Section 3.2.5) results.
o <techContacts> contains <iris:entity> element references to the
technical contacts for this organization. The referents MUST be
<contact> (Section 3.2.5) results.
o <abuseContacts> contains <iris:entity> element references to the
abuse contacts for this organization. The referents MUST be
<contact> (Section 3.2.5) results.
o <nocContacts> contains <iris:entity> element references to the NOC
contacts for this organization. The referents MUST be <contact>
(Section 3.2.5) results.
o The <iris:seeAlso> element contains <iris:entity> elements
specifying entities that are indirectly associated with this
contact.
3.3 Support for <iris:lookupEntity>
The following types of entity classes are recognized by the
<lookupEntity> query of IRIS for this registry:
o name-server - the fully qualified domains names of nameservers.
Queries with these names will yield a <nameServer> result. A host
may be multi-homed and therefore known by many domain names.
o ns-handle - a registry unique identifier of a nameserver. Yields
a <nameServer> result.
o ipv4-ns - the IPv4 address of a nameserver. Yields a <nameServer>
result.
o ipv6-ns - the IPv6 address of a nameserver. Yields a <nameServer>
result.
o ipv4-address - a network for which an IPv4 address resides.
Queries with these names will yield a <ipv4Network> result.
Newton Expires December 5, 2003 [Page 10]
Internet-Draft iris-areg June 2003
o ipv6-address - a network for which an IPv6 address resides.
Queries with these names will yield a <ipv6Network> result.
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.
Newton Expires December 5, 2003 [Page 11]
Internet-Draft iris-areg June 2003
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" >
<import namespace="urn:ietf:params:xml:ns:iris1" />
<annotation>
<documentation>
IP address registry schema
derived from IRIS schema
</documentation>
</annotation>
<!-- -->
<!-- Query types -->
<!-- -->
<complexType name="findByNameType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="name"
type="areg:exactOrPartialMatchParameter" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findOrganizations"
type="areg:findByNameType"
substitutionGroup="iris:query" />
<element name="findAutonomousSystems"
type="areg:findByNameType"
substitutionGroup="iris:query" />
<element name="findNetworks"
Newton Expires December 5, 2003 [Page 12]
Internet-Draft iris-areg June 2003
type="areg:findByNameType"
substitutionGroup="iris:query" />
<complexType name="findNetworksByAddressType" >
<complexContent>
<extension base="iris:queryType">
<choice>
<element name="ipv4Address"
type="token" />
<element name="ipv6Address"
type="token" />
</choice>
</extension>
</complexContent>
</complexType>
<element name="findNetworksByAddress"
type="areg:findNetworksByAddressType"
substitutionGroup="iris:query" />
<complexType name="findSubNetworksByParentType" >
<complexContent>
<extension base="iris:queryType">
<sequence>
<element name="networkHandle"
type="token" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="findSubNetworksByParent"
type="areg:findSubNetworksByParentType"
substitutionGroup="iris:query" />
<complexType name="findContactsType">
<complexContent>
<extension base="iris:queryType">
<choice>
<element name="firstName"
type="areg:exactOrPartialMatchParameter" />
<element name="middleName"
type="areg:exactOrPartialMatchParameter" />
<element name="lastName"
type="areg:exactOrPartialMatchParameter" />
<element name="eMail"
type="areg:domainResourceParameter" />
</choice>
Newton Expires December 5, 2003 [Page 13]
Internet-Draft iris-areg June 2003
</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 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" />
Newton Expires December 5, 2003 [Page 14]
Internet-Draft iris-areg June 2003
</sequence>
</group>
<!-- -->
<!-- Result types -->
<!-- -->
<complexType name="nameServerType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="nameServerHandle"
type="token" />
<element name="name"
type="normalizedString" />
<element name="ipV4Addresses"
minOccurs="0" maxOccurs="1" >
<complexType>
<sequence>
<element name="ipV4Address"
type="token"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element name="ipV6Addresses"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element name="ipV6Address"
type="token"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element name="nameServerContacts"
minOccurs="0" maxOccurs="1" >
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element ref="iris:seeAlso"
minOccurs="0" maxOccurs="1" />
</sequence>
</extension>
Newton Expires December 5, 2003 [Page 15]
Internet-Draft iris-areg June 2003
</complexContent>
</complexType>
<element name="nameServer"
type="areg:nameServerType"
substitutionGroup="iris:result" />
<complexType name="ipv4NetworkType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="ipv4NetworkHandle"
type="token" />
<element name="name"
minOccurs="0" maxOccurs="1"
type="normalizedString" />
<element name="cidrAddress"
type="token" />
<element name="startAddress"
type="token" />
<element name="endAddress"
type="token" />
<choice>
<element name="directAllocation">
<complexType/>
</element>
<element name="directAssignment">
<complexType/>
</element>
<element name="reassigned">
<complexType/>
</element>
</choice>
<element name="organization"
minOccurs="1" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity" />
</sequence>
</complexType>
</element>
<element name="parent"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity" />
</sequence>
</complexType>
Newton Expires December 5, 2003 [Page 16]
Internet-Draft iris-areg June 2003
</element>
<element name="nameServers"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element name="netContacts"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<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="1" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="ipv4Network"
type="areg:ipv4NetworkType"
substitutionGroup="iris:result" />
<complexType name="ipv6NetworkType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="ipv6NetworkHandle"
type="token" />
<element name="name"
minOccurs="0" maxOccurs="1"
type="normalizedString" />
<element name="cidrAddress"
type="token" />
<element name="startAddress"
Newton Expires December 5, 2003 [Page 17]
Internet-Draft iris-areg June 2003
type="token" />
<element name="endAddress"
type="token" />
<choice>
<element name="directAllocation">
<complexType/>
</element>
<element name="directAssignment">
<complexType/>
</element>
<element name="reassigned">
<complexType/>
</element>
</choice>
<element name="organization"
minOccurs="1" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity" />
</sequence>
</complexType>
</element>
<element name="parent"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity" />
</sequence>
</complexType>
</element>
<element name="nameServers"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element name="netContacts"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
Newton Expires December 5, 2003 [Page 18]
Internet-Draft iris-areg June 2003
<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="1" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="ipv6Network"
type="areg:ipv6NetworkType"
substitutionGroup="iris:result" />
<complexType name="autonomousSystemType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="asHandle"
type="token" />
<element name="number"
type="integer" />
<element name="name"
type="normalizedString" />
<element name="organization"
minOccurs="1" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"/>
</sequence>
</complexType>
</element>
<element name="asContacts"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element ref="iris:seeAlso"
minOccurs="0" maxOccurs="1" />
</sequence>
</extension>
Newton Expires December 5, 2003 [Page 19]
Internet-Draft iris-areg June 2003
</complexContent>
</complexType>
<element name="autonomousSystem"
type="areg:autonomousSystemType"
substitutionGroup="iris:result" />
<complexType name="contactType">
<complexContent>
<extension base="iris:resultType">
<sequence>
<element name="contactHandle"
type="token" />
<choice>
<sequence>
<element name="firstName"
type="normalizedString" />
<element name="middleName"
minOccurs="0" maxOccurs="1"
type="normalizedString" />
<element name="lastName"
type="normalizedString" />
</sequence>
<element name="role"
type="normalizedString" />
</choice>
<element name="eMail"
type="normalizedString"
minOccurs="0" maxOccurs="2" />
<element name="organization"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="1" />
</sequence>
</complexType>
</element>
<element name="phone"
minOccurs="0" maxOccurs="2" >
<complexType>
<sequence>
<element name="number"
type="normalizedString" />
<element name="extension"
type="normalizedString"
minOccurs="0" maxOccurs="unbounded" />
<element name="type"
Newton Expires December 5, 2003 [Page 20]
Internet-Draft iris-areg June 2003
type="normalizedString" />
</sequence>
</complexType>
</element>
<element ref="iris:seeAlso"
minOccurs="0" maxOccurs="1" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="contact"
type="areg:contactType"
substitutionGroup="iris:result" />
<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"
type="token"
minOccurs="0" maxOccurs="1" />
<element name="adminContacts"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element name="techContacts"
Newton Expires December 5, 2003 [Page 21]
Internet-Draft iris-areg June 2003
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element name="abuseContacts"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element name="nocContacts"
minOccurs="0" maxOccurs="1">
<complexType>
<sequence>
<element ref="iris:entity"
minOccurs="1" maxOccurs="unbounded" />
</sequence>
</complexType>
</element>
<element ref="iris:seeAlso"
minOccurs="0" maxOccurs="1" />
</sequence>
</extension>
</complexContent>
</complexType>
<element name="organization"
type="areg:organizationType"
substitutionGroup="iris:result" />
</schema>
Figure 1
Newton Expires December 5, 2003 [Page 22]
Internet-Draft iris-areg June 2003
5. BEEP Transport Compliance
IRIS allows several extensions of the core capabilities. This
section outlines those extensions allowable by IRIS-BEEP [10].
5.1 Message Pattern
This registry type uses the default message pattern as described in
IRIS-BEEP [10].
5.2 Server Authentication
This registry type uses the default server authentication method as
described in IRIS-BEEP [10].
Newton Expires December 5, 2003 [Page 23]
Internet-Draft iris-areg June 2003
6. URI Resolution
The authority resolution of an IRIS URI for this registry type is
similar to the default resolution spelled out in IRIS [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 IRIS [9] default resolution process is tried on this
reverse-map domain name.
3. If no records are found, then the left-most component of the
reverse-map domain name is removed, and the second step is
repeated again (e.g. "37.83.64.in-addr.arpa" )
4. If all the components of the reverse-map domain name from step
one are removed 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.
The application service label associated with this registry type MUST
be "XP-IP". This label has no significance other than "XP" is short
for "CRISP" and "IP" is short for "Internet Protocol Address".
Because the service field, of which this label is just one of many
components, is limited to 32 characters, this label is purposefully
meaningful but short.
Newton Expires December 5, 2003 [Page 24]
Internet-Draft iris-areg June 2003
7. Internationalization Considerations
This document lays out no new considerations for internationalization
beyond that specified in IRIS [9].
Newton Expires December 5, 2003 [Page 25]
Internet-Draft iris-areg June 2003
8. 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]:
XP-IP
Newton Expires December 5, 2003 [Page 26]
Internet-Draft iris-areg June 2003
9. Security Considerations
This document lays out no new considerations for security precautions
beyond that specified in IRIS [9].
Newton Expires December 5, 2003 [Page 27]
Internet-Draft iris-areg June 2003
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.
Newton Expires December 5, 2003 [Page 28]
Internet-Draft iris-areg June 2003
Author's Address
Andrew L. Newton
VeriSign, Inc.
21345 Ridgetop Circle
Sterling, VA 20166
USA
Phone: +1 703 948 3382
EMail: anewton@verisignlabs.com; anewton@ecotroph.net
URI: http://www.verisignlabs.com/
Newton Expires December 5, 2003 [Page 29]
Internet-Draft iris-areg June 2003
Appendix A. An Example Request and Response
The following is an example of an IRIS request and response using
this registry schema.
This XML instance is a request to find a network given an IP
address.
<?xml version="1.0"?>
<request xmlns="urn:ietf:params:xml:ns:iris1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:iris1 iris.xsd" >
<searchSet>
<areg:findNetworksByAddress
xmlns:areg="urn:ietf:params:xml:ns:areg1"
xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd" >
<areg:ipv4Address>
65.201.175.9
</areg:ipv4Address>
</areg:findNetworksByAddress>
<bag>
AAAAB3NzaC1yc2EAAAABIwAAAIEA0ddD+W3Agl0Lel98G1r77fZ
c3nBl8CHdkmKuVGUy/ijmvdO5QxuSlU0R4BoCLZk/Sob22RApTn
T+ROMbXFQBrxGH08daAOy98WqpfAutWJri61JLpubIbaqhGyB48
Qt69V6OhYfFsJjvoNEOh1k2dgzXhSlzP3OMVSKRlBzGcO8=
</bag>
</searchSet>
</request>
Figure 2: areg-request.xml
This XML instance is a response from Figure 2.
<?xml version="1.0"?>
<response xmlns="urn:ietf:params:xml:ns:iris1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:iris1 iris.xsd" >
<resultSet>
Newton Expires December 5, 2003 [Page 30]
Internet-Draft iris-areg June 2003
<answer>
<areg:ipv4Network
xmlns="urn:ietf:params:xml:ns:areg1"
xmlns:areg="urn:ietf:params:xml:ns:areg1"
xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
authority="65.0.0.0" registryType="areg1"
entityClass="ipv4-handle" entityName="NET-65-201-175-0-1" >
<ipv4NetworkHandle>
NET-65-201-175-0-1
</ipv4NetworkHandle>
<name>
UU-65-201-175-D6
</name>
<cidrAddress>
65.201.175.0/24
</cidrAddress>
<startAddress>
65.201.175.0
</startAddress>
<endAddress>
65.201.175.255
</endAddress>
<reassigned/>
<organization>
<iris:entity authority="arin.net" registryType="areg1"
entityClass="organization-id" entityName="VERIS">
<displayName language="en">
VeriSign, Inc.
</displayName>
</iris:entity>
</organization>
<parent>
<iris:entity authority="65.0.0.0" registryType="areg1"
entityClass="ipv4-handle" entityName="NET-65-192-0-0-1"/>
</parent>
<nameServers>
<iris:entity authority="uu.net" registryType="areg1"
entityClass="ipv4-ns" entityName="AUTH03.NS.UU.NET"
bagRef="x1" />
<iris:entity authority="uu.net" registryType="areg1"
entityClass="ipv4-ns" entityName="AUTH00.NS.UU.NET"
bagRef="x1" />
</nameServers>
<netContacts>
<iris:entity authority="arin.net" registryType="areg1"
entityClass="contact-handle" entityName="JN560-ARIN">
<displayName language="en">
Newton Expires December 5, 2003 [Page 31]
Internet-Draft iris-areg June 2003
Niland, John
</displayName>
</iris:entity>
</netContacts>
<registrationDate>
2002-11-18
</registrationDate>
<lastUpdatedDate>
2002-11-18
</lastUpdatedDate>
<iris:seeAlso>
<iris:entity authority="arin.net" registryType="areg1"
entityClass="service-defintion" entityName="portability-notice"/>
</iris:seeAlso>
</areg:ipv4Network>
<areg:ipv4Network
xmlns="urn:ietf:params:xml:ns:areg1"
xmlns:areg="urn:ietf:params:xml:ns:areg1"
xsi:schemaLocation="urn:ietf:params:xml:ns:areg1 areg.xsd"
authority="65.0.0.0" registryType="areg1"
entityClass="ipv4-handle" entityName="NET-65-192-0-0-1" >
<ipv4NetworkHandle>
NET-65-192-0-0-1
</ipv4NetworkHandle>
<name>
UUNET65
</name>
<cidrAddress>
65.192.0.0/11
</cidrAddress>
<startAddress>
65.192.0.0
</startAddress>
<endAddress>
65.223.255.255
</endAddress>
<directAllocation/>
<organization>
<iris:entity authority="arin.net" registryType="areg1"
entityClass="organization-id" entityName="UU">
<displayName language="en">
UUNET Technologies, Inc.
</displayName>
</iris:entity>
</organization>
<parent>
<iris:entity authority="65.0.0.0" registryType="areg1"
Newton Expires December 5, 2003 [Page 32]
Internet-Draft iris-areg June 2003
entityClass="ipv4-handle" entityName="NET-65-0-0-0-1"/>
</parent>
<nameServers>
<iris:entity authority="uu.net" registryType="areg1"
entityClass="ipv4-ns" entityName="AUTH03.NS.UU.NET"
bagRef="x1" />
<iris:entity authority="uu.net" registryType="areg1"
entityClass="ipv4-ns" entityName="AUTH00.NS.UU.NET"
bagRef="x1" />
</nameServers>
<netContacts>
<iris:entity authority="arin.net" registryType="areg1"
entityClass="contact-handle" entityName="OA12-ARIN" />
</netContacts>
<registrationDate>
2000-10-27
</registrationDate>
<lastUpdatedDate>
2002-02-13
</lastUpdatedDate>
<iris:seeAlso>
<iris:entity authority="arin.net" registryType="areg1"
entityClass="service-defintion" entityName="portability-notice"/>
</iris:seeAlso>
</areg:ipv4Network>
</answer>
<additional>
<simpleEntity
authority="arin.net" registryType="areg1"
entityClass="service-definition" entityName="portability-notice" >
<property name="portability" language="en">
Addresses within this block are non-portable.
</property>
</simpleEntity>
</additional>
<bags>
<bag id="x1">
AAAAB3NzaC1yc2EAAAABIwAAAIEA0ddD+W3Agl0Lel98G1r77fZ
c3nBl8CHdkmKuVGUy/ijmvdO5QxuSlU0R4BoCLZk/Sob22RApTn
T+ROMbXFQBrxGH08daAOy98WqpfAutWJri61JLpubIbaqhGyB48
Qt69V6OhYfFsJjvoNEOh1k2dgzXhSlzP3OMVSKRlBzGcO8=
</bag>
</bags>
Newton Expires December 5, 2003 [Page 33]
Internet-Draft iris-areg June 2003
</resultSet>
</response>
Figure 3: areg-response.xml
Newton Expires December 5, 2003 [Page 34]
Internet-Draft iris-areg June 2003
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.
Newton Expires December 5, 2003 [Page 35]
Internet-Draft iris-areg June 2003
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property 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; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Copyright (C) The Internet Society (2003). 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 assignees.
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
Newton Expires December 5, 2003 [Page 36]
Internet-Draft iris-areg June 2003
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 December 5, 2003 [Page 37]
| PAFTECH AB 2003-2026 | 2026-04-24 03:00:34 |