From mailman-admin@ietf.org Sat May 1 11:40:17 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26919 for ; Sat, 1 May 2004 11:40:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BJuWL-0003pt-Fj for hubmib-archive@lists.ietf.org; Sat, 01 May 2004 09:27:09 -0400 Date: Sat, 01 May 2004 09:27:09 -0400 Message-ID: <20040501132709.27207.7611.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: hubmib-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, hubmib-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for hubmib-archive@lists.ietf.org: List Password // URL ---- -------- hubmib@ietf.org XUKx https://www1.ietf.org/mailman/options/hubmib/hubmib-archive%40lists.ietf.org From hubmib-admin@ietf.org Thu May 6 06:40:46 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04670 for ; Thu, 6 May 2004 06:40:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLgAb-0007gd-Lf; Thu, 06 May 2004 06:32:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLg4T-0005MV-N8 for hubmib@optimus.ietf.org; Thu, 06 May 2004 06:25:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03812 for ; Thu, 6 May 2004 06:25:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLg4P-0002zp-Ro for hubmib@ietf.org; Thu, 06 May 2004 06:25:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLg3X-0002aM-00 for hubmib@ietf.org; Thu, 06 May 2004 06:24:44 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1BLg2g-00029p-00 for hubmib@ietf.org; Thu, 06 May 2004 06:23:50 -0400 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 i46AIlrw018550 for ; Thu, 6 May 2004 05:18:47 -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 i46AIjrw018508 for ; Thu, 6 May 2004 05:18:46 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43354.38225A71" Date: Thu, 6 May 2004 13:23:48 +0300 Message-ID: Thread-Topic: Status, last call, meeting in San Diego Thread-Index: AcQzVDf+ntDnRxlkSbyN2H4r/g7olQ== From: "Romascanu, Dan (Dan)" To: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Status, last call, meeting in San Diego Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C43354.38225A71 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I am very disappointed and concerned with the fact that we missed our = schedule for going to Last Call for the EFM MIBs documents in April. = Actually, none of the revised Internet-Drafts was published, and with = one exception (the editor of the EPON MIB) no notice was sent concerning = the reasons of the delay. With the IEEE 802.3ah technical issues now = solved (to the best of my knowledge), I see no technical reason for this = delay. I would kindly request the editors of the three documents to let = the WG know what is their schedule for submitting the documents, so that = we can plan for WG Last Call, and ask for changes in the WG Charter = schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the = next IETF meeting planned for August 1-6. I will ask for a two hours = meeting slot, same as we had in Seoul. I would advise the editors and = other interested participants to plan for this meeting, please let me = know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C43354.38225A71 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Status, last call, meeting in San Diego

I am very disappointed and = concerned with the fact that we missed our schedule for going to Last = Call for the EFM MIBs documents in April. Actually, none of the revised = Internet-Drafts was published, and with one exception (the editor of the = EPON MIB) no notice was sent concerning the reasons of the delay. With = the IEEE 802.3ah technical issues now solved (to the best of my = knowledge), I see no technical reason for this delay. I would kindly = request the editors of the three documents to let the WG know what is = their schedule for submitting the documents, so that we can plan for WG = Last Call, and ask for changes in the WG Charter schedules = accordingly.

Taking into account the = delay, we may need to meet in San Diego, at the next IETF meeting = planned for August 1-6. I will ask for a two hours meeting slot, same as = we had in Seoul. I would advise the editors and other interested = participants to plan for this meeting, please let me know if there are = any issues.

Thanks = and Regards,

Dan

------_=_NextPart_001_01C43354.38225A71-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu May 6 06:42:46 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04839 for ; Thu, 6 May 2004 06:42:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLgIe-0001iS-Q6 for hubmib-archive@odin.ietf.org; Thu, 06 May 2004 06:40:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46AeKjG006596 for hubmib-archive@odin.ietf.org; Thu, 6 May 2004 06:40:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLgAb-0007gd-Lf; Thu, 06 May 2004 06:32:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLg4T-0005MV-N8 for hubmib@optimus.ietf.org; Thu, 06 May 2004 06:25:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03812 for ; Thu, 6 May 2004 06:25:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLg4P-0002zp-Ro for hubmib@ietf.org; Thu, 06 May 2004 06:25:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLg3X-0002aM-00 for hubmib@ietf.org; Thu, 06 May 2004 06:24:44 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1BLg2g-00029p-00 for hubmib@ietf.org; Thu, 06 May 2004 06:23:50 -0400 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 i46AIlrw018550 for ; Thu, 6 May 2004 05:18:47 -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 i46AIjrw018508 for ; Thu, 6 May 2004 05:18:46 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43354.38225A71" Date: Thu, 6 May 2004 13:23:48 +0300 Message-ID: Thread-Topic: Status, last call, meeting in San Diego Thread-Index: AcQzVDf+ntDnRxlkSbyN2H4r/g7olQ== From: "Romascanu, Dan (Dan)" To: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_20_30,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] Status, last call, meeting in San Diego Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C43354.38225A71 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I am very disappointed and concerned with the fact that we missed our = schedule for going to Last Call for the EFM MIBs documents in April. = Actually, none of the revised Internet-Drafts was published, and with = one exception (the editor of the EPON MIB) no notice was sent concerning = the reasons of the delay. With the IEEE 802.3ah technical issues now = solved (to the best of my knowledge), I see no technical reason for this = delay. I would kindly request the editors of the three documents to let = the WG know what is their schedule for submitting the documents, so that = we can plan for WG Last Call, and ask for changes in the WG Charter = schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the = next IETF meeting planned for August 1-6. I will ask for a two hours = meeting slot, same as we had in Seoul. I would advise the editors and = other interested participants to plan for this meeting, please let me = know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C43354.38225A71 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Status, last call, meeting in San Diego

I am very disappointed and = concerned with the fact that we missed our schedule for going to Last = Call for the EFM MIBs documents in April. Actually, none of the revised = Internet-Drafts was published, and with one exception (the editor of the = EPON MIB) no notice was sent concerning the reasons of the delay. With = the IEEE 802.3ah technical issues now solved (to the best of my = knowledge), I see no technical reason for this delay. I would kindly = request the editors of the three documents to let the WG know what is = their schedule for submitting the documents, so that we can plan for WG = Last Call, and ask for changes in the WG Charter schedules = accordingly.

