1. Project: IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: [Resolutions for CID 85, 86, and 87]
Date Submitted: [17 Mar 2016]
Source: [Andrew Estrada] Company [Sony]
Address [San Diego, CA, USA]
Voice:[ ],
Re: [Proposed comment resolutions]
Abstract: [Material submitted to resolve comments 85, 86, and 87]
Purpose: []
Notice: This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P

2. What is a piconet?
Piconet appears over 1000 times in the base standard
1 or more devices.
Piconet implies a relationship between devices
Parent, child, and neighbor piconets
Requirements apply to devices, not on the piconet. Piconet behavior is determined by devices.

3. What is a DEV? DEV appears over 2000 times in the base standard
DEV = independent data device.
Don’t really want to change every occurrence of DEV in the base standard.
DEV might take on the role of PNC.

4. Why pairnet?
Pairnet is used as a way to clarify the device relationships.
Pairnet = 2 associated devices.
Pairnet = a special case of a piconet.
Pairnet would be helpful, but keep the definition very generic.

5. Proposal
Use pairnet to help the reader distinguish between existing piconet relationships.
HRCP DEV = an independent data device capable of participating in a pairnet.
HRCP PNC = a role that enables an HRCP DEV to coordinate the pairnet.
Future standards (3d) can define new terms, THZ DEV and THZ PNC for new types of devices that can form a pairnet.