Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] FW: [802SEC] Responses to comments on P802.3bn PAR



Howard,

Thank you, your response satisfactorily addresses my questions.

Regards,

--Paul


From: "Shellhammer, Steve" <sshellha@QUALCOMM.COM>
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Sent: Wednesday, July 18, 2012 8:44 PM
Subject: [802SEC] FW: [802SEC] Responses to comments on P802.3bn PAR

Paul,
 
               I am forwarding this to EC reflector on behalf of Howard and the Study Group.
 
Steve
 
From: Howard Frazier [mailto:hfrazier@broadcom.com]
Sent: Wednesday, July 18, 2012 5:42 PM
To: Shellhammer, Steve
Subject: RE: [802SEC] Responses to comments on P802.3bn PAR
 
The IEEE 802.3 EPoC PHY Study Group considered several different
proposals for the scope statement in the PAR. Some had a
broad scope while others had a very narrow scope. Our attempts to
narrow the scope led to concerns that potentially beneficial options
would be precluded. We settled on the statement contained in the
draft PAR as the best way of defining what the Task Force must do,
while leaving the Task Force enough freedom to define the optimal solution.
We believe that the set of project objectives provides sufficient limits on
the scope of the work to limit the development time of the standard to
the minimum possible.
 
From: Shellhammer, Steve [mailto:sshellha@qualcomm.com]
Sent: Wednesday, July 18, 2012 5:28 PM
To: Howard Frazier
Subject: FW: [802SEC] Responses to comments on P802.3bn PAR
 
 
 
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of paul nikolich
Sent: Wednesday, July 18, 2012 5:04 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: [802SEC] Responses to comments on P802.3bn PAR
 
Howard,
 
Thanks for the response. I appreciate the SG/WG uses the Project Objectives to define the operational characteristics of the project, and that partially addresses my concern, as there are a good set of quantitative requirements in the objective.
 
However, you didn't quite answer my question:
 
"...I would like to ask if the WG at least considered opportunities to narrow the scope and potentially reduce the development time, and what was the rationale for settling on the current scope?"
 
Please respond to the question.  Your perspective as SG Chair will be sufficient for my purposes (i.e., I don't expect the SG or WG to have to vote on a response) because I know you as the SG Chair will provide a reasonable approximation of the SG/WG's perspective.
 
Regards,
 
--Paul
 
 

From: John D'Ambrosia <jdambrosia@FORCE10LABS.COM>
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Sent: Wednesday, July 18, 2012 7:43 PM
Subject: [802SEC] FW: Responses to comments on P802.3bn PAR

Forwarding this email on behalf of Howard Frazier.

-----Original Message-----
From: Howard Frazier [mailto:hfrazier@BROADCOM.COM]
Sent: Wednesday, July 18, 2012 4:35 PM
To: STDS-802-3-EPOC@LISTSERV.IEEE.ORG
Subject: [802.3_EPOC] Responses to comments on P802.3bn PAR

Dear Members of the IEEE 802.3 EPoC PHY Study Group,

Attached please find two files:

frazier_01_0712.pdf is the file that we edited at during the meeting to create responses to the comments we received on our PAR and 5 Criteria documents.

P802_3bn_response_to_comments.pdf reduces the above to the comments and responses, without my additional explanatory material. This is the file which I sent to the EC.

I will post both of these to our web page.

Howard Frazier
Chair IEEE 802.3 EPoC PHY Study Group

________________________________________________________________________

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

----------
This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.


---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.