From daemon@optimus.ietf.org Tue Apr 2 05:54: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 FAA11723 for ; Tue, 2 Apr 2002 05:54:25 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id FAA02674 for bridge-archive@odin.ietf.org; Tue, 2 Apr 2002 05:54:27 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA02649; Tue, 2 Apr 2002 05:54:19 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA28999 for ; Tue, 2 Apr 2002 04:29:19 -0500 (EST) Received: from mlry.radlan.co.il ([212.117.141.35]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10535 for ; Tue, 2 Apr 2002 04:29:12 -0500 (EST) Received: by MLRY with Internet Mail Service (5.5.2653.19) id <21F2MG7A>; Tue, 2 Apr 2002 12:28:46 +0200 Message-ID: <42AB6BE23C29D511831E0002B3202488C29FC5@messenger.radlan.co.il> From: Sharon Meir To: "'bridge-mib@ietf.org'" Date: Tue, 2 Apr 2002 12:28:57 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Bridge-mib] draft-ietf-bridge-ext-v2-00 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 Hello, I have a question regarding dot1dPortRestrictedGroupRegistration which defined in the draft-ietf-bridge-ext-v2-00. ---------------------------------------------------------------------------- -------- ot1dPortRestrictedGroupRegistration OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "The state of Restricted Group Registration on this port. If the value of this control is true(1), then creation of a new dynamic entry is permitted only if there is a Static Filtering Entry for the VLAN concerned, in which the Registrar Administrative Control value is Normal Registration." REFERENCE "IEEE 802.1t clause 10.3.2.3, 14.10.1.3." DEFVAL { false } ---------------------------------------------------------------------------- ------------ My question is: Here it's define: "creation of a new dynamic entry is permitted..." While in IEEE 802.1t clause 10.3.2.3 it is define: "creation or modification..." Is it a mistake ? Thanks Sharon _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed Apr 3 03:40: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 DAA27277 for ; Wed, 3 Apr 2002 03:40:50 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id DAA04554 for bridge-archive@odin.ietf.org; Wed, 3 Apr 2002 03:40:51 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04530; Wed, 3 Apr 2002 03:40:35 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04498 for ; Wed, 3 Apr 2002 03:40:33 -0500 (EST) 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 DAA27270 for ; Wed, 3 Apr 2002 03:40:30 -0500 (EST) Received: from toucana.eur.3com.com (toucana.EUR.3Com.COM [140.204.220.50]) by columba.www.eur.3com.com with ESMTP id g338fxx00231; Wed, 3 Apr 2002 09:41:59 +0100 (BST) Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id g338eGc17565; Wed, 3 Apr 2002 09:40:16 +0100 (BST) Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256B90.002FC87A ; Wed, 3 Apr 2002 09:41:55 +0100 X-Lotus-FromDomain: 3COM From: "Les Bell" To: Michael MacFaden cc: bridge-mib@ietf.org Message-ID: <80256B90.002FC6F3.00@notesmta.eur.3com.com> Date: Wed, 3 Apr 2002 09:35:11 +0100 Subject: Re: [Bridge-mib] problems with dot1dStpPortDesignatedPort Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline 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 Mike MacFaden wrote: > In draft-ietf-bridge-bridgemib-smiv2-02.txt, > the managed object: > > dot1dStpPortDesignatedPort OBJECT-TYPE > SYNTAX OCTET STRING (SIZE (2)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The Port Identifier of > the port on the Designated > Bridge for this port's segment." > REFERENCE "IEEE 802.1D-1990: Section 4.5.5.7" > ::= { dot1dStpPortEntry 9 } > > has not been updated with text to > say what one should do if the bridge > has greater than 255 ports. > > I understand 802.1T has modified how these 16 bits are > being divided up, however I don't think this > object can be reused and must only report > on the range it is capable of reporting on. > > A new object would have to be added to represent > the new interpretation of the 16 bits in a port identifer. The dot1dStpPortDesignatedPort object is defined as an opaque octet string and it does not understand the priority and port number fields embedded within it. Therefore, it does not matter (to this MIB object) that the boundary between them has changed. > Testing with existing fielded products > has shown that the priority bits often just > get shifted out which strikes me as rather broken. The products with this behaviour are broken, not the MIB. > So is is possible that some prose be added to > the front matter about what a conforming application > should expect from a device implementing the BRIDGE-MIB > when it device has > 255 ports? I did not think this was necessary. If you have some proposed text, we can discuss it. > Thanks, > Mike MacFaden Les... _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed Apr 3 19:06:56 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 TAA19523 for ; Wed, 3 Apr 2002 19:06:55 -0500 (EST) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id TAA08008 for bridge-archive@odin.ietf.org; Wed, 3 Apr 2002 19:06:52 -0500 (EST) Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07994; Wed, 3 Apr 2002 19:06:45 -0500 (EST) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA07961 for ; Wed, 3 Apr 2002 19:06:43 -0500 (EST) Received: from agile.yagosys.com (host3.riverstonenet.com [63.113.148.3]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA19516 for ; Wed, 3 Apr 2002 19:06:39 -0500 (EST) Received: (qmail 5925 invoked by uid 10041); 4 Apr 2002 00:06:09 -0000 Date: Wed, 3 Apr 2002 16:06:09 -0800 From: Michael MacFaden To: Les Bell Cc: bridge-mib@ietf.org Subject: Re: [Bridge-mib] problems with dot1dStpPortDesignatedPort Message-ID: <20020403160609.F4479@riverstonenet.com> References: <80256B90.002FC6F3.00@notesmta.eur.3com.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80256B90.002FC6F3.00@notesmta.eur.3com.com> 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 Wed, Apr 03, 2002 at 09:35:11AM +0100, Les Bell wrote: >> In draft-ietf-bridge-bridgemib-smiv2-02.txt, >> the managed object: >> >> dot1dStpPortDesignatedPort OBJECT-TYPE >> SYNTAX OCTET STRING (SIZE (2)) >> MAX-ACCESS read-only >> STATUS current >> DESCRIPTION >> "The Port Identifier of >> the port on the Designated >> Bridge for this port's segment." >> REFERENCE "IEEE 802.1D-1990: Section 4.5.5.7" >> ::= { dot1dStpPortEntry 9 } > >The dot1dStpPortDesignatedPort object is defined as an opaque >octet string and it does not understand the priority and port >number fields embedded within it. Therefore, it does not matter >(to this MIB object) that the boundary between them has changed. How did you reach that conclusion? What I see is an object that is clearly a 'Port Identifier' which is well defined in the base 802.1D 1990 spec. If dot1dStpPortDesignatedPort is opaque, how can it be used at all in an interoperable fashion? >> So is is possible that some prose be added to >> the front matter about what a conforming application >> should expect from a device implementing the BRIDGE-MIB >> when it device has > 255 ports? > >I did not think this was necessary. I agree if as you say, the octet string is opaque. >If you have some proposed text, we can discuss it. If the octet string is not opaque, then something like this would lead to well defined behavior that enahances interoperability. 99.99 Special cases: dot1dStpPortDesignatedPort If a device has greater than 255 ports, the Port Identifier encoding can not be done with the bit allocations as defined prior to IEEE 802.1T. dot1dStpPortDesignatedPort object instances greater than 255 are not visible to management queries. Mike MacFaden _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed Apr 10 01:58:14 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 BAA03738 for ; Wed, 10 Apr 2002 01:58:14 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id BAA28502 for bridge-archive@odin.ietf.org; Wed, 10 Apr 2002 01:58:17 -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 BAA28448; Wed, 10 Apr 2002 01:56:44 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA28421 for ; Wed, 10 Apr 2002 01:56:43 -0400 (EDT) Received: from c001.snv.cp.net (c001-h001.c001.snv.cp.net [209.228.32.115]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03727 for ; Wed, 10 Apr 2002 01:56:38 -0400 (EDT) Received: (cpmta 4113 invoked from network); 9 Apr 2002 22:56:08 -0700 Received: from 24.221.253.53 (HELO kcn) by smtp.register-admin.com (209.228.32.115) with SMTP; 9 Apr 2002 22:56:08 -0700 X-Sent: 10 Apr 2002 05:56:08 GMT Message-ID: <011501c1e054$9aa98480$850f880a@kcn> From: "K.C. Norseth" To: Date: Tue, 9 Apr 2002 23:57:30 -0600 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Transfer-Encoding: 7bit Subject: [Bridge-mib] 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 Content-Transfer-Encoding: 7bit Hello folks, I have v3 of the Definitions of Managed Objects for Bridges completed. I have not submitted it to the IETF where we have a couple of issues being discussed. They draft can be found at: http://norseth.org/ietf/bridgemib/draft-ietf-bridge-bridgemib-smiv2-03.txt The main changes were the references to the 1998 IEEE draft instead of the 1990 draft. The sections have been updated also. We have the following issues to resolve still: dot1dStpPortDesignatedPort - Mike Mcfadden A new object would have to be added to represent the new interpretation of the 16 bits in a port identifer. Is it enough to say add that that the value should be less than 255 and if it > 255 the object should return noSuchInstance? We should not be trying to fix implementations that did not implement it right.? What do people say? K.C. _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed Apr 10 01:59:59 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 BAA03786 for ; Wed, 10 Apr 2002 01:59:59 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA28604 for bridge-archive@odin.ietf.org; Wed, 10 Apr 2002 02:00:02 -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 CAA28595; Wed, 10 Apr 2002 02:00:01 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA28544 for ; Wed, 10 Apr 2002 01:59:59 -0400 (EDT) Received: from c001.snv.cp.net (c001-h005.c001.snv.cp.net [209.228.32.119]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA03781 for ; Wed, 10 Apr 2002 01:59:55 -0400 (EDT) Received: (cpmta 6649 invoked from network); 9 Apr 2002 22:59:27 -0700 Received: from 24.221.253.53 (HELO kcn) by smtp.register-admin.com (209.228.32.119) with SMTP; 9 Apr 2002 22:59:27 -0700 X-Sent: 10 Apr 2002 05:59:27 GMT Message-ID: <011d01c1e055$10fafa10$850f880a@kcn> From: "K.C. Norseth" To: Date: Wed, 10 Apr 2002 00:00:49 -0600 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Transfer-Encoding: 7bit Subject: [Bridge-mib] Definitions for Port Access Control (IEEE 802.1X) 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 Hello folks, We have received permission to reprint the 802.1x mib in the IETF. The draft I prepared can be found at: http://norseth.org/ietf/bridgemib/draft-ietf-bridge-8021x-00.txt before I submit it to the IETF, I wold like comments on it. This is a reprint of the IEEE mib, so we are not at liberty to change the actual mib. If I goofed up on it, if I am missing something or did not follow proper precedure, let me know. K.C. _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed Apr 10 02:41:35 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 CAA12568 for ; Wed, 10 Apr 2002 02:41:35 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA01085 for bridge-archive@odin.ietf.org; Wed, 10 Apr 2002 02:41: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 CAA01065; Wed, 10 Apr 2002 02:41:37 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA09291 for ; Tue, 9 Apr 2002 14:03:42 -0400 (EDT) Received: from sjs2kavd.st-johns.org (user-132.st-johns.org [209.7.195.132] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA14447 for ; Tue, 9 Apr 2002 14:03:39 -0400 (EDT) Received: FROM st-johns.org BY sjs2kavd.st-johns.org ; Tue Apr 09 12:57:54 2002 -0500 Received: from SJSGWIA-Message_Server by st-johns.org with Novell_GroupWise; Tue, 09 Apr 2002 13:03:08 -0500 Message-Id: X-Mailer: Novell GroupWise 5.5.5 Date: Tue, 09 Apr 2002 13:02:42 -0500 From: "Bill Halpin" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA09292 Subject: [Bridge-mib] Location Information 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 I hope this is the correct list to pose my question? If it isn't could someone please point me right direction and I apologize! I would like to keep track of our horizontal cabling on our switches. Is there a field at the port level of a switch to do this? Example: Port #1 on switch X.X.X.X is connected to location 100-01 out of communication closet C-1. I am using the system location field to keep track of the closet information a switch is installed in. I am using ANSI/TIA/EIA 568 cabling standard so I know what cable comes out of what closet. I would like to be able to query the switch in the C-1 closet and see what locations are cross-connected to it. I hope this makes sense and thank you for any information you could provide! Bill Halpin RCDD/LAN Specialist Network Engineer St. John's Hospital 217-544-64664 ext: 44297 bhalpin@st-johns.org _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed Apr 10 06:22:49 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 GAA14754 for ; Wed, 10 Apr 2002 06:22:48 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id GAA11538 for bridge-archive@odin.ietf.org; Wed, 10 Apr 2002 06:22: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 GAA11526; Wed, 10 Apr 2002 06:22: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 GAA11492 for ; Wed, 10 Apr 2002 06:22:46 -0400 (EDT) Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14748 for ; Wed, 10 Apr 2002 06:22:43 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3AAMD817847 for ; Wed, 10 Apr 2002 06:22:14 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2GN74WGG>; Wed, 10 Apr 2002 12:22:13 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: "K.C. Norseth" , bridge-mib@ietf.org Subject: RE: [Bridge-mib] Definitions for Port Access Control (IEEE 802.1X ) MIB Date: Wed, 10 Apr 2002 12:22:11 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" 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 Well, have you tried to run it trhough a MIB compiler or syntax-checker? I get various errors/warnings. Bert > -----Original Message----- > From: K.C. Norseth [mailto:kcn@norseth.com] > Sent: Wednesday, April 10, 2002 8:01 AM > To: bridge-mib@ietf.org > Subject: [Bridge-mib] Definitions for Port Access Control > (IEEE 802.1X) > MIB > > > Hello folks, > > We have received permission to reprint the 802.1x mib in the > IETF. The > draft I prepared can be found at: > http://norseth.org/ietf/bridgemib/draft-ietf-bridge-8021x-00.txt > > before I submit it to the IETF, I wold like comments on it. This is a > reprint of the IEEE mib, so we are not at liberty to change > the actual mib. > If I goofed up on it, if I am missing something or did not > follow proper > precedure, let me know. > > K.C. > > > _______________________________________________ > 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 Wed Apr 10 08:41:31 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 IAA17380 for ; Wed, 10 Apr 2002 08:41:30 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA19078 for bridge-archive@odin.ietf.org; Wed, 10 Apr 2002 08:41:34 -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 IAA19067; Wed, 10 Apr 2002 08:41:33 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA19036 for ; Wed, 10 Apr 2002 08:41:29 -0400 (EDT) Received: from ctron-dnm.ctron.com (firewall-user@ctron-dnm.enterasys.com [12.25.1.120]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17374 for ; Wed, 10 Apr 2002 08:41:24 -0400 (EDT) Received: (from uucp@localhost) by ctron-dnm.ctron.com (8.8.7/8.8.7) id IAA09862; Wed, 10 Apr 2002 08:51:30 -0400 (EDT) Received: from unknown(134.141.77.96) by ctron-dnm.ctron.com via smap (4.1) id xma009846; Wed, 10 Apr 02 08:50:55 -0400 Received: by cnc-exc1.enterasys.com with Internet Mail Service (5.5.2653.19) id <2GYJ6ZZ6>; Wed, 10 Apr 2002 08:38:49 -0400 Message-ID: <59358A738F45D51186A30008C74CE250DA0886@slc-exc1.ctron.com> From: "Norseth, KC" To: "'Wijnen, Bert (Bert)'" , "K.C. Norseth" , bridge-mib@ietf.org Subject: RE: [Bridge-mib] Definitions for Port Access Control (IEEE 802.1X ) MIB Date: Wed, 10 Apr 2002 08:40:08 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1E08C.D8EE6570" 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 message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1E08C.D8EE6570 Content-Type: text/plain Hi Bert, I had run it, this mib was even implemented as is. Maybe I clipped something in putting it into the verbage. Which mib checker did you use? K.C. |-----Original Message----- |From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] |Sent: Wednesday, April 10, 2002 4:22 AM |To: K.C. Norseth; bridge-mib@ietf.org |Subject: RE: [Bridge-mib] Definitions for Port Access Control |(IEEE 802.1X ) MIB | | |Well, have you tried to run it trhough a MIB compiler or |syntax-checker? I get various errors/warnings. | |Bert | |> -----Original Message----- |> From: K.C. Norseth [mailto:kcn@norseth.com] |> Sent: Wednesday, April 10, 2002 8:01 AM |> To: bridge-mib@ietf.org |> Subject: [Bridge-mib] Definitions for Port Access Control |> (IEEE 802.1X) |> MIB |> |> |> Hello folks, |> |> We have received permission to reprint the 802.1x mib in the |> IETF. The |> draft I prepared can be found at: |> http://norseth.org/ietf/bridgemib/draft-ietf-bridge-8021x-00.txt |> |> before I submit it to the IETF, I wold like comments on it. |This is a |> reprint of the IEEE mib, so we are not at liberty to change |the actual |> mib. If I goofed up on it, if I am missing something or did not |> follow proper |> precedure, let me know. |> |> K.C. |> |> |> _______________________________________________ |> 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 | ------_=_NextPart_001_01C1E08C.D8EE6570 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [Bridge-mib] Definitions for Port Access Control (IEEE = 802.1X ) MIB

