Re: [802SEC] Responses to comments on 802.15.4e draft PAR
Bob:
As an amendment, the Scope and Purpose do not have to agree with text in
the standard. IEEE SASB rules are consistent with the following.
As stated in the IEEE Standards Style Manual, 10.3.2:
"For new and revision projects, the scope of the draft standard
submitted for ballot shall match the scope of the approved PAR.
"For amendments and corrigenda, there is normally no scope in the draft
document. Therefore, on the PAR form, the scope shall state what the
amendment/corrigendum is changing."
As stated in the IEEE Standards Style Manual, 10.3.3:
"For new and revision projects, the purpose (if included) of the draft
standard submitted for ballot shall match the purpose of the approved
PAR.
"For amendments and corrigenda, there is normally no purpose in the
draft standard. Therefore, on the PAR form, the purpose shall state why
the changes are being made."
I have no problems with the modifications, but they were unnecessary.
--Bob Grow
-----Original Message-----
From: ***** IEEE 802 Executive Committee List *****
[mailto:STDS-802-SEC@LISTSERV.IEEE.ORG] On Behalf Of Bob Heile
Sent: Wednesday, November 14, 2007 12:37 PM
To: STDS-802-SEC@LISTSERV.IEEE.ORG
Subject: [802SEC] Responses to comments on 802.15.4e draft PAR
EC Colleagues:
Comments were received from one person on the 802.15.4e PAR . There were
no
comments on the 5C. The revised documents are available at
http://ieee802.org/15/pending.html. These changes were approved by the
Working Group by a vote of 55/0/2
The comments received on the 802.15.4e PAR were editorial in nature.
They
were:
From: "Ronald C Petersen" <r.c.petersen@ieee.org>
5.2 Scope: The scope on the PAR should appear exactly as it will appear
in
the published standard. Consider revising the scope to describe what the
standard covers rather than what it will cover or what will be
considered.
5.4 Purpose: If the standard has a purpose clause, it should appear on
the
PAR exactly as it will appear in the published standard, i.e., the
purpose
of the standard rather than what the purpose of the proposed standard
will be.
Response to the above two comments was to recast the tense of the scope
and
purpose.
5.2 Scope of Proposed Standard: The intent of this amendment is to
enhance
and add functionality to the 802.15.4-2006 MAC to a) better support the
industrial markets and b) permit compatibility with modifications being
proposed within the Chinese WPAN.
Specifically, the MAC enhancements are limited to:
* TDMA: to provide a)determinism, b)enhanced utilization of
bandwidth
* Channel Hopping: to provide additional robustness in high
interfering environments and enhance coexistence with other wireless
networks
* GTS: to increase its flexibility such as a) supporting peer to
peer,
b)the length of the slot, and c) number of slots
* CSMA: to improve throughput and reduce energy consumption
* Security: to add support for additional options such as
asymmetrical
keys
* Low latency: to reduce end to end delivery time such as needed
for
control applications
5.4 Purpose of Proposed Standard: This functionality facilitates
Industrial
applications (such as addressed by HART 7 and the ISA100 proposed
standards), and those enhancements defined by the proposed Chinese WPAN
standard that aren't included in TG4c.
This amendment addresses coexistence with wireless protocols such as
802.11, 802.15.1, 802.15.3, and 802.15.4.
Bob Heile, Ph.D
Chairman, ZigBee Alliance
Chair, IEEE 802.15 Working Group on Wireless Personal Area Networks
11 Louis Road
Attleboro, MA 02703 USA
Mobile: +1-781-929-4832
email: bheile@ieee.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.