RFC Errata
RFC 4991, "A Common Schema for Internet Registry Information Service Transfer Protocols", August 2007
Source of RFC: crisp (app)
Errata ID: 1011
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-09-09
Held for Document Update by: Alexey Melnikov
Date Held: 2010-05-21
Section 10 says:
Section 10 (on page 10) is confusing due to missing appropriate structuring, misleadingly joining the two distinct registrations. The RFC says (I have omitted blank lines in the bullets for the sake of better readability in the context of this message): ------ 10. IANA Considerations 10.1. XML Namespace URN Registration This document makes use of the XML namespace and schema registry specified in XML_URN [7]. Accordingly, the following registrations have been made by IANA: o XML Namespace URN/URI: * urn:ietf:params:xml:ns:iris-transport o Contact: * Andrew Newton <andy@hxr.us> o XML: * None o XML Schema URN/URI: * urn:ietf:params:xml:schema:iris-transport o Contact: * Andrew Newton <andy@hxr.us> o XML: * The XML Schema specified in Section 3 ------ Perhaps, it should better say: ------ 10. IANA Considerations This document makes use of the XML namespace and schema registry specified in XML_URN [7]. Accordingly, the following registrations have been made by IANA: 10.1. XML Namespace URN Registration o XML Namespace URN/URI: * urn:ietf:params:xml:ns:iris-transport o Contact: * Andrew Newton <andy@hxr.us> o XML: * None 10.2. XML Schema URN/URI Registration o XML Schema URN/URI: * urn:ietf:params:xml:schema:iris-transport o Contact: * Andrew Newton <andy@hxr.us> o XML: * The XML Schema specified in Section 3 ------ Furthermore, all occurrences of "URN/URI" might better have been shortened to "URN" there, for brevity and clarity.