22090140040000meetingminutesofthesecurityandmanagementplaneproceduresadhocsWord格式文档下载.docx

1、AddressPhoneemailApurva ModyBAE SystemsP.O. Box 868, MER 15-2350, Nashua, NH 03061-0868603-885-2621404-819-0314apurva.mody, apurva_modyRanga ReddyUS Army （CERDEC）Ft Monmouth, NJ-Ranga.reddyus.army.milTom KiernanThomas.kiernanus.army.milAbstractThis document provides the minutes of the Security Ad-Ho

2、c conference calls held on, Year 2009 August 3rd, August 10th, August 17th, August 24th, August 31st 2009Notice: This document has been prepared to assist IEEE 802.22. It is offered as a basis for discussion and is not binding on the contributing individual（s） or organization（s）. The material in thi

3、s 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 grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any

4、 modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEEs name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEEs sole discretion to permit others to reproduce in whole or in part the resulting IEEE Stan

5、dards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.22.Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures , including the statement IEEE standards may include the known use of pat

6、ent（s）, including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard. Early disclosure to the Working Group of patent information that might be releva

7、nt to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology （or technology

8、under patent application） might be incorporated into a draft standard being developed within the IEEE 802.22 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at .1. August 3rd 2009 Security Ad-Hoc Conference Call Meeting MinutesMeeting Minutes 1. AttendanceApurva

9、 Mody BAE SystemsGerald Chouinard - CRCRanga Reddy US ArmyWinston Caldwell Fox2.1 Agenda Attendance Chair asked if everyone attendingwasfamiliar with the IEEE patent policy - http:/standards.ieee.org/board/pat/pat-slideset.pdf - Everyone was familiar. Minutesof all the Security Ad-Hoc Conference Cal

10、lspreviously heldcan be found at https:/mentor.ieee.org/802.22/dcn/08/22-08-0163-22-0000-meeting-minutes-of-the-security-ad-hoc-group-in-802-22.doc Discussion on Protection Mechanisms for Co-existence Beaconing Packets led by Ranga Reddy. https:/mentor.ieee.org/802.22/dcn/08/22-08-0296-03-0000-cbp-s

11、ecurity-protection-mechanisms.doc Recommended Text for Section 7 on Security in 802.22 included in Draft v 2.0 can be found at https:/mentor.ieee.org/802.22/dcn/08/22-08-0174-18-0000-recommended-text-for-section-7-on-security-in-802-22.doc Reference Document - Table of Contents for Section 7. The re

12、ference document for the proposed text can be found athttps:/mentor.ieee.org/802.22/file/08/22-08-0165-00-0000-table-of-content-for-the-security-section-in-802-22.doc Reference Document - Scope and the Workplan for the Security Ad-Hoc Group https:/mentor.ieee.org/802.22/file/08/22-08-0159-00-0000-sc

13、ope-agenda-workplan-and-timeline-for-the-security-ad-hoc-in-802-22.doc Reference Document - Presentation on the PRM and Security Enhancements in 802.22 802.22 Threat Analysis/mentor.ieee.org/802.22/dcn/08/22-08-0083-08-0000-security-and-prm-enhancements-in-80222-v3.ppt Proposed Reference Architectur

14、e for 802.22 - https:/mentor.ieee.org/802.22/dcn/08/22-08-0121-10-0000-text-on-protocol-reference-model-enhancements-in-802-22.doc 802.22 Database Interface Architecture and Security Mechanisms - https:/mentor.ieee.org/802.22/dcn/09/22-09-0111-02-0000-database-interface-architecture-and-security-mec

15、hanisms.ppt Whitespace Database Service - https:/mentor.ieee.org/802.19/dcn/09/19-09-0047-00-tvws-white-spaces-database.pptMinutes and Discussions Comments 667, 668, 673, 674, 675, 676, 679 and 680 were resolved. The proposed resolutions can be found in the Document https:/mentor.ieee.org/802.22/dcn

16、/09/22-09-0120-03-0000-wran-draft-2-0-ballot-comment-database.xls Comment #662 Gerald Chouinard. There were some discussions on this comment. Gerald s comment is to keep the complexity of the security suites in 802.22 low so that there is not a high barrier to the market Ranga Reddy suggested that w

17、hen the security ad-hoc started exploring the architecture for the security in 802.22, we found the 802.16 model most appropriate. Many things from the 802.16 security architecture have been streamlined. There is also an option, that if a user does not have a capability to perform security related f

18、unctions such as encryption / authentication, it may tell the BS and the BS may either choose to serve the user with no security features or it may decide to de-authorize the user from the network. Apurva Mody suggested that the security ad-hoc will consider providing some 802.11 type of mechanisms

19、so that it may facilitate quicker adoption of the standard. Ranga Reddy suggested that security ad-hoc is already considering adding Extensivle Authentication Protocol （EAP） which will allow the service providers to automatically generate the certificates and keys. Ranga Reddy suggested that we wait

20、 until all the comments are resolved and then re-visti this comment to see if something can be done to reduce the complexity. Winston We need to keep in mind the market where 802.22 is likely to be deployed more not Africa but the US Apurva Mody suggested that looking at the trends in 802.16 / WiMAX

21、, it looked like 802.22 may be adopted more quickly in other countries with lesser broadband penetration as compared to the US. 2. August 10th 2009 Security Ad-Hoc Conference Call Meeting Minutes Discussions on security aspects with the external Whitespace database was carried out. Ranga Reddy broug

22、ht to the attention of the group that the Whitespaces Databases Group has started talking about the security issues of the database with the Whitespace Device. This document includes Public Key Infrastructure （PKI）, Transport Security and Device Security. PKI - For PKI, X.509 based use of certificat

23、es is suggested for key exchange. These X.509 certificates will hold an entity name in the SubjectAltName field, following the convention of the World Wide Web. A 2048-bit RSA key for initial deployment is suggested with forward compatibility for key size increases. Use key rollover procedures based

24、 on pre-published supersession to ensure long-term stability of the security architecture is proposed. The OSCP protocol （RFC2560） may be used by WSDs to verify that WSSP certificates have not been revoked by the Repository. Transport Security Transport Layer Security or TLS （RFC4346, though it is sometimes better known by its old name, Secure Sockets Layer or SSL） is suggested. TLS provides authentication, integrity, and confidentiality pro