[OPS-NM] OPS Area WG

Ron Bonica <rbonica@juniper.net> Thu, 10 May 2007 18:37 UTC

Return-path: <ops-nm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmDWS-0001HW-SC; Thu, 10 May 2007 14:37:52 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43) id 1HmDWR-0001HH-R0 for ops-nm-confirm+ok@megatron.ietf.org; Thu, 10 May 2007 14:37:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmDWR-0001H8-HR; Thu, 10 May 2007 14:37:51 -0400
Received: from kremlin.juniper.net ([207.17.137.120] helo=smtpa.juniper.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmDWR-0004of-8C; Thu, 10 May 2007 14:37:51 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37]) by smtpa.juniper.net with ESMTP; 10 May 2007 11:37:51 -0700
X-IronPort-AV: i="4.14,518,1170662400"; d="scan'208"; a="1490037:sNHT33980736"
Received: from [172.23.1.86] ([172.23.1.86] RDNS failed) by proton.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 10 May 2007 14:37:49 -0400
Message-ID: <46436677.1070309@juniper.net>
Date: Thu, 10 May 2007 14:37:43 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ops-area@ietf.org, ops-nm@ietf.org
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 May 2007 18:37:49.0878 (UTC) FILETIME=[4FBCF560:01C79332]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc:
Subject: [OPS-NM] OPS Area WG
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>, <mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Folks,

Dan and I would like to propose an area-wide working group whose charter
is reflected below. Please read and comment upon the proposed charter.

                               Dan and Ron

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

Chair(s):

TBD
TBD

Area Directors:

Dan Romascanu <dromasca@avaya.com>
Ronald Bonica <rbonica@juniper.net>


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
or 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
operational and manageability requirements that need to be covered in
IETF documents, especially those documents that include requirements
and specification of new protocols or protocol extensions.

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

(C) Maintenance and extensions of documents that define MIB modules
which were developped in working groups that have concluded.

Goals and Milestones:

June 2007 - Initial submission for the Guidelines for Considering
Operations and Management of New Protocols Internet-Draft

October 2007 - Initial submission for the Template for Generic
Management Data Models

October 2007 - Initial submission for the Structured Data Elements
(SDEs) for syslog

December  2007 - WGLC for the Guidelines for Considering Operations and
Management of New Protocols Internet-Draft

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

April 2008 - WGLC for the Template for Generic
Management Data Models

April 2008 - WGLC for the  Structured Data Elements
(SDEs) for syslog

June 2008 - Submit the Template for Generic
Management Data Models to the IESG for consideration as BCP

June 2008 - Submit the  Structured Data Elements
(SDEs) for syslog to the IESG for consideration as Proposed Standard


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm