RE: RE: [OPS-NM] OPS Area WG
"STEPHAN Emile RD-CORE-LAN" <[email protected]> Tue, 15 May 2007 15:39:53 +0200
| Newsgroups | gmane.ietf.ops,gmane.ietf.ops-nm |
|---|---|
| Message-ID | <DD8B8FEBBFAF9E488F63FF0F1A69EDD103760C47@ftrdmel1.rd.francetelecom.fr> |
Dear Dan and Ron, OPSAWG charter includes: > (B) Templates and tools for Operations and Management Area Documents I enhanced XSL part of draft-stephan-ops-xml-mib-module-template. The = last version transforms a RFC2629-based XML MIB draft in a XML schema = directly under Mozilla. I think it's a good starting point for working on an update of RFC2629 = leading to a common document format for specifying datamodels. Regards Emile -----Message d'origine----- De=A0: Romascanu, Dan (Dan) [mailto:[email protected]]=20 Envoy=E9=A0: jeudi 10 mai 2007 21:02 =C0=A0: Ron Bonica; [email protected]; [email protected] Objet=A0: [OPS-AREA] RE: [OPS-NM] OPS Area WG 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.=20 Dan and Ron =20 =20 > -----Original Message----- > From: Ron Bonica [mailto:[email protected]]=20 > Sent: Thursday, May 10, 2007 9:38 PM > To: [email protected]; [email protected] > Subject: [OPS-NM] OPS Area WG >=20 > Folks, >=20 > Dan and I would like to propose an area-wide working group=20 > whose charter is reflected below. Please read and comment=20 > upon the proposed charter. >=20 > Dan and Ron >=20 > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Operations and Management Area Working Group (opsawg) >=20 > Chair(s): >=20 > TBD > TBD >=20 > Area Directors: >=20 > Dan Romascanu <[email protected]> > Ronald Bonica <[email protected]> >=20 >=20 > The Operations and Management Area receives occasional=20 > proposals for the development and publication of RFCs dealing=20 > with operational and management topics that are not in scope=20 > of an existing working group or do not justify the formation=20 > of a new working group. The OPSAWG will serve as the forum=20 > for developing such work items in the IETF. >=20 > The OPSAWG mailing list is an open discussion forum for such=20 > work items, when they arise. The working group meets if there=20 > are active proposals that require discussion. The working=20 > group milestones are updated as needed to reflect the current=20 > work items and their associated milestones. All new work=20 > items and rechartering proposals will be brought for approval=20 > with the IESG. >=20 > The focus of the work will be on topics that govern the=20 > behavior or WGs in the O&M area (e.g., manageability > requirements) and on small, highly focused projects that=20 > don't merit a WG of their own or belong to WGs that have=20 > already concluded (e.g. > advancement of documents on the standards track, application=20 > statements, extensions of MIB modules). >=20 > The OPSAWG will undertake only work items that are proved to=20 > have at least a reasonable level of interest from the=20 > operators and users community and have a committed number of=20 > editors and reviewers. It is not within the scope of the=20 > OPSAWG to pick up failed WG work or parts of a WG charter=20 > items that could not come to convergence on what they were=20 > chartered to do. >=20 > The currently active OPSAWG work items mostly fall under the following > topics: >=20 > (A) Development of a BCP document that will provide=20 > guidelines for operational and manageability requirements=20 > that need to be covered in IETF documents, especially those=20 > documents that include requirements and specification of new=20 > protocols or protocol extensions. >=20 > (B) Templates and tools for Operations and Management Area Documents >=20 > (C) Maintenance and extensions of documents that define MIB=20 > modules which were developped in working groups that have concluded. >=20 > Goals and Milestones: >=20 > June 2007 - Initial submission for the Guidelines for=20 > Considering Operations and Management of New Protocols Internet-Draft >=20 > October 2007 - Initial submission for the Template for=20 > Generic Management Data Models >=20 > October 2007 - Initial submission for the Structured Data Elements > (SDEs) for syslog >=20 > December 2007 - WGLC for the Guidelines for Considering=20 > Operations and Management of New Protocols Internet-Draft >=20 > February 2008 - Submit the Guidelines for Considering=20 > Operations and Management of New Protocols Internet-Draft to=20 > the IESG for consideration as BCP >=20 > April 2008 - WGLC for the Template for Generic Management Data Models >=20 > April 2008 - WGLC for the Structured Data Elements > (SDEs) for syslog >=20 > June 2008 - Submit the Template for Generic Management Data=20 > Models to the IESG for consideration as BCP >=20 > June 2008 - Submit the Structured Data Elements > (SDEs) for syslog to the IESG for consideration as Proposed Standard >=20 >=20 > _______________________________________________ > OPS-NM mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/ops-nm >=20 _______________________________________________ OPS-AREA mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ops-area _______________________________________________ OPS-AREA mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ops-area