RE: 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
>