| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
All
For better or worse, there is no rule that says a PAR notification expires at the end of a plenary. Hence, you can announce a PAR 5 months in advance of the plenary session and it would meet the 30 day rule.
The relevant rule is in the OM, 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."
and later in 9.3 Plenary review:
"Prior to the start of the IEEE 802 LMSC session, draft PARs and CSDs under consideration for approval by the Sponsor shall be available at a publicly accessible URL and an email sent to the Sponsor reflector should contain the URLs required for viewing the PAR and associated documentation."
James Gilb
On 11/05/2017 07:24 PM, Glenn Parsons wrote:
On Wed, Nov 1, 2017 at 1:59 PM, Paul Nikolich <paul.nikolich@att.net<mailto:Jon and EC colleagues,
This PAR was pre-submitted for July and commented on extensively. I believe the WGs have had time to review this YANG PAR.
The 802.1 WG needed time to address the comments appropriately and deal with myProject issues -- as I have documented:
http://www.ieee802.org/1/files/public/docs2017/cv-draft-PAR- history-1017-v01.pdf
There are no explicit rules allowing or disallowing continuation of the PAR review process across plenaries, so I agree that it is debatable. As a result, I requested for this to be considered “at the discretion of the Sponsor Chair” so that the work can progress.
Cheers,
Glenn.
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Jon Rosdahl
Sent: Wednesday, November 01, 2017 7:34 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] 802.1CBcv PAR revision for November consideration
HI Paul,
I would disagree with you for 4 the reasons I stated in the earlier email,
but to recap, even though this is a re-posting, it should have been posted to give the WG sufficient time.
The rule for 30 day is in place to give folks time to review (whether they do nor not, that is not part of the rules).
Glen posted to the Reflector on Oct 18, but the deadline was Oct 6.
As directed, I will add P802.1CBcv to the List of PARs that 802.11 will review next week, but it is definitely not posted in a timely manner.
We do not have "continuation" of the PARs in our rules.
I would ask James to check, but I think I am correct.
Regards,
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!!
paul.nikolich@att.net >> wrote:
Dear EC Members,
I discussed the below with Glenn.
Please recall he submitted the original version for consideration at the July 2017 plenary session, they received comments on the original version, have been working (slowly) on incorporating changes based on the comments into a revision. Therefore, I don't consider this revised version of the original July version as a 'new' submission, but a continuation of consideration of the origninal July version, hence I will allow it to be considered at the November plenary session.
Regards,
--Paul
------ Original Message ------
From: "Glenn Parsons" <glenn.parsons@ericsson.com<mailto:glenn.parsons@ericsson.co From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org<m >>
To: STDS-802-SEC@listserv.ieee.org<mailto:STDS-802-SEC@listserv. ieee.org >
Cc:
Sent: 10/31/2017 11:59:47 AM
Subject: Re: [802SEC] 802.1CBcv PAR revision for November consideration
Colleagues,
There were further issues with myProject that has delayed my follow-up on this.
I have provided a history of the original pre-circulation in July, the responses to the comments and the myProject delay here:
http://www.ieee802.org/1/files/public/docs2017/cv-draft-PAR- history-1017-v01.pdf
To continue to progress this proposed amendment, I would like the EC to consider this PAR & CSD revision in November as a follow-on to the initial PAR pre-submitted in July.
The PAR for approval (updated based on the July comments and now with no Purpose clause) is:
http://www.ieee802.org/1/files/public/docs2017/cv-draft-PAR- 1017-v03.pdf
The CSD for approval (updated based on the July comments) is:
http://www.ieee802.org/1/files/public/docs2017/cv-draft-CSD- 0917-v01.pdf
Cheers,
Glenn.
mailto:STDS-802-SEC@ieee.org>] On Behalf Of Glenn Parsons
Sent: Wednesday, October 18, 2017 9:09 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG<mailto:STDS-802-SEC@LISTSERV. IEEE.ORG >
Subject: [802SEC] 802.1CBcv PAR revision for November consideration
Colleagues,
You may recall that 802.1 had provided a new PAR proposal in July for P802.1CBcv.
As a result of a number of comments on the PAR, as well as a delay with base standard approval, the 802.1 WG decided to defer approval from July to November.
IEEE Std 802.1CB has only recently been approved and the myProject database is now updated to allow PAR creation.
As a result, I would like to propose a revision to this PAR as a follow-on to the initial PAR pre-submitted in July for the November plenary.
The revised PAR and CSD are:
http://ieee802.org/1/files/public/docs2017/cv-draft-PAR-0917 -v02.pdf
http://ieee802.org/1/files/public/docs2017/cv-draft-CSD-0917 <http://ieee802.org/1/-v01.pdf files/public/docs2017/cv- >draft-CSD-0917-v01pdf
I would like to have this PAR considered for November approval.
Cheers,
Glenn.
--
Glenn Parsons - Chair, IEEE 802.1
glenn.parsons@ericsson.com<mailto:glenn.parsons@ericsson.com >
+1-613-963-8141<tel:(613)%20963-8141>
---------- 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.