Taking into account the = delay, we may need to meet in San Diego, at the next IETF meeting = planned for August 1-6. I will ask for a two hours meeting slot, same as = we had in Seoul. I would advise the editors and other interested = participants to plan for this meeting, please let me know if there are = any issues.

Thanks = and Regards,

Dan

------_=_NextPart_001_01C43354.38225A71-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 6 14:25:36 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09173 for ; Thu, 6 May 2004 14:25:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnJv-0004IY-M6; Thu, 06 May 2004 14:10:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnCF-0000Fg-N3 for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:02:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08029 for ; Thu, 6 May 2004 14:02:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnCD-0006nM-9U for hubmib@ietf.org; Thu, 06 May 2004 14:02:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnBQ-0006NC-00 for hubmib@ietf.org; Thu, 06 May 2004 14:01:21 -0400 Received: from [62.90.13.193] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 1BLnAY-0005rr-00 for hubmib@ietf.org; Thu, 06 May 2004 14:00:26 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Thu, 6 May 2004 21:00:46 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF2742327@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" , hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:00:45 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43394.0DEA1EC0" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_20_30,HTML_FONTCOLOR_BLUE, HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43394.0DEA1EC0 Content-Type: text/plain; charset="windows-1255" Hi Dan, Sorry for the delay with the new version - I was traveling the whole last month (on business) + waiting for draft D3.3. I would like to shoot for the end of May with publishing the new version based on Draft D3.4 which would be ready to be submitted to RevCom I believe on May 14th. I got some comments from the people on ADSLMIB group, which called for drastic changes in the MIB (separation of AvailableStackTable into a new MIB and referencing of the newest VDSL and SHDSL MIBs instead of defining everything in the EFM-CU-MIB). I'm reluctant to go in this direction and would like to hear opinions of the people on this list. Regards, -E. -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C43394.0DEA1EC0 Content-Type: text/html; charset="windows-1255" Status, last call, meeting in San Diego
Hi Dan,
Sorry for the delay with the new version - I was traveling the whole last month (on business) + waiting for draft D3.3.
I would like to shoot for the end of May with publishing the new version based on Draft D3.4 which would be ready to be submitted to RevCom I believe on May 14th.
 
I got some comments from the people on ADSLMIB group, which called for drastic changes in the MIB
(separation of AvailableStackTable into a new MIB and referencing of the newest VDSL and SHDSL MIBs instead of defining everything in the EFM-CU-MIB).
I'm reluctant to go in this direction and would like to hear opinions of the people on this list.
 
Regards,
-E. 
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 01:24 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, last call, meeting in San Diego

I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly.

Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues.

Thanks and Regards,

Dan

------_=_NextPart_001_01C43394.0DEA1EC0-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 6 14:29:48 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09385 for ; Thu, 6 May 2004 14:29:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnVR-0000aO-AX; Thu, 06 May 2004 14:22:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnGv-0002k1-BM for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:07:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08311 for ; Thu, 6 May 2004 14:06:58 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnGt-00018L-0V for hubmib@ietf.org; Thu, 06 May 2004 14:06:59 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnG2-0000i6-00 for hubmib@ietf.org; Thu, 06 May 2004 14:06:07 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1BLnFB-0000IE-00 for hubmib@ietf.org; Thu, 06 May 2004 14:05:13 -0400 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 i46I05rw001504 for ; Thu, 6 May 2004 13:00:05 -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 i46I03rw001444 for ; Thu, 6 May 2004 13:00:04 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43394.A92B063F" Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:05:05 +0300 Message-ID: Thread-Topic: [Hubmib] Status, last call, meeting in San Diego Thread-Index: AcQzk/Ljd/5zRPOFRuih20tk5gnxYgAAD8OQ From: "Romascanu, Dan (Dan)" To: "Edward Beili" , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C43394.A92B063F Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Edward, =20 Thank you for your message. =20 I believe that it would be useful if you can address more in details the = issues raised by the ADSL MIB WG participants, and you would argue why = you consider the current proposal good enough, and you are 'reluctant' = to go in the direction of the changes that they are proposing. =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 06 May, 2004 9:01 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Hi Dan, Sorry for the delay with the new version - I was traveling the whole = last month (on business) + waiting for draft D3.3. I would like to shoot for the end of May with publishing the new version = based on Draft D3.4 which would be ready to be submitted to RevCom I = believe on May 14th. =20 I got some comments from the people on ADSLMIB group, which called for = drastic changes in the MIB (separation of AvailableStackTable into a new MIB and referencing of the = newest VDSL and SHDSL MIBs instead of defining everything in the = EFM-CU-MIB). I'm reluctant to go in this direction and would like to hear opinions of = the people on this list. =20 Regards, -E.=20 -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our = schedule for going to Last Call for the EFM MIBs documents in April. = Actually, none of the revised Internet-Drafts was published, and with = one exception (the editor of the EPON MIB) no notice was sent concerning = the reasons of the delay. With the IEEE 802.3ah technical issues now = solved (to the best of my knowledge), I see no technical reason for this = delay. I would kindly request the editors of the three documents to let = the WG know what is their schedule for submitting the documents, so that = we can plan for WG Last Call, and ask for changes in the WG Charter = schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the = next IETF meeting planned for August 1-6. I will ask for a two hours = meeting slot, same as we had in Seoul. I would advise the editors and = other interested participants to plan for this meeting, please let me = know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C43394.A92B063F Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Status, last call, meeting in San Diego
Edward,
 
Thank you for your message.
 
I believe that it would be useful if you can address more in = details the=20 issues raised by the ADSL MIB WG participants, and you would argue why = you=20 consider the current proposal good enough, and you are 'reluctant' to go = in the=20 direction of the changes that they are=20 proposing.
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 06 May, 2004 9:01=20 PM
To: Romascanu, Dan (Dan); = hubmib@ietf.org
Subject: RE:=20 [Hubmib] Status, last call, meeting in San Diego

