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

Re: [802SEC] PARs



If I recall correctly, those were for work that needed to amend both 802.16.1 and 802.16 so one standards effort needed two amendment PARs. However, I think they should have a small difference in scope that indicates what part of the work is being done in that amendment. E.g. when we needed an amendment to 802.1Q and 802.3 to do PFC, the scope for the 802.3 amendment specified that it was to add the MAC control frame for PFC. 

Pat

-----Original Message-----
From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of James P. K. Gilb
Sent: Wednesday, November 02, 2011 10:05 AM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: Re: [802SEC] PARs

All

Sorry about that, I finally got around to updating the page.

However, I am confused about Roger's PARs, perhaps he can explain them.

802.16.1b and 802.16p seem to cover the same scope.  Likewise,802.16.1a 
and 802.16n are also the same scope.

I assume that what is really happening is that one PAR is replacing the 
other, but then that doesn't make sense really either.

James Gilb

On 11/01/2011 07:42 AM, Tony Jeffree wrote:
> I notice that the PARs page  shows no PARs under consideration for
> November, but I'm sure I have seen one or two whizz by on the exploder.
> Does anyone have a definitive list?
>
> Regards,
> Tony
>
> ----------
> 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.