[Hubmib] Possible 802.3 MIB work in IEEE 802.3

"Bert Wijnen \(IETF\)" <bertietf@bwijnen.net> Mon, 15 September 2008 15:30 UTC

Return-Path: <hubmib-bounces@ietf.org>
X-Original-To: hubmib-archive@megatron.ietf.org
Delivered-To: ietfarch-hubmib-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99A603A68B4; Mon, 15 Sep 2008 08:30:11 -0700 (PDT)
X-Original-To: hubmib@core3.amsl.com
Delivered-To: hubmib@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B72EC3A6A97 for <hubmib@core3.amsl.com>; Mon, 15 Sep 2008 02:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yq1Y+hvsjxey for <hubmib@core3.amsl.com>; Mon, 15 Sep 2008 02:01:56 -0700 (PDT)
Received: from relay.versatel.net (relay.versatel.net [62.250.3.110]) by core3.amsl.com (Postfix) with SMTP id 53BBA3A63D2 for <hubmib@ietf.org>; Mon, 15 Sep 2008 02:01:52 -0700 (PDT)
Received: (qmail 62405 invoked from network); 15 Sep 2008 09:02:00 -0000
Received: from unknown (HELO BertLaptop) (87.215.199.34) by relay.versatel.net with SMTP; 15 Sep 2008 09:02:00 -0000
Message-ID: <BE145F80CAC746B7BCE60F7E7D0594AE@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: <hubmib@ietf.org>
Date: Mon, 15 Sep 2008 11:01:26 +0200
Organization: Consultant
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_090F_01C91722.65FAC530"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
X-Mailman-Approved-At: Mon, 15 Sep 2008 08:30:11 -0700
Cc: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>
Subject: [Hubmib] Possible 802.3 MIB work in IEEE 802.3
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/hubmib>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

HUBMIB WG members and MIB doctors.
 
Well, we all know the HUBMIB WG is closed.
Nevertheless, I thik it is good for you all to be aware of this
activity in IEEE 802.3.
 
It looks like any new MIB work in this space may indeed be
taken up by IEEE 802.3, similar as the BRIDGE-MIB work
was picked up a few years back by the IEEE 802.1

Bert Wijnen
old (indeed) WG chair of the (closed) HUBMIB WG.
 
> ----- Original Message ----- 
> From: "Howard Frazier" <hfrazier@BROADCOM.COM>
> To: <STDS-802-3-MAINT@LISTSERV.IEEE.ORG>
> Sent: Monday, September 15, 2008 5:49 AM
> Subject: [802.3_MAINT] draft PAR and 5 Critters for P802.3.1
> 
> 
> 
> Dear IEEE 802.3 maintenance task force members,
> 
> attached please find draft text for a PAR and the 5 criteria
> responses for a new project, P802.3.1, to create a standard
> for Ethernet MIB modules.  I am circulating the draft text
> to this reflector for discussion at our meeting in Seoul.
> 
> Howard Frazier
> Broadcom Corporation
>
_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www.ietf.org/mailman/listinfo/hubmib