From daemon@optimus.ietf.org Wed May 1 10:58:37 2002 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 KAA01637 for ; Wed, 1 May 2002 10:58:37 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA18825 for bridge-archive@odin.ietf.org; Wed, 1 May 2002 10:58:38 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18813; Wed, 1 May 2002 10:58:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA18777 for ; Wed, 1 May 2002 10:58:22 -0400 (EDT) Received: from apollo.nbase.co.il (apollo.nbase.co.il [194.90.137.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01625 for ; Wed, 1 May 2002 10:58:18 -0400 (EDT) Received: from Alexr ([194.90.136.135]) by apollo.nbase.co.il (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-44418U200L2S100) with SMTP id AAA606; Wed, 1 May 2002 17:58:19 +0200 Reply-To: From: alexr@nbase.co.il (Alex Ruzin) To: Cc: , , Date: Wed, 1 May 2002 17:54:55 +0200 Message-ID: <000301c1f128$8ab99ad0$87885ac2@Alexr> 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 CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <001401c17cb4$b511e190$87885ac2@Alexr> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 7bit Subject: [Bridge-mib] Q: Traps in Bridge MIB? Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org Content-Transfer-Encoding: 7bit Is Bridge MIB WG (or IEEE 802.1 WG?) working on Spanning Tree traps in the MIB? If yes - what is a status? For example, which parameters will have legacy (newRoot & topologyChange) and/or new traps? Thanks, Alex --------------------- Open Source RSTP http://rstplib.sourceforge.net Optical Access Ltd. http://www.opticalaccess.com _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed May 1 11:36:04 2002 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 LAA03649 for ; Wed, 1 May 2002 11:36:03 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA21722 for bridge-archive@odin.ietf.org; Wed, 1 May 2002 11:36:05 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21714; Wed, 1 May 2002 11:36:04 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA21677 for ; Wed, 1 May 2002 11:36:01 -0400 (EDT) Received: from columba.www.eur.3com.com (ip-161-71-171-238.corp-eur.3com.com [161.71.171.238]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03644 for ; Wed, 1 May 2002 11:35:59 -0400 (EDT) Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id g41Fbcx00166; Wed, 1 May 2002 16:37:39 +0100 (BST) Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id g41Fa4D11664; Wed, 1 May 2002 16:36:04 +0100 (BST) Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256BAC.0055EAF3 ; Wed, 1 May 2002 16:38:27 +0100 X-Lotus-FromDomain: 3COM From: "Les Bell" To: Arozin@Opticalaccess.com cc: bridge-mib@ietf.org, stds-802-1@ieee.org, rstplib-users@lists.sourceforge.net Message-ID: <80256BAC.0055E871.00@notesmta.eur.3com.com> Date: Wed, 1 May 2002 16:30:30 +0100 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Bridge-mib] Re: Q: Traps in Bridge MIB? Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org There is no work ongoing for Spanning Tree traps, other than to define them in the SMIv2 notification format. See http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-02.txt for the definitions. The newRoot and topologyChange traps apply to RSTP as well as legacy STP. Les... alexr@nbase.co.il (Alex Ruzin) on 01/05/2002 16:54:55 Please respond to Arozin@Opticalaccess.com Sent by: alexr@nbase.co.il (Alex Ruzin) To: Les Bell/GB/3Com cc: bridge-mib@ietf.org, stds-802-1@ieee.org, rstplib-users@lists.sourceforge.net Subject: Q: Traps in Bridge MIB? Is Bridge MIB WG (or IEEE 802.1 WG?) working on Spanning Tree traps in the MIB? If yes - what is a status? For example, which parameters will have legacy (newRoot & topologyChange) and/or new traps? Thanks, Alex --------------------- Open Source RSTP http://rstplib.sourceforge.net Optical Access Ltd. http://www.opticalaccess.com _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Fri May 3 06:07:10 2002 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 GAA08242 for ; Fri, 3 May 2002 06:07:10 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA24789 for bridge-archive@odin.ietf.org; Fri, 3 May 2002 06:07:12 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24776; Fri, 3 May 2002 06:07:07 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA24745 for ; Fri, 3 May 2002 06:07:05 -0400 (EDT) Received: from columba.www.eur.3com.com (ip-161-71-171-238.corp-eur.3com.com [161.71.171.238]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08237 for ; Fri, 3 May 2002 06:07:02 -0400 (EDT) Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id g43A8lx19987 for ; Fri, 3 May 2002 11:08:47 +0100 (BST) Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id g43A7CD08850 for ; Fri, 3 May 2002 11:07:12 +0100 (BST) Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256BAE.0037CFC3 ; Fri, 3 May 2002 11:09:36 +0100 X-Lotus-FromDomain: 3COM From: "Les Bell" To: bridge-mib@ietf.org Message-ID: <80256BAE.0037CEE0.00@notesmta.eur.3com.com> Date: Fri, 3 May 2002 11:01:38 +0100 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Bridge-mib] Mailman upgrade at ietf.org Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org ---------------------- Forwarded by Les Bell/GB/3Com on 03/05/2002 11:05 --------------------------- mailadmin@ietf.org on 02/05/2002 22:16:58 Sent by: mailadmin@ietf.org To: mailmanlist-owners@ietf.org cc: scoya@ietf.org, rbinder@ietf.org, sweilnau@ietf.org, gcunning@ietf.org (Les Bell/GB/3Com) Subject: Mailman upgrade at ietf.org Mailman is going to be upgraded from the version currently running (version 1.0) to version 2.0 on Tuesday, May 7, 2002. This conversion should be transparent to you and your list members. The lists will be shut down for about a two hour period during the conversion that day. At this time, I cannot provide a time during the day I am going to do it, more than likely between 1 and 3 pm EST in the afternoon. If you have any questions, please reply to this message. Feel free to notify your list members if desired. Mailman List Administrator _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Tue May 7 06:20:21 2002 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 GAA01453 for ; Tue, 7 May 2002 06:20:21 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA12761 for bridge-archive@odin.ietf.org; Tue, 7 May 2002 06:20:27 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA12745; Tue, 7 May 2002 06:20:17 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA05284 for ; Fri, 3 May 2002 17:07:03 -0400 (EDT) Received: from shell4.bayarea.net (shell4.BAYAREA.NET [209.128.82.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01003 for ; Fri, 3 May 2002 17:06:57 -0400 (EDT) Received: from localhost (heard@localhost) by shell4.bayarea.net (8.9.3/8.9.3) with ESMTP id OAA17771; Fri, 3 May 2002 14:07:00 -0700 (envelope-from heard@pobox.com) X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 3 May 2002 14:06:59 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "K.C. Norseth" cc: bridge-mib@ietf.org Subject: Re: [Bridge-mib] Definitions for Port Access Control (IEEE 802.1X) MIB Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org On April 22, K.C. Norseth wrote: > I have an update to the 802.1x mib for the IETF. I corrected the compile > problem. The draft I prepared can be found at: > http://norseth.org/ietf/bridgemib/8021x/draft-ietf-bridge-8021x-00.txt > > Logs of the smidumps can be found in http://norseth.org/ietf/bridgemib/8021x > directory if you would like to use them. > > There are only a couple of changes from the original published IEEE mib > (http://www.ieee802.org/1/mirror/8021/MIBs/802-1x-2001-mib.txt) required to > make it compile. They are in the IMPORTS section. If you have any > comments, please let me know. If there are no issues, I will submit it to > the IETF this week. K.C., I think there is an error in one of the compilation fixups, namely that this OID assignment (for the MODULE-IDENTITY invocation) -- ::= { iso(1) std(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) 1 } ::= { iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) 1 } looks like it will yield a wrong (and illegal) OID. I think the correct way to fix the problem is this: ::= { iso std(0) iso8802(8802) ieee802dot1(1) ieee802dot1mibs(1) 1 } i.e. just change "iso(1)" to "iso" (this is a predefined identifier of type OID inherited from ASN.1 by SMIv2). Also, there are some other problems that your previous passes did not catch: % ./libsmi-0.3.1/tools/smilint -s -l 9 ./IEEE8021-PAE-MIB |& grep -v 'object identifier name .* longer than 32 characters$' ./IEEE8021-PAE-MIB:188: [4] node `dot1xPaePortReauthenticate' must be contained in at least one conformance group ./IEEE8021-PAE-MIB:1101: [4] node `dot1xAuthSessionUserName' must be contained in at least one conformance group Hope I'm not too late with these comments. Mike _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed May 8 02:58:21 2002 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 CAA27709 for ; Wed, 8 May 2002 02:58:21 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA07919 for bridge-archive@odin.ietf.org; Wed, 8 May 2002 02:58:28 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA07910; Wed, 8 May 2002 02:58:27 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA07877 for ; Wed, 8 May 2002 02:58:25 -0400 (EDT) Received: from columba.www.eur.3com.com (ip-161-71-171-238.corp-eur.3com.com [161.71.171.238]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27706 for ; Wed, 8 May 2002 02:58:18 -0400 (EDT) Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id g4870Bx16982 for ; Wed, 8 May 2002 08:00:11 +0100 (BST) Received: from notesmta.eur.3com.com (eurmta2.EUR.3Com.COM [140.204.220.207]) by toucana.eur.3com.com with SMTP id g486wdD26411 for ; Wed, 8 May 2002 07:58:39 +0100 (BST) Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256BB3.00269080 ; Wed, 8 May 2002 08:01:13 +0100 X-Lotus-FromDomain: 3COM From: "Les Bell" To: bridge-mib@ietf.org Message-ID: <80256BB3.00268E8C.00@notesmta.eur.3com.com> Date: Wed, 8 May 2002 07:52:55 +0100 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Bridge-mib] Mailman upgrade at ietf.org Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org ---------------------- Forwarded by Les Bell/GB/3Com on 08/05/2002 07:58 --------------------------- mailadm@ietf.org on 07/05/2002 20:16:09 Sent by: mailadm@ietf.org To: mailmanlist-owners@ietf.org cc: (Les Bell/GB/3Com) Subject: Mailman upgrade at ietf.org Due to some unforseen complications, the upgrade did not occur. It is now slated for next week around the 15th of May. My apologies for the inconvenience. Mailman List Administrator ---------- Forwarded message ---------- Date: Thu, 2 May 2002 17:13:23 -0400 (Eastern Daylight Time) From: mailadmin@ietf.org To: mailmanlist-owners@ietf.org Subject: Mailman upgrade at ietf.org Mailman is going to be upgraded from the version currently running (version 1.0) to version 2.0 on Tuesday, May 7, 2002. This conversion should be transparent to you and your list members. The lists will be shut down for about a two hour period during the conversion that day. At this time, I cannot provide a time during the day I am going to do it, more than likely between 1 and 3 pm EST in the afternoon. If you have any questions, please reply to this message. Feel free to notify your list members if desired. Mailman List Administrator _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Thu May 23 07:30:02 2002 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 HAA04746 for ; Thu, 23 May 2002 07:30:02 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA11590 for bridge-archive@odin.ietf.org; Thu, 23 May 2002 07:30:22 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA11574; Thu, 23 May 2002 07:30:20 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA11452 for ; Thu, 23 May 2002 07:30:15 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04730; Thu, 23 May 2002 07:29:53 -0400 (EDT) Message-Id: <200205231129.HAA04730@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: bridge-mib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 23 May 2002 07:29:52 -0400 Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bridge MIB Working Group of the IETF. Title : Definitions of Managed Objects for Bridges Author(s) : K. Norseth, E. Bell Filename : draft-ietf-bridge-bridgemib-smiv2-03.txt Pages : 36 Date : 22-May-02 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing MAC bridges based on the IEEE 802.1D-1998 standard between Local Area Network (LAN) segments. Provisions are made for support of transparent bridging. Provisions are also made so that these objects apply to bridges connected by subnetworks other than LAN segments. The MIB presented in this memo is a direct translation of the BRIDGE MIB defined in [RFC1493], to the SMIv2 syntax required for current IETF MIB standards. This memo obsoletes RFC 1493. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemib-smiv2-03.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-bridge-bridgemib-smiv2-03.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-bridge-bridgemib-smiv2-03.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020522154723.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-bridge-bridgemib-smiv2-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-bridge-bridgemib-smiv2-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020522154723.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Thu May 23 10:13:25 2002 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 KAA11403 for ; Thu, 23 May 2002 10:13:25 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id KAA21064 for bridge-archive@odin.ietf.org; Thu, 23 May 2002 10:13:44 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA21049; Thu, 23 May 2002 10:13:43 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA21020 for ; Thu, 23 May 2002 10:13:42 -0400 (EDT) Received: from apollo.nbase.co.il (apollo.nbase.co.il [194.90.137.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11380; Thu, 23 May 2002 10:13:19 -0400 (EDT) Received: from Alexr ([194.90.136.135]) by apollo.nbase.co.il (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-44418U200L2S100) with SMTP id AAA693; Thu, 23 May 2002 17:17:55 +0200 Reply-To: From: alexr@nbase.co.il (Alex Ruzin) To: Cc: Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt Date: Thu, 23 May 2002 17:14:24 +0200 Message-ID: <003801c2026c$86d49f00$87885ac2@Alexr> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200205231129.HAA04730@ietf.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Content-Transfer-Encoding: 7bit Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org Content-Transfer-Encoding: 7bit [This comment isn't devoted to this edition of the draft, but to all previous editions too] It seems to me, that the object dot1dStpPortEnable doesn't reflect a *port state* as it is defined in "IEEE 802.1D-1998: Section 8.5.5.2"; rather it correspondents to "Force port state" from Section 14.8.2.2. I propose to discuss an option to: 1) do this object "MAX-ACCESS write-only" 2) set possible values as SYNTAX INTEGER { forceBlock(1), forceDisable(2) } 3) change REFERENCE: "IEEE 802.1D-1998: Section 14.8.2.2" Yours faithfully, Alex > -----Original Message----- > From: bridge-mib-admin@ietf.org [mailto:bridge-mib-admin@ietf.org]On > Behalf Of Internet-Drafts@ietf.org > Sent: Thursday, May 23, 2002 1:30 PM > To: IETF-Announce: > Cc: bridge-mib@ietf.org > Subject: [Bridge-mib] I-D > ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Bridge MIB Working Group of the IETF. > > Title : Definitions of Managed Objects for Bridges > Author(s) : K. Norseth, E. Bell > Filename : draft-ietf-bridge-bridgemib-smiv2-03.txt > Pages : 36 > Date : 22-May-02 > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in TCP/IP based internets. > In particular it defines objects for managing MAC bridges based on > the IEEE 802.1D-1998 standard between Local Area Network (LAN) > segments. Provisions are made for support of transparent bridging. > Provisions are also made so that these objects apply to bridges > connected by subnetworks other than LAN segments. > The MIB presented in this memo is a direct translation of the BRIDGE > MIB defined in [RFC1493], to the SMIv2 syntax required for current > IETF MIB standards. This memo obsoletes RFC 1493. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemi b-smiv2-03.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-bridge-bridgemib-smiv2-03.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-bridge-bridgemib-smiv2-03.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 daemon@ns.ietf.org Thu May 23 14:16:10 2002 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 OAA21453 for ; Thu, 23 May 2002 14:16:10 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA09806 for bridge-archive@odin.ietf.org; Thu, 23 May 2002 14:16:30 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09793; Thu, 23 May 2002 14:16:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09762 for ; Thu, 23 May 2002 14:16:27 -0400 (EDT) Received: from agile.yagosys.com (host60.riverstonenet.com [64.95.122.60] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21425 for ; Thu, 23 May 2002 14:16:05 -0400 (EDT) Received: (qmail 1639 invoked by uid 10041); 23 May 2002 18:15:55 -0000 Date: Thu, 23 May 2002 11:15:55 -0700 From: Michael MacFaden To: Arozin@Opticalaccess.com Cc: Internet-Drafts@ietf.org, bridge-mib@ietf.org Subject: Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt Message-ID: <20020523111555.D1464@riverstonenet.com> References: <200205231129.HAA04730@ietf.org> <003801c2026c$86d49f00$87885ac2@Alexr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003801c2026c$86d49f00$87885ac2@Alexr> User-Agent: Mutt/1.3.22i X-Operating-System: GNU/Linux 2.4.18 Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org On Thu, May 23, 2002 at 05:14:24PM +0200, Alex Ruzin wrote: >It seems to me, that the object dot1dStpPortEnable doesn't reflect a *port >state* as it is defined in "IEEE 802.1D-1998: Section 8.5.5.2"; rather it >correspondents to "Force port state" from Section 14.8.2.2. >I propose to discuss an option to: >1) do this object "MAX-ACCESS write-only" >2) set possible values as > SYNTAX INTEGER { > forceBlock(1), > forceDisable(2) > } >3) change REFERENCE: "IEEE 802.1D-1998: Section 14.8.2.2" See RFC 2578 page 9, in SMIv2 MAX-ACCESS does not support "write-only " Mike MacFaden _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@ns.ietf.org Thu May 23 14:21:09 2002 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 OAA21670 for ; Thu, 23 May 2002 14:21:09 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA09986 for bridge-archive@odin.ietf.org; Thu, 23 May 2002 14:21:29 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09979; Thu, 23 May 2002 14:21:28 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09942 for ; Thu, 23 May 2002 14:21:26 -0400 (EDT) Received: from windlord.WWP.COM (mail.worldwidepackets.com [12.46.89.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21646; Thu, 23 May 2002 14:21:03 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt Date: Thu, 23 May 2002 11:21:10 -0700 Message-ID: <917063BAB0DDB043AF5FAA73C7A835D417302F@windlord.WWP.COM> Thread-Topic: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt Thread-Index: AcICZGq2zebWOhDUS1S9qWFgLAQkCgAIfb0Q From: "Rohit Rohit" To: , Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA09943 Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org Content-Transfer-Encoding: 8bit Hi Alex, I have never heard of "MAX-ACCESS write-only" I have heard it to be read-only; read-write or read-create. Thanks Rohit -----Original Message----- From: Alex Ruzin [mailto:alexr@nbase.co.il] Sent: Thursday, May 23, 2002 8:14 AM To: Internet-Drafts@ietf.org Cc: bridge-mib@ietf.org Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt [This comment isn't devoted to this edition of the draft, but to all previous editions too] It seems to me, that the object dot1dStpPortEnable doesn't reflect a *port state* as it is defined in "IEEE 802.1D-1998: Section 8.5.5.2"; rather it correspondents to "Force port state" from Section 14.8.2.2. I propose to discuss an option to: 1) do this object "MAX-ACCESS write-only" 2) set possible values as SYNTAX INTEGER { forceBlock(1), forceDisable(2) } 3) change REFERENCE: "IEEE 802.1D-1998: Section 14.8.2.2" Yours faithfully, Alex > -----Original Message----- > From: bridge-mib-admin@ietf.org [mailto:bridge-mib-admin@ietf.org]On > Behalf Of Internet-Drafts@ietf.org > Sent: Thursday, May 23, 2002 1:30 PM > To: IETF-Announce: > Cc: bridge-mib@ietf.org > Subject: [Bridge-mib] I-D > ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > This draft is a work item of the Bridge MIB Working Group of the IETF. > > Title : Definitions of Managed Objects for Bridges > Author(s) : K. Norseth, E. Bell > Filename : draft-ietf-bridge-bridgemib-smiv2-03.txt > Pages : 36 > Date : 22-May-02 > > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in TCP/IP based internets. > In particular it defines objects for managing MAC bridges based on > the IEEE 802.1D-1998 standard between Local Area Network (LAN) > segments. Provisions are made for support of transparent bridging. > Provisions are also made so that these objects apply to bridges > connected by subnetworks other than LAN segments. > The MIB presented in this memo is a direct translation of the BRIDGE > MIB defined in [RFC1493], to the SMIv2 syntax required for current > IETF MIB standards. This memo obsoletes RFC 1493. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-bridge-bridgemi b-smiv2-03.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-bridge-bridgemib-smiv2-03.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-bridge-bridgemib-smiv2-03.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 _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Sun May 26 02:19:33 2002 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 CAA16586 for ; Sun, 26 May 2002 02:19:28 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA23744 for bridge-archive@odin.ietf.org; Sun, 26 May 2002 02:19:48 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA23735; Sun, 26 May 2002 02:19:47 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA23704 for ; Sun, 26 May 2002 02:19:45 -0400 (EDT) Received: from apollo.nbase.co.il (apollo.nbase.co.il [194.90.137.2]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16559; Sun, 26 May 2002 02:19:17 -0400 (EDT) Received: from Alexr ([194.90.136.135]) by apollo.nbase.co.il (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-44418U200L2S100) with SMTP id AAA643; Sun, 26 May 2002 09:23:52 +0200 Reply-To: From: alexr@nbase.co.il (Alex Ruzin) To: "'Rohit Rohit'" , "'Michael MacFaden'" , Cc: Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt Date: Sun, 26 May 2002 09:20:20 +0200 Message-ID: <005001c20485$cc2c4510$87885ac2@Alexr> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0051_01C20496.8FB51510" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <917063BAB0DDB043AF5FAA73C7A835D417302F@windlord.WWP.COM> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-MS-TNEF-Correlator: 000000000B849FA1C974D211B9A800AA00BD851E640DE304 Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org This is a multi-part message in MIME format. ------=_NextPart_000_0051_01C20496.8FB51510 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit OK, OK, OK... Actually I only meant to make the definition for this object *semantically* better. Are you agree with my proposition "in general", except "MAX-ACCESS"? Do you think, that definition of this object has to be improved? If so, I propose dot1dStpPortEnable OBJECT-TYPE SYNTAX INTEGER { dummyReadValue(0), forceBlock(1), forceDisable(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "'Force Port State' of the port. Both GET and GETNEXT operation always return value dummyReadValue(0). An attempt to write the value dummyReadValue(0) must cause an error." REFERENCE "IEEE 802.1D-1998: Section 14.8.2.2" ::= { dot1dStpPortEntry 4 } Your comments and/or proposition, please? Alex On Thursday, May 23, 2002 8:16 PM Michael MacFaden wrote: Michael > See RFC 2578 page 9, in SMIv2 MAX-ACCESS does not support Michael > "write-only " On Thursday, May 23, 2002 8:21 PM Rohit Rohit wrote: Rohit> I have never heard of "MAX-ACCESS write-only" Rohit> I have heard it to be read-only; read-write or read-create. ------=_NextPart_000_0051_01C20496.8FB51510 Content-Type: application/ms-tnef; name="winmail.dat" Content-Disposition: attachment; filename="winmail.dat" Content-Transfer-Encoding: base64 eJ8+IhYHAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5wQAAAAAAADrAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANIHBQAaAAkAFAAAAAAAFQEB A5AGAHwIAAAoAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADAC4AAAAAAAMANgAA AAAAHgBwAAEAAABBAAAAW0JyaWRnZS1taWJdIEktRCBBQ1RJT046ZHJhZnQtaWV0Zi1icmlkZ2Ut YnJpZGdlbWliLXNtaXYyLTAzLnR4dAAAAAACAXEAAQAAABYAAAABwgSFyzwCKiN7ACxCPLYoStw5 N4UVAAACAR0MAQAAAB4AAABTTVRQOkFST1pJTkBPUFRJQ0FMQUNDRVNTLkNPTQAAAAsAAQ4AAAAA QAAGDgCQ6r6FBMIBAgEKDgEAAAAYAAAAAAAAAAuEn6HJdNIRuagAqgC9hR7CgAAAAwAUDgEAAAAL AB8OAQAAAAIBCRABAAAA6QMAAOUDAAB7BgAATFpGdeKA72oDAAoAcmNwZzEyNeI1A0N0ZXgFQQED AfcHCoACpAPkRGF2aWRPAoAP8wBQBFZNaQchbbAgRml4CYARJTIC4wkCAGNoCsBzZXQyNwYABsMR JTMERhPHMCC/CFUHsgKAETMI7wn3Oxgvdw4xESIMYGMAUAsJAWQzhjYWYAumIE9LLBz1Di4doAqi CoBBY3R1wQdAbHkgSSACIB6RJweAAHAFQHRvHyBhazplH4BoH/ABAQuAaXT6aQIgIAIQBcAgEAQA HdTYb2JqBZAFQCoUIAOBxSCwYx5yKiBiFDAOsFhyLiAHEB/weQhgIHphCcIgA/AgEB8gHqBwuQNg cG8AkCCyHdQiC4DcIGcJ8ASQB0AiHSAOwARjZQUxIk1BWC0AQUNDRVNTIj/PEMAfoCQCIUFuax0g IBDuYQVAIFghhWYhMx7QIfRvE/AEIB+RI0AgB3AlIXaVCYA/HdRJKqBzbx0gWx7AJSRlHdQd1CAu 0WQAb3QxZFN0cFApF9FFbgGgbB/wT0IASkVDVC1UWVCGRS54LtJTWU5UJ6CFMVRJMfBFR0VSAzBH AAAxCzQOZHVtJPBSGR9AZFYHQApQKDApXiwzPzcLIQEnMEIXwGO4aygxNh83LzgxRAQAcS/yKDIp CuM5Py7SXD59MPwnmC7QGDA1gC13zwUQDrAw/TIAVFU+8S7SXmMIcBgwAjAw/EQoAEOAUklQVElP Tjvf6SdwJ0Y4IiAvkgYAAZD9DrAnHtAqoh/wJVAAICOgLkIvICTQMtBUJDBuZPFG0k5FWEcAJUAm oSWY4zxcB0B3YXkEIBgwHlDtBKF2NbI1DykjoQOgKWD/DrAsMB9zP3MgA0qTSH80//M2AB8gdXMF QCLQUFAf8C8DkQSQA2AjkCIw/FJFckYy4EVOJ/BN/ydwSQJFVEAgODAyLjGARC0xOTk4OgZRgx5A IMIxNC44LlSgYjJRjTo6PTMBLw102nIeoDQ9Vx3UWQhhQVDfA3AHgAIwBCBHIS8FsSUpXx0gC1Af QBQgLKVBMBB4JS4aTwOgVGgIcHNki0ngHSBNSeAgMjMdIEcB0FSQVHA6MTZE8E2bEiET4WUDIF6Q Y0Y1gGcJ8EzxLyBlOh3UX+Y+IwZRH/BSRkNewDU3bjglECRAH/A5HSAmQVN4TUl2FFA+aS8QB5Fu cy8gLTB1cEYyO8VhuCI9P3MtHuNRhV1vXn8yMf9foggAIVAFQGqkYPpqo2Iw7zJxK3EscGUgZSxw BcAgIP8LEUWyJ4ku0GcIUYVsLm2E72rRK8Q/Ix7iOz8ZHtAFwF8/IwUAH0AOsB3FfXSgAAAAHgBC EAEAAAA6AAAAPDkxNzA2M0JBQjBEREIwNDNBRjVGQUE3M0M3QTgzNUQ0MTczMDJGQHdpbmRsb3Jk LldXUC5DT00+AAAAAwAJWQEAAAALAACACCAGAAAAAADAAAAAAAAARgAAAAADhQAAAAAAAAMAAoAI IAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwAFgAggBgAAAAAAwAAAAAAAAEYAAAAAUoUAAI5q AQAeACWACCAGAAAAAADAAAAAAAAARgAAAABUhQAAAQAAAAQAAAA5LjAAAwAmgAggBgAAAAAAwAAA AAAAAEYAAAAAAYUAAAAAAAALAC+ACCAGAAAAAADAAAAAAAAARgAAAAAOhQAAAAAAAAMAMIAIIAYA AAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwAygAggBgAAAAAAwAAAAAAAAEYAAAAAGIUAAAAAAAAe AEGACCAGAAAAAADAAAAAAAAARgAAAAA2hQAAAQAAAAEAAAAAAAAAHgBCgAggBgAAAAAAwAAAAAAA AEYAAAAAN4UAAAEAAAABAAAAAAAAAB4AQ4AIIAYAAAAAAMAAAAAAAABGAAAAADiFAAABAAAAAQAA AAAAAAALANqACCAGAAAAAADAAAAAAAAARgAAAAAGhQAAAAAAAAIB+A8BAAAAEAAAAAuEn6HJdNIR uagAqgC9hR4CAfoPAQAAABAAAAALhJ+hyXTSEbmoAKoAvYUeAgH7DwEAAABNAAAAAAAAADihuxAF 5RAaobsIACsqVsIAAG1zcHN0LmRsbAAAAAAATklUQfm/uAEAqgA32W4AAABEOlxFeGNoYW5nZVxv dXRsb29rLnBzdAAAAAADAP4PBQAAAAMADTT9NwAAAgF/AAEAAAAxAAAAMDAwMDAwMDAwQjg0OUZB MUM5NzREMjExQjlBODAwQUEwMEJEODUxRTY0MERFMzA0AAAAAAMABhDF2vfUAwAHEEgDAAADABAQ AAAAAAMAERABAAAAHgAIEAEAAABlAAAAT0ssT0ssT0tBQ1RVQUxMWUlPTkxZTUVBTlRUT01BS0VU SEVERUZJTklUSU9ORk9SVEhJU09CSkVDVCpTRU1BTlRJQ0FMTFkqQkVUVEVSQVJFWU9VQUdSRUVX SVRITVlQUk9QTwAAAACe+A== ------=_NextPart_000_0051_01C20496.8FB51510-- _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Sun May 26 02:42:46 2002 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 CAA17011 for ; Sun, 26 May 2002 02:42:46 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA24990 for bridge-archive@odin.ietf.org; Sun, 26 May 2002 02:43:07 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24983; Sun, 26 May 2002 02:43:06 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24946 for ; Sun, 26 May 2002 02:43:04 -0400 (EDT) Received: from web13108.mail.yahoo.com (web13108.mail.yahoo.com [216.136.174.153]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA17004 for ; Sun, 26 May 2002 02:42:43 -0400 (EDT) Message-ID: <20020526064304.86416.qmail@web13108.mail.yahoo.com> Received: from [194.90.136.135] by web13108.mail.yahoo.com via HTTP; Sat, 25 May 2002 23:43:04 PDT Date: Sat, 25 May 2002 23:43:04 -0700 (PDT) From: Ali Chanaui Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt To: alexr@nbase.co.il Cc: bridge-mib@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org Alex, Why we cannot make the object dot1dStpPortState read-write for this purpose? Ali On Thu, May 23, 2002 at 05:14:24PM +0200, Alex Ruzin wrote: > It seems to me, that the object dot1dStpPortEnable > doesn't reflect a *port > state* as it is defined > in "IEEE 802.1D-1998: Section 8.5.5.2"; rather it > correspondents to "Force port state" from Section 14.8.2.2. > I propose to discuss an option to: > 1) do this object "MAX-ACCESS write-only" > 2) set possible values as > SYNTAX INTEGER { > forceBlock(1), > forceDisable(2) > } > 3) change REFERENCE: "IEEE 802.1D-1998: Section 14.8.2.2" __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Mon May 27 01:15:04 2002 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 BAA03764 for ; Mon, 27 May 2002 01:15:04 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA18916 for bridge-archive@odin.ietf.org; Mon, 27 May 2002 01:15:26 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA18901; Mon, 27 May 2002 01:15:24 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA18872 for ; Mon, 27 May 2002 01:15:23 -0400 (EDT) Received: from agile.yagosys.com ([63.198.118.162]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03756 for ; Mon, 27 May 2002 01:14:59 -0400 (EDT) Received: (qmail 2673 invoked by uid 10041); 27 May 2002 05:15:20 -0000 Date: Sun, 26 May 2002 22:15:20 -0700 From: Michael MacFaden To: bridge-mib@ietf.org Subject: Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt Message-ID: <20020526221520.C2410@riverstonenet.com> References: <917063BAB0DDB043AF5FAA73C7A835D417302F@windlord.WWP.COM> <004f01c20485$cc0ab350$87885ac2@Alexr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004f01c20485$cc0ab350$87885ac2@Alexr> User-Agent: Mutt/1.3.22i X-Operating-System: GNU/Linux 2.4.18 Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org On Sun, May 26, 2002 at 09:20:20AM +0200, Alex Ruzin wrote: >Actually I only meant to make the definition for this >object *semantically* better. Are you agree with my proposition >"in general", except "MAX-ACCESS"? Do you think, that definition >of this object has to be improved? >If so, I propose > > dot1dStpPortEnable OBJECT-TYPE > SYNTAX INTEGER { > dummyReadValue(0), > forceBlock(1), > forceDisable(2) > } > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "'Force Port State' of the port. Both GET and GETNEXT operation > always return value dummyReadValue(0). An attempt to write the value > dummyReadValue(0) must cause an error." > REFERENCE > "IEEE 802.1D-1998: Section 14.8.2.2" > ::= { dot1dStpPortEntry 4 } > >Your comments and/or proposition, please? The operation of this object is clear but such a redefinition would not be allowed by IESG mib doctors as it is not backward compatible. If this definition were for a new object, then I don't see why there is a need for a dummyReadValue other than to create a write-only style access. The SMIv2 dropped write-only access for a purpose and as such most MIB doctors would discourage its use. I think dot1dStpPortEnable should be left as-is but the front matter should explain how this object was supposed to operate since it is clear that many vendors did not implement it according to the original authors intentions. Mike MacFaden _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Mon May 27 02:17:50 2002 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 CAA12726 for ; Mon, 27 May 2002 02:17:50 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA21378 for bridge-archive@odin.ietf.org; Mon, 27 May 2002 02:18:13 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA21365; Mon, 27 May 2002 02:18:12 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA21333 for ; Mon, 27 May 2002 02:18:10 -0400 (EDT) Received: from web13103.mail.yahoo.com (web13103.mail.yahoo.com [216.136.174.148]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA12720 for ; Mon, 27 May 2002 02:17:47 -0400 (EDT) Message-ID: <20020527061808.85590.qmail@web13103.mail.yahoo.com> Received: from [194.90.136.135] by web13103.mail.yahoo.com via HTTP; Sun, 26 May 2002 23:18:08 PDT Date: Sun, 26 May 2002 23:18:08 -0700 (PDT) From: Ali Chanaui Subject: Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-03.txt To: Michael MacFaden , bridge-mib@ietf.org Cc: stds-802-1@ieee.org In-Reply-To: <20020526221520.C2410@riverstonenet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org I have another question (it seems to me, it dedicated rather to stds-802-1@ieee.org). If Port has been done forceDisable(2) or disabled(2) - does this Port take place in Active Topology? I mean: does it forward frames, leran addresses? Does it participate in GVRP, etc.? Ali --- Michael MacFaden wrote: > On Sun, May 26, 2002 at 09:20:20AM +0200, Alex Ruzin > wrote: > >Actually I only meant to make the definition for > this > >object *semantically* better. Are you agree with my > proposition > >"in general", except "MAX-ACCESS"? Do you think, > that definition > >of this object has to be improved? > >If so, I propose > > > > dot1dStpPortEnable OBJECT-TYPE > > SYNTAX INTEGER { > > dummyReadValue(0), > > forceBlock(1), > > forceDisable(2) > > } > > MAX-ACCESS read-write > > STATUS current > > DESCRIPTION > > "'Force Port State' of the port. Both > GET and GETNEXT operation > > always return value > dummyReadValue(0). An attempt to write the value > > dummyReadValue(0) must cause an > error." > > REFERENCE > > "IEEE 802.1D-1998: Section 14.8.2.2" > > ::= { dot1dStpPortEntry 4 } > > > >Your comments and/or proposition, please? > > The operation of this object is clear but such a > redefinition > would not be allowed by IESG mib doctors as it is > not backward compatible. > > If this definition were for a new object, then I > don't see why there is > a need for a dummyReadValue other than to create a > write-only style access. > The SMIv2 dropped write-only access for a purpose > and as such most MIB > doctors would discourage its use. > > I think dot1dStpPortEnable should be left as-is but > the front matter > should explain how this object was supposed to > operate since it > is clear that many vendors did not implement it > according to > the original authors intentions. > > Mike MacFaden > > _______________________________________________ > Bridge-mib mailing list > Bridge-mib@ietf.org > https://www1.ietf.org/mailman/listinfo/bridge-mib __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Fri May 31 07:21:26 2002 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 HAA11527 for ; Fri, 31 May 2002 07:21:26 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA23948 for bridge-archive@odin.ietf.org; Fri, 31 May 2002 07:21:51 -0400 (EDT) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA23933; Fri, 31 May 2002 07:21:48 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA23871 for ; Fri, 31 May 2002 07:21:44 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11491; Fri, 31 May 2002 07:21:15 -0400 (EDT) Message-Id: <200205311121.HAA11491@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: bridge-mib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 31 May 2002 07:21:15 -0400 Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-00.txt Sender: bridge-mib-admin@ietf.org Errors-To: bridge-mib-admin@ietf.org X-Mailman-Version: 1.0 Precedence: bulk List-Id: X-BeenThere: bridge-mib@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Bridge MIB Working Group of the IETF. Title : Definitions for Port Access Control (IEEE 802.1X) MIB Author(s) : K. Norseth Filename : draft-ietf-bridge-8021x-00.txt Pages : 41 Date : 30-May-02 This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the operation of Port Access Control, based on the specification contained in Clause 8 and Clause 9 of the IEEE 802.1X standard. This clause includes a MIB module that is SNMPv2 SMI compliant. This standard defines a mechanism for Port-based network access control that makes use of the physical access characteristics of IEEE 802 LAN infrastructures in order to provide a means of authenticating and authorizing devices attached to a LAN port that has point-to-point connection characteristics, and of preventing access to that port in cases in which the authentication and authorization process fails. This standard is part of a family of standards for local and metropolitan area networks. This draft is written within the IEEE 802.1X working group and is being presented to the IETF for informational purposes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bridge-8021x-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-bridge-8021x-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-bridge-8021x-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020530104831.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-bridge-8021x-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-bridge-8021x-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20020530104831.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib