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

Re: [802SEC] PARs Uploaded



No they can not be done in one acyion.
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!!

Sent from BlueMail
On Jun 16, 2017, at 5:38 PM, Pat Thaler <000006d722d423ba-dmarc-request@ieee.org> wrote:
An extension request has its own form. There probably isn't any benefit in combining extension and modification. There may be benefit in waiting until closer to the time the PAR runs out - e.g. July 2018.

From the NesCom conventions:
Extension Requests may be requested for a period of one to four years. Extension requests shall include sufficient information to provide reasonable confidence that the project will be completed with the additional time requested in the extension. The usual extension approval is for one to two years. When longer extensions are requested (i.e., three to four years), sufficient extenuating circumstances must be provided to justify the length of the extension.

It would be easier to provide an accurate schedule and know whether to ask for a one or two year extension once closer to Dec 2018. At that point, there would be a draft close to ready for sponsor ballot under the current schedule.

Regards,
Pat

On Fri, Jun 16, 2017 at 4:19 PM, Benjamin Rolfe <ben@blindcreek.com> wrote:

Pat points out another reason the PAR will need work before balloting on their current schedule: the PAR will expire before they can complete balloting.  Both an amendment and an extension is needed at some point - can they be done in one action?

B

On 6/16/2017 3:17 PM, Pat Thaler wrote:
We have never considered a PAR modification for pre-circulation that came to the EC from outside the Working Group. 

I've looked at the closing reports and skimmed the minutes from 802.11ax from March and May. They don't mention any discussion of PAR modification.

Furthermore, a PAR modification needs to be accompanied by a CSD so the submission is incomplete as well as late. I expect that the WG/TG reviewed whether the extension of the band affects the Technical and Economic Feasibility responses (or any other responses).

Note that the LMSC OM Proceedure for PARs includes the following:
"All PARs must be accompanied by supporting documentation, which shall include:
a) Explanatory technical background material
b) Expository remarks on the status of the development of the PAR (e.g., approved by WG,
Draft pending WG approval at next meeting, etc.)"

The schedule for 802.11ax in the closing report for March has Sponsor Ballot Pool formation in May* 2018 and starting Sponsor Ballot in November 2018. Any PAR modification that would increase scope needs to be approved by the Standards Board before sending the invitation for the Ballot Pool. Increasing the scope after that requires withdrawing the PAR and creating a new PAR. (NesCom conventions 13.) EC approval of forwarding the PAR modification in November would be more than adequate to do that even if May 2018 is when the invitation is started. 

*Is that a typo? May is early to form the ballot pool if the ballot is expected to start in November. That's 6 months. A ballot pool expires and has to be reformed if Sponsor Ballot hasn't started within 6 months of the invitation close The prior schedule had January and March - a time span that makes more sense. (2017 SB OM 5.4.2)

Regards,
Pat

On Fri, Jun 16, 2017 at 2:34 PM, John D'Ambrosia <jdambrosia@gmail.com> wrote:

Rich,

It is not clear if you are sending this to me as a PAR request that you want to present to 802.11 or something you wanted the EC to consider in July.

 

If your wish was for the EC to consider it, then you have missed the 30 day deadline.  Please refer to the text below from the IEEE 802 OM [ http://ieee802.org/PNP/approved/IEEE_802_OM_v19.pdf  ]–  

 

9.2 IEEE 802 LMSC approval

A complete  proposed PAR and, if applicable,  the criteria for standards development (CSD) statement, as described in Clause 13, shall be submitted to the Sponsor via the Sponsor email reflector for review no less than 30 days prior to the day of the opening Sponsor meeting of an IEEE 802 LMSC plenary session.  The submittal message should include Internet links to the required submittal documents.  Presence of the submittal message in the reflector archive (with time stamp) is evidence of delivery.

 

I reviewed the 802 Reflector Archive, and did not see a message prior to today’s regarding this PAR modification.

 

Regards,

 

John D’Ambrosia

Recording Secretary, IEEE 802 LMSC

 

 

 

 

From: Kennedy, Rich [mailto:rich.kennedy@hpe.com]
Sent: Friday, June 16, 2017 4:41 PM
To: John D'Ambrosia <jdambrosia@GMAIL.COM>; STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: RE: [802SEC] PARs Uploaded

 

John:

 

I have a PAR modification for P802.11ax. The document is here: https://mentor.ieee.org/802.11/dcn/17/11-17-0913-00-00ax-par-modification-to-support-6-ghz-band.docx and attached.

 

Thank you.

 

Rich Kennedy

 

Director, Global Spectrum Strategy

HPE logo

 

Board Director, Dynamic Spectrum Alliance

Chair, IEEE 802.18 Radio Regulatory Technical Advisory Group

Chair Emeritus, IEEE 802.11af WLAN in TVWS

Chair, Wi-Fi Alliance Spectrum & Regulatory Task Group

 

rich.kennedy@hpe.com

(737) 202-7014

 

From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of John D'Ambrosia
Sent: Thursday, June 15, 2017 8:27 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: [802SEC] PARs Uploaded

 

Dear WG Chairs,

I have uploaded the PARs I have received emails for.  All were from Glenn.  If I have missed any PARs by anyone, please contact me tomorrow 6/16.

 

Regards,

 

John D’Ambrosia

Recording Secretary, IEEE 802 LMSC

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