From mailman-admin@ietf.org Thu May 1 14:43:15 2003 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 OAA28445 for ; Thu, 1 May 2003 14:43:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41InP807345 for ; Thu, 1 May 2003 14:49:25 -0400 Date: Thu, 01 May 2003 14:49:25 -0400 Message-ID: <20030501184925.17986.61050.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: hubmib-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, hubmib-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for hubmib-archive@lists.ietf.org: List Password // URL ---- -------- hubmib@ietf.org XUKx https://www1.ietf.org/mailman/options/hubmib/hubmib-archive%40lists.ietf.org From mailnull@www1.ietf.org Thu May 1 15:01:38 2003 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 PAA29629 for ; Thu, 1 May 2003 15:01:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41J7nS12145 for hubmib-archive@odin.ietf.org; Thu, 1 May 2003 15:07:49 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41J7n812140; Thu, 1 May 2003 15:07:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41J5J810686 for ; Thu, 1 May 2003 15:05:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29354 for ; Thu, 1 May 2003 14:58:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJIY-0005LM-00 for hubmib@ietf.org; Thu, 01 May 2003 15:00:50 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJIS-0005Jy-00 for hubmib@ietf.org; Thu, 01 May 2003 15:00:44 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h41IxE906945; Thu, 1 May 2003 11:59:14 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 1 May 2003 11:59:12 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "Wijnen, Bert (Bert)" cc: "Dan Romascanu (E-mail)" , "Hubmib Mailing List (E-mail)" Subject: Re: [Hubmib] rfc1643 to historic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Bert, The IETF secretariat expired a large number of I-Ds yesterday, and unfortunately draft-ietf-hubmib-1643-to-historic-01.txt was one of them. It has been replaced with a -02 version which is an expiration notice. Since it was only being held while we finished the companion documents, could you ask the I-D administrator to please re-instate it? Thanks, Mike On Mon, 18 Nov 2002, Wijnen, Bert (Bert) wrote: > Dan/Mike, wg > > I am OK with this document. > Does the WG want me to hold this till we also have the other > 3 documents ready or shall I go ahead and put this one on IESG agenda now? > > Thanks, > Bert _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 1 15:01:43 2003 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 PAA29644 for ; Thu, 1 May 2003 15:01:43 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41J7n812140; Thu, 1 May 2003 15:07:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41J5J810686 for ; Thu, 1 May 2003 15:05:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29354 for ; Thu, 1 May 2003 14:58:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJIY-0005LM-00 for hubmib@ietf.org; Thu, 01 May 2003 15:00:50 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJIS-0005Jy-00 for hubmib@ietf.org; Thu, 01 May 2003 15:00:44 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h41IxE906945; Thu, 1 May 2003 11:59:14 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Thu, 1 May 2003 11:59:12 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "Wijnen, Bert (Bert)" cc: "Dan Romascanu (E-mail)" , "Hubmib Mailing List (E-mail)" Subject: Re: [Hubmib] rfc1643 to historic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Bert, The IETF secretariat expired a large number of I-Ds yesterday, and unfortunately draft-ietf-hubmib-1643-to-historic-01.txt was one of them. It has been replaced with a -02 version which is an expiration notice. Since it was only being held while we finished the companion documents, could you ask the I-D administrator to please re-instate it? Thanks, Mike On Mon, 18 Nov 2002, Wijnen, Bert (Bert) wrote: > Dan/Mike, wg > > I am OK with this document. > Does the WG want me to hold this till we also have the other > 3 documents ready or shall I go ahead and put this one on IESG agenda now? > > Thanks, > Bert _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Mon May 5 06:22:21 2003 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 GAA28470 for ; Mon, 5 May 2003 06:22:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45AUIk21326 for hubmib-archive@odin.ietf.org; Mon, 5 May 2003 06:30:18 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45AUF821321; Mon, 5 May 2003 06:30:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45ATY821199 for ; Mon, 5 May 2003 06:29:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28413 for ; Mon, 5 May 2003 06:20:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cd7b-0004wy-00 for hubmib@ietf.org; Mon, 05 May 2003 06:22:59 -0400 Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19Cd7V-0004wk-00 for hubmib@ietf.org; Mon, 05 May 2003 06:22:53 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h45AMZW29493 for ; Mon, 5 May 2003 06:22:35 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R198SFC>; Mon, 5 May 2003 12:22:34 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155017C1787@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" Cc: "Dan Romascanu (E-mail)" , "Hubmib Mailing List (E-mail)" Subject: RE: [Hubmib] rfc1643 to historic Date: Mon, 5 May 2003 12:22:31 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , I have asked to resurrect it. Thanks, Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: donderdag 1 mei 2003 20:59 > To: Wijnen, Bert (Bert) > Cc: Dan Romascanu (E-mail); Hubmib Mailing List (E-mail) > Subject: Re: [Hubmib] rfc1643 to historic > > > Bert, > > The IETF secretariat expired a large number of I-Ds yesterday, and > unfortunately draft-ietf-hubmib-1643-to-historic-01.txt was one of > them. It has been replaced with a -02 version which is an > expiration notice. > > Since it was only being held while we finished the companion > documents, could you ask the I-D administrator to please re-instate > it? > > Thanks, > > Mike > > On Mon, 18 Nov 2002, Wijnen, Bert (Bert) wrote: > > Dan/Mike, wg > > > > I am OK with this document. > > Does the WG want me to hold this till we also have the other > > 3 documents ready or shall I go ahead and put this one on > IESG agenda now? > > > > Thanks, > > Bert > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon May 5 06:22:28 2003 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 GAA28484 for ; Mon, 5 May 2003 06:22:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45AUF821321; Mon, 5 May 2003 06:30:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45ATY821199 for ; Mon, 5 May 2003 06:29:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28413 for ; Mon, 5 May 2003 06:20:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cd7b-0004wy-00 for hubmib@ietf.org; Mon, 05 May 2003 06:22:59 -0400 Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19Cd7V-0004wk-00 for hubmib@ietf.org; Mon, 05 May 2003 06:22:53 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h45AMZW29493 for ; Mon, 5 May 2003 06:22:35 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R198SFC>; Mon, 5 May 2003 12:22:34 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155017C1787@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" Cc: "Dan Romascanu (E-mail)" , "Hubmib Mailing List (E-mail)" Subject: RE: [Hubmib] rfc1643 to historic Date: Mon, 5 May 2003 12:22:31 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , I have asked to resurrect it. Thanks, Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: donderdag 1 mei 2003 20:59 > To: Wijnen, Bert (Bert) > Cc: Dan Romascanu (E-mail); Hubmib Mailing List (E-mail) > Subject: Re: [Hubmib] rfc1643 to historic > > > Bert, > > The IETF secretariat expired a large number of I-Ds yesterday, and > unfortunately draft-ietf-hubmib-1643-to-historic-01.txt was one of > them. It has been replaced with a -02 version which is an > expiration notice. > > Since it was only being held while we finished the companion > documents, could you ask the I-D administrator to please re-instate > it? > > Thanks, > > Mike > > On Mon, 18 Nov 2002, Wijnen, Bert (Bert) wrote: > > Dan/Mike, wg > > > > I am OK with this document. > > Does the WG want me to hold this till we also have the other > > 3 documents ready or shall I go ahead and put this one on > IESG agenda now? > > > > Thanks, > > Bert > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Mon May 5 11:23:39 2003 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 LAA05354 for ; Mon, 5 May 2003 11:23:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45FVgK09943 for hubmib-archive@odin.ietf.org; Mon, 5 May 2003 11:31:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45FVg809938; Mon, 5 May 2003 11:31:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45FEV809037 for ; Mon, 5 May 2003 11:14:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04994 for ; Mon, 5 May 2003 11:05:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ChZG-0006Oe-00 for hubmib@ietf.org; Mon, 05 May 2003 11:07:50 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19ChZA-0006OT-00 for hubmib@ietf.org; Mon, 05 May 2003 11:07:45 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h45F88p14066 for ; Mon, 5 May 2003 08:08:08 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 5 May 2003 08:08:07 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "Hubmib Mailing List (E-mail)" Subject: RE: [Hubmib] rfc1643 to historic In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155017C1787@nl0006exch001u.nl.lucent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , draft-ietf-hubmib-1643-to-historic-01.txt is once again available in the I-D repository and on the WG web page. //cmh On Mon, 5 May 2003, Wijnen, Bert (Bert) wrote: > I have asked to resurrect it. > > Thanks, > Bert > > > -----Original Message----- > > From: C. M. Heard [mailto:heard@pobox.com] > > Sent: donderdag 1 mei 2003 20:59 > > To: Wijnen, Bert (Bert) > > Cc: Dan Romascanu (E-mail); Hubmib Mailing List (E-mail) > > Subject: Re: [Hubmib] rfc1643 to historic > > > > > > Bert, > > > > The IETF secretariat expired a large number of I-Ds yesterday, and > > unfortunately draft-ietf-hubmib-1643-to-historic-01.txt was one of > > them. It has been replaced with a -02 version which is an > > expiration notice. > > > > Since it was only being held while we finished the companion > > documents, could you ask the I-D administrator to please re-instate > > it? > > > > Thanks, > > > > Mike > > > > On Mon, 18 Nov 2002, Wijnen, Bert (Bert) wrote: > > > Dan/Mike, wg > > > > > > I am OK with this document. > > > Does the WG want me to hold this till we also have the other > > > 3 documents ready or shall I go ahead and put this one on > > > IESG agenda now? > > > > > > Thanks, > > > Bert > > > > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Mon May 5 11:23:49 2003 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 LAA05372 for ; Mon, 5 May 2003 11:23:49 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45FVg809938; Mon, 5 May 2003 11:31:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45FEV809037 for ; Mon, 5 May 2003 11:14:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04994 for ; Mon, 5 May 2003 11:05:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ChZG-0006Oe-00 for hubmib@ietf.org; Mon, 05 May 2003 11:07:50 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19ChZA-0006OT-00 for hubmib@ietf.org; Mon, 05 May 2003 11:07:45 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h45F88p14066 for ; Mon, 5 May 2003 08:08:08 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 5 May 2003 08:08:07 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "Hubmib Mailing List (E-mail)" Subject: RE: [Hubmib] rfc1643 to historic In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155017C1787@nl0006exch001u.nl.lucent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , draft-ietf-hubmib-1643-to-historic-01.txt is once again available in the I-D repository and on the WG web page. //cmh On Mon, 5 May 2003, Wijnen, Bert (Bert) wrote: > I have asked to resurrect it. > > Thanks, > Bert > > > -----Original Message----- > > From: C. M. Heard [mailto:heard@pobox.com] > > Sent: donderdag 1 mei 2003 20:59 > > To: Wijnen, Bert (Bert) > > Cc: Dan Romascanu (E-mail); Hubmib Mailing List (E-mail) > > Subject: Re: [Hubmib] rfc1643 to historic > > > > > > Bert, > > > > The IETF secretariat expired a large number of I-Ds yesterday, and > > unfortunately draft-ietf-hubmib-1643-to-historic-01.txt was one of > > them. It has been replaced with a -02 version which is an > > expiration notice. > > > > Since it was only being held while we finished the companion > > documents, could you ask the I-D administrator to please re-instate > > it? > > > > Thanks, > > > > Mike > > > > On Mon, 18 Nov 2002, Wijnen, Bert (Bert) wrote: > > > Dan/Mike, wg > > > > > > I am OK with this document. > > > Does the WG want me to hold this till we also have the other > > > 3 documents ready or shall I go ahead and put this one on > > > IESG agenda now? > > > > > > Thanks, > > > Bert > > > > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Tue May 20 11:50:51 2003 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 LAA18808 for ; Tue, 20 May 2003 11:50:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KFKMt10539 for hubmib-archive@odin.ietf.org; Tue, 20 May 2003 11:20:22 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KFKKB10532; Tue, 20 May 2003 11:20:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KFJDB10470 for ; Tue, 20 May 2003 11:19:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18699 for ; Tue, 20 May 2003 11:49:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I9OH-0006JB-00 for hubmib@ietf.org; Tue, 20 May 2003 11:51:01 -0400 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19I9OG-0006J0-00 for hubmib@ietf.org; Tue, 20 May 2003 11:51:00 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4KFpmN15261 for ; Tue, 20 May 2003 11:51:49 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10GP16>; Tue, 20 May 2003 17:51:47 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155019C2397@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" , hubmib@ietf.org Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-etherif-mib-v3-03.txt Date: Tue, 20 May 2003 17:51:47 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , I am OK with this document. So it is ready for IETF Last Call. I propose that the two minor editorial issues raised by Mike below can be either done if another rev is needed later, or we can ask John to make sure this gets fixed during rfc-editor author48 call. Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: vrijdag 7 maart 2003 23:38 > To: hubmib@ietf.org > Subject: Re: [Hubmib] I-D > ACTION:draft-ietf-hubmib-etherif-mib-v3-03.txt > > > On Fri, 7 Mar 2003 Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line > > Internet-Drafts directories. This draft is a work item of the > > Ethernet Interfaces and Hub MIB Working Group of the IETF. > > > > Title : Definitions of Managed Objects for > the Ethernet-like > > Interface Types > > Author(s) : J. Flick > > Filename : draft-ietf-hubmib-etherif-mib-v3-03.txt > > Pages : 64 > > Date : 2003-3-6 > > Thanks to John Flick for posting this update. I have reviewed the > changes relative to the -02 draft and on a quick look they all > appear to be OK, with two exceptions: > > - There is a stray comma in the last sentence of the second > paragraph of the Introduction (Section 1). The fix: > s/version of this MIB, module,/version of this MIB module,/ > > - The date in the full copyright notice reads (2002) instead of > (2003). > > Regards, > > Mike Heard > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue May 20 11:51:00 2003 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 LAA18825 for ; Tue, 20 May 2003 11:51:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KFKKB10532; Tue, 20 May 2003 11:20:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KFJDB10470 for ; Tue, 20 May 2003 11:19:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18699 for ; Tue, 20 May 2003 11:49:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I9OH-0006JB-00 for hubmib@ietf.org; Tue, 20 May 2003 11:51:01 -0400 Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19I9OG-0006J0-00 for hubmib@ietf.org; Tue, 20 May 2003 11:51:00 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4KFpmN15261 for ; Tue, 20 May 2003 11:51:49 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10GP16>; Tue, 20 May 2003 17:51:47 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155019C2397@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" , hubmib@ietf.org Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-etherif-mib-v3-03.txt Date: Tue, 20 May 2003 17:51:47 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , I am OK with this document. So it is ready for IETF Last Call. I propose that the two minor editorial issues raised by Mike below can be either done if another rev is needed later, or we can ask John to make sure this gets fixed during rfc-editor author48 call. Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: vrijdag 7 maart 2003 23:38 > To: hubmib@ietf.org > Subject: Re: [Hubmib] I-D > ACTION:draft-ietf-hubmib-etherif-mib-v3-03.txt > > > On Fri, 7 Mar 2003 Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line > > Internet-Drafts directories. This draft is a work item of the > > Ethernet Interfaces and Hub MIB Working Group of the IETF. > > > > Title : Definitions of Managed Objects for > the Ethernet-like > > Interface Types > > Author(s) : J. Flick > > Filename : draft-ietf-hubmib-etherif-mib-v3-03.txt > > Pages : 64 > > Date : 2003-3-6 > > Thanks to John Flick for posting this update. I have reviewed the > changes relative to the -02 draft and on a quick look they all > appear to be OK, with two exceptions: > > - There is a stray comma in the last sentence of the second > paragraph of the Introduction (Section 1). The fix: > s/version of this MIB, module,/version of this MIB module,/ > > - The date in the full copyright notice reads (2002) instead of > (2003). > > Regards, > > Mike Heard > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Tue May 20 14:47:42 2003 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 OAA24762 for ; Tue, 20 May 2003 14:47:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KIE7924342 for hubmib-archive@odin.ietf.org; Tue, 20 May 2003 14:14:07 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIE5B24337; Tue, 20 May 2003 14:14:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIDOB24310 for ; Tue, 20 May 2003 14:13:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24738 for ; Tue, 20 May 2003 14:46:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IC6m-0007be-00 for hubmib@ietf.org; Tue, 20 May 2003 14:45:08 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19IC6l-0007bb-00 for hubmib@ietf.org; Tue, 20 May 2003 14:45:07 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4KIjtW03720 for ; Tue, 20 May 2003 14:45:56 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10GRPB>; Tue, 20 May 2003 20:45:54 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155019C23D0@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" , hubmib@ietf.org Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-03.txt Date: Tue, 20 May 2003 20:45:52 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , I am OK with this document. So it seems ready for IETF Last Call. I think the comments below can be don during rfc-editor auth48 call. I would add that I prefer to not have citations in MIB clauses. They get lost when a MIB module is extracted. For example DESCRIPTION "Compliance for MAUs attached to repeater ports. Note that compliance with this compliance statement requires compliance with the snmpRptrModCompl MODULE-COMPLIANCE statement of the SNMP-REPEATER-MIB [RFC2108]." reads equally well if you replace [RFC2108] with RFC 2108. There are more of these. There were a few in the etherlike-mib too by the way. Thanks, Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: vrijdag 7 maart 2003 23:33 > To: hubmib@ietf.org > Subject: Re: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-03.txt > > > On Fri, 7 Mar 2003 Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line > > Internet-Drafts directories. This draft is a work item of the > > Ethernet Interfaces and Hub MIB Working Group of the IETF. > > > > Title : Definitions of Managed Objects for > IEEE 802.3 Medium > > Attachment Units (MAUs) > > Author(s) : J. Flick > > Filename : draft-ietf-hubmib-mau-mib-v3-03.txt > > Pages : 62 > > Date : 2003-3-6 > > Thanks to John Flick for posting this update. I have reviewed the > changes relative to the -02 draft and on a quick look they all > appear to be OK. I did notice two very minor things that can > probably be addressed by the RFC Editor: > > - The title of Section 10 is "Authors' Addresses". I think that it > should be "Author's Address" since there is now only one author. > > - The dates in the copyright notice on the front page and on the > full copyright notice in Appendix B read (2002) instead of (2003). > > Regards, > > Mike Heard > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue May 20 14:47:47 2003 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 OAA24776 for ; Tue, 20 May 2003 14:47:47 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIE5B24337; Tue, 20 May 2003 14:14:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIDOB24310 for ; Tue, 20 May 2003 14:13:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24738 for ; Tue, 20 May 2003 14:46:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IC6m-0007be-00 for hubmib@ietf.org; Tue, 20 May 2003 14:45:08 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19IC6l-0007bb-00 for hubmib@ietf.org; Tue, 20 May 2003 14:45:07 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4KIjtW03720 for ; Tue, 20 May 2003 14:45:56 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10GRPB>; Tue, 20 May 2003 20:45:54 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155019C23D0@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" , hubmib@ietf.org Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-03.txt Date: Tue, 20 May 2003 20:45:52 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , I am OK with this document. So it seems ready for IETF Last Call. I think the comments below can be don during rfc-editor auth48 call. I would add that I prefer to not have citations in MIB clauses. They get lost when a MIB module is extracted. For example DESCRIPTION "Compliance for MAUs attached to repeater ports. Note that compliance with this compliance statement requires compliance with the snmpRptrModCompl MODULE-COMPLIANCE statement of the SNMP-REPEATER-MIB [RFC2108]." reads equally well if you replace [RFC2108] with RFC 2108. There are more of these. There were a few in the etherlike-mib too by the way. Thanks, Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: vrijdag 7 maart 2003 23:33 > To: hubmib@ietf.org > Subject: Re: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-03.txt > > > On Fri, 7 Mar 2003 Internet-Drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line > > Internet-Drafts directories. This draft is a work item of the > > Ethernet Interfaces and Hub MIB Working Group of the IETF. > > > > Title : Definitions of Managed Objects for > IEEE 802.3 Medium > > Attachment Units (MAUs) > > Author(s) : J. Flick > > Filename : draft-ietf-hubmib-mau-mib-v3-03.txt > > Pages : 62 > > Date : 2003-3-6 > > Thanks to John Flick for posting this update. I have reviewed the > changes relative to the -02 draft and on a quick look they all > appear to be OK. I did notice two very minor things that can > probably be addressed by the RFC Editor: > > - The title of Section 10 is "Authors' Addresses". I think that it > should be "Author's Address" since there is now only one author. > > - The dates in the copyright notice on the front page and on the > full copyright notice in Appendix B read (2002) instead of (2003). > > Regards, > > Mike Heard > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Tue May 20 15:01:38 2003 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 PAA25207 for ; Tue, 20 May 2003 15:01:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KIS3Z24919 for hubmib-archive@odin.ietf.org; Tue, 20 May 2003 14:28:03 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIS3B24914; Tue, 20 May 2003 14:28:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIRLB24891 for ; Tue, 20 May 2003 14:27:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25165 for ; Tue, 20 May 2003 15:00:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICKH-0007gn-00 for hubmib@ietf.org; Tue, 20 May 2003 14:59:05 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICKG-0007gk-00 for hubmib@ietf.org; Tue, 20 May 2003 14:59:04 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h4KJ0Mb01518; Tue, 20 May 2003 12:00:22 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 20 May 2003 12:00:21 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "Wijnen, Bert (Bert)" cc: hubmib@ietf.org Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-03.txt In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155019C23D0@nl0006exch001u.nl.lucent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Tue, 20 May 2003, Wijnen, Bert (Bert) wrote: > I am OK with this document. So it seems ready for IETF Last Call. > > I think the comments below can be don during rfc-editor auth48 call. > > I would add that I prefer to not have citations in MIB clauses. > They get lost when a MIB module is extracted. For example > DESCRIPTION "Compliance for MAUs attached to repeater > ports. > > Note that compliance with this compliance > statement requires compliance with the > snmpRptrModCompl MODULE-COMPLIANCE statement of > the SNMP-REPEATER-MIB [RFC2108]." > > reads equally well if you replace [RFC2108] with RFC 2108. > > There are more of these. > > There were a few in the etherlike-mib too by the way. Just to be perfectly clear, may I suggest s/[RFC2108]/(RFC 2108)/ as the global change (and similarly for the other cases). That way the text will read "... of the SNMP-REPEATER-MIB ((RFC 2108)." Thanks, Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue May 20 15:01:44 2003 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 PAA25221 for ; Tue, 20 May 2003 15:01:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIS3B24914; Tue, 20 May 2003 14:28:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIRLB24891 for ; Tue, 20 May 2003 14:27:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25165 for ; Tue, 20 May 2003 15:00:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICKH-0007gn-00 for hubmib@ietf.org; Tue, 20 May 2003 14:59:05 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICKG-0007gk-00 for hubmib@ietf.org; Tue, 20 May 2003 14:59:04 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h4KJ0Mb01518; Tue, 20 May 2003 12:00:22 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Tue, 20 May 2003 12:00:21 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: "Wijnen, Bert (Bert)" cc: hubmib@ietf.org Subject: RE: [Hubmib] I-D ACTION:draft-ietf-hubmib-mau-mib-v3-03.txt In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155019C23D0@nl0006exch001u.nl.lucent.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Tue, 20 May 2003, Wijnen, Bert (Bert) wrote: > I am OK with this document. So it seems ready for IETF Last Call. > > I think the comments below can be don during rfc-editor auth48 call. > > I would add that I prefer to not have citations in MIB clauses. > They get lost when a MIB module is extracted. For example > DESCRIPTION "Compliance for MAUs attached to repeater > ports. > > Note that compliance with this compliance > statement requires compliance with the > snmpRptrModCompl MODULE-COMPLIANCE statement of > the SNMP-REPEATER-MIB [RFC2108]." > > reads equally well if you replace [RFC2108] with RFC 2108. > > There are more of these. > > There were a few in the etherlike-mib too by the way. Just to be perfectly clear, may I suggest s/[RFC2108]/(RFC 2108)/ as the global change (and similarly for the other cases). That way the text will read "... of the SNMP-REPEATER-MIB ((RFC 2108)." Thanks, Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Tue May 20 15:32:53 2003 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 PAA27362 for ; Tue, 20 May 2003 15:32:53 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KIxJB27175 for hubmib-archive@odin.ietf.org; Tue, 20 May 2003 14:59:19 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIxJB27170; Tue, 20 May 2003 14:59:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIuZB26991 for ; Tue, 20 May 2003 14:56:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27240 for ; Tue, 20 May 2003 15:29:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICmY-00005Q-00 for hubmib@ietf.org; Tue, 20 May 2003 15:28:18 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19ICmY-00005G-00 for hubmib@ietf.org; Tue, 20 May 2003 15:28:18 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4KJT5W28706 for ; Tue, 20 May 2003 15:29:06 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10GR99>; Tue, 20 May 2003 21:29:04 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155019C23E8@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" , Hub MIB Mailing List Cc: AToM MIB Mailing list Date: Tue, 20 May 2003 21:29:04 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Hubmib] RE: New WIS MIB draft now available Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This doc is fine with me and I am ready to ask for IETF Last Call Thanks, Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: zaterdag 22 maart 2003 17:08 > To: Hub MIB Mailing List > Cc: AToM MIB Mailing list > Subject: New WIS MIB draft now available > > > Hub MIB and AToM MIB WG members, > > The latest WIS MIB draft, which was submitted on 17 March 2003, is > now available at > > http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-07.txt > > The I-D actually made its appearance in the repository before the > official announcement, which can be expected to arrive shortly. > > Here is what has changed since the previous version: > > 1.) The prerequisite external compliance statements > (IF-MIB.ifCompliance3, IF-INVERTED-STACK-MIB.ifInvCompliance, > EtherLike-MIB.dot3Compliance2, and MAU-MIB.mauModIfCompl3) are now > listed explicitly in the etherWisCompliance DESCRIPTION clause. > > 2.) The OBJECT clauses for etherWisDeviceTxTestPatternMode and > etherWisDeviceRxTestPatternMode no longer state that an > implementation is not required to support certain combinations of > settings because the Clause 45 MDIO registers do not, in fact, > impose any inter-dependencies in the settings. > > 3.) The dates in the LAST-UPDATED and REVISION clauses of the > MODULE-IDENTITY invocation were changed to the current date. > > 4.) References [ETHERIF] and [MAU-MIB] were updated to point to > and > , respectively. > > Note that change #1 brings the document into compliance with the > recently issued MIB review guidelines document > (which postdates the > -06 version of the ETHER-WIS MIB) and that change #2 undoes an > erroneous modification that was introduced into the -05 version. > > As I've noted before the following three normative references > need to be progressed to Proposed Standard or higher prior to or > simultaneously with the WIS MIB document in order for it to be > published as an RFC: > > [SONETng] Tesink, K., "Definitions of Managed Objects for the > SONET/SDH Interface Type", 01.txt>, work in progress. > > [ETHERIF] Flick, J., "Definitions of Managed Objects for the > Ethernet-like Interface Types", > mib-v3-03.txt>, work in progress. > > [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 > Medium Attachment Units (MAUs)", mib-v3-03.txt>, work in progress. > > The IETF last call on [SONETng] recently expired and it is now in > the "waiting for writeup" state. [ETHERIF] and [MAU-MIB] were > recently updated to address A-D review comments, and I believe this > means that the document package consisting of [ETHERIF], [MAU-MIB], > this submission, and draft-ietf-hubmib-1643-to-historic-01.txt is > ready for the next step. > > Thanks and regards, > > Mike > -- > C. M. Heard > heard@pobox.com > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue May 20 15:33:00 2003 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 PAA27379 for ; Tue, 20 May 2003 15:33:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIxJB27170; Tue, 20 May 2003 14:59:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIuZB26991 for ; Tue, 20 May 2003 14:56:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27240 for ; Tue, 20 May 2003 15:29:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICmY-00005Q-00 for hubmib@ietf.org; Tue, 20 May 2003 15:28:18 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19ICmY-00005G-00 for hubmib@ietf.org; Tue, 20 May 2003 15:28:18 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4KJT5W28706 for ; Tue, 20 May 2003 15:29:06 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id <2R10GR99>; Tue, 20 May 2003 21:29:04 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155019C23E8@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" , Hub MIB Mailing List Cc: AToM MIB Mailing list Date: Tue, 20 May 2003 21:29:04 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Hubmib] RE: New WIS MIB draft now available Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This doc is fine with me and I am ready to ask for IETF Last Call Thanks, Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: zaterdag 22 maart 2003 17:08 > To: Hub MIB Mailing List > Cc: AToM MIB Mailing list > Subject: New WIS MIB draft now available > > > Hub MIB and AToM MIB WG members, > > The latest WIS MIB draft, which was submitted on 17 March 2003, is > now available at > > http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-07.txt > > The I-D actually made its appearance in the repository before the > official announcement, which can be expected to arrive shortly. > > Here is what has changed since the previous version: > > 1.) The prerequisite external compliance statements > (IF-MIB.ifCompliance3, IF-INVERTED-STACK-MIB.ifInvCompliance, > EtherLike-MIB.dot3Compliance2, and MAU-MIB.mauModIfCompl3) are now > listed explicitly in the etherWisCompliance DESCRIPTION clause. > > 2.) The OBJECT clauses for etherWisDeviceTxTestPatternMode and > etherWisDeviceRxTestPatternMode no longer state that an > implementation is not required to support certain combinations of > settings because the Clause 45 MDIO registers do not, in fact, > impose any inter-dependencies in the settings. > > 3.) The dates in the LAST-UPDATED and REVISION clauses of the > MODULE-IDENTITY invocation were changed to the current date. > > 4.) References [ETHERIF] and [MAU-MIB] were updated to point to > and > , respectively. > > Note that change #1 brings the document into compliance with the > recently issued MIB review guidelines document > (which postdates the > -06 version of the ETHER-WIS MIB) and that change #2 undoes an > erroneous modification that was introduced into the -05 version. > > As I've noted before the following three normative references > need to be progressed to Proposed Standard or higher prior to or > simultaneously with the WIS MIB document in order for it to be > published as an RFC: > > [SONETng] Tesink, K., "Definitions of Managed Objects for the > SONET/SDH Interface Type", 01.txt>, work in progress. > > [ETHERIF] Flick, J., "Definitions of Managed Objects for the > Ethernet-like Interface Types", > mib-v3-03.txt>, work in progress. > > [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 > Medium Attachment Units (MAUs)", mib-v3-03.txt>, work in progress. > > The IETF last call on [SONETng] recently expired and it is now in > the "waiting for writeup" state. [ETHERIF] and [MAU-MIB] were > recently updated to address A-D review comments, and I believe this > means that the document package consisting of [ETHERIF], [MAU-MIB], > this submission, and draft-ietf-hubmib-1643-to-historic-01.txt is > ready for the next step. > > Thanks and regards, > > Mike > -- > C. M. Heard > heard@pobox.com > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Thu May 22 12:36:11 2003 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 MAA20387 for ; Thu, 22 May 2003 12:36:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4MG3XH22923 for hubmib-archive@odin.ietf.org; Thu, 22 May 2003 12:03:33 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MG3WB22918; Thu, 22 May 2003 12:03:32 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFmhB21850 for ; Thu, 22 May 2003 11:48:43 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19914; Thu, 22 May 2003 12:20:51 -0400 (EDT) Message-Id: <200305221620.MAA19914@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:20:51 -0400 Subject: [Hubmib] Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-4. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-03.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 22 12:36:17 2003 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 MAA20401 for ; Thu, 22 May 2003 12:36:17 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MG3WB22918; Thu, 22 May 2003 12:03:32 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFmhB21850 for ; Thu, 22 May 2003 11:48:43 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19914; Thu, 22 May 2003 12:20:51 -0400 (EDT) Message-Id: <200305221620.MAA19914@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:20:51 -0400 Subject: [Hubmib] Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-4. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-03.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Thu May 22 12:36:27 2003 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 MAA20415 for ; Thu, 22 May 2003 12:36:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4MG3nk22968 for hubmib-archive@odin.ietf.org; Thu, 22 May 2003 12:03:49 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MG3nB22963; Thu, 22 May 2003 12:03:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFo2B21988 for ; Thu, 22 May 2003 11:50:02 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20004; Thu, 22 May 2003 12:22:10 -0400 (EDT) Message-Id: <200305221622.MAA20004@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:22:10 -0400 Subject: [Hubmib] Last Call: Applicability Statement for Reclassification of RFC 1643 to Historic Status to Informational Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Applicability Statement for Reclassification of RFC 1643 to Historic Status as a Informational. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-1643-to-historic-01.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 22 12:36:31 2003 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 MAA20429 for ; Thu, 22 May 2003 12:36:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MG3nB22963; Thu, 22 May 2003 12:03:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFo2B21988 for ; Thu, 22 May 2003 11:50:02 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20004; Thu, 22 May 2003 12:22:10 -0400 (EDT) Message-Id: <200305221622.MAA20004@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:22:10 -0400 Subject: [Hubmib] Last Call: Applicability Statement for Reclassification of RFC 1643 to Historic Status to Informational Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Applicability Statement for Reclassification of RFC 1643 to Historic Status as a Informational. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-1643-to-historic-01.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 14:00:12 2003 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 OAA17525 for ; Fri, 23 May 2003 14:00:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NHxkU14500 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 13:59:46 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NHxjB14495; Fri, 23 May 2003 13:59:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NDgjB16012 for ; Fri, 23 May 2003 09:42:45 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06710; Fri, 23 May 2003 10:14:28 -0400 (EDT) Message-Id: <200305231414.KAA06710@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 23 May 2003 10:14:27 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-05.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@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 Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt Pages : 28 Date : 2003-5-22 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.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-hubmib-power-ethernet-mib-05.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-hubmib-power-ethernet-mib-05.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-5-22142826.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-22142826.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 14:00:17 2003 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 OAA17581 for ; Fri, 23 May 2003 14:00:17 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NHxjB14495; Fri, 23 May 2003 13:59:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NDgjB16012 for ; Fri, 23 May 2003 09:42:45 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06710; Fri, 23 May 2003 10:14:28 -0400 (EDT) Message-Id: <200305231414.KAA06710@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 23 May 2003 10:14:27 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-power-ethernet-mib-05.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@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 Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Power Ethernet MIB Author(s) : A. Berger, D. Romascanu Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt Pages : 28 Date : 2003-5-22 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. The document proposes an extension to the Ethernet-like Interfaces MIB with a set of objects for managing a Power Source Equipment (PSE). Distribution of this memo is unlimited. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.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-hubmib-power-ethernet-mib-05.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-hubmib-power-ethernet-mib-05.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-5-22142826.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-power-ethernet-mib-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-22142826.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 14:47:31 2003 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 OAA19717 for ; Fri, 23 May 2003 14:47:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NIl3R20404 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 14:47:03 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NIl3B20399; Fri, 23 May 2003 14:47:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NIkfB20378 for ; Fri, 23 May 2003 14:46:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19673 for ; Fri, 23 May 2003 14:46:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JHXS-00019O-00 for hubmib@ietf.org; Fri, 23 May 2003 14:45:10 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19JHXR-00019L-00 for hubmib@ietf.org; Fri, 23 May 2003 14:45:09 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h4NIkVl12478; Fri, 23 May 2003 11:46:31 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 23 May 2003 11:46:30 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Fri, 23 May 2003, Internet-Drafts@ietf.org wrote: >A New Internet-Draft is available from the on-line >Internet-Drafts directories. This draft is a work item of the >Ethernet Interfaces and Hub MIB Working Group of the IETF. > > Title : Power Ethernet MIB > Author(s) : A. Berger, D. Romascanu > Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt > Pages : 28 > Date : 2003-5-22 > >This memo defines a portion of the Management Information Base >(MIB) for use with network management protocols in the Internet >community. The document proposes an extension to the >Ethernet-like Interfaces MIB with a set of objects for managing a >Power Source Equipment (PSE). > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.txt In order to help the WG produce the cleanest possible document I've attempted to do a complete "MIB Doctor" review of this draft. The draft does seem to address the comments raised by my previous review, but there are a few additional small issues that I did not catch last time (my apologies to the authors for this). As before, I've not been able to check the document for editorial and technical consistency with the 802.3af draft, since I have not been participating in the Power Ethernet work and do not have access to the specification. I'm hoping that the 802.3af participants who monitor the Hub MIB mailing list will make those checks. The comments below follow the MIB review checklist from Appendix A of . 1.) I-D Boilerplate -- OK 2.) Abstract -- OK 3.) MIB Boilerplate -- OK 4.) IPR Notices -- OK: (a) the required boilerplate is present and no claims are noted; and (b) the following search of the IPR statements on the IETF web site did not reveal any relevant claims: IETF Search Engine _________________________________________________________________ Query: power ethernet____________________________________ Press button to submit your query or reset the form: Search Reset Query Options: Maximum number of hits: [1000] Scope: [IPR Statements________] Match: [All____] Format: [Long_] Sort by: [Score________] _________________________________________________________________ Search results _________________________________________________________________ No matches were found for '(power or powered or powering or powers) and (ethernet or ethernets)' NOTE: if any WG participants are aware of any pertinent intellectual property claims, please post them to the WG mailing list. 5.) References -- OK 6.) Security Considerations Section -- OK 7.) IANA Considerations Section -- OK (none present and none required). 8.) Copyright notices -- OK 9.) MIB compilation -- no problems found from smilint: This command (smilint 0.4.2-pre1, as of Mon May 19 16:33:46 2003) has been processed to get the following results: smilint -m -s -l 6 -i namelength-32 POWER-ETHERNET-MIB no errors found. 10.) Other issues, e.g., stuff in http://www.ietf.org/ID-nits.html that is not covered above: (a) there are a few places in the text of the MIB module (Section 5, "Definitions") and in the references section where the line length exceeds 72 characters. With one exception, the MIB module will obey the 72-character limit once the RFC Editor notes are removed if the three space indentation is taken out; the exception is in the MANDATORY-GROUPS clause of the pethPseCompliance definition. The references section is clean once the RFC Editor notes are removed except for [IEEE-802.3af]; this should not be a problem, however, since the RFC Editor routinely reformats the references. (b) In the second paragraph of Section 3, "Overview": s/IEEE 802.3af WG will not define/IEEE 802.3af WG did not define/ (c) In Section 4, "MIB Structure", third paragraph: s/pethNotificationsControlTable/pethNotificationControlTable/ s/Transmission of notifications/transmission of notifications/ (please be sure to fix this one; it is especially important to get the name of the table name right) 11.) Technical content -- here are the comments on the content of Section 5, "Definitions." (a) There needs to be an RFC Editor note with an instruction to replace "IEEE Draft P802.3af/D4.3" with "IEEE Std 802.3af" in all REFERENCE clauses. Alternatively, if another draft is issued after the draft is approved by the IEEE standards board, then the authors could make this change. (b) The pethPseCompliance compliance statement appears both to be misnamed (it applies only to PSE that have a main power supply, not necessarily to all PSE) and to be redundant with pethCompliance (the latter imposes the same requirements on PSE with a main power supply). I would recommend, therefore, that pethPseCompliance be removed (which would also solve the formatting problem mentioned in 10(a) above). An alternative (which would be acceptable, but which I do not recommend) would be to re-name it to pethMainPSECompliance and change the DESCRIPTION clause to something along the lines of: "Describes the requirements for PSE devices that have a main power supply." (b) It seems that pethMainPseGroup was assigned the OID { pethGroups 3 } by mistake. In order to have no gaps, it should be { pethGroups 2 } instead (sorry for not finding this earlier). (c) It seems that pethNotificationControlGroup was assigned the OID { pethGroups 4 } by mistake. In order to have no gaps, it should be { pethGroups 3 } instead (sorry for not finding this earlier). (d) It seems that pethPsePortNotificationGroup was assigned the OID { pethCompliances 4 } by mistake. For consistency, it should be { pethGroups 4 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left two spaces.] (e) It seems that pethMainPowerNotificationGroup was assigned he OID { pethCompliances 5 } by mistake. or consistency, it should be { pethGroups 5 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left four spaces.] This concludes the POWER-ETHERNET-MIB review comments. Regards, Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 14:47:40 2003 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 OAA19731 for ; Fri, 23 May 2003 14:47:40 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NIl3B20399; Fri, 23 May 2003 14:47:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NIkfB20378 for ; Fri, 23 May 2003 14:46:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19673 for ; Fri, 23 May 2003 14:46:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JHXS-00019O-00 for hubmib@ietf.org; Fri, 23 May 2003 14:45:10 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19JHXR-00019L-00 for hubmib@ietf.org; Fri, 23 May 2003 14:45:09 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h4NIkVl12478; Fri, 23 May 2003 11:46:31 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 23 May 2003 11:46:30 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Fri, 23 May 2003, Internet-Drafts@ietf.org wrote: >A New Internet-Draft is available from the on-line >Internet-Drafts directories. This draft is a work item of the >Ethernet Interfaces and Hub MIB Working Group of the IETF. > > Title : Power Ethernet MIB > Author(s) : A. Berger, D. Romascanu > Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt > Pages : 28 > Date : 2003-5-22 > >This memo defines a portion of the Management Information Base >(MIB) for use with network management protocols in the Internet >community. The document proposes an extension to the >Ethernet-like Interfaces MIB with a set of objects for managing a >Power Source Equipment (PSE). > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05.txt In order to help the WG produce the cleanest possible document I've attempted to do a complete "MIB Doctor" review of this draft. The draft does seem to address the comments raised by my previous review, but there are a few additional small issues that I did not catch last time (my apologies to the authors for this). As before, I've not been able to check the document for editorial and technical consistency with the 802.3af draft, since I have not been participating in the Power Ethernet work and do not have access to the specification. I'm hoping that the 802.3af participants who monitor the Hub MIB mailing list will make those checks. The comments below follow the MIB review checklist from Appendix A of . 1.) I-D Boilerplate -- OK 2.) Abstract -- OK 3.) MIB Boilerplate -- OK 4.) IPR Notices -- OK: (a) the required boilerplate is present and no claims are noted; and (b) the following search of the IPR statements on the IETF web site did not reveal any relevant claims: IETF Search Engine _________________________________________________________________ Query: power ethernet____________________________________ Press button to submit your query or reset the form: Search Reset Query Options: Maximum number of hits: [1000] Scope: [IPR Statements________] Match: [All____] Format: [Long_] Sort by: [Score________] _________________________________________________________________ Search results _________________________________________________________________ No matches were found for '(power or powered or powering or powers) and (ethernet or ethernets)' NOTE: if any WG participants are aware of any pertinent intellectual property claims, please post them to the WG mailing list. 5.) References -- OK 6.) Security Considerations Section -- OK 7.) IANA Considerations Section -- OK (none present and none required). 8.) Copyright notices -- OK 9.) MIB compilation -- no problems found from smilint: This command (smilint 0.4.2-pre1, as of Mon May 19 16:33:46 2003) has been processed to get the following results: smilint -m -s -l 6 -i namelength-32 POWER-ETHERNET-MIB no errors found. 10.) Other issues, e.g., stuff in http://www.ietf.org/ID-nits.html that is not covered above: (a) there are a few places in the text of the MIB module (Section 5, "Definitions") and in the references section where the line length exceeds 72 characters. With one exception, the MIB module will obey the 72-character limit once the RFC Editor notes are removed if the three space indentation is taken out; the exception is in the MANDATORY-GROUPS clause of the pethPseCompliance definition. The references section is clean once the RFC Editor notes are removed except for [IEEE-802.3af]; this should not be a problem, however, since the RFC Editor routinely reformats the references. (b) In the second paragraph of Section 3, "Overview": s/IEEE 802.3af WG will not define/IEEE 802.3af WG did not define/ (c) In Section 4, "MIB Structure", third paragraph: s/pethNotificationsControlTable/pethNotificationControlTable/ s/Transmission of notifications/transmission of notifications/ (please be sure to fix this one; it is especially important to get the name of the table name right) 11.) Technical content -- here are the comments on the content of Section 5, "Definitions." (a) There needs to be an RFC Editor note with an instruction to replace "IEEE Draft P802.3af/D4.3" with "IEEE Std 802.3af" in all REFERENCE clauses. Alternatively, if another draft is issued after the draft is approved by the IEEE standards board, then the authors could make this change. (b) The pethPseCompliance compliance statement appears both to be misnamed (it applies only to PSE that have a main power supply, not necessarily to all PSE) and to be redundant with pethCompliance (the latter imposes the same requirements on PSE with a main power supply). I would recommend, therefore, that pethPseCompliance be removed (which would also solve the formatting problem mentioned in 10(a) above). An alternative (which would be acceptable, but which I do not recommend) would be to re-name it to pethMainPSECompliance and change the DESCRIPTION clause to something along the lines of: "Describes the requirements for PSE devices that have a main power supply." (b) It seems that pethMainPseGroup was assigned the OID { pethGroups 3 } by mistake. In order to have no gaps, it should be { pethGroups 2 } instead (sorry for not finding this earlier). (c) It seems that pethNotificationControlGroup was assigned the OID { pethGroups 4 } by mistake. In order to have no gaps, it should be { pethGroups 3 } instead (sorry for not finding this earlier). (d) It seems that pethPsePortNotificationGroup was assigned the OID { pethCompliances 4 } by mistake. For consistency, it should be { pethGroups 4 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left two spaces.] (e) It seems that pethMainPowerNotificationGroup was assigned he OID { pethCompliances 5 } by mistake. or consistency, it should be { pethGroups 5 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left four spaces.] This concludes the POWER-ETHERNET-MIB review comments. Regards, Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 15:56:33 2003 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 PAA23028 for ; Fri, 23 May 2003 15:56:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NJu7R25778 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 15:56:07 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu7B25773; Fri, 23 May 2003 15:56:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFnFB21925 for ; Thu, 22 May 2003 11:49:15 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19956; Thu, 22 May 2003 12:21:23 -0400 (EDT) Message-Id: <200305221621.MAA19956@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:21:23 -0400 Subject: [Hubmib] Last Call: Definitions of Managed Objects for the Ethernet-like Interface Types to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definitions of Managed Objects for the Ethernet-like Interface Types as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-etherif-mib-v3-03.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 15:56:34 2003 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 PAA23041 for ; Fri, 23 May 2003 15:56:34 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NJu8d25806 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 15:56:08 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu8B25801; Fri, 23 May 2003 15:56:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFnaB21956 for ; Thu, 22 May 2003 11:49:36 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19971; Thu, 22 May 2003 12:21:45 -0400 (EDT) Message-Id: <200305221621.MAA19971@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:21:44 -0400 Subject: [Hubmib] Last Call: Definition of Managed Objects for the Ethernet WAN Interface Sublayer to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definition of Managed Objects for the Ethernet WAN Interface Sublayer as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-07.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 15:56:34 2003 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 PAA23044 for ; Fri, 23 May 2003 15:56:34 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NJu8A25834 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 15:56:08 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu8B25829; Fri, 23 May 2003 15:56:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MLMtB12215 for ; Thu, 22 May 2003 17:22:55 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00243; Thu, 22 May 2003 17:54:57 -0400 (EDT) Message-Id: <200305222154.RAA00243@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 17:54:57 -0400 Subject: [Hubmib] Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-4. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-03.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 15:56:35 2003 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 PAA23054 for ; Fri, 23 May 2003 15:56:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NJu9l25862 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 15:56:09 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu8B25857; Fri, 23 May 2003 15:56:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MLO1B12251 for ; Thu, 22 May 2003 17:24:01 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00375; Thu, 22 May 2003 17:56:02 -0400 (EDT) Message-Id: <200305222156.RAA00375@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 17:56:02 -0400 Subject: [Hubmib] Last Call: Applicability Statement for Reclassification of RFC 1643 to Historic Status to Informational Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Applicability Statement for Reclassification of RFC 1643 to Historic Status as a Informational. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-1643-to-historic-01.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 15:56:39 2003 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 PAA23084 for ; Fri, 23 May 2003 15:56:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu8B25801; Fri, 23 May 2003 15:56:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFnaB21956 for ; Thu, 22 May 2003 11:49:36 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19971; Thu, 22 May 2003 12:21:45 -0400 (EDT) Message-Id: <200305221621.MAA19971@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:21:44 -0400 Subject: [Hubmib] Last Call: Definition of Managed Objects for the Ethernet WAN Interface Sublayer to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definition of Managed Objects for the Ethernet WAN Interface Sublayer as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-07.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 15:56:39 2003 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 PAA23085 for ; Fri, 23 May 2003 15:56:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu8B25857; Fri, 23 May 2003 15:56:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MLO1B12251 for ; Thu, 22 May 2003 17:24:01 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00375; Thu, 22 May 2003 17:56:02 -0400 (EDT) Message-Id: <200305222156.RAA00375@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 17:56:02 -0400 Subject: [Hubmib] Last Call: Applicability Statement for Reclassification of RFC 1643 to Historic Status to Informational Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Applicability Statement for Reclassification of RFC 1643 to Historic Status as a Informational. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-1643-to-historic-01.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 15:56:44 2003 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 PAA23123 for ; Fri, 23 May 2003 15:56:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu7B25773; Fri, 23 May 2003 15:56:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MFnFB21925 for ; Thu, 22 May 2003 11:49:15 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19956; Thu, 22 May 2003 12:21:23 -0400 (EDT) Message-Id: <200305221621.MAA19956@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 12:21:23 -0400 Subject: [Hubmib] Last Call: Definitions of Managed Objects for the Ethernet-like Interface Types to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definitions of Managed Objects for the Ethernet-like Interface Types as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-5. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-etherif-mib-v3-03.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 15:59:28 2003 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 PAA23230 for ; Fri, 23 May 2003 15:59:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NJx2b26091 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 15:59:02 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJx2B26086; Fri, 23 May 2003 15:59:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJw4B26016 for ; Fri, 23 May 2003 15:58:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23170 for ; Fri, 23 May 2003 15:58:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JIeZ-0001p4-00 for hubmib@ietf.org; Fri, 23 May 2003 15:56:35 -0400 Received: from [12.25.1.120] (helo=ctron-dnm.enterasys.com ident=firewall-user) by ietf-mx with esmtp (Exim 4.12) id 19JIeX-0001ox-00 for hubmib@ietf.org; Fri, 23 May 2003 15:56:33 -0400 Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id QAA24994 for ; Fri, 23 May 2003 16:11:16 -0400 (EDT) Received: from nhrocavg2(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1) id xma024984; Fri, 23 May 03 16:10:27 -0400 Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2.ets.enterasys.com with InterScan Messaging Security Suite for SMTP; Fri, 23 May 2003 15:57:58 -0400 Received: from nhrocmbx1 ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 23 May 2003 15:57:58 -0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Date: Fri, 23 May 2003 15:57:58 -0400 Message-ID: Thread-Topic: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Thread-Index: AcMhXIFweAieHzUwRGmordQ4oXIdvwACAC0g From: "McTague, Charles" To: "Hub MIB Mailing List" X-OriginalArrivalTime: 23 May 2003 19:57:58.0424 (UTC) FILETIME=[9BB4D980:01C32165] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4NJw5B26017 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit If this has been covered in previous emails please ignore this question. In the pethPsePortEntry I noticed that entries 6, 9, 10, and 12 are not used. The same sparseness occurs in pethMainPseEntry with entries 5 and 6. Is this sparse OID allocation a result of multiple changes over the 5 drafts and could therefore be compressed, or is there another reason behind it? I realize this is perfectly legal from the syntax side of things, but I thought I would ask. Thanks, chuck --------------------------- Charles McTague Principal Firmware Engineer Enterasys Networks, Inc. >-----Original Message----- >From: C. M. Heard [mailto:heard@pobox.com] >Sent: Fri, 23 May, 2003 2:47 PM >To: Hub MIB Mailing List >Subject: [Hubmib] MIB doctor comments on >draft-ietf-hubmib-power-ethernet-mib-05.txt > > >On Fri, 23 May 2003, Internet-Drafts@ietf.org wrote: >>A New Internet-Draft is available from the on-line >>Internet-Drafts directories. This draft is a work item of the >>Ethernet Interfaces and Hub MIB Working Group of the IETF. >> >> Title : Power Ethernet MIB >> Author(s) : A. Berger, D. Romascanu >> Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt >> Pages : 28 >> Date : 2003-5-22 >> >>This memo defines a portion of the Management Information Base >>(MIB) for use with network management protocols in the Internet >>community. The document proposes an extension to the >>Ethernet-like Interfaces MIB with a set of objects for managing a >>Power Source Equipment (PSE). >> >>A URL for this Internet-Draft is: >>http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-et >hernet-mib-05.txt > >In order to help the WG produce the cleanest possible document I've >attempted to do a complete "MIB Doctor" review of this draft. The >draft does seem to address the comments raised by my previous >review, but there are a few additional small issues that I did not >catch last time (my apologies to the authors for this). As before, >I've not been able to check the document for editorial and technical >consistency with the 802.3af draft, since I have not been >participating in the Power Ethernet work and do not have access to >the specification. I'm hoping that the 802.3af participants who >monitor the Hub MIB mailing list will make those checks. > >The comments below follow the MIB review checklist from Appendix A >of . > >1.) I-D Boilerplate -- OK > >2.) Abstract -- OK > >3.) MIB Boilerplate -- OK > >4.) IPR Notices -- OK: (a) the required boilerplate is present >and no claims are noted; and (b) the following search of the IPR >statements on the IETF web site did not reveal any relevant claims: > > IETF Search Engine > _________________________________________________________________ > > Query: power ethernet____________________________________ > > Press button to submit your query or reset the form: Search Reset > > Query Options: > Maximum number of hits: [1000] > Scope: [IPR Statements________] > Match: [All____] > Format: [Long_] > Sort by: [Score________] > _________________________________________________________________ > > Search results > _________________________________________________________________ > > No matches were found for '(power or powered or powering or powers) > and (ethernet or ethernets)' > >NOTE: if any WG participants are aware of any pertinent intellectual >property claims, please post them to the WG mailing list. > >5.) References -- OK > >6.) Security Considerations Section -- OK > >7.) IANA Considerations Section -- OK (none present and none >required). > >8.) Copyright notices -- OK > >9.) MIB compilation -- no problems found from smilint: > > This command (smilint 0.4.2-pre1, as of Mon May 19 16:33:46 2003) > has been processed to get the following results: > smilint -m -s -l 6 -i namelength-32 POWER-ETHERNET-MIB > > no errors found. > >10.) Other issues, e.g., stuff in http://www.ietf.org/ID-nits.html >that is not covered above: > >(a) there are a few places in the text of the MIB module (Section 5, >"Definitions") and in the references section where the line length >exceeds 72 characters. With one exception, the MIB module will obey >the 72-character limit once the RFC Editor notes are removed if the >three space indentation is taken out; the exception is in the >MANDATORY-GROUPS clause of the pethPseCompliance definition. The >references section is clean once the RFC Editor notes are removed >except for [IEEE-802.3af]; this should not be a problem, however, >since the RFC Editor routinely reformats the references. > >(b) In the second paragraph of Section 3, "Overview": >s/IEEE 802.3af WG will not define/IEEE 802.3af WG did not define/ > >(c) In Section 4, "MIB Structure", third paragraph: >s/pethNotificationsControlTable/pethNotificationControlTable/ >s/Transmission of notifications/transmission of notifications/ > >(please be sure to fix this one; it is especially important to get >the name of the table name right) > >11.) Technical content -- here are the comments on the content of >Section 5, "Definitions." > >(a) There needs to be an RFC Editor note with an instruction to >replace "IEEE Draft P802.3af/D4.3" with "IEEE Std 802.3af" >in all REFERENCE clauses. Alternatively, if another draft is >issued after the draft is approved by the IEEE standards board, >then the authors could make this change. > >(b) The pethPseCompliance compliance statement appears both to be >misnamed (it applies only to PSE that have a main power supply, not >necessarily to all PSE) and to be redundant with pethCompliance (the >latter imposes the same requirements on PSE with a main power >supply). I would recommend, therefore, that pethPseCompliance be >removed (which would also solve the formatting problem mentioned in >10(a) above). An alternative (which would be acceptable, but which >I do not recommend) would be to re-name it to pethMainPSECompliance >and change the DESCRIPTION clause to something along the lines of: > > "Describes the requirements for PSE devices > that have a main power supply." > >(b) It seems that pethMainPseGroup was assigned the OID >{ pethGroups 3 } by mistake. In order to have no gaps, it should be >{ pethGroups 2 } instead (sorry for not finding this earlier). > >(c) It seems that pethNotificationControlGroup was assigned the OID >{ pethGroups 4 } by mistake. In order to have no gaps, it should be >{ pethGroups 3 } instead (sorry for not finding this earlier). > >(d) It seems that pethPsePortNotificationGroup was assigned the OID >{ pethCompliances 4 } by mistake. For consistency, it should be >{ pethGroups 4 } (sorry for not finding this earlier). [It would >also look better if the indentation were consistent with that of >pethNotificationControlGroup, i.e., moved left two spaces.] > >(e) It seems that pethMainPowerNotificationGroup was assigned he OID >{ pethCompliances 5 } by mistake. or consistency, it should be >{ pethGroups 5 } (sorry for not finding this earlier). [It would >also look better if the indentation were consistent with that of >pethNotificationControlGroup, i.e., moved left four spaces.] > >This concludes the POWER-ETHERNET-MIB review comments. > >Regards, > >Mike Heard > >_______________________________________________ >Hubmib mailing list >Hubmib@ietf.org >https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 15:59:33 2003 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 PAA23244 for ; Fri, 23 May 2003 15:59:33 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJx2B26086; Fri, 23 May 2003 15:59:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJw4B26016 for ; Fri, 23 May 2003 15:58:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23170 for ; Fri, 23 May 2003 15:58:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JIeZ-0001p4-00 for hubmib@ietf.org; Fri, 23 May 2003 15:56:35 -0400 Received: from [12.25.1.120] (helo=ctron-dnm.enterasys.com ident=firewall-user) by ietf-mx with esmtp (Exim 4.12) id 19JIeX-0001ox-00 for hubmib@ietf.org; Fri, 23 May 2003 15:56:33 -0400 Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id QAA24994 for ; Fri, 23 May 2003 16:11:16 -0400 (EDT) Received: from nhrocavg2(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1) id xma024984; Fri, 23 May 03 16:10:27 -0400 Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2.ets.enterasys.com with InterScan Messaging Security Suite for SMTP; Fri, 23 May 2003 15:57:58 -0400 Received: from nhrocmbx1 ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 23 May 2003 15:57:58 -0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Date: Fri, 23 May 2003 15:57:58 -0400 Message-ID: Thread-Topic: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Thread-Index: AcMhXIFweAieHzUwRGmordQ4oXIdvwACAC0g From: "McTague, Charles" To: "Hub MIB Mailing List" X-OriginalArrivalTime: 23 May 2003 19:57:58.0424 (UTC) FILETIME=[9BB4D980:01C32165] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4NJw5B26017 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit If this has been covered in previous emails please ignore this question. In the pethPsePortEntry I noticed that entries 6, 9, 10, and 12 are not used. The same sparseness occurs in pethMainPseEntry with entries 5 and 6. Is this sparse OID allocation a result of multiple changes over the 5 drafts and could therefore be compressed, or is there another reason behind it? I realize this is perfectly legal from the syntax side of things, but I thought I would ask. Thanks, chuck --------------------------- Charles McTague Principal Firmware Engineer Enterasys Networks, Inc. >-----Original Message----- >From: C. M. Heard [mailto:heard@pobox.com] >Sent: Fri, 23 May, 2003 2:47 PM >To: Hub MIB Mailing List >Subject: [Hubmib] MIB doctor comments on >draft-ietf-hubmib-power-ethernet-mib-05.txt > > >On Fri, 23 May 2003, Internet-Drafts@ietf.org wrote: >>A New Internet-Draft is available from the on-line >>Internet-Drafts directories. This draft is a work item of the >>Ethernet Interfaces and Hub MIB Working Group of the IETF. >> >> Title : Power Ethernet MIB >> Author(s) : A. Berger, D. Romascanu >> Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt >> Pages : 28 >> Date : 2003-5-22 >> >>This memo defines a portion of the Management Information Base >>(MIB) for use with network management protocols in the Internet >>community. The document proposes an extension to the >>Ethernet-like Interfaces MIB with a set of objects for managing a >>Power Source Equipment (PSE). >> >>A URL for this Internet-Draft is: >>http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-et >hernet-mib-05.txt > >In order to help the WG produce the cleanest possible document I've >attempted to do a complete "MIB Doctor" review of this draft. The >draft does seem to address the comments raised by my previous >review, but there are a few additional small issues that I did not >catch last time (my apologies to the authors for this). As before, >I've not been able to check the document for editorial and technical >consistency with the 802.3af draft, since I have not been >participating in the Power Ethernet work and do not have access to >the specification. I'm hoping that the 802.3af participants who >monitor the Hub MIB mailing list will make those checks. > >The comments below follow the MIB review checklist from Appendix A >of . > >1.) I-D Boilerplate -- OK > >2.) Abstract -- OK > >3.) MIB Boilerplate -- OK > >4.) IPR Notices -- OK: (a) the required boilerplate is present >and no claims are noted; and (b) the following search of the IPR >statements on the IETF web site did not reveal any relevant claims: > > IETF Search Engine > _________________________________________________________________ > > Query: power ethernet____________________________________ > > Press button to submit your query or reset the form: Search Reset > > Query Options: > Maximum number of hits: [1000] > Scope: [IPR Statements________] > Match: [All____] > Format: [Long_] > Sort by: [Score________] > _________________________________________________________________ > > Search results > _________________________________________________________________ > > No matches were found for '(power or powered or powering or powers) > and (ethernet or ethernets)' > >NOTE: if any WG participants are aware of any pertinent intellectual >property claims, please post them to the WG mailing list. > >5.) References -- OK > >6.) Security Considerations Section -- OK > >7.) IANA Considerations Section -- OK (none present and none >required). > >8.) Copyright notices -- OK > >9.) MIB compilation -- no problems found from smilint: > > This command (smilint 0.4.2-pre1, as of Mon May 19 16:33:46 2003) > has been processed to get the following results: > smilint -m -s -l 6 -i namelength-32 POWER-ETHERNET-MIB > > no errors found. > >10.) Other issues, e.g., stuff in http://www.ietf.org/ID-nits.html >that is not covered above: > >(a) there are a few places in the text of the MIB module (Section 5, >"Definitions") and in the references section where the line length >exceeds 72 characters. With one exception, the MIB module will obey >the 72-character limit once the RFC Editor notes are removed if the >three space indentation is taken out; the exception is in the >MANDATORY-GROUPS clause of the pethPseCompliance definition. The >references section is clean once the RFC Editor notes are removed >except for [IEEE-802.3af]; this should not be a problem, however, >since the RFC Editor routinely reformats the references. > >(b) In the second paragraph of Section 3, "Overview": >s/IEEE 802.3af WG will not define/IEEE 802.3af WG did not define/ > >(c) In Section 4, "MIB Structure", third paragraph: >s/pethNotificationsControlTable/pethNotificationControlTable/ >s/Transmission of notifications/transmission of notifications/ > >(please be sure to fix this one; it is especially important to get >the name of the table name right) > >11.) Technical content -- here are the comments on the content of >Section 5, "Definitions." > >(a) There needs to be an RFC Editor note with an instruction to >replace "IEEE Draft P802.3af/D4.3" with "IEEE Std 802.3af" >in all REFERENCE clauses. Alternatively, if another draft is >issued after the draft is approved by the IEEE standards board, >then the authors could make this change. > >(b) The pethPseCompliance compliance statement appears both to be >misnamed (it applies only to PSE that have a main power supply, not >necessarily to all PSE) and to be redundant with pethCompliance (the >latter imposes the same requirements on PSE with a main power >supply). I would recommend, therefore, that pethPseCompliance be >removed (which would also solve the formatting problem mentioned in >10(a) above). An alternative (which would be acceptable, but which >I do not recommend) would be to re-name it to pethMainPSECompliance >and change the DESCRIPTION clause to something along the lines of: > > "Describes the requirements for PSE devices > that have a main power supply." > >(b) It seems that pethMainPseGroup was assigned the OID >{ pethGroups 3 } by mistake. In order to have no gaps, it should be >{ pethGroups 2 } instead (sorry for not finding this earlier). > >(c) It seems that pethNotificationControlGroup was assigned the OID >{ pethGroups 4 } by mistake. In order to have no gaps, it should be >{ pethGroups 3 } instead (sorry for not finding this earlier). > >(d) It seems that pethPsePortNotificationGroup was assigned the OID >{ pethCompliances 4 } by mistake. For consistency, it should be >{ pethGroups 4 } (sorry for not finding this earlier). [It would >also look better if the indentation were consistent with that of >pethNotificationControlGroup, i.e., moved left two spaces.] > >(e) It seems that pethMainPowerNotificationGroup was assigned he OID >{ pethCompliances 5 } by mistake. or consistency, it should be >{ pethGroups 5 } (sorry for not finding this earlier). [It would >also look better if the indentation were consistent with that of >pethNotificationControlGroup, i.e., moved left four spaces.] > >This concludes the POWER-ETHERNET-MIB review comments. > >Regards, > >Mike Heard > >_______________________________________________ >Hubmib mailing list >Hubmib@ietf.org >https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 16:31:33 2003 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 QAA24826 for ; Fri, 23 May 2003 16:31:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NKV8e28716 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 16:31:08 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NKV7B28710; Fri, 23 May 2003 16:31:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NKUnB28625 for ; Fri, 23 May 2003 16:30:49 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24713 for ; Fri, 23 May 2003 16:30:44 -0400 (EDT) Message-Id: <200305232030.QAA24713@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Fri, 23 May 2003 16:30:44 -0400 Subject: [Hubmib] Last CAll: Definitions of Managed Objects for the Ethernet-like Interface Types to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from Ethernet Interfaces and Hub MIB to consider the following Internet-Draft(s) as Proposed Standard. o Ethernet Interfaces and Hub MIB (HUBMIB): Definitions of Managed Objects for the Ethernet-like Interface Types Proposed Standard o Ethernet Interfaces and Hub MIB (HUBMIB): Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Proposed Standard o Ethernet Interfaces and Hub MIB (HUBMIB): Definition of Managed Objects for the Ethernet WAN Interface Sublayer Proposed Standard o Ethernet Interfaces and Hub MIB (HUBMIB): Applicability Statement for Reclassification of RFC 1643 to Historic Status Informational The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-6. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-etherif-mib-v3-03.txt http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-03.txt http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-07.txt http://www.ietf.org/internet-drafts/draft-ietf-hubmib-1643-to-historic-01.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 16:32:01 2003 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 QAA24891 for ; Fri, 23 May 2003 16:32:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NKV7B28710; Fri, 23 May 2003 16:31:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NKUnB28625 for ; Fri, 23 May 2003 16:30:49 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24713 for ; Fri, 23 May 2003 16:30:44 -0400 (EDT) Message-Id: <200305232030.QAA24713@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Fri, 23 May 2003 16:30:44 -0400 Subject: [Hubmib] Last CAll: Definitions of Managed Objects for the Ethernet-like Interface Types to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from Ethernet Interfaces and Hub MIB to consider the following Internet-Draft(s) as Proposed Standard. o Ethernet Interfaces and Hub MIB (HUBMIB): Definitions of Managed Objects for the Ethernet-like Interface Types Proposed Standard o Ethernet Interfaces and Hub MIB (HUBMIB): Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) Proposed Standard o Ethernet Interfaces and Hub MIB (HUBMIB): Definition of Managed Objects for the Ethernet WAN Interface Sublayer Proposed Standard o Ethernet Interfaces and Hub MIB (HUBMIB): Applicability Statement for Reclassification of RFC 1643 to Historic Status Informational The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-6. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-etherif-mib-v3-03.txt http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-03.txt http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-07.txt http://www.ietf.org/internet-drafts/draft-ietf-hubmib-1643-to-historic-01.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 16:45:57 2003 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 PAA23087 for ; Fri, 23 May 2003 15:56:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NJu8B25829; Fri, 23 May 2003 15:56:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4MLMtB12215 for ; Thu, 22 May 2003 17:22:55 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00243; Thu, 22 May 2003 17:54:57 -0400 (EDT) Message-Id: <200305222154.RAA00243@ietf.org> To: IETF-Announce: ; Cc: hubmib@ietf.org From: The IESG Reply-to: iesg@ietf.org Date: Thu, 22 May 2003 17:54:57 -0400 Subject: [Hubmib] Last Call: Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) to Proposed Standard Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , The IESG has received a request from the Ethernet Interfaces and Hub MIB Working Group to consider Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-4. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hubmib-mau-mib-v3-03.txt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 23 17:01:38 2003 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 RAA26038 for ; Fri, 23 May 2003 17:01:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NL1Dr31605 for hubmib-archive@odin.ietf.org; Fri, 23 May 2003 17:01:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NL1DB31599; Fri, 23 May 2003 17:01:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NL0kB31254 for ; Fri, 23 May 2003 17:00:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25966 for ; Fri, 23 May 2003 17:00:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JJdE-0002co-00 for hubmib@ietf.org; Fri, 23 May 2003 16:59:16 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19JJdD-0002cf-00 for hubmib@ietf.org; Fri, 23 May 2003 16:59:15 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h4NL0ec25861 for ; Fri, 23 May 2003 14:00:40 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 23 May 2003 14:00:39 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: RE: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Fri, 23 May 2003, McTague, Charles wrote: > In the pethPsePortEntry I noticed that entries 6, 9, 10, and 12 > are not used. The same sparseness occurs in pethMainPseEntry > with entries 5 and 6. > > Is this sparse OID allocation a result of multiple changes over > the 5 drafts and could therefore be compressed, or is there > another reason behind it? I realize this is perfectly legal > from the syntax side of things, but I thought I would ask. Thanks for pointing this out; I missed it completely, and recommend that the OID assignments be made contiguous. Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 23 17:01:42 2003 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 RAA26056 for ; Fri, 23 May 2003 17:01:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NL1DB31599; Fri, 23 May 2003 17:01:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NL0kB31254 for ; Fri, 23 May 2003 17:00:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25966 for ; Fri, 23 May 2003 17:00:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JJdE-0002co-00 for hubmib@ietf.org; Fri, 23 May 2003 16:59:16 -0400 Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx with esmtp (Exim 4.12) id 19JJdD-0002cf-00 for hubmib@ietf.org; Fri, 23 May 2003 16:59:15 -0400 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id h4NL0ec25861 for ; Fri, 23 May 2003 14:00:40 -0700 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Fri, 23 May 2003 14:00:39 -0700 (PDT) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub MIB Mailing List Subject: RE: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , On Fri, 23 May 2003, McTague, Charles wrote: > In the pethPsePortEntry I noticed that entries 6, 9, 10, and 12 > are not used. The same sparseness occurs in pethMainPseEntry > with entries 5 and 6. > > Is this sparse OID allocation a result of multiple changes over > the 5 drafts and could therefore be compressed, or is there > another reason behind it? I realize this is perfectly legal > from the syntax side of things, but I thought I would ask. Thanks for pointing this out; I missed it completely, and recommend that the OID assignments be made contiguous. Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Sun May 25 13:25:21 2003 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 NAA06418 for ; Sun, 25 May 2003 13:25:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4PHP1918611 for hubmib-archive@odin.ietf.org; Sun, 25 May 2003 13:25:01 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4PHP0B18606; Sun, 25 May 2003 13:25:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4PHNCB18549 for ; Sun, 25 May 2003 13:23:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06388 for ; Sun, 25 May 2003 13:23:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JzBd-0007Oy-00 for hubmib@ietf.org; Sun, 25 May 2003 13:21:33 -0400 Received: from sc-f100-01.extremenetworks.com ([63.251.106.30] helo=extrgate1.extremenetworks.com) by ietf-mx with esmtp (Exim 4.12) id 19JzBd-0007Ot-00 for hubmib@ietf.org; Sun, 25 May 2003 13:21:33 -0400 Received: by extrgate1.extremenetworks.com with Internet Mail Service (5.5.2656.59) id ; Sun, 25 May 2003 10:22:18 -0700 Message-ID: <4C8B0EA487B9554D910B0587CD91395C010FD785@sc-msexch-03.extremenetworks.com> From: Derek Pitcher To: Hub MIB Mailing List Subject: RE: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ether net-mib-05.txt Date: Sun, 25 May 2003 10:21:40 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Regarding the pethPsePortType object. In order to provide more flexibility and allow for a greater variety of PD types to be represented without requiring a MIB update, a better representation of this would be to use a limited DisplayString type. -----Original Message----- From: C. M. Heard [mailto:heard@pobox.com] Sent: Friday, May 23, 2003 11:47 AM To: Hub MIB Mailing List Subject: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt On Fri, 23 May 2003, Internet-Drafts@ietf.org wrote: >A New Internet-Draft is available from the on-line >Internet-Drafts directories. This draft is a work item of the >Ethernet Interfaces and Hub MIB Working Group of the IETF. > > Title : Power Ethernet MIB > Author(s) : A. Berger, D. Romascanu > Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt > Pages : 28 > Date : 2003-5-22 > >This memo defines a portion of the Management Information Base >(MIB) for use with network management protocols in the Internet >community. The document proposes an extension to the >Ethernet-like Interfaces MIB with a set of objects for managing a >Power Source Equipment (PSE). > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05 .txt In order to help the WG produce the cleanest possible document I've attempted to do a complete "MIB Doctor" review of this draft. The draft does seem to address the comments raised by my previous review, but there are a few additional small issues that I did not catch last time (my apologies to the authors for this). As before, I've not been able to check the document for editorial and technical consistency with the 802.3af draft, since I have not been participating in the Power Ethernet work and do not have access to the specification. I'm hoping that the 802.3af participants who monitor the Hub MIB mailing list will make those checks. The comments below follow the MIB review checklist from Appendix A of . 1.) I-D Boilerplate -- OK 2.) Abstract -- OK 3.) MIB Boilerplate -- OK 4.) IPR Notices -- OK: (a) the required boilerplate is present and no claims are noted; and (b) the following search of the IPR statements on the IETF web site did not reveal any relevant claims: IETF Search Engine _________________________________________________________________ Query: power ethernet____________________________________ Press button to submit your query or reset the form: Search Reset Query Options: Maximum number of hits: [1000] Scope: [IPR Statements________] Match: [All____] Format: [Long_] Sort by: [Score________] _________________________________________________________________ Search results _________________________________________________________________ No matches were found for '(power or powered or powering or powers) and (ethernet or ethernets)' NOTE: if any WG participants are aware of any pertinent intellectual property claims, please post them to the WG mailing list. 5.) References -- OK 6.) Security Considerations Section -- OK 7.) IANA Considerations Section -- OK (none present and none required). 8.) Copyright notices -- OK 9.) MIB compilation -- no problems found from smilint: This command (smilint 0.4.2-pre1, as of Mon May 19 16:33:46 2003) has been processed to get the following results: smilint -m -s -l 6 -i namelength-32 POWER-ETHERNET-MIB no errors found. 10.) Other issues, e.g., stuff in http://www.ietf.org/ID-nits.html that is not covered above: (a) there are a few places in the text of the MIB module (Section 5, "Definitions") and in the references section where the line length exceeds 72 characters. With one exception, the MIB module will obey the 72-character limit once the RFC Editor notes are removed if the three space indentation is taken out; the exception is in the MANDATORY-GROUPS clause of the pethPseCompliance definition. The references section is clean once the RFC Editor notes are removed except for [IEEE-802.3af]; this should not be a problem, however, since the RFC Editor routinely reformats the references. (b) In the second paragraph of Section 3, "Overview": s/IEEE 802.3af WG will not define/IEEE 802.3af WG did not define/ (c) In Section 4, "MIB Structure", third paragraph: s/pethNotificationsControlTable/pethNotificationControlTable/ s/Transmission of notifications/transmission of notifications/ (please be sure to fix this one; it is especially important to get the name of the table name right) 11.) Technical content -- here are the comments on the content of Section 5, "Definitions." (a) There needs to be an RFC Editor note with an instruction to replace "IEEE Draft P802.3af/D4.3" with "IEEE Std 802.3af" in all REFERENCE clauses. Alternatively, if another draft is issued after the draft is approved by the IEEE standards board, then the authors could make this change. (b) The pethPseCompliance compliance statement appears both to be misnamed (it applies only to PSE that have a main power supply, not necessarily to all PSE) and to be redundant with pethCompliance (the latter imposes the same requirements on PSE with a main power supply). I would recommend, therefore, that pethPseCompliance be removed (which would also solve the formatting problem mentioned in 10(a) above). An alternative (which would be acceptable, but which I do not recommend) would be to re-name it to pethMainPSECompliance and change the DESCRIPTION clause to something along the lines of: "Describes the requirements for PSE devices that have a main power supply." (b) It seems that pethMainPseGroup was assigned the OID { pethGroups 3 } by mistake. In order to have no gaps, it should be { pethGroups 2 } instead (sorry for not finding this earlier). (c) It seems that pethNotificationControlGroup was assigned the OID { pethGroups 4 } by mistake. In order to have no gaps, it should be { pethGroups 3 } instead (sorry for not finding this earlier). (d) It seems that pethPsePortNotificationGroup was assigned the OID { pethCompliances 4 } by mistake. For consistency, it should be { pethGroups 4 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left two spaces.] (e) It seems that pethMainPowerNotificationGroup was assigned he OID { pethCompliances 5 } by mistake. or consistency, it should be { pethGroups 5 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left four spaces.] This concludes the POWER-ETHERNET-MIB review comments. Regards, Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Sun May 25 13:25:30 2003 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 NAA06433 for ; Sun, 25 May 2003 13:25:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4PHP0B18606; Sun, 25 May 2003 13:25:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4PHNCB18549 for ; Sun, 25 May 2003 13:23:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06388 for ; Sun, 25 May 2003 13:23:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JzBd-0007Oy-00 for hubmib@ietf.org; Sun, 25 May 2003 13:21:33 -0400 Received: from sc-f100-01.extremenetworks.com ([63.251.106.30] helo=extrgate1.extremenetworks.com) by ietf-mx with esmtp (Exim 4.12) id 19JzBd-0007Ot-00 for hubmib@ietf.org; Sun, 25 May 2003 13:21:33 -0400 Received: by extrgate1.extremenetworks.com with Internet Mail Service (5.5.2656.59) id ; Sun, 25 May 2003 10:22:18 -0700 Message-ID: <4C8B0EA487B9554D910B0587CD91395C010FD785@sc-msexch-03.extremenetworks.com> From: Derek Pitcher To: Hub MIB Mailing List Subject: RE: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ether net-mib-05.txt Date: Sun, 25 May 2003 10:21:40 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Regarding the pethPsePortType object. In order to provide more flexibility and allow for a greater variety of PD types to be represented without requiring a MIB update, a better representation of this would be to use a limited DisplayString type. -----Original Message----- From: C. M. Heard [mailto:heard@pobox.com] Sent: Friday, May 23, 2003 11:47 AM To: Hub MIB Mailing List Subject: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt On Fri, 23 May 2003, Internet-Drafts@ietf.org wrote: >A New Internet-Draft is available from the on-line >Internet-Drafts directories. This draft is a work item of the >Ethernet Interfaces and Hub MIB Working Group of the IETF. > > Title : Power Ethernet MIB > Author(s) : A. Berger, D. Romascanu > Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt > Pages : 28 > Date : 2003-5-22 > >This memo defines a portion of the Management Information Base >(MIB) for use with network management protocols in the Internet >community. The document proposes an extension to the >Ethernet-like Interfaces MIB with a set of objects for managing a >Power Source Equipment (PSE). > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-05 .txt In order to help the WG produce the cleanest possible document I've attempted to do a complete "MIB Doctor" review of this draft. The draft does seem to address the comments raised by my previous review, but there are a few additional small issues that I did not catch last time (my apologies to the authors for this). As before, I've not been able to check the document for editorial and technical consistency with the 802.3af draft, since I have not been participating in the Power Ethernet work and do not have access to the specification. I'm hoping that the 802.3af participants who monitor the Hub MIB mailing list will make those checks. The comments below follow the MIB review checklist from Appendix A of . 1.) I-D Boilerplate -- OK 2.) Abstract -- OK 3.) MIB Boilerplate -- OK 4.) IPR Notices -- OK: (a) the required boilerplate is present and no claims are noted; and (b) the following search of the IPR statements on the IETF web site did not reveal any relevant claims: IETF Search Engine _________________________________________________________________ Query: power ethernet____________________________________ Press button to submit your query or reset the form: Search Reset Query Options: Maximum number of hits: [1000] Scope: [IPR Statements________] Match: [All____] Format: [Long_] Sort by: [Score________] _________________________________________________________________ Search results _________________________________________________________________ No matches were found for '(power or powered or powering or powers) and (ethernet or ethernets)' NOTE: if any WG participants are aware of any pertinent intellectual property claims, please post them to the WG mailing list. 5.) References -- OK 6.) Security Considerations Section -- OK 7.) IANA Considerations Section -- OK (none present and none required). 8.) Copyright notices -- OK 9.) MIB compilation -- no problems found from smilint: This command (smilint 0.4.2-pre1, as of Mon May 19 16:33:46 2003) has been processed to get the following results: smilint -m -s -l 6 -i namelength-32 POWER-ETHERNET-MIB no errors found. 10.) Other issues, e.g., stuff in http://www.ietf.org/ID-nits.html that is not covered above: (a) there are a few places in the text of the MIB module (Section 5, "Definitions") and in the references section where the line length exceeds 72 characters. With one exception, the MIB module will obey the 72-character limit once the RFC Editor notes are removed if the three space indentation is taken out; the exception is in the MANDATORY-GROUPS clause of the pethPseCompliance definition. The references section is clean once the RFC Editor notes are removed except for [IEEE-802.3af]; this should not be a problem, however, since the RFC Editor routinely reformats the references. (b) In the second paragraph of Section 3, "Overview": s/IEEE 802.3af WG will not define/IEEE 802.3af WG did not define/ (c) In Section 4, "MIB Structure", third paragraph: s/pethNotificationsControlTable/pethNotificationControlTable/ s/Transmission of notifications/transmission of notifications/ (please be sure to fix this one; it is especially important to get the name of the table name right) 11.) Technical content -- here are the comments on the content of Section 5, "Definitions." (a) There needs to be an RFC Editor note with an instruction to replace "IEEE Draft P802.3af/D4.3" with "IEEE Std 802.3af" in all REFERENCE clauses. Alternatively, if another draft is issued after the draft is approved by the IEEE standards board, then the authors could make this change. (b) The pethPseCompliance compliance statement appears both to be misnamed (it applies only to PSE that have a main power supply, not necessarily to all PSE) and to be redundant with pethCompliance (the latter imposes the same requirements on PSE with a main power supply). I would recommend, therefore, that pethPseCompliance be removed (which would also solve the formatting problem mentioned in 10(a) above). An alternative (which would be acceptable, but which I do not recommend) would be to re-name it to pethMainPSECompliance and change the DESCRIPTION clause to something along the lines of: "Describes the requirements for PSE devices that have a main power supply." (b) It seems that pethMainPseGroup was assigned the OID { pethGroups 3 } by mistake. In order to have no gaps, it should be { pethGroups 2 } instead (sorry for not finding this earlier). (c) It seems that pethNotificationControlGroup was assigned the OID { pethGroups 4 } by mistake. In order to have no gaps, it should be { pethGroups 3 } instead (sorry for not finding this earlier). (d) It seems that pethPsePortNotificationGroup was assigned the OID { pethCompliances 4 } by mistake. For consistency, it should be { pethGroups 4 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left two spaces.] (e) It seems that pethMainPowerNotificationGroup was assigned he OID { pethCompliances 5 } by mistake. or consistency, it should be { pethGroups 5 } (sorry for not finding this earlier). [It would also look better if the indentation were consistent with that of pethNotificationControlGroup, i.e., moved left four spaces.] This concludes the POWER-ETHERNET-MIB review comments. Regards, Mike Heard _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Mon May 26 03:26:37 2003 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 DAA04576 for ; Mon, 26 May 2003 03:26:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4Q7QWW14624 for hubmib-archive@odin.ietf.org; Mon, 26 May 2003 03:26:32 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4Q7QVB14619; Mon, 26 May 2003 03:26:31 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4Q7PCB14573 for ; Mon, 26 May 2003 03:25:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04545 for ; Mon, 26 May 2003 03:24:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19KCKB-00049L-00 for hubmib@ietf.org; Mon, 26 May 2003 03:23:15 -0400 Received: from iere.net.avaya.com ([198.152.12.101]) by ietf-mx with esmtp (Exim 4.12) id 19KCKA-00049I-00 for hubmib@ietf.org; Mon, 26 May 2003 03:23:14 -0400 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 h4Q7Lcu01826 for ; Mon, 26 May 2003 03:21:39 -0400 (EDT) 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 h4Q7LbT01802 for ; Mon, 26 May 2003 03:21:38 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Date: Mon, 26 May 2003 10:24:43 +0300 Message-ID: Thread-Topic: [Hubmib] MIB doctor comments on draft-ietf-hubmib-power-ethernet-mib-05.txt Thread-Index: AcMi5R9nCAw0SfsvRS2kMVasTaJ2WwAcYuOg From: "Romascanu, Dan (Dan)" To: "Derek Pitcher" , "Hub MIB Mailing List" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4Q7PCB14574 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Thanks for the comment. Can you clarify what you mean by 'limited'? - limited size? Dan > -----Original Message----- > From: Derek Pitcher [mailto:dpitcher@extremenetworks.com] > Sent: Sunday, May 25, 2003 8:22 PM > To: Hub MIB Mailing List > Subject: RE: [Hubmib] MIB doctor comments on > draft-ietf-hubmib-power-ethernet-mib-05.txt > > > Regarding the pethPsePortType object. In order to provide > more flexibility > and allow for a greater variety of PD types to be represented without > requiring a MIB update, a better representation of this would > be to use a > limited DisplayString type. > > > > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: Friday, May 23, 2003 11:47 AM > To: Hub MIB Mailing List > Subject: [Hubmib] MIB doctor comments on > draft-ietf-hubmib-power-ethernet-mib-05.txt > > > On Fri, 23 May 2003, Internet-Drafts@ietf.org wrote: > >A New Internet-Draft is available from the on-line > >Internet-Drafts directories. This draft is a work item of the > >Ethernet Interfaces and Hub MIB Working Group of the IETF. > > > > Title : Power Ethernet MIB > > Author(s) : A. Berger, D. Romascanu > > Filename : draft-ietf-hubmib-power-ethernet-mib-05.txt > > Pages : 28 > > Date : 2003-5-22 > > > >This memo defines a portion of the Management Information Base > >(MIB) for use with network management protocols in the Internet > >community. The document proposes an extension to the > >Ethernet-like Interfaces MIB with a set of objects for managing a > >Power Source Equipment (PSE). > > > >A URL for this Internet-Draft is: > >http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-e > thernet-mib-05 > .txt > > In order to help the WG produce the cleanest possible document I've > attempted to do a complete "MIB Doctor" review of this draft. The > draft does seem to address the comments raised by my previous > review, but there are a few additional small issues that I did not > catch last time (my apologies to the authors for this). As before, > I've not been able to check the document for editorial and technical > consistency with the 802.3af draft, since I have not been > participating in the Power Ethernet work and do not have access to > the specification. I'm hoping that the 802.3af participants who > monitor the Hub MIB mailing list will make those checks. > > The comments below follow the MIB review checklist from Appendix A > of . > > 1.) I-D Boilerplate -- OK > > 2.) Abstract -- OK > > 3.) MIB Boilerplate -- OK > > 4.) IPR Notices -- OK: (a) the required boilerplate is present > and no claims are noted; and (b) the following search of the IPR > statements on the IETF web site did not reveal any relevant claims: > > IETF Search Engine > _________________________________________________________________ > > Query: power ethernet____________________________________ > > Press button to submit your query or reset the form: Search Reset > > Query Options: > Maximum number of hits: [1000] > Scope: [IPR Statements________] > Match: [All____] > Format: [Long_] > Sort by: [Score________] > _________________________________________________________________ > > Search results > _________________________________________________________________ > > No matches were found for '(power or powered or powering or powers) > and (ethernet or ethernets)' > > NOTE: if any WG participants are aware of any pertinent intellectual > property claims, please post them to the WG mailing list. > > 5.) References -- OK > > 6.) Security Considerations Section -- OK > > 7.) IANA Considerations Section -- OK (none present and none > required). > > 8.) Copyright notices -- OK > > 9.) MIB compilation -- no problems found from smilint: > > This command (smilint 0.4.2-pre1, as of Mon May 19 16:33:46 2003) > has been processed to get the following results: > smilint -m -s -l 6 -i namelength-32 POWER-ETHERNET-MIB > > no errors found. > > 10.) Other issues, e.g., stuff in http://www.ietf.org/ID-nits.html > that is not covered above: > > (a) there are a few places in the text of the MIB module (Section 5, > "Definitions") and in the references section where the line length > exceeds 72 characters. With one exception, the MIB module will obey > the 72-character limit once the RFC Editor notes are removed if the > three space indentation is taken out; the exception is in the > MANDATORY-GROUPS clause of the pethPseCompliance definition. The > references section is clean once the RFC Editor notes are removed > except for [IEEE-802.3af]; this should not be a problem, however, > since the RFC Editor routinely reformats the references. > > (b) In the second paragraph of Section 3, "Overview": > s/IEEE 802.3af WG will not define/IEEE 802.3af WG did not define/ > > (c) In Section 4, "MIB Structure", third paragraph: > s/pethNotificationsControlTable/pethNotificationControlTable/ > s/Transmission of notifications/transmission of notifications/ > > (please be sure to fix this one; it is especially important to get > the name of the table name right) > > 11.) Technical content -- here are the comments on the content of > Section 5, "Definitions." > > (a) There needs to be an RFC Editor note with an instruction to > replace "IEEE Draft P802.3af/D4.3" with "IEEE Std 802.3af" > in all REFERENCE clauses. Alternatively, if another draft is > issued after the draft is approved by the IEEE standards board, > then the authors could make this change. > > (b) The pethPseCompliance compliance statement appears both to be > misnamed (it applies only to PSE that have a main power supply, not > necessarily to all PSE) and to be redundant with pethCompliance (the > latter imposes the same requirements on PSE with a main power > supply). I would recommend, therefore, that pethPseCompliance be > removed (which would also solve the formatting problem mentioned in > 10(a) above). An alternative (which would be acceptable, but which > I do not recommend) would be to re-name it to pethMainPSECompliance > and change the DESCRIPTION clause to something along the lines of: > > "Describes the requirements for PSE devices > that have a main power supply." > > (b) It seems that pethMainPseGroup was assigned the OID > { pethGroups 3 } by mistake. In order to have no gaps, it should be > { pethGroups 2 } instead (sorry for not finding this earlier). > > (c) It seems that pethNotificationControlGroup was assigned the OID > { pethGroups 4 } by mistake. In order to have no gaps, it should be > { pethGroups 3 } instead (sorry for not finding this earlier). > > (d) It seems that pethPsePortNotificationGroup was assigned the OID > { pethCompliances 4 } by mistake. For consistency, it should be > { pethGroups 4 } (sorry for not finding this earlier). [It would > also look better if the indentation were consistent with that of > pethNotificationControlGroup, i.e., moved left two spaces.] > > (e) It seems that pethMainPowerNotificationGroup was assigned he OID > { pethCompliances 5 } by mistake. or consistency, it should be > { pethGroups 5 } (sorry for not finding this earlier). [It would > also look better if the indentation were consistent with that of > pethNotificationControlGroup, i.e., moved left four spaces.] > > This concludes the POWER-ETHERNET-MIB review comments. > > Regards, > > Mike Heard > > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Tue May 27 05:18:22 2003 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 FAA05520 for ; Tue, 27 May 2003 05:18:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4R9IK100881 for hubmib-archive@odin.ietf.org; Tue, 27 May 2003 05:18:20 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4R9IKB00875; Tue, 27 May 2003 05:18:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4R9FAB00748 for ; Tue, 27 May 2003 05:15:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05451 for ; Tue, 27 May 2003 05:14:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19KaW5-0002WO-00 for hubmib@ietf.org; Tue, 27 May 2003 05:13:09 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19KaW4-0002WL-00 for hubmib@ietf.org; Tue, 27 May 2003 05:13:09 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id FAB02949 for ; Tue, 27 May 2003 05:12:00 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id FAA02941 for ; Tue, 27 May 2003 05:11:59 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C32430.66E74AD0" Date: Tue, 27 May 2003 12:14:39 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Message-ID: Thread-Topic: Power Ethernet MIB - WG Last Call Thread-Index: AcMkMGd5giRk1iYmT6iZllSRxwwMGA== From: "Romascanu, Dan (Dan)" To: Cc: Subject: [Hubmib] Power Ethernet MIB - WG Last Call Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C32430.66E74AD0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable This is an Ethernet Interfaces and Hub MIB WG Last Call for the Power = Ethernet MIB. The document can be found at:=20 http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-ethernet-mib-= 05 All comments must be sent to the WG e-mail list hubmib@ietf.org, until = Tuesday, June 10, 2003. This is a second WG Last Call. I decided to call for it, as there have = been significant changes in the Internet-Draft, as well as in the IEEE = 802.3af Draft since the previous Last Call. The IEEE 802.3af WG is = copied on this announcement, in order to invite comments from the = participants in the IEEE process. With the IEEE 802,3af standard in = final phases of approval, we have now a stable basis, and we hope to = wrap up this work pretty fast.=20 The comments already received relative to the Internet-Draft will be = incorporated in the Last Call comments - no need to send them again. Regards, Dan ------_=_NextPart_001_01C32430.66E74AD0 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Power Ethernet MIB - WG Last Call

