WG Review: Operations and Management Area Working Group (opsawg)

The IESG <iesg-secretary@ietf.org> Tue, 02 October 2012 16:08 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2496121F844A for <ietf-announce@ietfa.amsl.com>; Tue, 2 Oct 2012 09:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id NS5lZla0aVdP for <ietf-announce@ietfa.amsl.com>; Tue, 2 Oct 2012 09:08:41 -0700 (PDT)
Received: from ietfa.amsl.com (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6901421F843F for <ietf-announce@ietf.org>; Tue, 2 Oct 2012 09:08:41 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: Operations and Management Area Working Group (opsawg)
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121002160841.15638.53423.idtracker@ietfa.amsl.com>
Date: Tue, 02 Oct 2012 09:08:41 -0700
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Oct 2012 16:08:42 -0000

The Operations and Management Area Working Group (opsawg) working group
in the Operations and Management Area of the IETF is undergoing
rechartering. The IESG has not made any determination yet. The following
draft charter was submitted, and is provided for informational purposes
only. Please send your comments to the IESG mailing list (iesg at
ietf.org) by 2012-10-09.

Operations and Management Area Working Group (opsawg)
Current Status: Active Working Group

  Scott Bradner <sob@harvard.edu>
  Chris Liljenstolpe <christopher.liljenstolpe@bigswitch.com>
  Melinda Shore <melinda.shore@gmail.com>

Assigned Area Director:
  Ronald Bonica <rbonica@juniper.net>

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

Charter 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 
  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
  (A) Templates and tools for Operations and Management Area Documents
  (B) Maintenance and small scale extensions of documents that were
  developed in working groups that have concluded (e.g. MIB modules).

  (C) The RFC 5066 "Ethernet in the First Mile Copper (EFMCu) Interfaces 
  MIB" has transitioned to the IEEE 802.3. However, as agreed with the 
  IEEE, the IF-CAP-STACK-MIB MIB module (from RFC5066) is generic by 
  nature and should continue to be supported by the IETF. The WG will 
  develop a document extracting the IF-CAP-STACK-MIB from RFC5066, 
  emphasizing the generic nature of this module, and obsolete RFC5066.

   (D) Documenting the list of RFCs transitioned to the IEEE 
   802.3.1-2011. Considering RFC 4663 "Transferring MIB Work from IETF 
   Bridge MIB WG to IEEE 802.1 WG" as an reference, the following pieces 
   of information would the foundation for the document: a table mapping 
   the old IETF MIB names with the corresponding new IEEE ones, 
   clarifications/rules on the IETF-IEEE interactions (mailing lists, 
   reviews), and clarifications on the intellectual property 

Goals and Milestones
Oct 2012     Initial submission for the 'IF-CAP-STACK-MIB MIB module' 
Oct 2012     Initial submission for the 'RFCs transitioned to the IEEE 
             802.3.1-2011' Internet-Draft
March  2013  Submit the 'IF-CAP-STACK-MIB MIB module' Internet-Draft
             to the IESG for consideration as Proposed Standard
March  2013  Submit the 'RFCs transitioned to the IEEE 802.3.1-2011'
             Internet-Draft to the IESG for consideration as