RE: VlanID and VlanIDOrAny

Bert,

It seems pointless to me to define a TC where any module that uses it
MUST (or even MAY) add special semantics to one or more of the values.
Why then bother defining the TC at all? We should either define what the
special "none" value is, including its semantics, in the TC definition
or else not define any such TC. I also don't think that the name
"...OrZero" is very helpful: the name should give a hint as to the
semantics, not the syntax, even for a TC name.

N.B. if what IPCDN wants to do is identify the "priority-tagged" frames
permitted by 802.1D/802.1Q (that is frames that carry user_priority
information but no relevant VLAN information) then that should be
handled in one of 2 ways: (a) add 0 as a valid value for VlanId or
VlanIdOrAny or (b) define separate VlanIdOrPriorityOnly and/or
VlanIdOrAnyOrPriorityOnly TCs with ranges (0 | 1..4094) and/or (0 |
1..4094 | 4095) respectively [but I thought in the bridge-mib list
discussions previously, we'd decided that there was no requirement for
the priority-tagged semantics, no?].

Andrew


-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Wijnen, Bert (Bert)
Sent: Sunday, September 07, 2003 11:14 AM
To: 'Romascanu, Dan (Dan)'; Bridge-Mib (E-mail)
Subject: RE: [Bridge-mib] VlanID and VlanIDOrAny


Not sure if they need it or not, but it would be to
indicate "wildcard", not "none"

Thanks,
Bert 

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:[email protected]]
> Sent: zondag 7 september 2003 10:55
> To: Wijnen, Bert (Bert); Bridge-Mib (E-mail)
> Subject: RE: [Bridge-mib] VlanID and VlanIDOrAny
> 
> 
> So, I guess that the IPCDN people do not need 4095. 
> 
> Otherwise, it looks OK to me. 
> 
> Dan
> 
> 
> > -----Original Message-----
> > From: Wijnen, Bert (Bert) [mailto:[email protected]]
> > Sent: 07 September, 2003 10:29 AM
> > To: Bridge-Mib (E-mail)
> > Subject: FW: [Bridge-mib] VlanID and VlanIDOrAny
> > 
> > 
> > It seems that in IPCDN, some people would like
> > to see yet another TC, namely:
> > 
> >     VlanIdOrZero      ::= TEXTUAL CONVENTION
> >         DISPLAY-HINT "d"
> >         STATUS        current
> >         DESCRIPTION  "The VLAN ID that uniquely identifies a VLAN.
> > 
> >                       The value zero is NOT a valid VLAN ID. 
> >                       
> >                       When this textual convention is used as the
> >                       syntax of an object, the object definition
> >                       MUST specify in the DESCRIPTION clause what
> >                       the value zero means.
> >                      "
> >         SYNTAX        Integer32 (0 | 1..4094)
> > 
> > Does anyone see a problem with that?
> > 
> > Thanks,
> > Bert 
> > 
> > -----Original Message-----
> > From: Wijnen, Bert (Bert) [mailto:[email protected]]
> > Sent: vrijdag 5 september 2003 0:48
> > To: Bridge-Mib (E-mail)
> > Subject: [Bridge-mib] VlanID and VlanIDOrAny
> > 
> > 
> > So... nobody has reacted to my request for
> > writeup. So I am preparing to do an ID myself.
> > 
> > This is what I think the discussion boiled down to.
> > 
> >     VlanId            ::= TEXTUAL CONVENTION
> >         DISPLAY-HINT "d"
> >         STATUS        current
> >         DESCRIPTION  "The VLAN ID that uniquely identifies a VLAN."
> >         SYNTAX        Integer32 (1..4094)
> > 
> > 
> >     VlanIdOrAny       ::= TEXTUAL CONVENTION
> >         DISPLAY-HINT "d"
> >         STATUS        current
> >         DESCRIPTION  "The VLAN ID that uniquely identifies a VLAN.
> >                       The value of 4095 is used to indicate a 
> > wildcard,
> >                       i.e. any value.
> >                      "
> >         SYNTAX        Integer32 (1..4094 | 4095)
> > 
> > Any comments?
> > 
> > Bert
> > 
> > _______________________________________________
> > Bridge-mib mailing list
> > [email protected]
> > https://www1.ietf.org/mailman/listinfo/bridge-mib
> > 
> > _______________________________________________
> > Bridge-mib mailing list
> > [email protected]
> > https://www1.ietf.org/mailman/listinfo/bridge-mib
> > 
> 

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