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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 01 January 2004 08:58 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02048 for <bridge-archive@odin.ietf.org>; 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 <bridge-mib@ietf.org>; 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 <bridge-mib@ietf.org>; 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 <bridge-mib@ietf.org>; 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: <AAB4B3D3CF0F454F98272CBE187FDE2F042599C0@is0004avexu1.global.avaya.com>
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)" <dromasca@avaya.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>
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: <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: quoted-printable

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