idnits 2.17.1 draft-ietf-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 : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC5070, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5070, updated by this document, for RFC5378 checks: 2002-10-29) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 9, 2012) is 4363 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 (==), 3 comments (--). 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 Updates: 5070 (if approved) May 9, 2012 5 Intended status: Standards Track 6 Expires: November 10, 2012 8 Expert Review for IODEF Extensions in IANA XML Registry 9 draft-ietf-mile-iodef-xmlreg-01.txt 11 Abstract 13 This document specifies restrictions on additions to the subset of 14 the IANA XML Namespace and Schema registries, to require Expert 15 Review for extensions to IODEF. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on November 10, 2012. 34 Copyright Notice 36 Copyright (c) 2012 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 1. Introduction 51 IODEF extensions via class extension through AdditionalData and 52 RecordItem elements, as per section 5.2 of [RFC5070], generally 53 register their namespaces and schemas with the IANA XML Namespace 54 registry at http://www.iana.org/assignments/xml-registry/ns.html and 55 the IANA XML Schema registry at 56 http://www.iana.org/assignments/xml-registry/schema.html, 57 respectively [RFC3688]. 59 In addition to schema reviews required by IANA, these registry 60 requests should be accompanied by a review by IODEF experts to ensure 61 the specified AdditionalData and/or RecordItem contents are 62 compatible with IODEF and with other existing IODEF extensions. This 63 document specifies that review. 65 2. Expert Review of IODEF-related XML Registry Entries 67 Changes to the XML Schema registry for schema names beginning with 68 "urn:ietf:params:xml:schema:iodef" are subject to an additional IODEF 69 Expert Review [RFC5226] for IODEF-correctness and -appropriateness. 71 The IODEF expert(s) for these reviews will be designated by the IETF 72 Security Area Directors. 74 3. Security Considerations 76 This document has no security considerations. 78 4. IANA Considerations 80 [IANA NOTE: The authors request that IANA list an IODEF Expert be 81 designated by the IETF Security Area Directors on the XML Schema 82 registry, responsible for performing an IODEF Expert Review [RFC5226] 83 on schemas with names beginning with 84 'urn:ietf:params:xml:schema:iodef', to be noted in the most 85 appropriate way. This should appear in the same place as other 86 expert designations, and note that the review is IODEF-specific. In 87 addition, the References column of 88 urn:ietf:params:xml:schema:iodef-1.0 at 89 https://www.iana.org/assignments/xml-registry/schema.html should be 90 made to reference this document as well as RFC5070.] 92 This document specifies additional expert reviews for IODEF 93 extensions, on the XML Schema registry 94 (http://www.iana.org/assignments/xml-registry/schema.html), in 95 Section 2. 97 5. Normative References 99 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 100 January 2004. 102 [RFC5070] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident 103 Object Description Exchange Format", RFC 5070, 104 December 2007. 106 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 107 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 108 May 2008. 110 Author's Address 112 Brian Trammell 113 Swiss Federal Institute of Technology Zurich 114 Gloriastrasse 35 115 8092 Zurich 116 Switzerland 118 Phone: +41 44 632 70 13 119 Email: trammell@tik.ee.ethz.ch