RFC 6685

Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry

📅 published July 2012, from ietf

RFC 6685 📜💖

Title: Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML Registry 🎀

  • Authors: B. Trammell (ETH Zurich)
  • Category: Standards Track ✨
  • Date: July 2012 🌸
  • Updates: RFC 5070 🦋
  • ISSN: 2070-1721

Abstract 🌈

okay so this doc puts restrictions on new stuff going into the IANA XML Namespace and Schema registries 💅 specifically, it makes sure Expert Review happens for extensions to Incident Object Description Exchange Format (IODEF). it's giving quality control, bestie 🫶

Status of This Memo 📝

this is an Internet Standards Track document 🔥

it's a product of the Internet Engineering Task Force (IETF) 🧚 it represents the consensus of the IETF community. it got public review and was approved for publication by the Internet Engineering Steering Group (IESG). more info on Internet Standards is in Section 2 of RFC 5741 💜

for the current status, any errata, and how to give feedback, check http://www.rfc-editor.org/info/rfc6685.

Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. 🎀

this document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication. please actually read these, bestie, because they spell out your rights and restrictions for this doc 🙈 code components pulled out of this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they're provided without warranty as described in the Simplified BSD License 💅

1. Introduction ✨

so, IODEF extensions usually work through class extension using AdditionalData and RecordItem elements, per Section 5.2 of [RFC5070] 🦋 those extensions normally register their namespaces and schemas with the IANA XML Namespace registry at http://www.iana.org/assignments/xml-registry/ns.html and the IANA XML Schema registry at http://www.iana.org/assignments/xml-registry/schema.html, respectively [RFC3688] 🧚

on top of the schema reviews IANA already does, these registry requests should also get a review from IODEF experts 👑 that makes sure the AdditionalData and/or RecordItem contents are compatible with IODEF and with the other existing IODEF extensions. this document is where that review gets specified 💖

main character moment 💅 changes to the XML Schema registry for schema names beginning with urn:ietf:params:xml:schema:iodef get an extra IODEF Expert Review [RFC5226] for IODEF correctness and appropriateness 🔥

the IODEF expert(s) for these reviews will be designated by the IETF Security Area Directors 🫶

3. Security Considerations 🔐

this document has no security considerations 🙈

4. IANA Considerations 🎀

this document adds the extra expert reviews for IODEF extensions on the XML Schema registry (http://www.iana.org/assignments/xml-registry/schema.html), as described in Section 2 🌈

5. Normative References 📚

  • [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. 🧚
  • [RFC5070] Danyliw, R., Meijer, J., and Y. Demchenko, "The Incident Object Description Exchange Format", RFC 5070, December 2007. 🦋
  • [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. 💜

Author's Address 🌷

Brian Trammell Swiss Federal Institute of Technology Zurich Gloriastrasse 35 8092 Zurich Switzerland

Phone: +41 44 632 70 13 EMail: trammell@tik.ee.ethz.ch 💌

📦 where this page comes from