Hi Paul,
Thanks ever so much for the approval. I note however that Clause 12
includes the requirement '... provided that the Sponsor Chair first
notifies the Sponsor email reflector ....'. Based on this may I suggest
that you send the following email to the SEC reflector.
Thanks and best regards,
David
-----
Subject: IEEE P802.3br submittal to RevCom
Dear EC members,
Per out process which states a WG Chair may submit a draft to RevCom
without EC approval '.. provided that the Sponsor Chair first notifies
the Sponsor email reflector that, in the Chair's view based on the
complete RevCom package, there is a reasonable expectation that the
submittal will be approved by the Sponsor before the RevCom meeting.'.
David Law has requested I review the status of the IEEE P802.3br
project in preparation for RevCom review. I have determined there is a
reasonable expectation the attached submittal will be approved by the
EC before the next RevCom meeting and, via this email, am notifying the
EC as such. See the details below.
Regards,
--Paul
-------- Original message --------
From: "Law, David" <dlaw@hpe.com>
Date: 5/4/16 1:29 PM (GMT-05:00)
To: "Paul Nikolich <p.nikolich@ieee.org>" <p.nikolich@ieee.org>
Cc: "Adam Healey <adam.healey@broadcom.com>"
<adam.healey@broadcom.com>, "Ludwig Winkel <ludwig.winkel@siemens.com>"
<ludwig.winkel@siemens.com>, "Pat Thaler <pat.thaler@broadcom.com>"
<pat.thaler@broadcom.com>
Subject: Request for approval to submit IEEE P802.3br draft D3.1 to
RevCom
Hi Paul,
The last paragraph of Clause 12 'Procedure for Conditional Approval to
Forward a Draft Standard' states that 'Submissions may be forwarded to
RevCom without Sponsor Approval or Conditional Approval in order to
meet the submittal requirements for the next RevCom meeting, provided
that the Sponsor Chair first notifies the Sponsor email reflector that,
in the Sponsor Chair's view based on the complete RevCom package, there
is a reasonable expectation that the submittal will be approved by the
Sponsor before the RevCom meeting. If it becomes apparent that approval
will not be completed, the submittal shall be withdrawn from the RevCom
agenda as early as possible'.
Based on this provision I am requesting your approval as the Sponsor
Chair to submit IEEE P802.3br draft D3.1 to RevCom in time for the June
2016 submittal deadline of 20th May 2016. As you will see in the email
below I have announced that we received no comments on the most recent
recirculation ballot.
Since the RevCom submittal of IEEE P802.3br hasn't received IEEE 802.3
approval I expect a motion to approve this at the IEEE 802.3 Interim
meeting taking place on the evening of Thursday 26th May. Assuming that
motion passes I'll make a motion to approve RevCom submittal at the
IEEE 802 EC teleconference on Tuesday 7th June.
The full submittal package is attached in <802.3br.zip>, the 5
unresolved comments from the 2 remaining disapprove voters are attached
in <p8023br-3-0-unsatisfied-v0.pdf>.
Thanks and best regards,
David
----
From: Law, David
Sent: 02 May 2016 16:01
To: STDS-802-3@LISTSERV.IEEE.ORG
Subject: [STDS-802-3] IEEE P802.3br Interspersing Express Traffic 1st
Sponsor recirculation ballot results
Dear Colleagues,
The 1st Sponsor recirculation ballot on the amendment IEEE P802.3br
Interspersing Express Traffic closed successfully on 30th April 2016.
The ballot exceeded the required 75% for consensus to approve the
draft. Since no comments were received the additional IEEE P802.3br
interim meeting planned for 3rd May in Karlsruhe, Germany has been
cancelled. The next meeting of the IEEE P802.3br Task Force will take
place during the IEEE 802.3 interim meeting series
<http://www.ieee802.org/3/interims/index.html>.
The ballot statistics are:
143 Voters
106 Approve
2 Disapprove
11 Abstain
119 Ballots returned
83.22% Response Rate (>= 75% required)
9.24% Abstain Rate (< 30% required)
98.15% Approval Rate (>= 75% required)
Thank you to all that participated in this ballot.
David Law
Chair, IEEE 802.3 Ethernet Working Group
Ludwig Winkel
Chair, IEEE P802.3br Interspersing Express Traffic Task Force