Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt
Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Wed, 06 October 2004 06:49 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24099 for <bridge-mib-archive@ietf.org>; Wed, 6 Oct 2004 02:49:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF5lB-0001pG-Ve for bridge-mib-archive@ietf.org; Wed, 06 Oct 2004 02:58:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF5as-0005p2-8E; Wed, 06 Oct 2004 02:48:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF5a1-0005is-AQ for bridge-mib@megatron.ietf.org; Wed, 06 Oct 2004 02:47:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24042 for <bridge-mib@ietf.org>; Wed, 6 Oct 2004 02:47:15 -0400 (EDT)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF5jR-0001le-B3 for bridge-mib@ietf.org; Wed, 06 Oct 2004 02:57:03 -0400
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 95DC899CB; Wed, 6 Oct 2004 08:46:43 +0200 (CEST)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by localhost (demetrius [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 24004-08; Wed, 6 Oct 2004 08:46:42 +0200 (CEST)
Received: from james (unknown [212.201.46.187]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id 81620992C; Wed, 6 Oct 2004 08:46:42 +0200 (CEST)
Received: from schoenw by james with local (Exim 4.34) id 1CF5ZS-0000Wq-7L; Wed, 06 Oct 2004 08:46:42 +0200
Date: Wed, 06 Oct 2004 08:46:41 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: David B Harrington <dbharrington@comcast.net>
Subject: Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt
Message-ID: <20041006064641.GB1745@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>, bridge-mib@ietf.org
References: <20041005224825.GA2498@james> <20041006045739.7186698D3@hermes.iu-bremen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20041006045739.7186698D3@hermes.iu-bremen.de>
User-Agent: Mutt/1.5.6+20040722i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: bridge-mib.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
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>
Sender: bridge-mib-bounces@ietf.org
Errors-To: bridge-mib-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
On Wed, Oct 06, 2004 at 12:57:37AM -0400, David B Harrington wrote: > Some vendors use 0 as "no vlan" and some use 0 as a wildcard. I > believe other values are used for other local proprietary purposes. > There has been debate about whether the TCs should permit the mib > module designer to define special semantics per object, or whether the > values should be standardized. > > I agree some guidelines for usage should be provided. > > Personally, I think it would be good to standardize the local vlan IDs > for use in management, otherwise a manager application would need to > know whether it was a box from vendor-A or vendor-B, or which mib > module it is used in, to understand the semantics and present the info > in a user-friendly manner. Well, my concern was about value > 4095 which RFC 2674 explicitely permits in the VlanIndex TC but not in the VlanId TC and Bert's MIB module does not discuss this either. In principle, if RFC 2674 is indeed revised in due time, I think putting the VLAN TCs in an update of the Q-BRIDGE-MIB probably not a bad thing. But even then it needs to be spelled out clearly which TC should be used in which situation. However, if the Q-BRIDGE-MIB update ends up taking years to be finalized, then going forward with Bert's ID might be easier. /js -- Juergen Schoenwaelder International University Bremen <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib
- [Bridge-mib] RE: draft-ietf-ops-vlanid-tc-mib-00.… Wijnen, Bert (Bert)
- [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt David B Harrington
- Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.… Juergen Schoenwaelder
- RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.… David B Harrington
- Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.… Juergen Schoenwaelder
- RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.… David Levi