Hi Bert,

I had run it, this mib was even implemented as = is.  Maybe I clipped something in putting it into the = verbage.  Which mib checker did you use?

K.C.


|-----Original Message-----
|From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] =
|Sent: Wednesday, April 10, 2002 4:22 AM
|To: K.C. Norseth; bridge-mib@ietf.org
|Subject: RE: [Bridge-mib] Definitions for Port = Access Control
|(IEEE 802.1X ) MIB
|
|
|Well, have you tried to run it trhough a MIB = compiler or
|syntax-checker? I get various = errors/warnings.
|
|Bert
|
|> -----Original Message-----
|> From: K.C. Norseth [mailto:kcn@norseth.com]
|> Sent: Wednesday, April 10, 2002 8:01 AM
|> To: bridge-mib@ietf.org
|> Subject: [Bridge-mib] Definitions for Port = Access Control
|> (IEEE 802.1X)
|> MIB
|>
|>
|> Hello folks,
|>
|> We have received permission to reprint the = 802.1x mib in the
|> IETF.  The
|> draft I prepared can be found at:
|> http://norseth.org/ietf/bridgemib/draft-ietf-bridge-80= 21x-00.txt
|>
|> before I submit it to the IETF, I wold like = comments on it. 
|This is a
|> reprint of the IEEE mib, so we are not at = liberty to change
|the actual
|> mib. If I goofed up on it,  if I am = missing something or did not
|> follow proper
|> precedure, let me know.
|>
|> K.C.
|>
|>
|> = _______________________________________________
|> Bridge-mib mailing list
|> Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib<= /FONT>
|>
|
|_______________________________________________
|Bridge-mib mailing list
|Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib<= /FONT>
|

