Re: [Bridge-mib] Future directions

Elisabeth Gloria <green_elisabeth@yahoo.com.au> Thu, 01 April 2004 07:46 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23970 for <bridge-archive@odin.ietf.org>; Thu, 1 Apr 2004 02:46:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8wtn-0001m2-7M for bridge-archive@odin.ietf.org; Thu, 01 Apr 2004 02:46:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i317k3l4006809 for bridge-archive@odin.ietf.org; Thu, 1 Apr 2004 02:46:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8wtl-0001lS-HW; Thu, 01 Apr 2004 02:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8wt9-0001jd-3A for bridge-mib@optimus.ietf.org; Thu, 01 Apr 2004 02:45:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23913 for <bridge-mib@ietf.org>; Thu, 1 Apr 2004 02:45:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B8wt5-0004YN-00 for bridge-mib@ietf.org; Thu, 01 Apr 2004 02:45:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B8ws5-0004Rv-00 for bridge-mib@ietf.org; Thu, 01 Apr 2004 02:44:17 -0500
Received: from web13125.mail.yahoo.com ([216.136.174.143]) by ietf-mx with smtp (Exim 4.12) id 1B8wrV-0004LW-00 for Bridge-mib@ietf.org; Thu, 01 Apr 2004 02:43:41 -0500
Message-ID: <20040401074342.51062.qmail@web13125.mail.yahoo.com>
Received: from [194.90.136.135] by web13125.mail.yahoo.com via HTTP; Thu, 01 Apr 2004 17:43:42 EST
Date: Thu, 1 Apr 2004 17:43:42 +1000 (EST)
From: =?iso-8859-1?q?Elisabeth=20Gloria?= <green_elisabeth@yahoo.com.au>
Subject: Re: [Bridge-mib] Future directions
To: "Harrington, David" <dbh@enterasys.com>, Bridge-mib@ietf.org
In-Reply-To: <6D745637A7E0F94DA070743C55CDA9BA017E1113@NHROCMBX1.ets.enterasys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 8bit
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

David,

I my opinion (while I am not a member of WG):

> 1) Do you agree with having the IEEE write
> their own mibs?
Yes, I do.
 
> 2) Will you participate in the IEEE 802.1
> process for developing the mib modules?
Yes, I will as far as I can.

> 3) Do you agree the bridgemib WG should be
> closed down, since it will
> have completed its charter?
No, I wouldn't like, see next item. 

> 4) Should they also be published as RFCs?
Yes, they should.

> 5) Synchronization between IEEE/IETF
> review/publishing cycles has proven
> difficult, so we are considering publishing
> Informational RFCs with only
> a pointer to the IEEE standard. Would that
> suffice?
Yes, it would.

> For existing 802.1-related MIBs (1493, 1525, 2674,
> et al):
> 6) Should these be moved to the IEEE?
Not, it is not necessarily.

> 7) If not, why not? How should the IETF mib modules
> be maintained as the
> IEEE 802.1 technologies change?
These MIBs should be made obsolete by new ones.

Regards, Beth


Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com

_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib