IEEE
`Std 802.3u-1995
`
`BEHAVIOUR DEFINED AS:
`
`SUPPLEMENT TO 802.3:
`
`If the MAU is a link or fiber type (FOIRL, 10BASE-T, IOBASE-F), then this is equivalent to the
`link test fail state/low light function. For an AUI , 10BASE2, l0BASE5, or l0BROAD36 MAU,
`this indicates whether or not loopback is detected on the DI circuit. The Value ofthis attribute persists
`between packets for MAU types AUI, l0BASE5, l0BASE2, l0BROAD36, and 10BASE-FP.
`At power-up or following a reset, the value ofthis attribute will be “unknown” for AUI, l0BASE5 ,
`l0BASE2, l0BROAD36, and 10BASE-FP MAUs. For these MAUs loopback will be tested on
`each transmission during which no collision is detected. If D1 is receiving input when DO returns
`to IDL after a transmission and there has been no collision during the transmission, then loopback
`will be detected. The value of this attribute will only change during noncollided transmissions for
`AUI, IOBASE2, 10BASE5, l0BROAD36, and 10BASE-FP MAUs.
`For l00BASE-T4, IOOBASE-TX, and 100BASE-FX the enumerations match the states within the
`respective link integrity state diagrams, figure 23-12 and 24-15. Any MAU that implements
`management of clause 28 Auto-Negotiation will map remote fault indication to MediaAvailable
`remote fault.
`
`The enumeration “remote fault” applies to IOBASE-FB, 100BASE—X, far-end fault indication and
`non-specified remote faults from a system running clause 28 Auto-Negotiation. The enumerations
`“remote jabber,” “remote link loss,” or “remote test” should be used instead of “remote fault” where
`the reason for remote fault is identified in the remote signaling protocol.
`Where a clause 22 MII is present, a logic one in the remote fault bit (22.2.4.2.9) maps to the
`enumeration “remote fault,” a logic zero in the link status bit (22.2.4.2.11) maps to the enumeration
`“not available.” The enumeration “not available” takes precedence over “remote fault”;
`
`30.5.1.1 .5 aLoseMediaCounter
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`Generalized nonresettable counter. This counter has a maximum increment rate of 10 counts per
`second
`
`BEHAVIOUR DEFINED AS:
`Counts the number of times that the MAU leaves
`
`MediaAvailState “available.” Mandatory for MAU type “AUI,” optional for all others.;
`
`30.5.1.1.6 aJabber
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`A SEQUENCE of two indications. The first, IabberFlag, consists of an ENUMERATED value list
`that has the following entries:
`other
`undefined
`
`initializing, true state not yet known
`unknown
`state is true or normal
`normal
`state is false, fault, or abnormal
`fault
`The second, jabberCounter, is a generalized nonresettable counter. This counter has a maximum
`increment rate of 40 counts per second
`BEHAVIOUR DEFINED AS:
`
`If the MAU is in the JABBER state, the jabberFlag portion of the attribute is set to the “fault”
`value. The jabberCounter portion of the attribute is incremented each time the flag is set to the
`“fault” value. This attribute returns the value “other” for type AUI. Note that this counter will not
`increment for a 100 Mb/s PHY, as there is no defined JABBER state.;
`
`This is an3Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`0346
`
`t 1025
`
`Aerohive - Exhibit 1025
`
`0346
`
`

`
`IEEE
`Std 802.3u-1995
`
`CSMA/CD
`
`30.5.1.1 .7 aMAUAdminState
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`An ENUIVEERATED value list that has the following entries:
`other
`undefined
`
`initializing, true state not yet known
`unknown
`powered and connected
`operational
`inactive but on
`standby
`similar to power down
`shutdown
`BEHAVIOUR DEFINED AS:
`
`A MAU in management state “standby” forces DI and CI to idle and the media transmitter to idle
`or fault, if supported. The management state “standby” only applies to link type MAUs. The state
`of MediaAvailable is unaffected. A MAU or AUI in the management state “shutdown” assumes
`the same condition on DI, CI and the media transmitter as if it were powered down or not
`connected. For an AUI, this management state will remove power from the AUI. The MAU may
`return the value “undefined” for Jabber and MediaAvailable attributes when it is in this
`
`management state. A MAU in the management state “operational” is fully functional, and operates
`and passes signals to its attached DTE or repeater port in accordance with its specification.;
`
`30.5.1.1.8 aBbMAUXmitRcvSplitType
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`An ENUMERATED value list that has the following entries:
`other
`undefined
`
`single-cable system
`single
`dual-cable system, offset normally zero
`dual
`BEHAVIOUR DEFINED AS:
`
`Returns a value that indicates the type of frequency multiplexing/cabling system used to separate
`the transmit and receive paths for the IOBROAD36 MAU. All other types return “undefined”;
`
`30.5.1.1.9 aBroadbandFrequencies
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`A SEQUENCE of two instances of the type INTEGER.
`
`The first INTEGER represents the Transmitter Carrier Frequency. The value of its INTEGER
`represents the frequency of the carrier divided by 250 kHz.
`
`The second INTEGER represents the Translation Offset Frequency. The value of its INTEGER
`represents the frequency of the offset divided by 250 kHz
`BEHAVIOUR DEFINED AS:
`
`Returns a value that indicates the transmit carrier frequency and translation offset frequency in
`l\/H-Iz/4 for the IOBROAD36 MAU. This allows the frequencies to be defined to a resolution of
`250 kHz.;
`
`30.5.1.1 .10 aFalseCarriers
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`Generalized nonresettable counter. This counter has a maximum increment rate of 160 000 counts
`
`per second under maximum network load, and 10 counts per second under zero network load, for
`100 Mb/s implementations
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanggrd.
`
`0347
`
`t 1025
`
`Aerohive - Exhibit 1025
`
`0347
`
`

`
`IEEE
`Std 802.3u-1995
`
`BEHAVIOUR DEFINED AS:
`
`SUPPLEMENT TO 802.3:
`
`A count of the number of false carrier events during IDLE in IOOBASE-X links. This counter does
`not increment at the symbol rate. It can increment after a valid carrier completion at a maximum
`rate of once per 100 ms until the next carrier event.;
`
`30.5.1.2 MAU actions
`
`30.5.1.2.1 acResetMAU
`
`ACTION
`
`APPROPRIATE SYNTAX:
`
`None required
`BEHAVIOUR DEFINED AS:
`
`Resets the MAU in the same manner as would a power-off, power-on cycle of at least 0.5 s
`duration. During the 0.5 s DO, DI, and CI should be idle.;
`
`30.5.1 .2.2 acMAUAdminControl
`
`ACTION
`
`APPROPRIATE SYNTAX:
`The same as used for aMAUAdminState
`
`BEHAVIOUR DEFINED AS:
`
`Executing an acMAUAdminControl action causes the MAU to assume the aMAUAdminState
`attribute value of one of the defined valid management states for control input. The valid inputs
`are “standby,” “operational,” and “shutdown” state (see the behaviour definition
`bMAUAdminState for the description of each of these states) except that a “standby” action to a
`mixing type MAU or an AUI will cause the MAU to enter the “shutdown” management state.;
`
`30.5.1.3 MAU notifications
`
`30.5.1.3.1 nJabber
`
`NOTIFICATION
`
`APPROPRIATE SYNTAX:
`The same as used for alabber
`
`BEHAVIOUR DEFINED AS:
`
`The notification is sent whenever a managed MAU enters the JABBER state.;
`
`30.6 Management for link Auto-Negotiation
`
`30.6.1 Auto-Negotiation managed object class
`
`This subclause formally defines the behaviours for the oAuto—Negotiation managed object class, attributes,
`actions, and notifications.
`
`This is an3Qg'chive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`0348
`
`1025
`
`Aerohive - Exhibit 1025
`
`0348
`
`

