Guidelines for Defining Extensions to IODEF
draft-ietf-mile-template-03

The information below is for an old version of the document
Document Type Active Internet-Draft (mile WG)
Last updated 2012-03-07
Replaces draft-trammell-mile-template
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Kathleen Moriarty
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
mile Working Group                                           B. Trammell
Internet-Draft                                                ETH Zurich
Intended status: Informational                             March 7, 2012
Expires: September 8, 2012

              Guidelines for Defining Extensions to IODEF
                    draft-ietf-mile-template-03.txt

Abstract

   This document provides guidelines for extensions to IODEF [RFC5070]
   for exchange of incident management data, and 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 8, 2012.

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                Expires September 8, 2012               [Page 1]
Internet-Draft         IODEF Extension Guidelines             March 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Applicability of Extensions to IODEF . . . . . . . . . . . . .  3
   3.  Selecting a Mechanism for IODEF Extension  . . . . . . . . . .  4
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  5
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  5
   6.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  5
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  5
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  6
   Appendix A.  Document Template . . . . . . . . . . . . . . . . . .  6
     A.1.  Introduction . . . . . . . . . . . . . . . . . . . . . . .  6
     A.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  7
     A.3.  Applicability  . . . . . . . . . . . . . . . . . . . . . .  7
     A.4.  Extension Definition . . . . . . . . . . . . . . . . . . .  7
       A.4.1.  IODEF Data Types . . . . . . . . . . . . . . . . . . .  8
     A.5.  Security Considerations  . . . . . . . . . . . . . . . . .  9
     A.6.  IANA Considerations  . . . . . . . . . . . . . . . . . . .  9
     A.7.  References . . . . . . . . . . . . . . . . . . . . . . . . 10
     A.8.  Appendix A: XML Schema Definition for Extension  . . . . . 10
     A.9.  Appendix B: Examples . . . . . . . . . . . . . . . . . . . 10
   Appendix B.  Example Enumerated Type Extension Definition:
                E.164 Address . . . . . . . . . . . . . . . . . . . . 11
   Appendix C.  Example Element Definition: Test  . . . . . . . . . . 11
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12

Trammell                Expires September 8, 2012               [Page 2]
Internet-Draft         IODEF Extension Guidelines             March 2012

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 is itself designed to be copied out and
   filled in as the starting point of an Internet-Draft about an IODEF
   extension.

2.  Applicability of Extensions to IODEF

   Before deciding to extend IODEF, the first step is to determine
   whether an IODEF extension is a good fit for a given problem.  There
   are two sides to this question:
Show full document text