A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)

The data model used for the domain availability check (DCHK) service is a strict subset of the DREG data model. This section describes the DCHK registry type.

References to XML elements with no namespace qualifier are from the schema defined in . References to elements and attributes with the "iris" XML namespace qualifier are from the schema defined in IRIS. The schema present in this document is tied to the protocol version associated with the XML namespace URI defined in . Extensions to the present DCHK schema are allowed, though not recommended, but would require a new version. Please refer to RFC 3981 for more details about versioning the IRIS protocol. The descriptions contained within this section refer to XML elements and attributes and their relation to the exchange of data within the protocol. These descriptions also contain specifications outside the scope of the formal XML syntax. Therefore, this section will use terms defined by RFC 2119 to describe the specification outside the scope of the formal XML syntax. While reading this section, please reference for needed details on the formal XML syntax.

An example of a <domain> result:

<domain authority="iana.org" registryType="dchk1" entityClass="domain-name" entityName="example.com"> <domainName>example.com</domainName> <status><active/></status> </domain> The <domain> result represents an instance of a domain assignment. The children of the <domain> element are as follows: <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 1035. <idn> - the name of the domain in nameprep form, if applicable. See RFC 3491. <status> - this element contains child elements representing domain status information. It defines the following status types: <active> - available via DNS (either via delegation or direct publication). <inactive> - unavailable via DNS.s <dispute> - registrant assignment is in dispute. <renew> - renewal of domain registration. <addPeriod> - the domain is in the grace period after creation or activation (see RFC 3915). <renewPeriod> - the domain is in the grace period after renewal (see RFC 3915). <autoRenewPeriod> - the domain is in the grace period after automatic renewal (see RFC 3915). <transferPeriod> - the domain is in the grace period after transfer (see RFC 3915). <redemptionPeriod> - the domain is in the grace period after deletion (see RFC 3915). <restore> - change to previous status of this domain. <policyCompliant> - the domain is considered compliant according to a given policy specified by the substatus identifier. <policyNoncompliant> - the domain is not considered compliant according to a given policy specified by the substatus identifier. <reserved> - the domain is reserved and is not available for registration under normal registration procedures. <create> - specifies the creation status of the domain in the registration system. <delete> - specifies the deletion status of the domain in the registration system. <transfer> - specifies the transfer status of the domain from one responsible or owning entity in the registration system to another. <update> - specifies the status of the domain as it relates to information in the domain being modified or having the ability to be modified. <other> - specifies a registration system specific status of the domain. <registrationReference> - an element containing an entity reference, the referent of which MUST be either a <domain> or a <domain> as defined by RFC 3982. The intent 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. <createdDateTime> - an element containing the date and time of the creation of this domain. <initialDelegationDateTime> - an element containing the date and time of the initial delegation of this domain. <expirationDateTime> - an element containing the date and time of the expiration of this domain. <lastDatabaseUpdateDateTime> - an element containing the date and time of the last actualization of the database that is source for this result. <iris:seeAlso> - an element containing an entity reference specifying a referent that is indirectly associated with this domain.

Each element of type 'domainStatusType' has the following composition: <appliedDate> - an optional child element containing the date applicable to creation of the status. <ticket> - an optional child element containing a service ticket identifier relevant to the status. <description> - zero or more child elements with text to describe the status in natural language. Each of these elements MUST have a 'language' attribute describing the language of the description element. <subStatus> - a child element indicating further status information. Values for this element are not defined by this specification. This child element has a required 'authority' attribute to indicate the origin of the specification of the value of this element. 'actor' - an optional attribute indicating the acting entity for which this status is applied. The values may be "registry", "registrar", or "registrationServiceProvider". 'disposition' - an optional attribute indicating the nature of this status. The values may be "pending" or "prohibited". 'scope' - an optional attribute indicating the context or origin of the status value.

