Subject: RE: [Bridge-mib] RE: VLAn ID

From: "Wijnen, Bert (Bert)" <[email-masked]>
Date: Thu, 14 Aug 2003 23:34:32 +0200

So... what do we do for a common (or a few) common TCs.
Anyone wants to write a I-D for it?

It seems like we would define the VlanIDOrAny as (0..4095)
now and make 4095 mean "wildcard"

There is another MIB coming up in the IPCDN WG that wants
to define a VlanIDOrAny (not a TC, but the concetp) for
one of their objects. If we could give them guidance on 
what to do (soon), that would be great.

Thanks,
Bert 

> -----Original Message-----
> From: Les Bell [mailto:[email-masked]]
> Sent: dinsdag 10 juni 2003 12:10
> To: C. M. Heard
> Cc: Tony Jeffree; MIBs (E-mail); Bridge-Mib (E-mail)
> Subject: Re: [Bridge-mib] RE: VLAn ID
> 
> 
> 
> 
> 
> I agree that no changes are required to clause 12 of 802.1Q.
> 
> Les...
> 
> 
> 
> 
> 
> "C. M. Heard" <[email-masked]>@ietf.org on 07/06/2003 04:07:22
> 
> Sent by:  [email-masked]
> 
> 
> To:   Tony Jeffree <[email-masked]>
> 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
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/bridge-mib
> 
> 
> 
> 
> 

_______________________________________________
Bridge-mib mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/bridge-mib