`
`IEEE
`Std 802.3u-1995
`
`CSMA/CD
`
`30.6.1.1 Auto-Negotiation attributes
`
`30.6.1.1.1 aAutoNeglD
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`INTEGER
`
`BEHAVIOUR DEFINED AS:
`
`The value of aAutoNeglD is assigned so as to uniquely identify an Auto—Negotiation managed
`object among the subordinate managed objects of the containing object;
`
`30.6.1.1.2 aAutoNegAdminState
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`An ENUMERATED VALUE that has one of the following entries:
`enabled
`disabled
`
`BEHAVIOUR DEFINED AS:
`
`An interface which has Auto—Negotiation signaling ability will be enabled to do so when this
`attribute is in the enabled state. If disabled then the interface will act as it would if it had no Auto-
`
`Negotiation signaling. Under these conditions it will immediately be forced to the states indicated
`by a write to the attribute aMAUType.;
`
`30.6.1.1.3 aAutoNegRemoteSignaling
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`An ENUMERATED VALUE that has one of the following entries:
`detected
`notdetected
`
`BEHAVIOUR DEFINED AS:
`
`The value indicates whether the remote end of the link is operating Auto—Negotiation signaling or
`not. It shall take the value detected if, during the previous link negotiation, FLP Bursts were
`received fiom the remote end.;
`
`30.6.1.1 .4 aAutoNegAutoConfig
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`An ENUMERATED VALUE that has one of the following entries:
`other
`
`configuring
`complete
`disabled
`
`parallel detect fail
`BEHAVIOUR DEFINED AS:
`
`Indicates whether Auto—Negotiation signaling is in progress or has completed. The enumeration
`“parallel detect fail” maps to a failure in parallel detection as defined in 28.2.3.1.;
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanggrd.
`
`0349
`
`t 1025
`
`Aerohive - Exhibit 1025
`
`0349
`
`

`
`IEEE
`Std 802.3u-1995
`
`SUPPLEMENT TO 802.3:
`
`30.6.1.1 .5 aAutoNegLocalTechnologyAbility
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`A SEQUENCE that meets the requirements of the description below:
`global
`Reserved for future use
`other
`Undefined
`
`unknown
`10BASE-T
`
`Initializing, true ability not yet known
`10BASE-T as defined in clause 14
`
`IOBASE-TFD
`100BASE-TX
`
`Full-duplex 10BASE-T
`100BASE-TX as defined in clause 25
`
`l00BASE-TXFD Full-duplex 100BASE-TX
`100BASE-T4
`100BASE-T4 as defined in clause 23
`isoethemet
`IEEE Std 802.9 ISLAN—16T
`
`BEHAVIOUR DEFINED AS:
`
`This indicates the technology ability of the local hardware, as defined in clause 28.;
`
`30.6.1.1.6 aAutoNegAdvertisedTechnologyAbility
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`Same as aAutoNegLocalTechnologyAbility
`BEHAVIOUR DEFINED AS:
`
`This GET-SET attribute maps to the Technology Ability Field ofthe Auto—Negotiation Link Code
`Word, defined in clause 28. A SET operation to a value not available in
`aAutoNegLocalTechnologyAbility will be rejected. A successful set operation will result in
`immediate link renegotiation if aAutoNegAdrninState is enabled.
`
`NOTE—This will in every case cause temporary link loss during link renegotiation. If set to a value incom-
`patible with aAutoNegReceivedTechno1ogyAbility, link negotiation will not be successful and will cause
`permanent link loss.;
`
`30.6.1.1 .7 aAutoNegReceivedTechnologyAbility
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`Same as aAutoNegLocalTechnologyAbility
`BEHAVIOUR DEFINED AS:
`
`Indicates the advertised technology ability of the remote hardware. Maps to the Technology
`Ability Field of the last received Auto—Negotiation Link Code Word(s), defined in clause 28.;
`
`30.6.1.1 .8 aAutoNegLocalSelectorAbility
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`A SEQUENCE that meets the requirements of the description below:
`other
`Undefined
`ethemet
`IEEE Std 802.3
`isoethemet
`IEEE Std 802.9 ISLAN—16T
`
`BEHAVIOUR DEFINED AS:
`This indicates the value of the selector field of the local hardware. Selector field is defined in
`
`28.2. 1 .2. l. The enumeration of the Selector Field indicates the standard that defines the remaining
`encodings for Auto—Negotiation using that value of enumeration. Additional future enurnerations
`may be assigned to this attribute through the 802.3 maintenance process.;
`
`This is ar13Qg'chive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`
`
`Aerohive - Exhibit 1025
`
`0350
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`30.6.1.1 .9 aAutoNegAdvertisedSelectorAbility
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`Same as aAutoNegLoca1Se1ectorAbility
`BEHAVIOUR DEFINED AS:
`
`This GET-SET attribute maps to the Message Selector Field of the Auto-Negotiation Link Code
`Word, defined in clause 28. A SET operation to a value not available in
`aAutoNegLocalSelectorAbility will be rejected. A successful set operation will result in
`immediate link renegotiation if aAutoNegAd1ninState is enabled.
`
`NOTE—'I‘his will in every case cause temporary li11k loss during link renegotiation. If set to a value incom-
`patible with aAutoNegReceivedSelectorAbility, link negotiation will not be successful and will cause per-
`manent link loss.;
`
`30.6.1.1 .1 0 aAutoNegReceivedSelectorAbility
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`Same as aAutoNegLocalSelectorAbility
`BEHAVIOUR DEFINED AS:
`
`Indicates the advertised message transmission ability of the remote hardware. Maps to the Message
`Selector Field of the last received Auto-Negotiation Link Code Word, defined in clause 28.;
`
`30.6.1.2 Auto-Negotiation actions
`
`30.6.1 .2.1 acAutoNegRestartAutoConfig
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`None required
`BEHAVIOUR DEFINED AS:
`
`Forces Auto-Negotiation to begin link renegotiation. Has no effect if Auto-Negotiation signaling
`is disabled.;
`
`30.6.1.2.2 acAutoNegAdminControl
`
`ATTRIBUTE
`
`APPROPRIATE SYNTAX:
`
`Same as aAutoNegAdminState
`BEHAVIOUR DEFINED AS:
`
`This action provides a means to turn Auto-Negotiation signaling on or off;
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanggrd.
`
`
`
`Aerohive - Exhibit 1025
`
`0351
`
`

`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`0352
`
`1025
`
`Aerohive - Exhibit 1025
`
`0352
`
`

`
`CSMNCD
`
`Annex 22A
`
`(informative)
`
`IEEE
`Std B{}2_3u—‘l 995
`
`MII output delay, setup, and hold time budget
`
`22A.1 System model
`
`The discussion of signal timing characteristics that follows will refer to the system n1odel depicted in
`figure 22A-1, figure 22A-2, and figure 22A-3. This system model can be applied to each of the three
`application enviromnents defined in 22.2.].
`
`Figure 22A—1 depicts a simple system model in which the MII is used to interconnect two integrated
`circuits on the same circuit assembly. In this n1odel the Reconciliation sublayer comprises one integrated
`circuit, and the PHY comprises the other. A Reconciliation sublayer or a PHY may actually be
`composed of several separate integrated circuits. The system model
`in figure 22A-1 includes two
`unidirectional signal transmission paths, one from the Reconciliation sublayer to the PHY and one from
`the PHY to the Reconciliation sublayer. The path from the Reconciliation sublayer to the PHY is
`separated into two sections, labeled A1 and B]. The path from the PHY to the Reconciliation sublayer is
`separated into two sections, labeled C1 and D1.
`
`Reconciliation
`
`sublayer
`
`PHY“)
`
`Figure 22A-1—Mode| for integrated circuit to integrated circuit connection
`
`Figure 22A—1 depicts a system model for the case where the M11 is used to interconnect two circuit
`assemblies. The circuit assemblies may be physically connected in a motherboardfdaughterboard
`arrangement, or they may be physically connected with the cable defined in 22.4.5 and the line interface
`connector defined in 22.6. The system model
`in figure 22A-2 includes two unidirectional signal
`transmission paths, one from the Reconciliation sublayer to the PHY and one from the PHY to the
`Reconciliation sublayer. The path from the Reconciliation sublayer to the PHY is separated into two
`sections, labeled A2 and B2. The path from the PHY to the Reconciliation sublayer is separated into two
`sections, labeled C2 and D2.
`
`Figure 22A-3 depicts a system model in which the MII is used to interconnect both integrated circuits
`and circuit assemblies. This system model allows for separate signal transmission paths to exist between
`the Reconciliation sublayer and a local PHY(L)_. and between the Reconciliation sublayer and a remote
`PI-TY(R). The unidirectional paths between the Reconciliation sublayer and the PHY(L) are composed of
`sections A1, B1, C1, and D1. The unidirectional paths between the Reconciliation sublayer and the
`remote PHY(R) are composed of sections A2, B2, C2, and D2.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stangigrd.
`
`Aerohive - Exhibit 1
`
`0
`
`Aerohive - Exhibit 1025
`
`0353
`
`

`
`IEEE
`Std 8D2.3u—1995
`
`SUPPLEMENT TO 802.3:
`
`Reconciliation
`
`sublayer
`
`Figure 22A-2—|'1i‘|ode| for circuit assembly to circuit assembly connection
`
`Reconciliation
`
`sublayer
`
`Figure 22A-3—Combined model
`
`Each of these system models assumes a set of common tinning and electrical cllaracteristics that shall be met
`at the input and output ports of the Reconciliation sublayer and PHY devices. The characteristics of the signal
`transmission paths are identified for each of the sections A1, B1, C1, D1, A2. B2, C2, and D2.
`
`22A.2 Signal transmission path characteristics
`
`The signal transmission path characteristics are specified for each of the path sections defined in 22A.1.
`The characteristics for these sections are specified so as to allow sections Al, B1, C1, and D1 to be
`implemented in the form of printed circuit board traces, while sections A2, B2, C2, and D2 may be
`implemented with a combination of printed circuit board traces and wire conductors in a cable assembly.
`
`This is angggchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1
`
`Aerohive - Exhibit 1025
`
`0354
`
`

`
`CSMA/CD
`
`IEEE
`Std 8D2.3u-1995
`
`The signal transmission path characteristics are stated in terms of their maximum delay and their
`characteristic impedance. These values are summarized in table 22A-1.
`
`Table 22A-1—SignaI transmission path characteristics
`
`
`
`The driver characteristics specified in 22.4.3, the receiver characteristics specified in 22.4.4, and the
`signal transmission path characteristics specified in table 22A-1 can be applied to the system models
`shown in figure 22A-1 or figure 22A-2. The combination of loads presented in figure 22A-3 cannot be
`adequately driven by an output buffer that meets the driver characteristics specified in 22.4.3 while being
`sampled by an input buffer that meets the receiver characteristics specified in 22.4.4.
`
`To address the system model depicted in figure 22A-3, it is permissible to incorporate an additional
`stage of buffering into path sections Al, A2, D1, and D2, provided that the resulting maximum delay
`characteristic for those path sections does not exceed the value stated in table 22A-1. The delay
`characteristic for transmission path sections A2 and D2 includes an allowance for the delay that results
`from the presence of a lumped capacitive load at the end of the path. For a transmission path section
`with a characteristic impedance Z0, with a lumped capacitive load CL, this delay is nominally ZOCL. In
`the case of a maximum transmission path section impedance of 78 Q with a lumped load of 8 pF, the
`nominal delay is 0.6 ns. Thus the allowable delay for a buffer inserted into transmission path section A2
`or D2 is 4.4 ns.
`
`22A.3 Budget calculation
`
`A recommended timing budget is shown in table 22A-2. This budget assumes that the combined system
`model shown in figure 22A-3 represents a worst case.
`
`Table 22A-2—Round-trip delay budget
`
`
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stangigrd.
`
`
`
`Aerohive - Exhibit 1025
`
`0355
`
`

