# Main

Comment:
Currently, there are no references to communication behavior and security associations with child and neighbor piconets.

SuggestedRemedy:
Incorporate communication behavior and security associations with child piconets and neighbor piconets.


Comment:
Add the following (informative) paragraph hereafter:"First, however, we give a general overview.The system comprises of ordinary devices, a single piconet controller, and a fixed external trusted party (see the mapping of roles to devices as defined in 10.3.2.2). The piconet controller acts as the security manager of the operational network. As such, it authenticates devices that would like to join the piconet and facilitates the distribution of data keys, to be used for securing communications between devices in the piconet. In addition, it allocates time slots for these message exchanges to each piconet device (see the role model of 10.3.2.1). Finally, it enforces the security rules as formulated in 10.3.3. Device authentication and the initial establishment of keying material are based on public key techniques. Evidence regarding the authenticity and validity of these public keys is corroborated via the external trusted party, who facilitates the generation of authentic public keying material for each device and the verification hereof during system operations (see 10.3.1.3 and 10.3.2.1). The role of the external trusted party is limited to the system initialization phase." Comment: this informative text illuminates some of the design rationale behind the current security architecture and should prove useful, esp. to non-specialists.


# TypeList

TypeList:
[CommentType] In("TR") AND [ResponseStatus] Not In("C", "Z")


TypeList:
[CommentType] = "TR" AND [ResponseStatus] = "W"  AND [CommentStatus] In ("A","R")

Header:
Thank you for your participation in the recent IEEE 802.3ae ballot. We have received your ballot.
not yet received an email from you confirming your reaction to the committee's 
proposed responses to your comments. Please take the time to let us know, 
for each item, whether each response, in your judgement, satisfactorily 
resolves your comment(s). 

If you would like, you may simply insert the word APPROVE, or DISAPPROVE, 
next to each comment and return this file.  That is all that is required.

In those instances where you indicate that you APPROVE or DISAPPROVE the committee's 
proposed response, our records will be updated. In those instances where you 
do not indicate a response, your vote will stand as previously submitted.

Thank you for your assistance.

Sincerely,
Dr. Howard Johnson, 
Chief Technical Editor of IEEE P802.3z Gigabit Ethernet

----**<copy of proposed committee responses attached>**----
>
>


TypeList:
[CommentType] In ("T","E") AND [CommentStatus] In ("A","R") AND [ResponseStatus] In ("W")

Comment:
The report "close T and E" will change these response statuses to "C"


TypeList:
[CommentType] In("TR") AND [ResponseStatus] Not In ("C","Z")


