draft-ietf-crisp-iris-common-transport-03.txt   draft-ietf-crisp-iris-common-transport-04.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: July 13, 2007 January 9, 2007
A Common Schema for Internet Registry Information Service Transfer A Common Schema for Internet Registry Information Service Transfer
Protocols Protocols
draft-ietf-crisp-iris-common-transport-03 draft-ietf-crisp-iris-common-transport-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 August 11, 2006. This Internet-Draft will expire on July 13, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2007).
Abstract Abstract
This document describes an XML Schema for use by Internet Registry This document describes an XML Schema for use by Internet Registry
Information Service (IRIS) application transfer protocols that share Information Service (IRIS) application transfer protocols that share
common characteristics. It describes common information about the common characteristics. It describes common information about the
transfer protocol, such as version, supported extensions, and transfer protocol, such as version, supported extensions, and
supported security mechanisms. supported security mechanisms.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Terminology . . . . . . . . . . . . . . . . . . . . 4 2. Document Terminology . . . . . . . . . . . . . . . . . . . . . 4
3. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . 5 3. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . . 5
4. Version Information . . . . . . . . . . . . . . . . . . . . 8 4. Version Information . . . . . . . . . . . . . . . . . . . . . 8
5. Size Information . . . . . . . . . . . . . . . . . . . . . . 9 5. Size Information . . . . . . . . . . . . . . . . . . . . . . . 9
6. Authentication Success Information . . . . . . . . . . . . . 10 6. Authentication Success Information . . . . . . . . . . . . . . 10
7. Authentication Failure Information . . . . . . . . . . . . . 11 7. Authentication Failure Information . . . . . . . . . . . . . . 11
8. Other Information . . . . . . . . . . . . . . . . . . . . . 12 8. Other Information . . . . . . . . . . . . . . . . . . . . . . 12
9. Internationalization Considerations . . . . . . . . . . . . 13 9. Internationalization Considerations . . . . . . . . . . . . . 13
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . 14 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
10.1 XML Namespace URN Registration . . . . . . . . . . . . . 14 10.1. XML Namespace URN Registration . . . . . . . . . . . . . 14
11. Security Considerations . . . . . . . . . . . . . . . . . . 15 11. Security Considerations . . . . . . . . . . . . . . . . . . . 15
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
12.1 Normative References . . . . . . . . . . . . . . . . . . 16 12.1. Normative References . . . . . . . . . . . . . . . . . . 16
12.2 Informative References . . . . . . . . . . . . . . . . . 16 12.2. Informative References . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . 17 Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 17
A. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18
Intellectual Property and Copyright Statements . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Introduction 1. Introduction
IRIS [8] has two transfer protocols, LWZ [9] and XPC [10], that share IRIS [8] has two transfer protocols, LWZ [9] and XPC [10], that share
common negotiation mechanisms. Both transfer protocols have a need common negotiation mechanisms. Both transfer protocols have a need
for the server to provide rich status information to clients during for the server to provide rich status information to clients during
protocol negotiation. In many cases, this status information would protocol negotiation. In many cases, this status information would
be too complex to describe using simple bit fields and length- be too complex to describe using simple bit fields and length-
specifed octet sequences. This document defines an XML Schema for specifed octet sequences. This document defines an XML Schema for
this rich status information and describes the usage of comforant XML this rich status information and describes the usage of comforant XML
skipping to change at page 14, line 7 skipping to change at page 14, line 7
9. Internationalization Considerations 9. Internationalization Considerations
XML processors are obliged to recognize both UTF-8 and UTF-16 [1] XML processors are obliged to recognize both UTF-8 and UTF-16 [1]
encodings. XML provides for mechanisms to identify and use other encodings. XML provides for mechanisms to identify and use other
character encodings. Application transfer protocols MUST define character encodings. Application transfer protocols MUST define
which additional character encodings, if any, are to be allowed in which additional character encodings, if any, are to be allowed in
the use of the XML defined in this document. the use of the XML defined in this document.
10. IANA Considerations 10. IANA Considerations
10.1 XML Namespace URN Registration 10.1. XML Namespace URN Registration
This document makes use of the XML namespace and schema registry This document makes use of the XML namespace and schema registry
specified in XML_URN [7]. Accordingly, the following registration specified in XML_URN [7]. Accordingly, the following registration
information is provided for the IANA: information is provided for the IANA:
o XML Namespace URN/URI: o XML Namespace URN/URI:
* urn:ietf:params:xml:ns:iris-transport * urn:ietf:params:xml:ns:iris-transport
o Contact: o Contact:
skipping to change at page 15, line 7 skipping to change at page 15, line 7
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 * The XML Schema specified in Section 3
11. Security Considerations 11. Security Considerations
This document has not applicable security considerations. Transfer protocols using XML conformant to the XML Schema in this
document and offering security properties such as authentication and
confidentiality SHOULD offer an initial message from the server to
the client using the <version> element. This <version> element
SHOULD contain all relevant authentication identifiers in its
'autheticationId' attribute. The purpose of providing this initial
message is to help thwart downgrade attacks.
12. References 12. References
12.1 Normative References 12.1. Normative References
[1] The Unicode Consortium, "The Unicode Standard, Version 3", [1] The Unicode Consortium, "The Unicode Standard, Version 3",
ISBN 0-201-61633-5, 2000, <The Unicode Standard, Version 3>. ISBN 0-201-61633-5, 2000, <The Unicode Standard, Version 3>.
[2] World Wide Web Consortium, "Extensible Markup Language (XML) [2] World Wide Web Consortium, "Extensible Markup Language (XML)
1.0", W3C XML, February 1998, 1.0", W3C XML, February 1998,
<http://www.w3.org/TR/1998/REC-xml-19980210>. <http://www.w3.org/TR/1998/REC-xml-19980210>.
[3] World Wide Web Consortium, "Namespaces in XML", W3C XML [3] World Wide Web Consortium, "Namespaces in XML", W3C XML
Namespaces, January 1999, Namespaces, January 1999,
skipping to change at page 16, line 34 skipping to change at page 16, line 34
[5] World Wide Web Consortium, "XML Schema Part 1: Structures", [5] 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/>.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement [6] 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.
[7] Mealling, M., "The IETF XML Registry", RFC 3688, BCP 81, [7] Mealling, M., "The IETF XML Registry", RFC 3688, BCP 81,
February 2004. February 2004.
12.2 Informative References 12.2. Informative References
[8] Newton, A. and M. Sanz, "Internet Registry Information [8] Newton, A. and M. Sanz, "Internet Registry Information
Service", RFC 3891, January 2004. Service", RFC 3891, January 2004.
[9] Newton, A., "A Lightweight UDP Transfer Protocol for the [9] Newton, A., "A Lightweight UDP Transfer Protocol for the
Internet Registry Information Service", Internet Registry Information Service",
draft-ietf-crips-iris-lwz-02 (work in progress), April 2005. draft-ietf-crips-iris-lwz-02 (work in progress), April 2005.
[10] Newton, A., "XML Pipelining with Chunks for the Internet [10] Newton, A., "XML Pipelining with Chunks for the Internet
Registry Information Service", draft-ietf-crips-iris-xpc-00 Registry Information Service", draft-ietf-crips-iris-xpc-00
(work in progress), April 2005. (work in progress), April 2005.
Appendix A. Contributors
Substantive contributions to this document have been provided by the
members of the IETF's CRISP Working Group, especially Robert Martin-
Legene, Milena Caires, and David Blacka.
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: andy@hxr.us Email: andy@hxr.us
URI: http://www.verisignlabs.com/ URI: http://www.verisignlabs.com/
Appendix A. Contributors
Substantive contributions to this document have been provided by the
members of the IETF's CRISP Working Group, especially Robert Martin-
Legene, Milena Caires, and David Blacka.
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
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 19, line 41 skipping to change at page 19, 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 (2006). This document is subject Copyright (C) The Internet Society (2007). 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. 12 change blocks. 
33 lines changed or deleted 39 lines changed or added

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