Re: [Bridge-mib] RE: VLAn ID

"Les Bell" <Les_Bell@eur.3com.com> Tue, 10 June 2003 10:13 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 GAA19132 for <bridge-archive@odin.ietf.org>; Tue, 10 Jun 2003 06:13:40 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5AADGp05416 for bridge-archive@odin.ietf.org; Tue, 10 Jun 2003 06:13:16 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AAD5B05408; Tue, 10 Jun 2003 06:13:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AAAZB05293 for <bridge-mib@optimus.ietf.org>; Tue, 10 Jun 2003 06:10:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19113 for <bridge-mib@ietf.org>; Tue, 10 Jun 2003 06:10:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Pg3I-0003Qt-00 for bridge-mib@ietf.org; Tue, 10 Jun 2003 06:08:29 -0400
Received: from ip-161-71-171-238.corp-eur.3com.com ([161.71.171.238] helo=columba.www.eur.3com.com) by ietf-mx with esmtp (Exim 4.12) id 19Pg3I-0003Qq-00 for bridge-mib@ietf.org; Tue, 10 Jun 2003 06:08:28 -0400
Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id h5AABjfO007018; Tue, 10 Jun 2003 11:11:46 +0100 (BST)
Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id h5AAC9M07054; Tue, 10 Jun 2003 11:12:09 +0100 (BST)
Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256D41.0037F3D5 ; Tue, 10 Jun 2003 11:11:09 +0100
X-Lotus-FromDomain: 3COM
From: "Les Bell" <Les_Bell@eur.3com.com>
To: "C. M. Heard" <heard@pobox.com>
cc: Tony Jeffree <tony@jeffree.co.uk>, "MIBs (E-mail)" <mibs@ops.ietf.org>, "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Message-ID: <80256D41.0037F1BF.00@notesmta.eur.3com.com>
Date: Tue, 10 Jun 2003 11:10:06 +0100
Subject: Re: [Bridge-mib] RE: VLAn ID
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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>



I agree that no changes are required to clause 12 of 802.1Q.

Les...





"C. M. Heard" <heard@pobox.com>@ietf.org on 07/06/2003 04:07:22

Sent by:  bridge-mib-admin@ietf.org


To:   Tony Jeffree <tony@jeffree.co.uk>
cc:   "MIBs , "Bridge-Mib
Subject:  [Bridge-mib] RE: VLAn ID


On Fri, 6 Jun 2003, in a message forwarded by Bert Wijnen,
Tony Jeffree wrote:
> We have concluded that the use of 4095 as a wildcard is
> acceptable to 802.1, and we will make any necessary changes to
> 802.1Q in due course to relax the current stated restriction.
> However, we need to know whether that is all that needs to be
> done to 802.1Q - i.e., is there any need to change our
> definitions of the managed objects in the document (Clause 12)
> to reflect the interpretation of 4095 as a wildcard, or is this
> simply an issue for the SNMP machinery to handle?

After a quick look at 802.1Q-1998, 802.1u-2001, and 802.1v-2001 it
appears to me that no changes are required to clause 12 of 802.1Q.

Can any Bridge-Mib folk confirm that?

//cmh

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




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