From mailnull@www1.ietf.org Wed Dec 4 05:21:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04810 for ; Wed, 4 Dec 2002 05:21:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB4AOFS06537 for bridge-archive@odin.ietf.org; Wed, 4 Dec 2002 05:24:15 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4AOBv06529; Wed, 4 Dec 2002 05:24:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gB4ANRv06503 for ; Wed, 4 Dec 2002 05:23:27 -0500 Received: from columba.www.eur.3com.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04766 for ; Wed, 4 Dec 2002 05:20:36 -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 gB4AP3Rc011505 for ; Wed, 4 Dec 2002 10:25:03 GMT Received: from notesmta.eur.3com.com (eurmta1.EUR.3Com.COM [140.204.220.206]) by toucana.eur.3com.com with SMTP id gB4AOdk10272 for ; Wed, 4 Dec 2002 10:24:39 GMT Received: by notesmta.eur.3com.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 80256C85.003913B2 ; Wed, 4 Dec 2002 10:23:25 +0000 X-Lotus-FromDomain: 3COM From: "Les Bell" To: bridge-mib@ietf.org Message-ID: <80256C85.0039126D.00@notesmta.eur.3com.com> Date: Wed, 4 Dec 2002 10:23:12 +0000 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Bridge-mib] Re: Begin WG Last Call - draft-ietf-bridge-8021x-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: , New guidelines from the RFC-Editor require that the Refences section be split into two parts, "Normative References" and "Informative References". See http://www.rfc-editor.org/policy.html for details. Les... _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From mailnull@www1.ietf.org Wed Dec 11 08:01:49 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03091 for ; Wed, 11 Dec 2002 08:01:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBBD4Fm24988 for bridge-archive@odin.ietf.org; Wed, 11 Dec 2002 08:04:15 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBD48v24981; Wed, 11 Dec 2002 08:04:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBD3bv24955 for ; Wed, 11 Dec 2002 08:03:37 -0500 Received: from iere.net.avaya.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03057 for ; Wed, 11 Dec 2002 08:00:40 -0500 (EST) Received: from iere.net.avaya.com (localhost [127.0.0.1]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id gBBD17E18949 for ; Wed, 11 Dec 2002 08:01:07 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by iere.net.avaya.com (8.11.2/8.9.3) with ESMTP id gBBD16C18933 for ; Wed, 11 Dec 2002 08:01:06 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Bridge-mib] Begin WG Last Call - draft-ietf-bridge-8021x-00.txt Date: Wed, 11 Dec 2002 15:03:33 +0200 Message-ID: Thread-Topic: [Bridge-mib] Begin WG Last Call - draft-ietf-bridge-8021x-00.txt Thread-Index: AcKVYPuHDPJhaovfRduynuWDyXZhKgLso8eg From: "Romascanu, Dan (Dan)" To: "Les Bell" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBBD3bv24956 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: 8bit As the scope of this document is to produce a replica of the MIB defined in the IEEE document, I will not refer my comments to the MIB itself, but to the surrounding IETF-ish envelope. I have one fundamental issue, and a few editorials. The fundamental one: I think that the Security Considerations section is much too weak taking into account the scope of the IEEE 802.1X standard. We need to fix this before it gets under the IESG scrutiny. The security section needs to mention the fact that the standard modeled by this MIB has a strong security functionality. It needs to list explicitly the objects with MAX-ACCESS of read-write or read-create that if be potentially written by a malicious attacker can endanger the security by allowing access to the layer 2 network by un-authorized users. It also needs to mention that some of the objects (even of those with MAX-ACCESS clause of read-only) if exposed can allow for security holes in the access to the network to be exposed to un-authorized viewers. Now the editorial issues: 1. page 3, section 2 - the second paragraph seems broken in syntax, and content - Source Route and transparent are not modes, by rather methods. They happen to be the ones standardized in IEEE 802, but there are at least two other methods (translation and encapsulation) which are not covered by IEEE 802 standards. 2. Formatting of section 3, paragraph 1 seems broken 3. Same for section 3.1 4. The numbering of some of the objects (9.4.3, 9.4.4, etc.) in section 3.1 seems out of context 5. Section 3.3 and following - the term 'System' is used here, without a clear explanation of what it means 6. I think that it would help to define shortly (or at least refer to the IEEE standard) the supplicant and authenticator 7. Section 3.6 - there seems to be a mis-spelling of an object name referred from RFC 2863 8. Section 6 - IEEE is duplicated 9. Section 7 - need to divide references into normative and non-normative. Thanks, Dan > -----Original Message----- > From: Les Bell [mailto:Les_Bell@eur.3com.com] > Sent: Tuesday, November 26, 2002 5:24 PM > To: bridge-mib@ietf.org > Subject: [Bridge-mib] Begin WG Last Call - > draft-ietf-bridge-8021x-00.txt > > > > > > Hi, > > The Bridge MIB WG has completed work on the "Definitions for > Port Access Control > (IEEE 802.1X) MIB". This memo proposes to re-publish the > Port Access Entity > MIB, as defined in IEEE 802.1X, in an Informational RFC, for > the convenience of > the IETF community. > > The WG proposes that the I-D 'draft-ietf-bridge-8021x-00.txt' > is the completed > version of this document. The WG members are strongly urged > to review this > document as soon as possible, and express any concerns, or > identify any errors, in an email to the Bridge MIB WG mailing list. > > Unless there are strong objections, published on the WG > mailing list by December > 11, 2002, this document will be forwarded to the OPS Area > Directors for > consideration to publish as an Informational RFC. > > Please send all comments to the WG mailing list at > bridge-mib@ietf.org. > > Thanks, > Les... > > > _______________________________________________ > 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 mailnull@www1.ietf.org Wed Dec 11 08:03:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03210 for ; Wed, 11 Dec 2002 08:03:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBBD6PF25114 for bridge-archive@odin.ietf.org; Wed, 11 Dec 2002 08:06:25 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBD62v25105; Wed, 11 Dec 2002 08:06:02 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBD5vv25088 for ; Wed, 11 Dec 2002 08:05:57 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03172; Wed, 11 Dec 2002 08:02:59 -0500 (EST) Message-Id: <200212111302.IAA03172@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: Wed, 11 Dec 2002 08:02:59 -0500 Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-bridgemib-smiv2-04.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: , --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-04.txt Pages : 38 Date : 2002-12-9 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-04.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-04.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-04.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: <2002-12-9150019.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-bridge-bridgemib-smiv2-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-bridge-bridgemib-smiv2-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-12-9150019.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From mailnull@www1.ietf.org Wed Dec 18 15:22:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17906 for ; Wed, 18 Dec 2002 15:22:01 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBIKOaH28650 for bridge-archive@odin.ietf.org; Wed, 18 Dec 2002 15:24:36 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBIKNav28629; Wed, 18 Dec 2002 15:23:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBIKMgv28606 for ; Wed, 18 Dec 2002 15:22:42 -0500 Received: from wry.lachman.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17891 for ; Wed, 18 Dec 2002 15:19:35 -0500 (EST) Received: from medved by wry.lachman.com with local-smtp (Exim 3.12 #1 (Debian)) id 18Oki9-0003pj-00; Wed, 18 Dec 2002 14:22:33 -0600 Date: Wed, 18 Dec 2002 14:22:33 -0600 (CST) From: Pat Medved To: bridge-mib@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Bridge-mib] Portlist in RFC2764 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: , I noticed the portlist in rfc2764. I've seen this same thing in other Vendors MIbs as well. I was wondering what these port numbers are. If they are ports 1-256, what do those numbers map to on the switch itself? I was trying to find the correlation between these ports and the ports in the bridge MIB itself. Also, if there is only 32 octets, what goes in this list if more than 256 ports are on a bridge? I didn't see the correlation in this MIB. Thanks, Pat Pat Medved medved@lachman.com _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From mailnull@www1.ietf.org Thu Dec 19 04:19:03 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12133 for ; Thu, 19 Dec 2002 04:19:03 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBJ9Ljt12841 for bridge-archive@odin.ietf.org; Thu, 19 Dec 2002 04:21:45 -0500 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBJ9Lfv12833; Thu, 19 Dec 2002 04:21:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBJ9Kwv12790 for ; Thu, 19 Dec 2002 04:20:58 -0500 Received: from agile.yagosys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA12126 for ; Thu, 19 Dec 2002 04:17:45 -0500 (EST) Received: (qmail 4255 invoked by uid 10041); 19 Dec 2002 09:20:45 -0000 Date: Thu, 19 Dec 2002 01:20:45 -0800 From: Michael MacFaden To: Pat Medved Cc: bridge-mib@ietf.org Subject: Re: [Bridge-mib] Portlist in RFC2764 Message-ID: <20021219092045.GC4160@riverstonenet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Operating-System: GNU/Linux 2.4.18 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: , On Wed, Dec 18, 2002 at 02:22:33PM -0600, Pat Medved wrote: >I noticed the portlist in rfc2764. I've seen this same thing in other >Vendors MIbs as well. I was wondering what these port numbers are. > >If they are ports 1-256, what do those numbers map to on the switch >itself? I was trying to find the correlation between these ports >and the ports in the bridge MIB itself. Have a look at http://www.nanog.org/mtg-0102/ppt/mibs/sld082.htm In short, dot1dBasePortNum are typically mapped to an ifIndex. Then from ifIndex you can check with either an entity mib or an enterprise mib module to locate the vendor port identifier. >Also, if there is only 32 octets, what goes in this list if more than 256 >ports are on a bridge? PortList TC uses a plain OCTET STRING, it can be larger than 32 octets. See rfc 2578 section 7.1.2. Regards, Mike MacFaden _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib