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

Re: [802.3_4PPOE] missed discussion before closing

Dan, thanks for the suggestion. Others should be encouraged to also take this approach. 

Chad Jones
MGR, HW ENG, Cisco Systems
Chair, IEEE P802.3bt 4PPoE Task Force

From: Dan Dove <dan.dove@xxxxxxxxxxxxxxxxxx>
Organization: Dove Networking Solutions
Date: Monday, November 2, 2015 at 12:54 PM
To: Chad Jones <cmjones@xxxxxxxxx>, 4PPOE Reflector <STDS-802-3-4PPOE@xxxxxxxxxxxxxxxxx>
Subject: Re: [802.3_4PPOE] missed discussion before closing

Hi Chad,

One thought that comes to me. For comments that are helpful, but not absolutely essential to D1.5, I plan to NOT mark them as required. This will get them into the record, but give the editor an opportunity to either address them with EZ or reject them.

Others may want to use that approach as well.

Dan Dove
Chief Consultant
Dove Networking Solutions
530-906-3683 - Mobile
On 10/29/15 1:19 PM, Chad Jones (cmjones) wrote:
I saw no replies to this email. That either means no one read it or everyone agrees. Please keep your comments to the championed topics. Make sure you write good comments to help Dave be expedient in suggested remedies. Please withhold any comments you know are controversial where you haven’t done the required consensus building. 

Chad Jones
MGR, HW ENG, Cisco Systems
Chair, IEEE P802.3bt 4PPoE Task Force

From: Chad Jones <cmjones@xxxxxxxxx>
Reply-To: Chad Jones <cmjones@xxxxxxxxx>
Date: Friday, October 16, 2015 at 4:46 AM
To: 4PPOE Reflector <STDS-802-3-4PPOE@xxxxxxxxxxxxxxxxx>
Subject: [802.3_4PPOE] missed discussion before closing

If you recall back to comment resolution on Tuesday, Dave floated the idea of holding at least a 1/2 day adhoc in Dallas to work on the State Machine. To do this, we need to limit the comments or presentations (or both) to something that will fit in 1.5 – 2 days. That is around 150 non-EZ comments and 8 presentations, based on our past meetings. Dave asked for you to think about how to limit ourselves and that we would discuss it. 

I would like to have that discussion here, since we forgot to do it in the closing business. 

One way is to insist that there are no presentations that are not addressing baseline, a remedy to a comment or something assigned to a ‘champion’ as a progress blocking topic during the closing business yesterday. Another way is to withhold comments that you know are controversial in nature where you haven’t yet completed the work to drive consensus. My last remark wold be the thing that Dave emphasized all during comment resolution. Ensure you have made a ‘good’ comment. Copy the text to which the comment refers, make extra effort to provide a concise solution.  If you can’t, save that comment for D1.5.

Anyone else have thoughts on how to minimize the comment resolution portion of Dallas to give dedicated face-to-face time for work on the State Machines?

Chad Jones
MGR, HW ENG, Cisco Systems
Chair, IEEE P802.3bt 4PPoE Task Force