| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Roger Thanks much, I will update the PARs web page to reflect this. James Gilb On 11/05/2011 08:13 AM, Roger Marks wrote:
Sure: Proposed Modification to P802.16n PAR http://ieee802.org/16/docs/#11_0030 Continues project to amend IEEE Std 802.16. Proposed P802.16.1a PAR http://ieee802.org/16/docs/#11_0031 Starts project to amend IEEE Std 802.16.1, based on existing P802.16n. Proposed Modification to P802.16p PAR http://ieee802.org/16/docs/#11_0032 Continues project to amend IEEE Std 802.16. Proposed P802.16.1b PAR http://ieee802.org/16/docs/#11_0033 Starts project to amend IEEE Std 802.16.1, based on existing P802.16p. Roger B. Marks<roger@consensii.com> Consensii LLC<http://consensii.com> On 2011/11/05, at 01:24 AM, James P. K. Gilb wrote:Roger OK, can you give me a short note one which new PAR applies to which part of the new .16 split? James Gilb On 11/02/2011 03:44 PM, Roger Marks wrote:Pat, Yes, this is right. Two existing amendment PARs are being split because the base standard was split. This was noted in the announcement: <http://ieee802.org/secmail/msg14123.html> I'll bring your comment to the 802.16 WG for review. Thanks, Roger Roger B. Marks<roger@consensii.com> Consensii LLC<http://consensii.com> Chair, IEEE 802.16 Working Group on Broadband Wireless Access<http://WirelessMAN.org> On 2011/11/02, at 12:08 PM, Pat Thaler wrote: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.---------- 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.