From exim@www1.ietf.org Tue Nov 4 10:25:20 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18310 for ; Tue, 4 Nov 2003 10:25:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH33G-0003A8-7x for bridge-archive@odin.ietf.org; Tue, 04 Nov 2003 10:25:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA4FP2Be012153 for bridge-archive@odin.ietf.org; Tue, 4 Nov 2003 10:25:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH33F-00039m-ER; Tue, 04 Nov 2003 10:25:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AH32M-00038P-DF for bridge-mib@optimus.ietf.org; Tue, 04 Nov 2003 10:24:07 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18259 for ; Tue, 4 Nov 2003 10:23:53 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AH32K-0006tc-00 for bridge-mib@ietf.org; Tue, 04 Nov 2003 10:24:04 -0500 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AH32J-0006tP-00 for bridge-mib@ietf.org; Tue, 04 Nov 2003 10:24:03 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hA4FNTN24187 for ; Tue, 4 Nov 2003 09:23:29 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id ; Tue, 4 Nov 2003 16:23:27 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502D94F94@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "K.C. Norseth" , Les Bell , "C. M. Heard" Cc: bridge-mib@ietf.org, Kenyon C Norseth Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03p.txt Date: Tue, 4 Nov 2003 16:23:25 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" 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: , Some comments that I may not have vented earlier. - Abstract talks about "this standard" a few times. I think you mean "This IEEE 802.1X standard". Probably better to spell that out every time, otherwise people may read it as "this standard as specified in this document" - last para in abstract. s/This draft/This document/ Reads much better once it becomes an RFC - Did we discuss section 1 before? Why would we not make it in sync with the standard MIB boilerplate that we use these days? I believe Mike has made the same comments - Mike has already commented on the REVISION and LAST-UPDATED dates, and how to document the various revisions. I agree with that, except REVISION "200101160000Z" -- Jan 16th, 2001 DESCRIPTION "The initial and authoritative version as published at: Why is that "older" version authoritative? It has bugs that we're fixing, does it not? Can we just keep it at "The initial version as piblished at:" ?? With the current "authoritative", I would wonder what to do with this one, since it is not authoritative anyway? - I wonder about section 11. Should we add a note to RFC-Editor to remove it when RFC gets published? I thinks we should! Other than that, I support and agree with the comments made by Mike on Sept 9th (and posted on the bridge wg list) Thanks, Bert > -----Original Message----- > From: K.C. Norseth [mailto:kcn@norseth.com] > Sent: dinsdag 9 september 2003 6:39 > To: Les Bell; C. M. Heard > Cc: bridge-mib@ietf.org; Kenyon C Norseth > Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.txt > > > Folks, saved as draft-ietf-bridge-8021x-03p.txt > > Here is the latest proposed revision to draft-ietf-bridge-8021x-03 > > I have added the changes we have been discussing about > copyright. I have > not added the page formatting on this revison yet. I also > have not compiled > it yet because I didn't have access to libsmi this weekend. > > How is this? Comments, suggestions? > > K.C. > _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Thu Nov 6 03:05:21 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27869 for ; Thu, 6 Nov 2003 03:05:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHf8a-0003NH-2x for bridge-archive@odin.ietf.org; Thu, 06 Nov 2003 03:05:04 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA68532d012959 for bridge-archive@odin.ietf.org; Thu, 6 Nov 2003 03:05:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHf8Y-0003Ml-Qy; Thu, 06 Nov 2003 03:05:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHf8L-0003MH-Rl for bridge-mib@optimus.ietf.org; Thu, 06 Nov 2003 03:04:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27860 for ; Thu, 6 Nov 2003 03:04:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHf8H-0004S6-00 for bridge-mib@ietf.org; Thu, 06 Nov 2003 03:04:45 -0500 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHf8H-0004S3-00 for bridge-mib@ietf.org; Thu, 06 Nov 2003 03:04:45 -0500 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id hA684dD04464; Thu, 6 Nov 2003 00:04:40 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 6 Nov 2003 00:04:38 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: bridge-mib@ietf.org Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03p.txt In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15502D94F94@nl0006exch001u.nl.lucent.com> 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-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Tue, 4 Nov 2003, Wijnen, Bert (Bert) wrote: > Other than that, I support and agree with the comments made by Mike > on Sept 9th (and posted on the bridge wg list) Actually, the -03 version that K.C. submitted just before the blackout deadline addresses most of those comments. The ones that were not addressed were the questions of using standard boilerplate or at least updating the old boilerplate with current references (which Bert discussed) and of making RFC 1213 into a normative reference (because of the requirements in Section 3.5). This version is not yet in the repository; I saw it because I was cc'd on some e-mail correspondence that contained it. Mike _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Thu Nov 6 07:54:20 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06556 for ; Thu, 6 Nov 2003 07:54:20 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjeD-0004Rg-Et for bridge-archive@odin.ietf.org; Thu, 06 Nov 2003 07:54:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA6Cs1St017077 for bridge-archive@odin.ietf.org; Thu, 6 Nov 2003 07:54:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjeD-0004RK-6E; Thu, 06 Nov 2003 07:54:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AHjeA-0004Qo-4p for bridge-mib@optimus.ietf.org; Thu, 06 Nov 2003 07:53:58 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06544 for ; Thu, 6 Nov 2003 07:53:45 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AHje7-0000RS-00 for bridge-mib@ietf.org; Thu, 06 Nov 2003 07:53:55 -0500 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1AHje7-0000R6-00 for bridge-mib@ietf.org; Thu, 06 Nov 2003 07:53:55 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hA6CrI909457 for ; Thu, 6 Nov 2003 06:53:18 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59) id ; Thu, 6 Nov 2003 13:53:11 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502D953AB@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" , bridge-mib@ietf.org Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03p.txt Date: Thu, 6 Nov 2003 12:27:17 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain 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: , > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: donderdag 6 november 2003 9:05 > To: bridge-mib@ietf.org > Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03p.txt > > > On Tue, 4 Nov 2003, Wijnen, Bert (Bert) wrote: > > Other than that, I support and agree with the comments made by Mike > > on Sept 9th (and posted on the bridge wg list) > > Actually, the -03 version that K.C. submitted just before the > blackout deadline addresses most of those comments. The ones that > were not addressed were the questions of using standard boilerplate > or at least updating the old boilerplate with current references > (which Bert discussed) and of making RFC 1213 into a normative > reference (because of the requirements in Section 3.5). This > version is not yet in the repository; I saw it because I was cc'd > on some e-mail correspondence that contained it. > OK, so I guess I have not yet seen the latest rev. Will check after Minneapolis Bert > Mike _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Wed Nov 19 15:21:33 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09238 for ; Wed, 19 Nov 2003 15:21:29 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMYp6-0004Yn-9a for bridge-archive@odin.ietf.org; Wed, 19 Nov 2003 15:21:12 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJKLC7S017522 for bridge-archive@odin.ietf.org; Wed, 19 Nov 2003 15:21:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMYp1-0004Xr-7B; Wed, 19 Nov 2003 15:21:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMYoc-0004WF-Eh for bridge-mib@optimus.ietf.org; Wed, 19 Nov 2003 15:20:42 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09099; Wed, 19 Nov 2003 15:20:26 -0500 (EST) Message-Id: <200311192020.PAA09099@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, 19 Nov 2003 15:20:26 -0500 Subject: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.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 for Port Access Control (IEEE 802.1X) MIB Author(s) : K. Norseth Filename : draft-ietf-bridge-8021x-03.txt Pages : 42 Date : 2003-11-19 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bridge-8021x-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-8021x-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-8021x-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: <2003-11-19144128.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-bridge-8021x-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-bridge-8021x-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-11-19144128.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Thu Nov 20 10:33:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09470 for ; Thu, 20 Nov 2003 10:33:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMqnm-0001lF-2h for bridge-archive@odin.ietf.org; Thu, 20 Nov 2003 10:33:02 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKFX2hF006768 for bridge-archive@odin.ietf.org; Thu, 20 Nov 2003 10:33:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMqnl-0001l0-AF; Thu, 20 Nov 2003 10:33:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMqng-0001ko-Jz for bridge-mib@optimus.ietf.org; Thu, 20 Nov 2003 10:32:56 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09442 for ; Thu, 20 Nov 2003 10:32:42 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMqne-0004iB-00 for bridge-mib@ietf.org; Thu, 20 Nov 2003 10:32:54 -0500 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMqnd-0004i8-00 for bridge-mib@ietf.org; Thu, 20 Nov 2003 10:32:53 -0500 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id hAKFWpo24443; Thu, 20 Nov 2003 07:32:51 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 20 Nov 2003 07:32:50 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: bridge-mib@ietf.org Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.txt In-Reply-To: <200311192020.PAA09099@ietf.org> <7D5D48D2CAA3D84C813F5B154F43B15502D94F94@nl0006exch001u.nl.lucent.com> 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-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Thu, 6 Nov 2003, C. M. Heard wrote: > On Tue, 4 Nov 2003, Wijnen, Bert (Bert) wrote: > > Other than that, I support and agree with the comments made by Mike > > on Sept 9th (and posted on the bridge wg list) > > Actually, the -03 version that K.C. submitted just before the > blackout deadline addresses most of those comments. The ones that > were not addressed were the questions of using standard boilerplate > or at least updating the old boilerplate with current references > (which Bert discussed) and of making RFC 1213 into a normative > reference (because of the requirements in Section 3.5). This > version is not yet in the repository; I saw it because I was cc'd > on some e-mail correspondence that contained it. I see that K.C.'s submission has now appeared in the repository. Here are my detailed comments, which are basically just an expansion of the above and some earlier comments from Bert: 1.) In the Abstract: s/this draft/this document/ and s/SNMPv2 SMI compliant/SMIv2-compliant/. 2.) In Section 1: I recommend to replace this with the current boilerplate at http://www.ops.ietf.org/mib-boilerplate.html (also mentioned in Bert's comments of Tue, 4 Nov 2003). 3.) In the MIB module revision description for the current version: OLD: The IETF Bridge-mib WG made the following changes: NEW: The IETF Bridge-mib WG made the following changes in order to get the MIB module to compile: 4.) In the MIB MODULE revision description for the previous version: OLD: DESCRIPTION "The initial and authoritative version as published at: NEW: DESCRIPTION "The initial version as published at: 5.) In Section 7: change the dates on [RFC2578], [RFC2579], and [RFC2580] from May 1999 back to April 1999 (this seems to have resulted from a global replace in this version). 6.) In Section 7: add RFC 1213 as a normative reference. That is needed because of its mention in Section 3.5. 7.) In Sections 7 and 8: move [RFC3410] from Section 7 to Section 8 since it is customary to list this as an informative reference. 8.) In Section 8: eliminate [RFC1157], [RFC1212], [RFC1901], [RFC1905], [RFC1906], [RFC2119], [RFC2570], [RFC2572], [RFC2574], [RFC2573], and [RFC2575]. Of these, [RFC2119] is not needed because there are no capitalized MUST, MAY, etc. keywords, and the rest are obsolete and are not needed if the current boilerplate is used for Section 1. 9.) Add an RFC Editor note that Section 11 is to be removed prior to publication. Bert had some additional comments in his message of 4 Nov. Regards, Mike Heard _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Thu Nov 20 14:19:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19462 for ; Thu, 20 Nov 2003 14:19:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMuKT-0002Xu-Mh for bridge-archive@odin.ietf.org; Thu, 20 Nov 2003 14:19:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKJJ1Q9009775 for bridge-archive@odin.ietf.org; Thu, 20 Nov 2003 14:19:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMuKT-0002XX-Ck; Thu, 20 Nov 2003 14:19:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AMuKJ-0002XB-7Y for bridge-mib@optimus.ietf.org; Thu, 20 Nov 2003 14:18:51 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19423 for ; Thu, 20 Nov 2003 14:18:37 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AMuKG-0000gU-00 for bridge-mib@ietf.org; Thu, 20 Nov 2003 14:18:48 -0500 Received: from falcon.mail.pas.earthlink.net ([207.217.120.74]) by ietf-mx with esmtp (Exim 4.12) id 1AMuKG-0000gR-00 for bridge-mib@ietf.org; Thu, 20 Nov 2003 14:18:48 -0500 Received: from h-68-164-78-60.snvacaid.dynamic.covad.net ([68.164.78.60] helo=oemcomputer) by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AMuKG-0006Pt-00 for bridge-mib@ietf.org; Thu, 20 Nov 2003 11:18:48 -0800 Message-ID: <011301c3af9b$5e7abe80$7f1afea9@oemcomputer> From: "Randy Presuhn" To: References: Subject: Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.txt Date: Thu, 20 Nov 2003 11:20:33 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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: , Hi - > From: "C. M. Heard" > To: > Sent: Thursday, November 20, 2003 7:32 AM > Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.txt ... > 6.) In Section 7: add RFC 1213 as a normative reference. That is > needed because of its mention in Section 3.5. ... It would be better to replace it with a reference to RFC 3418. Randy _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib From exim@www1.ietf.org Thu Nov 20 21:27:18 2003 Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14228 for ; Thu, 20 Nov 2003 21:27:18 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN10f-0007nB-1r for bridge-archive@odin.ietf.org; Thu, 20 Nov 2003 21:27:01 -0500 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hAL2R1VH029942 for bridge-archive@odin.ietf.org; Thu, 20 Nov 2003 21:27:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN10e-0007ml-DC; Thu, 20 Nov 2003 21:27:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AN10T-0007mU-NX for bridge-mib@optimus.ietf.org; Thu, 20 Nov 2003 21:26:49 -0500 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14214 for ; Thu, 20 Nov 2003 21:26:36 -0500 (EST) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN10Q-0001gz-00 for bridge-mib@ietf.org; Thu, 20 Nov 2003 21:26:46 -0500 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 1AN10Q-0001gw-00 for bridge-mib@ietf.org; Thu, 20 Nov 2003 21:26:46 -0500 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id hAL2Qke18118; Thu, 20 Nov 2003 18:26:46 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 20 Nov 2003 18:26:45 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: bridge-mib@ietf.org Subject: Re: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.txt In-Reply-To: <011301c3af9b$5e7abe80$7f1afea9@oemcomputer> 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-BeenThere: bridge-mib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Thu, 20 Nov 2003, Randy Presuhn wrote: > > From: "C. M. Heard" > > To: > > Sent: Thursday, November 20, 2003 7:32 AM > > Subject: RE: [Bridge-mib] I-D ACTION:draft-ietf-bridge-8021x-03.txt > ... > > 6.) In Section 7: add RFC 1213 as a normative reference. That is > > needed because of its mention in Section 3.5. > ... > > It would be better to replace it with a reference to RFC 3418. I don't object, but I would like to point out that it's not as simple as just changing the reference. Section 3.5 be would also need to be modified along the following lines: OLD: It is assumed that a system implementing this MIB will also implement (at least) the system group defined in MIB-II defined in IETF RFC 1213 and the interfaces group defined in IETF RFC 2863. NEW: It is assumed that a system implementing this MIB will also implement (at least) the system group defined in MIB-II defined in IETF RFC 3418 and the interfaces group defined in IETF RFC 2863. Since RFC 3418 (actually RFC 1907) expanded the system group by adding sysORLastChange, sysORID, sysORUpTime, and sysORDescr to the RFC 1213 objects sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation, and sysServices, this would not be a purely editorial change and therefore should be vetted by the IEEE. Mike _______________________________________________ Bridge-mib mailing list Bridge-mib@ietf.org https://www1.ietf.org/mailman/listinfo/bridge-mib