RE: Status, last call, meeting in San Diego

Edward Beili <[email protected]>
Newsgroups gmane.ietf.hubmib
Message-ID <[email protected]>
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:[email protected]]
Sent: Thursday, 06 May, 2004 01:24 PM
To: [email protected]
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.