[Bridge-mib] VLAn ID
"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Thu, 27 February 2003 16:33 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10445 for <bridge-archive@odin.ietf.org>; Thu, 27 Feb 2003 11:33:11 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1RGhEq00726 for bridge-archive@odin.ietf.org; Thu, 27 Feb 2003 11:43:14 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGh4p00704; Thu, 27 Feb 2003 11:43:04 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1RGgbp00673 for <bridge-mib@optimus.ietf.org>; Thu, 27 Feb 2003 11:42:37 -0500
Received: from auemail1.firewall.lucent.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10416 for <bridge-mib@ietf.org>; Thu, 27 Feb 2003 11:32:02 -0500 (EST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h1RGZum14190 for <bridge-mib@ietf.org>; Thu, 27 Feb 2003 11:35:57 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <DVZN9DY9>; Thu, 27 Feb 2003 17:35:55 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15501062FA1@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Randy Presuhn (E-mail)" <randy_presuhn@mindspring.com>
Cc: "Bridge-Mib (E-mail)" <bridge-mib@ietf.org>, mibs@ops.ietf.org
Date: Thu, 27 Feb 2003 17:35:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [Bridge-mib] VLAn ID
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>
Randy, you wrote: >To: bridge-mib@ietf.org >cc: mibs@ops.ietf.org (Les Bell/GB/3Com) >Subject: Re: [Bridge-mib] VLAN-ID > >Hi - > >I think it would be better if the "any" value in the *OrAny TC were >a non-negative value so that the type could be used to define an >index. There may not be a need today, but thinking ahead to >representing policy-like things wouldn't hurt. > As far as I can tell, you seem to be the only one sofar who has spoken up on the idea of not having a negative value for the "any" for the VlanIdOrAny TC that I proposed. You do not claim an immediate need, but a possible future (yet-undefined) need. So if there are any other people who feel that this makes sense, please speak up soon. We already have (rfc3289) DscpOrAny ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The IP header Differentiated Services Code-Point that may be used for discriminating among traffic streams. The value -1 is used to indicate a wild card i.e. any value." REFERENCE "RFC 2474, RFC 2780" SYNTAX Integer32 (-1 | 0..63) Based on that, we also got to (draft-ietf-ops-ipv6-flowlabel-00.txt) IPv6FlowLabelOrAny ::= TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The flow identifier or Flow Label in an IPv6 packet header that may be used to discriminate traffic flows. The value of -1 is used to indicate a wildcard, i.e. any value. " SYNTAX Integer32 (-1 | 0..1048575) And so now we were going down the same path VlanIdOrAny ::= TEXTUAL CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "The VLAN ID that uniquely identifies a VLAN. The value of -1 is used to indicate a wildcard, i.e. any value. " SYNTAX Integer32 (-1 | 1..4094) So that seems consistent, no? If we do so, we can bypass that discussion about if it is valid to use value 4095 to mean "any"... I suspect that discussion may take a while and we may need to check with IEEE 802 people/docs. Or are you telling us we better change all of the above to use a positive number for "any". >Randy > Thanks, Bert _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib
- [Bridge-mib] VLAn ID Wijnen, Bert (Bert)
- [Bridge-mib] Re: VLAn ID Tom Petch
- [Bridge-mib] RE: VLAn ID Andrew Smith
- [Bridge-mib] RE: VLAn ID Les Bell
- [Bridge-mib] RE: VLAn ID Wijnen, Bert (Bert)
- [Bridge-mib] RE: VLAn ID Les Bell
- [Bridge-mib] RE: VLAn ID Wijnen, Bert (Bert)
- [Bridge-mib] RE: VLAn ID Tony Jeffree
- [Bridge-mib] RE: VLAn ID Wijnen, Bert (Bert)
- [Bridge-mib] RE: VLAn ID C. M. Heard
- Re: [Bridge-mib] RE: VLAn ID Les Bell
- RE: [Bridge-mib] RE: VLAn ID Wijnen, Bert (Bert)