Guidelines and Template for Defining Extensions to the Incident Object Description Exchange Format (IODEF)
RFC 6684

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 02
• 03
• 04
• 05

Internet Engineering Task Force (IETF)                       B. Trammell
Request for Comments: 6684                                    ETH Zurich
Category: Informational                                        July 2012
ISSN: 2070-1721

         Guidelines and Template for Defining Extensions to the
          Incident Object Description Exchange Format (IODEF)

Abstract

   This document provides guidelines for extensions to the Incident
   Object Description Exchange Format (IODEF) described in RFC 5070 for
   exchange of incident management data, and it contains a template for
   Internet-Drafts describing those extensions, in order to ease the
   work and improve the quality of extension descriptions.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6684.

Copyright Notice

   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 of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Trammell                      Informational                     [Page 1]
RFC 6684               IODEF Extension Guidelines              July 2012

Table of Contents

   1. Introduction ....................................................2
   2. Applicability of Extensions to IODEF ............................3
   3. Selecting a Mechanism for IODEF Extension .......................3
   4. Security Considerations .........................................5
   5. Acknowledgments .................................................5
   6. References ......................................................5
      6.1. Normative References .......................................5
      6.2. Informative References .....................................5
   Appendix A. Document Template ......................................7
     A.1. Introduction ................................................7
     A.2. Terminology .................................................7
     A.3. Applicability ...............................................7
     A.4. Extension Definition ........................................8
     A.5. Security Considerations .....................................8
     A.6. IANA Considerations .........................................9
     A.7. Manageability Considerations ...............................10
     A.8. Appendix A: XML Schema Definition for Extension ............10
     A.9. Appendix B: Examples .......................................10
   Appendix B. Example Enumerated Type Extension Definition:
               Presentation Action ...................................10
   Appendix C. Example Element Definition: Test ......................10

1.  Introduction

   In the five years since the specification of IODEF [RFC5070], the
   threat environment has evolved, as has the practice of cooperative
   network defense.  These trends, along with experience gained through
   implementation and deployment, have indicated the need to extend
   IODEF.  This document provides guidelines for defining these
   extensions.  It starts by describing the applicability of IODEF
   extensions, and the IODEF extension mechanisms, before providing a
   section (Appendix A) that contains a template to be the starting
   point for any future Internet-Draft about an IODEF extension.

   This document is designed to give guidance on the extension of IODEF,
   especially for those extension authors who may be new to the IETF
   process.  Nothing in this document should be construed as defining
   policies for the definition of these extensions.

   At publication time, the Managed Incident Lightweight Exchange (MILE)
   working group of the IETF provides a home for work on IODEF
   extensions that do not otherwise have a natural home.  IODEF
   extensions that require the expertise of other IETF working groups or
   other standards development organizations may be done within those