This is an Ethernet = Interfaces and Hub MIB WG Last Call for the Power Ethernet MIB. The = document can be found at:

http://www.ietf.org/internet-drafts/draft-ietf-hubmib-power-e= thernet-mib-05

All comments must be sent to = the WG e-mail list hubmib@ietf.org, until Tuesday, June 10, = 2003.

This is a second WG Last = Call. I decided to call for it, as there have been significant changes = in the Internet-Draft, as well as in the IEEE 802.3af Draft since the = previous Last Call. The IEEE 802.3af WG is copied on this announcement, = in order  to invite comments from the participants in the IEEE = process. With the IEEE 802,3af standard in final phases of approval, we = have now a stable basis, and we hope to wrap up this work pretty fast. =

The comments already received = relative to the Internet-Draft will be incorporated in the Last Call = comments - no need to send them again.

Regards,

Dan

------_=_NextPart_001_01C32430.66E74AD0-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Thu May 29 11:37:51 2003 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 LAA07597 for ; Thu, 29 May 2003 11:37:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4TFbNH30729 for hubmib-archive@odin.ietf.org; Thu, 29 May 2003 11:37:23 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TFbMB30716; Thu, 29 May 2003 11:37:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TFa3B29952 for ; Thu, 29 May 2003 11:36:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07556 for ; Thu, 29 May 2003 11:36:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LPQ7-00007W-00 for hubmib@ietf.org; Thu, 29 May 2003 11:34:23 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19LPQ6-00007T-00 for hubmib@ietf.org; Thu, 29 May 2003 11:34:22 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06256 for ; Thu, 29 May 2003 11:33:18 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06225 for ; Thu, 29 May 2003 11:33:17 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C325F8.001DBAD0" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Date: Thu, 29 May 2003 18:35:58 +0300 Message-ID: Thread-Topic: IEEE 802.3ah MIB? Thread-Index: AcMl+AAhfdHi5owEROeNud8ZfI0LfQ== From: "Romascanu, Dan (Dan)" To: Cc: Subject: [Hubmib] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C325F8.001DBAD0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Our Area Directors copied me on a query that they received about = eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list = last January, and I do not remember having received any feedback. Truth = is that by that point in time the Management and OAM clauses in the EFM = work were pretty open. This has probably changed by now and with the = 802.3ah Draft getting closer to Sponsor Ballot, it is probably a good = time to ask the question again. is there interest for a 802.3ah (EFM) = MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As = the IETF rules say, we need a visible level of interest, and volunteers = to commit to do the work in order to be able to discuss re-chartering = the WG with the ADs.=20 I am copying the IEEE 802.3ah list - feedback is obviously welcome from = them as well. Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG ------_=_NextPart_001_01C325F8.001DBAD0 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable IEEE 802.3ah MIB?

