Comment #1 from 802.19WG

1. Comment #1 from 802.19WG • Comment: In Section 5.2.b two examples of spectrum resource measurements are given: PER and delay.   These seem to be more network performance metrics.  Please explain the difference between spectrum resource measurements and network performance metrics. Response and Action: In an effort to provide a bit more clarity in the description, we propose that Section 5.2 in the PAR bemodified as follows (action to be done by NesCom admin): This amendment to IEEE Std 802.15.4 defines MAC related functions to enable spectrum resource management. It specifies • spectrum resource measurements and network performance metrics, such as packet error ratio, delay, etc, • information elements and data structures to capture these measurements, • procedures for collecting and exchanging spectrum resource measurement information with higher layers or other devices. Shoichi Kitazawa, ATR

2. Comment #2 from 802.19WG • Comment: Will these spectrum resource measurements provide input to the 802.19.1 coexistence model? Response: These spectrum resource measurements may be used by the 802.19.1. Action: No change needed to the PAR or CSD Shoichi Kitazawa, ATR

3. Comment from 802.11 • Comment: 1.2.4 b) need a response: b) Proven similar technology via testing, modeling, simulation, etc. Response and Action: The following has been added to1.2.4 b) in the CSD: Same as 1.2.4 a). Similar capabilities have already been deployed and demonstrated in many proprietary implementations. Shoichi Kitazawa, ATR

4. Comment #1 from 802.3 • Comment: The CSD does not respond to the question 'Describe the plan for developing a definition of managed objects.', Response and Action: The below has been added to the CSD Intended plan for developing a definition of managed objects: • Understand the common capabilities associated with spectrum resource and network performance metrics of all the PHYs currently defined in the IEEE 802.15.4-2011 plus completed amendments. Also identify and record specific unique capabilities as needed. • Where necessary, understand how to express those capabilities in a common manner, for example, if latency is such a capability then determine if it is used in a consistent manner from PHY to PHY. If not, define a mechanism to normalize. • Define a transport mechanism, like an IE. • Reduce the above to a set defined managed objects. Shoichi Kitazawa, ATR

5. Comment #2 from 802.3 • Comment: for Economic Feasibility the CSD simply states that existing 15.4 model is still valid, a pointer to that model at a minimum should be provided. Response: Reference to a 15.4 model has been removed. CSD has been modified as follows Economic Feasibility Each proposed IEEE 802 LMSC standard shall provide evidence of economic feasibility. Demonstrate, as far as can reasonably be estimated, the economic feasibility of the proposed project for its intended applications. Among the areas that may be addressed in the cost for performance analysis are the following: • Balanced costs (infrastructure versus attached stations). Since there is no added hardware costs, the existing balance remains unchanged • Known cost factors. Firmware change - no added hardware costs • Consideration of installation costs. No change to installation costs • Consideration of operational costs (e.g., energy consumption). No change to operational costs • Other areas, as appropriate. None. Shoichi Kitazawa, ATR