Re: [STDS-802-3-EPOC] updated technical decisions on web site
IEEE does not write specifications, rather, it creates international standards.
CableLabs creates specifications for the North American cable industry. For a CableLabs specification to become an internatinoal standard, it would have to go through both the ANSI process (likely SCTE) and then an international standards process. These would easily tack on a few years. With that perspective, the IEEE process looks quick.
dj
From: Salinger, Jorge [mailto:Jorge_Salinger@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, March 27, 2013 11:01 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-3-EPOC] updated technical decisions on web site
Dear EPoC TF colleagues,
I know I was not able to attend the meeting last week to comment on the new timeline, so I recognize that in some way this a Monday quarterbacking comment. But, I can't help but express my frustration with the IEEE Spec process. According to this new schedule the standard will now take almost 3 years! If you just counted the time from the TF to the Sponsor Ballot, as I heard from many that we should count, this is still just shy of 2 years. I believe that things won't happen any faster than the schedule shows, and further believe that they will quite possibly take longer.
By comparison, the DOCSIS 3.1 spec, which I believe to be quite more complex, will take about 1 year from start to finish. In fact, as things look we'll likely have Certified products before the EPoC standard is completed.
I think I have heard all the reasons why the IEEE standards take as long as they do (e.g., open process, better specs, its people and not companies that contribute and vote, etc., etc.). But, this process just does not keep with the pace of our times. There is got to be something that can be fundamentally changed in the IEEE standard process to make it more streamlined.
I would really like to look into what can be done, discuss options, and see if we can find a way to improve on the timeline. And I have some thoughts about this already, some of which It hope we could be applied already, now, for EPoC.
So, if I am not the only one wanting to get the process to improve its velocity, then I would be the first to volunteer to try to do so.
Regards,
Jorge
From: Mark Laubach [mailto:laubach@xxxxxxxxxxxx]
Sent: Thursday, March 21, 2013 3:21 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx<mailto:STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-3-EPOC] updated technical decisions on web site
Dear IEEE P802.3bn EPoC PHY Task Force participants,
Based on the technical motions approved at this meeting (28 motions), the list of technical decisions on our website has been updated to include each of these motions. Please see:
http://www.ieee802.org/3/bn/public/decisions/decisions.html
In addition, the Task Force timeline was updated as of today. Please see:
http://www.ieee802.org/3/bn/public/tf_timeline_updated_130321.pdf
Yours truly,
Mark Laubach, Chair,
IEEE P802.3bn Task Force
Broadband Communications Group
Broadcom Corporation
1351 Redwood Way
Petaluma, CA, 94954
[broadcom.jpg]
Tel: +1.707.792.9093
Cell: +1.650.996.2219
________________________________
<="" p="">
________________________________
<="" p="">
________________________________________________________________________
To unsubscribe from the STDS-802-3-EPOC list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-EPOC&A=1