Our Area Directors copied me = on a query that they received about eventual work on a IEEE 802.3af MIB. = I have sent a query to the WG list last January, and I do not remember = having received any feedback. Truth is that by that point in time the = Management and OAM clauses in the EFM work were pretty open. This has = probably changed by now and with the 802.3ah Draft getting closer to = Sponsor Ballot, it is probably a good time to ask the question again. is = there interest for a 802.3ah (EFM) MIB work in the IETF Ethernet = Interfaces and Hub MIB Working Group? As the IETF rules say, we need a = visible level of interest, and volunteers to commit to do the work in = order to be able to discuss re-chartering the WG with the ADs. =

I am copying the IEEE 802.3ah = list - feedback is obviously welcome from them as well.

Thanks,

Dan

Dan Romascanu,

Chair, IETF Ethernet = Interfaces and Hub MIB WG

------_=_NextPart_001_01C325F8.001DBAD0-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 29 11:37:58 2003 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 LAA07611 for ; Thu, 29 May 2003 11:37:58 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TFbMB30716; Thu, 29 May 2003 11:37:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TFa3B29952 for ; Thu, 29 May 2003 11:36:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07556 for ; Thu, 29 May 2003 11:36:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LPQ7-00007W-00 for hubmib@ietf.org; Thu, 29 May 2003 11:34:23 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19LPQ6-00007T-00 for hubmib@ietf.org; Thu, 29 May 2003 11:34:22 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06256 for ; Thu, 29 May 2003 11:33:18 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06225 for ; Thu, 29 May 2003 11:33:17 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C325F8.001DBAD0" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Date: Thu, 29 May 2003 18:35:58 +0300 Message-ID: Thread-Topic: IEEE 802.3ah MIB? Thread-Index: AcMl+AAhfdHi5owEROeNud8ZfI0LfQ== From: "Romascanu, Dan (Dan)" To: Cc: Subject: [Hubmib] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C325F8.001DBAD0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Our Area Directors copied me on a query that they received about = eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list = last January, and I do not remember having received any feedback. Truth = is that by that point in time the Management and OAM clauses in the EFM = work were pretty open. This has probably changed by now and with the = 802.3ah Draft getting closer to Sponsor Ballot, it is probably a good = time to ask the question again. is there interest for a 802.3ah (EFM) = MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As = the IETF rules say, we need a visible level of interest, and volunteers = to commit to do the work in order to be able to discuss re-chartering = the WG with the ADs.=20 I am copying the IEEE 802.3ah list - feedback is obviously welcome from = them as well. Thanks, Dan Dan Romascanu, Chair, IETF Ethernet Interfaces and Hub MIB WG ------_=_NextPart_001_01C325F8.001DBAD0 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable IEEE 802.3ah MIB?

