RE: [OPS-NM] OPS Area WG
"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Thu, 10 May 2007 19:02 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 1HmDu3-0008Qx-9d; Thu, 10 May 2007 15:02:15 -0400
Received: from ops-nm by megatron.ietf.org with local (Exim 4.43) id 1HmDu1-0008QZ-Uj for ops-nm-confirm+ok@megatron.ietf.org; Thu, 10 May 2007 15:02:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmDu1-0008QQ-Kr; Thu, 10 May 2007 15:02:13 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100] helo=nj300815-nj-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmDtz-00077F-AH; Thu, 10 May 2007 15:02:13 -0400
Received: from 51.105.64.135.in-addr.arpa (HELO IS0004AVEXU1.global.avaya.com) ([135.64.105.51]) by nj300815-nj-outbound.avaya.com with ESMTP; 10 May 2007 15:02:10 -0400
X-IronPort-AV: i="4.14,518,1170651600"; d="scan'208"; a="14310763:sNHT7966698"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OPS-NM] OPS Area WG
Date: Thu, 10 May 2007 22:02:09 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0CCFB46C@is0004avexu1.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPS-NM] OPS Area WG
Thread-Index: AceTMoBK450xlhzPR+mXSR7Z0W5mdQAAv6rQ
References: <46436677.1070309@juniper.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Ron Bonica <rbonica@juniper.net>, ops-area@ietf.org, ops-nm@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc:
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
One more thing - please send feedback until May 17 the latest as we want to put the charter for approval on the agenda of the may 24 IESG telechat. Dan and Ron > -----Original Message----- > From: Ron Bonica [mailto:rbonica@juniper.net] > Sent: Thursday, May 10, 2007 9:38 PM > To: ops-area@ietf.org; ops-nm@ietf.org > Subject: [OPS-NM] OPS Area WG > > 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 > _______________________________________________ OPS-NM mailing list OPS-NM@ietf.org https://www1.ietf.org/mailman/listinfo/ops-nm
- [OPS-NM] OPS Area WG Ron Bonica
- RE: [OPS-NM] OPS Area WG Romascanu, Dan (Dan)
- Re: [OPS-NM] OPS Area WG Juergen Schoenwaelder
- RE: [OPS-AREA] RE: [OPS-NM] OPS Area WG STEPHAN Emile RD-CORE-LAN