Re: [802.3_DIALOG] Amendment order
David,
Thanks so much for your response and rationale.
The P802.3cs timeline is clearly in need of update. Looking at my spreadsheet that I shared, I clearly lost the fact that cs was months behind on entry into WG ballot. I would hope they can move as fast as the P802.3ck timeline. The current P802.3cs timeline is pretty aggressive for ballot periods and slipping on entry into WG ballot doesn’t lend confidence in them meeting aggressive WG and SA ballot periods and P802.3cs ballot periods are quire achievable.
I personally have trouble believing timelines until the TF gets to WG ballot, so both P802.3cs and P802.3ck planning on requesting WG ballot is an important item to consider that supports your assigning them amendment numbers. Thanks for that piece or information. That though still leaves me wondering why you assigned P802.3cw an amendment number at this time.
For the rest of us in TF review or baseline adoption, the projects with aggressive timelines (four and five month ballot periods) IMHO have credibility challenges. So, I’ll leave it to P802.3cw, P802.3cx, and P802.3db to make their cases if they believe they really are going to beat P802.3ck, or that they believe P802.3ck will finish earlier than the timeline says. (As you noted, being at RevCom at the same time as P802.3ck would be fine).
—Bob
.
> On Feb 3, 2021, at 2:23 PM, Law, David <dlaw@xxxxxxx> wrote:
>
> Hi Bob,
>
> My IEEE P802.3ct then IEEE P802.3cp order is more based on IEEE P802.3ct being in 1st Standards Association ballot comment resolution, yet IEEE P802.3cp won't complete initial Standards Association ballot until 21st February 2021. And an IEEE P802.3ct then IEEE P802.3cp order would not prevent both being on the same RevCom agenda, should IEEE P802.3cp be able to catch up.
>
> With regards to IEEE P802.3cs and IEEE P802.3ck, I understand that both IEEE P802.3cs and IEEE P802.3ck are working towards seeking approval to proceed to Working Group ballot at the March 2021 plenary, hence why I'm listing them. The revision can be inserted at any point in the list, it would just reset the amendment number, but not change the order.
>
> Best regards,
> David
>
> -----Original Message-----
>
> From: ROBERT GROW <bobgrow@xxxxxxx>
> Sent: 03 February 2021 19:25
> To: Law, David <dlaw@xxxxxxx>
> Cc: IEEE 802.3 WGAC <stds-802-3-wgac@xxxxxxxx> <STDS-802-3-WGAC@xxxxxxxxxxxxxxxxx>
> Subject: Re: Amendment order
>
> David,
>
> I assume your P802.3ct then P802.3cp order is based on the comment volume, but I believe ct has a tough terminology problem to work out. For me, these two are too close to call, but they do need an order for SA recirculations. So, I trust your judgement on this close call.
>
> I do though question making the call on P802.3ck and P802.3cw right now. The revision is scheduled to finish before either to them. I also see on Adam’s revision timeline that P802.3cx and P802.3db are also scheduled to finish one month after the revision (P802.3ck has the latest approval date of the four on their timelines). These four projects could be the first four amendments to IEEE Std 802.3-20xx, or if we slip the revision, then they could all be amendments to IEEE Std 802.3-2018.
>
> Is their something you have gotten from ck and cw that raise your confidence that they will beat the revision?
>
> —Bob
>
>> On Feb 3, 2021, at 4:58 AM, Law, David <dlaw@xxxxxxx> wrote:
>>
>> Dear WGAC,
>>
>> I've been looking at the progress of our amendment projects, with respect to the amendment order. IEEE P802.3cp is currently in initial Standards Association ballot closing on 21st February 2021, IEEE P802.3ct has just completed its 1st Standards Association recirculation ballot receiving 99 comments, and IEEE P802.3cv is just about to start its 1st Standards Association recirculation ballot having received 20 comments on initial ballot.
>>
>> Based on this it seems that it is likely IEEE P802.3ct and IEEE P802.3cv will be submitted to RevCom before IEEE P802.3cp, and that IEEE P802.3cv may be submitted before, or at the same time as, IEEE P802.3ct. Based on this I believe that we should revise the amendment order to the following:
>>
>> Amendment 8: IEEE Std 802.3ch-2020 Published
>> Amendment 9: IEEE Std 802.3ca-2020 Published
>> Amendment 10: IEEE Std 802.3cr-20xx Recommended for approval by RevCom
>> Amendment 11: IEEE Std 802.3cu-20xx Recommended for approval by RevCom
>> Amendment 12: IEEE Std 802.3cv-20xx Draft D3.1
>> Amendment 13: IEEE Std 802.3ct-20xx Draft D3.1
>> Amendment 14: IEEE Std 802.3cp-20xx Draft D3.0
>> Amendment 15: IEEE Std 802.3cs-20xx Draft D1.4
>> Amendment 16: IEEE Std 802.3ck-20xx Draft D1.4
>> Amendment 17: IEEE Std 802.3cw-20xx Draft D0.9
>>
>> Please let me know if you have any comments.
>>
>> Thanks and best regards,
>> David
>>
>> ________________________________________________________________________
>> To unsubscribe from the STDS-802-3-WGAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-WGAC&A=1
>
>
> ________________________________________________________________________
> To unsubscribe from the STDS-802-3-DIALOG list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-DIALOG&A=1
________________________________________________________________________
To unsubscribe from the STDS-802-3-DIALOG list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-DIALOG&A=1