`
`IEEE
`Std 802.3u—1995
`
`Annex 22B
`
`(informative)
`
`Mll driver ac characteristics
`
`SUPPLEMENT T0 802.3:
`
`22B.1 Implications of CMOS ASIC processes
`
`For M11 drivers that drive rail to rail, such as those commonly used in CMOS ASICS (complimentary
`metal oxide semiconductor application-specific integrated circuits), the ac characteristic performance
`requirements of 22.4.3.2 can be met if tl1e V0,, vs. Ioh and V0] vs. I01 dc characteristics of the driver stay
`within the unshaded areas of figure 22B-1.
`
`The variation in output resistance of a field effect transistor (FET) due to variations in supply voltage,
`temperature, and process may require that a resistance be placed in series with the output of the FETs to
`meet this specification. The series resistance can be part of the driver circuit, or external to the driver. If
`the series resistance is not part of the driver circuit, the driver vendor shall specify the value of series
`resistance required to meet
`the specification. A series resistor used to meet
`this specification is
`conceptually part of the driver regardless of whether it is physically internal or external to the driver.
`
`The propagation delay of the path between the driver and an external series resistor used to meet the
`specification shall not exceed 10% of the 10-90% riseffall time of the driver.
`
`Figure 22B-1—Driver output V—l curve
`
`This is anggrchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`0356
`
`

`
`CSMA/CD
`
`IEEE
`Std 8D2.3u-1995
`
`22B.2 R°(min) and V, I values for operation from 5V :1 0% supply
`
`Referring to figure 22B-1, Rommin) and R010-njn) both equal 40 Q, and the values for the V-I points on the
`curve are given in table 22B-1 below for MII drivers that drive rail to rail from a +5 V :I: 10% power
`supply.
`
`Table 22B-1—Values for driver output V-I curve (5 V supply)
`
`
`
`22B.3 R°(mi,,) and\I, I values for operation from 3.3 1 0.3V supply
`
`Referring to figure 22B-1, Rohonin) and Roumin) both equal 33 Q, and the values for the V-I points on the
`curve are given in table 22B-2 below for MII drivers that drive rail to rail from a +3.3 :: 0.3 V power
`supply.
`
`Table 22B-2—Values for driver output V-I curve (3.3 V supply)
`
`
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stangigrd.
`
`
`
`Aerohive - Exhibit 1025
`
`0357
`
`

