From mailman-bounces@ietf.org Fri Oct 1 10:17:06 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 KAA03177 for ; Fri, 1 Oct 2004 10:17:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDKDE-0007V7-TB for hubmib-archive@lists.ietf.org; Fri, 01 Oct 2004 06:00:28 -0400 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: Fri, 01 Oct 2004 05:23:16 -0400 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 Tue Oct 5 15:46:02 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 PAA01352 for ; Tue, 5 Oct 2004 15:46:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEv6J-0002v8-CA; Tue, 05 Oct 2004 15:35:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEv34-000169-Vw for hubmib@megatron.ietf.org; Tue, 05 Oct 2004 15:32:35 -0400 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 PAA00040 for ; Tue, 5 Oct 2004 15:32:30 -0400 (EDT) Received: from [62.90.13.193] (helo=il-mail.actelis.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEvC9-00078I-SI for hubmib@ietf.org; Tue, 05 Oct 2004 15:42:11 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hubmib] FW: Checking of boilerplate for Internet-Drafts (fwd) Date: Tue, 5 Oct 2004 21:31:29 +0200 Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E13C252@il-mail.actelis.net> Thread-Topic: Checking of boilerplate for Internet-Drafts (fwd) Thread-Index: AcSlXQwmdtaSLkVkQzetJykSyH63hwAEekBQAWiumGA= From: "Edward Beili" To: "Romascanu, Dan \(Dan\)" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433 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 >> (Note: Any recent version of xml2rfc should be compatible with these = rules, >> provided you use the "rfc ipr=3Dfull3667" directive) I use the latest version of xml2rfc (v1.26) with "rfc ipr=3Dfull3667" = directive, so from the quote above I assume I'm safe. Regards, -Edward > -----Original Message----- > From: hubmib-bounces@ietf.org=20 > [mailto:hubmib-bounces@ietf.org]On Behalf Of Romascanu, Dan (Dan) > Sent: Tuesday, 28 September, 2004 05:25 PM > To: hubmib@ietf.org > Subject: [Hubmib] FW: Checking of boilerplate for=20 > Internet-Drafts (fwd) >=20 >=20 > Editors, >=20 > Please make sure that all newly submitted drafts comply with=20 > draft-ietf-ipr-subm-rights-fix-00.txt.=20 >=20 > Thanks and Regards, >=20 > Dan >=20 >=20 >=20 > -----Original Message----- > From: wgchairs-bounces@ietf.org=20 > [mailto:wgchairs-bounces@ietf.org]On Behalf Of Harald Tveit Alvestrand > Sent: 28 September, 2004 2:23 PM > To: wgchairs@ietf.org > Subject: Checking of boilerplate for Internet-Drafts (fwd) >=20 >=20 > Just a reminder.... this change in procedure is in effect as of today. >=20 > Harald >=20 > ---------- Forwarded Message ---------- > Date: 20. september 2004 11:10 -0400 > From: Harald Alvestrand > To: IETF Announcement list > Subject: Checking of boilerplate for Internet-Drafts >=20 > Hello, >=20 > A bit before the August IETF, we announced that it was time=20 > to use the new > boilerplate from RFC 3667 in internet-drafts, and instructed the > secretariat to heck that boilerplate. > Due to some confusion, and the impending meeting, we asked=20 > them to stop > checking after a while. >=20 > But we have to move on.... it is now almost a year since RFC 3667 was > published, and the legal issues that the document was set to=20 > address ARE > important to the continued operation of the IETF. >=20 > I have therefore instructed the secretariat to check some items of the > boilerplate again, starting from September 28, 2004. >=20 > On the particular issue of the boilerplate that got changed=20 > between RFC > 3667 and the "fixed" draft-ietf-ipr-subm-rights-fix, I have=20 > asked them to > check that statement is present, and that it contains words=20 > that indicate > that it was intended to be a conformant boilerplate - we=20 > will make those > instructions tighter once draft-ietf-ipr-subm-rights-fix is=20 > published, but > not now. >=20 > Instructions for making conformant drafts can be found at the=20 > usual URL: > http://www.ietf.org/ietf/1id-guidelines.txt >=20 > Pay particular attention to the section "Notices required in > internet-drafts". >=20 > (Note: Any recent version of xml2rfc should be compatible=20 > with these rules, > provided you use the "rfc ipr=3Dfull3667" directive) >=20 > If the secretariat finds a violation of the rules, the=20 > secretariat is to > return the wording of the violated rule to the submitter; this should > eliminate ambiguity about WHAT is wrong with a submission. >=20 > With the hope of being able to go forward without worrying, >=20 > Harald >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce >=20 >=20 >=20 > ---------- End Forwarded Message ---------- >=20 >=20 >=20 >=20 >=20 >=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 Tue Oct 5 18:48:03 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 SAA20003 for ; Tue, 5 Oct 2004 18:48:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEy2j-0006rp-H7; Tue, 05 Oct 2004 18:44:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CExty-0005EJ-FC for hubmib@megatron.ietf.org; Tue, 05 Oct 2004 18:35:23 -0400 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 SAA19068 for ; Tue, 5 Oct 2004 18:35:18 -0400 (EDT) Received: from hoemail1.lucent.com ([192.11.226.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEy3G-0008GV-KB for hubmib@ietf.org; Tue, 05 Oct 2004 18:45:03 -0400 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 i95MZE3M009457 for ; Tue, 5 Oct 2004 17:35:15 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id ; Wed, 6 Oct 2004 00:35:13 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550566B93B@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Edward Beili , "Romascanu, Dan (Dan)" , hubmib@ietf.org Subject: RE: [Hubmib] FW: Checking of boilerplate for Internet-Drafts (fw d) Date: Wed, 6 Oct 2004 00:35:12 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 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 > > >> (Note: Any recent version of xml2rfc should be compatible > >> with these rules, > >> provided you use the "rfc ipr=full3667" directive) > > I use the latest version of xml2rfc (v1.26) with "rfc > ipr=full3667" directive, so from the quote above I assume I'm safe. > Yes. Bert _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Fri Oct 15 11:47:55 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 LAA15016 for ; Fri, 15 Oct 2004 11:47:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIUEo-0008A0-0k; Fri, 15 Oct 2004 11:43:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CIU64-0005iy-W3 for hubmib@megatron.ietf.org; Fri, 15 Oct 2004 11:34:25 -0400 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 LAA13428 for ; Fri, 15 Oct 2004 11:34:22 -0400 (EDT) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CIUHS-0002DF-4G for hubmib@ietf.org; Fri, 15 Oct 2004 11:46:11 -0400 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 i9FFWYZp003571 for ; Fri, 15 Oct 2004 11:32:34 -0400 (EDT) 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 i9FFWUZp003456 for ; Fri, 15 Oct 2004 11:32:31 -0400 (EDT) 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, 15 Oct 2004 17:34:15 +0200 Message-ID: Thread-Topic: Internet-Draft Submission Cutoff Dates for the 61st IETF Meeting inWashington, DC, USA Thread-Index: AcSyxJGlmyhpoc57TgadcEUggQuSwgAB44uw From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] FW: Internet-Draft Submission Cutoff Dates for the 61st IETF Meeting inWashington, DC, USA 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 A kind reminder to the editors! - The initial submission for the MAU MIB draft must be submitted until = the coming Monday, 10/18, at 9AM ET! - The other submissions are due one week later, Monday 10/25 Regards, Dan -----Original Message----- From: ietf-announce-bounces@ietf.org = [mailto:ietf-announce-bounces@ietf.org]On Behalf Of = ietf-secretariat@ietf.org Sent: 15 October, 2004 4:22 PM To: IETF-Announce@ietf.org Subject: Internet-Draft Submission Cutoff Dates for the 61st IETF = Meeting inWashington, DC, USA=20 There are two (2) Internet-Draft cutoff dates for the 61st IETF Meeting=20 in Washington, DC, USA: October 18: Cutoff Date for Initial (i.e., -00) Internet-Draft = Submissions=20 All initial Internet-Drafts (-00) must be submitted by Monday, October = 18 at=20 9:00 AM ET. As always, all initial submissions (-00) with a filename = beginning=20 with "draft-ietf" must be approved by the appropriate WG Chair before = they can=20 be processed or announced. WG Chair approval must be received by Monday, = October 11 at 9:00 AM ET. October 25: Cutoff Date for Revised (i.e., -01 and higher) = Internet-Draft=20 Submissions=20 All revised Internet-Drafts (-01 and higher) must be submitted by = Monday,=20 October 25 at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective = cutoff=20 dates will not be made available in the Internet-Drafts directory or = announced, and will have to be resubmitted. Please do not wait until the last = minute to=20 submit. The Secretariat will begin accepting Internet-Draft submissions = starting Monday, November 08 at 9:00 AM ET, but may not post or announce them = until=20 Monday, November 15. Thank you for your understanding and cooperation. If you have any = questions or=20 concerns, then please send a message to internet-drafts at ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates = for=20 the 61st IETF Meeting can be found at=20 http://www.ietf.org/meetings/cutoff_dates_61.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Fri Oct 22 13:10: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 NAA21234 for ; Fri, 22 Oct 2004 13:10:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2pb-0006kq-Hf; Fri, 22 Oct 2004 13:03:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CL2m6-0004px-Bp for hubmib@megatron.ietf.org; Fri, 22 Oct 2004 13:00:22 -0400 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 NAA20518 for ; Fri, 22 Oct 2004 13:00:18 -0400 (EDT) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CL2yv-0002Ea-5X for hubmib@ietf.org; Fri, 22 Oct 2004 13:13:37 -0400 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 i9MGwUgC028684 for ; Fri, 22 Oct 2004 12:58:30 -0400 (EDT) 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 i9MGvGgC027431 for ; Fri, 22 Oct 2004 12:57:30 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Date: Fri, 22 Oct 2004 18:56:46 +0200 Message-ID: Thread-Topic: Revised Internet-Draft Submission Cutoff Date for the 61st IETFMeeting in Washington, DC, USA Thread-Index: AcS4ROlNQqwk1jJtRVSEG8rzQJp0gQAEvqpA From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] FW: Revised Internet-Draft Submission Cutoff Date for the 61st IETFMeeting in Washington, DC, USA 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 Hubmib Editors - we are still missing two submissions for the revised = EFM MIB documents. The cutoff date is Monday! Regards, Dan -----Original Message----- From: ietf-announce-bounces@ietf.org = [mailto:ietf-announce-bounces@ietf.org]On Behalf Of = ietf-secretariat@ietf.org Sent: 22 October, 2004 4:18 PM To: IETF-Announce@ietf.org Subject: Revised Internet-Draft Submission Cutoff Date for the 61st = IETFMeeting in Washington, DC, USA=20 All revised Internet-Drafts (-01 and higher) must be submitted by = Monday,=20 October 25th at 9:00 AM ET. Revised Internet-Drafts received after the cutoff date will not be made = available in the Internet-Drafts directory or announced, and will have=20 to be resubmitted. Please do not wait until the last minute to submit. =20 The Secretariat will begin accepting Internet-Draft submissions starting = Monday, November 8th at 9:00 AM ET, but may not post or announce them=20 until Monday, November 15th. Thank you for your understanding and cooperation. If you have any = questions=20 or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates=20 for the 61st IETF Meeting can be found at=20 http://www.ietf.org/meetings/cutoff_dates_61.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Mon Oct 25 13:19:11 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 NAA15354 for ; Mon, 25 Oct 2004 13:19:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM8RH-0006Vf-BL; Mon, 25 Oct 2004 13:15:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM8KU-0005Bo-BS for hubmib@megatron.ietf.org; Mon, 25 Oct 2004 13:08:22 -0400 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 NAA14570 for ; Mon, 25 Oct 2004 13:08:19 -0400 (EDT) Received: from mailserv.hatterasnetworks.com ([63.89.58.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM8Xy-00033u-Kh for hubmib@ietf.org; Mon, 25 Oct 2004 13:22:19 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Oct 2004 13:07:50 -0400 Message-ID: <8052E2EA753D144EB906B7A7AA39971402A3B7E7@mailserv.hatteras.com> Thread-Topic: draft-ietf-hubmib-efm-mib-02.txt Thread-Index: AcS6tSi4g4/lwVseQsWl1HExHk8P3g== From: "Matt Squire" To: X-Spam-Score: 0.2 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: quoted-printable Subject: [Hubmib] 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 Content-Transfer-Encoding: quoted-printable The latest Internet Draft for the EFM OAM MIB can be found at:=20 http://24.199.201.22/draft-ietf-hubmib-efm-mib-02.txt This draft is an update of the -01 version discussed at the last IETF = meeting. The primary changes since then are: 1) Added a section on relationships to other EFM MIBs, including EPON = and point-to-point emulation. 2) Removed rowstatus from dot3OamTable and dot3OamPeerTable. This = required adding a new dot3OamPeerStatus to the dot3OamPeerTable entries = to indicate if the information about that peer is valid/known or not.=20 3) Updated to latest (and final) IEEE 802.3ah standard. 4) Generalized the event reporting table (what used to be = dot3OamEventStatusTable to dot3OamEventLogTable) so that all OAM events = are included as generic entries in the event log (rather than specific = objects for each event type). =20 5) Changed the use of dot3OamUnsigned64 to use either = CounterBasedGauge64 or to use two unsigned 32-bit integers as a = representation of a 64-bit unsigned integer. =20 6) Misc editorial changes. =20 - Matt _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-bounces@ietf.org Mon Oct 25 14:06:12 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 OAA19708 for ; Mon, 25 Oct 2004 14:06:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM9Cy-00047v-4X; Mon, 25 Oct 2004 14:04:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CM9C8-00041k-AL for hubmib@megatron.ietf.org; Mon, 25 Oct 2004 14:03:48 -0400 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 OAA19506 for ; Mon, 25 Oct 2004 14:03:45 -0400 (EDT) Received: from [62.90.13.193] (helo=il-mail.actelis.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CM9Pb-0004Jr-FP for hubmib@ietf.org; Mon, 25 Oct 2004 14:17:44 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 25 Oct 2004 20:02:54 +0200 Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E296A6B@il-mail.actelis.net> Thread-Topic: [mau-mib] draft-ietf-hubmib-rfc3636bis-00.txt Thread-Index: AcS6vNobTX96bSaVRgmM8XeY2y3VsQ== From: "Edward Beili" To: X-Spam-Score: 0.8 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Subject: [Hubmib] [mau-mib] draft-ietf-hubmib-rfc3636bis-00.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: , Content-Type: multipart/mixed; boundary="===============2044031452==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============2044031452== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4BABC.DA2448FD" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4BABC.DA2448FD Content-Type: text/plain; charset="WINDOWS-1255" Content-Transfer-Encoding: quoted-printable Hi, The first version of the revised MAU-MIB = (draft-ietf-hubmib-rfc3636bis-00) can be found at: http://www.actelis.com/efm/ I've missed the deadline for the initial I-D submission, so it won't be = published at the www.ietf.org till Nov 7th. You can also find there the latest EFM-CU-MIB draft = (draft-ietf-hubmib-efm-cu-mib-02). I've submitted it just before the = deadline today, so it'll probably take a few days for it to appear on = the IETF site. Your comments are greatly appreciated. Regards, -Edward ------_=_NextPart_001_01C4BABC.DA2448FD Content-Type: text/html; charset="WINDOWS-1255" Content-Transfer-Encoding: quoted-printable [mau-mib] draft-ietf-hubmib-rfc3636bis-00.txt

