Re: [802SEC] Response to Commentors on 802.15 KMP PAR
The answer we really wanted is maybe. The Recommended Practice could be
implemented either way depending on trade-offs. I am inferring your counsel
is to include it as a yes even though we may not use it and if so are there
any issues of saying yes but then not needing it?
At 10:17 PM 11/9/2011 +0000, Tony Jeffree wrote:
The .15 response to 802.1's comments clearly indicates that the WG is aware
of possible registration activity, yet the revised draft PAR text answers
question 6.1b with "No". Please fix this - the right answer is, by your own
WG's admission, "Yes". The PAR form will also require an explanation to be
On 9 November 2011 21:47, Bob Heile <email@example.com> wrote:
> We received five sets of comments on the KMP PAR and 5C. They were from:
> * 802.15.6 Task Group
> * 802.11 Working Group
> * 802.21 Working Group
> * IEEE 802.1 Working Group
> * Rene Struik 802.15 voting member
> Attached are three documents, a word doc containing all the comments
> received and responses to them, a redline of the PAR and a revised copy of
> the 5C reflecting those responses. I will send a redline of the 5C once I
> track it down.
> Bob Heile, Ph.D
> Chairman, ZigBee Alliance
> Chair, IEEE 802.15 Working Group on Wireless Personal Area Networks
> Co-Chair IEEE P2030 Task Force 3 on Smartgrid Communications
> 11 Robert Toner Blvd
> Suite 5-301
> North Attleboro, MA 02763 USA
> Mobile: +1-781-929-4832
> email: firstname.lastname@example.org
> 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.
Bob Heile, Ph.D
Chairman, ZigBee Alliance
Chair, IEEE 802.15 Working Group on Wireless Personal Area Networks
Co-Chair IEEE P2030 Task Force 3 on Smartgrid Communications
11 Robert Toner Blvd
North Attleboro, MA 02763 USA
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.