From mailman-bounces@ietf.org Mon Nov 1 08:56:18 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03645 for ; Mon, 1 Nov 2004 08:56:17 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZjS-0000Lf-GO for hubmib-archive@lists.ietf.org; Mon, 01 Nov 2004 05:48:14 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: hubmib-archive@ietf.org X-No-Archive: yes Message-ID: Date: Mon, 01 Nov 2004 05:18:57 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org Content-Transfer-Encoding: 7bit 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, mailman-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: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@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 hubmib-bounces@ietf.org Thu Nov 4 06:47:23 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11642 for ; Thu, 4 Nov 2004 06:47:23 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPg2x-0006To-Ku; Thu, 04 Nov 2004 06:44:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPg2A-0006Ko-3k for hubmib@megatron.ietf.org; Thu, 04 Nov 2004 06:44:06 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11430 for ; Thu, 4 Nov 2004 06:44:03 -0500 (EST) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPgHd-0001aG-80 for hubmib@ietf.org; Thu, 04 Nov 2004 07:00:08 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iA4BgC3i021901 for ; Thu, 4 Nov 2004 06:42:12 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iA4Bg53i021742 for ; Thu, 4 Nov 2004 06:42:06 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 4 Nov 2004 13:43:53 +0200 Message-ID: Thread-Topic: Working Group Last Call for the EFM MIB Documents Thread-Index: AcTCY49a++kgaYuOShKoX2qyOcsEYA== From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 1.0 (+) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: "Mreview \(E-mail\)" , stds-802-3@ieee.org Subject: [Hubmib] Working Group Last Call for the EFM MIB Documents X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0956242284==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0956242284== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4C263.8F553534" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4C263.8F553534 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable The Ethernet Interfaces and Hub MIB Working Group completed the work on = the EFM MIB documents, and intents to submit these documents to the IESG = for consideration as Proposed Standards. The WG members and all other = interested participants are invited to review the documents and send = their comments to hubmib@ietf.org, until December 2, 2004 the latest. The documents are available at: http://24.199.201.22/draft-ietf-hubmib-efm-mib-02.txt (missed the IETF = submission date by a few hours - will be re-submitted after Washington) http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-e= pon-mib-02.txt http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-c= u-mib-02.txt Regards, Dan ------_=_NextPart_001_01C4C263.8F553534 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Working Group Last Call for the EFM MIB Documents

The Ethernet Interfaces and = Hub MIB Working Group completed the work on the EFM MIB documents, and = intents to submit these documents to the IESG for consideration as = Proposed Standards. The WG members and all other interested participants = are invited to review the documents and send their comments to = hubmib@ietf.org, until December 2, 2004 the latest.

The documents are available = at:

http://24.= 199.201.22/draft-ietf-hubmib-efm-mib-02.txt (missed the IETF = submission date by a few hours - will be re-submitted after = Washington)

http://www.ietf.cnri.reston.va.us/internet-drafts= /draft-ietf-hubmib-efm-epon-mib-02.txt

http://www.ietf.cnri.reston.va.us/internet-drafts/d= raft-ietf-hubmib-efm-cu-mib-02.txt

Regards,

Dan

