$Id: opsec-meta.txt,v 1.1 2003/05/17 11:47:04 george Exp $

This document gives meta-information about the opsec draft
(http://www.port111.com/opsec/) it's goals, pending changes and it's
relationship to related efforts.  Send feedback to the mailing list
(opsec@ops.ietf.org).

Why ?

  The opsec Internet Draft is being released as a "request for
  comments" (in the standard English sense of the words, not the
  technical IETF meaning of the term).  The goal is to get feedback
  from the network operations, vendor and security communities.

Where Next ?

  The intent is to go through one to three rounds as an Internet Draft
  and then re-evaluate the proper course of action.  Some
  possibilities include:

    * Collaborate with ANSI on updates to T1.276-200x
    * Proceed towards a single individual submission informational RFC
    * Split into several drafts (BCP vs. non-BCP, functional vs.
      assurance, etc.)
    * Form a working group

Relationship to ANSI draft T1.276-200x

  There is heavy overlap between part the opsec document and ANSI draft
  T1.276-200x.  Some of the distinctions between opsec and the ANSI draft
  are that the opsec draft is:

    * exclusively focused on IP
    * not exclusive to telecom infrastructure
    * not restricted to the management plane 
    * has support for "profiles" (core, edge, hosts, toasters..)
    * written in the IETF context (format, references, etc.)
    * something that originated from customer requirements

Outstanding Issues

  The draft is far from perfect.  It is large.  There are many 
  know, outstanding issues.  A list of some of the outstanding
  issues and pending changes is available at 
  
      http://www.port111.com/opsec/opsec-todo.txt

  Also see the mailing list archives at http://ops.ietf.org

$Log: opsec-meta.txt,v $
Revision 1.1  2003/05/17 11:47:04  george
Prepare for -00 release.