logo资料库

IEEE Std 802.11r-2008.pdf

第1页 / 共126页
第2页 / 共126页
第3页 / 共126页
第4页 / 共126页
第5页 / 共126页
第6页 / 共126页
第7页 / 共126页
第8页 / 共126页
资料共126页,剩余部分请下载后查看
IEEE Std 802.11r-2008, Front Cover
Title Page
Abstract/Keywords
Introduction
Notice to users
Laws and regulations
Copyrights
Updating of IEEE documents
Errata
Interpretations
Patents
Participants
Contents
List of figures
List of tables
Important Notice
2. Normative references
3. Definitions
4. Abbreviations and acronyms
5. General description
5.2 Components of the IEEE 802.11 architecture
5.2.3 Distribution system (DS) concepts
5.2.3.2 Robust security network association (RSNA)
5.4 Overview of the services
5.4.2 Services that support the distribution services
5.4.2.1 Mobility types
5.4.3 Access control and data confidentiality services
5.4.3.1 Authentication
5.4.3.4 Key management
5.4.3.7 Fast BSS transition
5.8 IEEE Std 802.11 and IEEE Std 802.1X-2004
5.8.1 IEEE 802.11 usage of IEEE Std 802.1X-2004
5.8.2 Infrastructure functional model overview
5.8.2.1 Authentication and key management (AKM) operations with Authentication Server (AS)
6. Medium access control (MAC) service definition
6.1 Overview of MAC services
6.1.2 Security services
7. Frame formats
7.2 Format of individual frame types
7.2.3 Management frames
7.2.3.1 Beacon frame format
7.2.3.4 Association Request frame format
7.2.3.5 Association Response frame format
7.2.3.6 Reassociation Request frame format
7.2.3.7 Reassociation Response frame format
7.2.3.9 Probe Response frame format
7.2.3.10 Authentication frame format
7.3 Management frame body components
7.3.1 Fields that are not information elements
7.3.1.1 Authentication Algorithm Number field
7.3.1.9 Status Code field
7.3.1.11 Action field
7.3.2 Information elements
7.3.2.25 RSN information element (RSNIE)
7.3.2.25.2 AKM suites
7.3.2.25.4 PMKID
7.3.2.37 Neighbor Report element
7.3.2.47 Mobility domain information element (MDIE)
7.3.2.48 Fast BSS transition information element (FTIE)
7.3.2.49 Timeout Interval information element (TIE)
7.3.2.50 RIC Data information element (RDIE)
7.3.2.51 RIC Descriptor information element
7.4 Action frame format details
7.4.8 FT Action frame details
7.4.8.1 FT Request frame
7.4.8.2 FT Response frame
7.4.8.3 FT Confirm frame
7.4.8.4 FT Ack frame
8. Security
8.4 RSNA Security association management
8.4.1 Security associations
8.4.1.1 Security association definitions
8.4.1.1.1a PMK-R0 security association
8.4.1.1.1b PMK-R1 security association
8.4.1.1.2 PTKSA
8.4.6 RSNA authentication in an ESS
8.4.6.1 Preauthentication and RSNA key management
8.4.10 RSNA security association termination
8.5 Keys and key distribution
8.5.1 Key hierarchy
8.5.1.5 FT key hierarchy
8.5.1.5.1 Overview
8.5.1.5.2 Key derivation function (KDF)
8.5.1.5.3 PMK-R0
8.5.1.5.4 PMK-R1
8.5.1.5.5 PTK
8.5.2 EAPOL-Key frames
8.5.2.1 EAPOL-Key frame notation
8.5.3 4-Way Handshake
8.5.3.1 4-Way Handshake Message 1
8.5.3.2 4-Way Handshake Message 2
8.5.3.3 4-Way Handshake Message 3
8.5.3.4 4-Way Handshake Message 4
8.5.4 Group Key Handshake
8.5.4.1 Group Key Handshake Message 1
8.5.4.2 Group Key Handshake Message 2
8.5.8 PeerKey Handshake
8.5.8.1 SMK Handshake
8.5.8.1.1 SMK Handshake Message 1
8.5.8.1.2 SMK Handshake Message 2
8.5.8.1.3 SMK Handshake Message 3
8.5.8.1.4 SMK Handshake Message 4
8.5.8.1.5 SMK Handshake Message 5
8.5.8.3 STKSA rekeying
8.5.8.4 Error reporting
10. Layer management
10.3 MLME SAP interface
10.3.4 Authenticate
10.3.4.1 MLME-AUTHENTICATE.request
10.3.4.1.2 Semantics of the service primitive
10.3.4.2 MLME-AUTHENTICATE.confirm
10.3.4.2.2 Semantics of the service primitive
10.3.4.3 MLME-AUTHENTICATE.indication
10.3.4.3.2 Semantics of the service primitive
10.3.4.4 MLME-AUTHENTICATE.response
10.3.4.4.2 Semantics of the service primitive
10.3.6 Associate
10.3.6.1 MLME-ASSOCIATE.request
10.3.6.1.2 Semantics of the service primitive
10.3.6.2 MLME-ASSOCIATE.confirm
10.3.6.2.2 Semantics of the service primitive
10.3.6.3 MLME-ASSOCIATE.indication
10.3.6.3.2 Semantics of the service primitive
10.3.6.4 MLME-ASSOCIATE.response
10.3.6.4.2 Semantics of the service primitive
10.3.7 Reassociate
10.3.7.1 MLME-REASSOCIATE.request
10.3.7.1.2 Semantics of the service primitive
10.3.7.2 MLME-REASSOCIATE.confirm
10.3.7.2.2 Semantics of the service primitive
10.3.7.3 MLME-REASSOCIATE.indication
10.3.7.3.2 Semantics of the service primitive
10.3.7.4 MLME-REASSOCIATE.response
10.3.7.4.2 Semantics of the service primitive
10.3.33 MLME SAP interface for resource request
10.3.33.1 MLME-RESOURCE_REQUEST.request
10.3.33.1.1 Function
10.3.33.1.2 Semantics of the service primitive
10.3.33.1.3 When generated
10.3.33.1.4 Effect of receipt
10.3.33.2 MLME-RESOURCE_REQUEST.indication
10.3.33.2.1 Function
10.3.33.2.2 Semantics of the service primitive
10.3.33.2.3 When generated
10.3.33.2.4 Effect of receipt
10.3.33.3 MLME-RESOURCE_REQUEST.response
10.3.33.3.1 Function
10.3.33.3.2 Semantics of the service primitive
10.3.33.3.3 When generated
10.3.33.3.4 Effect of receipt
10.3.33.4 MLME-RESOURCE_REQUEST.confirm
10.3.33.4.1 Function
10.3.33.4.2 Semantics of the service primitive
10.3.33.4.3 When generated
10.3.33.4.4 Effect of receipt
10.3.33.5 MLME-RESOURCE_REQUEST_LOCAL.request
10.3.33.5.1 Function
10.3.33.5.2 Semantics of the service primitive
10.3.33.5.3 When generated
10.3.33.5.4 Effect of receipt
10.3.33.6 MLME-RESOURCE_REQUEST_LOCAL.confirm
10.3.33.6.1 Function
10.3.33.6.2 Semantics of the service primitive
10.3.33.6.3 When generated
10.3.33.6.4 Effect of receipt
10.3.34 MLME SAP interface for remote requests
10.3.34.1 MLME-REMOTE_REQUEST.request
10.3.34.1.1 Function
10.3.34.1.2 Semantics of the service primitive
10.3.34.1.3 When generated
10.3.34.1.4 Effect of receipt
10.3.34.2 MLME-REMOTE_REQUEST.indication
10.3.34.2.1 Function
10.3.34.2.2 Semantics of the service primitive
10.3.34.2.3 When generated
10.3.34.2.4 Effect of receipt
10.3.34.3 MLME-REMOTE_REQUEST.confirm
10.3.34.3.1 Function
10.3.34.3.2 Semantics of the service primitive
10.3.34.3.3 When generated
10.3.34.3.4 Effect of receipt
11. MLME
11.3 STA authentication and association
11.3.1 Authentication and deauthentication
11.3.1.1 Authentication-originating STA
11.3.1.2 Authentication-destination STA
11.3.2 Association, reassociation, and disassociation
11.3.2.3 STA reassociation procedures
11.3.2.4 AP reassociation procedures
11.4 Traffic stream (TS) operation
11.4.1 Introduction
11.4.3 TS lifecycle
11.4.4a TS setup by resource request during a fast BSS transition
11A. Fast BSS transition
11A.1 Overview
11A.2 Key holders
11A.2.1 Introduction
11A.2.2 Authenticator key holders
11A.2.3 Supplicant key holders
11A.3 Capability and policy advertisement
11A.4 FT initial mobility domain association
11A.4.1 Overview
11A.4.2 FT initial mobility domain association in an RSN
11A.4.3 FT initial mobility domain association in a non-RSN
11A.5 FT Protocol
11A.5.1 Overview
11A.5.2 Over-the-air FT Protocol authentication in an RSN
11A.5.3 Over-the-DS FT Protocol authentication in an RSN
11A.5.4 Over-the-air FT Protocol authentication in a non-RSN
11A.5.5 Over-the-DS FT Protocol authentication in a non-RSN
11A.6 FT Resource Request Protocol
11A.6.1 Overview
11A.6.2 Over-the-air fast BSS transition with resource request
11A.6.3 Over-the-DS fast BSS transition with resource request
11A.7 FT reassociation
11A.7.1 FT reassociation in an RSN
11A.7.2 FT reassociation in a non-RSN
11A.8 FT authentication sequence
11A.8.1 Overview
11A.8.2 FT authentication sequence: contents of first message
11A.8.3 FT authentication sequence: contents of second message
11A.8.4 FT authentication sequence: contents of third message
11A.8.5 FT authentication sequence: contents of fourth message
11A.9 FT security architecture state machines
11A.9.1 Introduction
11A.9.2 R0KH state machine
11A.9.2.1 R0KH state machine states
11A.9.2.2 R0KH state machine variables
11A.9.2.3 R0KH state machine procedures
11A.9.3 R1KH state machine
11A.9.3.1 R1KH state machine states
11A.9.3.2 R1KH state machine variables
11A.9.3.3 R1KH state machine procedures
11A.9.4 S0KH state machine
11A.9.4.1 S0KH state machine states
11A.9.4.2 S0KH state machine variables
11A.9.4.3 S0KH state machine procedures
11A.9.5 S1KH state machine
11A.9.5.1 S1KH state machine states
11A.9.5.2 S1KH state machine variables
11A.9.5.3 S1KH state machine procedures
11A.10 Remote request broker (RRB) communication
11A.10.1 Overview
11A.10.2 Remote request broker (RRB)
11A.10.3 Remote Request/Response frame definition
11A.11 Resource request procedures
11A.11.1 General
11A.11.2 Resource information container (RIC)
11A.11.3 Creation and handling of a resource request
11A.11.3.1 STA procedures
11A.11.3.2 AP procedures
Annex A (normative) Protocol Implementation Conformance Statement (PICS) proforma
Annex D (normative) ASN.1 encoding of the MAC and PHY MIB
Annex Q (normative) ASN.1 encoding of the RRM MIB
Information technology— exchange between systems— IEEE Standard for Telecommunications and information Local and metropolitan area networks— Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 2: Fast Basic Service Set (BSS) Transition IEEE Computer Society Sponsored by the LAN/MAN Standards Committee M T . r 1 1 2 0 8 IEEE 3 Park Avenue New York, NY 10016-5997, USA 15 July 2008 IEEE Std 802.11r™-2008 (Amendment to IEEE Std 802.11™-2007 as amended by IEEE Std 802.11k™-2008) Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
IEEE Std 802.11r™-2008 (Amendment to IEEE Std 802.11™-2007 as amended by IEEE Std 802.11k™-2008) IEEE Standard for Information Technology— Telecommunications and information exchange between systems— Local and metropolitan area networks— Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications Amendment 2: Fast Basic Service Set (BSS) Transition Sponsored by LAN/MAN Standards Committee of the IEEE Computer Society Approved 9 May 2008 IEEE-SA Standards Board Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
Abstract: This amendment specifies the extensions to IEEE Std 802.11-2007 for wireless local area networks (WLANs) providing mechanisms for fast basic service set (BSS) transition. Keywords: LAN, local area network, wireless LAN, WLAN The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright © 2008 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 15 July 2008. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and Electronics Engineers, Incorporated. PDF: Print: ISBN 973-07381-5442-0 STD95794 ISBN 973-07381-5423-7 STDPD95794 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained in its standards. Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document. The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied “AS IS.” The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. In publishing and making this document available, the IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be relied upon as, a formal interpretation of the IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the formal position, explanation, or interpretation of the IEEE. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Comments on standards and requests for interpretations should be submitted to the following address: Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USA Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
Introduction This introduction is not part of IEEE Std 802.11-2007, IEEE Standard for information technology— Telecommunications and information exchange between systems—Local and metropolitan area networks— Specific requirements—Part 11: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications—Amendment 2: Fast Basic Service Set (BSS) Transition. This amendment describes mechanisms that minimize the amount of time data connectivity is lost between the station (STA) and the distribution system (DS) during a basic service set (BSS) transition. The STA determines when to transition and to which access point (AP) to transition based on a number of factors, some of which may be out of the scope of this standard. The following summarizes the typical behavior of the non-AP STA and AP when a transition occurs without fast BSS transition (FT) services: — The STA uses scanning or neighbor reports to discover APs available for transition. — The STA chooses a target AP and performs an IEEE 802.11 authentication exchange with that AP; typically this exchange will be an “open auth” exchange. During this time, the STA may still exchange data with the DS through its current AP. — The STA sends a (Re)Association frame to establish a connection at the target AP. — In a robust security network (RSN), the STA and the AP then generate and confirm matching temporal keys based on a preshared key (PSK) or an IEEE 802.1X authentication (which could be through an earlier preauthentication or key caching). — In an RSN, the STA and AP install the keys and start to exchange data with the DS. — For a quality of service (QoS) STA connected to a QoS AP, the STA may then request QoS resources by issuing one or more ADDTS (add traffic stream) requests. The FT mechanism allows a STA to establish security and/or QoS state at the target AP prior to or during reassociation, avoiding delays in connecting to the DS after transition. The overall changes to the protocol do not introduce any new security vulnerabilities beyond the current IEEE 802.11 standard and its amendments. The FT mechanism preserves the behavior of legacy STAs and APs. The FT time is the total transition time that starts after the receipt of the last acknowledged data frame sent within an originating BSS and ends after the receipt of the first acknowledged data frame sent within the destination BSS, while the non-AP STA transitions from one BSS to another using the FT mechanisms. This amendment addresses solutions to two classes of network infrastructures from a QoS perspective: one where the transition-enabled AP is willing to provision QoS resources at reassociation time; and another where the AP needs to reserve the network infrastructure resources before transitioning. This amendment does not specifically address the solution of when or where a STA will roam. Other tools give the STA information that could be used in making this decision. IEEE 802.11 enables the AP to convey a BSS Load information element in Probe Response and Beacon frames. The BSS Load information element has three fields that indicate the number of associated STAs, the channel utilization for the BSS, and the available admission capacity. These QoS BSS metrics give information on the AP's ability to accept new QoS streams. IEEE 802.11 defines the neighbor reports, which can assist in optimizing scanning. iv Copyright © 2008 IEEE. All rights reserved. Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisions of this standard does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE Standards Association website at http:// ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA website at http://standards.ieee.org. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:// standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/ index.html. Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patents or patent applications for which a license may be required to implement an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. A patent holder or patent applicant has filed a statement of assurance that it will grant licenses under these rights without compensation or under reasonable rates and nondiscriminatory, reasonable terms and conditions to Copyright © 2008 IEEE. All rights reserved. v Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
applicants desiring to obtain such licenses. The IEEE makes no representation as to the reasonableness of rates, terms, and conditions of the license agreements offered by patent holders or patent applicants. Further information may be obtained from the IEEE Standards Department. Participants At the time this amendment was sent to sponsor ballot, the IEEE 802.11 Working Group had the following officers: Stuart J. Kerry, Chair Al Petrick, Vice Chair, Treasurer and Chair, Task Group mb Harry R. Worstell, Vice Chair Stephen McCann, Secretary and Chair, Publicity Standing Committee Teik-Kheong Tan, Chair, Wireless Next Generation Standing Committee Terry L. Cole, Technical Editor and Assigned Number Authority Bruce P. Kraemer, Chair, Task Group n and Co-Chair IMT-Advanced Ad hoc Committee Richard H. Paine, Chair, Task Group k Sheung Li, Vice Chair, Task Group n Lee Armstrong, Chair, Task Group p Donald E. Eastlake III, Chair, Task Group s Neeraj Sherma, Chair, Task Group T Stephen McCann, Chair, Task Group u Dorothy V. Stanley, Chair, Task Group v & IETF Ad hoc Committee Jesse Walker, Chair, Task Group w & JCT1 Ad hoc Committee Peter Ecclesine, Chair, Task Group y Menzo Wentink, Direct Link Setup Study Group Bob O’Hara, QoS Extensions Study Group Ganesh Venkatesan, Video Transport Stream Study Group Eldad Perahia, Very High Throughput Study Group Darwin Engwer, Co-Chair, IMT-Advanced Ad hoc Committee At the time this amendment was submitted to sponsor ballot, the Task Group r had the following officers: Clint Chaplin, Chair Michael Montemurro, Secretary Bill Marshall, Technical Editor When the IEEE 802.11 Working Group approved this amendment, the Working Group had the following membership: Osama Aboul-Magd Tomoko Adachi Carlos Aldana Thomas Alexander Keith Amann David Andrus Takashi Aramaki Sirikiat Lek Ariyavisitakul Larry Arnett Alex Ashley Arthur Astrin Malik Audeh Geert Awater Floyd Backes David Bagby Michael Bahr Dennis Baker Amit Bansal John Barr Gal Basson Anuj Batra Moussa Bavafa Mathilde Benveniste Bjorn Bjerke Tony Braskich George Bumiller Alistair Buttar Pat Calhoun Nancy Cam-Winget James Carlo Pat Carson Broady Cash Dave Cavalcanti Douglas Chan Yi-Ming Chen Hong Cheng Paul Cheng Aik Chindapol Abhijit Choudhury Liwen Chu Frank Ciotti W. Steven Conner Charles Cook Steven Crowley David Cypher Marc de Courville vi Copyright © 2008 IEEE. All rights reserved. Authorized licensed use limited to: ULAKBIM UASL - TOBB Ekonomi ve Teknoloji Univ. Downloaded on May 11,2014 at 13:26:53 UTC from IEEE Xplore. Restrictions apply.
分享到:
收藏