Hi,

The first version of the = revised MAU-MIB (draft-ietf-hubmib-rfc3636bis-00) can be found = at:

http://www.actelis.com/efm/

I've missed the deadline for = the initial I-D submission, so it won't be published at the www.ietf.org = till Nov 7th.

You can also find there the = latest EFM-CU-MIB draft (draft-ietf-hubmib-efm-cu-mib-02). I've = submitted it just before the deadline today, so it'll probably take a = few days for it to appear on the IETF site.

Your comments are greatly = appreciated.

Regards,

-Edward

------_=_NextPart_001_01C4BABC.DA2448FD-- --===============2044031452== 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 --===============2044031452==-- From hubmib-bounces@ietf.org Mon Oct 25 19:55:33 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 TAA20335 for ; Mon, 25 Oct 2004 19:55:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMEPI-00011x-7u; Mon, 25 Oct 2004 19:37:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMCP8-00070J-DM for hubmib@megatron.ietf.org; Mon, 25 Oct 2004 17:29:26 -0400 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 RAA14165 for ; Mon, 25 Oct 2004 17:29:23 -0400 (EDT) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMCcd-0002Lk-PR for hubmib@ietf.org; Mon, 25 Oct 2004 17:43:25 -0400 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 i9PLRWO7022535 for ; Mon, 25 Oct 2004 17:27:33 -0400 (EDT) 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 i9PLQAO7020810 for ; Mon, 25 Oct 2004 17:26:25 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Subject: RE: [Hubmib] draft-ietf-hubmib-efm-mib-02.txt Date: Mon, 25 Oct 2004 23:27:46 +0200 Message-ID: Thread-Topic: draft-ietf-hubmib-efm-mib-02.txt Thread-Index: AcS6tSi4g4/lwVseQsWl1HExHk8P3gAI/eKw From: "Romascanu, Dan \(Dan\)" To: "Matt Squire" , X-Spam-Score: 0.2 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: quoted-printable Cc: bwijnen@lucent.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: , Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org Content-Transfer-Encoding: quoted-printable Unfortunately this Internet-Draft missed the submission time by a few = tens of minutes, and will show up in the Internet-Drafts repository only = after the Washington DC meeting.=20 Is there any objection from the WG to have the version of the draft = pointed to by Matt used for the Working Group Last Call?=20 Thanks and Regards, Dan > -----Original Message----- > From: hubmib-bounces@ietf.org=20 > [mailto:hubmib-bounces@ietf.org]On Behalf Of Matt Squire > Sent: 25 October, 2004 7:08 PM > To: hubmib@ietf.org > Subject: [Hubmib] draft-ietf-hubmib-efm-mib-02.txt >=20 >=20 >=20 > The latest Internet Draft for the EFM OAM MIB can be found at:=20 >=20 > http://24.199.201.22/draft-ietf-hubmib-efm-mib-02.txt >=20 > This draft is an update of the -01 version discussed at the=20 > last IETF meeting. The primary changes since then are: >=20 > 1) Added a section on relationships to other EFM MIBs,=20 > including EPON and point-to-point emulation. >=20 > 2) Removed rowstatus from dot3OamTable and dot3OamPeerTable. =20 > This required adding a new dot3OamPeerStatus to the=20 > dot3OamPeerTable entries to indicate if the information about=20 > that peer is valid/known or not.=20 >=20 > 3) Updated to latest (and final) IEEE 802.3ah standard. >=20 > 4) Generalized the event reporting table (what used to be=20 > dot3OamEventStatusTable to dot3OamEventLogTable) so that all=20 > OAM events are included as generic entries in the event log=20 > (rather than specific objects for each event type). =20 >=20 > 5) Changed the use of dot3OamUnsigned64 to use either=20 > CounterBasedGauge64 or to use two unsigned 32-bit integers as=20 > a representation of a 64-bit unsigned integer. =20 >=20 > 6) Misc editorial changes. =20 >=20 > - Matt >=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 Tue Oct 26 10:08:47 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 KAA07549 for ; Tue, 26 Oct 2004 10:08:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMRwJ-0005wi-Hr; Tue, 26 Oct 2004 10:04:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CMRvJ-00050e-35 for hubmib@megatron.ietf.org; Tue, 26 Oct 2004 10:03:43 -0400 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 KAA07092 for ; Tue, 26 Oct 2004 10:03:38 -0400 (EDT) Received: from [62.90.13.193] (helo=il-mail.actelis.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMS8t-0003i5-BH for hubmib@ietf.org; Tue, 26 Oct 2004 10:17:48 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.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] IANA Maintained TC for MAU types Date: Tue, 26 Oct 2004 16:02:28 +0200 Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E296A6E@il-mail.actelis.net> Thread-Topic: [Hubmib] IANA Maintained TC for MAU types Thread-Index: AcR6Qx5z03yZP0HBQpiXeJSF60JWNBBHuoUw From: "Edward Beili" To: "C. M. Heard" X-Spam-Score: 0.0 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Content-Transfer-Encoding: quoted-printable Cc: "Romascanu, Dan \(Dan\)" , hubmib@ietf.org 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 Mike, I've submitted the first revision of MAU-MIB - = draft-ietf-hubmib-rfc3636bis-00 available at: http://www.actelis.com/efm/ 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. Also, while changing description of rpMauType and ifMauType, I noticed a = text reference to=20 unknownMauType OBJECT IDENTIFIER ::=3D { 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. I would appreciate your comments. Regards, -Edward -----Original Message----- From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On Behalf Of C. M. Heard Sent: Wednesday, August 04, 2004 6:26 PM To: Hub Mib Subject: [Hubmib] IANA Maintained TC for MAU types On Tue, 3 Aug 2004, Romascanu, Dan (Dan) wrote: > The Ethernet interfaces and hub MIB WG (hubmib) met for one > session at the 60th IETF. The WG discussed the latest changes, > comments and open issues for the three chartered WG > Internet-Drafts related to the Ethernet First Mile (EFM) > technology. The participants in the meeting recommended that > the MAU MIB be re-written to refer to a IANA-maintained Textual > Convention, which would ease the support for new MAUs in the > future, without requiring opening of the MAU MIB documents. I'd like to make a few comments about this idea. The first point is that what needs to be extended in the MAU-MIB is not just a single BITS type definition but rather a BITS type definition that is lined up with a matched set of OBJECT-IDENTITY definitions. The affected definitions in the MAU-MIB are these OBJECT-IDENTITY definitions: dot3MauType OBJECT IDENTIFIER ::=3D { snmpDot3MauMgt 4 } dot3MauTypeAUI OBJECT-IDENTITY STATUS current DESCRIPTION "no internal MAU, view from AUI" REFERENCE "[IEEE 802.3 Std.], Section 7" ::=3D { dot3MauType 1 } [ ... ] dot3MauType10GigBaseSW OBJECT-IDENTITY STATUS current DESCRIPTION "W fiber over 850 nm optics" REFERENCE "[IEEE 802.3 Std.], Section 52" ::=3D { dot3MauType 40 } and the BITS type in the following OBJECT-TYPE definition: ifMauTypeListBits OBJECT-TYPE SYNTAX BITS { bOther(0), -- other or unknown bAUI(1), -- AUI [ ... ] b10GbaseSW(40) -- 10GBASE-SW } MAX-ACCESS read-only STATUS current DESCRIPTION "A value that uniquely identifies the set of possible IEEE 802.3 types that the MAU could be. If auto-negotiation is present on this MAU, this object will map to ifMauAutoNegCapabilityBits. Note that this MAU may be capable of operating as a MAU type that is beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for capabilities that are listed above." ::=3D { ifMauEntry 13 } The IANA-maintained MIB module would need to contain the dot3MauType* OBJECT-IDENTITY definitions along with a TC (which might be called IANAifMauTypeListBits) that whose SYNTAX clause is what is presently in ifMauTypeListBits. That, of course, is because these items have to remain in sync and so have to be maintained in parallel. The IANA-maintained module would, of course, import the base OID descriptor dot3MauType from the MAU-MIB. One minor backward-compatibility issue is that migrating the OBJECT-IDENTITY definitions in this way could cause problems if any existing MIB modules have imported those descriptors from MAU-MIB. This could be addressed by keeping the existing list of dot3MauType* descriptors in the MAU-MIB as object identifier value assignments; while RFC 2578 does not permit two "registrations" of the same OID value, it does allow a descriptor to be associated with both a registration and an object identifier value assignment, providing both are associated with the same OBJECT IDENTIFIER value and semantics (cf. Section 3.6). Another issue that needs to be addressed is what rules apply to new MAU types. My thinking is that this should be allowed ONLY by a Standards Action (as defined in RFC 2434) -- or at least IETF Consensus -- so that any prospective assignments are documented in an RFC. Any document that proposes such an assignment should also be required to note any special properties of the MAU types that it defines -- for example, side effects on the ifStackTable such as are noted in RFC 3636 Section 3.4.1 for 10GBASE-W MAUs. Also to be noted is that the MAU-MIB itself will need some minor modifications beyond those discussed above, such as the DESCRIPTION clauses for rpMauType and ifMauType. A good editor is needed to ferret all those things out. One final point: in his reply to Dan Romascanu's comments on draft-ietf-hubmib-efm-epon-mib-01.txt, Lior Khermosh said: > Sorry for being not clear but my intention is that MAU type > objects in the MAU section should be added to the MAUMIBs as > with the efm-cu document. If it is not done there then the MAU > section in the efm-epon mib should contain them (as now). My position would be that we MUST modify the MAU-MIB -- either directly or by putting the MAU types into an IANA-maintained module -- to contain the new MAU type definitions. It invites catastrophe (i.e., conflicting OID/bit position assignments) if the values assigned to MAU types are scattered over several documents. I do agree that it is OK to split off MAU-specific stats counters and so on and put those in a separate module; in fact there is no practical alternative to doing so if we don't want to change the MAU-MIB every time we add an MAU type that requires such things. 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-bounces@ietf.org Thu Oct 28 11:22:42 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 LAA25918 for ; Thu, 28 Oct 2004 11:22:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNBZD-0002Ja-PK; Thu, 28 Oct 2004 10:47:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNBSV-0000QI-1s; Thu, 28 Oct 2004 10:41: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 KAA18615; Thu, 28 Oct 2004 10:40:57 -0400 (EDT) Message-Id: <200410281440.KAA18615@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 28 Oct 2004 10:40:57 -0400 Cc: hubmib@ietf.org Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-efm-cu-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 Copper (EFMCu) Interfaces MIB Author(s) : E. Beili Filename : draft-ietf-hubmib-efm-cu-mib-02.txt Pages : 69 Date : 2004-10-27 This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. This document proposes an extension to the Ethernet-like Interfaces MIB and MAU MIB with a set of objects for managing an Ethernet in the First Mile Copper (EFMCu) interfaces 10PASS-TS and 2BASE-TL, defined in IEEE Std 802.3ah-2004. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-cu-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-cu-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-cu-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-10-28105604.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-efm-cu-mib-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-efm-cu-mib-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-10-28105604.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--