Hi=20 Dan,
Sorry for the delay with the new version - I was traveling = the whole=20 last month (on business) + waiting for draft D3.3.
I=20 would like to shoot for the end of May with publishing the new version = based=20 on Draft D3.4 which would be ready to be submitted to RevCom I believe = on May=20 14th.
 
I=20 got some comments from the people on ADSLMIB group, which called for = drastic=20 changes in the MIB
(separation of AvailableStackTable into a new MIB = and referencing=20 of the newest VDSL and SHDSL MIBs instead of defining everything in = the=20 EFM-CU-MIB).
I'm reluctant to go in this direction and would like to = hear=20 opinions of the people on this list.
 
Regards,
-E. 
-----Original Message-----
From: Romascanu, Dan = (Dan)=20 [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 = 01:24=20 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, = last=20 call, meeting in San Diego

I am very disappointed and = concerned with=20 the fact that we missed our schedule for going to Last Call for the = EFM MIBs=20 documents in April. Actually, none of the revised Internet-Drafts = was=20 published, and with one exception (the editor of the EPON MIB) no = notice was=20 sent concerning the reasons of the delay. With the IEEE 802.3ah = technical=20 issues now solved (to the best of my knowledge), I see no technical = reason=20 for this delay. I would kindly request the editors of the three = documents to=20 let the WG know what is their schedule for submitting the documents, = so that=20 we can plan for WG Last Call, and ask for changes in the WG Charter=20 schedules accordingly.

Taking into account the = delay, we may=20 need to meet in San Diego, at the next IETF meeting planned for = August 1-6.=20 I will ask for a two hours meeting slot, same as we had in Seoul. I = would=20 advise the editors and other interested participants to plan for = this=20 meeting, please let me know if there are any issues.

Thanks = and=20 Regards,

Dan

------_=_NextPart_001_01C43394.A92B063F-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu May 6 14:32:41 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09572 for ; Thu, 6 May 2004 14:32:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnYS-0001vE-K3 for hubmib-archive@odin.ietf.org; Thu, 06 May 2004 14:25:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46IP8Ct007387 for hubmib-archive@odin.ietf.org; Thu, 6 May 2004 14:25:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnJv-0004IY-M6; Thu, 06 May 2004 14:10:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnCF-0000Fg-N3 for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:02:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08029 for ; Thu, 6 May 2004 14:02:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnCD-0006nM-9U for hubmib@ietf.org; Thu, 06 May 2004 14:02:09 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnBQ-0006NC-00 for hubmib@ietf.org; Thu, 06 May 2004 14:01:21 -0400 Received: from [62.90.13.193] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 1BLnAY-0005rr-00 for hubmib@ietf.org; Thu, 06 May 2004 14:00:26 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Thu, 6 May 2004 21:00:46 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF2742327@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" , hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:00:45 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43394.0DEA1EC0" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_20_30,HTML_FONTCOLOR_BLUE, HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C43394.0DEA1EC0 Content-Type: text/plain; charset="windows-1255" Hi Dan, Sorry for the delay with the new version - I was traveling the whole last month (on business) + waiting for draft D3.3. I would like to shoot for the end of May with publishing the new version based on Draft D3.4 which would be ready to be submitted to RevCom I believe on May 14th. I got some comments from the people on ADSLMIB group, which called for drastic changes in the MIB (separation of AvailableStackTable into a new MIB and referencing of the newest VDSL and SHDSL MIBs instead of defining everything in the EFM-CU-MIB). I'm reluctant to go in this direction and would like to hear opinions of the people on this list. Regards, -E. -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C43394.0DEA1EC0 Content-Type: text/html; charset="windows-1255" Status, last call, meeting in San Diego
Hi Dan,
Sorry for the delay with the new version - I was traveling the whole last month (on business) + waiting for draft D3.3.
I would like to shoot for the end of May with publishing the new version based on Draft D3.4 which would be ready to be submitted to RevCom I believe on May 14th.
 
I got some comments from the people on ADSLMIB group, which called for drastic changes in the MIB
(separation of AvailableStackTable into a new MIB and referencing of the newest VDSL and SHDSL MIBs instead of defining everything in the EFM-CU-MIB).
I'm reluctant to go in this direction and would like to hear opinions of the people on this list.
 
Regards,
-E. 
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 01:24 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, last call, meeting in San Diego

I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly.

Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues.

Thanks and Regards,

Dan

------_=_NextPart_001_01C43394.0DEA1EC0-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu May 6 14:37:28 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10053 for ; Thu, 6 May 2004 14:37:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLncX-0003Nv-5y for hubmib-archive@odin.ietf.org; Thu, 06 May 2004 14:29:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46ITLSW013003 for hubmib-archive@odin.ietf.org; Thu, 6 May 2004 14:29:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnVR-0000aO-AX; Thu, 06 May 2004 14:22:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnGv-0002k1-BM for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:07:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08311 for ; Thu, 6 May 2004 14:06:58 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnGt-00018L-0V for hubmib@ietf.org; Thu, 06 May 2004 14:06:59 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnG2-0000i6-00 for hubmib@ietf.org; Thu, 06 May 2004 14:06:07 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1BLnFB-0000IE-00 for hubmib@ietf.org; Thu, 06 May 2004 14:05:13 -0400 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 i46I05rw001504 for ; Thu, 6 May 2004 13:00:05 -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 i46I03rw001444 for ; Thu, 6 May 2004 13:00:04 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C43394.A92B063F" Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:05:05 +0300 Message-ID: Thread-Topic: [Hubmib] Status, last call, meeting in San Diego Thread-Index: AcQzk/Ljd/5zRPOFRuih20tk5gnxYgAAD8OQ From: "Romascanu, Dan (Dan)" To: "Edward Beili" , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C43394.A92B063F Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Edward, =20 Thank you for your message. =20 I believe that it would be useful if you can address more in details the = issues raised by the ADSL MIB WG participants, and you would argue why = you consider the current proposal good enough, and you are 'reluctant' = to go in the direction of the changes that they are proposing. =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 06 May, 2004 9:01 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Hi Dan, Sorry for the delay with the new version - I was traveling the whole = last month (on business) + waiting for draft D3.3. I would like to shoot for the end of May with publishing the new version = based on Draft D3.4 which would be ready to be submitted to RevCom I = believe on May 14th. =20 I got some comments from the people on ADSLMIB group, which called for = drastic changes in the MIB (separation of AvailableStackTable into a new MIB and referencing of the = newest VDSL and SHDSL MIBs instead of defining everything in the = EFM-CU-MIB). I'm reluctant to go in this direction and would like to hear opinions of = the people on this list. =20 Regards, -E.=20 -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our = schedule for going to Last Call for the EFM MIBs documents in April. = Actually, none of the revised Internet-Drafts was published, and with = one exception (the editor of the EPON MIB) no notice was sent concerning = the reasons of the delay. With the IEEE 802.3ah technical issues now = solved (to the best of my knowledge), I see no technical reason for this = delay. I would kindly request the editors of the three documents to let = the WG know what is their schedule for submitting the documents, so that = we can plan for WG Last Call, and ask for changes in the WG Charter = schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the = next IETF meeting planned for August 1-6. I will ask for a two hours = meeting slot, same as we had in Seoul. I would advise the editors and = other interested participants to plan for this meeting, please let me = know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C43394.A92B063F Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Status, last call, meeting in San Diego
Edward,
 
Thank you for your message.
 
I believe that it would be useful if you can address more in = details the=20 issues raised by the ADSL MIB WG participants, and you would argue why = you=20 consider the current proposal good enough, and you are 'reluctant' to go = in the=20 direction of the changes that they are=20 proposing.
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 06 May, 2004 9:01=20 PM
To: Romascanu, Dan (Dan); = hubmib@ietf.org
Subject: RE:=20 [Hubmib] Status, last call, meeting in San Diego

Hi=20 Dan,
Sorry for the delay with the new version - I was traveling = the whole=20 last month (on business) + waiting for draft D3.3.
I=20 would like to shoot for the end of May with publishing the new version = based=20 on Draft D3.4 which would be ready to be submitted to RevCom I believe = on May=20 14th.
 
I=20 got some comments from the people on ADSLMIB group, which called for = drastic=20 changes in the MIB
(separation of AvailableStackTable into a new MIB = and referencing=20 of the newest VDSL and SHDSL MIBs instead of defining everything in = the=20 EFM-CU-MIB).
I'm reluctant to go in this direction and would like to = hear=20 opinions of the people on this list.
 
Regards,
-E. 
-----Original Message-----
From: Romascanu, Dan = (Dan)=20 [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 = 01:24=20 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, = last=20 call, meeting in San Diego

I am very disappointed and = concerned with=20 the fact that we missed our schedule for going to Last Call for the = EFM MIBs=20 documents in April. Actually, none of the revised Internet-Drafts = was=20 published, and with one exception (the editor of the EPON MIB) no = notice was=20 sent concerning the reasons of the delay. With the IEEE 802.3ah = technical=20 issues now solved (to the best of my knowledge), I see no technical = reason=20 for this delay. I would kindly request the editors of the three = documents to=20 let the WG know what is their schedule for submitting the documents, = so that=20 we can plan for WG Last Call, and ask for changes in the WG Charter=20 schedules accordingly.

Taking into account the = delay, we may=20 need to meet in San Diego, at the next IETF meeting planned for = August 1-6.=20 I will ask for a two hours meeting slot, same as we had in Seoul. I = would=20 advise the editors and other interested participants to plan for = this=20 meeting, please let me know if there are any issues.

Thanks = and=20 Regards,

Dan

------_=_NextPart_001_01C43394.A92B063F-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 6 15:06:39 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11692 for ; Thu, 6 May 2004 15:06:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLo0P-000544-So; Thu, 06 May 2004 14:54:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnsj-0001hF-7L for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:46:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10535 for ; Thu, 6 May 2004 14:46:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnsg-0001rc-Ho for hubmib@ietf.org; Thu, 06 May 2004 14:46:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnrh-0001Rk-00 for hubmib@ietf.org; Thu, 06 May 2004 14:45:01 -0400 Received: from [62.90.13.193] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 1BLnql-0000dL-00 for hubmib@ietf.org; Thu, 06 May 2004 14:44:03 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Thu, 6 May 2004 21:44:25 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF274232A@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" , hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:44:23 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4339A.265D37C0" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_20_30,HTML_FONTCOLOR_BLUE, HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4339A.265D37C0 Content-Type: text/plain; charset="windows-1255" Dan, About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6. Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week. Regards, -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C4339A.265D37C0 Content-Type: text/html; charset="windows-1255" Status, last call, meeting in San Diego
Dan,
About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6.
Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week.
Regards,
-Edward 
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 01:24 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, last call, meeting in San Diego

I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly.

Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues.

Thanks and Regards,

Dan

------_=_NextPart_001_01C4339A.265D37C0-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 6 15:12:59 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12460 for ; Thu, 6 May 2004 15:12:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLoC2-00058L-6k; Thu, 06 May 2004 15:06:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnzZ-0004j4-K8 for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:53:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10816 for ; Thu, 6 May 2004 14:53:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnzW-0004lv-Nx for hubmib@ietf.org; Thu, 06 May 2004 14:53:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnyg-0004Me-00 for hubmib@ietf.org; Thu, 06 May 2004 14:52:15 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1BLnxx-0003wN-00 for hubmib@ietf.org; Thu, 06 May 2004 14:51:29 -0400 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 i46IkPrw013515 for ; Thu, 6 May 2004 13:46:25 -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 i46IkNrw013472 for ; Thu, 6 May 2004 13:46:24 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4339B.22812355" Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:51:26 +0300 Message-ID: Thread-Topic: [Hubmib] Status, last call, meeting in San Diego Thread-Index: AcQzmgtzIN/lAk65Q+WwixZMm2WueAAALfAA From: "Romascanu, Dan (Dan)" To: "Edward Beili" , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C4339B.22812355 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Yes, I can ask for a Monday morning or for a Friday morning meeting = slot. There are no WG meetings on Sunday. Monday is probably slightly = better. Are other folks OK with this schedule request? =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 06 May, 2004 9:44 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Dan, About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 = meeting in Nevada planned for August 2-6. Could you please try to have the Hubmib slot allocated in the very = beginning (Sunday/Monday) or the very end (Friday) of this week. Regards, -Edward=20 -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our = schedule for going to Last Call for the EFM MIBs documents in April. = Actually, none of the revised Internet-Drafts was published, and with = one exception (the editor of the EPON MIB) no notice was sent concerning = the reasons of the delay. With the IEEE 802.3ah technical issues now = solved (to the best of my knowledge), I see no technical reason for this = delay. I would kindly request the editors of the three documents to let = the WG know what is their schedule for submitting the documents, so that = we can plan for WG Last Call, and ask for changes in the WG Charter = schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the = next IETF meeting planned for August 1-6. I will ask for a two hours = meeting slot, same as we had in Seoul. I would advise the editors and = other interested participants to plan for this meeting, please let me = know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C4339B.22812355 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Status, last call, meeting in San Diego
Yes, I can ask for a Monday morning or for a Friday = morning=20 meeting slot. There are no WG meetings on Sunday. Monday is probably = slightly=20 better. Are other folks OK with this schedule=20 request?
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 06 May, 2004 9:44=20 PM
To: Romascanu, Dan (Dan); = hubmib@ietf.org
Subject: RE:=20 [Hubmib] Status, last call, meeting in San Diego

Dan,
About the IETF meeting in August - it coincides with the = ITU-T SG15/Q4=20 meeting in Nevada planned for August 2-6.
Could you please try to have the Hubmib slot allocated = in the very=20 beginning (Sunday/Monday) or the very end (Friday) of this=20 week.
Regards,
-Edward 
-----Original Message-----
From: Romascanu, Dan = (Dan)=20 [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 = 01:24=20 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, = last=20 call, meeting in San Diego

I am very disappointed and = concerned with=20 the fact that we missed our schedule for going to Last Call for the = EFM MIBs=20 documents in April. Actually, none of the revised Internet-Drafts = was=20 published, and with one exception (the editor of the EPON MIB) no = notice was=20 sent concerning the reasons of the delay. With the IEEE 802.3ah = technical=20 issues now solved (to the best of my knowledge), I see no technical = reason=20 for this delay. I would kindly request the editors of the three = documents to=20 let the WG know what is their schedule for submitting the documents, = so that=20 we can plan for WG Last Call, and ask for changes in the WG Charter=20 schedules accordingly.

Taking into account the = delay, we may=20 need to meet in San Diego, at the next IETF meeting planned for = August 1-6.=20 I will ask for a two hours meeting slot, same as we had in Seoul. I = would=20 advise the editors and other interested participants to plan for = this=20 meeting, please let me know if there are any issues.

Thanks = and=20 Regards,

Dan

------_=_NextPart_001_01C4339B.22812355-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu May 6 15:13:15 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12528 for ; Thu, 6 May 2004 15:13:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLoCC-0005PL-B4 for hubmib-archive@odin.ietf.org; Thu, 06 May 2004 15:06:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46J6CbM020756 for hubmib-archive@odin.ietf.org; Thu, 6 May 2004 15:06:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLo0P-000544-So; Thu, 06 May 2004 14:54:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnsj-0001hF-7L for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:46:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10535 for ; Thu, 6 May 2004 14:46:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnsg-0001rc-Ho for hubmib@ietf.org; Thu, 06 May 2004 14:46:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnrh-0001Rk-00 for hubmib@ietf.org; Thu, 06 May 2004 14:45:01 -0400 Received: from [62.90.13.193] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 1BLnql-0000dL-00 for hubmib@ietf.org; Thu, 06 May 2004 14:44:03 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Thu, 6 May 2004 21:44:25 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF274232A@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" , hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:44:23 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4339A.265D37C0" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_20_30,HTML_FONTCOLOR_BLUE, HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4339A.265D37C0 Content-Type: text/plain; charset="windows-1255" Dan, About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6. Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week. Regards, -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C4339A.265D37C0 Content-Type: text/html; charset="windows-1255" Status, last call, meeting in San Diego
Dan,
About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6.
Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week.
Regards,
-Edward 
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 01:24 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, last call, meeting in San Diego

I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly.

Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues.

Thanks and Regards,

Dan

------_=_NextPart_001_01C4339A.265D37C0-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu May 6 15:19:17 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13268 for ; Thu, 6 May 2004 15:19:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLoIJ-0003Lb-2V for hubmib-archive@odin.ietf.org; Thu, 06 May 2004 15:12:31 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i46JCVGJ012859 for hubmib-archive@odin.ietf.org; Thu, 6 May 2004 15:12:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLoC2-00058L-6k; Thu, 06 May 2004 15:06:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLnzZ-0004j4-K8 for hubmib@optimus.ietf.org; Thu, 06 May 2004 14:53:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10816 for ; Thu, 6 May 2004 14:53:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLnzW-0004lv-Nx for hubmib@ietf.org; Thu, 06 May 2004 14:53:06 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLnyg-0004Me-00 for hubmib@ietf.org; Thu, 06 May 2004 14:52:15 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx with esmtp (Exim 4.12) id 1BLnxx-0003wN-00 for hubmib@ietf.org; Thu, 06 May 2004 14:51:29 -0400 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 i46IkPrw013515 for ; Thu, 6 May 2004 13:46:25 -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 i46IkNrw013472 for ; Thu, 6 May 2004 13:46:24 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4339B.22812355" Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Thu, 6 May 2004 21:51:26 +0300 Message-ID: Thread-Topic: [Hubmib] Status, last call, meeting in San Diego Thread-Index: AcQzmgtzIN/lAk65Q+WwixZMm2WueAAALfAA From: "Romascanu, Dan (Dan)" To: "Edward Beili" , X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C4339B.22812355 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Yes, I can ask for a Monday morning or for a Friday morning meeting = slot. There are no WG meetings on Sunday. Monday is probably slightly = better. Are other folks OK with this schedule request? =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 06 May, 2004 9:44 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Dan, About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 = meeting in Nevada planned for August 2-6. Could you please try to have the Hubmib slot allocated in the very = beginning (Sunday/Monday) or the very end (Friday) of this week. Regards, -Edward=20 -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our = schedule for going to Last Call for the EFM MIBs documents in April. = Actually, none of the revised Internet-Drafts was published, and with = one exception (the editor of the EPON MIB) no notice was sent concerning = the reasons of the delay. With the IEEE 802.3ah technical issues now = solved (to the best of my knowledge), I see no technical reason for this = delay. I would kindly request the editors of the three documents to let = the WG know what is their schedule for submitting the documents, so that = we can plan for WG Last Call, and ask for changes in the WG Charter = schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the = next IETF meeting planned for August 1-6. I will ask for a two hours = meeting slot, same as we had in Seoul. I would advise the editors and = other interested participants to plan for this meeting, please let me = know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C4339B.22812355 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Status, last call, meeting in San Diego
Yes, I can ask for a Monday morning or for a Friday = morning=20 meeting slot. There are no WG meetings on Sunday. Monday is probably = slightly=20 better. Are other folks OK with this schedule=20 request?
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 06 May, 2004 9:44=20 PM
To: Romascanu, Dan (Dan); = hubmib@ietf.org
Subject: RE:=20 [Hubmib] Status, last call, meeting in San Diego

Dan,
About the IETF meeting in August - it coincides with the = ITU-T SG15/Q4=20 meeting in Nevada planned for August 2-6.
Could you please try to have the Hubmib slot allocated = in the very=20 beginning (Sunday/Monday) or the very end (Friday) of this=20 week.
Regards,
-Edward 
-----Original Message-----
From: Romascanu, Dan = (Dan)=20 [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 = 01:24=20 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, = last=20 call, meeting in San Diego

I am very disappointed and = concerned with=20 the fact that we missed our schedule for going to Last Call for the = EFM MIBs=20 documents in April. Actually, none of the revised Internet-Drafts = was=20 published, and with one exception (the editor of the EPON MIB) no = notice was=20 sent concerning the reasons of the delay. With the IEEE 802.3ah = technical=20 issues now solved (to the best of my knowledge), I see no technical = reason=20 for this delay. I would kindly request the editors of the three = documents to=20 let the WG know what is their schedule for submitting the documents, = so that=20 we can plan for WG Last Call, and ask for changes in the WG Charter=20 schedules accordingly.

Taking into account the = delay, we may=20 need to meet in San Diego, at the next IETF meeting planned for = August 1-6.=20 I will ask for a two hours meeting slot, same as we had in Seoul. I = would=20 advise the editors and other interested participants to plan for = this=20 meeting, please let me know if there are any issues.

Thanks = and=20 Regards,

Dan

------_=_NextPart_001_01C4339B.22812355-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Sun May 9 05:41:46 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25502 for ; Sun, 9 May 2004 05:41:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMkmz-0002kK-9q; Sun, 09 May 2004 05:40:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMklA-0002Xi-7R for hubmib@optimus.ietf.org; Sun, 09 May 2004 05:38:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25268 for ; Sun, 9 May 2004 05:38:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BMkl6-0004fb-RJ for hubmib@ietf.org; Sun, 09 May 2004 05:38:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BMkjp-0004Gg-00 for hubmib@ietf.org; Sun, 09 May 2004 05:36:49 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BMkjI-0003mF-01; Sun, 09 May 2004 05:36:17 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BMkXq-0001kq-7T; Sun, 09 May 2004 05:24:26 -0400 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 i499J3rw027208; Sun, 9 May 2004 04:19:03 -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 i499J1rw027197; Sun, 9 May 2004 04:19:02 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C435A7.603FC476" Date: Sun, 9 May 2004 12:24:06 +0300 Message-ID: Thread-Topic: IETF 60 - hubmib scheduling request Thread-Index: AcQ1p18PbnNFL87JSyCR0N28MLLLAg== From: "Romascanu, Dan (Dan)" To: Cc: , "Bert Wijnen (E-mail)" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_40_50,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] IETF 60 - hubmib scheduling request Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C435A7.603FC476 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable a. Working Group or BOF full name with acronym in brackets: Ethernet Interfaces and hub MIB (hubmib)=20 b. AREA under which Working Group or BOF appears: Operations and Management c. CONFLICTS you wish to avoid, please be as specific as possible: rmonmib, sip, sipping, simple, bridge, disman, netconf, avt, midcom d. Expected Attendance (figures from the 59th IETF are at the end of = this message): 20 e. Special requests (i.e. multicast): Please schedule as first session on Monday Morning. An ITU meeting is = scheduled during the same week, and some of the key participants can = attend only if the meeting is scheduled at this time. f. Number of slots: 1 g. Length of slot:=20 - 2 1/2 hours Regards, Dan Dan Romascanu, Chair, Ethernet Interfaces and Hub MIB (hubmib) WG ------_=_NextPart_001_01C435A7.603FC476 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable IETF 60 - hubmib scheduling request

  a. Working Group or = BOF full name with acronym in brackets:

Ethernet Interfaces and hub = MIB (hubmib)

  b. AREA under which = Working Group or BOF appears:

Operations and = Management

  c. CONFLICTS you wish = to avoid, please be as specific as possible:

rmonmib, sip, sipping, = simple, bridge, disman, netconf, avt, midcom

  d. Expected Attendance = (figures from the 59th IETF are at the end of this message):

20

  e. Special requests = (i.e. multicast):

Please schedule as first = session on Monday Morning. An ITU meeting is scheduled during the same = week, and some of the key participants can attend only if the meeting is = scheduled at this time.

  f. Number of = slots:

1

  g. Length of slot: =

   - 2 1/2 = hours



Regards,

Dan

Dan = Romascanu,

Chair, = Ethernet Interfaces and Hub MIB (hubmib) WG

------_=_NextPart_001_01C435A7.603FC476-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Sun May 9 05:42:46 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25536 for ; Sun, 9 May 2004 05:42:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMkoB-0002vW-38 for hubmib-archive@odin.ietf.org; Sun, 09 May 2004 05:41:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i499fJ8o011250 for hubmib-archive@odin.ietf.org; Sun, 9 May 2004 05:41:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMkmz-0002kK-9q; Sun, 09 May 2004 05:40:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BMklA-0002Xi-7R for hubmib@optimus.ietf.org; Sun, 09 May 2004 05:38:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25268 for ; Sun, 9 May 2004 05:38:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BMkl6-0004fb-RJ for hubmib@ietf.org; Sun, 09 May 2004 05:38:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BMkjp-0004Gg-00 for hubmib@ietf.org; Sun, 09 May 2004 05:36:49 -0400 Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BMkjI-0003mF-01; Sun, 09 May 2004 05:36:17 -0400 Received: from tierw.net.avaya.com ([198.152.13.100]) by mx2.foretec.com with esmtp (Exim 4.24) id 1BMkXq-0001kq-7T; Sun, 09 May 2004 05:24:26 -0400 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 i499J3rw027208; Sun, 9 May 2004 04:19:03 -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 i499J1rw027197; Sun, 9 May 2004 04:19:02 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C435A7.603FC476" Date: Sun, 9 May 2004 12:24:06 +0300 Message-ID: Thread-Topic: IETF 60 - hubmib scheduling request Thread-Index: AcQ1p18PbnNFL87JSyCR0N28MLLLAg== From: "Romascanu, Dan (Dan)" To: Cc: , "Bert Wijnen (E-mail)" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_40_50,HTML_MESSAGE autolearn=no version=2.60 Subject: [Hubmib] IETF 60 - hubmib scheduling request Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C435A7.603FC476 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable a. Working Group or BOF full name with acronym in brackets: Ethernet Interfaces and hub MIB (hubmib)=20 b. AREA under which Working Group or BOF appears: Operations and Management c. CONFLICTS you wish to avoid, please be as specific as possible: rmonmib, sip, sipping, simple, bridge, disman, netconf, avt, midcom d. Expected Attendance (figures from the 59th IETF are at the end of = this message): 20 e. Special requests (i.e. multicast): Please schedule as first session on Monday Morning. An ITU meeting is = scheduled during the same week, and some of the key participants can = attend only if the meeting is scheduled at this time. f. Number of slots: 1 g. Length of slot:=20 - 2 1/2 hours Regards, Dan Dan Romascanu, Chair, Ethernet Interfaces and Hub MIB (hubmib) WG ------_=_NextPart_001_01C435A7.603FC476 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable IETF 60 - hubmib scheduling request

  a. Working Group or = BOF full name with acronym in brackets:

Ethernet Interfaces and hub = MIB (hubmib)

  b. AREA under which = Working Group or BOF appears:

Operations and = Management

  c. CONFLICTS you wish = to avoid, please be as specific as possible:

rmonmib, sip, sipping, = simple, bridge, disman, netconf, avt, midcom

  d. Expected Attendance = (figures from the 59th IETF are at the end of this message):

20

  e. Special requests = (i.e. multicast):

Please schedule as first = session on Monday Morning. An ITU meeting is scheduled during the same = week, and some of the key participants can attend only if the meeting is = scheduled at this time.

  f. Number of = slots:

1

  g. Length of slot: =

   - 2 1/2 = hours



Regards,

Dan

Dan = Romascanu,

Chair, = Ethernet Interfaces and Hub MIB (hubmib) WG

------_=_NextPart_001_01C435A7.603FC476-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Tue May 11 04:15:29 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10709 for ; Tue, 11 May 2004 04:15:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNSM0-0006of-QM; Tue, 11 May 2004 04:11:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNS75-00025R-PT for hubmib@optimus.ietf.org; Tue, 11 May 2004 03:55:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09531 for ; Tue, 11 May 2004 03:55:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNS73-0001j7-4s for hubmib@ietf.org; Tue, 11 May 2004 03:55:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNS69-0001Lg-00 for hubmib@ietf.org; Tue, 11 May 2004 03:54:46 -0400 Received: from [62.90.13.193] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 1BNS5J-0000g4-00 for hubmib@ietf.org; Tue, 11 May 2004 03:53:53 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Tue, 11 May 2004 10:54:26 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF274234D@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" , hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Tue, 11 May 2004 10:54:25 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4372D.2DF58E60" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4372D.2DF58E60 Content-Type: text/plain; charset="windows-1255" I also think Monday is better. -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 09:51 PM To: Edward Beili; hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Yes, I can ask for a Monday morning or for a Friday morning meeting slot. There are no WG meetings on Sunday. Monday is probably slightly better. Are other folks OK with this schedule request? Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 06 May, 2004 9:44 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Dan, About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6. Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week. Regards, -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C4372D.2DF58E60 Content-Type: text/html; charset="windows-1255" Status, last call, meeting in San Diego
I also think Monday is better.
-Edward
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 09:51 PM
To: Edward Beili; hubmib@ietf.org
Subject: RE: [Hubmib] Status, last call, meeting in San Diego

Yes, I can ask for a Monday morning or for a Friday morning meeting slot. There are no WG meetings on Sunday. Monday is probably slightly better. Are other folks OK with this schedule request?
 

Regards,

Dan

-----Original Message-----
From: Edward Beili [mailto:EdwardB@actelis.com]
Sent: 06 May, 2004 9:44 PM
To: Romascanu, Dan (Dan); hubmib@ietf.org
Subject: RE: [Hubmib] Status, last call, meeting in San Diego

Dan,
About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6.
Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week.
Regards,
-Edward 
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 01:24 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, last call, meeting in San Diego

I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly.

Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues.

Thanks and Regards,

Dan

------_=_NextPart_001_01C4372D.2DF58E60-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Tue May 11 04:32:18 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11766 for ; Tue, 11 May 2004 04:32:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNSPl-0000KV-Cn for hubmib-archive@odin.ietf.org; Tue, 11 May 2004 04:15:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4B8F1go001268 for hubmib-archive@odin.ietf.org; Tue, 11 May 2004 04:15:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNSM0-0006of-QM; Tue, 11 May 2004 04:11:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNS75-00025R-PT for hubmib@optimus.ietf.org; Tue, 11 May 2004 03:55:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09531 for ; Tue, 11 May 2004 03:55:41 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNS73-0001j7-4s for hubmib@ietf.org; Tue, 11 May 2004 03:55:41 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNS69-0001Lg-00 for hubmib@ietf.org; Tue, 11 May 2004 03:54:46 -0400 Received: from [62.90.13.193] (helo=il-mail02.actelis.net) by ietf-mx with esmtp (Exim 4.12) id 1BNS5J-0000g4-00 for hubmib@ietf.org; Tue, 11 May 2004 03:53:53 -0400 Received: by il-mail02.actelis.net with Internet Mail Service (5.5.2653.19) id ; Tue, 11 May 2004 10:54:26 +0300 Message-ID: <36EB88BFB60BD711B29C00062939CDF274234D@il-mail02.actelis.net> From: Edward Beili To: "'Romascanu, Dan (Dan)'" , hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Date: Tue, 11 May 2004 10:54:25 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4372D.2DF58E60" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,HTML_30_40, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60 Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4372D.2DF58E60 Content-Type: text/plain; charset="windows-1255" I also think Monday is better. -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 09:51 PM To: Edward Beili; hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Yes, I can ask for a Monday morning or for a Friday morning meeting slot. There are no WG meetings on Sunday. Monday is probably slightly better. Are other folks OK with this schedule request? Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 06 May, 2004 9:44 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Status, last call, meeting in San Diego Dan, About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6. Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week. Regards, -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, 06 May, 2004 01:24 PM To: hubmib@ietf.org Subject: [Hubmib] Status, last call, meeting in San Diego I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly. Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues. Thanks and Regards, Dan ------_=_NextPart_001_01C4372D.2DF58E60 Content-Type: text/html; charset="windows-1255" Status, last call, meeting in San Diego
I also think Monday is better.
-Edward
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 09:51 PM
To: Edward Beili; hubmib@ietf.org
Subject: RE: [Hubmib] Status, last call, meeting in San Diego

Yes, I can ask for a Monday morning or for a Friday morning meeting slot. There are no WG meetings on Sunday. Monday is probably slightly better. Are other folks OK with this schedule request?
 

Regards,

Dan

-----Original Message-----
From: Edward Beili [mailto:EdwardB@actelis.com]
Sent: 06 May, 2004 9:44 PM
To: Romascanu, Dan (Dan); hubmib@ietf.org
Subject: RE: [Hubmib] Status, last call, meeting in San Diego

Dan,
About the IETF meeting in August - it coincides with the ITU-T SG15/Q4 meeting in Nevada planned for August 2-6.
Could you please try to have the Hubmib slot allocated in the very beginning (Sunday/Monday) or the very end (Friday) of this week.
Regards,
-Edward 
-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Thursday, 06 May, 2004 01:24 PM
To: hubmib@ietf.org
Subject: [Hubmib] Status, last call, meeting in San Diego

I am very disappointed and concerned with the fact that we missed our schedule for going to Last Call for the EFM MIBs documents in April. Actually, none of the revised Internet-Drafts was published, and with one exception (the editor of the EPON MIB) no notice was sent concerning the reasons of the delay. With the IEEE 802.3ah technical issues now solved (to the best of my knowledge), I see no technical reason for this delay. I would kindly request the editors of the three documents to let the WG know what is their schedule for submitting the documents, so that we can plan for WG Last Call, and ask for changes in the WG Charter schedules accordingly.

Taking into account the delay, we may need to meet in San Diego, at the next IETF meeting planned for August 1-6. I will ask for a two hours meeting slot, same as we had in Seoul. I would advise the editors and other interested participants to plan for this meeting, please let me know if there are any issues.

Thanks and Regards,

Dan

------_=_NextPart_001_01C4372D.2DF58E60-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From hubmib-admin@ietf.org Thu May 13 13:14:23 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24453 for ; Thu, 13 May 2004 13:14:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOJW8-0004A4-5B; Thu, 13 May 2004 12:57:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOJSx-0003QP-7b for hubmib@optimus.ietf.org; Thu, 13 May 2004 12:53:51 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23027; Thu, 13 May 2004 12:53:47 -0400 (EDT) Message-Id: <200405131653.MAA23027@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 13 May 2004 12:53:47 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-efm-epon-mib-01.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Managed Objects for the Ethernet Passive Optical Networks Author(s) : L. Khermosh Filename : draft-ietf-hubmib-efm-epon-mib-01.txt Pages : 67 Date : 2004-5-12 This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based Internets. In particular, it defines objects for managing devices and interfaces that conform to the Ethernet Passive Optical Networks (EPON) standards as defined in [802.3ah]. The document contains a list of management entities based on the registers defined in the Institute of Electrical and Electronic Engineers, IEEE Draft 802.3ah-2002 Draft 3.2 Annex 30A and mainly partitioned accordingly. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-epon-mib-01.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-epon-mib-01.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-epon-mib-01.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-5-13131711.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-efm-epon-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-efm-epon-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-5-13131711.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib From exim@www1.ietf.org Thu May 13 13:28:50 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25984 for ; Thu, 13 May 2004 13:28:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOJmN-0000Qv-AW for hubmib-archive@odin.ietf.org; Thu, 13 May 2004 13:13:55 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4DHDtoW001665 for hubmib-archive@odin.ietf.org; Thu, 13 May 2004 13:13:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOJW8-0004A4-5B; Thu, 13 May 2004 12:57:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOJSx-0003QP-7b for hubmib@optimus.ietf.org; Thu, 13 May 2004 12:53:51 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23027; Thu, 13 May 2004 12:53:47 -0400 (EDT) Message-Id: <200405131653.MAA23027@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: hubmib@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 13 May 2004 12:53:47 -0400 Subject: [Hubmib] I-D ACTION:draft-ietf-hubmib-efm-epon-mib-01.txt Sender: hubmib-admin@ietf.org Errors-To: hubmib-admin@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Ethernet Interfaces and Hub MIB Working Group of the IETF. Title : Managed Objects for the Ethernet Passive Optical Networks Author(s) : L. Khermosh Filename : draft-ietf-hubmib-efm-epon-mib-01.txt Pages : 67 Date : 2004-5-12 This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based Internets. In particular, it defines objects for managing devices and interfaces that conform to the Ethernet Passive Optical Networks (EPON) standards as defined in [802.3ah]. The document contains a list of management entities based on the registers defined in the Institute of Electrical and Electronic Engineers, IEEE Draft 802.3ah-2002 Draft 3.2 Annex 30A and mainly partitioned accordingly. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-epon-mib-01.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-epon-mib-01.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-epon-mib-01.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-5-13131711.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hubmib-efm-epon-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hubmib-efm-epon-mib-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-5-13131711.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib