draft-ietf-crisp-iris-dchk-07.txt   draft-ietf-crisp-iris-dchk-08.txt 
Network Working Group A. Newton Network Working Group A. Newton
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Intended status: Standards Track M. Sanz Intended status: Standards Track M. Sanz
Expires: December 6, 2007 DENIC eG Expires: April 30, 2008 DENIC eG
Jun 4, 2007 Oct 28, 2007
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-07 draft-ietf-crisp-iris-dchk-08
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 36 skipping to change at page 1, line 36
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 December 6, 2007. This Internet-Draft will expire on April 30, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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 Internet Registry Information Service (IRIS) framework and
Registry service. the data model of the IRIS Domain Registry (DREG) 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. Domain Availability Check 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> . . . . . . . . . . . 8 3.1.2. Support for <iris:lookupEntity> . . . . . . . . . . . 8
3.2. DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 8 3.2. DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . 8
3.3. BEEP Transport Compliance . . . . . . . . . . . . . . . . 13 3.3. BEEP Transport Compliance . . . . . . . . . . . . . . . . 13
3.3.1. Message Pattern . . . . . . . . . . . . . . . . . . . 13 3.3.1. Message Pattern . . . . . . . . . . . . . . . . . . . 13
3.3.2. Server Authentication . . . . . . . . . . . . . . . . 13 3.3.2. Server Authentication . . . . . . . . . . . . . . . . 13
3.4. URI Resolution . . . . . . . . . . . . . . . . . . . . . . 13 3.4. URI Resolution . . . . . . . . . . . . . . . . . . . . . . 13
3.4.1. Application Service Label . . . . . . . . . . . . . . 13 3.4.1. Application Service Label . . . . . . . . . . . . . . 13
3.4.2. Bottom-Up Resolution . . . . . . . . . . . . . . . . . 14 3.4.2. Bottom-Up Resolution . . . . . . . . . . . . . . . . . 14
skipping to change at page 3, line 16 skipping to change at page 3, line 16
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 RFC3982 [7]. By doing framework and uses the data model defined by RFC3982 [7]. By doing
this, the domain availability service has the advantages provided by this, the domain availability service has the advantages provided by
IRIS and DREG, such as well-known methods for server navigation, IRIS 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 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 DREG. This allows a user to find the availability status of a domain
and reference the full registration information in DREG. and reference the full registration information in DREG.
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 DREG data model. This enables
implementors to directly reuse DREG code paths and allows operators implementors to directly reuse DREG 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 DREG
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 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
seamlessly complementary. seamlessly complementary.
When coupled with [11], this domain availability service is When coupled with [11], this domain availability service is
lightweight and extremely effecient for high-volume, public-facing lightweight and extremely efficient 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 [2]. document are to be interpreted as described in RFC2119 [2].
3. DCHK Registry 3. Domain Availability Check 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 DREG data model. This section describes
the DCHK registry type. the DCHK registry type.
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
skipping to change at page 5, line 38 skipping to change at page 5, line 38
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><active/></status> <status><active/></status>
</domain> </domain>
&amp;lt;domain&gt; Example &lt;domain&gt; Example
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 [1]. 1035 [1].
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 [3]. See RFC 3491 [3].
skipping to change at page 6, line 14 skipping to change at page 6, line 14
* <active> - available via DNS (either via delegation or direct * <active> - available via DNS (either via delegation or direct
publication) publication)
* <inactive> - unavailable via DNS * <inactive> - unavailable via DNS
* <dispute> - registrant assignment is in dispute * <dispute> - registrant assignment is in dispute
* <renew> - renewal of domain registration * <renew> - renewal of domain registration
* <addPeriod> - period at the creation or activation of this * <addPeriod> - the domain is in the grace period after creation
domain (see RFC 3915 [5]) or activation (see RFC 3915 [5]).
* <renewPeriod> - period at the renewal of this domain (see RFC * <renewPeriod> - the domain is in the grace period after renewal
3915 [5]) (see RFC 3915 [5]).
* <autoRenewPeriod> - period at the automatic renewal of this * <autoRenewPeriod> - the domain is in the grace period after
domain (see RFC 3915 [5]) automatic renewal (see RFC 3915 [5]).
* <transferPeriod> - period at the transfer of this domain (see * <transferPeriod> - the domain is in the grace period after
RFC 3915 [5]) transfer (see RFC 3915 [5]).
* <redemptionPeriod> - period at the redemption of this domain * <redemptionPeriod> - the domain is in the grace period after
(see RFC 3915 [5]) deletion (see RFC 3915 [5]).
* <restore> - change to previous status of this domain * <restore> - change to previous status of this domain
* <policyCompliant> - the domain is considered compliant * <policyCompliant> - the domain is considered compliant
according to a given policy specified by the substatus according to a given policy specified by the substatus
identifier. identifier.
* <policyNoncompliant> - the domain is not considered compliant * <policyNoncompliant> - the domain is not considered compliant
according to a given policy specified by the substatus according to a given policy specified by the substatus
identifier. identifier.
skipping to change at page 7, line 49 skipping to change at page 7, line 49
Each element of type 'domainStatusType' has the following Each element of type 'domainStatusType' has the following
composition: composition:
o <appliedDate> - an optional child element containing the date o <appliedDate> - an optional child element containing the date
applicable to creation of the status. applicable to creation of the status.
o <ticket> - an optional child element containing a service ticket o <ticket> - an optional child element containing a service ticket
identifier relevant to the status. identifier relevant to the status.
o <description> - zero or more child elements with text to describe o <description> - zero or more child elements with text to describe
the status in natural language. Each of these elements must have the status in natural language. Each of these elements MUST have
a 'language' attribute describing the language of the description a 'language' attribute describing the language of the description
element. element.
o <subStatus> - a child element indicating further status o <subStatus> - a child element indicating further status
information. Values for this element are not defined by this information. Values for this element are not defined by this
specification. This child element has a required 'authority' specification. This child element has a required 'authority'
attribute to indicate the origin of the specification of the value attribute to indicate the origin of the specification of the value
of this element. of this element.
o 'actor' - an optional attribute indicating the acting entity for o 'actor' - an optional attribute indicating the acting entity for
skipping to change at page 13, line 25 skipping to change at page 13, line 25
type="token" /> type="token" />
</complexType> </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 [11], it is still possible to use DCHK lightweight transport such as [11], it is still possible to use DCHK
with the [8] transport. The use of this transport is completely at with the BEEP transport [8]. The use of this transport is completely
the discretion of the server operator. at the discretion 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 17, line 9 skipping to change at page 17, line 9
5.3. S-NAPTR Registration 5.3. 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 [6]: IRIS [6]:
DCHK1 DCHK1
5.4. BEEP Registration 5.4. BEEP Registration
The following BEEP Profile URI is to be registeried with IANA, in The following BEEP Profile URI is to be registered 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
6. Security Considerations 6. Security Considerations
Being a proper subset of RFC3982 [7], the registry described in this Being a proper subset of RFC3982 [7], the registry described in this
document has the same security considerations. document introduces no security considerations beyond those
documented in RFC3981 [6].
7. References 7. References
7.1. Normative References 7.1. Normative References
[1] Mockapetris, P., "Domain names - implementation and [1] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 19, line 48 skipping to change at page 19, line 48
[9] World Wide Web Consortium, "XML Schema Part 2: Datatypes", [9] 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/>.
[10] World Wide Web Consortium, "XML Schema Part 1: Structures", [10] 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/>.
7.2. Informative References 7.2. Informative References
[11] Newton, A., "A Lightweight UDP Transport for IRIS", [11] Newton, A., "A Lightweight UDP Transfer Protocol for the
draft-ietf-crips-iris-lwz-08 (work in progress), March 2007. Internet Registry Information Service", RFC 4993, August 2007.
Authors' Addresses Authors' Addresses
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. 20 change blocks. 
29 lines changed or deleted 30 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/