<sequence>
<element
name="unsupportedLanguage"
type="language"
minOccurs="1"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="languageNotSupported"
type="ereg:languageNotSupportedType"
substitutionGroup="iris:genericCode" />
</schema>
Figure 1: ereg.xsd
5. Blocks Extensible Exchange Protocol (BEEP) Transport Compliance
IRIS allows several extensions of the core capabilities. This
section outlines those extensions allowable by IRIS-BEEP [6].
5.1. Message Pattern
This registry type uses the default message pattern as described in
IRIS-BEEP [6].
5.2. Server Authentication
This registry type only uses the basic Transport Layer Security (TLS)
server authentication method as described in IRIS-BEEP [6].
6. URI Resolution
6.1. Application Service Label
The application service label associated with this registry type MUST
be "EREG1". This is the abbreviated form of the URN for this
registry type, urn:ietf:params:xml:ns:ereg1.
7. Internationalization Considerations
Implementers should be aware of considerations for
internationalization in IRIS [5].
The social data associated with contacts may be non-ASCII, and could
contain virtually any Unicode character. The <language> element is
provided in queries that have potential to traverse such data.
Clients should use these elements to indicate to the server of the
target languages desired, and servers should use these elements to
better enable normalization and search processes (see
<http://www.unicode.org/reports/tr15/>).
Clients needing to localize the data tags in this protocol should
take note that localization is only needed on the names of XML
elements and attributes with the exception of elements containing
date and time information. The schema for this registry has been
designed so that clients need not interpret the content of elements
or attributes for localization, other than those elements containing
date and time information.
Clients should also make use of the <language> elements provided in
many of the results. Results containing data that may be in Unicode
are accompanied by these elements in order to aid better presentation
of the data to the user.
The "dateTimePrivacyType" element content conforms to the XML Schema
[3] data type "dateTime". The contents of this element MUST be
specified using the ’Z’ indicator for Coordinated Universal Time
(UTC).
8. IANA Considerations
8.1. XML Namespace URN Registration
This document makes use of a proposed XML namespace and schema
registry specified in XML_URN [16]. Accordingly, the following
registration information is provided for the IANA:
o URN/URI:
* urn:ietf:params:xml:schema:ereg1
o Contact:
* Andrew Newton <andy@hxr.us>
o XML:
* The XML Schema specified in Section 4
o URN/URI:
* urn:ietf:params:xml:ns:ereg1
o Contact:
* Andrew Newton <andy@hxr.us>
o XML:
* None.
8.2. S-NAPTR Registration
The following S-NAPTR application service tag [20] has been
registered with IANA according to the IANA considerations defined in
IRIS [5]:
EREG1
8.3. BEEP Registration
The following BEEP Profile URI has been registered with IANA
(http://www.iana.org/assignments/beep-parameters), in addition to the
registration provided in IRIS-BEEP [6].
http://iana.org/beep/iris1/ereg1
9. Security Considerations
This document lays out no new considerations for security precautions
beyond that specified in IRIS [5].
10. Normative References
[1] World Wide Web Consortium, "Extensible Markup Language (XML)
1.0", W3C XML, February 1998,
<http://www.w3.org/TR/1998/REC-xml-19980210>.
[2] World Wide Web Consortium, "Namespaces in XML", W3C XML
Namespaces, January 1999,
<http://www.w3.org/TR/1999/REC-xml-names-19990114>.
[3] World Wide Web Consortium, "XML Schema Part 2: Datatypes", W3C
XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-2/>.
[4] World Wide Web Consortium, "XML Schema Part 1: Structures", W3C
XML Schema, October 2004, <http://www.w3.org/TR/xmlschema-1/>.
[5] Newton, A. and M. Sanz, "IRIS: The Internet Registry
Information Service (IRIS) Core Protocol", RFC 3981, January
2005.
[6] Newton, A. and M. Sanz, "Using the Internet Registry
Information Service (IRIS) over the Blocks Extensible Exchange
Protocol (BEEP)", RFC 3983, January 2005.
[7] Hinden, R. and S. Deering, "Internet Protocol Version 6 (IPv6)
Addressing Architecture", RFC 3513, April 2003.
[8] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981.
[9] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987.
[10] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, BCP 14, March 1997.
[11] International Organization for Standardization, "Codes for the
representation of names of countries, 3rd edition", ISO
Standard 3166, August 1988.
[12] Braden, R., "Requirements for Internet Hosts - Application and
Support", STD 3, RFC 1123, October 1989.
[13] International Telecommunications Union, "The International
Public Telecommunication Numbering Plan", ITU-T Recommendation
E.164, February 2005.
[14] International Telecommunications Union, "Notation for national
and international telephone numbers, e-mail addresses and Web
addresses", ITU-T Recommendation E.123, February 2001.
[15] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile
for Internationalized Domain Names (IDN)", RFC 3491, March
2003.
[16] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[17] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
Identifiers (URI) Dynamic Delegation Discovery System (DDDS)
Application (ENUM)", RFC 3761, April 2004.
[18] Hollenbeck, S., "Domain Registry Grace Period Mapping for the
Extensible Provisioning Protocol (EPP)", RFC 3915, September
2004.
[19] Braden, R., "Requirements for Internet Hosts - Application and
Support", STD 3, RFC 1123, October 1989.
[20] Daigle, L. and A. Newton, "Domain-Based Application Service
Location Using SRV RRs and the Dynamic Delegation Discovery
Service (DDDS)", RFC 3958, January 2005.
Appendix A. Contributions and Acknowledgements
This document is a derivative of the specification used to define
forward domain registries for IRIS. Marcos Sanz was a major
contributor to that specification, and many of his words and ideas
are present in this document. Other contributors include Alexander
Mayrhofer, Bernie Hoeneisen, Otmar Lendl, and Scott Hollenbeck.
Author’s Address
Andrew L. Newton
VeriSign, Inc.
21345 Ridgetop Circle
Sterling, VA 20166
USA
Phone: +1.7039483382
EMail: andy@hxr.us
URI: http://www.verisignlabs.com/
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
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
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).