------_=_NextPart_001_01C4C263.8F553534-- --===============0956242284== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0956242284==-- From hubmib-bounces@ietf.org Thu Nov 4 13:14:36 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17898 for ; Thu, 4 Nov 2004 13:14:36 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPm2u-0004m0-Mf; Thu, 04 Nov 2004 13:09:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPm0W-00049B-Or for hubmib@megatron.ietf.org; Thu, 04 Nov 2004 13:06:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17036 for ; Thu, 4 Nov 2004 13:06:46 -0500 (EST) Received: from [213.70.90.131] (helo=mail.advaoptical.de) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPmG4-0002lm-J1 for hubmib@ietf.org; Thu, 04 Nov 2004 13:22:54 -0500 Received: from muc-srv-mail2.advaoptical.com (unverified) by mail.advaoptical.de (Content Technologies SMTPRS 4.3.1) with ESMTP id for ; Thu, 4 Nov 2004 19:05:17 +0100 Received: from muc-srv-mail.advaoptical.com ([172.20.1.46]) by muc-srv-mail2.advaoptical.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 4 Nov 2004 19:06:36 +0100 Received: from yrk-srv-mail.yrk.advaoptical.com ([172.22.21.13]) by muc-srv-mail.advaoptical.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 4 Nov 2004 19:06:36 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Date: Thu, 4 Nov 2004 18:06:35 -0000 Message-ID: <149127BC7EEE5A48B1F550A57086C1EB04597A@yrk-srv-mail.yrk.advaoptical.com> Thread-Topic: Working Group Last Call for the EFM MIB Documents Thread-Index: AcTCY49a++kgaYuOShKoX2qyOcsEYAANSWlw From: "John Messenger" To: X-OriginalArrivalTime: 04 Nov 2004 18:06:36.0627 (UTC) FILETIME=[0664CA30:01C4C299] X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] RE: [802.3] Working Group Last Call for the EFM MIB Documents X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Hi, I have reviewed the EFM-MIB (common MIB only) and it seems good to = me. Regards, -- John -- John Messenger (JMessenger@advaoptical.com)=20 R&D Manager, Software=20 ADVA Optical Networking Ltd.=20 +44-1904-699309=20 www.advaoptical.com=20 > The WG members and all other interested participants are invited to = review the > documents and send their comments to hubmib@ietf.org, until December = 2, 2004 the latest. _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Thu Nov 4 13:48:00 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21007 for ; Thu, 4 Nov 2004 13:48:00 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPmQ5-0001BL-Sd; Thu, 04 Nov 2004 13:33:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPmJf-0007M5-Cv for hubmib@megatron.ietf.org; Thu, 04 Nov 2004 13:26:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18884 for ; Thu, 4 Nov 2004 13:26:32 -0500 (EST) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPmZE-0003FP-67 for hubmib@ietf.org; Thu, 04 Nov 2004 13:42:41 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iA4IOh3i015596 for ; Thu, 4 Nov 2004 13:24:43 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iA4ILt3i011977 for ; Thu, 4 Nov 2004 13:22:49 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] RE: [802.3] Working Group Last Call for the EFM MIBDocuments Date: Thu, 4 Nov 2004 20:23:16 +0200 Message-ID: Thread-Topic: Working Group Last Call for the EFM MIB Documents Thread-Index: AcTCY49a++kgaYuOShKoX2qyOcsEYAANSWlwAACf0eA= From: "Romascanu, Dan \(Dan\)" To: "John Messenger" , X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: quoted-printable X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Thanks John. I should mention that such messages ('I read the documents or document = and it seems good to me') are welcome as part of the review.=20 Regards, Dan > -----Original Message----- > From: hubmib-bounces@ietf.org=20 > [mailto:hubmib-bounces@ietf.org]On Behalf > Of John Messenger > Sent: 04 November, 2004 8:07 PM > To: hubmib@ietf.org > Subject: [Hubmib] RE: [802.3] Working Group Last Call for the EFM > MIBDocuments >=20 >=20 > Hi, I have reviewed the EFM-MIB (common MIB only) and it=20 > seems good to me. > Regards, > -- John > -- > John Messenger (JMessenger@advaoptical.com)=20 > R&D Manager, Software=20 > ADVA Optical Networking Ltd.=20 > +44-1904-699309=20 > www.advaoptical.com=20 >=20 > > The WG members and all other interested participants are=20 > invited to review the > > documents and send their comments to hubmib@ietf.org, until=20 > December 2, 2004 the latest. >=20 > _______________________________________________ > Hubmib mailing list > Hubmib@ietf.org > https://www1.ietf.org/mailman/listinfo/hubmib >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Thu Nov 18 02:52:21 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26389 for ; Thu, 18 Nov 2004 02:52:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUh2w-0000x8-8o; Thu, 18 Nov 2004 02:49:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUgyU-0008Ss-9j for hubmib@megatron.ietf.org; Thu, 18 Nov 2004 02:45:02 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25907 for ; Thu, 18 Nov 2004 02:45:00 -0500 (EST) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUh12-0002QN-Uf for hubmib@ietf.org; Thu, 18 Nov 2004 02:47:42 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAI7ac2m027847 for ; Thu, 18 Nov 2004 02:36:38 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAI7aZ2m027792 for ; Thu, 18 Nov 2004 02:36:36 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 18 Nov 2004 09:44:55 +0200 Message-ID: Thread-Topic: Mail Delivery (failure dromasca@avaya.com) Thread-Index: AcTNQn8wCLjHntf+TTW/JCKPWK3ccAAAAANW From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 0.5 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Subject: [Hubmib] Out of Office AutoReply: Mail Delivery (failure dromasca@avaya.com) X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1555062878==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============1555062878== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4CD42.7F3C1634" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4CD42.7F3C1634 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I will be traveling for business purposes between November 7 and 19. My = e-mail connectivity may be scarce during this period, and there may be = delays in my e-mail answers. I will however check voice mail daily, and = can be reached for urgent matters at the mobile phone number = +1-917-622-7831. Regards, Dan ------_=_NextPart_001_01C4CD42.7F3C1634 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Out of Office AutoReply: <Possible SPAM> Mail Delivery = (failure dromasca@avaya.com)

