[Bridge-mib] VLAN-ID
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Wed, 19 February 2003 15:12 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27630 for <bridge-archive@odin.ietf.org>; Wed, 19 Feb 2003 10:12:29 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1JFIbn18090 for bridge-archive@odin.ietf.org; Wed, 19 Feb 2003 10:18:37 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JFITp18071; Wed, 19 Feb 2003 10:18:29 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1JFH8p17933 for <bridge-mib@optimus.ietf.org>; Wed, 19 Feb 2003 10:17:08 -0500
Received: from hoemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27548 for <bridge-mib@ietf.org>; Wed, 19 Feb 2003 10:10:29 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1JFECc23423 for <bridge-mib@ietf.org>; Wed, 19 Feb 2003 10:14:13 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <DVZNZNQP>; Wed, 19 Feb 2003 16:14:12 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155F7C06C@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: bridge-mib@ietf.org
Date: Wed, 19 Feb 2003 16:14:04 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Bridge-mib] VLAN-ID
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>
Bridgemibbers.... I do not see much (if any activity lately) :-( But I have a question. I see a VLAN ID represented in various forms: - draft-ietf-bridge-ext-v2-01.txt VlanId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A 12-bit VLAN ID used in the VLAN Tag header." SYNTAX INTEGER (1..4094) - somehwere I found: dot1vProtocolPortGroupVid OBJECT-TYPE SYNTAX INTEGER (1..4094) MAX-ACCESS read-create STATUS current DESCRIPTION "The VID associated with a group of protocols for each port." REFERENCE "IEEE 802.1v clause 8.4.4, 12.10.1.2" - In a DOCSIS document I find: docsQosPktClassVlanId OBJECT-TYPE SYNTAX Integer32 (0..4095) MAX-ACCESS read-only STATUS current - In the framework PIB (draft-ietf-rap-frameworkpib-09.txt) I find: frwk802FilterVlanId OBJECT-TYPE SYNTAX Integer32 (-1 | 1..4094) STATUS current DESCRIPTION "The VLAN ID (VID) that uniquely identifies a VLAN within the device. This VLAN may be known or unknown (i.e., traffic associated with this VID has not yet been seen by the device) at the time this entry is instantiated. Setting the frwk802FilterVlanId object to -1 indicates that VLAN data should not be considered during traffic classification." - In rfc2613 I find: smonVlanIdStatsId OBJECT-TYPE SYNTAX Integer32 (1..4094) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The unique identifier of the VLAN monitored for this specific statistics collection. Tagged packets match the VID for the range between 1 and 4094. An external RMON probe MAY detect VID=0 on an Inter Switch Link, in which case the packet belongs to a VLAN determined by the PVID of the ingress port. The VLAN to which such a packet belongs can be determined only by a RMON probe internal to the switch." REFERENCE "Draft Standard for Virtual Bridged Local Area Networks, P802.1Q/D10, chapter 3.13" - In RFC2674 I find: 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 - IN RFC2674 I also find VlanId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A 12-bit VLAN ID used in the VLAN Tag header." SYNTAX INTEGER (1..4094) Not sure I found all occurances. So my question is: what is the CORRECT spec, and could we try to define one (or a few) TC(s) that everyone else can IMPORT and use. Bert _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib
- RE: [Bridge-mib] VLAN-ID Wijnen, Bert (Bert)
- [Bridge-mib] VLAN-ID Wijnen, Bert (Bert)
- RE: [Bridge-mib] VLAN-ID Romascanu, Dan (Dan)
- RE: [Bridge-mib] VLAN-ID Romascanu, Dan (Dan)
- Re: [Bridge-mib] VLAN-ID Mike MacFaden
- RE: [Bridge-mib] VLAN-ID Andrew Smith
- RE: [Bridge-mib] VLAN-ID Eduardo Cardona
- RE: [Bridge-mib] VLAN-ID Eduardo Cardona
- RE: [Bridge-mib] VLAN-ID Wijnen, Bert (Bert)
- RE: [Bridge-mib] VLAN-ID Les Bell
- Re: [Bridge-mib] VLAN-ID Randy Presuhn
- RE: [Bridge-mib] VLAN-ID Les Bell
- Re: [Bridge-mib] VLAN-ID Les Bell
- RE: [Bridge-mib] VLAN-ID Wijnen, Bert (Bert)
- Re: [Bridge-mib] VLAN-ID Tom Petch
- Re: [Bridge-mib] VLAN-ID Tom Petch