RE: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vl anid-tc-mib-00.tx t

Bert,

As I've said before, I think that's a backwards step. There's no point
in having the TC either (a) if you have to still refine its
definition/semantics in the DESCRIPTION of any object that uses it, or
(b) if the name represents syntax, not semantics 

(I don't care how many other TCs people have already defined called
"...OrZero" - that does not make them good - if only the syntax is
common between various uses of such a TC, without there being common
semantics, again I think the TC does not deserve to exist).

Sorry for the repetitiocity - this argument does seem to be going around
in non-diminishing circles.

Andrew

-----Original Message-----
From: bridge-mib-admin@ietf.org [mailto:bridge-mib-admin@ietf.org] On
Behalf Of Wijnen, Bert (Bert)
Sent: Sunday, February 15, 2004 3:04 PM
To: 'Juergen Schoenwaelder'; Wijnen, Bert (Bert)
Cc: bridge-mib@ietf.org
Subject: RE: [Bridge-mib] FW: Please review and comment:
draft-ietf-ops-vl anid-tc-mib-00.tx t

> I think Tom was more pointing into the direction of
> InterfaceIndexOrZero where Zero basically indicates that there is a
> special value but its semantics must be specified in the description
> of the object using that TC. If you are very precise how the special
> value (or values) are going to be used, then you will end up with
> many TCs.
> 
So would yopu prefer that instead of:

   VlanIdentifierOrNone  ::= TEXTUAL-CONVENTION
       DISPLAY-HINT     "d"
       STATUS            current
       DESCRIPTION      "The VLAN ID that uniquely identifies a VLAN.

                         The special value of zero is used to indicate
                         that no VLAN ID is present or used.  
                        "
       SYNTAX            Integer32 (0 | 1..4094) 

I do a different descriptor and DESCRIPTION, something like:

   VlanIdentifierOrZero  ::= TEXTUAL-CONVENTION
       DISPLAY-HINT     "d"
       STATUS            current
       DESCRIPTION      "The VLAN ID that uniquely identifies a VLAN.

                         The special value of zero is object-specific
                         and must therefore be defined as part of the
                         description of any object which uses this
syntax.
                         Examples of the usage of zero might include
                         situations where VLAN ID is unknown, where a
                         VLAN ID is not present, or where none or any
                         VLAN ID need to be specified."
                        "
       SYNTAX            Integer32 (0 | 1..4094) 

And then possibly do away with the VlanIdentifierOrAny?

Bert

_______________________________________________
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