Network Working Group A. Newton Internet-Draft VeriSign, Inc. Expires: August 20, 2002 February 19, 2002 IRIS Address Registry Schema draft-newton-iris-areg-00 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 20, 2002. Copyright Notice Copyright (C) The Internet Society (2002). All Rights Reserved. Abstract This document describes an IRIS registry namespace and schema for registered Internet address information. The schema extends the necessary query and result operations of IRIS (draft-newton-iris-00.txt) to provide the functional information service needs for syntaxes and results used by Internet address registries. Newton Expires August 20, 2002 [Page 1] Internet-Draft iris-areg February 2002 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Document Terminology . . . . . . . . . . . . . . . . . . . . 4 3. Schema Description . . . . . . . . . . . . . . . . . . . . . 5 3.1 Query Derivatives . . . . . . . . . . . . . . . . . . . . . 5 3.1.1 Query . . . . . . . . . . . . . . . . . . . 5 3.1.2 Query . . . . . . . . . . . . . . . . . . . . 5 3.1.3 Query . . . . . . . . . . . . . . . . . . . . . 5 3.1.4 Query . . . . . . . . . . . . . . . . . . . 5 3.1.5 Query . . . . . . . . . . . . . . . 6 3.2 Result Derivatives . . . . . . . . . . . . . . . . . . . . . 6 3.2.1 Result . . . . . . . . . . . . . . . . . . . . . 6 3.2.2 Result . . . . . . . . . . . . . . . . . . . . 6 3.2.3 Result . . . . . . . . . . . . . . . 6 3.2.4 Result . . . . . . . . . . . . . . . . . . . . 7 3.2.5 Result . . . . . . . . . . . . . . . . . . . . . 7 3.3 Global Types . . . . . . . . . . . . . . . . . . . . . . . . 7 3.4 Support for . . . . . . . . . . . . . . 7 4. Formal XML Syntax . . . . . . . . . . . . . . . . . . . . . 9 5. Internationalization Considerations . . . . . . . . . . . . 17 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . 18 7. Security Considerations . . . . . . . . . . . . . . . . . . 19 References . . . . . . . . . . . . . . . . . . . . . . . . . 20 Author's Address . . . . . . . . . . . . . . . . . . . . . . 20 A. An Example Request and Response . . . . . . . . . . . . . . 21 B. Outstanding Issues . . . . . . . . . . . . . . . . . . . . . 23 Full Copyright Statement . . . . . . . . . . . . . . . . . . 24 Newton Expires August 20, 2002 [Page 2] Internet-Draft iris-areg February 2002 1. Introduction This document describes an IRIS namespace for Internet address registries using an XML Schema[4] derived from and using the IRIS[8] schema. The query and result types outlined in this document are based on the functional requirements described in [9]. The schema given is this document is specified using the Extensible Markup Language (XML) 1.0 as described in [1], XML Schema notation as described in [3] and [4], and XML Namespaces as described in [2]. It is important to note that XML is case sensitive. XML specifications and examples provided in this document MUST be interpreted in the exact character case presented to develop a conforming implementation. Newton Expires August 20, 2002 [Page 3] Internet-Draft iris-areg February 2002 2. Document Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119[7]. Newton Expires August 20, 2002 [Page 4] Internet-Draft iris-areg February 2002 3. Schema Description The schema for this registry namespace defines no derivative. Applications of this namespace should rely on either the IRIS transport or for client authentication. IRIS requires the derivation of both query and result elements by a registry namespace. These descriptions follow. 3.1 Query Derivatives 3.1.1 Query This is a simple named look up of a single contact. The contact is specified by the element. 3.1.2 Query searches for contacts given search constraints. The element MUST be present and specifies the beginning of the common name of the contact. The element is OPTIONAL and MUST contain the end of the common name of the contact. The element is OPTIONAL and SHOULD contain a recognized type of contact. Typically the values for this element denote multiplicity of the contact, such as "organization" or "person". 3.1.3 Query This is a simple named look up of a name server host. The host MUST be specified by one of the following elements: o - a registry assigned unique identifier. o - the fully-qualified name of the host. o - the IP version 4 address of the host. o - the IP version 6 address of the host. 3.1.4 Query This is a simple named look up of an IP network. The network MUST be specified by one of the following elements: o - the IP version 4 network address of the network. o - the IP version 6 network address of the network. Newton Expires August 20, 2002 [Page 5] Internet-Draft iris-areg February 2002 3.1.5 Query This is a simple named look up of an autonomous system. The system MUST be specified by one of the following elements: o - a registry assigned unique identifier. o - the autonomous system number. 3.2 Result Derivatives 3.2.1 Result The element is the expected result of a query. It contains elements for the fully qualified host name of the host, the IP address of the host, and a reference to the host contact. The address elements contain the IP address of the name server, either IP v4 or IP v6, and an OPTIONAL reference to the network which contains the given address. 3.2.2 Result The element is the expected result of a query. It has the following child elements: o is an entity reference to the holder of the network. This element is OPTIONAL. o is an entity reference to the technical contact of the network. The element is OPTIONAL. o Either or MUST be present. Each element contains children representing the start and end of the network in the appropriate format. 3.2.3 Result The element is the expected result of a query. It has the following children: o is an entity reference to the holder of the autonomous system. This is an OPTIONAL element. o is an entity reference to the technical contact of the autonomous system. This is an OPTIONAL element. o is a registry assigned unique identifier. This element Newton Expires August 20, 2002 [Page 6] Internet-Draft iris-areg February 2002 MUST be present. o is a positive integer representing the starting number of the autonomous system. This element MUST be present. o is a positive integer representing the final number of the autonomous system. This element MUST be present. 3.2.4 Result The element is the expected result of a query. The children that MUST be present are , containing a registry assigned unique identifier, and , which holds the common name of the contact. The other children of this element are OPTIONAL and contain Internet, phone, and postal address information. 3.2.5 Result The element is the expected result of a query. This element MAY have no children, if it is not empty the children MUST be elements. 3.3 Global Types Some of the global types defined by the schema specified in this document are expressed using regular expressions. The regular expressions used for these definitions do not fully represent every allowable syntax for the intended type, but meet a standard of reasonableness for the expression of the types. 3.4 Support for The following types of named entities are recognized by the query of IRIS: o handles - unique identifiers assigned the IP address registry. These handles are defined to have their type as the first part of the handle. A query with a type "host" will yield a result. A query with a type "net" will yield a result. A query with a type "as" will yield a result. The other types, "org", "person", and "role" will yield a result. o host names - the fully qualified host names of nameservers. Queries with these names will yield a result. A host may be multi-homed and therefore known by many host names. o IP addresses - the address, either IP v4 or IP v6, of a Newton Expires August 20, 2002 [Page 7] Internet-Draft iris-areg February 2002 nameserver or a network. Because both name servers and networks are known by IP addresses, an entity lookup using an address will result in either or results. In rare cases where this may present a problem, a result may be returned. The children of this element are entity references, one to a name server and the other to a network. o autonomous system numbers - yields a result of . Newton Expires August 20, 2002 [Page 8] Internet-Draft iris-areg February 2002 4. Formal XML Syntax This IP address registry is specified in the XML Schema notation. 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. Due to document formatting restrictions, readers should note that the regular expressions expressed in this schema DO NOT contain whitespace within the quotes containing the regular expression. IP address registry schema derived from IRIS schema Newton Expires August 20, 2002 [Page 10] Internet-Draft iris-areg February 2002 Newton Expires August 20, 2002 [Page 15] Internet-Draft iris-areg February 2002 Newton Expires August 20, 2002 [Page 16] Internet-Draft iris-areg February 2002 5. Internationalization Considerations The defining schema for this registry namespace is represented in XML, which provides native support for encoding information using the double-byte Unicode character set and its more compact representations including UTF-8. Compliant XML processors are required to understand both UTF-8 and raw Unicode character sets; XML also includes a provision for identifying other character sets through use of an "encoding" attribute in an processing instruction. The complete list of character set encoding identifiers is maintained by IANA and is described in [10] and [5]. Newton Expires August 20, 2002 [Page 17] Internet-Draft iris-areg February 2002 6. IANA Considerations XML schemas require a URI for unique identification. Schemas MUST be registered to ensure URI uniqueness, but the IETF does not currently have a recommended repository for the registration of XML schemas. This document uses URNs to describe XML namespaces and XML schemas. IANA SHOULD maintain a registry of XML namespace and schema URI assignments. Per policies described in [6], URI assignment requests SHOULD be reviewed by a designated expert, and values SHOULD be assigned only as a result of standards action taken by the IESG. Newton Expires August 20, 2002 [Page 18] Internet-Draft iris-areg February 2002 7. Security Considerations The schema given in this document describes no derivatives nor specifies any authentication mechanism beyond that specified by [8]. Newton Expires August 20, 2002 [Page 19] Internet-Draft iris-areg February 2002 References [1] World Wide Web Consortium, "Extensible Markup Language (XML) 1.0", W3C XML, February 1998, . [2] World Wide Web Consortium, "Namespaces in XML", W3C XML Namespaces, January 1999, . [3] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C XML Schema, October 2000, . [4] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C XML Schema, October 2000, . [5] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", RFC 1700, STD 2, October 1994. [6] Narten, T. and H.T. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", RFC 2434, BCP 26, October 1998. [7] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. [8] Newton, A, "Internet Registry Information Service", Internet Draft, a work in-progress., February 2002. [9] Newton, A and S Kerr, "Internet Registry Directory Requirements", Internet Draft, a work in-progress., January 2002. [10] Author's Address Andrew L. Newton VeriSign, Inc. 21345 Ridgetop Circle Sterling, VA 20166 USA Phone: +1 703 948 3382 EMail: anewton@verisignlabs.com URI: http://www.research.netsol.com/ Newton Expires August 20, 2002 [Page 20] Internet-Draft iris-areg February 2002 Appendix A. An Example Request and Response The following is an example of an IRIS request and response using this registry namespace. This XML instance is a request to find contacts. RIPE organization This XML instance is a response from Figure 2. org:RIPE-NCC-ARIN RIPE Network Coordination Centre Newton Expires August 20, 2002 [Page 21] Internet-Draft iris-areg February 2002 Reseaux IP European Network Co-ordination Centre nicdb@RIPE.NET
Singel 258
Amsterdam NL-1016 AB NL +31 20 535 4444
Newton Expires August 20, 2002 [Page 22] Internet-Draft iris-areg February 2002 Appendix B. Outstanding Issues The following items will need further investigation for future versions of this document. o According to draft-newton-ir-dir-requirements.txt, there needs to be a query to find the network for which a contact is associated. o Some of the terminology between the documents needs to be synced. For instance, the word "nameserver" should be used instead of "host". Newton Expires August 20, 2002 [Page 23] Internet-Draft iris-areg February 2002 Full Copyright Statement Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgement Funding for the RFC editor function is currently provided by the Internet Society. Newton Expires August 20, 2002 [Page 24]