------_=_NextPart_001_01C1E08C.D8EE6570-- _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@optimus.ietf.org Wed Apr 10 09:54:40 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 JAA19379 for ; Wed, 10 Apr 2002 09:54:35 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA23235 for bridge-archive@odin.ietf.org; Wed, 10 Apr 2002 09:54:39 -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 JAA23222; Wed, 10 Apr 2002 09:54:37 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA23184 for ; Wed, 10 Apr 2002 09:54:35 -0400 (EDT) Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19372 for ; Wed, 10 Apr 2002 09:54:23 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id g3ADsNR26183 for ; Wed, 10 Apr 2002 09:54:24 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2GN749CA>; Wed, 10 Apr 2002 15:54:23 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: "Norseth, KC" , "K.C. Norseth" , bridge-mib@ietf.org Subject: RE: [Bridge-mib] Definitions for Port Access Control (IEEE 802.1X ) MIB Date: Wed, 10 Apr 2002 15:54:21 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1E097.37898F10" 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 message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C1E097.37898F10 Content-Type: text/plain I used SMICng ... did not try SMIlint yet, but that is anotehr good one to run against. Bert -----Original Message----- From: Norseth, KC [mailto:knorseth@enterasys.com] Sent: Wednesday, April 10, 2002 2:40 PM To: 'Wijnen, Bert (Bert)'; K.C. Norseth; bridge-mib@ietf.org Subject: RE: [Bridge-mib] Definitions for Port Access Control (IEEE 802.1X ) MIB Hi Bert, I had run it, this mib was even implemented as is. Maybe I clipped something in putting it into the verbage. Which mib checker did you use? K.C. |-----Original Message----- |From: Wijnen, Bert (Bert) [ mailto:bwijnen@lucent.com ] |Sent: Wednesday, April 10, 2002 4:22 AM |To: K.C. Norseth; bridge-mib@ietf.org |Subject: RE: [Bridge-mib] Definitions for Port Access Control |(IEEE 802.1X ) MIB | | |Well, have you tried to run it trhough a MIB compiler or |syntax-checker? I get various errors/warnings. | |Bert | |> -----Original Message----- |> From: K.C. Norseth [ mailto:kcn@norseth.com ] |> Sent: Wednesday, April 10, 2002 8:01 AM |> To: bridge-mib@ietf.org |> Subject: [Bridge-mib] Definitions for Port Access Control |> (IEEE 802.1X) |> MIB |> |> |> Hello folks, |> |> We have received permission to reprint the 802.1x mib in the |> IETF. The |> draft I prepared can be found at: |> http://norseth.org/ietf/bridgemib/draft-ietf-bridge-8021x-00.txt |> |> before I submit it to the IETF, I wold like comments on it. |This is a |> reprint of the IEEE mib, so we are not at liberty to change |the actual |> mib. If I goofed up on it, if I am missing something or did not |> follow proper |> precedure, let me know. |> |> K.C. |> |> |> _______________________________________________ |> 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 | ------_=_NextPart_001_01C1E097.37898F10 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [Bridge-mib] Definitions for Port Access Control (IEEE = 802.1X ) MIB
I used=20 SMICng ... did not try SMIlint yet, but that is anotehr good one=20 to
run=20 against.
Bert
-----Original Message-----
From: Norseth, KC=20 [mailto:knorseth@enterasys.com]
Sent: Wednesday, April 10, = 2002 2:40=20 PM
To: 'Wijnen, Bert (Bert)'; K.C. Norseth;=20 bridge-mib@ietf.org
Subject: RE: [Bridge-mib] Definitions = for Port=20 Access Control (IEEE 802.1X ) MIB