Our Area Directors copied me = on a query that they received about eventual work on a IEEE 802.3af MIB. = I have sent a query to the WG list last January, and I do not remember = having received any feedback. Truth is that by that point in time the = Management and OAM clauses in the EFM work were pretty open. This has = probably changed by now and with the 802.3ah Draft getting closer to = Sponsor Ballot, it is probably a good time to ask the question again. is = there interest for a 802.3ah (EFM) MIB work in the IETF Ethernet = Interfaces and Hub MIB Working Group? As the IETF rules say, we need a = visible level of interest, and volunteers to commit to do the work in = order to be able to discuss re-chartering the WG with the ADs. =

I am copying the IEEE 802.3ah = list - feedback is obviously welcome from them as well.

Thanks,

Dan

Dan Romascanu,

Chair, IETF Ethernet = Interfaces and Hub MIB WG

------_=_NextPart_001_01C325F8.001DBAD0-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 30 04:09:39 2003 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 EAA24396 for ; Fri, 30 May 2003 04:09:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4U89B313255 for hubmib-archive@odin.ietf.org; Fri, 30 May 2003 04:09:11 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U898B13249; Fri, 30 May 2003 04:09:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U5bHB23522 for ; Fri, 30 May 2003 01:37:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08645 for ; Fri, 30 May 2003 01:37:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LcYA-0007PQ-00 for hubmib@ietf.org; Fri, 30 May 2003 01:35:34 -0400 Received: from ajax.cnchost.com ([207.155.248.31]) by ietf-mx with esmtp (Exim 4.12) id 19LcY9-0007PN-00 for hubmib@ietf.org; Fri, 30 May 2003 01:35:33 -0400 Received: from dominetsystems.com (adsl-64-171-25-157.dsl.sntc01.pacbell.net [64.171.25.157]) by ajax.cnchost.com id BAA01702; Fri, 30 May 2003 01:37:10 -0400 (EDT) [ConcentricHost SMTP Relay 1.15] Message-ID: <3ED6ED94.30600@dominetsystems.com> Date: Thu, 29 May 2003 22:35:16 -0700 From: Howard Frazier User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" CC: hubmib@ietf.org, stds-802-3-efm@ieee.org References: Content-Type: text/plain; charset=windows-1255; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Hubmib] Re: [EFM] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dan, I offer my hope that the IETF will continue the practice of reviewing the work of the IEEE 802.3 Working Group and developing compatible MIB definitions in the Ethernet Interfaces and Hub MIB Working Group. This relationship has been very successful in the past, and I have every expectation that it will continue to be successful. If you would like the IEEE 802.3ah EFM Task Force to provide a statement along these lines, I would be happy to raise the topic at our next meeting, which is scheduled for June 24-25 in Ottawa. The meeting announcement can be found at the following URL: http://www.nortelnetworks.com/corporate/events/2003b/ieee802-3ah/index.html Any interested members of the IETF Ethernet Interfaces and Hub MIB Working Group are of course welcome to attend this meeting. Howard Frazier Chair, IEEE 802.3ah EFM Task Force Romascanu, Dan (Dan) wrote: > Our Area Directors copied me on a query that they received about > eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list > last January, and I do not remember having received any feedback. Truth > is that by that point in time the Management and OAM clauses in the EFM > work were pretty open. This has probably changed by now and with the > 802.3ah Draft getting closer to Sponsor Ballot, it is probably a good > time to ask the question again. is there interest for a 802.3ah (EFM) > MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As > the IETF rules say, we need a visible level of interest, and volunteers > to commit to do the work in order to be able to discuss re-chartering > the WG with the ADs. > > I am copying the IEEE 802.3ah list - feedback is obviously welcome from > them as well. > > Thanks, > > Dan > > Dan Romascanu, > > Chair, IETF Ethernet Interfaces and Hub MIB WG > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 30 04:09:45 2003 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 EAA24410 for ; Fri, 30 May 2003 04:09:45 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U898B13249; Fri, 30 May 2003 04:09:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U5bHB23522 for ; Fri, 30 May 2003 01:37:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08645 for ; Fri, 30 May 2003 01:37:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LcYA-0007PQ-00 for hubmib@ietf.org; Fri, 30 May 2003 01:35:34 -0400 Received: from ajax.cnchost.com ([207.155.248.31]) by ietf-mx with esmtp (Exim 4.12) id 19LcY9-0007PN-00 for hubmib@ietf.org; Fri, 30 May 2003 01:35:33 -0400 Received: from dominetsystems.com (adsl-64-171-25-157.dsl.sntc01.pacbell.net [64.171.25.157]) by ajax.cnchost.com id BAA01702; Fri, 30 May 2003 01:37:10 -0400 (EDT) [ConcentricHost SMTP Relay 1.15] Message-ID: <3ED6ED94.30600@dominetsystems.com> Date: Thu, 29 May 2003 22:35:16 -0700 From: Howard Frazier User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" CC: hubmib@ietf.org, stds-802-3-efm@ieee.org References: Content-Type: text/plain; charset=windows-1255; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Hubmib] Re: [EFM] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dan, I offer my hope that the IETF will continue the practice of reviewing the work of the IEEE 802.3 Working Group and developing compatible MIB definitions in the Ethernet Interfaces and Hub MIB Working Group. This relationship has been very successful in the past, and I have every expectation that it will continue to be successful. If you would like the IEEE 802.3ah EFM Task Force to provide a statement along these lines, I would be happy to raise the topic at our next meeting, which is scheduled for June 24-25 in Ottawa. The meeting announcement can be found at the following URL: http://www.nortelnetworks.com/corporate/events/2003b/ieee802-3ah/index.html Any interested members of the IETF Ethernet Interfaces and Hub MIB Working Group are of course welcome to attend this meeting. Howard Frazier Chair, IEEE 802.3ah EFM Task Force Romascanu, Dan (Dan) wrote: > Our Area Directors copied me on a query that they received about > eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list > last January, and I do not remember having received any feedback. Truth > is that by that point in time the Management and OAM clauses in the EFM > work were pretty open. This has probably changed by now and with the > 802.3ah Draft getting closer to Sponsor Ballot, it is probably a good > time to ask the question again. is there interest for a 802.3ah (EFM) > MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As > the IETF rules say, we need a visible level of interest, and volunteers > to commit to do the work in order to be able to discuss re-chartering > the WG with the ADs. > > I am copying the IEEE 802.3ah list - feedback is obviously welcome from > them as well. > > Thanks, > > Dan > > Dan Romascanu, > > Chair, IETF Ethernet Interfaces and Hub MIB WG > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 30 04:20:29 2003 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 EAA24755 for ; Fri, 30 May 2003 04:20:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4U8K2f13705 for hubmib-archive@odin.ietf.org; Fri, 30 May 2003 04:20:02 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8K1B13699; Fri, 30 May 2003 04:20:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8JdB13652 for ; Fri, 30 May 2003 04:19:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24712 for ; Fri, 30 May 2003 04:19:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Lf5J-0001AR-00 for hubmib@ietf.org; Fri, 30 May 2003 04:17:57 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19Lf5I-0001AO-00 for hubmib@ietf.org; Fri, 30 May 2003 04:17:57 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA18078 for ; Fri, 30 May 2003 04:16:54 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA18068 for ; Fri, 30 May 2003 04:16:53 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Date: Fri, 30 May 2003 11:19:34 +0300 Message-ID: Thread-Topic: [EFM] IEEE 802.3ah MIB? Thread-Index: AcMmbYaneGj32yuCRhqtztloKfMn3gAFVg3Q From: "Romascanu, Dan (Dan)" To: "Howard Frazier" Cc: , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4U8JdB13653 Subject: [Hubmib] RE: [EFM] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Howard, Your position and the support of the IEEE 802.3ah EFM Task Force was recorded and I thank you for it. Even more useful than a statement would be if in the Ottawa meeting you would test the interest of people to participate in the SNMP MIB work. As in many other standard bodies, the work in the IETF relies exclusively on the volunteer work of the participants in the process (sometimes with support from their employers), and nothing has too many chances to happen without individuals expressing their interest to write the standards, and later implement them. Regards, Dan > -----Original Message----- > From: Howard Frazier [mailto:millardo@dominetsystems.com] > Sent: Friday, May 30, 2003 8:35 AM > To: Romascanu, Dan (Dan) > Cc: hubmib@ietf.org; stds-802-3-efm@ieee.org > Subject: Re: [EFM] IEEE 802.3ah MIB? > > > > Dan, > > I offer my hope that the IETF will continue the practice of > reviewing the work of the IEEE 802.3 Working Group and > developing compatible MIB definitions in the Ethernet Interfaces and > Hub MIB Working Group. This relationship has been very > successful in the past, and I have every expectation that > it will continue to be successful. > > If you would like the IEEE 802.3ah EFM Task Force to provide a > statement along these lines, I would be happy to raise the > topic at our next meeting, which is scheduled for June 24-25 in > Ottawa. The meeting announcement can be found at the following URL: > > http://www.nortelnetworks.com/corporate/events/2003b/ieee802-3 ah/index.html Any interested members of the IETF Ethernet Interfaces and Hub MIB Working Group are of course welcome to attend this meeting. Howard Frazier Chair, IEEE 802.3ah EFM Task Force Romascanu, Dan (Dan) wrote: > Our Area Directors copied me on a query that they received about > eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list > last January, and I do not remember having received any feedback. Truth > is that by that point in time the Management and OAM clauses in the EFM > work were pretty open. This has probably changed by now and with the > 802.3ah Draft getting closer to Sponsor Ballot, it is probably a good > time to ask the question again. is there interest for a 802.3ah (EFM) > MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As > the IETF rules say, we need a visible level of interest, and volunteers > to commit to do the work in order to be able to discuss re-chartering > the WG with the ADs. > > I am copying the IEEE 802.3ah list - feedback is obviously welcome from > them as well. > > Thanks, > > Dan > > Dan Romascanu, > > Chair, IETF Ethernet Interfaces and Hub MIB WG > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 30 04:21:04 2003 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 EAA24801 for ; Fri, 30 May 2003 04:21:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8K1B13699; Fri, 30 May 2003 04:20:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8JdB13652 for ; Fri, 30 May 2003 04:19:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24712 for ; Fri, 30 May 2003 04:19:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Lf5J-0001AR-00 for hubmib@ietf.org; Fri, 30 May 2003 04:17:57 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19Lf5I-0001AO-00 for hubmib@ietf.org; Fri, 30 May 2003 04:17:57 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA18078 for ; Fri, 30 May 2003 04:16:54 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id EAA18068 for ; Fri, 30 May 2003 04:16:53 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Date: Fri, 30 May 2003 11:19:34 +0300 Message-ID: Thread-Topic: [EFM] IEEE 802.3ah MIB? Thread-Index: AcMmbYaneGj32yuCRhqtztloKfMn3gAFVg3Q From: "Romascanu, Dan (Dan)" To: "Howard Frazier" Cc: , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4U8JdB13653 Subject: [Hubmib] RE: [EFM] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Howard, Your position and the support of the IEEE 802.3ah EFM Task Force was recorded and I thank you for it. Even more useful than a statement would be if in the Ottawa meeting you would test the interest of people to participate in the SNMP MIB work. As in many other standard bodies, the work in the IETF relies exclusively on the volunteer work of the participants in the process (sometimes with support from their employers), and nothing has too many chances to happen without individuals expressing their interest to write the standards, and later implement them. Regards, Dan > -----Original Message----- > From: Howard Frazier [mailto:millardo@dominetsystems.com] > Sent: Friday, May 30, 2003 8:35 AM > To: Romascanu, Dan (Dan) > Cc: hubmib@ietf.org; stds-802-3-efm@ieee.org > Subject: Re: [EFM] IEEE 802.3ah MIB? > > > > Dan, > > I offer my hope that the IETF will continue the practice of > reviewing the work of the IEEE 802.3 Working Group and > developing compatible MIB definitions in the Ethernet Interfaces and > Hub MIB Working Group. This relationship has been very > successful in the past, and I have every expectation that > it will continue to be successful. > > If you would like the IEEE 802.3ah EFM Task Force to provide a > statement along these lines, I would be happy to raise the > topic at our next meeting, which is scheduled for June 24-25 in > Ottawa. The meeting announcement can be found at the following URL: > > http://www.nortelnetworks.com/corporate/events/2003b/ieee802-3 ah/index.html Any interested members of the IETF Ethernet Interfaces and Hub MIB Working Group are of course welcome to attend this meeting. Howard Frazier Chair, IEEE 802.3ah EFM Task Force Romascanu, Dan (Dan) wrote: > Our Area Directors copied me on a query that they received about > eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list > last January, and I do not remember having received any feedback. Truth > is that by that point in time the Management and OAM clauses in the EFM > work were pretty open. This has probably changed by now and with the > 802.3ah Draft getting closer to Sponsor Ballot, it is probably a good > time to ask the question again. is there interest for a 802.3ah (EFM) > MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As > the IETF rules say, we need a visible level of interest, and volunteers > to commit to do the work in order to be able to discuss re-chartering > the WG with the ADs. > > I am copying the IEEE 802.3ah list - feedback is obviously welcome from > them as well. > > Thanks, > > Dan > > Dan Romascanu, > > Chair, IETF Ethernet Interfaces and Hub MIB WG > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From mailnull@www1.ietf.org Fri May 30 04:35:30 2003 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 EAA25104 for ; Fri, 30 May 2003 04:35:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4U8Z2s14320 for hubmib-archive@odin.ietf.org; Fri, 30 May 2003 04:35:02 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8Z2B14315; Fri, 30 May 2003 04:35:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8TrB14097 for ; Fri, 30 May 2003 04:29:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24956 for ; Fri, 30 May 2003 04:29:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LfFD-0001Dz-00 for hubmib@ietf.org; Fri, 30 May 2003 04:28:11 -0400 Received: from agamemnon.cnchost.com ([207.155.252.31]) by ietf-mx with esmtp (Exim 4.12) id 19LfFC-0001Dw-00 for hubmib@ietf.org; Fri, 30 May 2003 04:28:10 -0400 Received: from dominetsystems.com (adsl-64-171-25-157.dsl.sntc01.pacbell.net [64.171.25.157]) by agamemnon.cnchost.com id EAA22181; Fri, 30 May 2003 04:29:47 -0400 (EDT) [ConcentricHost SMTP Relay 1.15] Message-ID: <3ED71609.8000403@dominetsystems.com> Date: Fri, 30 May 2003 01:27:53 -0700 From: Howard Frazier User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" CC: hubmib@ietf.org, stds-802-3-efm@ieee.org References: Content-Type: text/plain; charset=windows-1255; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Hubmib] Re: [EFM] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dan, I will ask Matt Squire, the chairman of the IEEE 802.3ah OAM sub task force (with responsibility for all aspects of management in EFM) to test the interest and the level of support, and see if we can sign up some volunteers. Howard Frazier Chair, IEEE 802.3ah EFM Task Force Romascanu, Dan (Dan) wrote: > Howard, > > Your position and the support of the IEEE 802.3ah EFM Task Force was recorded and I thank you for it. Even more useful than a statement would be if in the Ottawa meeting you would test the interest of people to participate in the SNMP MIB work. As in many other standard bodies, the work in the IETF relies exclusively on the volunteer work of the participants in the process (sometimes with support from their employers), and nothing has too many chances to happen without individuals expressing their interest to write the standards, and later implement them. > > Regards, > > Dan > > >>-----Original Message----- >>From: Howard Frazier [mailto:millardo@dominetsystems.com] >>Sent: Friday, May 30, 2003 8:35 AM >>To: Romascanu, Dan (Dan) >>Cc: hubmib@ietf.org; stds-802-3-efm@ieee.org >>Subject: Re: [EFM] IEEE 802.3ah MIB? >> >> >> >>Dan, >> >>I offer my hope that the IETF will continue the practice of >>reviewing the work of the IEEE 802.3 Working Group and >>developing compatible MIB definitions in the Ethernet Interfaces and >>Hub MIB Working Group. This relationship has been very >>successful in the past, and I have every expectation that >>it will continue to be successful. >> >>If you would like the IEEE 802.3ah EFM Task Force to provide a >>statement along these lines, I would be happy to raise the >>topic at our next meeting, which is scheduled for June 24-25 in >>Ottawa. The meeting announcement can be found at the following URL: >> >>http://www.nortelnetworks.com/corporate/events/2003b/ieee802-3 >> > ah/index.html > > Any interested members of the IETF Ethernet Interfaces and > Hub MIB Working Group are of course welcome to attend this meeting. > > Howard Frazier > Chair, IEEE 802.3ah EFM Task Force > > Romascanu, Dan (Dan) wrote: > > >>Our Area Directors copied me on a query that they received about >>eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list >>last January, and I do not remember having received any feedback. Truth >>is that by that point in time the Management and OAM clauses in the EFM >>work were pretty open. This has probably changed by now and with the >>802.3ah Draft getting closer to Sponsor Ballot, it is probably a good >>time to ask the question again. is there interest for a 802.3ah (EFM) >>MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As >>the IETF rules say, we need a visible level of interest, and volunteers >>to commit to do the work in order to be able to discuss re-chartering >>the WG with the ADs. >> >>I am copying the IEEE 802.3ah list - feedback is obviously welcome from >>them as well. >> >>Thanks, >> >>Dan >> >>Dan Romascanu, >> >>Chair, IETF Ethernet Interfaces and Hub MIB WG >> >> > > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Fri May 30 04:35:37 2003 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 EAA25118 for ; Fri, 30 May 2003 04:35:37 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8Z2B14315; Fri, 30 May 2003 04:35:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U8TrB14097 for ; Fri, 30 May 2003 04:29:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24956 for ; Fri, 30 May 2003 04:29:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LfFD-0001Dz-00 for hubmib@ietf.org; Fri, 30 May 2003 04:28:11 -0400 Received: from agamemnon.cnchost.com ([207.155.252.31]) by ietf-mx with esmtp (Exim 4.12) id 19LfFC-0001Dw-00 for hubmib@ietf.org; Fri, 30 May 2003 04:28:10 -0400 Received: from dominetsystems.com (adsl-64-171-25-157.dsl.sntc01.pacbell.net [64.171.25.157]) by agamemnon.cnchost.com id EAA22181; Fri, 30 May 2003 04:29:47 -0400 (EDT) [ConcentricHost SMTP Relay 1.15] Message-ID: <3ED71609.8000403@dominetsystems.com> Date: Fri, 30 May 2003 01:27:53 -0700 From: Howard Frazier User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3 X-Accept-Language: en-us MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" CC: hubmib@ietf.org, stds-802-3-efm@ieee.org References: Content-Type: text/plain; charset=windows-1255; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Hubmib] Re: [EFM] IEEE 802.3ah MIB? Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dan, I will ask Matt Squire, the chairman of the IEEE 802.3ah OAM sub task force (with responsibility for all aspects of management in EFM) to test the interest and the level of support, and see if we can sign up some volunteers. Howard Frazier Chair, IEEE 802.3ah EFM Task Force Romascanu, Dan (Dan) wrote: > Howard, > > Your position and the support of the IEEE 802.3ah EFM Task Force was recorded and I thank you for it. Even more useful than a statement would be if in the Ottawa meeting you would test the interest of people to participate in the SNMP MIB work. As in many other standard bodies, the work in the IETF relies exclusively on the volunteer work of the participants in the process (sometimes with support from their employers), and nothing has too many chances to happen without individuals expressing their interest to write the standards, and later implement them. > > Regards, > > Dan > > >>-----Original Message----- >>From: Howard Frazier [mailto:millardo@dominetsystems.com] >>Sent: Friday, May 30, 2003 8:35 AM >>To: Romascanu, Dan (Dan) >>Cc: hubmib@ietf.org; stds-802-3-efm@ieee.org >>Subject: Re: [EFM] IEEE 802.3ah MIB? >> >> >> >>Dan, >> >>I offer my hope that the IETF will continue the practice of >>reviewing the work of the IEEE 802.3 Working Group and >>developing compatible MIB definitions in the Ethernet Interfaces and >>Hub MIB Working Group. This relationship has been very >>successful in the past, and I have every expectation that >>it will continue to be successful. >> >>If you would like the IEEE 802.3ah EFM Task Force to provide a >>statement along these lines, I would be happy to raise the >>topic at our next meeting, which is scheduled for June 24-25 in >>Ottawa. The meeting announcement can be found at the following URL: >> >>http://www.nortelnetworks.com/corporate/events/2003b/ieee802-3 >> > ah/index.html > > Any interested members of the IETF Ethernet Interfaces and > Hub MIB Working Group are of course welcome to attend this meeting. > > Howard Frazier > Chair, IEEE 802.3ah EFM Task Force > > Romascanu, Dan (Dan) wrote: > > >>Our Area Directors copied me on a query that they received about >>eventual work on a IEEE 802.3af MIB. I have sent a query to the WG list >>last January, and I do not remember having received any feedback. Truth >>is that by that point in time the Management and OAM clauses in the EFM >>work were pretty open. This has probably changed by now and with the >>802.3ah Draft getting closer to Sponsor Ballot, it is probably a good >>time to ask the question again. is there interest for a 802.3ah (EFM) >>MIB work in the IETF Ethernet Interfaces and Hub MIB Working Group? As >>the IETF rules say, we need a visible level of interest, and volunteers >>to commit to do the work in order to be able to discuss re-chartering >>the WG with the ADs. >> >>I am copying the IEEE 802.3ah list - feedback is obviously welcome from >>them as well. >> >>Thanks, >> >>Dan >> >>Dan Romascanu, >> >>Chair, IETF Ethernet Interfaces and Hub MIB WG >> >> > > > > _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib