draft-ietf-crisp-iris-dchk-00.txt   draft-ietf-crisp-iris-dchk-01.txt 
Network Working Group A. Newton Network Working Group A. Newton
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Expires: February 7, 2005 August 9, 2004 Expires: April 8, 2005 October 8, 2004
A Domain Availability Check (dchk) Registry Type for the Internet A Domain Availability Check (dchk) Registry Type for the Internet
Registry Information Service (IRIS) Registry Information Service (IRIS)
draft-ietf-crisp-iris-dchk-00 draft-ietf-crisp-iris-dchk-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, 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 and any of which I become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 7, 2005. This Internet-Draft will expire on April 8, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document describes a lightweight domain availability service This document describes a lightweight domain availability service
using the IRIS framework and the data model of the IRIS Domain using the IRIS framework and the data model of the IRIS Domain
Registry service. Registry service.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 5 2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 4
3. DCHK Registry . . . . . . . . . . . . . . . . . . . . . . . . 6 3. DCHK Registry . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Schema Description . . . . . . . . . . . . . . . . . . . . 6 3.1 Schema Description . . . . . . . . . . . . . . . . . . . . 5
3.1.1 The <domain> Result . . . . . . . . . . . . . . . . . 6 3.1.1 The <domain> Result . . . . . . . . . . . . . . . . . 5
3.1.2 Support for <iris:lookupEntity> . . . . . . . . . . . 7 3.1.2 Support for <iris:lookupEntity> . . . . . . . . . . . 6
3.2 DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 7 3.2 DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 6
3.3 BEEP Transport Compliance . . . . . . . . . . . . . . . . 11 3.3 BEEP Transport Compliance . . . . . . . . . . . . . . . . 10
3.3.1 Message Pattern . . . . . . . . . . . . . . . . . . . 11 3.3.1 Message Pattern . . . . . . . . . . . . . . . . . . . 10
3.3.2 Server Authentication . . . . . . . . . . . . . . . . 11 3.3.2 Server Authentication . . . . . . . . . . . . . . . . 10
3.4 URI Resolution . . . . . . . . . . . . . . . . . . . . . . 11 3.4 URI Resolution . . . . . . . . . . . . . . . . . . . . . . 10
3.4.1 Application Service Label . . . . . . . . . . . . . . 11 3.4.1 Application Service Label . . . . . . . . . . . . . . 10
3.4.2 Bottom-Up Resolution . . . . . . . . . . . . . . . . . 11 3.4.2 Bottom-Up Resolution . . . . . . . . . . . . . . . . . 10
3.4.3 Top-Down Resolution . . . . . . . . . . . . . . . . . 12 3.4.3 Top-Down Resolution . . . . . . . . . . . . . . . . . 11
4. UDP Transport . . . . . . . . . . . . . . . . . . . . . . . . 13 4. Internationalization Considerations . . . . . . . . . . . . . 12
4.1 Use of IRIS-LWZ . . . . . . . . . . . . . . . . . . . . . 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
4.1.1 IRIS-LWZ Packet Formats . . . . . . . . . . . . . . . 13 5.1 XML Namespace URN Registration . . . . . . . . . . . . . . 13
4.1.2 IRIS-LWZ Transactions . . . . . . . . . . . . . . . . 14 5.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 13
4.2 IRIS-LWZ Operations . . . . . . . . . . . . . . . . . . . 15 5.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 13
4.2.1 Requests . . . . . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
4.2.2 Responses . . . . . . . . . . . . . . . . . . . . . . 16 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Formal XML Syntax . . . . . . . . . . . . . . . . . . . . 18 7.1 Normative References . . . . . . . . . . . . . . . . . . . . 15
4.4 IRIS Transport Mapping Definitions . . . . . . . . . . . . 19 7.2 Informative References . . . . . . . . . . . . . . . . . . . 16
4.4.1 URI Scheme . . . . . . . . . . . . . . . . . . . . . . 19 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
4.4.2 Application Protocol Label . . . . . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . 18
4.5 Registrations . . . . . . . . . . . . . . . . . . . . . . 20
4.5.1 URI Scheme Registration . . . . . . . . . . . . . . . 20
4.5.2 Well-known UDP Port Registration . . . . . . . . . . . 20
4.5.3 NAPSTR Registration . . . . . . . . . . . . . . . . . 20
5. Internationalization Considerations . . . . . . . . . . . . . 22
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
6.1 XML Namespace URN Registration . . . . . . . . . . . . . . 23
6.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 23
6.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 23
7. Security Considerations . . . . . . . . . . . . . . . . . . . 24
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.1 Normative References . . . . . . . . . . . . . . . . . . . . 25
8.2 Informative References . . . . . . . . . . . . . . . . . . . 26
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 27
Intellectual Property and Copyright Statements . . . . . . . . 28
1. Introduction 1. Introduction
There are many ways to check domain name availability for
registration, but none of them are ideal for the general public.
Currently, checks for domain availability are conducted in the
following ways:
1. DNS - Checking the existance of a domain name using DNS is fast.
However, a DNS existance check only reveals if a domain name is
registered and active and does not reveal if a domain name is
registered and inactive. There are many administrative reasons
why a domain name may be inactive. Today, there are over 2
million in registered but inactive domains in .com.
2. EPP - This method of checking can indicate the state where a
domain is registered but not active. However, EPP is a
registrar-to-registry protocol and is not generally available to
the public. EPP environments are often tuned specifically for
registrar-to-registry communications with long-lived connections,
strong encryption and authentication, fixed sets of channels, and
other parameters that do not make it ideal for use by
non-registrars.
3. Nicname/Whois - This protocol was created before the advent of
DNS and consequently does not fulfill many of the needs for a
general domain-name information service much less a domain
availability service. Its defeciencies are well documented and
the basis for the [19] work.
4. DREG - The IRIS Domain Registry is a product of the [19] working
group, and it solves many of the deficiencies in the Nicname/
Whois protocol and is well positioned to serve as a general
domain registration information service for the general public.
This document describes a lightweight service for checking the This document describes a lightweight service for checking the
availability of domain names. This service is based on the IRIS availability of domain names. This service is based on the IRIS
framework and uses the data model defined by DREG. By doing this, framework and uses the data model defined by DREG. By doing this,
the domain availability service has the advantages provided by IRIS the domain availability service has the advantages provided by IRIS
and DREG, such as well-known methods for server navigation, and DREG, such as well-known methods for server navigation,
structured queries and results, and layered extensibility. structured queries and results, and layered extensibility.
The use of IRIS for this service also allows seemless integration The use of IRIS for this service also allows seemless integration
between the domain availability service and the service provided by between the domain availability service and the service provided by
DREG. This allows a user to find the availability status of domain DREG. This allows a user to find the availability status of domain
skipping to change at page 4, line 13 skipping to change at page 3, line 34
(different port) or machine (different host). (different port) or machine (different host).
As an example, an operator may wish to deploy both types of service As an example, an operator may wish to deploy both types of service
on the same set of machines. As time goes on, the operator may then on the same set of machines. As time goes on, the operator may then
decide to segregate the services, placing the domain availability decide to segregate the services, placing the domain availability
service on one set of machines and the DREG service on a separate set service on one set of machines and the DREG service on a separate set
of machines with a stricter set of controls. Either deployment of machines with a stricter set of controls. Either deployment
scenario is transparent to the end user and always appear to be scenario is transparent to the end user and always appear to be
seemlessly complementary. seemlessly complementary.
This domain availability service is lightweight because it defines a When coupled with [20], this domain availability service is
UDP transport. Using S-NAPTR, IRIS has the ability to define the use lightweight and extremely effecient for high-volume, public-facing
of multiple transports for different types of registry services, all service.
at the descretion of the server operator. The UDP transport defined
in this document is completely modular and may be used by other
registry types. An earlier version of it was previously described in
draft-newton-iris-lightweight-01.xml.
2. Document Terminology 2. Document Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [12]. document are to be interpreted as described in RFC2119 [12].
3. DCHK Registry 3. DCHK Registry
The data model used for the domain availability check (DCHK) service The data model used for the domain availability check (DCHK) service
skipping to change at page 11, line 10 skipping to change at page 10, line 10
<attribute <attribute
name="scope" name="scope"
type="string" /> type="string" />
</complexType> </complexType>
</schema> </schema>
Figure 2: dchk.xsd Figure 2: dchk.xsd
3.3 BEEP Transport Compliance 3.3 BEEP Transport Compliance
Though this document defines a UDP transport for use with DCHK, it is Though it is envisioned that a DCHK service will be deployed with a
still possible to use DCHK with the [8] transport. The use of this lightweight transport such as [20], it is still possible to use DCHK
transport is completely at the descretion of the server operator. with the [8] transport. The use of this transport is completely at
the descretion of the server operator.
IRIS allows several extensions of the core capabilities. This IRIS allows several extensions of the core capabilities. This
section outlines those extensions allowable by IRIS-BEEP [8]. section outlines those extensions allowable by IRIS-BEEP [8].
3.3.1 Message Pattern 3.3.1 Message Pattern
This registry type uses the default message pattern as described in This registry type uses the default message pattern as described in
IRIS-BEEP [8]. IRIS-BEEP [8].
3.3.2 Server Authentication 3.3.2 Server Authentication
skipping to change at page 13, line 5 skipping to change at page 12, line 5
connection can be made, then the original label to the left of connection can be made, then the original label to the left of
the rightmost label of the domain name is prepended, and the the rightmost label of the domain name is prepended, and the
second step is repeated again (e.g. if "." then "com", if "com" second step is repeated again (e.g. if "." then "com", if "com"
then "example.com"). then "example.com").
4. If all the labels of the original domain are present and no 4. If all the labels of the original domain are present and no
server connections have been made, then the DNS is queried for server connections have been made, then the DNS is queried for
the address records corresponding to the original domain name and the address records corresponding to the original domain name and
the port used is the well-known port for the default protocol of the port used is the well-known port for the default protocol of
IRIS. IRIS.
4. UDP Transport 4. Internationalization Considerations
To be fast, the domain availability service may use the UDP transport
defined in this section. The binding of this UDP transport to IRIS
is called IRIS-LWZ (for IRIS Lightweight using Compression). This
transport may be used with other registry types defined for IRIS,
such as DREG.
IRIS-LWZ is composed of two parts, a 1 byte payload header and an XML
request/response transaction payload. The XML request/response
transaction payload may be compressed using the DEFLATE algorithm.
4.1 Use of IRIS-LWZ
4.1.1 IRIS-LWZ Packet Formats
The UDP packet format for IRIS-LWZ is as follows:
0 8 16 31
+--------------------+--------------------+
| Src Port | Dst Port |
+--------------------+--------------------+
| Checksum | Length |
+--------------------+--------------------+
| LWZ-HEADER | |
+------------+ |
| Data: XML instance |
| compliant with IRIS-LWZ |
| schema defined above |
+-----------------------------------------+
Each IRIS-LWZ query and response is contained in a single UDP packet.
If no length information is contained in the IRIS-LWZ query, servers
should assume a packet size limitation of 512 bytes.
Each bit in the 1 byte payload header has the following meaning:
bit 7 - version - if 0, the protocol is the version defined in
this document. If 1, the rest of the bits in the header and the
payload may be interpreted as another version.
bit 6 - payload is deflate compressed - if 1, the payload is
compressed using DEFLATE.
bits 5 through 3 - reserved
bit 2 - deflate not supported - if 1, do not respond with a
payload compressed using DEFLATE.
bit 1 - reserved
bit 0 - protocol error - meaning that there was something not
understood in the payload (e.g. a version mis-match, malformed
XML, etc...).
4.1.2 IRIS-LWZ Transactions
4.1.2.1 Client behaviour
To initiate an IRIS-LWZ query, a client sends a UDP datagram to the
identified IRIS-LWZ port on the destination server.
The client then waits for a reply from the server on the same port
from which it sent the query packet. The timeout waiting for a reply
is at the discretion of the client.
As an example, the client may send the following XML to the server:
<request
xmlns="urn:ietf:params:xml:ns:iris-lwz"
serverName="com" length="1280">
<request xmlns="urn:ietf:params:xml:ns:iris1">
<searchSet>
<lookupEntity
registryType="dreg1"
entityClass="contact-handle"
entityName="mak21" />
</searchSet>
</request>
</request>
4.1.2.2 Server behaviour
Upon receipt of an IRIS-LWZ query, the server will apply DEFLATE
decompression to the payload if appropriate, carry out whatever
processing is appropriate, create a valid IRIS-LWZ XML response
instance to the query, and apply DEFLATE to that instance if
necessary and appropriate. If the resulting size is greater than the
maximum size provided in the query (or 512 bytes if no maximum size
was provided), the server will respond with a IRIS-LWZ XML indicating
the response was too large. The response is sent as a UDP datagram
to the source address and port of the original query.
The server's responsibility for addressing a query ends with the
transmission of the UDP response datagram.
4.2 IRIS-LWZ Operations
The XML in the following sections is descriptive of the formal XML
syntax described in Section 4.3.
For each request type, there is one or more response types. The
following shows a brief summary:
o <getProfiles>
* <profiles>
o <request>
* an IRIS response.
* <error> containing <profiles>
* <error> containing <length>
4.2.1 Requests
IRIS-LWZ requests use the formal syntax specified in Section 4.3.
There are two types of IRIS-LWZ requests:
o a profile request
o an IRIS query request
The profile request simply uses the <getProfiles> element.
<getProfiles
xmlns="urn:ietf:params:xml:ns:iris-lwz" />
An IRIS request is wrapped in an <request> element. This element has
an OPTIONAL 'length' attribute containing a positive integer. This
attribute indicates the allowable length of the response in bytes.
It allows clients that have an understanding of their UDP path to
specify how long the response should be. Clients that do not care
about UDP fragmentation may set this number arbitrarily high. If
this attribute is not present, servers MUST assume a length of 512
bytes.
The following is an example of an IRIS request with a query in the
'dchk1' registry-type.
<request
xmlns="urn:ietf:params:xml:ns:iris-lwz"
serverName="com" length="1280">
<request xmlns="urn:ietf:params:xml:ns:iris1">
<searchSet>
<lookupEntity
registryType="dchk1"
entityClass="domain-name"
entityName="example.com" />
</searchSet>
</request>
</request>
4.2.2 Responses
The IRIS-LWZ responses come in two flavors:
o a <profiles> response
o a <response> response
The <profiles> response MUST be returned by the server when a client
issues a <getProfiles> request. The <profiles> element contains
<profile> children. Each <profile> child element contains an IRIS
profile as defined by IRIS-BEEP [8].
The following is an example of a <profiles> response.
<profiles
xmlns="urn:ietf:params:xml:ns:iris-lwz" >
<profile>
http://iana.org/beep/iris1/dchk1
</profile>
</profiles>
The <response> response MUST be sent by the server to the client in
reply to an <request>. It contains one of three types of content:
o an IRIS result response
o an error indicating the IRIS request was for an unsupported
profile.
o an error indicating the IRIS response was too large to send.
An <response> containing an IRIS response simply contains the IRIS
response to the appropriate IRIS request. The following is an
example of 'dchk1' IRIS response.
<response
xmlns="urn:ietf:params:xml:ns:iris-lwz">
<response xmlns="urn:ietf:params:xml:ns:iris1">
<resultSet>
<domain
xmlns="urn:ietf:params:xml:ns:dchk1">
<domainName>example.com</domainName>
<status>
<activeAndOnHold/>
</domain>
</resultSet>
</response>
</response>
When a client makes an IRIS request for a profile that is not
supported by the server, the server MUST return an <response>
indicating that an error has occured. This is done with the <error>
child element. To signal this condition, the <error> element MUST
contain the <profiles> element. Here is an example:
<response
xmlns="urn:ietf:params:xml:ns:iris-lwz" >
<error>
<profiles>
<profile>
http://iana.org/beep/iris1/dchk1
</profile>
</profiles>
</error>
</response>
When a client makes an IRIS request that yields a response too large
to fit in the negotiated UDP packet, the server MUST respond with an
<response> indicating that a size error has occured. This is done
with the <error> child element. To signal this condition, the
<error> element MUST contain a <length> element. The content of the
<length> element is a positive integer stating the size of the IRIS
response.
Upon receiving this error, a client has the following options:
o Requery over IRIS-BEEP.
o Requery over IRIS-LWZ using a larger 'length' indicator.
o Signal an error to the user.
The following is an example of a length error:
<response
xmlns="urn:ietf:params:xml:ns:iris-lwz" >
<error>
<length>2652</length>
</error>
</response>
4.3 Formal XML Syntax
The following is the XML Schema used to define IRIS-LWZ operations.
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:irislwz="urn:ietf:params:xml:ns:iris-lwz"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:iris-lwz"
elementFormDefault="qualified" >
<import namespace="urn:ietf:params:xml:ns:iris1" />
<annotation>
<documentation>
Lightweight (LWZ) Transport for
Internet Registry Information Service (IRIS)
Schema v1
</documentation>
</annotation>
<element name="getProfiles">
<complexType>
</complexType>
</element>
<element name="profiles">
<complexType>
<sequence>
<element name="profile" type="anyURI"/>
</sequence>
</complexType>
</element>
<element name="request">
<complexType>
<sequence>
<element ref="iris:request" />
</sequence>
<attribute name="length" type="positiveInteger" />
<attribute name="serverName" type="string"
use="required" />
</complexType>
</element>
<element name="response">
<complexType>
<choice>
<element name="error">
<complexType>
<choice>
<element ref="irislwz:profiles" />
<element name="length" type="positiveInteger" />
<element name="invalidRequest" type="string" />
<element name="systemError" type="string" />
</choice>
</complexType>
</element>
<element ref="iris:response" />
</choice>
</complexType>
</element>
</schema>
4.4 IRIS Transport Mapping Definitions
This section lists the definitions required by IRIS [5] for transport
mappings.
4.4.1 URI Scheme
The URI scheme name specific to this transport MUST be "iris.lwz".
4.4.2 Application Protocol Label
The application protocol label MUST be "iris.lwz".
4.5 Registrations
4.5.1 URI Scheme Registration
URL scheme name: iris.lwz
URL scheme syntax: defined in Section 4.4.1 and [5].
Character encoding considerations: as defined in RFC2396 [6].
Intended usage: identifies an IRIS entity made available using
compressed XML over UDP
Applications using this scheme: defined in IRIS [5].
Interoperability considerations: n/a
Security Considerations: defined in Section 7.
Relevant Publications: IRIS [5].
Contact Information: Andrew Newton <andy@hxr.us>
Author/Change controller: the IESG
4.5.2 Well-known UDP Port Registration
Protocol Number: UDP
Message Formats, Types, Opcodes, and Sequences: defined in Section
4.1.1 and Section 4.2.
Functions: defined in IRIS [5].
Use of Broadcast/Multicast: none
Proposed Name: IRIS over LWZ
Short name: iris.lwz
Contact Information: Andrew Newton <andy@hxr.us>
4.5.3 NAPSTR Registration
Application Protocol Label: iris.lwz
Intended usage: identifies an IRIS server using compressed XML over
UDP
Interoperability considerations: n/a
Security Considerations: defined in Section 7.
Relevant Publications: IRIS [5].
Contact Information: Andrew Newton <andy@hxr.us>
Author/Change controller: the IESG
5. Internationalization Considerations
Implementers should be aware of considerations for Implementers should be aware of considerations for
internationalization in IRIS [5]. internationalization in IRIS [5].
This document specifies the lookup of domain names, both the This document specifies the lookup of domain names, both the
traditional ASCII form and the IDN form. In addition, the social traditional ASCII form and the IDN form. In addition, the social
data associated with contacts may also be non-ASCII, and could data associated with contacts may also be non-ASCII, and could
contain virtually any Unicode character. The <language> element is contain virtually any Unicode character. The <language> element is
provided in queries that have potential to traverse such data. provided in queries that have potential to traverse such data.
Clients should use these elements to indicate to the server of the Clients should use these elements to indicate to the server of the
target languages desired, and servers should use these elements to target languages desired, and servers should use these elements to
better enable normalization and search processes (see [20]). better enable normalization and search processes (see [21]).
Clients needing to localize the data tags in this protocol should Clients needing to localize the data tags in this protocol should
take note that localization is only needed on the names of XML take note that localization is only needed on the names of XML
elements and attributes with the exception of elements containing elements and attributes with the exception of elements containing
date and time information. The schema for this registry has been date and time information. The schema for this registry has been
designed so that clients need not interpret the content of elements designed so that clients need not interpret the content of elements
or attributes for localization, other than those elements containing or attributes for localization, other than those elements containing
date and time information. date and time information.
Clients should also make use of the <language> elements provided in Clients should also make use of the <language> elements provided in
many of the results. Results containing data that may be in Unicode many of the results. Results containing data that may be in Unicode
are accompanied by these elements in order to aid better presentation are accompanied by these elements in order to aid better presentation
of the data to the user. of the data to the user.
The "dateTimePrivacyType" element type contains the XML Schema [3] The "dateTimePrivacyType" element type contains the XML Schema [3]
data type "dateTime". The contents of this element MUST be specified data type "dateTime". The contents of this element MUST be specified
using the 'Z' indicator for Coordinated Universal Time (UTC). using the 'Z' indicator for Coordinated Universal Time (UTC).
6. IANA Considerations 5. IANA Considerations
6.1 XML Namespace URN Registration 5.1 XML Namespace URN Registration
This document makes use of a proposed XML namespace and schema This document makes use of a proposed XML namespace and schema
registry specified in XML_URN [18]. Accordingly, the following registry specified in XML_URN [18]. Accordingly, the following
registration information is provided for the IANA: registration information is provided for the IANA:
o URN/URI: o URN/URI:
* urn:ietf:params:xml:ns:dchk1 * urn:ietf:params:xml:ns:dchk1
o Contact: o Contact:
* Andrew Newton <andy@hxr.us> * Andrew Newton <andy@hxr.us>
o XML: o XML:
* The XML Schema specified in Section 3.2 * The XML Schema specified in Section 3.2
6.2 S-NAPTR Registration 5.2 S-NAPTR Registration
The following S-NAPTR application service label will need to be The following S-NAPTR application service label will need to be
registered with IANA according to the IANA considerations defined in registered with IANA according to the IANA considerations defined in
IRIS [5]: IRIS [5]:
DCHK1 DCHK1
6.3 BEEP Registration 5.3 BEEP Registration
The following BEEP Profile URI is to be registeried with IANA, in The following BEEP Profile URI is to be registeried with IANA, in
addition to the registration provided in IRIS-BEEP [8]. addition to the registration provided in IRIS-BEEP [8].
http://iana.org/beep/iris1/dchk1 http://iana.org/beep/iris1/dchk1
7. Security Considerations 6. Security Considerations
IRIS-LWZ is intended for serving public data; it provides no in-band IRIS-LWZ is intended for serving public data; it provides no in-band
mechanisms for authentication or encryption. Any application that mechanisms for authentication or encryption. Any application that
needs that must provide out of band mechanisms to provide it (e.g., needs that must provide out of band mechanisms to provide it (e.g.,
IPSec), or use the IRIS protocol with an application transport that IPSec), or use the IRIS protocol with an application transport that
provides such capabilities (e.g. BEEP [7]. provides such capabilities (e.g. BEEP [7].
8. References 7. References
8.1 Normative References 7.1 Normative References
[1] World Wide Web Consortium, "Extensible Markup Language (XML) [1] World Wide Web Consortium, "Extensible Markup Language (XML)
1.0", W3C XML, February 1998, 1.0", W3C XML, February 1998,
<http://www.w3.org/TR/1998/REC-xml-19980210>. <http://www.w3.org/TR/1998/REC-xml-19980210>.
[2] World Wide Web Consortium, "Namespaces in XML", W3C XML [2] World Wide Web Consortium, "Namespaces in XML", W3C XML
Namespaces, January 1999, Namespaces, January 1999,
<http://www.w3.org/TR/1999/REC-xml-names-19990114>. <http://www.w3.org/TR/1999/REC-xml-names-19990114>.
[3] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C [3] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C
skipping to change at page 26, line 25 skipping to change at page 16, line 25
Domain Names in Applications (IDNA)", RFC 3490, March 2003. Domain Names in Applications (IDNA)", RFC 3490, March 2003.
[17] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile [17] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile
for Internationalized Domain Names (IDN)", RFC 3491, March for Internationalized Domain Names (IDN)", RFC 3491, March
2003. 2003.
[18] Mealling, M., "The IETF XML Registry", [18] Mealling, M., "The IETF XML Registry",
draft-mealling-iana-xmlns-registry-03 (work in progress), draft-mealling-iana-xmlns-registry-03 (work in progress),
November 2001. November 2001.
8.2 Informative References 7.2 Informative References
[19] Newton, A., "Cross Registry Internet Service Protocol (CRISP) [19] Newton, A., "Cross Registry Internet Service Protocol (CRISP)
Requirements", RFC 3707, February 2004. Requirements", RFC 3707, February 2004.
[20] Newton, A., "A Lightweight UDP Transport for IRIS",
draft-ietf-crips-iris-lwz-00 (work in progress), Ocotober 2004.
URIs URIs
[20] <http://www.unicode.org/reports/tr15/> [21] <http://www.unicode.org/reports/tr15/>
Author's Address Author's Address
Andrew L. Newton Andrew L. Newton
VeriSign, Inc. VeriSign, Inc.
21345 Ridgetop Circle 21345 Ridgetop Circle
Sterling, VA 20166 Sterling, VA 20166
USA USA
Phone: +1 703 948 3382 Phone: +1 703 948 3382
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/