Hi Bert,

I had run it, this mib was even implemented as = is.  Maybe=20 I clipped something in putting it into the verbage.  Which mib = checker=20 did you use?

K.C.


|-----Original Message-----
|From:=20 Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]=20
|Sent: Wednesday, April 10, 2002 4:22 = AM=20
|To: K.C. Norseth; bridge-mib@ietf.org =
|Subject: RE: [Bridge-mib] Definitions for Port Access = Control=20
|(IEEE 802.1X ) MIB
|=20
|
|Well, have you tried = to run it=20 trhough a MIB compiler or
|syntax-checker? = I get=20 various errors/warnings.
|
|Bert
|
|>=20 -----Original Message-----
|> From: K.C. = Norseth=20 [mailto:kcn@norseth.com] =
|> Sent: Wednesday, April 10, 2002 8:01 AM =
|> To: bridge-mib@ietf.org
|> Subject:=20 [Bridge-mib] Definitions for Port Access Control
|>=20 (IEEE 802.1X)
|> MIB
|>=20
|>
|> Hello = folks,
|>
|> We have=20 received permission to reprint the 802.1x mib in the
|> IETF.  The
|> draft = I prepared=20 can be found at:
|> http://norseth.org/ietf/bridgemib/draft-ietf-bridge-8021x-00.txt=20
|>
|> before I = submit it to the=20 IETF, I wold like comments on it. 
|This is a=20
|> reprint of the IEEE mib, so we are = not at=20 liberty to change
|the actual =
|> mib. If I goofed up on it,  if I am missing = something or did=20 not
|> follow proper
|>=20 precedure, let me know.
|> =
|> K.C.
|>
|>=20
|>=20 _______________________________________________
|>=20 Bridge-mib mailing list
|> = Bridge-mib@ietf.org https://www1.= ietf.org/mailman/listinfo/bridge-mib=20
|>
|
|_______________________________________________ =
|Bridge-mib mailing list
|Bridge-mib@ietf.org=20 https://www1.= ietf.org/mailman/listinfo/bridge-mib=20
|

