IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`segments using similar or dissimilar PHY implementations (e.g., 100BASE—X to 100BASE—X, 100BASE—X
`to 100BASE-T4, etc.). (See IEEE 802.3 clauses 9 and 27.)
`
`1.4.164 Return Loss: In IOBROAD36, the ratio in decibels of the power reflected from a port to the power
`incident to the port. An indicator of impedance matching in a broadband system. (See IEEE 802.3 clause 11.)
`
`1.4.165 router: A layer 3 interconnection device that appears as a MAC to a CSMA/CD collision domain.
`(See IEEE Std 610.7-1995 [Al6].)
`
`1.4.166 Seed: In IOBROAD36, the 23 bits residing in the scrambler shifi register prior to the transmission of
`a packet. (See IEEE 802.3 clause 11.)
`
`1.4.167 Segment Delay Value (SDV): A number associated wit.l1 a given segment that represents the delay
`on that segment including repeaters and end stations, if present, used to assess path delays for 10 Mb/s
`CSMA/CD networks. (See IEEE 802.3, 13.4.)
`
`1.4.168 Segment Variability Value (SVV): A number associated with a given segment that represents the
`delay variability on that segment (including a repeater) for 10 Mb/s CSMA/CD networks. The SVVs for dif-
`ferent segment types are specified in IEEE 802.3 table 13-3. (See IEEE 802.3, 13.4.)
`
`1.4.169 segment: The medium connection, including connectors, between MDIs in a CSMA/CD LAN.
`
`1.4.170 Selector field: A five-bit field in the Base Link Code Word encoding that is used to encode up to 32
`types of messages that define basic abilities. For example, selector field 00001 indicates that the base tech-
`nology is IEEE 802.3. (See IEEE 802.3 clause 28.)
`
`1.4.171 shared service: A CSMA/CD network in which the collision domain consists of more than two
`
`DTEs so that the total network bandwidth is shared among them.
`
`1.4.172 shielded twisted-pair (STP) cable: An electrically conducting cable, comprising one or more ele-
`ments, each of which is individually shielded. There may be an overall shield, in which case the cable is
`referred to as shielded twisted pair cable with an overall shield. (From ISO/IEC 11801: 1995.) Specifically
`for IEEE 802.3 100BASE-TX, 150 Q balanced inside cable with performance characteristics specified to
`100 MHz (i.e., performance to Class D link standards as per ISO/IEC 11801: 1995). In addition to the
`requirements specified in ISO/IEC 11801: 1995, IEEE 802.3 clauses 23 and 25 provide additional perfor-
`mance requirements for 100BASE-T operation over STP.
`
`1.4.173 Simplex Fiber Optic Link Segment: A single fiber path between two MAUs or PHYS, including
`the terminating connectors, consisting of one or more fibers joined serially with appropriate connection
`devices, for example, patch cables and wall plates. (See IEEE 802.3 clause 15.)
`
`1.4.174 simplex link segment: A path between two MDIs, including the terminating connectors, consisting
`of one or more segments of twisted pair cable joined serially with appropriate connection devices, for exam-
`ple, patch cords and wall plates. (See IEEE 802.3 figure 14-2.)
`
`1.4.175 skew between pairs: The diiference in arrival times of two initially coincident signals propagated
`over two different pairs, as measured at the receiving end of the cable. Total skew includes contributions
`from transmitter circuits as well as the cable.
`
`1.4.176 special link (SL): A transmission system that replaces the normal medium. (See IEEE 802.3, 12.8.)
`
`1.4.177 Spectral Width, Full-Width Half Maximum (FWI-IlVI): The absolute difi‘erence between the
`wavelengths at which the spectral radiant intensity is 50% of the maximum. (See IEEE 802.3 clause 15.)
`
`This is anlgtrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`t 1025
`0033
`
`Aerohive - Exhibit 1025
`
`0033
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`1.4.178 spectrum mask: A graphic representation of the required power distribution as a function of fre-
`quency for a modulated transmission.
`
`1.4.179 star quad: A cable element that comprises four insulated connectors twisted together. Two diamet-
`rically facing conductors form a transmission pair. Note—Cables containing star quads can be used inter-
`changeably with cables consisting of pairs, provided the electrical characteristics meet
`the same
`specifications. O7rom ISO/IEC 11801: 1995.)
`
`1.4.180 Start-of-Stream Delimiter (SSD): A pattern of defined code words used to delineate the boundary
`of a data transmission sequence on the Physical Layer stream. The SSD is unique in that it may be recog-
`nized independent of previously defined code-group boundaries and it defines subsequent code-group
`boundaries for the stream it delimits. For 100BASE-T4, SSD is a pattern of three predefined sosb code-
`groups (one per wire pair) indicating the positions of the first data code-group on each wire pair. For
`l00BASE-X, SSD consists of tlie code-group sequence /J/K/.
`
`1.4.181 stream: The Physical Layer encapsulation of a MAC frame. Depending on the particular PHY, the
`MAC fi‘ame may be modified or have information appended or prepended to it to facilitate transfer through
`the PMA. Any conversion from a MAC fi'ame to a PHY stream and back to a MAC frame is transparent to
`the MAC. (See IEEE 802.3 clauses 23 and 24.)
`
`1.4.182 symbol: The smallest unit of data transmission on the medium. Symbols are unique to the coding
`system employed. 100BASE-T4 uses ternary symbols; 10BASE-T and IOOBASE-X use binary symbols or
`code bits.
`
`1.4.183 symbol rate (SR): The total number of symbols per second transferred to or fi'om the Media Depen-
`dent Interface (MDI) on a single wire pair. For 100BASE-T4,
`the symbol rate is 25 megabaud; for
`IOOBASE-X, the symbol rate is 125 megabaud.
`
`1.4.184 symbol time (ST): The duration of one symbol as transferred to and from the MDI via a single wire
`pair. The symbol time is the reciprocal of the symbol rate.
`
`1.4.185 Technology Ability Field: An eight-bit field in the Auto-Negotiation base page that is used to indi-
`cate the abilities of a local station, such as support for 10BASE-T, l00BASE-TX, 100BASE-T4, as well as
`fi1ll-duplex capabilities.
`
`1.4.186 ternary symbol: In 100BASE-T4, a ternary data element. A ternary symbol can have one of three
`values: -1, 0, or +1. (See IEEE 802.3 clause 23.)
`
`1.4.187 translation: In a single—cable IOBROAD36 system, the process by which incoming transmissions at
`one frequency are converted into another frequency for outgoing transmission. The translation takes place at
`the headend. (See IEEE 802.3 clause 11.)
`
`1.4.188 truncation loss: In a modulated data waveform, the power difierence before and after implementa-
`tion filtering necessary to constrain its spectrum to a specified frequency band.
`
`1.4.189 trunk cable: The main (often large diameter) cable of a coaxial cable system. (See: drop cable.)
`
`1.4.190 twisted-pair cable binder group: A group of twisted pairs within a cable that are bound together.
`Large telephone cables have multiple binder groups with high interbinder group near-end crosstalk loss.
`
`1.4.191 twisted-pair cable: A bundle of multiple twisted pairs within a single protective sheath. O7rom ISO/
`IEC11801: 1995.)
`
`1.4.192 twisted-pair link: A twisted-pair cable plus connecting hardware. (From ISO/IEC 11801: 1995.)
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`0034
`
`1025
`
`Aerohive - Exhibit 1025
`
`0034
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`1.4.193 twisted-pair link segment: In 100BASE—T, a tvvisted-pair link for connecting two PHYS.
`
`1.4.194 twisted pair: A cable element that consists of two insulated conductors twisted together in a regular
`fashion to form a balanced transmission line. (From ISO/IEC 11801: 1995.)
`
`1.4.195 Unformatted Page (UP): A Next Page encoding that contains an unformatted 12-bit message field.
`Use of this field is defined through Message Codes and information contained in the UP. (See IEEE 802.3,
`28.2.1.2.)
`
`1.4.196 unshielded twisted-pair cable (UTP): An electrically conducting cable, comprising one or more
`pairs, none of which is shielded. There may be an overall shield, in which case the cable is referred to as
`unshielded twisted pair with overall shield. (From ISO/IEC 11801: 1995.)
`
`1.4.197 weight of 6T code group: The algebraic sum of the logical ternary symbol values listed in the
`l00BASE—T4 8B6T code table. (See IEEE 802.3 clause 23.)
`
`Remove the definitions from 7.1.1, 8.1.2, 9.2, 10.1.2, 11.1.2, 12.1.3, 13.2, 14.1.2, 15.1.2, and 19.1.3 and
`insert thefollowing text under each ofthese subclauses:
`
`See 1.4.
`
`This is anlgrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`"t 1025
`0035
`
`Aerohive - Exhibit 1025
`
`0035
`
`

`
`IEEE
`Std 802.3u-1995
`
`CSMA/CD
`
`2. MAC service specification
`
`Replacefigure 2-1 with thefollowing:
`
`OSI
`REFERENCE
`MODEL
`LAYERS
`
`LAN
`CSMNCD
`LAYERS
`
`HIGHER LAYERS
`
`LLC—LOG|CAL LINK CONTROL
`
`MAC—MED|A ACCESS CONTROL
`
`PHY
`
`1 Mbls. 10 Mbls
`
`10 Mbls
`
`100 Mbls
`
`Au| = ATTACHMENT UNIT INTERFACE
`MDI = MEDIUM DEPENDENT INTERFACE
`M" = MED|A WDEPENDENT |NTER|=AcE
`MAU = MEDIUM ATTACHMENT UNIT
`
`PLS = PHYSICAL LAYER SIGNALING
`PCS = PHYSICAL CODING SUBI-AYER
`PMA = PHYSICAL MEDIUM ATTACHMENT
`PHY = PHYSICAL LAYER DEVICE
`PMD = PHYSICAL MEDIUM DEPENDENT
`
`NOTE—The three types of layers below the MAC sublayer are mutually independent.
`
`* AUI is optional for 10 Mbls systems and is not specified for 1 Mbls and 100 Mbls systems.
`** MII is optional for 10 Mbls DTEs and for 100 Mbls systems and is not specified for 1 Mbls systems.
`*** PMD is specified for 100BASE-X only; 100BASE-T4 does not use this layer.
`For an exposed AUI residing below an Mll, see 22.5.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standgrd.
`
`0036
`
`1025
`
`Aerohive - Exhibit 1025
`
`0036
`
`

`
`IEEE
`Std 8D2.3u—1995
`
`4. Media Access Control
`
`Replarefigure 4-1 with thefollowirrg:
`OSI
`
`REFERENCE
`MOD EL
`LAYERS
`
`APPLICATION
`
`PRESENTATION
`
`SESSION
`TRANSPORT
`
`NETWORK
`
`x
`
`DATA LINK
`
`PHYSICAL
`
`PMA
`
`'A”I—*
`MAU{
`Mm _,
`é MEDIUM;
`1 Mhfs, 10 Mbfs
`
`SUPPLEMENT TO 802.3:
`
`LAN
`CSMN-CD
`LAYERS
`
`HIGHER LAYERS
`
`LLC—LOG|CAL LINK CONTROL
`
`MAC—MEDIA ACCESS CONTROL
`RECONCILIATION
`RECONCILIATION
`I
`I
`
`..M”_,:
`
`‘
`PLS
`I
`"°‘”' ‘I’.
`PMA
`
`MD, __I_
`
`10 Mbfs
`
`...M"__*
`
`PCS
`PMA
`""'PMD
`Mm _,
`MEDIUM?
`100 Mbfs
`
`AUI : ATTACHMENT UNIT INTERFACE
`MDI : MEDIUM DEPENDENT INTERFACE
`MII = MEDIA INDEPENDENT INTERFACE
`MAU = MEDIUM ATTACHMENT UNIT
`
`PLS = PHYSICAL LAYER SIGNALING
`PCS = PHYSICAL CODING SUBLAYER
`PMA = PHYSICAL MEDIUM ATIACHMEHT
`PHY = PHYSICAL LAYER DEVICE
`PMD = PHYSICAL MEDIUM DEPENDENT
`
`NOTE—The three types of layers below the MAC sublayer are mutually independent.
`
`“ AUI is optional for1Cl Mbls systems and is not specified for 1 Mbfs and 100 Mbfs systems.
`“* MII is optional for 10 Mbfs DTEs and for 100 Mbfs systems and is not specified for 1 Mbfs systems.
`“"" PMD is specified for 1[]I]BASE—X only; 1D[]BASE—T4 does not use this layer.
`For an exposed AUI residing below an MIL see 2.5.
`
`Figure 4-1—|'II|AC sublayer partitioning, relationship to the ISO Open Systems
`Interconnection (08!) reference model
`
`Add to 4.4.2 rhefallowing subclause:
`
`4.4.2.3 Parameterized values
`
`The following parameter values shall be used for 100 ‘\/Ibis implementations:
`
`Parameters
`
`s1etTi.u1e
`
`interFrameGap
`attemptLim.it
`backofl‘l.i.I:J.it
`
`jamSize
`maxF1‘ameSize
`
`mJ'nFran1eSize
`addressSize
`
`512 bit times
`
`0.96 Its
`16
`10
`
`32 bits
`1518 octets
`
`512 bits (64 octets)
`48 bits
`
`WARNTNG—1-‘my deviation from the above specified values may afleet proper operation of the network.
`
`This is angarchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`Aerohive - Exhibit
`
`Aerohive - Exhibit 1025
`
`0037
`
`

`
`CSMA/CD
`
`5. Layer management
`
`Insert before 5.1:
`
`Clause 5 is deprecated by clause 30.
`
`IEEE
`Std 802.3u-1995
`
`14. Twisted-pair Medium Attachment Unit (MAU) and baseband medium,
`Type 10BASE-T
`
`EDITORIAL NOTE—The following changes add references to Auto-Negotiation and specifications for Auto-Negotia-
`tion to the appropriate places in clause 14 of ISO/IEC 8802-3: 1993 [ANSI/IEEE Std 802.3-1993 Edition] and IEEE Std
`802.31-1992. (These changes will also identically affect the 1995 edition of ISO/IEC 8802-3.) The changes do not alter
`the specifications for existing systems.
`
`In 14.2, renumber the list items (1) through (7) as a) through g) and add the following paragraph as the
`eighth functional capability:
`
`h) Auto-Negotiation. Optionally provides the capability for a device at one end of a link segment to
`advertise its abilities to the device at the other end (its link partner), to detect information defining
`the abilities of the link partner, and to determine if the two devices are compatable.
`
`Add to 14.2.1 the following sentence to the end of the paragraph:
`
`The MAU may optionally provide the Auto-Negotiation algorithm. When provided, the Auto-Negotiation
`algorithm shall be implemented in accordance with clause 28.
`
`Add to 14.2.1.1 thefollowingparagraph after thefourth paragraph:
`
`For a MAU that implements the Auto-Negotiation algorithm defined in clause 28, clause 28 shall define the
`allowable transmitted link pulse sequence.
`
`Add to 14.2.1. 7 thefollowing sentence at the end ofthefourth paragraph:
`
`For a MAU that implements the Auto-Negotiation algorithm defined in clause 28, the MAU shall enter the
`LINK TEST FAIL RESET state at power—on as specified in clause 28. For a MAU that does not implement
`the Auto-Negotiation algorithm defined in clause 28, it is highly recommended that it also power-on in the
`LINK TEST FAIL RESET state, although implementations may power-on in the LINK TEST PASS state.
`For a MAU that implements the Auto-Negotiation ftmction defined in clause 28, the Auto-Negotiation Tech-
`nology Dependent Interface shall be supported. Supporting the Technology Dependent Interface requires
`that in the Link Integrity Test function state diagram ’1ink_status=OK’ is added to the LINK TEST PASS
`state and ’link_status=FAIL’ is added to the LINK TEST FAIL RESET state. Note these ISO message vari-
`ables follow the conventions of clause 21.
`
`Add to 14.3.1.2.1 the following paragraph after the sixth paragraph:
`
`For a MAU that implements the Auto-Negotiation algorithm defined in clause 28, the FLP Burst Sequence
`will consist of multiple link test pulses. All link test pulses in the FLP Burst sequence shall meet the template
`requirements of figure 14-12 when measured across each of the test loads defined in figure 14-11; both with
`the load connected directly to the TD circuit and with the load connected through the twisted—pair model as
`defined in figures 14-7 and 14-8.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standgrd.
`
`0038
`
`it 1025
`
`Aerohive - Exhibit 1025
`
`0038
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`Add to 14.10.4.5.1 thefollowing entry as the eighth parameter:
`
` Auto-Negotiation
`
`Function provided by MAUs
`implementing the Auto-Nego-
`tiation algorithm, as defined in
`clause 28
`
`C
`
`Add this new subclause after 14.1 0.4. 7:
`
`14.10.4.8 PICS proforma tables for Auto-Negotiation-able MAUs
`
`The following are conditional on whether the Auto-Negotiation algorithm is provided (clause 28).
`
`Parameter
`
`Section
`
`Value/Comment
`
`TP_IDL
`
`Link Integrity Test Function
`State Diagram power-on
`default
`
`Link Test Fail state exit condi-
`tions
`
`Technology Dependent Inter-
`face support
`
`Link test pulse waveform for
`FLP Burst with and without
`twisted-pair model
`
`Defined in clause 28.2.1
`
`Power-on in Link Test Fail
`Reset state
`
`autoneg_wait_timer expired
`and either RD = active or con-
`secutive link test pulses =
`3 min., 10 max
`
`In the Link Integrity Test state
`diagram function
`’link_status=OK’ is added to
`the LINK TEST PASS state
`and ’link_status=FAIL’ is
`added to the LINK TEST FAIL
`RESET state
`
`Within figure 14-10 template
`for, all pulses in FLP Burst,
`overshoot S +50 mV after
`excursion below -50 mV
`
`19. Layer management for 10 Mbls baseband repeaters
`
`EDITORIAL NOTE—This clause can be found in IEEE Std 802.3k-1992.
`
`Insert the following phrase in from 0f19.1:
`
`Clause 19 is deprecated by clause 30.
`
`This is an2¢\rchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`0039
`
`Aerohive - Exhibit 1025
`
`0039
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`20. Layer management for 10 Mbls baseband Medium Attachment Units
`(MAUs)
`
`EDITORIAL NOTE—This clause can be found in IEEE Stds 802.3p&q-1993.
`
`Insert the following phrase in front of20.1:
`
`Clause 20 is deprecated by clause 30.
`
`Annex A
`
`(informative)11
`
`Additional reference material
`
`EDITORIAL NOTES
`
`1—This clause was changed from Annex to Annex A by IEEE Std 802.3j-1993.
`2—In the following references, changes are not indicated by strikethroughs and underscores.
`
`3::Tg18e0r2ei:'frence numbers in this armex do not correspond to those ofISO/IEC 8802-3: 1993 or the 1995 edition ofISO/
`IE
`-
`.
`
`Replace annexA with thefollowing:
`
`[A1] ANSI/EIA 364A: 1987, Standard Test Procedures for Low-Frequency O3elow 3 MHz) Electrical Con-
`nector Test Procedure.
`
`[A2] ANSI/EIA 455-34: 1985, Fiber Optics—Interconnection Device Insertion Loss Test.
`
`[A3] ANSI/EIA/TIA 455-59-1989, Measurement of Fiber Point Defects Using an Optical Time Domain
`Reflectometer (ODTR).
`
`[A4] ANSI/EIA/TIA 455-180-1990, FOTP-180, Measurement of the Optical Transfer Coefiicients of a Pas-
`sive Branching Device (Coupler).
`
`[AS] ANSI/EIA/TIA 526-14-1990, Optical Power Loss Measurements of Installed Multimode Fiber Cable
`Plant.
`
`[A6] ANSI/EIA/TIA 568-1991, Commercial Building Telecommunications Wiring Standard.
`
`[A7] ANSI/IEEE Std 770X3.97-1983, IEEE Standard Pascal Computer Programming Language.”
`
`[A8] ANSI/NFPA 70-1993, National Electrical Code.
`
`[A9] ANSI/UL 94-1990, Tests for Flammability of Plastic Materials for Parts in Devices and Appliances.
`
`[A10] ANSI/UL 114-1982, Safety Standard for Oflice Appliances and Business Equipment.”
`
`“This annex is informative for the International Standard but normative for IEEE Std 802.3.
`IZANSI/IEEE Std 770X3.97-1983 has been withdrawn; however, copies can be obtained fi'om Global Engineering, 15 Inverness Way
`East, Englewood, CO 80112-5704, USA, tel. (303) 792-2181.
`BANS]/UL 114-1982 was withdrawn and replaced by ANSI/UL 1950-1994.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standgrd.
`
`it 1025
`
`0040
`
`
`
`Aerohive - Exhibit 1025
`
`0040
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`[A1 1] ANSI/UL 478-1979, Safety Standard for Electronic Data—Processing Units and Systems.”
`
`[A12] ANSI/UL 1950-1994, Safety Standard for Information Technology Equipment Including Electrical
`Business Equipment.
`
`[A13] ECMA-97 (1985), Local Area Networks Safety Requirements.
`
`[A14] EIA CB8-1981, Components Bulletin (Cat 4) List of Approved Agencies, US and Other Countries,
`Impacting Electronic Components and Equipment.
`
`[A15] FCC Docket 20780-1980 (Part 15), Technical Standards for Computing Equipment. Amendment of
`Part 15 to redefine and clarify the rules governing restricted radiation devices and low-power communication
`devices. Reconsidered First Report and Order, April 1980.
`
`[A16] IEEE Std 610.7-1995, IEEE Standard Glossary of Computer Networking Terminology.
`
`[A17] IEEE Std 802.9a-1995, IEEE Standards for Local and Metropolitan Area Networks: Integrated Ser-
`vices (IS) LAN: IEEE 802.9 Isochronous Services with Carrier Sense Multiple Access with Collision Detec-
`tion (CSMA/CD) Media Access Control (MAC) service.”
`
`[A18] IEEE P1394/D8.0v3, Draft Standard for a High-Performance Serial Bus (July 7, 1995).
`
`[A19] MIL-C-17F-1983, General Specification for Cables, Radio Frequency, Flexible and Semirigid.
`
`[A20] MIL-C-24308B-1983, General Specifications for Connector, Electric, Rectangular, Miniature Polar-
`ized Shell, Rack and Panel.
`
`[A21] AMP, Inc., Departmental Publication 5525, Design Guide to Coaxial Taps. Harrisburg, PA 17105,
`USA.
`
`[A22] AMP, Inc., Instruction Sheet 6814, Active Tap Installation. Harrisburg, PA 17105, USA.
`
`[A23] Brinch Hansen, P. The Architecture of Concurrent Programs. Englewood Cliffs, NJ: Prentice Hall,
`1977.
`
`[A24] Digital Equipment Corporation, Intel, Xerox, The Ethernet, Version 2.0, November 1982.
`
`[A25] Hammond, J. L., Brown, J. E., and Liu, S. S. Development of a Transmission Error Model and Error
`Control Model. Technical Report RADC-TR-75-138. Rome: Air Development Center (1975).
`
`[A26] Shoch, J. F., Dalal, Y. K., Redell, D. D., and Crane, R. C., “The Evolution of Ethemet,” Computer
`Magazine, August 1982.
`
`[A27] UL Subject No 758: UL VW-1, Description ofAppliance Wiring Material.
`
`14ANsI/UL 478-1979 was withdrawn and replaced by ANSI/UL 1950-1994.
`15As this standard goes to press, IEEE Std 802.9a-1995 is approved but not yet published. The approved drafi standard is, however,
`available from the IEEE. Anticipated publication date is early 1996. Contact the IEEE Standards Department at 1 (908) 562-3800 for
`status information.
`
`This is an2Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`0041
`
`1025
`
`Aerohive - Exhibit 1025
`
`0041
`
`

