Operations and Management Area Working Group (opsawg)
-----------------------------------------------------

 Charter
 Last Modified: 2009-11-17

 Current Status: Active Working Group

 Chair(s):
     Scott Bradner  <sob@harvard.edu>
     Chris Liljenstolpe  <chris@cw.net>

 Operations and Management Area Director(s):
     Dan Romascanu  <dromasca@avaya.com>
     Ronald Bonica  <rbonica@juniper.net>

 Operations and Management Area Advisor:
     Dan Romascanu  <dromasca@avaya.com>

 Mailing Lists: 
     General Discussion:opsawg@ietf.org
     To Subscribe:      https://www.ietf.org/mailman/listinfo/opsawg
     Archive:           http://www.ietf.org/mail-archive/web/opsawg

Description of Working Group:

The Operations and Management Area receives occasional proposals for 
the development and publication of RFCs dealing with operational and
management topics that are not in scope of an existing working group 
and do not justify the formation of a new working group. The OPSAWG 
will serve as the forum for developing such work items in the IETF.

The OPSAWG mailing list is an open discussion forum for such work 
items, when they arise. The working group meets if there are active 
proposals that require discussion. The working group milestones are 
updated as needed to reflect the current work items and their 
associated milestones. All new work items and rechartering proposals 
will be brought for approval with the IESG.

The focus of the work will be on topics that govern the behavior or WGs
in the O&M area (e.g., manageability requirements) and on small, 
highly focused projects that don't merit a WG of their own or belong 
to WGs that have already concluded (e.g. advancement of documents on 
the standards track, application statements, extensions of MIB 
modules).

The OPSAWG will undertake only work items that are proved to have at
least a reasonable level of interest from the operators and users
community and have a committed number of editors and reviewers. It is
not within the scope of the OPSAWG to pick up failed WG work or parts 
of a WG charter items that could not come to convergence on what they 
were chartered to do.

The currently active OPSAWG work items mostly fall under the following
topics:

(A) Development of a BCP document that will provide guidelines for
authors and a reference for reviewers of IETF documents that specify 
new protocols or protocol extensions about the information about 
operational and manageability requirements that needs to be covered in 
these documents

(B) Templates and tools for Operations and Management Area Documents

(C) Maintenance and small scale extensions of documents that were
developed in working groups that have concluded (e.g. MIB modules).

 Goals and Milestones:

   Done         Initial submission for the 'SNMP Engine ID Discovery' 
                Internet-Draft 

   Done         Initial submission for the 'Guidelines for Considering 
                Operations and Management of New Protocols' Internet-Draft 

   Done         Initial submission for the 'Template for Generic Management 
                Data Models' Internet-Draft 

   Done         WGLC for the 'SNMP Engine ID Discovery' Internet-Draft 

   Done         Initial submission for the 'Structured Data Elements (SDEs) for 
                syslog' Internet-Draft 

   Done         Submit the 'SNMP Engine ID Discovery' Internet-Draft to the 
                IESG for consideration as Proposed Standard 

   Done         WGLC for the 'Guidelines for Considering Operations and 
                Management of New Protocols' Internet-Draft 

   Done         Submit the 'Guidelines for Considering Operations and 
                Management of New Protocols' Internet-Draft to the IESG for 
                consideration as BCP 

   Apr 2008       WGLC for the 'Template for Generic Management Data Models' 

   Done         WGLC for the 'Structured Data Elements (SDEs) for syslog' 

   Jun 2008       Submit the 'Template for Generic Management Data Models' to the 
                IESG for consideration as BCP 

   Done         Submit the 'Structured Data Elements (SDEs) for syslog' to the 
                IESG for consideration as Proposed Standard 


 Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Feb 2008 Mar 2009   <draft-ietf-opsawg-smi-datatypes-in-xsd-05.txt>
                Expressing SNMP SMI Datatypes in XML Schema Definition Language 

Sep 2009 Jan 2010   <draft-ietf-opsawg-mpls-tp-oam-def-01.txt>
                "The OAM Acronym Soup" 

Jan 2010 Jan 2010   <draft-ietf-opsawg-oam-overview-00.txt>
                An Overview of Operations, Administration, and Maintenance 
                (OAM) Mechanisms 

 Request For Comments:

  RFC   Stat Published     Title
------- -- ----------- ------------------------------------
RFC5343 PS   Sep 2008    Simple Network Management Protocol (SNMP) Context 
                       EngineID Discovery 

RFC5676 PS   Oct 2009    Definitions of Managed Objects for Mapping SYSLOG 
                       Messages to Simple Network Management Protocol (SNMP) 
                       Notifications 

RFC5675 PS   Oct 2009    Mapping Simple Network Management Protocol (SNMP) 
                       Notifications to SYSLOG Messages 

RFC5674 PS   Oct 2009    Alarms in SYSLOG 

RFC5706 I    Nov 2009    Guidelines for Considering Operations and Management of 
                       New Protocols and Protocol Extensions