`
`IEEE
`Std 802.3u-1995
`
`Annex 22C
`
`(informative)
`
`SUPPLEMENT TO 802.3:
`
`Measurement techniques for MII signal timing characteristics
`
`22C.1 Measuring timing characteristics of source terminated signals
`
`The measurement of timing relationships between MII signals at the MII connector is complicated by
`the use of driver output impedance to control transmission line reflections on point-to-point transmission
`paths passing through the connector. The voltage waveforms on point-to-point transmission paths can be
`different at the MII connector and at the end of the paths. A clean transition (or step) from one logic
`state to the other at the end of a point to point path can appear as two ha1f—steps at the M11 connector.
`
`To eliminate ambiguity as to where on a two half—step state transition to measure timing, all timing
`measurements on point-to-point transmission paths will be at the end of the path. In some cases, an end
`of path must be artificially created.
`
`22C.2 Measuring timing characteristics of transmit signals at the MII
`
`The timing of TX_EN, TX_ER, and TXD<3:0> relative to TX_CLK at the MII connector is measured as
`follows.
`
`Use the time base for TX_CLK as a timing reference. Break the TX_CLK path at the MII connector,
`forcing the TX_CLK point-to-point transmission path to end at the connector. Measure when the rising
`edge of TX_CLK passes through Vmmin) at the M11 connector. Call this time Tclk. Reconnect the
`TX_CLK path at the MII connector and break the paths of TX_EN, TX_ER, and TXD<3:0> at the IVJII
`connector, forcing the paths to end at the connector. Measure when TX_EN, TX_ER, and TXD<3:0>
`exit the switching region at the M11 connector. Call these times Ten, T6,, and T<3.0>, respectively.
`
`The timing relationships at the MII connector for TX_EN, TX_ER, and TXD<3:0> relative to TX_CLK
`are met if (Tm — Talk), (Te, — Tcug, (T3 — Tclk), (T2 — Tclk), (T1 — Tclk), and (T0 — Tclk), respectively, meet
`the timing relationships specified in 22.3.1.
`
`22C.3 Measuring timing characteristics of receive signals at the MII
`
`The timing of RX_DV, RX_ER, and RXD<3:0> relative to RX_CLK at the MII connector is measured
`as follows.
`
`Break the paths of RX_CLK, RX_DV, RX_ER, and RXD<3:0> at the MII connector, forcing the paths
`to end at the connector. Measure when RX_DV, RX_ER, and RXD<3:0> exit the switching region at the
`
`M11 connector relative to when the rising edge of RX_CLK passes through Vmmax). Also measure when
`RX_DV, RX_ER, and RXD<3:0> reenter the switching region relative to when the rising edge of
`RX_CLK passes through Vimmin) .
`
`The timing relationships at the MII connector for RX_DV, RX_ER, and RXD<3:0> relative to RX_CLK
`are met if the times measured in the previous step meet the timing relationships specified in 22.3.2.
`
`This is argggchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`
`
`Aerohive - Exhibit 1025
`
`0358
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`22C.4 Measuring timing characteristics of MDIO
`
`The MDIO and MDC signal timing characteristics cannot be measured using the techniques defined for
`the transmit and receive signals since MDIO and MDC may connect a single station management entity
`to multiple PHY devices. The MDIO and MDC timing characteristics are measured with a PHY
`connected to the MII connector. The signal timing characteristics for MDC and MDIO must be met over
`the range of conditions which occur when from one to 32 PHYS are connected to an STA. When 32
`PHYS are connected to an STA, the total capacitance can be as large as 390 pF on MDC, and as large as
`470 pF on MDIO.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`
`
`Aerohive - Exhibit 1025
`
`0359
`
`

`
`IEEE
`Std 802.3u-1995
`
`Annex 23A
`
`(nonnafive)
`
`6T code words
`
`SUPPLEMENT TO 802.3:
`
`The leftmost ternary symbol of each 6T Code group shown in table 23A-1 (broken into 23A-la and 23A-lb
`for pagination) shall be transmittedfirst. The leftmost nibble of each data octet is the most sigmficant.
`
`Table 23A-1a—100BASE-T4 8B6T code table
`
`6T code group
`—— O -— O O —
`
`0
`
`O
`
`o
`
`-o
`
`o
`
`Data
`octet
`
`60
`
`61
`
`62
`
`63
`
`64
`
`6T code group
`O-O——+O
`
`oo—uou
`
`o—o«o«
`
`o—o+
`
`O
`
`I I I
`
`Data
`octet
`
`m 1
`
`I\.
`Ix. [\)
`Ix. OJ
`Ix. Ib-
`Ix. U'|
`Ix. OW
`Ix. \l
`Ix. O0
`Ix. k.O
`
`Data
`octet
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`6T code group
`_++_
`00
`+ (D
`
`0..
`
`OOO++ O
`
`Data
`octet
`
`00
`
`O1
`
`02
`
`03
`
`O4
`
`O5
`
`O6
`
`O7
`
`O8
`
`09
`
`0A
`
`6Tcodegroup
`———OO+—
`
`O+—~—O
`
`———0-——O
`
`—O+~—O
`
`—O+O+—
`
`O+——0+
`
`+—O—O+
`
`—0+—0+
`
`—+OO+—
`
`O—++—O
`
`—+0+—O
`
`+
`
`+
`
`I I I
`
`I I IOOOOOOOOOOOIOOOOOOOOO+++OOOOOOOO
`
`++0
`
`7F
`
`OOOOOOOOOOOOOOOOOO+OII
`OOOOOOOO
`
`I
`
`B t
`
`a?
`
`(3
`
`oooO++++++OOooc>
`
`II+OOO
`
`OB
`
`OC
`
`0 3
`
`OZ
`
`L‘J
`
`OF
`
`10
`
`LJ'(7b3t37©b0\lb\LnJ>iA)Ni4
`
`1F
`
`»O—+—O
`
`»O—O+—
`
`O—+-O-
`
`—+O—0--
`
`_0__0_
`
`~O+——O
`
`—+0—0—
`
`.O__0_
`
`O+——0—
`
`0+-——O
`
`~+0O——
`
`-O+O——
`
`O++O——
`
`O+—O+—
`
`O+—O——
`
`O+—++—
`
`O+—OO——
`
`O—+O0+
`
`O—++—-
`
`O--O—+
`
`0--0-—
`
`2F
`
`30
`
`31
`
`32
`
`33
`
`34
`
`35
`
`36
`
`37
`
`38
`
`39
`
`3E
`
`3D
`
`3F
`
`This is an3gg'chive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`03 60
`
`Aerohive - Exhibit 1025
`
`0360
`
`

`
`CSMA/CD
`
`IEEE
`Std 802.3u-1995
`
`Table 23A-1b—10OBASE-T4 8B6T code table
`
`Data
`
`octet
`80
`
`81
`
`82
`
`83
`
`84
`
`85
`
`86
`
`6T code group
`-~—+OO—
`
`-~+—O—O
`
`——-+O—O
`
`—++O—O
`
`—++00—
`
`++--00
`
`+—+—0O
`
`Data
`
`octet
`A0
`
`Al
`
`A2
`
`A3
`
`A4
`
`A5
`
`A6
`
`6T code group
`O—O++—
`
`OO—+—-»
`
`0—0+—-—
`
`—OO+—-»
`
`—O0+--—
`
`oo—--~--
`
`0—O—
`
`Data
`
`octet
`CO
`
`Cl
`
`C2
`
`C3
`
`C4
`
`c5
`
`C6
`
`C7
`
`6T code group
`-~—--O+—
`
`-»+—+—O
`
`———--+—0
`
`—+——+—O
`
`—+—-O+—
`
`-~+--o-~
`
`»- —O+
`
`—+——0——
`
`Data
`
`octet
`E0
`
`El
`
`E2
`
`E3
`
`:34
`
`35
`
`36
`
`:37
`
`6T code group
`+—O--+-
`
`O+————+
`
`+—O—-—+
`
`—O+———+
`
`—0+----—
`
`0+--»+
`
`+—O—
`
`—O————
`
`87
`
`88
`
`89
`
`8A
`
`8B
`
`8C
`
`8D
`
`83
`
`8F
`
`—+——00
`
`O+OO0-
`
`0O—O—O
`
`0+0O—O
`
`-»OOO—O
`
`—00O0—
`
`OO+—0O
`
`0+0—0O
`
`-~OO—OO
`
`A7
`
`A8
`
`A9
`
`AA
`
`AB
`
`AC
`
`AD
`
`A3
`
`AF
`
`—O0————
`
`—+—+——
`
`——++——
`
`—+—+——
`
`+——+—
`
`+——+———
`
`——+—»
`
`—+——
`
`+———»»
`
`C8
`
`C9
`
`CA
`
`CB
`
`OC
`
`CD
`
`C3
`
`CF
`
`38
`
`:39
`
`EA
`
`4)
`
`I:
`
`O+0O+—
`
`00———0
`
`0+0———0
`
`~OO+—O
`
`—0O0+—
`
`OO+—O-~
`
`O+0—0--
`
`~OO—O-»
`
`*
`
`—+O-
`
`—
`
`0—————
`
`—+0———
`
`+0--—+
`
`+0--—-
`
`O—+—»—
`
`—+O---
`
`~O——~+
`
`90
`
`9l
`
`92
`
`93
`
`94
`
`95
`
`96
`
`97
`
`——+——+
`
`»+————
`
`»—+—-—
`
`—++— —
`
`—++——+
`
`++—+——
`
`+—++——
`
`—+++——
`
`B0
`
`Bl
`
`B2
`
`B3
`
`B4
`
`B5
`
`B6
`
`B7
`
`0-000
`
`OO—O~O
`
`0—O0~O
`
`—O00——O
`
`—OOOO+
`
`0O—+OO
`
`O—O+OO
`
`-OO+OO
`
`30
`
`31
`
`D2
`
`33
`
`34
`
`35
`
`36
`
`37
`
`-— O—-
`
`~+——+O
`
`~———+0
`
`—
`
`—+O
`
`—+-O—+
`
`» —~O—
`
`——--0-
`
`—
`
`-»O—
`
`F0
`
`Fl
`
`E2
`
`F3
`
`F4
`
`F5
`
`F6
`
`F7
`
`-000-
`
`O+—O»O
`
`~—O0—~O
`
`—0+0——0
`
`—O+OO+
`
`O+--O0
`
`+—O—-O0
`
`—0+—O0
`
`—--000+
`
`98
`
`99
`
`9A
`
`9B
`
`9C
`
`9D
`
`9E
`
`9F
`
`0+0——+
`
`OO+———
`
`0+0———
`
`—O0———
`
`»OO——+
`
`O0++——
`
`O+O+——
`
`+00+——
`
`B8
`
`B9
`
`BA
`
`BB
`
`BC
`
`BD
`
`BE
`
`BF
`
`—-—00+
`
`——+O--O
`
`———0—O
`
`+——0—O
`
`+——OO+
`
`——++0O
`
`—+—-i-OO
`
`+——+OO
`
`38
`
`39
`
`DA
`
`DB
`
`I2
`
`DD
`
`33
`
`DF
`
`0-—00—+
`
`O0 —+O
`
`0—0—+0
`
`—O0—+0
`
`»OOO—+
`
`O0+—0—
`
`O+O+O—
`
`+00-0-
`
`F8
`
`F9
`
`EA
`
`EB
`
`FC
`
`ED
`
`FE
`
`FF
`
`O—+O~0
`
`———00——O
`
`—0—O—0
`
`»O—0O+
`
`O—+—-O0
`
`—+O--O0
`
`+0---00
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`Aerohive - Exhibit 1025
`
`O3 61
`
`Aerohive - Exhibit 1025
`
`0361
`
`

`
`IEEE
`Std 802.3u-1995
`
`Annex 23B
`
`(informative)
`
`Noise budget
`
`SUPPLEMENT TO 802.3:
`
`Worst-case values for noise effects in the IOOBASE-T4 system are as shown in tables 23B-1 and 23B-2.
`
`Table 23B-1—Carrier presence analysis
`
`Table 23B-2—Far-end signal analysis
`
`
`
`This is ariglmchive IEEE Standard.
`
`It has been superseded by a later version of this standard.
`
`0362
`
`1025
`
`Aerohive - Exhibit 1025
`
`0362
`
`

`
`CSMA/CD
`
`Annex 23C
`
`(informative)
`
`IEEE
`Std 802.3u-1995
`
`Use of cabling systems with a nominal differential characteristic
`impedance of 120 Q
`
`The 100BASE-T4 standard specifies only the use of 100 9. link segments for conformance. Since
`ISO/IEC 11801: 1995 also recognizes 120 Q cabling, this informative annex specifies the conditions for
`using cabling systems with a nominal characteristic impedance of 120 Q by 100BASE-T4 conformant
`stations.
`
`The use of cables with a characteristic impedance outside the range specified in 23.6 will generally
`increase the mismatching effects in the link components, inducing additional noise in the received signals.
`
`In particular, the use of a homogeneous link segment having a characteristic impedance of 120 Q :I:15 (2
`over the frequency band 1 to 16 MHz may add up to 1.4% of additional noise to the signals at the input of
`the receivers (worst-case short-length link segment).
`
`Therefore, in order to keep the overall noise (MDFEXT + reflections) at the same value as for a 100 Q
`link segment when using a 120 9 link segment, the minimum ELFEXT loss requirement for the cable
`must be increased by 2 dB (i.e., from 23 dB to 25 dB at 12.5 MHz, see 23.6.3.2). Accordingly, the
`MDFEXT noise requirement shall be decreased from 87 mV peak to 69 mV peak. In practice, this means
`that cables rated category 4 or higher, as specified in ISO/IEC 11801: 1995, are required when 120 9
`cables are used with 100BASE-T4 compliant PMDs.
`
`NOTES
`
`l—The use of 100 Q cords at end points in conjunction with 120 Q premises cabling may be tolerated provided that all
`the components of the link are of category 5, as defined in ISO/IEC 11801: 1995.
`
`2—The use of 100 Q cords at any intermediate cross-connect points on 120 9 links as well as the use of 120 S2 cords in
`conjunction with 100 Q premises cabling is not allowed since it would result in worst-case jitter greater than that
`allowed in this standard.
`
`CAUTION—Users of this annex are fiirther advised to check with the manufacturer of the particular 100BASE-T4 cou-
`plers they intend to use with a 120 9 link to see whether those couplers can operate correctly on cables with Zc as high
`as
`Q2:
`9.
`
`This is an Archive IEEE Standard.
`
`It has been superseded by a later version of this stanglard.
`
`0363
`
`it 1025
`
`Aerohive - Exhibit 1025
`
`0363
`
`

`
`IEEE
`Std 802.3u-1995
`
`Annex 27A
`
`(normative)
`
`SUPPLEMENT TO 802.3:
`
`Repeater delay consistency requirements
`
`Proper operation of the network requires that repeaters do not cause the Inter-Packet Gap (IPG) to
`disappear by propagating the end of any carrier event to different output ports with greatly different delay
`times. Maximum port-to-port delays have been assigned as absolute delays to meet requirements for
`detection of collision within a slot time and limiting the length of collision fragments to less than
`minimum frame size. To avoid specification of minimum input—to—output propagation time as absolute
`values that reduce implementation flexibility, these delays are instead implied by imposing a triangular
`delay inequality relationship.
`
`Consider three ports {A, B, C}. Using the notation SOP(xy) to mean the start—of—packet delay for an input
`at port x to resulting output on port y, repeaters shall achieve this relationship for all groups of three ports
`within a repeater set:
`
`SOP(AC) < SOP(AB) + SOP(BC)
`
`Following a frame transmitted by node A that propagates to nodes B and C, this constraint ensures that
`node B cannot complete an IPG timer and initiate a transmission that arrives at node C before node C has
`also advanced its own IPG timer sufliciently that a pending frame can contend for access to the network.
`
`There is a second delay consistency requirement, one that relates to jam propagation by repeaters. Using a
`notation similar to that above, SOJ(xy) stands for the start