From exim@www1.ietf.org Fri Oct 3 03:06:25 2003 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 DAA25093 for ; Fri, 3 Oct 2003 03:06:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5K0q-0007d1-En for bridge-archive@odin.ietf.org; Fri, 03 Oct 2003 03:06:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h93764M7029323 for bridge-archive@odin.ietf.org; Fri, 3 Oct 2003 03:06:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A5K0o-0007cY-Vb; Fri, 03 Oct 2003 03:06:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A53JT-0006p7-At for bridge-mib@optimus.ietf.org; Thu, 02 Oct 2003 09:16:11 -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 JAA17747 for ; Thu, 2 Oct 2003 09:16:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A53JR-0000NF-00 for bridge-mib@ietf.org; Thu, 02 Oct 2003 09:16:09 -0400 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1A53JQ-0000Ms-00 for bridge-mib@ietf.org; Thu, 02 Oct 2003 09:16:09 -0400 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 h92DFYQ09369 for ; Thu, 2 Oct 2003 08:15:35 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id ; Thu, 2 Oct 2003 15:15:33 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155028EC3F0@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "mibs (E-mail)" Date: Thu, 2 Oct 2003 15:15:29 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Subject: [Bridge-mib] Please review and comment: draft-ietf-ops-vlanid-tc-mib-00.txt 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: , Comments on this ID very welcome. I have bcc:ed the bridgemib wg list. Pls post your comments to mibs@ops.ietf.org My idea is to have some discussion, make updates as a result of that discussion (if any) and then issue a 4 week IETF Last Call for PS (Proposed Standard) Thanks, Bert -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: maandag 29 september 2003 16:57 Subject: I-D ACTION:draft-ietf-ops-vlanid-tc-mib-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Operations & Management Open Area Working Group of the IETF. Title : Textual Conventions for Virtual Local Area Network Identifiers (VLAN-ID) Author(s) : B. Wijnen Filename : draft-ietf-ops-vlanid-tc-mib-00.txt Pages : 8 Date : 2003-9-29 This memo defines textual conventions to represent the commonly used Virtual Local Area Network Identifier (VLAN-ID). The intent is that these textual conventions (TCs) will be imported and used in MIB modules that would otherwise define their own representations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ops-vlanid-tc-mib-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ops-vlanid-tc-mib-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ops-vlanid-tc-mib-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Tue Oct 7 03:16:28 2003 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 DAA21778 for ; Tue, 7 Oct 2003 03:16: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 1A6m4h-0002Fm-5T for bridge-archive@odin.ietf.org; Tue, 07 Oct 2003 03:16:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h977G3WJ008662 for bridge-archive@odin.ietf.org; Tue, 7 Oct 2003 03:16:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6m4f-0002FU-Vc; Tue, 07 Oct 2003 03:16:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A6VPD-0005qF-Vt for bridge-mib@optimus.ietf.org; Mon, 06 Oct 2003 09:28:08 -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 JAA29321 for ; Mon, 6 Oct 2003 09:27:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A6VPC-0005AD-00 for bridge-mib@ietf.org; Mon, 06 Oct 2003 09:28:06 -0400 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1A6VPB-000590-00 for bridge-mib@ietf.org; Mon, 06 Oct 2003 09:28:05 -0400 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 h96DRVn16069 for ; Mon, 6 Oct 2003 08:27:32 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id ; Mon, 6 Oct 2003 15:26:41 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502A203AC@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Kristine Adamson , mibs@ops.ietf.org Date: Mon, 6 Oct 2003 15:26:37 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain Subject: [Bridge-mib] RE: draft-ietf-ops-vlanid-tc-mib-00.txt 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: , > > Hello! > We would like to use the new VLAN ID TCs in this document but have a > question about the meaning of the 4095 value. The following is from an > append to this mailing list in July, 2003: > > I agree that no changes are required to clause 12 of 802.1Q. > > Les... > > "C. M. Heard" @ietf.org on 07/06/2003 04:07:22 > > Sent by: bridge-mib-admin@ietf.org > > > On Fri, 6 Jun 2003, in a message forwarded by Bert Wijnen, > Tony Jeffree wrote: > > We have concluded that the use of 4095 as a wildcard is > > acceptable to 802.1, and we will make any necessary changes to > > 802.1Q in due course to relax the current stated restriction. > > However, we need to know whether that is all that needs to be > > done to 802.1Q - i.e., is there any need to change our > > definitions of the managed objects in the document (Clause 12) > > to reflect the interpretation of 4095 as a wildcard, or is this > > simply an issue for the SNMP machinery to handle? > > After a quick look at 802.1Q-1998, 802.1u-2001, and 802.1v-2001 it > appears to me that no changes are required to clause 12 of 802.1Q. > > Can any Bridge-Mib folk confirm that? > > //cmh > > Given this update, is the referenced IEEE spec being updated to state that > 4095 is a valid VLAN ID value? Or it is just going to indicate that 4095 > can be used by SNMP as a valid VLAN ID value, to mean _any_ VLAN ID value > from 1-4094? Thanks! > My understanding is the latter, as per the email from Tony. The new reference is to IEEE.802-1Q.2003 as per the references section of the I-D. Add on top of that there is expected to be as per : ----Original Message----- From: Tony Jeffree [mailto:tony@jeffree.co.uk] Sent: donderdag 25 september 2003 0:41 To: Wijnen, Bert (Bert) Cc: Wijnen, Bert (Bert); 'Les Bell (E-mail)'; Wijnen, Bert (Bert); Dan Romascanu (E-mail) Subject: RE: VLAN ID You can reference my Email copied below (6th June 03), which reflects the discussion in 802.1's June 03 interim meeting. Regards, Tony At 00:30 25/09/2003 +0200, Wijnen, Bert (Bert) wrote: >Thanks. WHat meeting or statement or whatever can I >reference where the decision was made that 4095 is OK >as a wildcard value? > >Thanks, >Bert _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Mon Oct 27 17:57:22 2003 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 RAA25516 for ; Mon, 27 Oct 2003 17:57:22 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGII-0004IP-NN for bridge-archive@odin.ietf.org; Mon, 27 Oct 2003 17:57:05 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RMv2xX016501 for bridge-archive@odin.ietf.org; Mon, 27 Oct 2003 17:57:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGIH-0004I1-9a; Mon, 27 Oct 2003 17:57:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEGHt-0004Fg-3T for bridge-mib@optimus.ietf.org; Mon, 27 Oct 2003 17:56: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 RAA25458 for ; Mon, 27 Oct 2003 17:56:23 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEGHq-0001Hh-00 for bridge-mib@ietf.org; Mon, 27 Oct 2003 17:56:34 -0500 Received: from mailx.wwp.com ([65.107.175.5]) by ietf-mx with esmtp (Exim 4.12) id 1AEGHp-0001He-00 for bridge-mib@ietf.org; Mon, 27 Oct 2003 17:56:33 -0500 Received: from localhost (localhost.filter.com [127.0.0.1]) by mailx.wwp.com (Postfix) with ESMTP id 08CAF58CC for ; Mon, 27 Oct 2003 14:56:31 -0800 (PST) Received: from mailx.wwp.com ([127.0.0.1]) by localhost (mailx.wwp.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31882-05 for ; Mon, 27 Oct 2003 14:56:29 -0800 (PST) Received: from mailx.wwp.com (unknown [192.168.6.15]) by mailx.wwp.com (Postfix) with ESMTP id 44F5158B0 for ; Mon, 27 Oct 2003 14:56:29 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 27 Oct 2003 14:56:31 -0800 Message-ID: <4E9A9436C008314EAA32033B23E96FD99B6B06@thorondor.wwp.com> Thread-Topic: newRoot TRAP-TYPE in RFC 1286 Thread-Index: AcOc3ZBRKazkwcXXSbGzM5lacaqUjA== From: "Amit Grover" To: Content-Transfer-Encoding: quoted-printable Subject: [Bridge-mib] newRoot TRAP-TYPE in RFC 1286 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 Hi, In this RFC 1286 newRoot trap is defined like this ******************************* newRoot TRAP-TYPE=20 ENTERPRISE dot1dBridge=20 DESCRIPTION "The newRoot trap indicates that the sending agent has = become the new root of the Spanning Tree; the trap is sent by a bridge = soon after its election as the new root, e.g., upon expiration of the = Topology Change Timer immediately subsequent to Decker, Langille, = Rijsinghani & McCloghrie [Page 36] RFC 1286 Bridge MIB December 1991 = its election."=20 ::=3D 1=20 ************************************************ Question: What is the OID of this TRAP ? thks amit _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Tue Oct 28 13:52:27 2003 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 NAA16458 for ; Tue, 28 Oct 2003 13:52: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 1AEYwk-00011d-Ut for bridge-archive@odin.ietf.org; Tue, 28 Oct 2003 13:52:08 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SIq2VJ003927 for bridge-archive@odin.ietf.org; Tue, 28 Oct 2003 13:52:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEYwj-000111-Mq; Tue, 28 Oct 2003 13:52:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AEYw3-0000rx-Ez for bridge-mib@optimus.ietf.org; Tue, 28 Oct 2003 13:51:19 -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 NAA16324 for ; Tue, 28 Oct 2003 13:51:07 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AEYw1-0004Ky-00 for bridge-mib@ietf.org; Tue, 28 Oct 2003 13:51:17 -0500 Received: from pengo.systems.pipex.net ([62.241.160.193]) by ietf-mx with esmtp (Exim 4.12) id 1AEYw0-0004K7-00 for bridge-mib@ietf.org; Tue, 28 Oct 2003 13:51:16 -0500 Received: from tom3 (1Cust199.tnt2.lnd1.gbr.da.uu.net [62.188.13.199]) by pengo.systems.pipex.net (Postfix) with SMTP id 123714C000A2; Tue, 28 Oct 2003 18:50:36 +0000 (GMT) Message-ID: <003701c39d83$f56ddb80$0301a8c0@tom3> Reply-To: "Tom Petch" From: "Tom Petch" To: "Amit Grover" , Subject: Re: [Bridge-mib] newRoot TRAP-TYPE in RFC 1286 Date: Tue, 28 Oct 2003 18:46:39 -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 .1.3.6.1.2.1.17.1 Tom Petch -----Original Message----- From: Amit Grover To: bridge-mib@ietf.org Date: 27 October 2003 22:57 Subject: [Bridge-mib] newRoot TRAP-TYPE in RFC 1286 Hi, In this RFC 1286 newRoot trap is defined like this ******************************* newRoot TRAP-TYPE ENTERPRISE dot1dBridge DESCRIPTION "The newRoot trap indicates that the sending agent has become the new root of the Spanning Tree; the trap is sent by a bridge soon after its election as the new root, e.g., upon expiration of the Topology Change Timer immediately subsequent to Decker, Langille, Rijsinghani & McCloghrie [Page 36] RFC 1286 Bridge MIB December 1991 its election." ::= 1 ************************************************ Question: What is the OID of this TRAP ? thks amit _______________________________________________ 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