`
`CSMA/CD
`
`Annex D
`
`(normative)
`
`IEEE
`Std 802.3u-1995
`
`GDMO specifications for CSMA/CD managed objects
`
`EDITORIAL NOTE—This annex can be found in IEEE Stds 802.3p&q-1993.
`
`Insert the following note at three places immediatelyfollowing the headings D1, D2, and D3:
`
`NOTE—'I'he arcs (that is, object identifier values) defined in annex 30A deprecate the arcs previously defined in D1
`(Layer Management), D2 (Repeater Management), and D3 (MAU Management). See IEEE Std 802.1F-1993, axmex C4.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standgrd.
`
`0042
`
`t 1025
`
`Aerohive - Exhibit 1025
`
`0042
`
`

`
`IEEE Standards for Local and Metropolitan Area Networks:
`
`Supplement to Carrier Sense Multiple Access with Collision
`Detection (CSMAICD) Access Method and Physical Layer
`Specifications
`
`Media Access Control (MAC) Parameters, Physical
`Layer, Medium Attachment Units, and Repeater for
`100 Mbls Operation,Type 100BASE-T (Clauses 21-30)
`
`21. Introduction to 100 Mbls baseband networks, type 100BASE-T
`
`21.1 Overview
`
`100BASE-T couples the ISO/IEC 8802-3 CSMA/CD MAC with a family of 100 Mb/s Physical Layers.
`While the MAC can be readily scaled to higher performance levels, new Physical Layer standards are
`required for 100 Mb/s operation.
`
`The relationships between 100BASE-T, the existing ISO/IEC 8802-3 (CSMA/CD MAC), and the ISO Open
`System Interconnection (OSI) reference model is shown in figure 21-1.
`
`100BASE-T uses the existing ISO/IEC 8802-3 MAC layer interface, connected through a Media-Indepen-
`dent Interface layer to a Physical Layer entity (PHY) sublayer such as l00BASE-T4, 100BASE-TX, or
`100BASE-FX.
`
`100BASE-T extends the ISO/IEC 8802-3 MAC to 100 Mb/s. The bit rate is faster, bit times are shorter,
`packet transmission times are reduced, and cable delay budgets are smaller—all in proportion to the change
`in bandwidth. This means that the ratio of packet duration to network propagation delay for 100BASE-T is
`the same as for IOBASE-T.
`
`21.1.1 Reconciliation Sublayer (RS) and Media Independent Interface (Mll)
`
`The Media Independent Interface (clause 22) provides an interconnection between the Media Access Con-
`trol OVIAC) sublayer and Physical Layer entities (PHY) and between PHY Layer and Station Management
`(STA) entities. This MH is capable of supporting both 10 Mb/s and 100 Mb/s data rates through four bit
`wide (nibble wide) transmit and receive paths. The Reconciliation sublayer provides a mapping between the
`signals provided at the MII and the MAC/PLS service definition.
`
`21.1.2 Physical Layer signaling systems
`
`This standard specifies a family of Physical Layer implementations. l00BASE-T4 (clause 23) uses four
`pairs of ISO/IEC 11801: 1995 Category 3, 4, or 5 balanced cable. 100BASE-TX (clauses 24 and 25) uses
`two pairs of Category 5 balanced cable or 150 Q shielded balanced cable as defined by ISO/IEC
`11801: 1995. 100BASE-FX (clauses 24 and 26) uses two multi-mode fibers. FDDI (ISO 9314 and ANSI
`X3T12) Physical Layers are used to provide 100BASE-TX and 100BASE-FX physical signaling channels,
`which are defined in IOOBASE-X (clause 24).
`
` 1025
`
`0043
`
`Aerohive - Exhibit 1025
`
`0043
`
`

`
`IEEE
`Std 802.3u-1995
`
`03'
`REFERENCE
`MODEL
`LAYERS
`
`LAN
`CSIVWCD
`LAYERS
`HIGHER LAYERS
`
`SUPPLEMENT TO 802.3:
`
`
`
`***AUTONEG
`
`***AUTONEG
`
`100BASE-T
`Baseband
`Repeater
`
`PHY Set
`
`100 Mb/S link Segment
`
`100 Mb/s link segment
`
`MDI = MEDIUM DEPENDENT INTERFACE
`MII = MEDIA INDEPENDENT INTERFACE
`
`PCS = PHYSICAL CODING SUBLAYER
`PMA = PHYSICAL MEDIUM ATTACHMENT
`PHY = PHYSICAL LAYER DEVICE
`PMD = PHYSICAL MEDIUM DEPENDENT
`
`* Mll is optional for 10 Mb/s DTEs and for 100 Mb/s systems and is not specified for 1 Mb/s systems.
`** PMD is specified for 100BASE-X only; 100BASE-T4 does not use this layer.
`Use of MII between PCS and Baseband Repeater Unit is optional.
`*** AUTONEG is optional.
`
`21.1.3 Repeater
`
`Repeater sets (clause 27) are an integral part of any l00BASE-T network with more than two DTEs in a col-
`lision domain. They extend the physical system topology by coupling two or more segments. Multiple
`repeaters are permitted within a single collision domain to provide the maximum path length.
`
`21.1.4 Auto-Negotiation
`
`Auto-Negotiation (clause 28) provides a linked device with the capability to detect the abilities (modes of
`operation) supported by the device at the other end of the link, determine comrnon abilities, and configure
`for joint operation. Auto-Negotiation is performed out-of-band using a pulse code sequence that is compati-
`ble with the IOBASE-T link integrity test sequence.
`
`21.1.5 Management
`
`Managed objects, attributes, and actions are defined for all l00BASE-T components (clause 30). This clause
`consolidates all IEEE 802.3 management specifications so that 10 Mb/s, 100 Mb/s or 10/100 Mb/s agents
`can be managed by existing 10 Mb/s—only network management stations with little or no modification to the
`agent code.
`
`This is anzgrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`
`
`it 1025
`
`
`0044
`
`Aerohive - Exhibit 1025
`
`0044
`
`

`
`CSMNCD
`
`21.2 Abbreviations
`
`This document contains the following abbreviations:
`
`IEEE
`Std 802.3u-1995
`
`8802-3
`8802-5
`ASIC
`ASN.1
`AUI
`
`BPSK
`BR
`BT
`
`CAT3
`CAT4
`CAT5
`CDO
`CD1
`
`CMIP
`CMIS
`CMOS
`CRC
`CVH
`CVL
`CRV
`
`CSO
`CS1
`CW
`
`DTE
`ELFEXT
`ESD
`
`FCS
`FDDI
`FEXT
`
`FIFO
`FLP
`FOIRL
`FOMAU
`FOMDI
`FOPMA
`HH
`IH
`
`IPG
`IRL
`LAN
`
`LLC
`LSDV
`MAC
`MAU
`
`ISO/[EC 8802-3 OEEE Std 802.3)
`ISO/IEC 8802-5 (IEEE Std 802.5)
`application-specific integrated circuit
`abstract syntax notation one as defined in ISO/IEC 8824: 1990
`attachment unit interface
`
`binary phase shift keying
`bit rate
`bit time
`
`Category 3 balanced cable
`Category 4 balanced cable
`Category 5 balanced cable
`clocked data zero
`clocked data one
`
`common management information protocol as defined in ISO/IEC 9596-1: 1991
`common management information service as defined in ISO/IEC 9595: 1991
`complimentary metal oxide semiconductor
`cyclic redundancy check
`clocked violation high
`clocked violation low
`code rule violation
`
`control signal zero
`control signal one
`continuous wave
`
`data terminal equipment
`equal—leve1 far—end crosstalk
`end of stream delimiter
`
`frame check sequence
`fibre distributed data interface
`far—end crosstalk
`
`first in, first out
`fast link pulse
`fiber optic inter—repeater link
`fiber optic medium attachment unit
`fiber optic medium dependent interface
`fiber optic physical medium attachment
`header hub
`intermediate hub
`
`inter-packet gap
`inter—repeater link
`local area network
`
`logical link control
`link segment delay value
`medium access control
`medium attachment unit
`
`MC
`MDELFEXT
`MDFEXT
`MDI
`MDNEXT
`MIB
`
`message code
`multiple-disturber equal-level far—end crosstalk
`multiple-disturber far—end crosstalk
`medium dependent interface
`multiple-dist11rber near-end crosstalk
`management information base
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standgrd.
`
`0045
`
`it 1025
`
`Aerohive - Exhibit 1025
`
`0045
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`MII
`MP
`NEXT
`
`NLP
`NPA
`NRZI
`
`PCS
`PDV
`PHY
`PICS
`PLS
`PMA
`PMD
`PMI
`PVV
`RS
`SSD
`
`SDV
`SFD
`
`SR
`ST
`STA
`STP
`SVV
`UCT
`
`UP
`UTP
`
`media independent interface
`message page
`near-end crosstalk
`
`normal link pulse
`next page algorithm
`non return to zero and invert on ones
`
`physical coding sublayer
`path delay value
`Physical Layer entity sublayer
`protocol implementation conformance statement
`physical signaling sublayer
`physical medium attachment
`physical medium dependent
`physical medium independent
`path variability value
`reconciliation sublayer
`start-of-stream delimiter
`
`segment delay value
`start-of-frame delimiter
`
`symbol rate
`symbol time
`station management entity
`shielded twisted pair (copper)
`segment variability value
`unconditional transition
`
`unformatted page
`unshielded twisted pair
`
`21.3 References
`
`References are shown beginning on pages 2 and 23 of this document (as updates to 1.3 and annex A).
`
`21.4 Definitions
`
`Definitions are shown beginning on page 5 of this document (as an update to 1.4).
`
`21.5 State diagrams
`
`State machine diagrams take precedence over text.
`
`The conventions of 1.2 are adopted, with the following extensions.
`
`21.5.1 Actions inside state blocks
`
`The actions inside a state block execute instantaneously. Actions inside state blocks are atomic (i.e., uninter-
`ruptible).
`
`After performing all the actions listed in a state block one time, the state block then continuously evaluates
`its exit conditions until one is satisfied, at which point con1:rol passes through a transition arrow to the next
`block. While the state awaits fiilfillrnent of one of its exit conditions, the actions inside do not implicitly
`repeat.
`
`This is an3Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`
`
`Aerohive - Exhibit 1025
`
`0046
`
`

