From hubmib-bounces@ietf.org Sat Feb 5 19:22:03 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14329 for ; Sat, 5 Feb 2005 19:22:03 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxaAn-0007qx-3B; Sat, 05 Feb 2005 19:21:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cxa90-0007bE-Lv for hubmib@megatron.ietf.org; Sat, 05 Feb 2005 19:19:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14214 for ; Sat, 5 Feb 2005 19:19:14 -0500 (EST) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxaS4-0003A7-6L for hubmib@ietf.org; Sat, 05 Feb 2005 19:39:01 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j1609WFx018995 for ; Sat, 5 Feb 2005 19:09:33 -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 j1609UFx018930 for ; Sat, 5 Feb 2005 19:09:31 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Sun, 6 Feb 2005 02:19:12 +0200 Message-ID: Thread-Topic: massas! Thread-Index: AcUL4Xo1wclc9paURvW5od0QutdeBwAAAGHc From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 0.8 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Subject: [Hubmib] Out of Office AutoReply: massas! X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0703210470==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0703210470== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C50BE1.7BBC299F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C50BE1.7BBC299F Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I am out of office, travelling for business purposes until February = 14th, 2005. I may be able to reply to your e-mail only after this date. = If you need to contact me urgently, please call my mobile phone number = +1-917-957-0270. Regards, Dan Regards, Dan ------_=_NextPart_001_01C50BE1.7BBC299F Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Out of Office AutoReply: massas!

I am out of office, travelling for business purposes = until February 14th, 2005. I may be able to reply to your e-mail only = after this date. If you need to contact me urgently, please call my = mobile phone number +1-917-957-0270.

Regards,

Dan


Regards,

Dan

------_=_NextPart_001_01C50BE1.7BBC299F-- --===============0703210470== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0703210470==-- From hubmib-bounces@ietf.org Wed Feb 16 12:22:48 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28384 for ; Wed, 16 Feb 2005 12:22:48 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1RKY-0003fS-Mg; Wed, 16 Feb 2005 10:43:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Qsv-00013S-73 for hubmib@megatron.ietf.org; Wed, 16 Feb 2005 10:14:37 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20487 for ; Wed, 16 Feb 2005 10:14:34 -0500 (EST) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1REB-00071z-Cj for hubmib@ietf.org; Wed, 16 Feb 2005 10:36:35 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j1GF4fOX014285 for ; Wed, 16 Feb 2005 10:04:42 -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 j1GF4ZOX014139 for ; Wed, 16 Feb 2005 10:04:36 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 16 Feb 2005 17:14:18 +0200 Message-ID: Thread-Topic: WGLC Comments on draft-ietf-hubmib-efm-epon-mib-02.txt Thread-Index: AcUULZFVY/b0G+CBQyiQiQ5/s1b3BA== From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 0.8 (/) X-Scan-Signature: 93e7fb8fef2e780414389440f367c879 Subject: [Hubmib] WGLC Comments on draft-ietf-hubmib-efm-epon-mib-02.txt X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1883855657==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============1883855657== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5143A.2F1A969C" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5143A.2F1A969C Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are my comments on draft-ietf-hubmib-efm-epon-mib-02.txt. As this = is a Last Call, I will not divide them into critical and minor - all = comments must be addressed at this phase. Regards, Dan Technical T1. As per the revised charter, the new MAU MIB should provide a = different mechanism for defining new MAU types. I recommend that all MAU = extensions be taken out of this document and the new MAU MIB and = extensibility mechanism be referred. This will also lead to changes in = the IANA section (I believe) Editorial E1. The IEEE 802.3ah draft references need to be replaced by the name of = the final IEEE standard, which is now available E2. Badly formatted title in Section 4.1 E3. Section 4.1, row 4 - unjustified capital T E4. Replace 'OAM EFM MIB' with 'EFM OAM MIB' E5. Section 4.1 to 4.6 define requirements without using key words such = as MUST and MAY as required by RFC 2119. E6. The last phrase in Section 5 needs not be introduced, or must be = marked for the RFC Editor to be taken out at standard publication. E7. Acronyms as MPCP, P2MP, etc. need to be expanded at their first = occurrence (which is I believe in Section 6) E8. The company designation of the WG chair is Avaya and not Avaya Inc. E9. Missing period in the DESCRIPTION clause of = eponDeviceObjectFecEnable ------_=_NextPart_001_01C5143A.2F1A969C Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable WGLC Comments on draft-ietf-hubmib-efm-epon-mib-02.txt

Here are my comments on = draft-ietf-hubmib-efm-epon-mib-02.txt. As this is a Last Call, I will = not divide them into critical and minor - all comments must be addressed = at this phase.

Regards,

Dan

Technical

