| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Adrian suggests that the motion should say to whom we are making the request:According to SASB Ops Man 8.1.2, the request is made to RevCom. Perhaps the motion should also include the document that will make the request."Approve forwarding the extension request (per SASB Ops Man 8.1.2) documentation in https://mentor.ieee.org/802.16/dcn/17/16-17-0022-01.pptx to RevCom"I derived this by looking at the motion templates for forwarding PARs to NesCom and projects to RevCom to match their style. It's a little clunky as there is no short name for this kind of extension request other than referring to the SASB Ops Manual subclause that permits it. I removed other details, e.g.: that it is being done to allow completion of P802.16s as they are documented in the referenced file.---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
On Tue, May 23, 2017 at 9:59 AM, Pat Thaler <pat.thaler@broadcom.com> wrote:
Thanks Glenn, I thought we had done it before but didn't remember the details.I think it is better to have an EC motion for IEEE 802 to formally make the request even if we didn't have one last time.The wording of the motion for 802.1Q doesn't seem precise to me. There was no general requirement to complete the revision by Dec. 2008. Without the extension, it had to be completed in order to allow processing further amendments.How about?:"IEEE 802 requests approval of a two year extension (until December 2017) as allowed by Ops Man 8.1.2 to allow completion of amendment P802.16s as a fourth amendment to IEEE Std 802.16-2012."Regards,Pat
On Tue, May 23, 2017 at 7:23 AM, Glenn Parsons <glenn.parsons@ericsson.com> wrote:
Colleagues,
As background I requested what Roger is looking for in Dec 2007 … when I as an 802.1Q amendment editor.
The SASB motion was:
Whereas 802.1Q-2005 revision is currently required to be completed by Dec. 2008; and whereas significant work remains; and whereas Ops Man 8.1.2 allows for a two year extension, RevCom recommends that the SASB approve a two-year extension for the completion of a revision of 802.1Q (until December 2010).
I noticed the problem and discussed it at the November 2007 plenary but it is not in the 802.1 minutes or the EC minutes. The reference is an email report from SASB in December:
http://www.ieee802.org/1/priva
te/email2/msg07199.html And a presentation to 802.1 in January 2008 on the background and agreed SASB motion:
http://www.ieee802.org/1/files
/public/docs2008/q-parsons- extension-0108.pdf
So at the time, there was no WG or EC motion. Only a motion from me, as a member of SASB…
Cheers,
Glenn.
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Roger Marks
Sent: Monday, May 15, 2017 4:33 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] reminder: IEEE 802 EC Interim Telecon - 1-3pm ET June 6
Geoff,
The SASB procedure I cited says:
After the three-year period, RevCom shall defer consideration of additional amendments or corrigenda until a revision or a two-year extension request is approved by the IEEE-SA Standards Board.
My intention is to request the action: "two-year extension request is approved by the IEEE-SA Standards Board".
Cheers,
Roger
On May 15, 2017, 10:28 PM +0200, Geoff Thompson <thompson@ieee.org>, wrote:
Roger-
No action from Revcom should be necessary since the main standard is actively under revision.
Be that as it may, your slide set might well be useful if any questions arise.
Geoff
On May 15, 2017, at 11:02 AMPDT, Roger Marks <r.b.marks@ieee.org> wrote:
Jon,
This is explained in my file (updated to <https://mentor.ieee.org/802.1
6/dcn/17/16-17-0022-02.pptx>).
We don't need to extend a PAR. The request is going to RevCom, not NesCom. The extension is required to bypass the rule limiting standards to three amendments. With the extension, we'll be allowed to complete 802.16s as the fourth amendment soon, with the revision to follow next year.
Cheers,
Roger
On May 15, 2017, 7:44 PM +0200, Jon Rosdahl <jrosdahl@ieee.org>, wrote:
Roger,
I have added it to the agenda, and the agenda file will be posted shortly.
I would like to ask/comment:
Your Revision PAR expires 31-Dec-2021So your Revision PAR does not need an extension.
Your 16s PAR expires: 31-Dec-2020
So it does not need an extension.
It would seem perfectly normal for your group to complete the 16s and then roll it into the revision project.
So What extension are you asking the EC to vote on?
Jon
------------------------------
------------------------------ -----------------
Jon Rosdahl Engineer, Senior Staff
office: 801-492-4023 Qualcomm Technologies, Inc.
cell: 801-376-6435 10871 North 5750 West
Highland, UT 84003
A Job is only necessary to eat!
A Family is necessary to be happy!!
On Sun, May 14, 2017 at 5:04 PM, Geoff Thompson <thompson@ieee.org> wrote:
Roger-
You have a revision PAR open for your main standard.
Why not just accept a Sponsor Ballot comment to...
"integrate the P802.16s draft at its current level of approval into the P802.15rev draft"
?
Geoff
On May 11, 2017, at 9:18 PMPDT, Roger Marks <r.b.marks@ieee.org> wrote:
Pat,
Thanks for the help on this. I hadn't been able to decipher exactly when the two-year extension would begin. This is a better way to proceed.
Thanks also for the eagle-eyed review and resulting off-line comments, and to input from Bob Grow. I've posted a consequential update:
Regards,
Roger
On May 12, 2017, 3:33 AM +0900, Pat Thaler <pat.thaler@broadcom.com>, wrote:
Should the extension request state the duration of the extension or date for it to cover?
The current text says:
•An extension to allow consideration of P802.16s as the fourth amendment to IEEE Std 802.16-2012
Since the three year window ended at the end of 2015 (IEEE SA practice has been to count in full years, rather than tracking based on when during the year the standard was approved), a two-year extension covers to the end of 2017.
"An extension to the end of 2017 to allow consideration of P802.16s as the fourth amendment to IEEE Std 802.16-12."
On Thu, May 11, 2017 at 6:50 AM, Roger Marks <r.b.marks@ieee.org> wrote:
Paul,
I'd like to add:
ME 802.16-2012 extension request to RevCom
This is a request to allow consideration of a fourth amendment to the base standard. The rules permit that, if an extension is granted. The fourth amendment isn't ready to submit yet, but I'd like to get the approval in advance.
I'd like your OK to presubmit the draft request <https://mentor.ieee.org/802.1
6/dcn/17/16-17-0022-00.pptx>, per Clause 11 of the OM:
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.
OK?
Regards,
Roger
On May 11, 2017, 1:54 AM +0900, Paul Nikolich <paul.nikolich@att.net>, wrote:
Dear EC Members,
This is a reminder we will be holding our usual mid-plenary 802 Executive Committee telecon soon on Tuesday 06 June 2017. Please submit your agenda items to me, JohnD and JonR. Remember, you can place items on the consent agenda if you timely circulate the material prior to the meeting*.
The tentative list of items I have are as follows:
1) Chair announcements, Nikolich
2) EC Action Item Review, D'Ambrosia
3) July 2017 Plenary Session logistics update, Rosdahl
4) Future Venue Options update, Rosdahl
5) WG/TAG Chair motions (tbd)
...additional items to be added here...
y) EC Action Item recap from this meeting, Nikolich/D'Ambrosia
z) Adjourn
The coordinates for the call are shown below. As usual, please join the meeting 10 minutes ahead of time so we can begin promptly at 1pm ET.
Regards,
--Paul
*from the IEEE 802 Chairs Guidelines
2.16 Consent agenda
The following should be considered for inclusion on the consent agenda upon request:
1) First renewal of a Study Group (either ECSG or WGSG)
2) Public statements (e.g., press releases, responses to regulatory bodies, liaison statements, etc.) that have been announced to the EC email reflector made available to the EC members 24 hours in advance of the start of the meeting.
3) Presentation of the Tutorial schedule at the opening meeting, only if all presentations have been given to the Recording Secretary according to the guidelines.
4) Other pro-forma information items
5) Meeting minutes from previous meetings if they have been announced to the EC email reflector and distributed 1 week in advance.
------ Forwarded Message ------
From: "Jon Rosdahl" <jrosdahl@ieee.org>
Sent: 1/19/2017 8:02:16 PM
Subject: [802SEC] Fwd: IEEE 802 EC Interim Telecon - June 6
Greetings --
You have been invited to a join.me online meeting
June 6, 2017 1300-1500 Eastern -- Calendar Place holder
Save the Date
Join the meeting:https://join.me/IEEE.802.EC
On a computer, use any browser. Nothing to download.
On a phone or tablet, launch thejoin.me app and enter meeting code:IEEE.802.EC
Join the audio conference:
Dial a phone number and enter access code, or connect via internet.
Access Code 499-916-599#
By phone:
United States - Los Angeles, CA +1.213.226.1066
United States - New York, NY +1.646.307.1990
United States - Hartford, CT +1.860.970.0010
United States - Camden, DE +1.302.202.5900
United States - Tampa, FL +1.813.769.0500
United States - Washington, DC +1.202.6021295
United States - San Francisco, CA +1.415.594.5500
United States - Atlanta, GA +1.404.400.8750
Other international numbers available
By computer via internet:
Join the meeting, click the phone icon and select 'Call via internet'. A small download might be required.
Start time by time zones
---------- 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.
---------- 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.
---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.