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

Re: [802SEC] *** 10 Day EC Email Ballot *** Higher Speed Ethernet Consensus" Industry Connections



David-

I understand that you very carefully considered your position on this.

I am badly disappointed that only one Working Group chair voted against this.
I think it is a very bad precedent on a procedural basis.
I have no doubt that this particular item would pass were it considered in the proper way which is with a WG vote behind it.

My opinion is that Sponsor approval of an Industry Connections group creation is procedurally equivalent to the approval of a PAR. This is true because by Industry Connection rules (as closely as I have been able to determine) an Industry Connection group is fully empowered to write a PAR (for a project outside of 802) and submit that PAR directly to NESCOM and that SASB without any further oversight from 802.

I don't think there is anything wrong with 802 considering this outcome for an 802 activity. I am just of the opinion that such a decision about an 802 activity is equivalent to a PAR decision and should be handled in the same manner.

Therefore, I am hereby requesting an agenda item at the Sunday rules meeting to consider wording additions to our P&P to clarify this matter.

Sincerely,

    Geoff Thompson

On 37//12 2:47 AM, Law, David wrote:
All,

I ABSTAIN.

I want to start with a disclosure. As John has already made you aware the oversight of the IEEE-SA Industry Connections (IC) program has recently moved from the IEEE-SA Board of Governors (BoG) to the IEEE-SA Standards Board (SASB) and as a result of this a new committee of the SASB has been set up, the IEEE-SA Industry Connection Committee (ICCom). Hence on the basis of full disclosure I there want to let you know I have been appointed a member of that committee.

The IEEE-SA Industry Connections (IC) program is a new tool that the IEEE-SA is making available under both the entity and individual process, both where there is an existing sponsor, and also where there is not. As I stated during the discussions of the IEEE 802.3 Bandwidth Assessment activity I believe that the use of the IC program by IEEE 802 has to be considered as an additional tool complementary to our existing processes - and not as a replacement to anything else we choose to do. That being said, there are currently no rules or policy within IEEE 802 in respect to what we can use the IC program for, or how we approve a proposed IEEE 802 IC activity.

I am not an appointed member of IEEE 802 EC - I am instead a member of the IEEE 802 EC through my election as IEEE 802.3 WG chair - so I will state that when asked to second this motion I chose not to as I did not want to imply a Working Group endorsement where it did not exist - from this position you can tell I have sympathy for the position that Pat and Geoff have expressed. I have to however balance this with the fact that at the request of John I sent an email to the IEEE 802.3 Working Group that he was requesting formation of this IC activity - and while this is not the same as taking a vote - nor have a majority of voting members expressed an opinion on the matter - I believe all that responded with the exception of two objections based on process supported the need to start an activity to allow discussion of this matter.

I am therefore choosing to abstain on this matter.

Best regards,
   David

------

From: John D'Ambrosia
Sent: Friday, June 22, 2012 3:25 AM
To: IEEE 802 SEC<stds-802-sec@ieee.org>
Subject: *** 10 Day EC Email Ballot *** Higher Speed Ethernet Consensus" Industry Connections

All,
Paul as authorized me to conduct a 10-Day e-mail ballot on the following motion
This will be a 10-day ballot, closing on 02 July 2012 AOE;
as per current P&P I will terminate the ballot early if it is clear that the outcome has been decided.

Thank you for your support

John


Motion:
The IEEE 802 LMSC endorses John D'Ambrosia to work with the Industry Connections program to develop appropriate approval documentation for a 12 month program for "Higher Speed Ethernet Consensus" with the expectation that oversight would be delegated to IEEE 802.3 Chair.

Moved: D'Ambrosia                       Second: Gilb

________________________________________________________

Background:
In November 2010, the IEEE 802 EC passed the following motion:

The IEEE 802 LMSC supports development of Industry Connections activities and charters John D'Ambrosia to work with the Industry Connections program to develop appropriate approval documentation for an 18 month pilot program for "Ethernet Wireline Bandwidth Needs" with the expectation that oversight would be delegated to IEEE Chair 802.3.

The IEEE 802.3 Ethernet Bandwidth Assessment Ad Hoc has now completed seeking and considering all comments on its draft report and, as there no further substantive comments been received on the report, will be seeking Working Group approval of the report at the IEEE 802.3 closing plenary of Thursday afternoon of the July Plenary.  Additionally, a tutorial, sponsored by David Law, presenting the finding of the ad hoc is scheduled for the second tutorial slot on Monday night of the plenary week.

In parallel I have been working with a group of approximately 60 individuals on a new "Higher Speed Ethernet Consensus" Industry Connections  (HE IC) activity.  The proposed scope of the activity would be to focus on building consensus related to the next speed of Ethernet for wireline applications, which will be used for the evaluation and possible development of a Call-For-Interest for the next Higher Speed Study Group. At the IEEE 802.3 May Interim I spoke at most of the Task Force and Study Group meetings (all but MIBs and Maintenance) regarding the future after the IEEE 802.3 BWA. In addition, I had already requested time at the July opening agenda to give the 802.3 WG an update,

An ICAID proposal was submitted to the Industry Connections Committee (ICCom) for conditional approval at its June 8th meeting. At that time I anticipated bringing a motion to the 802 EC for endorsement at the July plenary. However, ICCom postponed recommending its approval until it has been endorsed by the 802 (the sponsoring group), and it was indicated that ICCom will schedule a teleconference the Monday after the plenary (assuming 802 endorsement), which could then be submitted for a 10 day standards board email ballot.
In parallel, I have been working on a press release related to the completion of the assessment.  In discussions with the IEEE PR people, it was asked about follow-up activities related to the BWA.  The new HSE IC proposal was discussed, and a single press release covering the completion of the BWA and the formation of the new group (assuming necessary approvals) was recommended.  Assuming the necessary approvals of the new IC activity and the approval of the press release by the 802 EC in July, the PR was scheduled for release on July 30.  Assuming the necessary approvals the first meeting of the new IC activity would be planned for the IEEE 802.3 September Interim meeting to be held in Geneva, Switzerland.  This would also correspond to a joint workshop between the IEEE and ITU-T.  This press release would help to raise awareness of this new Industry Connections Activity, and its first meeting at the September Interim, which would help to drive industry participation fro!
m !
  all stakeholders.

Delaying the necessary approvals of the IC activity pushes back the release of the press release into August.  Due to August vacations, the IEEE PR people suggested that the press release be held off until late August / early September.  This would minimize the effectiveness of the press release, and subsequently the industry participation.

---------- 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.