Re: [Bridge-mib] draft-ietf-ops-vlanid-tc-mib-00.txt
Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Tue, 05 October 2004 22:57 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 SAA21008 for <bridge-mib-archive@ietf.org>; Tue, 5 Oct 2004 18:57:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEyPF-0003Su-I8 for bridge-mib-archive@ietf.org; Tue, 05 Oct 2004 19:07:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEyBX-0000KO-PK; Tue, 05 Oct 2004 18:53:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEy78-00082j-0J for bridge-mib@megatron.ietf.org; Tue, 05 Oct 2004 18:48:58 -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 SAA20106 for <bridge-mib@ietf.org>; Tue, 5 Oct 2004 18:48:55 -0400 (EDT)
Received: from hermes.iu-bremen.de ([212.201.44.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEyGV-00023e-0O for bridge-mib@ietf.org; Tue, 05 Oct 2004 18:58:39 -0400
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32]) by hermes.iu-bremen.de (Postfix) with ESMTP id 1AC2B998E; Wed, 6 Oct 2004 00:48:25 +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 05387-07; Wed, 6 Oct 2004 00:48:24 +0200 (CEST)
Received: from james (G503b.g.pppool.de [80.185.80.59]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by hermes.iu-bremen.de (Postfix) with ESMTP id DAA35992C; Wed, 6 Oct 2004 00:48:23 +0200 (CEST)
Received: from schoenw by james with local (Exim 4.34) id 1CEy6b-0000fr-Qb; Wed, 06 Oct 2004 00:48:25 +0200
Date: Wed, 06 Oct 2004 00:48:25 +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: <20041005224825.GA2498@james>
Mail-Followup-To: David B Harrington <dbharrington@comcast.net>, bridge-mib@ietf.org
References: <200409301230.IAA15316@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200409301230.IAA15316@ietf.org>
User-Agent: Mutt/1.5.6+20040722i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 2.9 (++)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
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: 2.9 (++)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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