From exim@www1.ietf.org Thu Jan 1 03:58:33 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02048 for ; Thu, 1 Jan 2004 03:58:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbyeZ-0007nG-T1 for bridge-archive@odin.ietf.org; Thu, 01 Jan 2004 03:58:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i018w3S5029957 for bridge-archive@odin.ietf.org; Thu, 1 Jan 2004 03:58:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbyeX-0007mx-4G; Thu, 01 Jan 2004 03:58:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AbyeC-0007lp-7I for bridge-mib@optimus.ietf.org; Thu, 01 Jan 2004 03:57:40 -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 DAA02038 for ; Thu, 1 Jan 2004 03:57:38 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Abye9-0000cX-00 for bridge-mib@ietf.org; Thu, 01 Jan 2004 03:57:37 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AbycL-0000ZA-00 for bridge-mib@ietf.org; Thu, 01 Jan 2004 03:55:48 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1AbyaW-0000WV-00 for bridge-mib@ietf.org; Thu, 01 Jan 2004 03:53:52 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i018oikn010284 for ; Thu, 1 Jan 2004 03:50:44 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i018ogkn010263 for ; Thu, 1 Jan 2004 03:50:43 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t Date: Thu, 1 Jan 2004 10:53:49 +0200 Message-ID: Thread-Topic: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t Thread-Index: AcPPvyNfoWYfzctYTnifZm2lkcawrAAhWqGw From: "Romascanu, Dan (Dan)" To: "Wijnen, Bert (Bert)" , "Bridge-Mib (E-mail)" Content-Transfer-Encoding: quoted-printable 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable VlanIdAssociation is definitely a bad name - there are other 'VLAN = associations' it may be confused with.=20 Regards, Dan > -----Original Message----- > From: bridge-mib-admin@ietf.org=20 > [mailto:bridge-mib-admin@ietf.org]On Behalf Of Wijnen, Bert (Bert) > Sent: 31 December, 2003 6:52 PM > To: Bridge-Mib (E-mail) > Subject: [Bridge-mib] FW: Please review and comment:=20 > draft-ietf-ops-vlanid-tc-mib-00.tx t >=20 >=20 > Any comments? >=20 > Thanks, > Bert=20 >=20 > -----Original Message----- > From: Mark Ellison [mailto:ellison@ieee.org] > Sent: woensdag 31 december 2003 20:04 > To: Wijnen, Bert (Bert) > Cc: mibs@ops.ietf.org > Subject: Re: Please review and comment: > draft-ietf-ops-vlanid-tc-mib-00.tx t >=20 >=20 > Hi Bert, >=20 > Thanks for your reply.=20 >=20 > I think I'd call a TC with a value range of Integer32 { 0 | 1..4094 |=20 > 4095 } a VlanIdReference or VlanIdAssociation. >=20 > This TC would be useful when defining an object that refers=20 > to a vlan. =20 > For example, a table where each entry can be associated with=20 > none, one,=20 > or any vlan. One alternative, with the existing TCs, would be to use=20 > VlanIdOrAny, but have the agent return noSuchInstance when=20 > there is no=20 > association with a vlan. Another alternative, with the existing TCs,=20 > would be to use VlanIdOrNone, and not have use of the special=20 > any/4095=20 > value. >=20 > Regards, >=20 > Mark >=20 > Wijnen, Bert (Bert) wrote: >=20 > >Sorry for late reaction... but I am now again looking at=20 > >this document and the discussion that we had back in October. > > > >inline > > =20 > > > >>-----Original Message----- > >>From: Mark Ellison [mailto:ellison@ieee.org] > >>Sent: donderdag 2 oktober 2003 20:12 > >>To: Wijnen, Bert (Bert) > >>Cc: Mark Ellison; mibs@ops.ietf.org > >>Subject: Re: Please review and comment: > >>draft-ietf-ops-vlanid-tc-mib-00.txt > >> > >> > >>Hi Bert, > >> > >>I'm wondering if there could be any mib or pib definition=20 > requiring a=20 > >>range of ( 0 | 1..4094 | 4095 ) for possible values? > >> > >> =20 > >> > >Mark, I have not seen anyone react to this as a option that they > >wanted, so for now I am not going to include it. > >It can of course always be added later if a need arises. > > > >By the way, what woyuld you call/name that TC? > > > >Bert > > =20 > > > >>Regards, > >> > >>Mark > >> > >> > >> > >> =20 > >> > > > > =20 > > >=20 >=20 > _______________________________________________ > Bridge-mib mailing list > Bridge-mib@ietf.org > https://www1.ietf.org/mailman/listinfo/bridge-mib >=20 _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Thu Jan 1 06:22:30 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05375 for ; Thu, 1 Jan 2004 06:22:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ac0tu-0003ed-9x for bridge-archive@odin.ietf.org; Thu, 01 Jan 2004 06:22:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i01BM2kK014041 for bridge-archive@odin.ietf.org; Thu, 1 Jan 2004 06:22:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ac0tt-0003e6-Ip; Thu, 01 Jan 2004 06:22:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ac0tb-0003dI-Ke for bridge-mib@optimus.ietf.org; Thu, 01 Jan 2004 06:21:43 -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 GAA05350 for ; Thu, 1 Jan 2004 06:21:40 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ac0tX-0004Oz-00 for bridge-mib@ietf.org; Thu, 01 Jan 2004 06:21:39 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ac0rt-0004Lc-00 for bridge-mib@ietf.org; Thu, 01 Jan 2004 06:20:00 -0500 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1Ac0po-0004Gz-00 for bridge-mib@ietf.org; Thu, 01 Jan 2004 06:17:48 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id i01BGjC12060 for ; Thu, 1 Jan 2004 05:16:48 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Thu, 1 Jan 2004 12:16:44 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155033D2F3F@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "Romascanu, Dan (Dan)" , "Bridge-Mib (E-mail)" Subject: RE: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vl anid-tc-mib-00.tx t Date: Thu, 1 Jan 2004 12:16:43 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" 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: , List-Id: List-Post: List-Help: List-Subscribe: , OK, but do you think that the TC specified (none, a specific one, or any) is a usefull one to have? ANd if yes, would then VlanIdReference be a proper name? Or do you have better names suggestions in that case. Would VlanIdOrNoneOrAny be better? Thanks, Bert > -----Original Message----- > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > Sent: donderdag 1 januari 2004 9:54 > 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 > > > VlanIdAssociation is definitely a bad name - there are other > 'VLAN associations' it may be confused with. > > Regards, > > Dan > > > > > -----Original Message----- > > From: bridge-mib-admin@ietf.org > > [mailto:bridge-mib-admin@ietf.org]On Behalf Of Wijnen, Bert (Bert) > > Sent: 31 December, 2003 6:52 PM > > To: Bridge-Mib (E-mail) > > Subject: [Bridge-mib] FW: Please review and comment: > > draft-ietf-ops-vlanid-tc-mib-00.tx t > > > > > > Any comments? > > > > Thanks, > > Bert > > > > -----Original Message----- > > From: Mark Ellison [mailto:ellison@ieee.org] > > Sent: woensdag 31 december 2003 20:04 > > To: Wijnen, Bert (Bert) > > Cc: mibs@ops.ietf.org > > Subject: Re: Please review and comment: > > draft-ietf-ops-vlanid-tc-mib-00.tx t > > > > > > Hi Bert, > > > > Thanks for your reply. > > > > I think I'd call a TC with a value range of Integer32 { 0 | > 1..4094 | > > 4095 } a VlanIdReference or VlanIdAssociation. > > > > This TC would be useful when defining an object that refers > > to a vlan. > > For example, a table where each entry can be associated with > > none, one, > > or any vlan. One alternative, with the existing TCs, would > be to use > > VlanIdOrAny, but have the agent return noSuchInstance when > > there is no > > association with a vlan. Another alternative, with the > existing TCs, > > would be to use VlanIdOrNone, and not have use of the special > > any/4095 > > value. > > > > Regards, > > > > Mark > > > > Wijnen, Bert (Bert) wrote: > > > > >Sorry for late reaction... but I am now again looking at > > >this document and the discussion that we had back in October. > > > > > >inline > > > > > > > > >>-----Original Message----- > > >>From: Mark Ellison [mailto:ellison@ieee.org] > > >>Sent: donderdag 2 oktober 2003 20:12 > > >>To: Wijnen, Bert (Bert) > > >>Cc: Mark Ellison; mibs@ops.ietf.org > > >>Subject: Re: Please review and comment: > > >>draft-ietf-ops-vlanid-tc-mib-00.txt > > >> > > >> > > >>Hi Bert, > > >> > > >>I'm wondering if there could be any mib or pib definition > > requiring a > > >>range of ( 0 | 1..4094 | 4095 ) for possible values? > > >> > > >> > > >> > > >Mark, I have not seen anyone react to this as a option that they > > >wanted, so for now I am not going to include it. > > >It can of course always be added later if a need arises. > > > > > >By the way, what woyuld you call/name that TC? > > > > > >Bert > > > > > > > > >>Regards, > > >> > > >>Mark > > >> > > >> > > >> > > >> > > >> > > > > > > > > > > > > > > > _______________________________________________ > > 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 From exim@www1.ietf.org Fri Jan 2 07:16:32 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03700 for ; Fri, 2 Jan 2004 07:16: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 1AcODi-0005eX-WE for bridge-archive@odin.ietf.org; Fri, 02 Jan 2004 07:16:03 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i02CG2Z7021718 for bridge-archive@odin.ietf.org; Fri, 2 Jan 2004 07:16:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcODg-0005dp-Eu; Fri, 02 Jan 2004 07:16:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AcOCq-0005dK-95 for bridge-mib@optimus.ietf.org; Fri, 02 Jan 2004 07:15:08 -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 HAA03662 for ; Fri, 2 Jan 2004 07:14:59 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AcOCf-0002bO-00 for bridge-mib@ietf.org; Fri, 02 Jan 2004 07:14:57 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AcO8N-0002MZ-00 for bridge-mib@ietf.org; Fri, 02 Jan 2004 07:10:34 -0500 Received: from pengo.systems.pipex.net ([62.241.160.193]) by ietf-mx with esmtp (Exim 4.12) id 1AcNzf-0001yy-00 for bridge-mib@ietf.org; Fri, 02 Jan 2004 07:01:31 -0500 Received: from tom3 (1Cust31.tnt2.lnd4.gbr.da.uu.net [62.188.131.31]) by pengo.systems.pipex.net (Postfix) with SMTP id 9DD004C0021B; Fri, 2 Jan 2004 12:00:19 +0000 (GMT) Message-ID: <014c01c3d127$f23b2d00$0301a8c0@tom3> Reply-To: "Tom Petch" From: "Tom Petch" 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 Date: Fri, 2 Jan 2004 11:32:10 -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 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit 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 ie VlanIdentifier VlanIds VlanId2 .. good VlanIdOrNone VlanIdOrNoneOrAny VlanIdAssociation .. bad Tom Petch -----Original Message----- From: Wijnen, Bert (Bert) To: Romascanu, Dan (Dan) ; Bridge-Mib (E-mail) Date: 01 January 2004 11:22 Subject: RE: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t >OK, but do you think that the TC specified (none, a specific one, or any) >is a usefull one to have? ANd if yes, would then VlanIdReference be >a proper name? Or do you have better names suggestions in that case. >Would VlanIdOrNoneOrAny be better? > >Thanks, >Bert > >> -----Original Message----- >> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] >> Sent: donderdag 1 januari 2004 9:54 >> 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 >> >> VlanIdAssociation is definitely a bad name - there are other >> 'VLAN associations' it may be confused with. >> >> Regards, >> >> Dan >> >> > -----Original Message----- >> > From: bridge-mib-admin@ietf.org >> > [mailto:bridge-mib-admin@ietf.org]On Behalf Of Wijnen, Bert (Bert) >> > Sent: 31 December, 2003 6:52 PM >> > To: Bridge-Mib (E-mail) >> > Subject: [Bridge-mib] FW: Please review and comment: >> > draft-ietf-ops-vlanid-tc-mib-00.tx t >> > >> > Any comments? >> > >> > Thanks, >> > Bert >> > >> > -----Original Message----- >> > From: Mark Ellison [mailto:ellison@ieee.org] >> > Sent: woensdag 31 december 2003 20:04 >> > To: Wijnen, Bert (Bert) >> > Cc: mibs@ops.ietf.org >> > Subject: Re: Please review and comment: >> > draft-ietf-ops-vlanid-tc-mib-00.tx t >> > >> > Hi Bert, >> > >> > Thanks for your reply. >> > >> > I think I'd call a TC with a value range of Integer32 { 0 | >> 1..4094 | >> > 4095 } a VlanIdReference or VlanIdAssociation. >> > >> > This TC would be useful when defining an object that refers >> > to a vlan. >> > For example, a table where each entry can be associated with >> > none, one, >> > or any vlan. One alternative, with the existing TCs, would >> be to use >> > VlanIdOrAny, but have the agent return noSuchInstance when >> > there is no >> > association with a vlan. Another alternative, with the >> existing TCs, >> > would be to use VlanIdOrNone, and not have use of the special >> > any/4095 >> > value. >> > >> > Regards, >> > >> > Mark >> > >> > Wijnen, Bert (Bert) wrote: >> > >> > >Sorry for late reaction... but I am now again looking at >> > >this document and the discussion that we had back in October. >> > > >> > >inline >> > > >> > >>-----Original Message----- >> > >>From: Mark Ellison [mailto:ellison@ieee.org] >> > >>Sent: donderdag 2 oktober 2003 20:12 >> > >>To: Wijnen, Bert (Bert) >> > >>Cc: Mark Ellison; mibs@ops.ietf.org >> > >>Subject: Re: Please review and comment: >> > >>draft-ietf-ops-vlanid-tc-mib-00.txt >> > >> >> > >>Hi Bert, >> > >> >> > >>I'm wondering if there could be any mib or pib definition >> > requiring a >> > >>range of ( 0 | 1..4094 | 4095 ) for possible values? >> > >> >> > >Mark, I have not seen anyone react to this as a option that they >> > >wanted, so for now I am not going to include it. >> > >It can of course always be added later if a need arises. >> > > >> > >By the way, what woyuld you call/name that TC? >> > > >> > >Bert >> > > >> > >>Regards, >> > >> >> > >>Mark >_______________________________________________ >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 From exim@www1.ietf.org Sun Jan 4 03:52:33 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19527 for ; Sun, 4 Jan 2004 03:52:33 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ad3zR-0000er-3r for bridge-archive@odin.ietf.org; Sun, 04 Jan 2004 03:52:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i048q5IB002528 for bridge-archive@odin.ietf.org; Sun, 4 Jan 2004 03:52:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ad3zP-0000eT-Mv; Sun, 04 Jan 2004 03:52:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ad3yz-0000cu-Ih for bridge-mib@optimus.ietf.org; Sun, 04 Jan 2004 03:51:37 -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 DAA19492 for ; Sun, 4 Jan 2004 03:51:35 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ad3yx-0000Ht-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 03:51:35 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ad3x2-0007ma-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 03:49:37 -0500 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1Ad3uk-0007Ia-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 03:47:14 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i048i5kn015855 for ; Sun, 4 Jan 2004 03:44:05 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id i048i3kn015849 for ; Sun, 4 Jan 2004 03:44:04 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t Date: Sun, 4 Jan 2004 10:47:11 +0200 Message-ID: Thread-Topic: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t Thread-Index: AcPQWMZLhT5QANBcTDOvAzhqo89LmwCRkX6w From: "Romascanu, Dan (Dan)" To: "Wijnen, Bert (Bert)" , "Bridge-Mib (E-mail)" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Yes, the TC is useful. Concerning names, I do not know what = VlanIdReference is supposed to mean, but at least it is not confusing = like VlanIdAssociation. VlanIdOrNoneOrAny would be better.=20 Regards, Dan > -----Original Message----- > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] > Sent: 01 January, 2004 1:17 PM > To: Romascanu, Dan (Dan); Bridge-Mib (E-mail) > Subject: RE: [Bridge-mib] FW: Please review and comment:=20 > draft-ietf-ops-vlanid-tc-mib-00.tx t >=20 >=20 > OK, but do you think that the TC specified (none, a specific=20 > one, or any) > is a usefull one to have? ANd if yes, would then VlanIdReference be > a proper name? Or do you have better names suggestions in that case. > Would VlanIdOrNoneOrAny be better? >=20 > Thanks, > Bert=20 >=20 > > -----Original Message----- > > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] > > Sent: donderdag 1 januari 2004 9:54 > > 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 > >=20 > >=20 > > VlanIdAssociation is definitely a bad name - there are other=20 > > 'VLAN associations' it may be confused with.=20 > >=20 > > Regards, > >=20 > > Dan > >=20 > >=20 > >=20 > > > -----Original Message----- > > > From: bridge-mib-admin@ietf.org=20 > > > [mailto:bridge-mib-admin@ietf.org]On Behalf Of Wijnen, Bert (Bert) > > > Sent: 31 December, 2003 6:52 PM > > > To: Bridge-Mib (E-mail) > > > Subject: [Bridge-mib] FW: Please review and comment:=20 > > > draft-ietf-ops-vlanid-tc-mib-00.tx t > > >=20 > > >=20 > > > Any comments? > > >=20 > > > Thanks, > > > Bert=20 > > >=20 > > > -----Original Message----- > > > From: Mark Ellison [mailto:ellison@ieee.org] > > > Sent: woensdag 31 december 2003 20:04 > > > To: Wijnen, Bert (Bert) > > > Cc: mibs@ops.ietf.org > > > Subject: Re: Please review and comment: > > > draft-ietf-ops-vlanid-tc-mib-00.tx t > > >=20 > > >=20 > > > Hi Bert, > > >=20 > > > Thanks for your reply.=20 > > >=20 > > > I think I'd call a TC with a value range of Integer32 { 0 |=20 > > 1..4094 |=20 > > > 4095 } a VlanIdReference or VlanIdAssociation. > > >=20 > > > This TC would be useful when defining an object that refers=20 > > > to a vlan. =20 > > > For example, a table where each entry can be associated with=20 > > > none, one,=20 > > > or any vlan. One alternative, with the existing TCs, would=20 > > be to use=20 > > > VlanIdOrAny, but have the agent return noSuchInstance when=20 > > > there is no=20 > > > association with a vlan. Another alternative, with the=20 > > existing TCs,=20 > > > would be to use VlanIdOrNone, and not have use of the special=20 > > > any/4095=20 > > > value. > > >=20 > > > Regards, > > >=20 > > > Mark > > >=20 > > > Wijnen, Bert (Bert) wrote: > > >=20 > > > >Sorry for late reaction... but I am now again looking at=20 > > > >this document and the discussion that we had back in October. > > > > > > > >inline > > > > =20 > > > > > > > >>-----Original Message----- > > > >>From: Mark Ellison [mailto:ellison@ieee.org] > > > >>Sent: donderdag 2 oktober 2003 20:12 > > > >>To: Wijnen, Bert (Bert) > > > >>Cc: Mark Ellison; mibs@ops.ietf.org > > > >>Subject: Re: Please review and comment: > > > >>draft-ietf-ops-vlanid-tc-mib-00.txt > > > >> > > > >> > > > >>Hi Bert, > > > >> > > > >>I'm wondering if there could be any mib or pib definition=20 > > > requiring a=20 > > > >>range of ( 0 | 1..4094 | 4095 ) for possible values? > > > >> > > > >> =20 > > > >> > > > >Mark, I have not seen anyone react to this as a option that they > > > >wanted, so for now I am not going to include it. > > > >It can of course always be added later if a need arises. > > > > > > > >By the way, what woyuld you call/name that TC? > > > > > > > >Bert > > > > =20 > > > > > > > >>Regards, > > > >> > > > >>Mark > > > >> > > > >> > > > >> > > > >> =20 > > > >> > > > > > > > > =20 > > > > > > >=20 > > >=20 > > > _______________________________________________ > > > Bridge-mib mailing list > > > Bridge-mib@ietf.org > > > https://www1.ietf.org/mailman/listinfo/bridge-mib > > >=20 > >=20 >=20 _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Sun Jan 4 05:49:28 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22372 for ; Sun, 4 Jan 2004 05:49:27 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ad5ob-0006SV-1g for bridge-archive@odin.ietf.org; Sun, 04 Jan 2004 05:49:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i04An1CE024818 for bridge-archive@odin.ietf.org; Sun, 4 Jan 2004 05:49:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ad5oa-0006SA-Jd; Sun, 04 Jan 2004 05:49:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Ad5oN-0006Ri-Bh for bridge-mib@optimus.ietf.org; Sun, 04 Jan 2004 05:48:48 -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 FAA22367 for ; Sun, 4 Jan 2004 05:48:43 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Ad5oJ-0004qN-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 05:48:43 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Ad5mT-0004nw-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 05:46:49 -0500 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1Ad5kx-0004jR-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 05:45:16 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id i04AihP05487 for ; Sun, 4 Jan 2004 04:44:43 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Sun, 4 Jan 2004 11:44:40 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155033D2FD6@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Tom Petch , "Bridge-Mib (E-mail)" Subject: RE: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vl anid-tc-mib-00.tx t Date: Sun, 4 Jan 2004 11:44:36 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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: , List-Id: List-Post: List-Help: List-Subscribe: , 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 From exim@www1.ietf.org Sun Jan 4 16:30:31 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09240 for ; Sun, 4 Jan 2004 16:30:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdFox-0000nn-3H for bridge-archive@odin.ietf.org; Sun, 04 Jan 2004 16:30:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i04LU3gD003072 for bridge-archive@odin.ietf.org; Sun, 4 Jan 2004 16:30:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdFow-0000nN-D8; Sun, 04 Jan 2004 16:30:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdFo4-0000li-4j for bridge-mib@optimus.ietf.org; Sun, 04 Jan 2004 16:29:08 -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 QAA09194 for ; Sun, 4 Jan 2004 16:29:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AdFo2-00041b-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 16:29:06 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AdFmL-0003xJ-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 16:27:21 -0500 Received: from falcon.mail.pas.earthlink.net ([207.217.120.74]) by ietf-mx with esmtp (Exim 4.12) id 1AdFli-0003sr-00 for bridge-mib@ietf.org; Sun, 04 Jan 2004 16:26:43 -0500 Received: from user-1121fpu.dsl.mindspring.com ([66.32.191.62] helo=ANDREWLAPTOP) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1AdFld-00012d-00; Sun, 04 Jan 2004 13:26:37 -0800 From: "Andrew Smith" To: "'Tom Petch'" , "'Bridge-Mib \(E-mail\)'" Subject: RE: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.tx t Date: Sun, 4 Jan 2004 13:26:23 -0800 Message-ID: <098001c3d309$6b1ac9f0$1600000a@ANDREWLAPTOP> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155033D2FD6@nl0006exch001u.nl.lucent.com> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit >> 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. I'd agree with Bert here: what's the point of having a name if it does not convey semantics. Might as well call it "fred" or "1.3.6.1.2.3.4.5.6.7.8.999" if not. Andrew Smith _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Mon Jan 5 05:32:32 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12550 for ; Mon, 5 Jan 2004 05: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 1AdS1j-0005YG-VK for bridge-archive@odin.ietf.org; Mon, 05 Jan 2004 05:32:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i05AW3QR021341 for bridge-archive@odin.ietf.org; Mon, 5 Jan 2004 05:32:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdS1g-0005Xy-Ua; Mon, 05 Jan 2004 05:32:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AdS0q-0005XP-K7 for bridge-mib@optimus.ietf.org; Mon, 05 Jan 2004 05:31:08 -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 FAA12496 for ; Mon, 5 Jan 2004 05:31:05 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AdS0n-0002Pb-00 for bridge-mib@ietf.org; Mon, 05 Jan 2004 05:31:05 -0500 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AdRyt-0002KE-00 for bridge-mib@ietf.org; Mon, 05 Jan 2004 05:29:07 -0500 Received: from agitator.ibr.cs.tu-bs.de ([134.169.34.18]) by ietf-mx with esmtp (Exim 4.12) id 1AdRx5-0002DS-00 for bridge-mib@ietf.org; Mon, 05 Jan 2004 05:27:16 -0500 Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i05ARCmQ001128 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 5 Jan 2004 11:27:12 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i05ARBCw030159; Mon, 5 Jan 2004 11:27:11 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian-6.6) id i05ARBKs030156; Mon, 5 Jan 2004 11:27:11 +0100 Date: Mon, 5 Jan 2004 11:27:11 +0100 Message-Id: <200401051027.i05ARBKs030156@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: bwijnen@lucent.com CC: bridge-mib@ietf.org In-reply-to: <7D5D48D2CAA3D84C813F5B154F43B155033D2FD6@nl0006exch001u.nl.lucent.com> (bwijnen@lucent.com) Subject: Re: [Bridge-mib] FW: Please review and comment: draft-ietf-ops-vl anid-tc-mib-00.tx t References: <7D5D48D2CAA3D84C813F5B154F43B155033D2FD6@nl0006exch001u.nl.lucent.com> X-IBRFilter-SpamReport: 0 () X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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: , List-Id: List-Post: List-Help: List-Subscribe: , >>>>> Wijnen, Bert (Bert) writes: >> -----Original Message----- From: Tom Petch >> >> But if it does, then keep the name simple, don't overload the name, >> the identifier, with a description of the semantics >> Bert> MMm... if we look at for example DateAndTime TC, does that not Bert> give similar semantics in the name? I am sure there are many Bert> others that do so too. I do not think this is a good comparison, especially since the DateAndTime definition does not speel out a NULL value and people frequently use a string will all 0s which is not really consistent with the TC definition which requires a value unequal to 0 for the month and day fields. 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, let me play devils advocate: Can someone summarize why we already have VlanIdOrAny plus VlanIdOrNone and why VlanIdOrZero is not good enough? /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Mon Jan 5 15:32:32 2004 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02204 for ; 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 ; 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" From: "Tom Petch" 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 Date: Mon, 5 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: , List-Id: List-Post: List-Help: List-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) To: Tom Petch ; Bridge-Mib (E-mail) 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