IETF Logo Mail Archive

Re: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t

"Tom Petch" <nwnetworks@dial.pipex.com> Mon, 05 January 2004 20:32 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02204 for <bridge-archive@odin.ietf.org>; Mon, 5 Jan 2004 15:32:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdbON-0002fp-7m for bridge-archive@odin.ietf.org; Mon, 05 Jan 2004 15:32:03 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i05KW2DZ010270 for bridge-archive@odin.ietf.org; Mon, 5 Jan 2004 15:32:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdbOM-0002fV-Em; Mon, 05 Jan 2004 15:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdbO9-0002eB-BN for bridge-mib@optimus.ietf.org; Mon, 05 Jan 2004 15:31:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02131 for <bridge-mib@ietf.org>; Mon, 5 Jan 2004 15:31:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AdbO7-0003tD-00 for bridge-mib@ietf.org; Mon, 05 Jan 2004 15:31:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AdbMl-0003ll-00 for bridge-mib@ietf.org; Mon, 05 Jan 2004 15:30:23 -0500
Received: from shockwave.systems.pipex.net ([62.241.160.9]) by ietf-mx with esmtp (Exim 4.12) id 1AdbKG-0003ZF-00 for bridge-mib@ietf.org; Mon, 05 Jan 2004 15:27:48 -0500
Received: from tom3 (1Cust120.tnt7.lnd1.gbr.da.uu.net [62.188.24.120]) by shockwave.systems.pipex.net (Postfix) with SMTP id 4FB291C002E5; Mon, 5 Jan 2004 20:26:35 +0000 (GMT)
Message-ID: <001a01c3d3ca$2902a6c0$0301a8c0@tom3>
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
From: Tom Petch <nwnetworks@dial.pipex.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
Subject: Re: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t
Date: Mon, 05 Jan 2004 20:25:29 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

I did say overload:-)  DateAndTime I think a good choice of name, quite
short (11 characters) no abbreviations, well known words that are unlikely
to be misspelt or misremembered.  It does not, for example, try to convey
its particular characteristics, such as the accuracy in seconds or the
presentation of the year (which is what distinguishes it from similar TCs).

VlanIdOrNoneOrAny? rather long to always get right; on my Windows client,
the l of Vlan is the same as the I of Id; repetition of Or another
opportunity to get confused; other similar TCs (in Disman) have OrZero as
opposed to OrNone (which is better English IMO)

I respond because I do think this non-technical issue matters, that it is a
sometimes serious mistake when people invent names, making the name
difficult to read and write, say and hear, leading to errors and
misunderstandings, perhaps thinking they will be unable to remember what it
means, which with time is actually the easy part.

Tom Petch
-----Original Message-----
From: Wijnen, Bert (Bert) <bwijnen@lucent.com>
To: Tom Petch <nwnetworks@dial.pipex.com>; Bridge-Mib (E-mail)
<bridge-mib@ietf.org>
Date: 04 January 2004 10:46
Subject: RE: [Bridge-mib] FW: Please review and comment:
draft-ietf-ops-vlanid-tc-mib-00.tx t


>Inline
>
>> -----Original Message-----
>> From: Tom Petch [mailto:nwnetworks@dial.pipex.com]
>> Sent: vrijdag 2 januari 2004 12:32
>> To: Wijnen, Bert (Bert); Bridge-Mib (E-mail)
>> Subject: Re: [Bridge-mib] FW: Please review and comment:
>> draft-ietf-ops-vlanid-tc-mib-00.tx t
>>
>> No thoughts on whether the TC should exist or no.
>>
>> But if it does, then keep the name simple, don't overload the
>> name, the identifier, with a description of the semantics
>>
>MMm... if we look at for example DateAndTime TC, does that not give
>similar semantics in the name? I am sure there are many others
>that do so too.
>
>> ie VlanIdentifier VlanIds VlanId2 .. good
>> VlanIdOrNone VlanIdOrNoneOrAny VlanIdAssociation   .. bad
>>
>Bert
>> Tom Petch


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

v2.23.0 | Report a Bug | By Email