T1. As per = the revised charter, the new MAU MIB should provide a different = mechanism for defining new MAU types. I recommend that all MAU = extensions be taken out of this document and the new MAU MIB and = extensibility mechanism be referred. This will also lead to changes in = the IANA section (I believe)



Editorial

E1. The = IEEE 802.3ah draft references need to be replaced by the name of the = final IEEE standard, which is now available

E2. Badly = formatted title in Section 4.1

E3. Section = 4.1, row 4 - unjustified capital T

E4. Replace = 'OAM EFM MIB' with 'EFM OAM MIB'

E5. Section = 4.1 to 4.6 define requirements without using key words such as MUST and = MAY as required by RFC 2119.

E6. The = last phrase in Section 5 needs not be introduced, or must be marked for = the RFC Editor to be taken out at standard = publication.

E7. = Acronyms as MPCP, P2MP, etc. need to be expanded at their first = occurrence (which is I believe in Section 6)

E8. The = company designation of the WG chair is Avaya and not Avaya = Inc.

E9. Missing = period in the DESCRIPTION clause of = eponDeviceObjectFecEnable




------_=_NextPart_001_01C5143A.2F1A969C-- --===============1883855657== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============1883855657==-- From hubmib-bounces@ietf.org Wed Feb 16 15:19:38 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17029 for ; Wed, 16 Feb 2005 15:19:38 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1VC3-0001N2-6u; Wed, 16 Feb 2005 14:50:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1TZY-0003W7-Uk for hubmib@megatron.ietf.org; Wed, 16 Feb 2005 13:06:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10541 for ; Wed, 16 Feb 2005 13:06:45 -0500 (EST) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Tuq-00060G-8L for hubmib@ietf.org; Wed, 16 Feb 2005 13:28:49 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j1GHuqOX026548 for ; Wed, 16 Feb 2005 12:56:53 -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 j1GHtgOX024553 for ; Wed, 16 Feb 2005 12:56:00 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 16 Feb 2005 20:05:16 +0200 Message-ID: Thread-Topic: Last Call Completed for EFM MIB Documents Thread-Index: AcUUUhFXG2eV01BHRgKWE9f1nOmrNg== From: "Romascanu, Dan \(Dan\)" To: X-Spam-Score: 0.5 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Subject: [Hubmib] Last Call Completed for EFM MIB Documents X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1159452839==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============1159452839== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C51452.118D9F58" This is a multi-part message in MIME format. ------_=_NextPart_001_01C51452.118D9F58 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable The EFM MIB documents completed the Working Group Last Call. A number of = technical and editorial comments were submitted against all three = documents, and a new round of Internet-Drafts followed by a shorter Last = Call period is necessary. In order to make sure that all last call = comments are addressed I would request that the editors submit a list = with the comments that were received and proposed resolution to the WG = e-mail list before submitting new Internet-Drafts. The updated MAU MIB = document can also be re-spanned and I suggest that it goes into the same = Last Call round with the three EFM MIB I-Ds. Suggested schedule: 2/25 - submit comments resolution to the WG list 3/11 (end of IETF non-submission period) - submit new round of = Internet-Drafts (all four documents) 3/25 - complete final Working Group Last Call end March - submit documents to the IESG for consideration as Proposed = Standards Please let me know if this schedule is appropriate or it causes any = problems. I am waiting for the specific confirmation from the editors. Regards, Dan ------_=_NextPart_001_01C51452.118D9F58 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Last Call Completed for EFM MIB Documents

The EFM MIB documents = completed the Working Group Last Call. A number of technical and = editorial comments were submitted against all three documents, and a new = round of Internet-Drafts followed by a shorter Last Call period is = necessary. In order to make sure that all last call comments are = addressed I would request that the editors submit a list with the = comments that were received and proposed resolution to the WG e-mail = list before submitting new Internet-Drafts. The updated MAU MIB document = can also be re-spanned and I suggest that it goes into the same Last = Call round with the three EFM MIB I-Ds.

Suggested = schedule:

2/25 - submit comments = resolution to the WG list

3/11 (end of IETF = non-submission period) - submit new round of Internet-Drafts (all four = documents)

3/25 - complete final Working = Group Last Call

end March - submit documents = to the IESG for consideration as Proposed Standards

Please let me know if this = schedule is appropriate or it causes any problems. I am waiting for the = specific confirmation from the editors.

Regards,

Dan

