| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
I looked at the PAR for 802.3bx: http://www.ieee802.org/3/bx/P802.3_PAR.pdf and this is what they list: IEEE Std 802.3-2012 will need to have a revision initiated by 2015 to allow consideration of future amendments per standards board policies. This Revision will include the merge of IEEE Std 802.3bk-2013, IEEE Std 802.3bj-2014 and accumulated maintenance changes. It is also expected to include IEEE Std 802.3bm-201x. Because there are multiple other amendments in the "pipeline", it will be desirable to complete this revision by 2015 to provide a solid base for sponsor balloting of other approved amendment projects. These schedule considerations require that new capabilities or functional enhancement will have to be deferred to a future amendment project to avoid delaying approved and current proposed new projects. I think this is pretty much in line with what we already have. Perhaps the words differ a bit but at the end of the day it is the same need for the project. Regards Marek From: stds-1904-rmtf@xxxxxxxx [mailto:stds-1904-rmtf@xxxxxxxx] On Behalf Of Glen Kramer Curtis, This field was filled automatically with the text from the original 1904.1 PAR. But good question. I will double check with IEEE-SA. Glen From: Curtis Knittle [mailto:C.Knittle@xxxxxxxxxxxxx] Glen, The only question I have is related to 5.5 Need for the project. Is it necessary to indicate a need to revise an existing standard based on maintenance requests? Regarding an online vote, I support anything we can do to get things moving quicker. Curtis From: stds-1904-rmtf@xxxxxxxx [mailto:stds-1904-rmtf@xxxxxxxx] On Behalf Of Glen Kramer Dear Colleagues, I have updated the draft 1904.1 revision PAR based on the suggestions at the meeting. The updated version with changes highlighted is posted here: http://www.ieee1904.org/revision/meeting_archive/2014/12/rmtf_1412_kramer_1a.pdf I am thinking it would be safer to conduct an online vote to approve this PAR rather defer it to our meeting in February. The upcoming NesCom submission deadlines are 19 December 2014 and 13 February 2015. We won’t be able to make the December deadline, as we need two weeks to conduct an online vote. For the 13 February 2015 deadline, we could do it at the meeting, but it may not leave enough time to conduct the required Sponsor’s vote (two weeks if done electronically). Please, reply on the reflector if you have any questions or further suggestions for the draft RAP and also if you have any feedback regarding the approval process. Regards, Glen |