draft-ietf-crisp-iris-dchk-03.txt   draft-ietf-crisp-iris-dchk-04.txt 
Network Working Group A. Newton Network Working Group A. Newton
Internet-Draft VeriSign, Inc. Internet-Draft VeriSign, Inc.
Expires: December 9, 2005 June 7, 2005 Expires: August 11, 2006 February 7, 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-03 draft-ietf-crisp-iris-dchk-04
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 December 9, 2005. This Internet-Draft will expire on August 11, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). 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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
3.3.2 Server Authentication . . . . . . . . . . . . . . . . 11 3.3.2 Server Authentication . . . . . . . . . . . . . . . . 11
3.4 URI Resolution . . . . . . . . . . . . . . . . . . . . . . 11 3.4 URI Resolution . . . . . . . . . . . . . . . . . . . . . . 11
3.4.1 Application Service Label . . . . . . . . . . . . . . 11 3.4.1 Application Service Label . . . . . . . . . . . . . . 11
3.4.2 Bottom-Up Resolution . . . . . . . . . . . . . . . . . 11 3.4.2 Bottom-Up Resolution . . . . . . . . . . . . . . . . . 11
3.4.3 Top-Down Resolution . . . . . . . . . . . . . . . . . 11 3.4.3 Top-Down Resolution . . . . . . . . . . . . . . . . . 11
4. Internationalization Considerations . . . . . . . . . . . . . 12 4. Internationalization Considerations . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5.1 XML Namespace URN Registration . . . . . . . . . . . . . . 13 5.1 XML Namespace URN Registration . . . . . . . . . . . . . . 13
5.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 13 5.2 S-NAPTR Registration . . . . . . . . . . . . . . . . . . . 13
5.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 13 5.3 BEEP Registration . . . . . . . . . . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1 Normative References . . . . . . . . . . . . . . . . . . . 15 7.1 Normative References . . . . . . . . . . . . . . . . . . . 16
7.2 Informative References . . . . . . . . . . . . . . . . . . 15 7.2 Informative References . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . 17 Intellectual Property and Copyright Statements . . . . . . . . 18
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 13, line 13 skipping to change at page 13, line 13
'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 [9]. Accordingly, the following
registration information is provided for the IANA: registration information is provided for the IANA:
o URN/URI: o XML Namespace URN/URI:
* urn:ietf:params:xml:ns:dchk1
o Contact:
* Andrew Newton <andy@hxr.us>
o XML:
* None.
o XML Schema 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
skipping to change at page 15, line 10 skipping to change at page 16, line 10
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", [1] World Wide Web Consortium, "XML Schema Part 2: Datatypes",
W3C XML Schema, October 2000, W3C XML Schema, October 2004,
<http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>. <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 2000, W3C XML Schema, October 2004,
<http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>. <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 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, Internet Registry Information Service (IRIS)", RFC 3892,
January 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)", (IRIS) over Blocks Extensible Exchange Protocol (BEEP)",
skipping to change at page 16, line 14 skipping to change at page 17, 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: 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
skipping to change at page 17, line 41 skipping to change at page 18, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 10 change blocks. 
17 lines changed or deleted 29 lines changed or added

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