draft-ietf-crisp-iris-dchk-04.txt   draft-ietf-crisp-iris-dchk-05.txt 
Network Working Group A. Newton Network Working Group A. Newton
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Expires: August 11, 2006 February 7, 2006 Expires: November 26, 2006 May 25, 2006
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-04 draft-ietf-crisp-iris-dchk-05
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
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 August 11, 2006. This Internet-Draft will expire on November 26, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 . . . . . . . . . . . . . . . . . . . . . 4 2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 4
3. DCHK Registry . . . . . . . . . . . . . . . . . . . . . . . . 5 3. DCHK Registry . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Schema Description . . . . . . . . . . . . . . . . . . . . 5 3.1. Schema Description . . . . . . . . . . . . . . . . . . . . 5
3.1.1 The <domain> Result . . . . . . . . . . . . . . . . . 5 3.1.1. The <domain> Result . . . . . . . . . . . . . . . . . 5
3.1.2 Support for <iris:lookupEntity> . . . . . . . . . . . 7 3.1.2. Support for <iris:lookupEntity> . . . . . . . . . . . 10
3.2 DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 7 3.2. DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 10
3.3 BEEP Transport Compliance . . . . . . . . . . . . . . . . 10 3.3. BEEP Transport Compliance . . . . . . . . . . . . . . . . 17
3.3.1 Message Pattern . . . . . . . . . . . . . . . . . . . 11 3.3.1. Message Pattern . . . . . . . . . . . . . . . . . . . 18
3.3.2 Server Authentication . . . . . . . . . . . . . . . . 11 3.3.2. Server Authentication . . . . . . . . . . . . . . . . 18
3.4 URI Resolution . . . . . . . . . . . . . . . . . . . . . . 11 3.4. URI Resolution . . . . . . . . . . . . . . . . . . . . . . 18
3.4.1 Application Service Label . . . . . . . . . . . . . . 11 3.4.1. Application Service Label . . . . . . . . . . . . . . 18
3.4.2 Bottom-Up Resolution . . . . . . . . . . . . . . . . . 11 3.4.2. Bottom-Up Resolution . . . . . . . . . . . . . . . . . 18
3.4.3 Top-Down Resolution . . . . . . . . . . . . . . . . . 11 3.4.3. Top-Down Resolution . . . . . . . . . . . . . . . . . 18
4. Internationalization Considerations . . . . . . . . . . . . . 12 4. Internationalization Considerations . . . . . . . . . . . . . 19
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
5.1 XML Namespace URN Registration . . . . . . . . . . . . . . 13 5.1. XML Namespace URN Registration . . . . . . . . . . . . . . 20
5.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 13 5.2. S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 20
5.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 13 5.3. BEEP Registration . . . . . . . . . . . . . . . . . . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.1 Normative References . . . . . . . . . . . . . . . . . . . 16 7.1. Normative References . . . . . . . . . . . . . . . . . . . 22
7.2 Informative References . . . . . . . . . . . . . . . . . . 16 7.2. Informative References . . . . . . . . . . . . . . . . . . 22
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 23
Intellectual Property and Copyright Statements . . . . . . . . 18 Intellectual Property and Copyright Statements . . . . . . . . . . 24
1. Introduction 1. Introduction
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 DREG2 [4]. By doing
the domain availability service has the advantages provided by IRIS this, the domain availability service has the advantages provided by
and DREG, such as well-known methods for server navigation, IRIS and DREG2, 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 seamless integration The use of IRIS for this service also allows seamless 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 DREG2. This allows a user to find the availability status of domain
and reference the full registration information in DREG. and reference the full registration information in DREG2.
The data model in this service (called a registry schema in IRIS The data model in this service (called a registry schema in IRIS
terms) is a strict subset of the DREG data model. This enables terms) is a strict subset of the DREG2 data model. This enables
implementors to directly reuse DREG code paths and allows operators implementors to directly reuse DREG2 code paths and allows operators
to deploy the service in either the same server processes as a DREG to deploy the service in either the same server processes as a DREG2
service (same host and port) or in a different server process service (same host and port) or in a different server process
(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 DREG2 service on a separate
of machines with a stricter set of controls. Either deployment set 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
seamlessly complementary. seamlessly complementary.
When coupled with [10], this domain availability service is When coupled with [12], this domain availability service is
lightweight and extremely effecient for high-volume, public-facing lightweight and extremely effecient for high-volume, public-facing
service. service.
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 [7]. document are to be interpreted as described in RFC2119 [8].
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
is a strict subset of the DREG data model. This section describes is a strict subset of the DREG2 data model. This section describes
the DCHK registry type. See [3]. the DCHK registry type. See [3].
3.1 Schema Description 3.1. Schema Description
References to XML elements with no namespace qualifier are from the References to XML elements with no namespace qualifier are from the
schema defined in Section 3.2. References to elements and attributes schema defined in Section 3.2. References to elements and attributes
with the "iris" XML namespace qualifier are from the schema defined with the "iris" XML namespace qualifier are from the schema defined
in IRIS [3]. in IRIS [3].
The descriptions contained within this section refer to XML elements The descriptions contained within this section refer to XML elements
and attributes and their relation to the exchange of data within the and attributes and their relation to the exchange of data within the
protocol. These descriptions also contain specifications outside the protocol. These descriptions also contain specifications outside the
scope of the formal XML syntax. Therefore, this section will use scope of the formal XML syntax. Therefore, this section will use
terms defined by RFC 2119 [7] to describe the specification outside terms defined by RFC 2119 [8] to describe the specification outside
the scope of the formal XML syntax. While reading this section, the scope of the formal XML syntax. While reading this section,
please reference Section 3.2 for needed details on the formal XML please reference Section 3.2 for needed details on the formal XML
syntax. syntax.
3.1.1 The <domain> Result 3.1.1. The <domain> Result
An example of a <domain> result: An example of a <domain> result:
<domain <domain
authority="iana.org" registryType="dchk1" authority="iana.org" registryType="dchk1"
entityClass="domain-name" entityName="example.com"> entityClass="domain-name" entityName="example.com">
<domainName>example.com</domainName> <domainName>example.com</domainName>
<status><activeAndAssigned/></status> <status><activeAndAssigned/></status>
</domain> </domain>
The <domain> result represents an instance of a domain assignment. The <domain> result represents an instance of a domain assignment.
The children of the <domain> element are as follows: The children of the <domain> element are as follows:
o <domainName> - the full name of the domain as it is in DNS. The o <domainName> - the full name of the domain as it is in DNS. The
contents of this element MUST be a domain name as specified by RFC contents of this element MUST be a domain name as specified by RFC
1035 [6]. 1035 [7].
o <idn> - the name of the domain in nameprep form if applicable. o <idn> - the name of the domain in nameprep form if applicable.
See RFC 3491 [8]. See RFC 3491 [9].
o <status> - may contain at least one of the following elements of o <status> - may contain at least one of the following elements of
type 'domainStatusType' (see Section 3.1.1.1), but none of these type 'domainStatusType' (see Section 3.1.1.1), but none of these
elements may appear more than once. elements may appear more than once.
* <reservedDelegation> - permanently inactive * <reservedDelegation> - permanently inactive
* <assignedAndActive> - normal state * <assignedAndActive> - normal state
* <assignedAndInactive> - registration assigned but delegation * <assignedAndInactive> - registration assigned but delegation
skipping to change at page 6, line 22 skipping to change at page 6, line 22
* <assignedAndOnHold> - dispute * <assignedAndOnHold> - dispute
* <revoked> - database purge pending * <revoked> - database purge pending
* <transferPending> - change of authority pending * <transferPending> - change of authority pending
* <registryLock> - on hold by registry * <registryLock> - on hold by registry
* <registrarLock> - on hold by registrar * <registrarLock> - on hold by registrar
o <enhancedStatus> - this element contains child elements
representing enhanced status information. It defines the
following additional status types:
* <active> - available via DNS (either via delegation or direct
publication)
* <inactive> - unavailable via DNS
* <lame> - the domain has been found to be lame (see
Section 3.1.1.3). This element is of "lameEnhancedStatusType".
* <resolvable> - the domain is not lame (see Section 3.1.1.3).
* <dispute> - registrant assignment is in dispute
* <renew> - renewal of domain registration
* <addPeriod> - period at the creation or activation of this
domain (see RFC 3915 [6])
* <renewPeriod> - period at the renewal of this domain (see RFC
3915 [6])
* <autoRenewPeriod> - period at the automatic renewal of this
domain (see RFC 3915 [6])
* <transferPeriod> - period at the transfer of this domain (see
RFC 3915 [6])
* <redemptionPeriod> - period at the redemption of this domain
(see RFC 3915 [6])
* <restore> - change to previous status of this domain
* <policyCompliant> - this domain is considered compliant
according to a given policy specified by the substatus
identifier.
* <policyNoncompliant> - this domain is not considered compliant
according to a given policy specified by the substatus
identifier.
* <reserved> - the containing result object is reserved and is
not available for registration under normal registration
procedures.
* <create> - specifies the creation status of the containing
result object in the registration system.
* <delete> - specifies the deletion status of the containing
result object in the registration system.
* <transfer> - specifies the transfer status of the containing
result object from one responsible or owning entity in the
registration system to another.
* <update> - specifies the status of the containing result object
as it relates to information in the containing result object
being modified or having the ability to be modified.
* <other> - specifies a registration system specific status of
the containing result object.
Both the <status> and <enhancedStatus> elements MAY appear in a
<domain> result object. However, sole use of the <enhancedStatus>
element is RECOMMENDED.
o <domainVariant> - contains an entity reference, the referent of o <domainVariant> - contains an entity reference, the referent of
which MUST be a <domain> (Section 3.1.1). which MUST be a <domain> (Section 3.1.1).
o <registrationReference> - an element containing an entity o <registrationReference> - an element containing an entity
reference, the referent of which MUST be either a <domain> reference, the referent of which MUST be either a <domain>
(Section 3.1.1) or a <domain> as defined by DREG [4]. The intent (Section 3.1.1) or a <domain> as defined by DREG2 [4]. The intent
of this element is to point to the downstream registration of this element is to point to the downstream registration
reference. Therefore, if this is a result given back by a domain reference. Therefore, if this is a result given back by a domain
registry, it should point to the domain in the domain registrar or registry, it should point to the domain in the domain registrar or
registrant service. registrant service.
o <initialDelegationDateTime> - an element containing the date and o <initialDelegationDateTime> - an element containing the date and
time of the initial delegation of this domain. time of the initial delegation of this domain.
o <lastDelegationModificationDateTime> - an element containing the o <lastDelegationModificationDateTime> - an element containing the
date and time of the last time one of the nameservers was added or date and time of the last time one of the nameservers was added or
removed for the delegation of this domain. removed for the delegation of this domain.
o <iris:seeAlso> - an element containing an entity reference o <iris:seeAlso> - an element containing an entity reference
specifying a referent that is indirectly associated with this specifying a referent that is indirectly associated with this
domain. domain.
3.1.1.1 Domain Status Type 3.1.1.1. Domain Status Type
Each element that is of the 'domainStatusType' may have an optional Each element that is of the 'domainStatusType' may have an optional
<appliedDate> element and one or more <description> elements, the <appliedDate> element and one or more <description> elements, the
text contents of which may be used to describe the status in natural text contents of which may be used to describe the status in natural
language. Each <description> element must have a 'language' language. Each <description> element must have a 'language'
attribute describing the language of the description element. attribute describing the language of the description element.
3.1.2 Support for <iris:lookupEntity> 3.1.1.2. Enhanced Domain Status Type
Each element that is of the 'enhancedStatusType' has the following
composition:
o <appliedDate> - a child element containing the date applicable to
creation of the status.
o <description> - one or more child elements with text to described
the status in natural language. Each of these elements must have
a 'language' attribute describing the language of the description
element.
o <ticket> - a child element containing a service ticket identifier
relevant to the status.
o <subStatus> - a child element indicating further status
information. Values for this element are not defined by the
specification. This child element has a required 'authority'
attribute to indicate the origin of the specification of the value
of this element.
o 'actor' - an optional attribute indicating the acting entity for
which this status is applied. The values may be "registry",
"registrar", or "registrationServiceProvider".
o 'disposition' - an optional attribute indicating the nature of
this status. The values may be "pending" or "prohibited".
o 'scope' - an optional attribute indicating the context or origin
of the status value.
3.1.1.3. Lameness
Some registries, registrars, or registration service providers may
periodically check to see if a domain is "lame". In DNS terms,
"lame" has a narrow definition as defined in [11], but the term is
often used in a wider context. The explanation given here covers the
wider context as is often found in registration systems and is not
meant to redefine the stricter meaning in DNS as specified in [11].
A nameserver listed as authoritative for a domain can be considered
lame for three reasons:
1. The nameserver is unresponsive.
2. The nameserver does not answer authoritatively for the domain.
See [11].
3. The address of the nameserver cannot be resolved, usually due to
the domain in which it exists being lame itself.
In a registration database, lameness may exist in three places:
1. A nameserver is lame if its address cannot be resolved or it does
not answer queries.
2. The relationship between a domain and a nameserver could be lame
if the nameserver does not authoritatively answer queries for the
domain (i.e. it could answer authoritatively for other domains).
3. A domain is lame if all of its nameservers are lame.
This specification enumerates the reasons for lameness with
"lameReasonType". The enumerated values are:
o queryTimeout - an answer was not received within a specified
duration of time.
o nonAuthoritativeAnswer - the name server queried did not return an
authoritative answer.
o unknownDomainName - the name server queried unknown the domain
name.
o unknownHostName - the name server's name is unknown.
o queryRefused - the name server refused to answer the query.
o connectionRefused - the name server refused to accept the query
connection.
o cannonicalName - the name server's name in a CNAME and not an A
record.
o soaVersionNotInSync - the SOA version is not in sync between this
server and the delegated master.
o dnsProtocolLevelError - the query resulted in a DNS protocol error
o other - lame for an unexplaned reason
A special status type also exists to describe lameness, the
"lameEnhancedStatusType". This type extends the "enhancedStatusType"
by adding an <lame> element of the "lameReasonType".
3.1.2. Support for <iris:lookupEntity>
The following types of entity classes are recognized by the The following types of entity classes are recognized by the
<lookupEntity> query of IRIS for this registry: <lookupEntity> query of IRIS for this registry:
o domain-name - the fully qualified name of a domain. This a domain o domain-name - the fully qualified name of a domain. This a domain
name as specified by RFC 1035 [6]. Yields a <domain> name as specified by RFC 1035 [7]. Yields a <domain>
(Section 3.1.1) in the response. (Section 3.1.1) in the response.
o idn - the fully qualified name of a domain in nameprep form (see o idn - the fully qualified name of a domain in nameprep form (see
RFC 3491 [8]). Yields a <domain> (Section 3.1.1) in the response. RFC 3491 [9]). Yields a <domain> (Section 3.1.1) in the response.
3.2 DCHK Formal XML Syntax 3.2. DCHK Formal XML Syntax
This registry schema is specified in the XML Schema notation (see [1] This registry schema is specified in the XML Schema notation (see [1]
and [2]). The formal syntax presented here is a complete schema and [2]). The formal syntax presented here is a complete schema
representation suitable for automated validation of an XML instance representation suitable for automated validation of an XML instance
when combined with the formal schema syntax of IRIS. when combined with the formal schema syntax of IRIS.
<?xml version="1.0"?> <?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" <schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:dchk="urn:ietf:params:xml:ns:dchk1" xmlns:dchk="urn:ietf:params:xml:ns:dchk1"
xmlns:iris="urn:ietf:params:xml:ns:iris1" xmlns:iris="urn:ietf:params:xml:ns:iris1"
skipping to change at page 9, line 23 skipping to change at page 12, line 41
maxOccurs="1" maxOccurs="1"
type="dchk:domainStatusType" /> type="dchk:domainStatusType" />
<element <element
name="other" name="other"
minOccurs="0" minOccurs="0"
maxOccurs="1" maxOccurs="1"
type="dchk:domainStatusType" /> type="dchk:domainStatusType" />
</all> </all>
</complexType> </complexType>
</element> </element>
<element name="enhancedStatus"
minOccurs="0"
maxOccurs="1">
<complexType>
<choice minOccurs="0" maxOccurs="unbounded">
<element
name="active"
type="dchk:enhancedStatusType" />
<element
name="inactive"
type="dchk:enhancedStatusType" />
<element
name="lame"
type="dchk:lameEnhancedStatusType" />
<element
name="resolvable"
type="dchk:enhancedStatusType" />
<element
name="dispute"
type="dchk:enhancedStatusType" />
<element
name="renew"
type="dchk:enhancedStatusType" />
<element
name="addPeriod"
type="dchk:enhancedStatusType" />
<element
name="renewPeriod"
type="dchk:enhancedStatusType" />
<element
name="autoRenewPeriod"
type="dchk:enhancedStatusType" />
<element
name="transferPeriod"
type="dchk:enhancedStatusType" />
<element
name="redemptionPeriod"
type="dchk:enhancedStatusType" />
<element
name="restore"
type="dchk:enhancedStatusType" />
<element
name="policyCompliant"
type="dchk:enhancedStatusType" />
<element
name="policyNoncompliant"
type="dchk:enhancedStatusType" />
<element
name="reserved"
type="dchk:enhancedStatusType"/>
<element
name="create"
type="dchk:enhancedStatusType"/>
<element
name="delete"
type="dchk:enhancedStatusType"/>
<element
name="transfer"
type="dchk:enhancedStatusType"/>
<element
name="update"
type="dchk:enhancedStatusType"/>
<element
name="other"
type="dchk:enhancedStatusType"/>
</choice>
</complexType>
</element>
<element <element
name="domainVariant" name="domainVariant"
type="iris:entityType" type="iris:entityType"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
<element <element
name="registrationReference" name="registrationReference"
type="iris:entityType" type="iris:entityType"
minOccurs="0" minOccurs="0"
maxOccurs="1" /> maxOccurs="1" />
skipping to change at page 10, line 39 skipping to change at page 15, line 29
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
</element> </element>
</sequence> </sequence>
<attribute <attribute
name="scope" name="scope"
type="string" /> type="string" />
</complexType> </complexType>
<complexType
name="enhancedStatusType">
<sequence>
<element
name="appliedDate"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="ticket"
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
<element
name="subStatus"
minOccurs="0"
maxOccurs="1">
<complexType>
<simpleContent>
<extension
base="token">
<attribute
type="token"
use="required"
name="authority"/>
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attribute
name="actor">
<simpleType>
<restriction
base="string">
<enumeration
value="registry"/>
<enumeration
value="registrar"/>
<enumeration
value="registrationServiceProvider"/>
</restriction>
</simpleType>
</attribute>
<attribute
name="disposition">
<simpleType>
<restriction
base="string">
<enumeration
value="prohibited"/>
<enumeration
value="pending"/>
</restriction>
</simpleType>
</attribute>
<attribute
name="scope"
type="token" />
</complexType>
<simpleType name="lameReasonType">
<restriction base="string">
<enumeration value="queryTimeout"/>
<enumeration value="nonAuthoritativeAnswer"/>
<enumeration value="unknownDomainName"/>
<enumeration value="unknownHostName"/>
<enumeration value="queryRefused"/>
<enumeration value="connectionRefused"/>
<enumeration value="canonicalName"/>
<enumeration value="soaVersionNotInSync"/>
<enumeration value="dnsProtocolLevelError"/>
<enumeration value="other"/>
</restriction>
</simpleType>
<complexType name="lameEnhancedStatusType">
<complexContent>
<extension base="dchk:enhancedStatusType">
<sequence>
<element name="lameReason"
type="dchk:lameReasonType" />
</sequence>
</extension>
</complexContent>
</complexType>
</schema> </schema>
Figure 2: dchk.xsd Figure 2: dchk.xsd
3.3 BEEP Transport Compliance 3.3. BEEP Transport Compliance
Though it is envisioned that a DCHK service will be deployed with a Though it is envisioned that a DCHK service will be deployed with a
lightweight transport such as [10], it is still possible to use DCHK lightweight transport such as [12], it is still possible to use DCHK
with the [5] transport. The use of this transport is completely at with the [5] transport. The use of this transport is completely at
the descretion of the server operator. 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 [5]. section outlines those extensions allowable by IRIS-BEEP [5].
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 [5]. IRIS-BEEP [5].
3.3.2 Server Authentication 3.3.2. Server Authentication
This registry type uses the default server authentication method as This registry type uses the default server authentication method as
described in IRIS-BEEP [5]. described in IRIS-BEEP [5].
3.4 URI Resolution 3.4. URI Resolution
3.4.1 Application Service Label 3.4.1. Application Service Label
The application service label associated with this registry type MUST The application service label associated with this registry type MUST
be "DCHK1". This is the abbreviated form of the URN for this be "DCHK1". This is the abbreviated form of the URN for this
registry type, urn:ietf:params:xml:ns:dchk1. registry type, urn:ietf:params:xml:ns:dchk1.
3.4.2 Bottom-Up Resolution 3.4.2. Bottom-Up Resolution
The bottom-up alternative resolution method MUST be identified as The bottom-up alternative resolution method MUST be identified as
'bottom' in IRIS URI's. Its process is identical to the 'bottom' 'bottom' in IRIS URI's. Its process is identical to the 'bottom'
process described by DREG [4]. process described by DREG2 [4].
3.4.3 Top-Down Resolution 3.4.3. Top-Down Resolution
The top-down alternative resolution method MUST be identified as The top-down alternative resolution method MUST be identified as
'top' in IRIS URI's. Its process is identical to the 'top' process 'top' in IRIS URI's. Its process is identical to the 'top' process
described by DREG [4]. described by DREG2 [4].
4. Internationalization Considerations 4. Internationalization Considerations
Implementers should be aware of considerations for Implementers should be aware of considerations for
internationalization in IRIS [3]. internationalization in IRIS [3].
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
skipping to change at page 13, line 7 skipping to change at page 20, line 7
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 "appliedDate" element contains the XML Schema [1] data type The "appliedDate" element contains the XML Schema [1] data type
"dateTime". The contents of this element MUST be specified using the "dateTime". The contents of this element MUST be specified using the
'Z' indicator for Coordinated Universal Time (UTC). 'Z' indicator for Coordinated Universal Time (UTC).
5. IANA Considerations 5. IANA Considerations
5.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 [9]. Accordingly, the following registry specified in XML_URN [10]. Accordingly, the following
registration information is provided for the IANA: registration information is provided for the IANA:
o XML Namespace URN/URI: o XML Namespace 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>
skipping to change at page 13, line 37 skipping to change at page 20, line 37
* 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
5.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 [3]: IRIS [3]:
DCHK1 DCHK1
5.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 [5]. addition to the registration provided in IRIS-BEEP [5].
http://iana.org/beep/iris1/dchk1 http://iana.org/beep/iris1/dchk1
6. Security Considerations 6. Security Considerations
Being a proper subset of DREG [4], the registry described in this Being a proper subset of DREG2 [4], the registry described in this
document has the same security considerations. document has the same security considerations.
7. References 7. References
7.1 Normative References 7.1. Normative References
[1] World Wide Web Consortium, "XML Schema Part 2: Datatypes", [1] World Wide Web Consortium, "XML Schema Part 2: Datatypes",
W3C XML Schema, October 2004, W3C XML Schema, October 2004,
<http://www.w3.org/TR/xmlschema-2/>. <http://www.w3.org/TR/xmlschema-2/>.
[2] World Wide Web Consortium, "XML Schema Part 1: Structures", [2] World Wide Web Consortium, "XML Schema Part 1: Structures",
W3C XML Schema, October 2004, W3C XML Schema, October 2004,
<http://www.w3.org/TR/xmlschema-1/>. <http://www.w3.org/TR/xmlschema-1/>.
[3] Newton, A. and M. Sanz, "Internet Registry Information Service", [3] Newton, A. and M. Sanz, "Internet Registry Information
RFC 3891, January 2005. Service", RFC 3981, January 2005.
[4] Newton, A. and M. Sanz, "A Domain Registry (dreg) Type for the [4] Newton, A. and F. Neves, "Domain Registry Version 2 for the
Internet Registry Information Service (IRIS)", RFC 3892, Internet Registry Information Service",
January 2005. draft-ietf-crisp-iris-dreg2-01 (work in progress), May 2006.
[5] Newton, A. and M. Sanz, "Internet Registry Information Service [5] Newton, A. and M. Sanz, "Internet Registry Information Service
(IRIS) over Blocks Extensible Exchange Protocol (BEEP)", (IRIS) over Blocks Extensible Exchange Protocol (BEEP)",
RFC 3893, January 2005. RFC 3983, January 2005.
[6] Mockapetris, P., "Domain names - implementation and [6] Hollenbeck, S., "Domain Registry Grace Period Mapping for the
Extensible Provisioning Protocol (EPP)", RFC 3915,
September 2004.
[7] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[7] Bradner, S., "Key words for use in RFCs to Indicate Requirement [8] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, BCP 14, March 1997. Levels", RFC 2119, BCP 14, March 1997.
[8] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile for [9] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile
Internationalized Domain Names (IDN)", RFC 3491, March 2003. for Internationalized Domain Names (IDN)", RFC 3491,
March 2003.
[9] Mealling, M., "The IETF XML Registry", [10] 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.
7.2 Informative References [11] Austein, R. and J. Saperia, "DNS Resolver MIB Extensions",
RFC 1612, May 1994.
[10] Newton, A., "A Lightweight UDP Transport for IRIS", 7.2. Informative References
draft-ietf-crips-iris-lwz-01 (work in progress), January 2005.
[12] Newton, A., "A Lightweight UDP Transport for IRIS",
draft-ietf-crips-iris-lwz-06 (work in progress), January 2005.
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. 50 change blocks. 
79 lines changed or deleted 420 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/