The following types of entity classes are recognized by the <lookupEntity> query of IRIS for this registry: domain-name - the fully qualified name of a domain. This is a domain name as specified by RFC 1035. Yields a <domain> in the response. idn - the fully qualified name of a domain in nameprep form (see RFC 3491). Yields a <domain> in the response.

This registry schema is specified in the XML Schema notation (see and ). The formal syntax presented here is a complete schema representation suitable for automated validation of an XML instance when combined with the formal schema syntax of IRIS.

<?xml version="1.0"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:dchk="urn:ietf:params:xml:ns:dchk1" xmlns:iris="urn:ietf:params:xml:ns:iris1" targetNamespace="urn:ietf:params:xml:ns:dchk1" elementFormDefault="qualified" > <import namespace="urn:ietf:params:xml:ns:iris1" /> <annotation> <documentation> Domain availability check schema derived from IRIS schema </documentation> </annotation>         <complexType name="domainType"> <complexContent> <extension base="iris:resultType"> <sequence> <element name="domainName" type="token" /> <element name="idn" type="token" minOccurs="0" maxOccurs="1" /> <element name="status" minOccurs="0" maxOccurs="1"> <complexType> <choice minOccurs="0" maxOccurs="unbounded"> <element name="active" type="dchk:domainStatusType" /> <element name="inactive" type="dchk:domainStatusType" /> <element name="dispute" type="dchk:domainStatusType" /> <element name="renew" type="dchk:domainStatusType" /> <element name="addPeriod" type="dchk:domainStatusType" /> <element name="renewPeriod" type="dchk:domainStatusType" /> <element name="autoRenewPeriod" type="dchk:domainStatusType" /> <element name="transferPeriod" type="dchk:domainStatusType" /> <element name="redemptionPeriod" type="dchk:domainStatusType" /> <element name="restore" type="dchk:domainStatusType" /> <element name="policyCompliant" type="dchk:domainStatusType" /> <element name="policyNoncompliant" type="dchk:domainStatusType" /> <element name="reserved" type="dchk:domainStatusType" /> <element name="create" type="dchk:domainStatusType" /> <element name="delete" type="dchk:domainStatusType" /> <element name="transfer" type="dchk:domainStatusType" /> <element name="update" type="dchk:domainStatusType" /> <element name="other" type="dchk:domainStatusType" /> </choice> </complexType> </element> <element name="registrationReference" type="iris:entityType" minOccurs="0" maxOccurs="1" /> <element name="createdDateTime" type="dateTime" minOccurs="0" maxOccurs="1" /> <element name="initialDelegationDateTime" type="dateTime" minOccurs="0" maxOccurs="1" /> <element name="expirationDateTime" type="dateTime" minOccurs="0" maxOccurs="1" /> <element name="lastDatabaseUpdateDateTime" type="dateTime" minOccurs="0" maxOccurs="1" /> <element ref="iris:seeAlso" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <element name="domain" type="dchk:domainType" substitutionGroup="iris:result" /> <complexType name="domainStatusType"> <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> </schema>

All DCHK clients and servers MUST implement the Lightweight UDP Transport Protocol (IRIS-LWZ) . The use of other transports like the XML Pipelining with Chunks (IRIS-XPC) transport or the BEEP transport is optional and completely at the discretion of the server operator. The XPC transport is in any case preferable to the BEEP transport. IRIS allows several extensions of the core capabilities. This section outlines those extensions allowable by IRIS-BEEP.

This registry type uses the default message pattern as described in IRIS-BEEP.

This registry type uses the default server authentication method as described in IRIS-BEEP.

The application service label associated with this registry type MUST be "DCHK1". This is the abbreviated form of the URN for this registry type, urn:ietf:params:xml:ns:dchk1.

The bottom-up alternative resolution method MUST be identified as 'bottom' in IRIS URI's. Its process is identical to the 'bottom' process described by RFC 3982.

The top-down alternative resolution method MUST be identified as 'top' in IRIS URI's. Its process is identical to the 'top' process described by RFC 3982.