------_=_NextPart_001_01C1E097.37898F10-- _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From daemon@ns.ietf.org Mon Apr 22 11:13:58 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 LAA28649 for ; Mon, 22 Apr 2002 11:13:58 -0400 (EDT) Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA20715 for bridge-archive@odin.ietf.org; Mon, 22 Apr 2002 11:14:02 -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 LAA20701; Mon, 22 Apr 2002 11:13:59 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA20672 for ; Mon, 22 Apr 2002 11:13:57 -0400 (EDT) Received: from c001.snv.cp.net (c001-h005.c001.snv.cp.net [209.228.32.119]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA28644 for ; Mon, 22 Apr 2002 11:13:53 -0400 (EDT) Received: (cpmta 8232 invoked from network); 22 Apr 2002 08:13:25 -0700 Received: from 24.221.253.53 (HELO kcn) by smtp.register-admin.com (209.228.32.119) with SMTP; 22 Apr 2002 08:13:25 -0700 X-Sent: 22 Apr 2002 15:13:25 GMT Message-ID: <004901c1ea10$3e8c6850$850f880a@kcn> From: "K.C. Norseth" To: Cc: "K.C. Norseth" References: <011d01c1e055$10fafa10$850f880a@kcn> Date: Mon, 22 Apr 2002 09:13:20 -0600 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Content-Transfer-Encoding: 7bit Subject: [Bridge-mib] Definitions for Port Access Control (IEEE 802.1X) 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 Hello folks, 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. Norseth Norseth Professional Consulting kcn@norseth.com Phone: 801.546.3316 Our questions to customers may need to change. Perhaps the questions we should be asking are less "What do you want?" and more "What are the problems you need solved?" These types of questions and answers become more important as we migrate from fixes to solutions. _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib