`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 1 of 97
`
`EXHIBIT 10
`EXHIBIT 10
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 2 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 2 of 97
`
`IEEE Std 802.11b-1999
`(Supplementto
`ANSIMEEE Std 802.11, 1999 Edition)
`
`Supplement to IEEE Standard for
`Information technology —
`Telecommunications and information exchange
`between systems—
`_ocal and metropolitan area networks—
`Specific requirements —
`
`Part 11: Wireless LAN Medium Access Control
`(MAC) and Physical Layer (PHY) specifications:
`
`Higher-Speed Physical Layer Extension in the
`2.4 GHz Band
`
`Sponsor
`
`LAN/MAN Standards Committee
`of the
`IEEE Computer Society
`
`Approved 16 September 1999
`
`IEEE-SA Standards Board
`
`Abstract: Changes and additions to IEEE Std 802.11, 1999 Edition are provided to support the
`higher rate physical layer (PHY) for operation in the 2.4 GHz band.
`Keywords: 2.4 GHz, high speed, local area network (LAN), radio frequency (RF), wireless
`
`The Institute of Electrical and Electronics Engineers, Inc.
`3 Park Avenue, New York, NY 10016-5997, USA
`
`Copyright © 2000 bythe Institute of Electrical and Electronics Engineers,inc.
`All rights reserved. Published 20 January 2000. Printed in the United States of America.
`
`Print:
`PDF:
`
`ISBN 0-7381-1811-7
`ISBN 0-7381-1812-5
`
`SH94788
`$S94788
`
`No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, withoutthe prior
`written permission of the publisher.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002411
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 3 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 3 of 97
`
`IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Com-
`
`mittees of the IEEE Standards Association (EEE-SA) Standards Board. Members of the committees serve
`voluntarily and without compensation. They are not necessarily members of the Institute. The standards
`developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as
`well as those activities outside of IEEE that have expressed an interest in participating in the developmentof
`the standard.
`
`Use of an IEEE Standard is wholly voluntary. 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 fromusers 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 rea-
`sonable to conclude thatits contents, although still of some value, do not wholly reflect the presentstate of
`the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard.
`
`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.
`
`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
`all concernedinterests, it is important to ensure that any interpretation has also received the concurrence of a
`balance of interests. For this reason, IEEE and the membersof 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.
`
`Comments on standards and requests for interpretations should be addressed to:
`
`Secretary, IEEE-SA Standards Board
`445 Hoes Lane
`P.O. Box 1331
`
`Piscataway, NJ 08855-1331
`USA
`
`Note: 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 for
`which a license may be required by an IEEE standard or for conducting inquiries into
`
`the legal validity or scope of those patents that are broughtto its attention.
`
`Authorization to photocopy portions of any individual standard for internal or personal use is granted bythe
`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, Cus-
`tomer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (978) 750-8400. Permission to photocopy
`portions of any individual standard for educational classroom use can also be obtained through the Copy-
`right Clearance Center.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002412
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 4 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 4 of 97
`
`Introduction
`
`[This introduction is not part of IEEE Std 802.11b-1999, Supplement to 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:
`Higher-Speed Physical Layer Extension in the 2.4 GHz Band.}
`
`This standard is part of a family of standards for local and metropolitan area networks. The relationship
`between the standard and other members of the family is shown below. (The numbers in the figure refer to
`IEEE standard numbers.)
`
`
`
`
`*
`cr
`>
`E
`ts
`=
`3
`a
`<
`8
`=
`in
`S
`i
`35
`
`x 802.12|PHYSICAL802.3 802.4 802.5 802.6 802.9 802.11
`
`
`
`
`
`
`&
`PHYSICAL]
`IPHYSICAL|
`|PHYSICAL}
`|PHYSICAL}
`|PHYSICAL|
`IPHYSICAL)
`[PHYSICAL]
`LAYER
`
`802.2 LOGICAL LINK GONTROL
`
`
`
`802.1 BRIDGING
`
`DATA
`LINK
`LAYER
`
`802.3
`MEDIUM
`ACCESS
`
`802.4
`MEDIUM
`ACCESS
`
`802.5
`MEDIUM
`ACCESS
`
`802.6
`MEDIUM
`ACCESS
`
`802.9
`MEDIUM
`ACCESS
`
`802.11
`MEDIUM
`ACCESS
`
`802.12
`MEDIUM
`ACCESS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`5
`u
`i
`Oo
`=
`=
`<
`2
`5
`2
`
`aEa a
`
`mt
`”
`°
`as
`©
`
`* Formerly IEEE Std 802.1A.
`
`This family of standards deals with the Physical and Data Link layers as defined by the International Organiza-
`tion for Standardization (SO) Open Systems Interconnection (OSD Basic Reference Model CSO/TEC
`7498-1:1994). The access standards define seven types of mediumaccess technologies and associated physi-
`cal media, each appropriate for particular applications or system objectives. Other types are under
`investigation.
`
`The standards defining the access technologies are as follows:
`
`IEEE Std 802
`
`Overview and Architecture. This standard provides an overview to the family
`of IEEE 802 Standards.
`
`* ANSI/IEEE Std 802.1B
`and 802.1k
`
`[ISO/IEC 15802-2]
`
`LAN/MAN Management. Defines an OSI management-compatible architec-
`ture, and services and protocol elements for use in a LAN/MANenvironment
`for performing remote management.
`
`¢ ANSI/IEEE Std 802.1D
`
`[ISO/IEC 15802-3]
`
`* ANSI/IEEE Std 802.1E
`
`[ISO/IEC 15802-4]
`
`e
`
`JEEE Std 802.1F
`
`* ANSI/IEEE Std 802.1G
`
`[ISO/IEC 15802-5]
`
`Media Access Control (MAC) Bridges. Specifies an architecture and protocol
`for the interconnection of IEEE 802 LANs belowthe MAC service boundary.
`
`System Load Protocol. Specifies a set of services and protocol for those
`aspects of management concerned with the loading of systems on IEEE 802
`LANs.
`
`CommonDefinitions and Procedures for IEEE 802 Management Information
`
`Remote Media Access Control Bridging. Specifies extensions for the intercon-
`nection, using non-LAN communication technologies, of geographically sepa-
`rated IEEE 802 LANsbelowthelevel ofthe logical link control protocol.
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`iti
`
`DELL-OZMO-1-002413
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 5 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 5 of 97
`
`ANSI/IEEE Std 802.2
`
`[ISO/IEC 8802-2]
`
`ANSI/IEEE Std 802.3
`
`[ISO/IEC 8802-3]
`
`ANSI/IEEE Std 802.4
`
`[ISO/IEC 8802-4]
`
`ANSI/TEEE Std 802.5
`
`[ISO/IEC 8802-5]
`
`ANSI/IEEE Std 802.6
`
`[ISO/IEC 8802-6]
`
`ANSI/IEEE Std 802.9
`
`[ISO/IEC 8802-9]
`
`_—
`
`ANSI/IEFE Std 802.10
`
`IEEE Std 802.11
`
`[ISO/IEC DIS 8802-11]
`
`ANSI/IEEE Std 802.12
`
`[ISO/IEC DIS 8802-12]
`
`Logical Link Control
`
`CSMA/CD Access Method and Physical Layer Specifications
`
`Token Passing Bus Access Method and Physical Layer Specifications
`
`Token Ring Access Method and Physical Layer Specifications
`
`Distributed Queue Dual Bus Access Method and Physical Layer Specifica-
`tions
`
`Integrated Services (IS) LAN Interface at the Medium Access Control and
`Physical Layers
`
`Interoperable LAN/MAN Security
`
`Wireless LAN Medium Access Control and Physical Layer Specifications
`
`Demand Priority Access Method, Physical Layer and Repeater Specifica-
`tions
`
`In addition to the family of standards, the following is a recommended practice for a common Physical
`Layer technology:
`
`IEEE Std 802.7
`
`LEEE Recommended Practice for Broadband Local Area Networks
`
`The following additional working groups have authorized standards projects under development:
`
`IEEE 802.14
`
`IEEE 802.15
`
`IEEE802.16
`
`Standard Protocol for Cable-TV Based Broadband Communication Network
`
`Wireless Personal Area Networks Access Method and Physical Layer
`Specifications
`
`Broadband Wireless Access Method and Physical Layer Specifications
`
`iv
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002414
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 6 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 6 of 97
`
`Participants
`
`At the time this standard wasballoted, the 802.11 Working Group had the following membership:
`
`Vic Hayes, Chair
`
`Stuart J. Kerry, Vice Chair
`
`Al Petrick, Co-Vice Chair
`
`George Fishel, Secretary
`
`Robert O'Hara, Chair and editor, 802.1 1-rev
`
`Allen Heberling, State-diagram editor
`
`Michael A. Fischer, State-diagram editor
`
`Dean M. Kawaguchi, Chair PHY group
`
`David Bagby, Chair MAC group
`
`Naftali Chayat, Chair Task Group a
`
`Hitoshi Takanashi, Technical Editor, 802.1 la
`
`John Fakatselis, Chair Task Group b
`
`Carl F. Andren, Technical Editor, 802.11b
`
`Jetfrey Abramowitz
`Reza Ahy
`Keith B. Amundsen
`James R. Baker
`
`Kevin M. Barry
`Phil Belanger
`John Biddick
`Simon Black
`Timothy J. Blaney
`Jan Boer
`Ronald Brockmann
`Wesley Brodsky
`John H. Cafarella
`Wen-Chiang Chen
`Ken Clements
`
`Wim Diepstraten
`Peter Ecclesine
`Richard Eckard
`
`Darwin Engwer
`Greg Ennis
`Jeffrey J. Fischer
`John Fisher
`Tan Gifford
`Motohiro Gochi
`
`Tim Godfrey
`Steven D. Gray
`Jan Haagh
`Karl Hannestad
`Kei Hara
`
`Chris D. Heegard
`Robert Heile
`Juha T. Heiskala
`Maarten Hoeben
`Masayuki Ikeda
`Donald C. Johnson
`Tal Kaitz
`Ad Kamerman
`Mika Kasslin
`
`Patrick Kinney
`Steven Knudsen
`Bruce P. Kraemer
`David S. Landeta
`James S. Li
`
`Stanley Ling
`Michael D. McInnis
`Gene Miller
`Akira Miura
`Henri Moelard
`Masaharu Mori
`Masahiro Morikura
`Richard van Nee
`Erwin R. Noble
`Tomoki Ohsawa
`Kazuhiro Okanoue
`Richard H.Paine
`
`Roger Pandanda
`Victoria M. Poncini
`Gregory S. Rawlins
`Stanley A. Reible
`
`Frits Riep
`William Roberts
`Kent G. Rollins
`
`Clemens C.W. Ruppel
`Anil K. Sanwalka
`
`Roy Sebring
`Tie-Jun Shan
`
`Stephen J. Shellhammer
`Matthew B. Shoemake
`
`Thomas Siep
`Donald T. Sloan
`
`Gary Spiess
`Satoru Toguchi
`Cherry Tom
`Mike Trompower
`Tom Tsoulogiannis
`Bruce Tuch
`Sarosh N. Vesuna
`
`Ikuo Wakayama
`Robert M. Ward,Jr.
`Mark Webster
`Leo Wilz
`
`Harry R. Worstell
`Lawrence W. Yonge,III
`Chris Zegelin
`Jonathan M. Zweig
`James Zyren
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002415
`
`Vv
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 7 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 7 of 97
`
`The following members of the balloting committee voted on this standard:
`Carl F. Andren
`Jack S. Andresen
`
`Raj Jain
`A. Kamerman
`
`Lek Ariyavisitakul
`David Bagby
`Kevin M. Barry
`John H. Cafarella
`James T. Carlo
`David E. Carlson
`Linda T. Cheng
`Thomas J. Dineen
`Christos Douligeris
`Peter Ecclesine
`Richard Eckard
`
`Philip H. Enslow
`John Fakatselis
`Jeffrey J. Fischer
`Michael A. Fischer
`Robert J. Gagliano
`GautamGarai
`Alireza Ghazizahedi
`Tim Godfrey
`Patrick S. Gonia
`
`Steven D. Gray
`Chris G. Guy
`Vic Hayes
`Allen Heberling
`Chris D. Heegard
`Juha T. Heiskala
`
`Dean M. Kawaguchi
`Stuart J. Kerry
`Patrick Kinney
`Daniel R. Krent
`Walter Levy
`Stanley Ling
`RandolphS. Little
`Roger B. Marks
`Peter Martini
`Richard McBride
`Bennett Meyer
`David S. Millman
`
`Hiroshi Miyano
`Warren Monroe
`Masahiro Morikura
`Shimon Muller
`Peter A. Murphy
`Paul Nikolich
`Erwin R. Noble
`Satoshi Obara
`Robert O'Hara
`Charles Oestereicher
`Kazuhiro Okanoue
`
`Roger Pandanda
`Ronald C. Petersen
`Al Petrick
`
`Vikram Punj
`
`Pete Rautenberg
`Stanley A. Reible
`Edouard Y. Rocher
`Kent G.Rollins
`James W. Romlein
`Floyd E. Ross
`Christoph Ruland
`Anil K. Sanwalka
`Norman Schneidewind
`James E. Schuessler
`Rich Seifert
`Matthew B. Shoemake
`Leo Sintonen
`Hitoshi Takanashi
`
`Mike Trompower
`Mark-Rene Uchida
`Scott A. Valcourt
`Richard Van Nee
`Sarosh N. Vesuna
`
`John Viaplana
`Hirohisa Wakai
`Robert M. Ward,Jr.
`Mark Webster
`Harry R. Worstell
`Stefan M. Wurster
`Oren Yuen
`
`Jonathan M. Zweig
`James Zyren
`
`When the IEEE-SA Standards Board approved this standard on 16 September 1999, it had the following
`membership:
`
`Richard J. Holleman, Chair
`Donald N. Heirman, Vice Chair
`Judith Gorman,Secretary
`
`James H. Gurney
`Lowell G. Johnson
`Robert J. Kennelly
`E. G. “Al” Kiener
`
`Joseph L. Koepfinger*
`L. Bruce McClung
`Daleep C. Mohla
`Robert F. Munzner
`
`Louis-Frangois Pau
`Ronald C. Petersen
`Gerald H. Peterson
`John B. Posey
`Gary S. Robinson
`Akio Tojo
`Hans E. Weinrich
`
`Donald W. Zipse
`
`Satish Kk. Aggarwal
`Dennis Bodson
`Mark D. Bowman
`James T. Carlo
`
`Gary R. Engmann
`Harold E. Epstein
`Jay Forster*
`Ruben D. Garzon
`
`*Member Emeritus
`
`Also included is the following nonvoting IEEE-SA Standards Board liaison:
`
`Robert E. Hebner
`
`Janet Rutigliano
`IEEE Standards Project Editor
`
`vi
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002416
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 8 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 8 of 97
`
`Contents
`
`3.8 Basic service set (BSS) basic rate SEC .......cccccssccccccccssssneecesecssesnseseceeeesssenaeaeeesevecsnausresesessesneanneess 1
`
`4.—Abbreviations and acronyms... ence entree cee eee cere renee eet eee ee eee eae eeaceeeeeee cee eaeaaaeeesneaeneenea 2
`
`7.2.3.1 Beacon frame format... ce cee cece neces renee tee rane cares ene caaesaeseesasneveoesaevaareeseesgevsaauaseeneasees 2
`
`7.2.3.9 Probe Response frame format...einen eniiee sme enenne 3
`7.3.1.4 Capability Information field 0.0... cece cece ceeeeenne eee ce tense eecaeeeeeeseneeesneeneeeeseneecureesnaeeenenecnrenena 3
`7.3.1.9 Status Code field o.oo ceeee e eee cee eee eens creas renee ee saaea ates ene caaes asses sasneneesaevareeseesoewsauaseeseasees 5
`7.3.2.2 Supported Rates element... cece cece eee cee ceeeee cerca e ee aeee see ce aes aeteecaneeeeesaesaeeseesaeseaneeveseaneas 5
`
`9.20 DCBoe cect ee eee tee ener tne ee tad nee sees sage see tase esaevae sates snecaessasaee case senses sgaeeeseecnevsaasenerenes 5
`
`9.6 Multirate Support... cee cece cece eee c ee eee tee tae ae ee seeee eee see ca aes aeneesas asses saesaveeseesgaesneeveessaneas 6
`
`10.3.2.2 MLME_scan. comity... ccccccccccccccecececeeeeceeceeeeeseeenecesecentecueesaeeaeceaueeseeeaeesaeeeeteeuenenesenteeeeteeeeees 6
`10.3.2.2.2 Semantics of the service primitive .....0.....ccccceccecesceeeeeeeeee conse cence eeeeeeeeeeseeeeeseeeneeeesereeenrennes 7
`10.3.3.1.2 Semantics of the service Primitive 0... ee eee ee eee cee e ee ene cee ta ete eeae seta eteesaetneseasneeas 8
`10.3.1 Start... eee cece eee cee cere tees ee aeeetsecae se aeeee case seeevaesaaseeseesaesasaae cane sueesaesaeesseecesensereaeeeseas 8
`
`10.3.10.1.2 Semantics of the service Primitive oo...ee ener eee neers ern etennee teen eeennnee 9
`10.4.4 PLME_DSSSTESTMODE|... ieee ect eee ee ca eee rene ce eae tee sae ee snes sae taavee sneer eg nneesaeneaeeeteee 10
`
`18.
`
`High Rate, direct sequence spread spectrum PHY specification .......0...0. cece tee ee teeter tee teee il
`
`LBL OVELVIOW occ cence reee rece neeeaeeneeaeceenecaeeeeneee ea enecaaecaaeseee scans cases aeeeeaeecnaeceneeenenyeennacnieeenaeeesnnsenienea il
`
`18.2 High Rate PLCP sublayer 02... cccceee esse ceeeeeecereneneceeneesaeeenereecaneesaeecneeesenceseaeesneeeseneernareeneeeneaeees 12
`18.3 High Rate PLME..... ice ce cine ene nn i erie ene nies tire ter eine neers tir eaar ea ennneeneretesereaeenneenerenete 27
`18.4 High Rate PMD sublayer......c ce iceececceceec ec eects ee eee ene cee eaaeeeeen eee ese seaaenee snes se sceseadeeeeeneeneanats 30
`
`Annex A (normative), Protocol implementation conformance statement (PICS) proforma ..... eee 59
`
`Annex C (normative), Formal description of MAC operation... eee cece eee reece teeee tee teeteeeeeneteaeeatees 64
`
`Annex D (normative), ASN.1 encoding of the MAC and PHY MIB ooo... iccceeeesneceseeeenereear eres cesneesennenens 88
`
`Annex F (informative), High Rate PHY/frequency-hopping interoperability...ee eee 89
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Vii
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002417
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 9 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 9 of 97
`
`Supplement to 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:
`
`Higher-Speed Physical Layer
`Extension in the 2.4 GHz Band
`
`(This supplement is based on IEEE Std 802.11, 1999 Edition.]
`
`EDITORIAL NOTE---Theediting instructions contained in this supplement define howto merge the material contained
`herein into the existing base standard to form the new comprehensive standard, as created by the addition of IEEE Std
`802.11b-1999.
`
`The editing instructions are shown in bold italic. Three editing instructions are used: change, delete, and
`insert. Change is used to make small corrections in existing text or tables. This editing instruction specifies
`the location of the change and describes what is being changed either by using strikethrough (to remove old
`material) or underscore (to add new material). Delefe removes existing material. Insert adds new material
`without disturbing the existing material. Insertions may require renumbering. If so, renumbering instructions
`are given in the editing instructions. Editorial notes will not be carried overinto future editions.
`
`3.8 Basic service set (BSS) basic rate set
`
`Change the text in this subclause as shown:
`
`The set of data transfer rates that all the stations in a BSS will be capable of using to receive and transmit
`frames to/from the wireless medium (WM). The BSS basic rate set data rates are preset for all stations in
`the BSS.
`
`Copyright © 2000 IEEE. All rights reserved.
`
`1
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002418
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 10 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 10 of 97
`IEEE
`Std 802.11b-1999
`
`SUPPLEMENTTO IEEE STANDARD FOR INFORMATION TECHNOLOGY —
`
`4. Abbreviations and acronyms
`
`Insert the following abbreviations alphabetically in the list in Clause 4:
`
`CCK
`HR/DSSS
`HR/DSSS/short
`
`HR/DSSS/PBCC
`
`complementary code keying
`High Rate direct sequence spread spectrumusing the Long Preamble and header
`High Rate direct sequence spread spectrum using the optional Short Preamble
`and header mode
`
`High Rate direct sequence spread spectrumusing the optional packet binary con-
`volutional coding mode and the Long Preamble and header
`
`HR/DSSS/PBCC/shert High Rate direct sequence spread spectrum using the optional packet binary con-
`volutional coding mode and the optional Short Preamble and header
`
`7.2.3.1 Beacon frame format
`
`Change Notes 1 and 2 of Table 5 as shown:
`
`Table 5— Beacon frame body
`
`
`
`TIM
`
`Order
`
`Information
`
`Note
`
`Timestamp
`
`Beacon interval
`
`Capability Information
`SSID
`
`Supported Rates
`FH Parameter Set
`
`DS Parameter Set
`
`CF Parameter Set
`
`IBSS Parameter Set
`
`NOTES:
`
`1—The FH Parameter Set information element is ealy present within Beacon frames generated by STAs using fre-
`quency-hopping PHYs.
`
`2—The DS Parameter Set information element is enly present within Beacon frames generated by STAs using direct
`sequence PITYs.
`
`3—The CF Parameter Set information element is only present within Beacon frames generated by APs supporting
`a PCF.
`
`4—The IBSS Parameter Set information element is only present within Beacon frames generated by STAsin an IBSS.
`
`5--The TIM information element is only present within Beacon frames generated by APs.
`
`2
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002419
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 11 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 11 of 97
`IEEE
`Stc 802.11b-1999
`
`HIGHER-SPEED PHYSICAL LAYER EXTENSION IN THE 2.4 GHz BAND
`
`7.2.3.9 Probe Response frame format
`
`Change Notes 1 and 2 of Table 12 as shown:
`
`Table 12—Probe Response frame body
`
`Information
`
`IBSS ParameterSet
`CF Parameter Set
`
`
`Timestamp
`Beaconinterval
`
`Capability Information
`SSID
`
`Supported Rates
`FH Parameter Set
`
`DS Parameter Set
`
`NOTES:
`
`1—The FH Parameter Set information element is enly present within Probe Response frames generated by STAsusing
`frequency-hopping PHYs.
`
`2—The DS Parameter Set information element is enly present within Probe Response frames generated by STAs using
`direct sequence PHYs.
`
`3—The CF Parameter Set information element is only present within Probe Response frames generated by APs support-
`ing a PCF
`
`4—The IBSS Parameter Set information element is only present within Probe Response frames generated by STAs in
`an IBSS.
`
`7.3.1.4 Capability Information field
`
`Change the text in 7.3.1.4 and Figure 27 as shown:
`
`The Capability Information field contains a numberof subfields that are used to indicate requested or adver-
`tised capabilities.
`
`The length of the Capability Information field is 2 octets. The Capability Information field consists of the
`
`following subfields: ESS, IBSS, CF-Pollable, CF-Poll Request, aad Privacy, Short Preamble, PBCC, and
`Channel Agility. The format of the Capability Information field is as illustrated in Figure 27.
`
`Copyright © 2000 IEEE. All rights reserved.
`
`3
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002420
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 12 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 12 of 97
`IEEE
`Std 802.1 1b-1999
`
`SUPPLEMENTTO IEEE STANDARD FOR INFORMATION TECHNOLOGY —
`
`
`BO
`Bt
`B2
`B3
`B4
`BS
`BS
`BZ
`BS
`YL
`B15
`|
`CF
`CF-Poll
`Short
`Channel
`
`
`
`
`ESS Privacy |Preamble|PBCCIBSS Pollable; Request| Agility | Reserved |
`
`Lf,
`L
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Octets:
`
`2
`
`<<
`
`-
`
`Figure 27 —Capability Information fixed field
`
`Insert the following text at the end of 7.3.1.4:
`
`
`APs (as_well as STAs in IBSSs) shall set the Short Preamble subfield to 1 in transmitted Beacon, Probe
`
`Response, Association Response, and Reassociation Response management MMPDUsto indicate that the
`
`use_of the Short Preamble option, as described in 18.2.2.2. is allowed within this BSS. To indicate that the
`
`use of the Short Preamble option is not allowed. the Short Preamble subfield shall be set to 0 in Beacon,
`
`Probe Response, Association Response, and Reassociation Response management MMPDUs transmitted
`within the BSS.
`
`
`STAs shali set the Short Preamble subfield to_1 in transmitted Association Request_and Reassociation
`
`Request MMPDUs when the MIB attribute dot] 1ShortPreambleOptionImplemented_is true. Otherwise,
`
`STAs shall set the Short Preamble subfield to 0 in transmitted Association Request _and Reassociation
`Request MMPDUs.
`
`
`APs (as well as STAs in IBSSs) shall set the PBCC subfield to 1 in transmitted Beacon, Probe Response,
`
`Association Response, and Reassociation Response management MMPDUs to indicate that the use of the
`
`PBCC Modulation option, as described in 18.4.6.6, is allowed within this BSS. To indicate that the use of the
`
`PBCC Modulation option is not allowed, the PBCC subfield shall be set to 0 in Beacon, Probe Response.
`
`Association Response, and Reassociation Response management MMPDUs transmitted within the BSS.
`
`
`STAs shall set the PBCC subfield to 1
`in transmitted Association Request and Reassociation Request
`
`MMPDUs when the MIB attribute dot!l1PBCCOptionImplemented is true. Otherwise, STAs shall set the
`
`PBCC subfield to 0 in transmitted Association Request and Reassociation Request MMPDUs.
`
`
`Bit 7 of the Capabilities Information field shall be used to indicate the usage of Channel Agility by the HR/
`
`DSSS PHY. STAs shall set the Channel Agility bit to_1 when Channel Agility is in use, and shall set_it
`to 0 otherwise.
`
`
`Bits 8-15 of the Capability Information field are reserved.
`
`4
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002421
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 13 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 13 of 97
`IEEE
`Std 802.11b-1999
`
`HIGHER-SPEED PHYSICAL LAYER EXTENSION IN THE 2.4 GHz BAND
`
`7.3.1.9 Status Codefield
`
`Add three Status Codes to Table 19 as shown:
`
`Table 19—Status Codes
`
`Status Code
`
`Meaning
`
`
`
`Association denied due to
`requesting station not sup-
`porting the Short Pream-
`ble option.
`
`
`Association denied due to
`requesting station not sup-
`porting the PBCC Modula-
`tion option.
`
`
`Association denied due to
`
`requesting station not sup-
`porting the Channel Agil-
`ity option.
`
`7.3.2.2 Supported Rates element
`
`Change the text in 7.3.2.2 as shown.
`
`
`The Supported Rates element specifies all the values ratesthat this_station _is_-capable_of receiving in the
`Operational-Rate-Set_ parameter, as described in the MLME_Join.request and MLME_Start.request_primi-
`tives. The information field is encoded as 1-8 octets, where each octet describes a single Supported Rate+a
`
`Within Beacon, Probe Response, Association Response, and Reassociation Response management frames,
`each Supported Rate belonging to the BSSBasie-Rate-Set BSSbasicrate set is encoded as an octet with the
`msb(bit 7) set to 1 (e.g., a 1 Mbit/s rate belonging to the BSSBasieRateSet BSS basic rate set is encoded as
`X'82'). Rates not belonging to the BSSBasicRateSet_BSS basic rate set are encoded with the msb set to 0
`(e.g., a 2 Mbit/s rate not belonging to the BSSBasieRateSet BSS basic rate set is encoded as X'04'). The msb
`of each Supported Rate octet in other management frame types is ignored by receiving STAs.
`
`BSSBasicRateSet The BSS basic rate set information in Beacon and Probe Response management frames is
`delivered to the managemententity in an STA via the BSSBasicRateSet parameter in the MLME_Scan.con-
`
`firm primitive. lt is used by the managemententity in an STAs in-order to avoid associating with a BSS if the
`
`STA cannot receive and transmit all
`the data rates in the BSSBasieRateSet BSS basic rate set (see
`Figure 36).
`
`9.2 DCF
`
`Change the eleventh paragraph in 9.2 as shown.
`
`The medium access protocolallowsfor stations to support different sets of data rates. All STAs shall _beable
`to_receive_and transmit
`at all
`the data rates
`in the aBasicRateSet
`specified parameter
`_of
`the
`
`
`aadtransmit-atone-or-more-ofMLME_Join.request and MLME_Start.request primitivestheaBasicRateset
`
`
`Copyright © 2000 IEEE. All rights reserved.
`
`5
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002422
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 14 of 97
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 14 of 97
`IEEE
`Std 802.11b-1999
`
`SUPPLEMENTTO IEEE STANDARD FOR INFORMATION TECHNOLOGY —
`
`datarates. To support the proper operation of the RTS/CTS and the Virtual Carrier Sense mechanism, all
`STAsshall be able to detect the RTS and CTS frames. For this reason, the RTS and CTS frames shall be
`transmitted at one of the rates in the BSS basic rate set aBasicRateSet-rates. (See 9.6 for a description of
`multirate operation.)
`
`9.6 Multirate support
`
`Change the existing text as shown:
`
`Some PHYs have multiple data transfer rate capabilities that allow implementations to perform dynamicrate
`switching with the objective of improving performance. The algorithm for performing rate switching is
`beyond the scope of this
`standard, but
`in order
`to ensure coexistence and interoperability on
`multirate-capable PHYs, this standard defines a set of rules that shall be followed by all STAs.
`
`All Control frames shall be transmitted at one of the rates in the BSSBasicRateSetBSS basic rate set see
`
`
`
`40.3101) eratoneoftheratesinthePHYmandatoryrate-setsothatthey will be understood by all STAsin
`theBSS.
`
`All frames with multicast and broadcast RA shall be transmitted at one of the rates included in the BSSBasi-
`eRateSetBSS basic rate set, regardless of their type or subtype.
`
`Data and/or management MPDUs with a unicast immediate-address RA shall be sent on any supported data
`rate selected by the rate switching mechanism (whose output is an internal MAC variable called MACCur-
`rentRate, defined-+nunits-of500_kbit/s_which is used for calculating the Duration/ID field of each frame).
`An STA shall not transmit at a rate that is known not to be supported by the destination STA, as reported in
`the Supported Rates element in the managementframes. For frames of type Data + CF — ACK, Data + CI’ —
`Poll + CF — ACK, and CF — Poll + CF — ACK, the rate chosen to transmit the frame must be supported by
`both the addressed recipient STA and the STA to which the ACKis intended.
`
`dnordertto To allow the transmitting STA to calculate the contents of the Duration/ID field, the responding
`STA shall transmit its Control Response and Management Response frames (either CTS or ACK)atthe
`highest rate in the BSS basic rate set that is less than or equal to the rate of atthe-same-rate-as the immedi-
`ately previous frame in the frame exchange sequence(as defined in 9.7). #this-ratebelongstethePHYman-
`
`datery_rates_or_else_at the _hichest pessibleratebelongingtothePHYratesintheBssBasicRateSet_In
`addition, the Control Response frame shall be sent using the same PHY optionsas the received frame.
`
`For the HR/DSSS PHY,the time required to transmit a frame for use in the Duration/ID field is determined
`using the PLME-TXTIME.request primitive and the PLME-TXTIME.confirm primitive, both defined
`in 1.3.4.
`
`10.3.2.2 MLME_scan.confirm
`
`Change "set" to "sets" in the Name and Description columnsfor the PHY ParameterSet.
`
`6
`
`Copyright © 2000 IEEE. All rights reserved.
`
`Authorized licensed use limited to:
`
`Downloaded on January 16,2023 at 15:40:25 UTC from IEEE Xplore. Restrictions apply.
`
`DELL-OZMO-1-002423
`
`
`
`Case 6:22-cv-00642-ADA Document 32-10 Filed 03/31/23 Page 15 of 97
`Case 6:22-cv-00642-AD