RE: [Bridge-mib] VlanID and VlanIDOrAny

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 07 September 2003 08:55 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05377 for <bridge-archive@odin.ietf.org>; Sun, 7 Sep 2003 04:55:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vvK3-00080y-1B for bridge-archive@odin.ietf.org; Sun, 07 Sep 2003 04:55:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h878t26a030807 for bridge-archive@odin.ietf.org; Sun, 7 Sep 2003 04:55:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vvK2-00080h-AG; Sun, 07 Sep 2003 04:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vvJx-0007zy-PH for bridge-mib@optimus.ietf.org; Sun, 07 Sep 2003 04:54:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05359 for <bridge-mib@ietf.org>; Sun, 7 Sep 2003 04:54:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19vvJt-00078m-00 for bridge-mib@ietf.org; Sun, 07 Sep 2003 04:54:53 -0400
Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 19vvJs-00078e-00 for bridge-mib@ietf.org; Sun, 07 Sep 2003 04:54:53 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.0/Switch-3.1.0) with ESMTP id h878rUXa010616 for <bridge-mib@ietf.org>; Sun, 7 Sep 2003 03:53:30 -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.0/Switch-3.1.0) with ESMTP id h878rRXa010607 for <bridge-mib@ietf.org>; Sun, 7 Sep 2003 03:53:28 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] VlanID and VlanIDOrAny
Date: Sun, 07 Sep 2003 11:54:51 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F038A9A8A@is0004avexu1.global.avaya.com>
Thread-Topic: [Bridge-mib] VlanID and VlanIDOrAny
Thread-Index: AcN1GXkAsRPeogatTqGyfiBeiWfgrgAA1aeg
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

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:bwijnen@lucent.com]
> 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:bwijnen@lucent.com]
> 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
> 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
> 

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