idnits 2.17.1 draft-trammell-mile-iodef-xmlreg-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 7, 2012) is 4433 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 5070 (Obsoleted by RFC 7970) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MILE Working Group B. Trammell 3 Internet-Draft ETH Zurich 4 Intended status: Standards Track March 7, 2012 5 Expires: September 8, 2012 7 Expert Review for IODEF Extensions in IANA XML Registry 8 draft-trammell-mile-iodef-xmlreg-01.txt 10 Abstract 12 This document specifies restrictions on additions to the subset of 13 the IANA XML Namespace and Schema registries, to require Expert 14 Review for extensions to IODEF. 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on September 8, 2012. 33 Copyright Notice 35 Copyright (c) 2012 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 1. Introduction 50 IODEF extensions via class extension through AdditionalData and 51 RecordItem elements, as per section 5.2 of [RFC5070], generally 52 register their namespaces and schemas with the IANA XML Namespace 53 registry at http://www.iana.org/assignments/xml-registry/ns.html and 54 the IANA XML Schema registry at 55 http://www.iana.org/assignments/xml-registry/schema.html, 56 respectively [RFC3688]. 58 In addition to schema reviews required by IANA, these registry 59 requests should be accompanied by a review by IODEF experts to ensure 60 the specified AdditionalData and/or RecordItem contents are 61 compatible with IODEF and with other existing IODEF extensions. This 62 document specifies that review. 64 2. Expert Review of IODEF-related XML Registry Entries 66 Changes to the XML Schema registry for schema names beginning with 67 "urn:ietf:params:xml:schema:iodef" are subject to an additional IODEF 68 Expert Review [RFC5226]. 70 The IODEF expert(s) for these reviews will be designated by the IETF 71 Security Area Directors. 73 3. Security Considerations 75 This document has no security considerations. 77 4. IANA Considerations 79 [IANA NOTE: The authors request that IANA include a note at the top 80 of http://www.iana.org/assignments/xml-registry/schema.html, stating 81 "Changes to the XML Schema registry for schema names beginning with 82 'urn:ietf:params:xml:schema:iodef' are subject to an additional IODEF 83 Expert Review [RFC5226]," and naming the designated expert.] 85 This document specifies additional expert reviews for IODEF 86 extensions, on the XML Schema registry 87 (http://www.iana.org/assignments/xml-registry/schema.html), in 88 Section 2. 90 5. Normative References 92 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 93 January 2004. 95 [RFC5070] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident 96 Object Description Exchange Format", RFC 5070, 97 December 2007. 99 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 100 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 101 May 2008. 103 Author's Address 105 Brian Trammell 106 Swiss Federal Institute of Technology Zurich 107 Gloriastrasse 35 108 8092 Zurich 109 Switzerland 111 Phone: +41 44 632 70 13 112 Email: trammell@tik.ee.ethz.ch