`
`CSMNCD
`
`IEEE
`Std 802.3u-1995
`
`The characters 0 and [bracket] are not used to denote any special meaning.
`
`Valid state actions may include .indicate and request messages.
`
`No actions are taken outside of any state block.
`
`21.5.2 State diagram variables
`
`Once set, variables retain their Values as long as succeeding blocks contain no references to them.
`
`Setting the parameter of a formal interface message assures that, on the next transmission of that message,
`the last parameter value set will be transmitted.
`
`Testing the parameter of a formal interface messages tests the value of that message parameter that was
`received on the last transmission of said message. Message parameters may be assigned default values that
`persist until the first reception of the relevant message.
`
`21.5.3 State transitions
`
`The following terms are valid transition qualifiers:
`
`Boolean expressions
`a)
`b) An event such as the expiration of a timer: timer_done
`c) An event such as the reception of a message: PMA_UNITDATA.indicate
`d) An unconditional transition: UCT
`e) A branch taken when other exit conditions are not satisfied: ELSE
`
`Any open arrow (an arrow with no source block) represents a global transition. Global transitions are evalu-
`ated continuously whenever any state is evaluating its exit conditions. When a global transition becomes
`true, it supersedes all other transitions, including UCT, returning control to the block pointed to by the open
`arrow.
`
`21.5.4 Operators
`
`The state machine operators are shown in table 21-1.
`
`Table 21-1—State machine operators
`
`
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standgrd.
`
`0047
`
`1025
`
`Aerohive - Exhibit 1025
`
`0047
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`21.6 Protocol Implementation Conformance Statement (PICS) proforma
`
`21.6.1 Introduction
`
`The supplier of a protocol implementation that is claimed to conform to any part of the IEEE 802.3u
`IOOBASE-T clauses 21 through 30 shall complete a Protocol Implementation Conformance Statement
`(PICS) proforma.
`
`A completed PICS proforma is the PICS for the implementation in question. The PICS is a statement of
`which capabilities and options of the protocol have been implemented. A PICS is included at the end of each
`clause as appropriate. The PICS can be used for a variety of purposes by various parties, including the
`following:
`
`a)
`
`As a checklist by the protocol implementor, to reduce the risk of failure to conform to the standard
`through oversight;
`b) As a detailed indication of the capabilities of the implementation, stated relative to the common
`basis for understanding provided by the standard PICS proforma, by the supplier and acquirer, or
`potential acquirer, of the implementation;
`c) As a basis for initially checking the possibility of interworking with another implementation by the
`user, or potential user, of the implementation (note that, while interworking can never be guaranteed,
`failure to interwork can o