draft-ietf-crisp-iris-dchk-02.txt   draft-ietf-crisp-iris-dchk-03.txt 
Network Working Group A. Newton Network Working Group A. Newton
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Expires: July 26, 2005 January 25, 2005 Expires: December 9, 2005 June 7, 2005
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-02 draft-ietf-crisp-iris-dchk-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
and any of which I become aware will be disclosed, in accordance with have been or will be disclosed, and any of which he or she becomes
RFC 3668. 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
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 July 26, 2005. This Internet-Draft will expire on December 9, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005).
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> . . . . . . . . . . . 6 3.1.2 Support for <iris:lookupEntity> . . . . . . . . . . . 7
3.2 DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 6 3.2 DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 7
3.3 BEEP Transport Compliance . . . . . . . . . . . . . . . . 10 3.3 BEEP Transport Compliance . . . . . . . . . . . . . . . . 10
3.3.1 Message Pattern . . . . . . . . . . . . . . . . . . . 10 3.3.1 Message Pattern . . . . . . . . . . . . . . . . . . . 11
3.3.2 Server Authentication . . . . . . . . . . . . . . . . 10 3.3.2 Server Authentication . . . . . . . . . . . . . . . . 11
3.4 URI Resolution . . . . . . . . . . . . . . . . . . . . . . 10 3.4 URI Resolution . . . . . . . . . . . . . . . . . . . . . . 11
3.4.1 Application Service Label . . . . . . . . . . . . . . 10 3.4.1 Application Service Label . . . . . . . . . . . . . . 11
3.4.2 Bottom-Up Resolution . . . . . . . . . . . . . . . . . 10 3.4.2 Bottom-Up Resolution . . . . . . . . . . . . . . . . . 11
3.4.3 Top-Down Resolution . . . . . . . . . . . . . . . . . 10 3.4.3 Top-Down Resolution . . . . . . . . . . . . . . . . . 11
4. Internationalization Considerations . . . . . . . . . . . . . 11 4. Internationalization Considerations . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5.1 XML Namespace URN Registration . . . . . . . . . . . . . . 12 5.1 XML Namespace URN Registration . . . . . . . . . . . . . . 13
5.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 12 5.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 13
5.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 12 5.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1 Normative References . . . . . . . . . . . . . . . . . . . . 14 7.1 Normative References . . . . . . . . . . . . . . . . . . . 15
7.2 Informative References . . . . . . . . . . . . . . . . . . . 14 7.2 Informative References . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 15 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . 16 Intellectual Property and Copyright Statements . . . . . . . . 17
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 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.
skipping to change at page 5, line 40 skipping to change at page 5, line 40
<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 [6].
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 [8].
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
inactive inactive
* <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 <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 a <domain> (Section reference, the referent of which MUST be either a <domain>
3.1.1). The intent of this reference is to point to the instance (Section 3.1.1) or a <domain> as defined by DREG [4]. The intent
of this domain in the registry's DREG [4] registry. of this element is to point to the downstream registration
reference. Therefore, if this is a result given back by a domain
registry, it should point to the domain in the domain registrar or
registrant service.
o <initialDelegationDateTime> - an element containing the date and
time of the initial delegation of this domain.
o <lastDelegationModificationDateTime> - an element containing the
date and time of the last time one of the nameservers was added or
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'
skipping to change at page 6, line 31 skipping to change at page 7, line 9
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.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> (Section name as specified by RFC 1035 [6]. Yields a <domain>
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 [8]). 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.
skipping to change at page 9, line 6 skipping to change at page 9, line 34
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" />
<element <element
name="initialDelegationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDelegationModificationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
ref="iris:seeAlso" ref="iris:seeAlso"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<element <element
name="domain" name="domain"
type="dchk:domainType" type="dchk:domainType"
substitutionGroup="iris:result" /> substitutionGroup="iris:result" />
<complexType <complexType
name="domainStatusType"> name="domainStatusType">
<sequence> <sequence>
<element <element
name="appliedDate" name="appliedDate"
skipping to change at page 14, line 9 skipping to change at page 15, line 9
6. Security Considerations 6. Security Considerations
Being a proper subset of DREG [4], the registry described in this Being a proper subset of DREG [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", W3C [1] World Wide Web Consortium, "XML Schema Part 2: Datatypes",
XML Schema, October 2000, W3C XML Schema, October 2000,
<http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>. <http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>.
[2] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C [2] World Wide Web Consortium, "XML Schema Part 1: Structures",
XML Schema, October 2000, W3C XML Schema, October 2000,
<http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>. <http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>.
[3] Newton, A. and M. Sanz, "Internet Registry Information Service", [3] Newton, A. and M. Sanz, "Internet Registry Information Service",
RFC 3891, January 2005. RFC 3891, January 2005.
[4] Newton, A. and M. Sanz, "A Domain Registry (dreg) Type for the [4] Newton, A. and M. Sanz, "A Domain Registry (dreg) Type for the
Internet Registry Information Service (IRIS)", RFC 3892, January Internet Registry Information Service (IRIS)", RFC 3892,
2005. January 2005.
[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)", RFC (IRIS) over Blocks Extensible Exchange Protocol (BEEP)",
3893, January 2005. RFC 3893, January 2005.
[6] Mockapetris, P., "Domain names - implementation and [6] 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 [7] 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 [8] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile for
Internationalized Domain Names (IDN)", RFC 3491, March 2003. Internationalized Domain Names (IDN)", RFC 3491, March 2003.
skipping to change at page 15, line 14 skipping to change at page 16, line 14
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
EMail: anewton@verisignlabs.com; andy@hxr.us Email: anewton@verisignlabs.com; andy@hxr.us
URI: http://www.verisignlabs.com/ URI: http://www.verisignlabs.com/
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 

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