I will be traveling for business purposes between = November 7 and 19.  My e-mail connectivity may be scarce during = this period, and there may be delays in my e-mail answers. I will = however check voice mail daily, and can be reached for urgent matters at = the mobile phone number +1-917-622-7831.

Regards,

Dan

------_=_NextPart_001_01C4CD42.7F3C1634-- --===============1555062878== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============1555062878==-- From hubmib-bounces@ietf.org Thu Nov 18 20:57:51 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16481 for ; Thu, 18 Nov 2004 20:57:51 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUxw9-0001go-PK; Thu, 18 Nov 2004 20:51:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUxul-0001Sd-CJ; Thu, 18 Nov 2004 20:50:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15941; Thu, 18 Nov 2004 20:50:17 -0500 (EST) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUxxU-0005hj-Nm; Thu, 18 Nov 2004 20:53:09 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAJ1mOZ4001582; Thu, 18 Nov 2004 20:48:24 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAJ1mMZ4001557; Thu, 18 Nov 2004 20:48:23 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 19 Nov 2004 03:50:14 +0200 Message-ID: Thread-Topic: [Bridge-mib] FW: [802.1] 802.1 PARs Thread-Index: AcTMzSobN3CZslaPQTyFbuMi0xouRgAyTipwABCOz0A= From: "Romascanu, Dan \(Dan\)" To: , X-Spam-Score: 0.0 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Content-Transfer-Encoding: quoted-printable Cc: hubmib@ietf.org, STDS-802-1-L@listserv.ieee.org Subject: [Hubmib] RE: [Bridge-mib] FW: [802.1] 802.1 PARs X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org Content-Transfer-Encoding: quoted-printable My understanding from the discussions at the 802.1 Plenary session this = week is that all 802.1 projects will include the definition of the = management model, management objects, and an SMIv2 MIB definition = wherever applicable - even if this is not explicitly mentioned in the = PAR. My understanding is that all the three projects whose PARs is being = discussed now will have such MIB modules defined.=20 - 802.1aj may extend the 802.3ae OAM. If so, it may need at least an = extension of the EFM OAM MIB defined now in hubmib. They also are = talking about some kind of agent-sub-agent model, possibly using the = extensions of the OAM protocol - 802.1ak looks like will need to extend the son-of-2674 MIB for MRP = operation Regards, Dan > -----Original Message----- > From: bridge-mib-bounces@ietf.org=20 > [mailto:bridge-mib-bounces@ietf.org]On Behalf Of David B Harrington > Sent: 18 November, 2004 7:49 PM > To: bridge-mib@ietf.org > Subject: [Bridge-mib] FW: [802.1] 802.1 PARs >=20 >=20 > FYI.=20 >=20 > There are three PARs being considered in IEEE 802.1 > The first will definitely use a MIB. > The second will either use a MIB directly, or indirectly. > I'm not sure if the third PAR plans to develop a MIB a not. > =20 > The appropriate mailing list for IEEE 802.1 mib module discussion is > STDS-802-1-L@listserv.ieee.org. > To subscribe to the STDS-802-1-L list, go to > http://www.ieee802.org/1/email-pages/ > To see the general information about 802,1, including how they work > and how to participate, go to http://www.ieee802.org/1/ > To see presentations on the technology, go to > http://www.ieee802.org/1/files/public/docs2004 > =20 >=20 > David Harrington > dbharrington@comcast.net > co-chair, IETF Bridge WG > =20 > ________________________________ >=20 > From: IEEE 802.1 [mailto:hdk-0316.pflrk@att.net] On Behalf Of > Tony Jeffree > Sent: Wednesday, November 17, 2004 12:44 PM > To: STDS-802-1-L@listserv.ieee.org > Subject: [802.1] 802.1 PARs > =09 > =09 > I have uploaded revised versions of the 3 802.1 proposed PARs, > with changes made in resolution of comments received.=20 > =09 > PLEASE NOTE that in response to Pat Thaler's comment that > accepted practice avoids the use if "i" in project numbering, the > P802.1ai PAR has been renumbered as p802.1ak. > =09 > The 5c's are unchanged, with the exception of the p802.1ai 5c > which has been relabeled as p802.1ak. > =09 > The files for the revised PARs and 5Cs are located here: > =09 > =09 > http://www.ieee802.org/1/files/public/docs2004/802-1ah-draft-par-for-3 > 0-day-rule-revised.htm > http://www.ieee802.org/1/files/public/docs2004/802-1ah-5c.pdf > =09 > =09 > http://www.ieee802.org/1/files/public/docs2004/802-1aj-draft-par-for-3 > 0-day-rule-revised.htm > =09 > 30-day-rule-revised.htm> > http://www.ieee802.org/1/files/public/docs2004/802-1-aj-5c.pdf > =09 > =09 > > http://www.ieee802.org/1/files/public/docs2004/802-1ak-draft-par-for-3 > 0-day-rule-revised.htm > http://www.ieee802.org/1/files/public/docs2004/802-1ak-5c.pdf > =09 > =09 >=20 > Regards, > Tony > IEEE 802.1 list info: > http://www.ieee802.org/1/email-pages/sjqnf904.html=20 >=20 >=20 >=20 >=20 > _______________________________________________ > Bridge-mib mailing list > Bridge-mib@ietf.org > https://www1.ietf.org/mailman/listinfo/bridge-mib >=20 _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Thu Nov 25 04:13:04 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18741 for ; Thu, 25 Nov 2004 04:13:04 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFVu-0003iP-Rf; Thu, 25 Nov 2004 04:02:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFNL-00018P-Dv for hubmib@megatron.ietf.org; Thu, 25 Nov 2004 03:53:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16606 for ; Thu, 25 Nov 2004 03:53:13 -0500 (EST) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXFRO-0005KQ-0N for hubmib@ietf.org; Thu, 25 Nov 2004 03:57:26 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAP8ijri009758 for ; Thu, 25 Nov 2004 03:44:45 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id iAP8ihri009685 for ; Thu, 25 Nov 2004 03:44:44 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 25 Nov 2004 10:53:10 +0200 Message-ID: Thread-Topic: Working Group Last Call for the EFM MIB Documents Thread-Index: AcTCY49a++kgaYuOShKoX2qyOcsEYAQaCLpg From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 1.1 (+) X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0 Subject: [Hubmib] FW: Working Group Last Call for the EFM MIB Documents X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0924232304==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0924232304== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4D2CC.30E29D46" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4D2CC.30E29D46 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable There is one more week until the WGLC expires. The silence on the list = concerns me. Please send your comments to the list until December 2nd. = Comments like 'I read and I liked the draft, seems OK to me' are welcome = as well.=20 =20 Regards, Dan -----Original Message----- From: owner-mreview@ops.ietf.org [mailto:owner-mreview@ops.ietf.org]On = Behalf Of Romascanu, Dan (Dan) Sent: 04 November, 2004 1:44 PM To: hubmib@ietf.org Cc: Mreview (E-mail); stds-802-3@ieee.org Subject: Working Group Last Call for the EFM MIB Documents The Ethernet Interfaces and Hub MIB Working Group completed the work on = the EFM MIB documents, and intents to submit these documents to the IESG = for consideration as Proposed Standards. The WG members and all other = interested participants are invited to review the documents and send = their comments to hubmib@ietf.org, until December 2, 2004 the latest. The documents are available at: http://24.199.201.22/draft-ietf-hubmib-efm-mib-02.txt (missed the IETF = submission date by a few hours - will be re-submitted after Washington) http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-e= pon-mib-02.txt http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-hubmib-efm-c= u-mib-02.txt Regards, Dan ------_=_NextPart_001_01C4D2CC.30E29D46 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Working Group Last Call for the EFM MIB Documents
There is one more week until the WGLC = expires.=20 The silence on the list concerns me. Please send your comments = to the=20 list until December 2nd. Comments like 'I read and I liked the draft, = seems OK=20 to me' are welcome as well.
 