------_=_NextPart_001_01C51452.118D9F58-- --===============1159452839== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============1159452839==-- From hubmib-bounces@ietf.org Thu Feb 17 08:17:51 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19920 for ; Thu, 17 Feb 2005 08:17:51 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1kYu-0008DF-9A; Thu, 17 Feb 2005 07:15:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1kVs-0006kZ-7R for hubmib@megatron.ietf.org; Thu, 17 Feb 2005 07:12:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14095 for ; Thu, 17 Feb 2005 07:12:03 -0500 (EST) Received: from [62.90.13.193] (helo=il-mail.actelis.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1krH-0000no-4H for hubmib@ietf.org; Thu, 17 Feb 2005 07:34:15 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Date: Thu, 17 Feb 2005 14:10:54 +0200 Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E38B258@il-mail.actelis.net> Thread-Topic: Last Call Completed for EFM MIB Documents Thread-Index: AcUUUhFXG2eV01BHRgKWE9f1nOmrNgAl2P5g From: "Edward Beili" To: "Romascanu, Dan \(Dan\)" , X-Spam-Score: 0.6 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0160329175==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0160329175== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C514E9.BAEE2618" This is a multi-part message in MIME format. ------_=_NextPart_001_01C514E9.BAEE2618 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I would suggest extending the comment resolution submittal till 3/11 and = submit the drafts with comments resolved on the next day. -Edward -----Original Message----- From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On Behalf = Of Romascanu, Dan (Dan) Sent: Wednesday, February 16, 2005 8:05 PM To: hubmib@ietf.org Subject: [Hubmib] Last Call Completed for EFM MIB Documents The EFM MIB documents completed the Working Group Last Call. A number of = technical and editorial comments were submitted against all three = documents, and a new round of Internet-Drafts followed by a shorter Last = Call period is necessary. In order to make sure that all last call = comments are addressed I would request that the editors submit a list = with the comments that were received and proposed resolution to the WG = e-mail list before submitting new Internet-Drafts. The updated MAU MIB = document can also be re-spanned and I suggest that it goes into the same = Last Call round with the three EFM MIB I-Ds. Suggested schedule: 2/25 - submit comments resolution to the WG list 3/11 (end of IETF non-submission period) - submit new round of = Internet-Drafts (all four documents) 3/25 - complete final Working Group Last Call end March - submit documents to the IESG for consideration as Proposed = Standards Please let me know if this schedule is appropriate or it causes any = problems. I am waiting for the specific confirmation from the editors. Regards, Dan ------_=_NextPart_001_01C514E9.BAEE2618 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Last Call Completed for EFM MIB Documents
I=20 would suggest extending the comment resolution submittal till 3/11 and = submit=20 the drafts with comments resolved on  the next = day.
-Edward
-----Original Message-----
From: = hubmib-bounces@ietf.org=20 [mailto:hubmib-bounces@ietf.org]On Behalf Of Romascanu, Dan=20 (Dan)
Sent: Wednesday, February 16, 2005 8:05 = PM
To:=20 hubmib@ietf.org
Subject: [Hubmib] Last Call Completed for = EFM MIB=20 Documents

The EFM MIB documents = completed the Working=20 Group Last Call. A number of technical and editorial comments were = submitted=20 against all three documents, and a new round of Internet-Drafts = followed by a=20 shorter Last Call period is necessary. In order to make sure that all = last=20 call comments are addressed I would request that the editors submit a = list=20 with the comments that were received and proposed resolution to the WG = e-mail=20 list before submitting new Internet-Drafts. The updated MAU MIB = document can=20 also be re-spanned and I suggest that it goes into the same Last Call = round=20 with the three EFM MIB I-Ds.

Suggested = schedule:

2/25 - submit comments = resolution to the WG=20 list

3/11 (end of IETF = non-submission period) -=20 submit new round of Internet-Drafts (all four documents)

3/25 - complete final Working = Group Last=20 Call

end March - submit documents = to the IESG=20 for consideration as Proposed Standards

Please let me know if this = schedule is=20 appropriate or it causes any problems. I am waiting for the specific=20 confirmation from the editors.

Regards,

Dan

------_=_NextPart_001_01C514E9.BAEE2618-- --===============0160329175== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0160329175==-- From hubmib-bounces@ietf.org Thu Feb 17 08:51:47 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24258 for ; Thu, 17 Feb 2005 08:51:47 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1ktQ-00088m-SW; Thu, 17 Feb 2005 07:36:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1krH-0006ql-Rg for hubmib@megatron.ietf.org; Thu, 17 Feb 2005 07:34:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15660 for ; Thu, 17 Feb 2005 07:34:15 -0500 (EST) Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1lCg-0001JV-8v for hubmib@ietf.org; Thu, 17 Feb 2005 07:56:26 -0500 Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j1HCOGOX004471 for ; Thu, 17 Feb 2005 07:24:16 -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 j1HCOEOX004420 for ; Thu, 17 Feb 2005 07:24:15 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Date: Thu, 17 Feb 2005 14:34:04 +0200 Message-ID: Thread-Topic: Last Call Completed for EFM MIB Documents Thread-Index: AcUUUhFXG2eV01BHRgKWE9f1nOmrNgAl2P5gAACoanA= From: "Romascanu, Dan \(Dan\)" To: "Edward Beili" , X-Spam-Score: 0.9 (/) X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7 X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0207028301==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0207028301== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C514EC.F760B638" This is a multi-part message in MIME format. ------_=_NextPart_001_01C514EC.F760B638 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Ed,=20 =20 Leaving some time between comments resolution and Internet-Drafts = submission is necessary for the people who submitted comments to review = the comments resolutions and react if necessary. If you have problems = with meeting 2/25 date for comments resolution, please let me know what = is the earliest date that would suit you.=20 =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 17 February, 2005 2:11 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents I would suggest extending the comment resolution submittal till 3/11 and = submit the drafts with comments resolved on the next day. -Edward -----Original Message----- From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On Behalf = Of Romascanu, Dan (Dan) Sent: Wednesday, February 16, 2005 8:05 PM To: hubmib@ietf.org Subject: [Hubmib] Last Call Completed for EFM MIB Documents The EFM MIB documents completed the Working Group Last Call. A number of = technical and editorial comments were submitted against all three = documents, and a new round of Internet-Drafts followed by a shorter Last = Call period is necessary. In order to make sure that all last call = comments are addressed I would request that the editors submit a list = with the comments that were received and proposed resolution to the WG = e-mail list before submitting new Internet-Drafts. The updated MAU MIB = document can also be re-spanned and I suggest that it goes into the same = Last Call round with the three EFM MIB I-Ds. Suggested schedule: 2/25 - submit comments resolution to the WG list 3/11 (end of IETF non-submission period) - submit new round of = Internet-Drafts (all four documents) 3/25 - complete final Working Group Last Call end March - submit documents to the IESG for consideration as Proposed = Standards Please let me know if this schedule is appropriate or it causes any = problems. I am waiting for the specific confirmation from the editors. Regards, Dan ------_=_NextPart_001_01C514EC.F760B638 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Last Call Completed for EFM MIB Documents
Ed,
 
Leaving some time between comments resolution and = Internet-Drafts=20 submission is necessary for the people who submitted comments to review = the=20 comments resolutions and react if necessary. If you have problems with = meeting=20 2/25 date for comments resolution, please let me know what is the = earliest date=20 that would suit you.
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 17 February, 2005 2:11=20 PM
To: Romascanu, Dan (Dan); = hubmib@ietf.org
Subject: RE:=20 [Hubmib] Last Call Completed for EFM MIB = Documents

I=20 would suggest extending the comment resolution submittal till 3/11 and = submit=20 the drafts with comments resolved on  the next = day.
-Edward
-----Original Message-----
From: = hubmib-bounces@ietf.org=20 [mailto:hubmib-bounces@ietf.org]On Behalf Of Romascanu, Dan=20 (Dan)
Sent: Wednesday, February 16, 2005 8:05 = PM
To:=20 hubmib@ietf.org
Subject: [Hubmib] Last Call Completed for = EFM MIB=20 Documents

The EFM MIB documents = completed the=20 Working Group Last Call. A number of technical and editorial = comments were=20 submitted against all three documents, and a new round of = Internet-Drafts=20 followed by a shorter Last Call period is necessary. In order to = make sure=20 that all last call comments are addressed I would request that the = editors=20 submit a list with the comments that were received and proposed = resolution=20 to the WG e-mail list before submitting new Internet-Drafts. The = updated MAU=20 MIB document can also be re-spanned and I suggest that it goes into = the same=20 Last Call round with the three EFM MIB I-Ds.

Suggested = schedule:

2/25 - submit comments = resolution to the=20 WG list

3/11 (end of IETF = non-submission period)=20 - submit new round of Internet-Drafts (all four = documents)

3/25 - complete final = Working Group Last=20 Call

end March - submit = documents to the IESG=20 for consideration as Proposed Standards

Please let me know if this = schedule is=20 appropriate or it causes any problems. I am waiting for the specific = confirmation from the editors.

Regards,

Dan

------_=_NextPart_001_01C514EC.F760B638-- --===============0207028301== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0207028301==-- From hubmib-bounces@ietf.org Thu Feb 17 10:54:05 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09754 for ; Thu, 17 Feb 2005 10:54:05 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1mus-0008WI-Vv; Thu, 17 Feb 2005 09:46:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1mlS-0004E2-Kk for hubmib@megatron.ietf.org; Thu, 17 Feb 2005 09:36:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29049 for ; Thu, 17 Feb 2005 09:36:19 -0500 (EST) Received: from [62.90.13.193] (helo=il-mail.actelis.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1n6p-0004s2-Ec for hubmib@ietf.org; Thu, 17 Feb 2005 09:58:32 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Date: Thu, 17 Feb 2005 16:35:03 +0200 Message-ID: <9C1CAB2B65E62D49A10E49DFCD68EF3E38B25C@il-mail.actelis.net> Thread-Topic: Last Call Completed for EFM MIB Documents Thread-Index: AcUUUhFXG2eV01BHRgKWE9f1nOmrNgAl2P5gAACoanAABF6VgA== From: "Edward Beili" To: "Romascanu, Dan \(Dan\)" X-Spam-Score: 0.9 (/) X-Scan-Signature: bc6181926481d86059e678c9f7cb8b34 Cc: hubmib@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0783618698==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0783618698== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C514FD.DE229C80" This is a multi-part message in MIME format. ------_=_NextPart_001_01C514FD.DE229C80 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable I understand. I do have a little problem and would like to postpone = comment resolution submittal till 2/30. -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, February 17, 2005 2:34 PM To: Edward Beili; hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Ed,=20 =20 Leaving some time between comments resolution and Internet-Drafts = submission is necessary for the people who submitted comments to review = the comments resolutions and react if necessary. If you have problems = with meeting 2/25 date for comments resolution, please let me know what = is the earliest date that would suit you.=20 =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 17 February, 2005 2:11 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents I would suggest extending the comment resolution submittal till 3/11 and = submit the drafts with comments resolved on the next day. -Edward -----Original Message----- From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On Behalf = Of Romascanu, Dan (Dan) Sent: Wednesday, February 16, 2005 8:05 PM To: hubmib@ietf.org Subject: [Hubmib] Last Call Completed for EFM MIB Documents The EFM MIB documents completed the Working Group Last Call. A number of = technical and editorial comments were submitted against all three = documents, and a new round of Internet-Drafts followed by a shorter Last = Call period is necessary. In order to make sure that all last call = comments are addressed I would request that the editors submit a list = with the comments that were received and proposed resolution to the WG = e-mail list before submitting new Internet-Drafts. The updated MAU MIB = document can also be re-spanned and I suggest that it goes into the same = Last Call round with the three EFM MIB I-Ds. Suggested schedule: 2/25 - submit comments resolution to the WG list 3/11 (end of IETF non-submission period) - submit new round of = Internet-Drafts (all four documents) 3/25 - complete final Working Group Last Call end March - submit documents to the IESG for consideration as Proposed = Standards Please let me know if this schedule is appropriate or it causes any = problems. I am waiting for the specific confirmation from the editors. Regards, Dan ------_=_NextPart_001_01C514FD.DE229C80 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Last Call Completed for EFM MIB Documents
I=20 understand. I do have a little problem and would like to postpone = comment=20 resolution submittal till 2/30.
-Edward
-----Original Message-----
From: Romascanu, Dan = (Dan)=20 [mailto:dromasca@avaya.com]
Sent: Thursday, February 17, = 2005 2:34=20 PM
To: Edward Beili; hubmib@ietf.org
Subject: RE: = [Hubmib]=20 Last Call Completed for EFM MIB Documents

Ed,
 
Leaving some time between comments resolution and = Internet-Drafts=20 submission is necessary for the people who submitted comments to = review the=20 comments resolutions and react if necessary. If you have problems with = meeting=20 2/25 date for comments resolution, please let me know what is the = earliest=20 date that would suit you.
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 17 February, 2005 2:11=20 PM
To: Romascanu, Dan (Dan); = hubmib@ietf.org
Subject:=20 RE: [Hubmib] Last Call Completed for EFM MIB = Documents

I=20 would suggest extending the comment resolution submittal till 3/11 = and=20 submit the drafts with comments resolved on  the next=20 day.
-Edward
-----Original Message-----
From: = hubmib-bounces@ietf.org=20 [mailto:hubmib-bounces@ietf.org]On Behalf Of Romascanu, Dan = (Dan)
Sent: Wednesday, February 16, 2005 8:05 = PM
To:=20 hubmib@ietf.org
Subject: [Hubmib] Last Call Completed = for EFM=20 MIB Documents

The EFM MIB documents = completed the=20 Working Group Last Call. A number of technical and editorial = comments were=20 submitted against all three documents, and a new round of = Internet-Drafts=20 followed by a shorter Last Call period is necessary. In order to = make sure=20 that all last call comments are addressed I would request that the = editors=20 submit a list with the comments that were received and proposed = resolution=20 to the WG e-mail list before submitting new Internet-Drafts. The = updated=20 MAU MIB document can also be re-spanned and I suggest that it goes = into=20 the same Last Call round with the three EFM MIB I-Ds.

Suggested = schedule:

2/25 - submit comments = resolution to=20 the WG list

3/11 (end of IETF = non-submission=20 period) - submit new round of Internet-Drafts (all four=20 documents)

3/25 - complete final = Working Group=20 Last Call

end March - submit = documents to the=20 IESG for consideration as Proposed Standards

Please let me know if = this schedule is=20 appropriate or it causes any problems. I am waiting for the = specific=20 confirmation from the editors.

Regards,

Dan

------_=_NextPart_001_01C514FD.DE229C80-- --===============0783618698== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0783618698==-- From hubmib-bounces@ietf.org Thu Feb 17 12:34:16 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01256 for ; Thu, 17 Feb 2005 12:34:16 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1nMQ-00035T-Jk; Thu, 17 Feb 2005 10:14:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1n4W-0004Iq-Dw for hubmib@megatron.ietf.org; Thu, 17 Feb 2005 09:56:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01267 for ; Thu, 17 Feb 2005 09:56:03 -0500 (EST) Received: from tiere.net.avaya.com ([198.152.12.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1nPw-0005Rx-8x for hubmib@ietf.org; Thu, 17 Feb 2005 10:18:16 -0500 Received: from tiere.net.avaya.com (localhost [127.0.0.1]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j1HErljV008342 for ; Thu, 17 Feb 2005 09:53:47 -0500 (EST) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tiere.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j1HErNjV007619 for ; Thu, 17 Feb 2005 09:53:27 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Date: Thu, 17 Feb 2005 16:53:36 +0200 Message-ID: Thread-Topic: Last Call Completed for EFM MIB Documents Thread-Index: AcUUUhFXG2eV01BHRgKWE9f1nOmrNgAl2P5gAACoanAABF6VgAAAsF3Q From: "Romascanu, Dan \(Dan\)" To: "Edward Beili" X-Spam-Score: 0.9 (/) X-Scan-Signature: 515708a075ffdf0a79d1c83b601e2afd Cc: hubmib@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1808068599==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============1808068599== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C51500.756FD014" This is a multi-part message in MIME format. ------_=_NextPart_001_01C51500.756FD014 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable ... which translates to 3/2 in my calendar :-) that's OK.=20 =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 17 February, 2005 4:35 PM To: Romascanu, Dan (Dan) Cc: hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents I understand. I do have a little problem and would like to postpone = comment resolution submittal till 2/30. -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, February 17, 2005 2:34 PM To: Edward Beili; hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Ed,=20 =20 Leaving some time between comments resolution and Internet-Drafts = submission is necessary for the people who submitted comments to review = the comments resolutions and react if necessary. If you have problems = with meeting 2/25 date for comments resolution, please let me know what = is the earliest date that would suit you.=20 =20 Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 17 February, 2005 2:11 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents I would suggest extending the comment resolution submittal till 3/11 and = submit the drafts with comments resolved on the next day. -Edward -----Original Message----- From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On Behalf = Of Romascanu, Dan (Dan) Sent: Wednesday, February 16, 2005 8:05 PM To: hubmib@ietf.org Subject: [Hubmib] Last Call Completed for EFM MIB Documents The EFM MIB documents completed the Working Group Last Call. A number of = technical and editorial comments were submitted against all three = documents, and a new round of Internet-Drafts followed by a shorter Last = Call period is necessary. In order to make sure that all last call = comments are addressed I would request that the editors submit a list = with the comments that were received and proposed resolution to the WG = e-mail list before submitting new Internet-Drafts. The updated MAU MIB = document can also be re-spanned and I suggest that it goes into the same = Last Call round with the three EFM MIB I-Ds. Suggested schedule: 2/25 - submit comments resolution to the WG list 3/11 (end of IETF non-submission period) - submit new round of = Internet-Drafts (all four documents) 3/25 - complete final Working Group Last Call end March - submit documents to the IESG for consideration as Proposed = Standards Please let me know if this schedule is appropriate or it causes any = problems. I am waiting for the specific confirmation from the editors. Regards, Dan ------_=_NextPart_001_01C51500.756FD014 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Last Call Completed for EFM MIB Documents
... which translates to 3/2 in my calendar :-) = that's OK.=20
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 17 February, 2005 4:35=20 PM
To: Romascanu, Dan (Dan)
Cc:=20 hubmib@ietf.org
Subject: RE: [Hubmib] Last Call Completed = for EFM=20 MIB Documents

I=20 understand. I do have a little problem and would like to postpone = comment=20 resolution submittal till 2/30.
-Edward
-----Original Message-----
From: Romascanu, Dan = (Dan)=20 [mailto:dromasca@avaya.com]
Sent: Thursday, February 17, = 2005 2:34=20 PM
To: Edward Beili; hubmib@ietf.org
Subject: = RE:=20 [Hubmib] Last Call Completed for EFM MIB = Documents

Ed,
 
Leaving some time between comments = resolution and=20 Internet-Drafts submission is necessary for the people who submitted = comments to review the comments resolutions and react if necessary. = If you=20 have problems with meeting 2/25 date for comments resolution, please = let me=20 know what is the earliest date that would suit you.=20
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 17 February, 2005 = 2:11=20 PM
To: Romascanu, Dan (Dan); = hubmib@ietf.org
Subject:=20 RE: [Hubmib] Last Call Completed for EFM MIB=20 Documents

I would suggest extending the comment = resolution=20 submittal till 3/11 and submit the drafts with comments resolved = on =20 the next day.
-Edward
-----Original Message-----
From:=20 hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On = Behalf Of=20 Romascanu, Dan (Dan)
Sent: Wednesday, February 16, = 2005=20 8:05 PM
To: hubmib@ietf.org
Subject: = [Hubmib] Last=20 Call Completed for EFM MIB Documents

The EFM MIB documents = completed the=20 Working Group Last Call. A number of technical and editorial = comments=20 were submitted against all three documents, and a new round of=20 Internet-Drafts followed by a shorter Last Call period is = necessary. In=20 order to make sure that all last call comments are addressed I = would=20 request that the editors submit a list with the comments that = were=20 received and proposed resolution to the WG e-mail list before = submitting=20 new Internet-Drafts. The updated MAU MIB document can also be = re-spanned=20 and I suggest that it goes into the same Last Call round with = the three=20 EFM MIB I-Ds.

Suggested = schedule:

2/25 - submit comments = resolution to=20 the WG list

3/11 (end of IETF = non-submission=20 period) - submit new round of Internet-Drafts (all four=20 documents)

3/25 - complete final = Working Group=20 Last Call

end March - submit = documents to the=20 IESG for consideration as Proposed Standards

Please let me know if = this schedule=20 is appropriate or it causes any problems. I am waiting for the = specific=20 confirmation from the editors.

Regards,

Dan

= ------_=_NextPart_001_01C51500.756FD014-- --===============1808068599== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============1808068599==-- From hubmib-bounces@ietf.org Fri Feb 18 04:05:21 2005 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07648 for ; Fri, 18 Feb 2005 04:05:21 -0500 (EST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D233A-0008L9-GW; Fri, 18 Feb 2005 02:59:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D22z2-0006Pd-SP for hubmib@megatron.ietf.org; Fri, 18 Feb 2005 02:55:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02101 for ; Fri, 18 Feb 2005 02:55:23 -0500 (EST) Received: from mail14a.g14.rapidsite.net ([128.121.64.70]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D23Ka-0000Hk-Rs for hubmib@ietf.org; Fri, 18 Feb 2005 03:17:45 -0500 Received: from mxw1400.sanjose14-verio.com (128.121.143.19) by mail14a.g14.rapidsite.net (RS ver 1.0.95vs) with SMTP id 2-0719063317; Fri, 18 Feb 2005 02:55:19 -0500 (EST) From: "Lior khermosh" To: "'Romascanu, Dan \(Dan\)'" , "'Edward Beili'" Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Date: Fri, 18 Feb 2005 09:56:01 +0200 Message-ID: <01cb01c5158f$4b7f7cc0$740b0b0b@passave.co.il> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: X-Loop-Detect: 1 X-Spam-Score: 0.9 (/) X-Scan-Signature: 24d000849df6f171c5ec1cca2ea21b82 Cc: hubmib@ietf.org X-BeenThere: hubmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ethernet Interfaces an Hub MIB WG List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0841851479==" Sender: hubmib-bounces@ietf.org Errors-To: hubmib-bounces@ietf.org This is a multi-part message in MIME format. --===============0841851479== Content-Type: multipart/alternative; boundary="----=_NextPart_000_01CC_01C515A0.0F084CC0" This is a multi-part message in MIME format. ------=_NextPart_000_01CC_01C515A0.0F084CC0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm O.K. with that. Lior -----Original Message----- From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan) Sent: Thursday, February 17, 2005 4:54 PM To: Edward Beili Cc: hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents ... which translates to 3/2 in my calendar :-) that's OK. Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 17 February, 2005 4:35 PM To: Romascanu, Dan (Dan) Cc: hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents I understand. I do have a little problem and would like to postpone comment resolution submittal till 2/30. -Edward -----Original Message----- From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] Sent: Thursday, February 17, 2005 2:34 PM To: Edward Beili; hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents Ed, Leaving some time between comments resolution and Internet-Drafts submission is necessary for the people who submitted comments to review the comments resolutions and react if necessary. If you have problems with meeting 2/25 date for comments resolution, please let me know what is the earliest date that would suit you. Regards, Dan -----Original Message----- From: Edward Beili [mailto:EdwardB@actelis.com] Sent: 17 February, 2005 2:11 PM To: Romascanu, Dan (Dan); hubmib@ietf.org Subject: RE: [Hubmib] Last Call Completed for EFM MIB Documents I would suggest extending the comment resolution submittal till 3/11 and submit the drafts with comments resolved on the next day. -Edward -----Original Message----- From: hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On Behalf Of Romascanu, Dan (Dan) Sent: Wednesday, February 16, 2005 8:05 PM To: hubmib@ietf.org Subject: [Hubmib] Last Call Completed for EFM MIB Documents The EFM MIB documents completed the Working Group Last Call. A number of technical and editorial comments were submitted against all three documents, and a new round of Internet-Drafts followed by a shorter Last Call period is necessary. In order to make sure that all last call comments are addressed I would request that the editors submit a list with the comments that were received and proposed resolution to the WG e-mail list before submitting new Internet-Drafts. The updated MAU MIB document can also be re-spanned and I suggest that it goes into the same Last Call round with the three EFM MIB I-Ds. Suggested schedule: 2/25 - submit comments resolution to the WG list 3/11 (end of IETF non-submission period) - submit new round of Internet-Drafts (all four documents) 3/25 - complete final Working Group Last Call end March - submit documents to the IESG for consideration as Proposed Standards Please let me know if this schedule is appropriate or it causes any problems. I am waiting for the specific confirmation from the editors. Regards, Dan ------=_NextPart_000_01CC_01C515A0.0F084CC0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
I'm=20 O.K. with that.
 
Lior
 
-----Original Message-----
From:=20 hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org] On Behalf = Of=20 Romascanu, Dan (Dan)
Sent: Thursday, February 17, 2005 = 4:54=20 PM
To: Edward Beili
Cc: = hubmib@ietf.org
Subject:=20 RE: [Hubmib] Last Call Completed for EFM MIB = Documents

... which translates to 3/2 in my calendar :-) = that's OK.=20
 

Regards,

Dan

-----Original Message-----
From: Edward Beili=20 [mailto:EdwardB@actelis.com]
Sent: 17 February, 2005 4:35=20 PM
To: Romascanu, Dan (Dan)
Cc:=20 hubmib@ietf.org
Subject: RE: [Hubmib] Last Call Completed = for EFM=20 MIB Documents

I=20 understand. I do have a little problem and would like to = postpone=20 comment resolution submittal till 2/30.
-Edward
-----Original Message-----
From: Romascanu, Dan = (Dan)=20 [mailto:dromasca@avaya.com]
Sent: Thursday, February 17, = 2005=20 2:34 PM
To: Edward Beili; = hubmib@ietf.org
Subject: RE:=20 [Hubmib] Last Call Completed for EFM MIB = Documents

Ed,
 
Leaving some time between comments = resolution and=20 Internet-Drafts submission is necessary for the people who = submitted=20 comments to review the comments resolutions and react if = necessary. If you=20 have problems with meeting 2/25 date for comments resolution, = please let=20 me know what is the earliest date that would suit you.=20
 

Regards,

Dan

-----Original Message-----
From: Edward Beili = [mailto:EdwardB@actelis.com]
Sent: 17 February, 2005 = 2:11=20 PM
To: Romascanu, Dan (Dan);=20 hubmib@ietf.org
Subject: RE: [Hubmib] Last Call = Completed for=20 EFM MIB Documents

I would suggest extending the comment = resolution submittal till 3/11 and submit the drafts with = comments=20 resolved on  the next day.
-Edward
-----Original Message-----
From:=20 hubmib-bounces@ietf.org [mailto:hubmib-bounces@ietf.org]On = Behalf=20 Of Romascanu, Dan (Dan)
Sent: Wednesday, = February 16,=20 2005 8:05 PM
To: hubmib@ietf.org
Subject: = [Hubmib]=20 Last Call Completed for EFM MIB = Documents

The EFM MIB documents = completed the=20 Working Group Last Call. A number of technical and editorial = comments=20 were submitted against all three documents, and a new round of = Internet-Drafts followed by a shorter Last Call period is = necessary.=20 In order to make sure that all last call comments are = addressed I=20 would request that the editors submit a list with the comments = that=20 were received and proposed resolution to the WG e-mail list = before=20 submitting new Internet-Drafts. The updated MAU MIB document = can also=20 be re-spanned and I suggest that it goes into the same Last = Call round=20 with the three EFM MIB I-Ds.

Suggested = schedule:

2/25 - submit = comments resolution=20 to the WG list

3/11 (end of IETF = non-submission=20 period) - submit new round of Internet-Drafts (all four=20 documents)

3/25 - complete final = Working Group=20 Last Call

end March - submit = documents to the=20 IESG for consideration as Proposed Standards

Please let me know if = this schedule=20 is appropriate or it causes any problems. I am waiting for the = specific confirmation from the editors.

Regards,

Dan

=
------=_NextPart_000_01CC_01C515A0.0F084CC0-- --===============0841851479== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib --===============0841851479==--