RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt
"David B Harrington" <dbharrington@comcast.net> Wed, 06 October 2004 04:59 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 AAA19628 for <bridge-mib-archive@ietf.org>; Wed, 6 Oct 2004 00:59:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF43X-00057d-Jn for bridge-mib-archive@ietf.org; Wed, 06 Oct 2004 01:09:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF3t3-0008UM-DY; Wed, 06 Oct 2004 00:58:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CF3sQ-0008Mg-73 for bridge-mib@megatron.ietf.org; Wed, 06 Oct 2004 00:58:10 -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 AAA19552 for <bridge-mib@ietf.org>; Wed, 6 Oct 2004 00:58:07 -0400 (EDT)
Message-Id: <200410060458.AAA19552@ietf.org>
Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CF41q-00054J-P5 for bridge-mib@ietf.org; Wed, 06 Oct 2004 01:07:55 -0400
Received: from djyxpy41 (h00104b8ce2a3.ne.client2.attbi.com[24.128.104.220]) by comcast.net (rwcrmhc12) with SMTP id <2004100604573701400rfmm0e>; Wed, 6 Oct 2004 04:57:38 +0000
From: David B Harrington <dbharrington@comcast.net>
To: j.schoenwaelder@iu-bremen.de
Subject: RE: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt
Date: Wed, 06 Oct 2004 00:57:37 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <20041005224825.GA2498@james>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-Index: AcSrLWzFtcsHeA0gSHOY4UxEjDJ96gALDmtw
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: 7bit
Cc: bridge-mib@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dbharrington@comcast.net
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.9 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: 7bit
Hi Juergen, 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. RFC2674bis (draft-ietf-bridge-ext-v2-02.txt) has been a product of this WG, but the draft expired in August. We expect to have a revision published before IETF61, possibly with TCs and usage guidelines included. David Harrington dbharrington@comcast.net Bridge-mib co-chair -----Original Message----- From: Juergen Schoenwaelder [mailto:schoenw@iu-bremen.de] On Behalf Of Juergen Schoenwaelder Sent: Tuesday, October 05, 2004 6:48 PM To: David B Harrington Cc: bridge-mib@ietf.org Subject: Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt On Thu, Sep 30, 2004 at 08:29:52AM -0400, David B Harrington wrote: > Hi, > > draft-ietf-ops-vlanid-tc-mib-00.txt has been submitted to for > publication as an I-D. > Please review this document and comment. > > If you read it and find nothing to which you strongly object, please > say so. If you have concerns about the content, or find typos or > grammar errors, please say so. In RFC 2674, I read the following: VlanIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A value used to index per-VLAN tables: values of 0 and 4095 are not permitted; if the value is between 1 and 4094 inclusive, it represents an IEEE 802.1Q VLAN-ID with global scope within a given bridged domain (see VlanId textual convention). If the value is greater than 4095 then it represents a VLAN with scope local to the particular agent, i.e. one without a global VLAN-ID assigned to it. Such VLANs are outside the scope of IEEE 802.1Q but it is convenient to be able to manage them in the same way using this MIB." SYNTAX Unsigned32 Note the language about values greater than 4095. The VLAN-ID-MIB defines things such as: VlanIdentifier ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The VLAN ID that uniquely identifies a VLAN. It is the 12-bit VLAN ID used in the VLAN Tag header. The range is defined by the REFERENCEd specification. " REFERENCE "IEEE Std 802.1Q 2003 Edition, Virtual Bridged Local Area Networks. " SYNTAX Integer32 (1..4094) I think we need to speel out guidelines in which situations which TC should be used and why. As it stands, it is kind of confusing for me as an outsider. How are those local scope VLAN IDs used in practice? (I don't think they fit into tagged frames.) > Should this be a separate document, or should it be merged into > rfc2674bis? Please indicate your preference when commenting on the draft. Is there actually a plan to revise RFC 2674? /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