Regards,

Dan

-----Original Message-----
From: = owner-mreview@ops.ietf.org=20 [mailto:owner-mreview@ops.ietf.org]On Behalf Of Romascanu, Dan=20 (Dan)
Sent: 04 November, 2004 1:44 PM
To:=20 hubmib@ietf.org
Cc: Mreview (E-mail);=20 stds-802-3@ieee.org
Subject: Working Group Last Call for the = EFM MIB=20 Documents

The Ethernet Interfaces and Hub = MIB Working=20 Group completed the work on the EFM MIB documents, and intents to submit = these=20 documents to the IESG for consideration as Proposed Standards. The WG = members=20 and all other interested participants are invited to review the = documents and=20 send their comments to hubmib@ietf.org, until December 2, 2004 the=20 latest.

The documents are available = at:

http://24.= 199.201.22/draft-ietf-hubmib-efm-mib-02.txt=20 (missed the IETF submission date by a few hours - will be re-submitted = after=20 Washington)

http://www.ietf.cnri.reston.va.us/internet-drafts= /draft-ietf-hubmib-efm-epon-mib-02.txt

http://www.ietf.cnri.reston.va.us/internet-drafts/d= raft-ietf-hubmib-efm-cu-mib-02.txt

Regards,

Dan

------_=_NextPart_001_01C4D2CC.30E29D46-- --===============0924232304== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0924232304==-- From hubmib-bounces@ietf.org Sun Nov 28 20:04:56 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03964 for ; Sun, 28 Nov 2004 20:04:56 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYZx2-0000yW-Pt; Sun, 28 Nov 2004 20:03:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYZwB-0000l0-7u for hubmib@megatron.ietf.org; Sun, 28 Nov 2004 20:02:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03778 for ; Sun, 28 Nov 2004 20:02:39 -0500 (EST) Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYa0x-0001SP-Sh for hubmib@ietf.org; Sun, 28 Nov 2004 20:07:40 -0500 Received: from shell4.bayarea.net (shell4.BAYAREA.NET [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id iAT126Kk022862 for ; Sun, 28 Nov 2004 17:02:06 -0800 Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id iAT125hr004558; Sun, 28 Nov 2004 17:02:05 -0800 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id iAT125DT004554; Sun, 28 Nov 2004 17:02:05 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Sun, 28 Nov 2004 17:02:05 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub Mib Subject: RE: [Hubmib] IANA Maintained TC for MAU types In-Reply-To: <9C1CAB2B65E62D49A10E49DFCD68EF3E296A6E@il-mail.actelis.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org On Tue, 26 Oct 2004, Edward Beili wrote: > I've submitted the first revision of MAU-MIB - > draft-ietf-hubmib-rfc3636bis-00 available at: > http://www.actelis.com/efm/ I have finally (on account of the recent holiday) had an opportunity to read this document. Sorry for the long delay. Other WG participants please note: this draft has not been posted to the I-D repository and much be accessed from the URL given above. Before I get into technical issues, there is an important "just why are we doing this" issue that I need to raise. Specifically, the draft as currently written requires a Standards Action (as defined in RFC 2434) in order to make modifications to the proposed IANA-maintained MIB module. That, I think, is the right thing to do, since we want the MAU types (and jack types) defined in that module to be in sync with what is standardized by the IEEE. On the other hand, it does mean that prior to adding any MAU types (or jack types) it will be necessary to get WG consensus and IESG approval to have a standards-track RFC published. It seems to me that very little time or effort will be saved compared to doing what we do now, namely getting WG consensus and IESG approval to issue a new revision of the MAU-MIB. If we cared about not recycling the MAU-MIB at Proposed Standard, there would be a difference, but I do not think that most WG participants care much about that. So before we move forward with the proposed IANA-maintained MIB module I suggest that we ask ourselves whether doing so will actually accomplish the intended purpose -- viz., to get the IETF MAU-related MIB updated to reflect revisions to IEEE 802.3 in a more timely and efficient manner than we have done heretofore. I have my doubts. Setting those doubts aside for the moment, I will now comment on some technical issues. > As far as I can tell no publically available MIBs import > dot3MauType OBJECT-IDENTITIES. However, if there is a problem, I > would suggest to import from IANA-MAU-TC-MIB all > OBJECT-IDENTITIES available in todays rfc3636 into the new > MAU-MIB. In looking over the draft I see that it is not just the dot3MauType* OBJECT-IDENTITY definitions that are to be migrated from the MAU-MIB to the IANA-maintained MIB module but also the JackType TEXTUAL-CONVENTION definition. I did an on-line search of my own for any MIB modules (IETF or otherwise) that might import these definitions, and I did not find any either. However, my search of non-IETF MIB modules can hardly be considered exhaustive, and I did find the following enterprise MIB modules that import things from the MAU-MIB: http://www.enterasys.com/support/relnotes/SSR-E9191-MIB.txt http://www.assure24.com/download/mibs/privatemibs/11/hpicf8023Rptr.mib http://www.assure24.com/download/mibs/privatemibs/5812/port.mib Fortunately, we do not need to take the risk of breaking anyone's MIB module, since there is a way to accomplish the objectives without losing backward compatibility. It will not do to just IMPORT the descriptors from the IANA-maintained MIB module, since IMPORTS does not work recursively. However, the following strategy will work: (a) in the MAU-MIB, change each of the dot3MauType* definitions from an OBJECT-IDENITY definition to a simple OBJECT IDENTIFIER value assignment; (b) leave the JackType textual convention in the MAU-MIB, changing its STATUS calue to 'deprecated', and call the new TC in the IANA-maintained module something like IanaJackType; then in the MAU-MIB, use IanaJackType in place of JackType in the appropriate object definitions. Note that this will allow any existing MIB module that might have IMPORTed the JackType TC or any of the dot3MauType* descriptors from the MAU-MIB to continue to compile without changes, but will also allow the migration to take place. The duplicate definitions of the dot3MauType* descriptors may draw warnings from some MIB compilers, but they are perfectly legal under the following clause of RFC 2578 (it is in the last paragraph of Section 3.6): A descriptor is allowed to be associated with both a registration and an assignment, providing both are associated with the same OBJECT IDENTIFIER value and semantics. As additional issues, I see that the maintenance instructions in the proposed IANA-maintained MIB module do not mention jack types, and it lacks the standard copyright notice mandated by RFC 3667. Finally, I would suggest that if we go forward with this that the name of the new IANA-maintained be IANA-MAU-MIB rather than IANA-MAU-TC-MIB since it does contain definitions other than just TCs. I have sent versions of the MAU-MIB and IANA-MAU-MIB that contain the changes described above to the draft author in an off-line e-mail. They generate a lot of noise from smilint but with the appropriate switches will compile cleanly with SMICng. One administrative issue I should mention is that the draft will need to have a separate IANA Considerations section in order to pass IESG muster. See Section 3.7.1 of the MIB review guidelines document for relevant guidelines. > Also, while changing description of rpMauType and ifMauType, I > noticed a text reference to unknownMauType OBJECT IDENTIFIER ::= > { 0 0 }, which is never defined anywhere in the MIB. I suggest > to import existing zerDotZero object from SNMPv2-SMI (defined as > {0 0}), and adding DEFVAL { zeroDotZero } to rpMauType and > ifMauType. That seems to me to be a reasonable thing to do (regardless of whether or not an IANA-maintained MIB module is created). However, since DEFVAL is only advisory, I would recommend retaining some version of the existing language in the DESCRIPTION clause (referring perhaps to zeroDotZero). Regards, Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Mon Nov 29 07:48:40 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14530 for ; Mon, 29 Nov 2004 07:48:39 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYkgL-0001Ce-Mh; Mon, 29 Nov 2004 07:31:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYkeF-0008Sg-N1 for hubmib@megatron.ietf.org; Mon, 29 Nov 2004 07:28:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00108 for ; Mon, 29 Nov 2004 04:30:52 -0500 (EST) Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYhwp-000439-VE for hubmib@ietf.org; Mon, 29 Nov 2004 04:35:56 -0500 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id iAT9UooB024085 for ; Mon, 29 Nov 2004 03:30:51 -0600 (CST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Mon, 29 Nov 2004 10:30:49 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C79FE3@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "'C. M. Heard'" , Hub Mib Subject: RE: [Hubmib] IANA Maintained TC for MAU types Date: Mon, 29 Nov 2004 10:30:47 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org Thanks for the review Mike. W.r.t. the first point (i.e. does it make sense to do an IANA maintained MIB module) see my comment inline. Bert > -----Original Message----- > From: hubmib-bounces@ietf.org > [mailto:hubmib-bounces@ietf.org]On Behalf > Of C. M. Heard > Sent: Monday, November 29, 2004 02:02 > To: Hub Mib > Subject: RE: [Hubmib] IANA Maintained TC for MAU types > > > On Tue, 26 Oct 2004, Edward Beili wrote: > > I've submitted the first revision of MAU-MIB - > > draft-ietf-hubmib-rfc3636bis-00 available at: > > http://www.actelis.com/efm/ > > I have finally (on account of the recent holiday) had an opportunity > to read this document. Sorry for the long delay. Other WG > participants please note: this draft has not been posted to the I-D > repository and much be accessed from the URL given above. > > Before I get into technical issues, there is an important "just why > are we doing this" issue that I need to raise. Specifically, the > draft as currently written requires a Standards Action (as defined > in RFC 2434) in order to make modifications to the proposed > IANA-maintained MIB module. That, I think, is the right thing to > do, since we want the MAU types (and jack types) defined in that > module to be in sync with what is standardized by the IEEE. On the > other hand, it does mean that prior to adding any MAU types (or jack > types) it will be necessary to get WG consensus and IESG approval to > have a standards-track RFC published. It seems to me that very > little time or effort will be saved compared to doing what we do > now, namely getting WG consensus and IESG approval to issue a new > revision of the MAU-MIB. If we cared about not recycling the > MAU-MIB at Proposed Standard, there would be a difference, but I do > not think that most WG participants care much about that. So before > we move forward with the proposed IANA-maintained MIB module I > suggest that we ask ourselves whether doing so will actually > accomplish the intended purpose -- viz., to get the IETF MAU-related > MIB updated to reflect revisions to IEEE 802.3 in a more timely and > efficient manner than we have done heretofore. I have my doubts. > So instead of requiring RFC2434 Standards Action, we could do a "Specification Required" and/or "Expert Review", For expert review we would make sure that we check with IEEE of course. Thinking aloud here. Bert > Setting those doubts aside for the moment, I will now comment on > some technical issues. > > > As far as I can tell no publically available MIBs import > > dot3MauType OBJECT-IDENTITIES. However, if there is a problem, I > > would suggest to import from IANA-MAU-TC-MIB all > > OBJECT-IDENTITIES available in todays rfc3636 into the new > > MAU-MIB. > > In looking over the draft I see that it is not just the dot3MauType* > OBJECT-IDENTITY definitions that are to be migrated from the MAU-MIB > to the IANA-maintained MIB module but also the JackType > TEXTUAL-CONVENTION definition. I did an on-line search of my own > for any MIB modules (IETF or otherwise) that might import these > definitions, and I did not find any either. However, my search of > non-IETF MIB modules can hardly be considered exhaustive, and I did > find the following enterprise MIB modules that import things from > the MAU-MIB: > > http://www.enterasys.com/support/relnotes/SSR-E9191-MIB.txt > http://www.assure24.com/download/mibs/privatemibs/11/hpicf8023Rptr.mib > http://www.assure24.com/download/mibs/privatemibs/5812/port.mib > > Fortunately, we do not need to take the risk of breaking anyone's > MIB module, since there is a way to accomplish the objectives > without losing backward compatibility. It will not do to just > IMPORT the descriptors from the IANA-maintained MIB module, since > IMPORTS does not work recursively. However, the following strategy > will work: > > (a) in the MAU-MIB, change each of the dot3MauType* definitions from > an OBJECT-IDENITY definition to a simple OBJECT IDENTIFIER value > assignment; > > (b) leave the JackType textual convention in the MAU-MIB, changing > its STATUS calue to 'deprecated', and call the new TC in the > IANA-maintained module something like IanaJackType; then in the > MAU-MIB, use IanaJackType in place of JackType in the appropriate > object definitions. > > Note that this will allow any existing MIB module that might have > IMPORTed the JackType TC or any of the dot3MauType* descriptors from > the MAU-MIB to continue to compile without changes, but will also > allow the migration to take place. The duplicate definitions of the > dot3MauType* descriptors may draw warnings from some MIB compilers, > but they are perfectly legal under the following clause of RFC 2578 > (it is in the last paragraph of Section 3.6): > > A descriptor is allowed to be associated with both a registration > and an assignment, providing both are associated with the same > OBJECT IDENTIFIER value and semantics. > > As additional issues, I see that the maintenance instructions in the > proposed IANA-maintained MIB module do not mention jack types, and > it lacks the standard copyright notice mandated by RFC 3667. > > Finally, I would suggest that if we go forward with this that the > name of the new IANA-maintained be IANA-MAU-MIB rather than > IANA-MAU-TC-MIB since it does contain definitions other than just > TCs. I have sent versions of the MAU-MIB and IANA-MAU-MIB that > contain the changes described above to the draft author in an > off-line e-mail. They generate a lot of noise from smilint but with > the appropriate switches will compile cleanly with SMICng. > > One administrative issue I should mention is that the draft will > need to have a separate IANA Considerations section in order to pass > IESG muster. See Section 3.7.1 of the MIB review guidelines > document for relevant guidelines. > > > Also, while changing description of rpMauType and ifMauType, I > > noticed a text reference to unknownMauType OBJECT IDENTIFIER ::= > > { 0 0 }, which is never defined anywhere in the MIB. I suggest > > to import existing zerDotZero object from SNMPv2-SMI (defined as > > {0 0}), and adding DEFVAL { zeroDotZero } to rpMauType and > > ifMauType. > > That seems to me to be a reasonable thing to do (regardless of > whether or not an IANA-maintained MIB module is created). However, > since DEFVAL is only advisory, I would recommend retaining some > version of the existing language in the DESCRIPTION clause > (referring perhaps to zeroDotZero). > > Regards, > > Mike > > > _______________________________________________ > 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-bounces@ietf.org Mon Nov 29 11:35:51 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07040 for ; Mon, 29 Nov 2004 11:35:51 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYoPe-0005iu-1e; Mon, 29 Nov 2004 11:30:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYoJy-0004eX-MV for hubmib@megatron.ietf.org; Mon, 29 Nov 2004 11:24:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06098 for ; Mon, 29 Nov 2004 11:24:12 -0500 (EST) Received: from smtpout1.bayarea.net ([209.128.95.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYoOu-0005S8-Jv for hubmib@ietf.org; Mon, 29 Nov 2004 11:29:21 -0500 Received: from shell4.bayarea.net (shell4.BAYAREA.NET [209.128.82.1]) by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id iATGNdKk006671 for ; Mon, 29 Nov 2004 08:23:39 -0800 Received: from shell4.bayarea.net (localhost [127.0.0.1]) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id iATGNcBB005684; Mon, 29 Nov 2004 08:23:38 -0800 Received: from localhost (heard@localhost) by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id iATGNcJo005680; Mon, 29 Nov 2004 08:23:38 -0800 X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs Date: Mon, 29 Nov 2004 08:23:38 -0800 (PST) From: "C. M. Heard" X-Sender: heard@shell4.bayarea.net To: Hub Mib Subject: RE: [Hubmib] IANA Maintained TC for MAU types In-Reply-To: <20041129075611.GA2792@james> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org On Mon, 29 Nov 2004, Wijnen, Bert (Bert) wrote: > [Mike Heard wrote:] > > [... T]he draft as currently written requires a Standards Action > > (as defined in RFC 2434) in order to make modifications to the > > proposed IANA-maintained MIB module. [ ... ] It seems to me > > that very little time or effort will be saved compared to doing > > what we do now, namely getting WG consensus and IESG approval to > > issue a new revision of the MAU-MIB. > > So instead of requiring RFC2434 Standards Action, we could do a > "Specification Required" and/or "Expert Review", For expert > review we would make sure that we check with IEEE of course. Perhaps then the optimal arrangement would indeed be Expert Review, provided that the IANA Considerations language in the MIB module explicitly state that new MAU types are to be added when & only when they are added to IEEE Std 802.3 In an offline e-mail on another matter, Juergen Schoenwaelder wrote: > Regarding the MIB that triggered your email: I think this MIB module > should be registered directly below mib-2 anyway. I think I agree with this. Note that it means just that as OID value of the form { mib-2 xxx } would be assigned to the MODULE-IDENTITY descriptor (which, BTW, should probably be ianaMauMib rather than ianaMauTC if my module name change suggestion is accepted); all of the OBJECT-IDENTITY definitions would remain as they are now. Mike _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Tue Nov 30 15:35:31 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01632 for ; Tue, 30 Nov 2004 15:35:31 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZEc4-0001CE-Nq; Tue, 30 Nov 2004 15:28:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZEIz-0006I1-73; Tue, 30 Nov 2004 15:08:57 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28471; Tue, 30 Nov 2004 15:08:54 -0500 (EST) Message-Id: <200411302008.PAA28471@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 30 Nov 2004 15:08:54 -0500 Cc: hubmib@ietf.org Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-efm-mib-02.txt X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org --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 : Ethernet in the First Mile (EFM) OAM MIB Author(s) : M. Squire Filename : draft-ietf-hubmib-efm-mib-02.txt Pages : 54 Date : 2004-11-30 This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet likeEthernet like interfaces conformant to the Ethernet OAM functionality defined in [802.3ah]. The Ethernet OAM functionality is complementary to SNMP management in that it is focused on a small set of link-specific functions for Ethernet interfaces. This document defines objects for controlling those link OAM functions, and on providing mechanisms to take status and input from Ethernet OAM and feed it into a larger TCP/IP network management system. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-mib-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-efm-mib-02.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-efm-mib-02.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: <2004-11-30110958.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-efm-mib-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-efm-mib-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-11-30110958.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --NextPart--