Content

•   Introduction to IEEE Std 802.3, 2000 Edition
•   Working group members
•   Officers
• 1 Introduction  ▶
  • 1.1 Overview  ▶
    • 1.1.1 Basic concepts  ▶
      • 1.1.1.1 Half duplex operation
      • 1.1.1.2 Full duplex operation
    • 1.1.2 Architectural perspectives  ▶
      • 1.1.2.1 Architectural rationale
      • 1.1.2.2 Compatibility interfaces
    • 1.1.3 Layer interfaces
    • 1.1.4 Application areas
  • 1.2 Notation  ▶
    • 1.2.1 State diagram conventions
    • 1.2.2 Service specification method and notation  ▶
      • 1.2.2.1 Classification of service primitives
    • 1.2.3 Physical Layer and media notation
    • 1.2.4 Physical Layer message notation
  • 1.3 Normative references
  • 1.4 Definitions
  • 1.5 Abbreviations
• 2 Media Access Control (MAC) service specification  ▶
  • 2.1 Scope and field of application
  • 2.2 Overview of the service  ▶
    • 2.2.1 General description of services provided by the layer
    • 2.2.2 Model used for the service specification
    • 2.2.3 Overview of interactions
    • 2.2.4 Basic services and options
  • 2.3 Detailed service specification  ▶
    • 2.3.1 MA_DATA.request  ▶
      • 2.3.1.1 Function
      • 2.3.1.2 Semantics of the service primitive
      • 2.3.1.3 When generated
      • 2.3.1.4 Effect of receipt
      • 2.3.1.5 Additional comments
    • 2.3.2 MA_DATA.indication  ▶
      • 2.3.2.1 Function
      • 2.3.2.2 Semantics of the service primitive
      • 2.3.2.3 When generated
      • 2.3.2.4 Effect of receipt
      • 2.3.2.5 Additional comments
    • 2.3.3 MA_CONTROL.request  ▶
      • 2.3.3.1 Function
      • 2.3.3.2 Semantics of the service primitive
      • 2.3.3.3 When generated
      • 2.3.3.4 Effect of receipt
    • 2.3.4 MA_CONTROL.indication  ▶
      • 2.3.4.1 Function
      • 2.3.4.2 Semantics of the service primitive
      • 2.3.4.3 When generated
      • 2.3.4.4 Effect of receipt
• 3 Media access control frame structure  ▶
  • 3.1 Overview  ▶
    • 3.1.1 MAC frame format
  • 3.2 Elements of the MAC frame  ▶
    • 3.2.1 Preamble field
    • 3.2.2 Start Frame Delimiter (SFD) field
    • 3.2.3 Address fields  ▶
      • 3.2.3.1 Address designation
    • 3.2.4 Destination Address field
    • 3.2.5 Source Address field
    • 3.2.6 Length/Type field
    • 3.2.7 Data and PAD fields
    • 3.2.8 Frame Check Sequence (FCS) field
    • 3.2.9 Extension field
  • 3.3 Order of bit transmission
  • 3.4 Invalid MAC frame
  • 3.5 Elements of the Tagged MAC Frame  ▶
    • 3.5.1 Preamble field
    • 3.5.2 Start Frame Delimiter (SFD) field
    • 3.5.3 Address fields
    • 3.5.4 Length/Type field
    • 3.5.5 Tag Control Information field (informative)
    • 3.5.6 MAC Client Length/Type field
    • 3.5.7 Data and PAD fields
    • 3.5.8 Frame Check Sequence (FCS) field
    • 3.5.9 Extension field
• 4 Media Access Control  ▶
  • 4.1 Functional model of the MAC method  ▶
    • 4.1.1 Overview
    • 4.1.2 CSMA/CD operation  ▶
      • 4.1.2.1 Normal operation  ▶
        • 4.1.2.1.1 Transmission without contention
        • 4.1.2.1.2 Reception without contention
      • 4.1.2.2 Access interference and recovery
    • 4.1.3 Relationships to the MAC client and Physical Layers
    • 4.1.4 CSMA/CD access method functional capabilities
  • 4.2 CSMA/CD Media Access Control (MAC) method: Precise specification  ▶
    • 4.2.1 Introduction
    • 4.2.2 Overview of the procedural model  ▶
      • 4.2.2.1 Ground rules for the procedural model
      • 4.2.2.2 Use of Pascal in the procedural model
      • 4.2.2.3 Organization of the procedural model
      • 4.2.2.4 Layer management extensions to procedural model
    • 4.2.3 Frame transmission model  ▶
      • 4.2.3.1 Transmit data encapsulation  ▶
        • 4.2.3.1.1 Frame assembly
        • 4.2.3.1.2 Frame check sequence generation
      • 4.2.3.2 Transmit media access management  ▶
        • 4.2.3.2.1 Deference
        • 4.2.3.2.2 Interframe spacing
        • 4.2.3.2.3 Collision handling (half duplex mode only)
        • 4.2.3.2.4 Collision detection and enforcement (half duplex mode only)
        • 4.2.3.2.5 Collision backoff and retransmission (half duplex mode only)
        • 4.2.3.2.6 Full duplex transmission
        • 4.2.3.2.7 Frame bursting (half duplex mode only)
      • 4.2.3.3 Minimum frame size
      • 4.2.3.4 Carrier extension (half duplex mode only)
    • 4.2.4 Frame reception model  ▶
      • 4.2.4.1 Receive data decapsulation  ▶
        • 4.2.4.1.1 Address recognition
        • 4.2.4.1.2 Frame check sequence validation
        • 4.2.4.1.3 Frame disassembly
      • 4.2.4.2 Receive media access management  ▶
        • 4.2.4.2.1 Framing
        • 4.2.4.2.2 Collision filtering
    • 4.2.5 Preamble generation
    • 4.2.6 Start frame sequence
    • 4.2.7 Global declarations  ▶
      • 4.2.7.1 Common constants, types, and variables
      • 4.2.7.2 Transmit state variables
      • 4.2.7.3 Receive state variables
      • 4.2.7.4 Summary of interlayer interfaces
      • 4.2.7.5 State variable initialization
    • 4.2.8 Frame transmission
    • 4.2.9 Frame reception
    • 4.2.10 Common procedures
  • 4.3 Interfaces to/from adjacent layers  ▶
    • 4.3.1 Overview
    • 4.3.2 Services provided by the MAC sublayer
    • 4.3.3 Services required from the physical layer
  • 4.4 Specific implementations  ▶
    • 4.4.1 Compatibility overview
    • 4.4.2 Allowable implementations  ▶
      • 4.4.2.1 Parameterized values
      • 4.4.2.2 Parameterized values
      • 4.4.2.3 Parameterized values
      • 4.4.2.4 Parameterized values
    • 4.4.3 Configuration guidelines
• 5 Layer Management  ▶
  • 5.1 Introduction  ▶
    • 5.1.1 Systems Management overview
    • 5.1.2 Layer Management model
    • 5.1.3 Packages
    • 5.1.4 Conformance requirements
  • 5.2 Management facilities  ▶
    • 5.2.1 Introduction
    • 5.2.2 DTE MAC Sublayer Management facilities  ▶
      • 5.2.2.1 DTE MAC sublayer attributes  ▶
        • 5.2.2.1.1 aMACID
        • 5.2.2.1.2 aFramesTransmittedOK
        • 5.2.2.1.3 aSingleCollisionFrames
        • 5.2.2.1.4 aMultipleCollisionFrames
        • 5.2.2.1.5 aFramesReceivedOK
        • 5.2.2.1.6 aFrameCheckSequenceErrors
        • 5.2.2.1.7 aAlignmentErrors
        • 5.2.2.1.8 aOctetsTransmittedOK
        • 5.2.2.1.9 aFramesWithDeferredXmissions
        • 5.2.2.1.10 aLateCollisions
        • 5.2.2.1.11 aFramesAbortedDueToXSColls
        • 5.2.2.1.12 aFramesLostDueToIntMACXmitError
        • 5.2.2.1.13 aCarrierSenseErrors
        • 5.2.2.1.14 aOctetsReceivedOK
        • 5.2.2.1.15 aFramesLostDueToIntMACRcvError
        • 5.2.2.1.16 aPromiscuousStatus
        • 5.2.2.1.17 aReadMulticastAddressList
        • 5.2.2.1.18 aMulticastFramesXmittedOK
        • 5.2.2.1.19 aBroadcastFramesXmittedOK
        • 5.2.2.1.20 aFramesWithExcessiveDeferral
        • 5.2.2.1.21 aMulticastFramesReceivedOK
        • 5.2.2.1.22 aBroadcastFramesReceivedOK
        • 5.2.2.1.23 aInRangeLengthErrors
        • 5.2.2.1.24 aOutOfRangeLengthField
        • 5.2.2.1.25 aFrameTooLongErrors
        • 5.2.2.1.26 aMACEnableStatus
        • 5.2.2.1.27 aTransmitEnableStatus
        • 5.2.2.1.28 aMulticastReceiveStatus
        • 5.2.2.1.29 aReadWriteMACAddress
        • 5.2.2.1.30 aCollisionFrames
      • 5.2.2.2 DTE MAC Sublayer actions  ▶
        • 5.2.2.2.1 acInitializeMAC
        • 5.2.2.2.2 acAddGroupAddress
        • 5.2.2.2.3 acDeleteGroupAddress
        • 5.2.2.2.4 acExecuteSelfTest
      • 5.2.2.3 ResourceTypeID Managed Object Class  ▶
        • 5.2.2.3.1 ResourceTypeID
    • 5.2.3 DTE Physical Sublayer Management facilities  ▶
      • 5.2.3.1 DTE Physical Sublayer attributes  ▶
        • 5.2.3.1.1 aPHYID
        • 5.2.3.1.2 aSQETestErrors
    • 5.2.4 DTE Management procedural model  ▶
      • 5.2.4.1 Common constants and types
      • 5.2.4.2 Transmit variables and procedures
      • 5.2.4.3 Receive variables and procedures
      • 5.2.4.4 Common procedures
• 6 Physical Signaling (PLS) service specifications  ▶
  • 6.1 Scope and field of application
  • 6.2 Overview of the service  ▶
    • 6.2.1 General description of services provided by the layer
    • 6.2.2 Model used for the service specification
    • 6.2.3 Overview of interactions
    • 6.2.4 Basic services and options
  • 6.3 Detailed service specification  ▶
    • 6.3.1 Peer-to-peer service primitives  ▶
      • 6.3.1.1 PLS_DATA.request  ▶
        • 6.3.1.1.1 Function
        • 6.3.1.1.2 Semantics of the service primitive
        • 6.3.1.1.3 When generated
        • 6.3.1.1.4 Effect of receipt
      • 6.3.1.2 PLS_DATA.indication  ▶
        • 6.3.1.2.1 Function
        • 6.3.1.2.2 Semantics of the service primitive
        • 6.3.1.2.3 When generated
        • 6.3.1.2.4 Effect of receipt
    • 6.3.2 Sublayer-to-sublayer service primitives  ▶
      • 6.3.2.1 PLS_CARRIER.indication  ▶
        • 6.3.2.1.1 Function
        • 6.3.2.1.2 Semantics of the service primitive
        • 6.3.2.1.3 When generated
        • 6.3.2.1.4 Effect of receipt
      • 6.3.2.2 PLS_SIGNAL.indication  ▶
        • 6.3.2.2.1 Function
        • 6.3.2.2.2 Semantics of the service primitive
        • 6.3.2.2.3 When generated
        • 6.3.2.2.4 Effect of receipt
      • 6.3.2.3 PLS_DATA_VALID.indication  ▶
        • 6.3.2.3.1 Function
        • 6.3.2.3.2 Semantics of the service primitive
        • 6.3.2.3.3 When generated
        • 6.3.2.3.4 Effect of receipt
• 7 Physical Signaling (PLS) and Attachment Unit Interface (AUI) specifications  ▶
  • 7.1 Scope  ▶
    • 7.1.1 Definitions
    • 7.1.2 Summary of major concepts
    • 7.1.3 Application
    • 7.1.4 Modes of operation
    • 7.1.5 Allocation of function
  • 7.2 Functional specification  ▶
    • 7.2.1 PLS-PMA (DTE-MAU) Interface protocol  ▶
      • 7.2.1.1 PLS to PMA messages  ▶
        • 7.2.1.1.1 output message
        • 7.2.1.1.2 output_idle message
        • 7.2.1.1.3 normal message
        • 7.2.1.1.4 isolate message (optional)
        • 7.2.1.1.5 mau_request message (optional)
      • 7.2.1.2 PMA to PLS interface  ▶
        • 7.2.1.2.1 input message
        • 7.2.1.2.2 input_idle message
        • 7.2.1.2.3 signal_quality_error message
        • 7.2.1.2.4 mau_available message
        • 7.2.1.2.5 mau_not_available message (optional)
    • 7.2.2 PLS interface to MAC and management entities  ▶
      • 7.2.2.1 PLS-MAC interface  ▶
        • 7.2.2.1.1 OUTPUT_UNIT
        • 7.2.2.1.2 OUTPUT_STATUS
        • 7.2.2.1.3 INPUT_UNIT
        • 7.2.2.1.4 CARRIER_STATUS
        • 7.2.2.1.5 SIGNAL_STATUS
        • 7.2.2.1.6 DATA_VALID_STATUS
      • 7.2.2.2 PLS-management entity interface  ▶
        • 7.2.2.2.1 RESET_REQUEST
        • 7.2.2.2.2 RESET_RESPONSE
        • 7.2.2.2.3 MODE_CONTROL
        • 7.2.2.2.4 SQE_TEST
    • 7.2.3 Frame structure  ▶
      • 7.2.3.1 Silence
      • 7.2.3.2 Preamble
      • 7.2.3.3 Start of Frame Delimiter (SFD)
      • 7.2.3.4 Data
      • 7.2.3.5 End of transmission delimiter
    • 7.2.4 PLS functions  ▶
      • 7.2.4.1 Reset and Identify function
      • 7.2.4.2 Mode function
      • 7.2.4.3 Output function
      • 7.2.4.4 Input function
      • 7.2.4.5 Error Sense function
      • 7.2.4.6 Carrier Sense function
  • 7.3 Signal characteristics  ▶
    • 7.3.1 Signal encoding  ▶
      • 7.3.1.1 Data encoding
      • 7.3.1.2 Control encoding
    • 7.3.2 Signaling rate
    • 7.3.3 Signaling levels
  • 7.4 Electrical characteristics  ▶
    • 7.4.1 Driver characteristics  ▶
      • 7.4.1.1 Differential output voltage, loaded
      • 7.4.1.2 Requirements after idle
      • 7.4.1.3 AC common-mode output voltage
      • 7.4.1.4 Differential output voltage, open circuit
      • 7.4.1.5 DC common-mode output voltage
      • 7.4.1.6 Fault tolerance
    • 7.4.2 Receiver characteristics  ▶
      • 7.4.2.1 Receiver threshold levels
      • 7.4.2.2 AC differential input impedance
      • 7.4.2.3 AC common-mode range
      • 7.4.2.4 Total common-mode range
      • 7.4.2.5 Idle input behavior
      • 7.4.2.6 Fault tolerance
    • 7.4.3 AUI cable characteristics  ▶
      • 7.4.3.1 Conductor size
      • 7.4.3.2 Pair-to-pair balanced crosstalk
      • 7.4.3.3 Differential characteristic impedance
      • 7.4.3.4 Transfer impedance
      • 7.4.3.5 Attenuation
      • 7.4.3.6 Timing jitter
      • 7.4.3.7 Delay
  • 7.5 Functional description of interchange circuits  ▶
    • 7.5.1 General
    • 7.5.2 Definition of interchange circuits  ▶
      • 7.5.2.1 Circuit DO-Data Out
      • 7.5.2.2 Circuit DI-Data In
      • 7.5.2.3 Circuit CO-Control Out (optional)
      • 7.5.2.4 Circuit CI-Control In
      • 7.5.2.5 Circuit VP-Voltage Plus
      • 7.5.2.6 Circuit VC-Voltage Common
      • 7.5.2.7 Circuit PG-Protective Ground
      • 7.5.2.8 Circuit shield terminations
  • 7.6 Mechanical characteristics  ▶
    • 7.6.1 Definition of mechanical interface
    • 7.6.2 Line interface connector
    • 7.6.3 Contact assignments
• 8 Medium Attachment Unit and baseband medium specifications, type 10BASE5  ▶
  • 8.1 Scope  ▶
    • 8.1.1 Overview  ▶
      • 8.1.1.1 Medium Attachment Unit
      • 8.1.1.2 Repeater unit
    • 8.1.2 Definitions
    • 8.1.3 Application perspective: MAU and MEDIUM objectives  ▶
      • 8.1.3.1 Object
      • 8.1.3.2 Compatibility considerations
      • 8.1.3.3 Relationship to PLS and AU interface
      • 8.1.3.4 Modes of operation
  • 8.2 MAU functional specifications  ▶
    • 8.2.1 MAU Physical Layer functions  ▶
      • 8.2.1.1 Transmit function requirements
      • 8.2.1.2 Receive function requirements
      • 8.2.1.3 Collision Presence function requirements
      • 8.2.1.4 Monitor function requirements (optional)
      • 8.2.1.5 Jabber function requirements
    • 8.2.2 MAU interface messages  ▶
      • 8.2.2.1 DTE physical layer to MAU physical layer messages
      • 8.2.2.2 MAU physical layer to DTE physical layer  ▶
        • 8.2.2.2.1 input message
        • 8.2.2.2.2 input_idle message
        • 8.2.2.2.3 mau_available message
        • 8.2.2.2.4 signal_quality_error message
    • 8.2.3 MAU state diagrams
  • 8.3 MAU-medium electrical characteristics  ▶
    • 8.3.1 MAU-to-coaxial cable interface  ▶
      • 8.3.1.1 Input impedance
      • 8.3.1.2 Bias current
      • 8.3.1.3 Coaxial cable signaling levels
      • 8.3.1.4 Transmit output levels symmetry
      • 8.3.1.5 Collision detect thresholds
    • 8.3.2 MAU electrical characteristics  ▶
      • 8.3.2.1 Electrical isolation
      • 8.3.2.2 Power consumption
      • 8.3.2.3 Reliability
    • 8.3.3 MAU—DTE electrical characteristics
    • 8.3.4 MAU–DTE mechanical connection
  • 8.4 Characteristics of the coaxial cable  ▶
    • 8.4.1 Coaxial cable electrical parameters  ▶
      • 8.4.1.1 Characteristic impedance
      • 8.4.1.2 Attenuation
      • 8.4.1.3 Velocity of propagation
      • 8.4.1.4 Edge jitter, untapped cable
      • 8.4.1.5 Transfer impedance
      • 8.4.1.6 Cable dc loop resistance
    • 8.4.2 Coaxial cable properties  ▶
      • 8.4.2.1 Mechanical requirements  ▶
        • 8.4.2.1.1 Generalconstruction
        • 8.4.2.1.2 Center conductor
        • 8.4.2.1.3 Dielectric material
        • 8.4.2.1.4 Shielding system
        • 8.4.2.1.5 Overall jacket
      • 8.4.2.2 Jacket marking
    • 8.4.3 Total segment dc loop resistance
  • 8.5 Coaxial trunk cable connectors  ▶
    • 8.5.1 Inline coaxial extension connector
    • 8.5.2 Coaxial cable terminator  ▶
      • 8.5.2.1 Termination
      • 8.5.2.2 Earthing
    • 8.5.3 MAU-to-coaxial cable connection  ▶
      • 8.5.3.1 Electrical requirements
      • 8.5.3.2 Mechanical requirements  ▶
        • 8.5.3.2.1 Connector housing
        • 8.5.3.2.2 Contact reliability
        • 8.5.3.2.3 Shield probe characteristics
  • 8.6 System considerations  ▶
    • 8.6.1 Transmission system model
    • 8.6.2 Transmission system requirements  ▶
      • 8.6.2.1 Cable sectioning
      • 8.6.2.2 MAU placement
      • 8.6.2.3 Trunk cable system grounding
    • 8.6.3 Labeling
  • 8.7 Environmental specifications  ▶
    • 8.7.1 General safety requirements
    • 8.7.2 Network safety requirements  ▶
      • 8.7.2.1 Installations
      • 8.7.2.2 Grounding
      • 8.7.2.3 Safety
      • 8.7.2.4 Breakdown path
      • 8.7.2.5 Isolation boundary
      • 8.7.2.6 Installation and maintenance guidelines
    • 8.7.3 Electromagnetic environment  ▶
      • 8.7.3.1 Susceptibility levels
      • 8.7.3.2 Emission levels
    • 8.7.4 Temperature and humidity
    • 8.7.5 Regulatory requirements
  • 8.8 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Medium Attachment Unit and baseband medium specifications, type 10BASE5  ▶
    • 8.8.1 Overview
    • 8.8.2 Abbreviations and special symbols  ▶
      • 8.8.2.1 Status symbols
      • 8.8.2.2 Abbreviations
    • 8.8.3 Instructions for completing the PICS proforma  ▶
      • 8.8.3.1 General structure of the PICS proforma
      • 8.8.3.2 Additional information
      • 8.8.3.3 Exception information
      • 8.8.3.4 Conditional items
    • 8.8.4 Identification  ▶
      • 8.8.4.1 Implementation identification
      • 8.8.4.2 Protocol summary
    • 8.8.5 Global statement of conformance
    • 8.8.6 PICS proforma tables for MAU  ▶
      • 8.8.6.1 MAU compatibility
      • 8.8.6.2 Transmit function
      • 8.8.6.3 Receive function
      • 8.8.6.4 Collision function
      • 8.8.6.5 Monitor function
      • 8.8.6.6 Jabber function
      • 8.8.6.7 MAU to coaxial cable interface
      • 8.8.6.8 MAU electrical characteristics
      • 8.8.6.9 MAU-DTE requirements
      • 8.8.6.10 MAU to coaxial cable connection
      • 8.8.6.11 Safety requirements
    • 8.8.7 PICS proforma tables for MAU AUI characteristics  ▶
      • 8.8.7.1 Signal characteristics
      • 8.8.7.2 DI and CI driver characteristics
      • 8.8.7.3 DO receiver characteristics
      • 8.8.7.4 CO receiver characteristics
      • 8.8.7.5 Circuit termination
      • 8.8.7.6 Mechanical characteristics
    • 8.8.8 PICS proforma tables for 10BASE5 coaxial cable  ▶
      • 8.8.8.1 10BASE5 coaxial cable characteristics
• 9 Repeater unit for 10 Mb/s baseband networks  ▶
  • 9.1 Overview
  • 9.2 References
  • 9.3 Definitions
  • 9.4 Compatibility interface  ▶
    • 9.4.1 AUI compatibility
    • 9.4.2 Mixing segment compatibility  ▶
      • 9.4.2.1 Direct coaxial cable attachment compatibility
      • 9.4.2.2 “N” connector compatibility
      • 9.4.2.3 BNC compatibility
      • 9.4.2.4 BFOC/2.5 (10BASE-FP) compatibility
    • 9.4.3 Link segment compatibility  ▶
      • 9.4.3.1 Vendor-dependent IRL
      • 9.4.3.2 Fiber optic FOIRL compatibility
      • 9.4.3.3 Twisted-pair jack compatibility
      • 9.4.3.4 Fiber optic 10BASE-FB and 10BASE-FL compatibility
  • 9.5 Basic functions  ▶
    • 9.5.1 Repeater set network properties
    • 9.5.2 Signal amplification
    • 9.5.3 Signal symmetry
    • 9.5.4 Signal retiming
    • 9.5.5 Data handling  ▶
      • 9.5.5.1 Start-of-packet propagation delays
      • 9.5.5.2 Start-of-packet variability
    • 9.5.6 Collision handling  ▶
      • 9.5.6.1 Collision presence
      • 9.5.6.2 Jam generation
      • 9.5.6.3 Collision-jam propagation delays
      • 9.5.6.4 Transmit recovery time
      • 9.5.6.5 Carrier recovery time
    • 9.5.7 Electrical isolation
  • 9.6 Detailed repeater functions and state diagrams  ▶
    • 9.6.1 State diagram notation
•   Description of state diagram variables  ▶
  • 9.6.2 Data and collision handling  ▶
    • 9.6.3 Preamble regeneration
    • 9.6.4 Fragment extension
    • 9.6.5 MAU Jabber Lockup Protection
    • 9.6.6 Auto-Partitioning/Reconnection (optional)  ▶
      • 9.6.6.1 Overview
      • 9.6.6.2 Detailed auto-partition/reconnection algorithm state diagram
  • 9.7 Electrical isolation  ▶
    • 9.7.1 Environment A requirements
    • 9.7.2 Environment B requirements
  • 9.8 Reliability
  • 9.9 Medium attachment unit and baseband medium specification for a vendor-independent FOIRL  ▶
    • 9.9.1 Scope  ▶
      • 9.9.1.1 Overview
      • 9.9.1.2 Application perspective: FOMAU and medium objectives
      • 9.9.1.3 Compatibility considerations
      • 9.9.1.4 Relationship to AUI
      • 9.9.1.5 Mode of operation
    • 9.9.2 FOMAU functional specifications  ▶
      • 9.9.2.1 Transmit function requirements
      • 9.9.2.2 Receive function requirements
      • 9.9.2.3 Collision Presence function requirements
      • 9.9.2.4 Jabber function requirements
      • 9.9.2.5 Low Light Level Detection function requirements
      • 9.9.2.6 Repeater Unit to FOMAU physical layer messages
      • 9.9.2.7 FOMAU physical layer to repeater unit messages  ▶
        • 9.9.2.7.1 input message
        • 9.9.2.7.2 input_idle message
        • 9.9.2.7.3 fomau_available message
        • 9.9.2.7.4 signal_quality_error message
      • 9.9.2.8 FOMAU state diagrams
    • 9.9.3 FOMAU electrical characteristics  ▶
      • 9.9.3.1 Electrical isolation
      • 9.9.3.2 Power consumption
      • 9.9.3.3 Reliability
      • 9.9.3.4 FOMAU/Repeater unit electrical characteristics
      • 9.9.3.5 FOMAU/Repeater unit mechanical connection
    • 9.9.4 FOMAU/Optical medium interface  ▶
      • 9.9.4.1 Transmit optical parameters  ▶
        • 9.9.4.1.1 Wavelength
        • 9.9.4.1.2 Spectral width
        • 9.9.4.1.3 Optical modulation
        • 9.9.4.1.4 Optical idle signal
        • 9.9.4.1.5 Transmit optical logic polarity
        • 9.9.4.1.6 Optical rise and fall times
        • 9.9.4.1.7 Transmit optical pulse edge jitter
        • 9.9.4.1.8 Peak coupled optical power
      • 9.9.4.2 Receive optical parameters  ▶
        • 9.9.4.2.1 Receive peak optical power range
        • 9.9.4.2.2 Receive optical pulse edge jitter
        • 9.9.4.2.3 Receive optical logic polarity
    • 9.9.5 Characteristics of the optical fiber cable link segment  ▶
      • 9.9.5.1 Optical fiber medium
      • 9.9.5.2 Optical medium connector plug and socket
    • 9.9.6 System requirements  ▶
      • 9.9.6.1 Optical transmission system considerations
      • 9.9.6.2 Timing considerations
    • 9.9.7 Environmental specifications  ▶
      • 9.9.7.1 Safety requirements  ▶
        • 9.9.7.1.1 Electrical safety
        • 9.9.7.1.2 Optical source safety
      • 9.9.7.2 Electromagnetic environment  ▶
        • 9.9.7.2.1 Susceptibility levels
        • 9.9.7.2.2 Emission levels
      • 9.9.7.3 Temperature and humidity
• 10 Medium attachment unit and baseband medium specifications, type 10BASE2  ▶
  • 10.1 Scope  ▶
    • 10.1.1 Overview  ▶
      • 10.1.1.1 Medium attachment unit (normally contained within the data terminal equipment [DTE])
      • 10.1.1.2 Repeater unit
    • 10.1.2 Definitions
    • 10.1.3 Application perspective: MAU and medium objectives  ▶
      • 10.1.3.1 Object
      • 10.1.3.2 Compatibility considerations
      • 10.1.3.3 Relationship to PLS and AUI
      • 10.1.3.4 Mode of operation
  • 10.2 References
  • 10.3 MAU functional specifications  ▶
    • 10.3.1 MAU Physical Layer functional requirements  ▶
      • 10.3.1.1 Transmit function requirements
      • 10.3.1.2 Receive function requirements
      • 10.3.1.3 Collision Presence function requirements
      • 10.3.1.4 Jabber functional requirements
    • 10.3.2 MAU interface messages  ▶
      • 10.3.2.1 DTE to MAU messages
      • 10.3.2.2 MAU to DTE messages  ▶
        • 10.3.2.2.1 input message
        • 10.3.2.2.2 input_idle message
        • 10.3.2.2.3 mau_available message
        • 10.3.2.2.4 signal_quality_error (SQE) message
    • 10.3.3 MAU state diagrams
  • 10.4 MAU–medium electrical characteristics  ▶
    • 10.4.1 MAU-to-coaxial cable interface  ▶
      • 10.4.1.1 Input impedance
      • 10.4.1.2 Bias current
      • 10.4.1.3 Coaxial cable signaling levels
      • 10.4.1.4 Transmit output levels symmetry
      • 10.4.1.5 Collision detect thresholds
    • 10.4.2 MAU electrical characteristics  ▶
      • 10.4.2.1 Electrical isolation
      • 10.4.2.2 Power consumption
      • 10.4.2.3 Reliability
    • 10.4.3 MAU–DTE electrical characteristics
  • 10.5 Characteristics of coaxial cable system  ▶
    • 10.5.1 Coaxial cable electrical parameters  ▶
      • 10.5.1.1 Characteristic impedance
      • 10.5.1.2 Attenuation
      • 10.5.1.3 Velocity of propagation
      • 10.5.1.4 Edge jitter; entire segment without DTEs attached
      • 10.5.1.5 Transfer impedance
      • 10.5.1.6 Cable dc loop resistance
    • 10.5.2 Coaxial cable physical parameters  ▶
      • 10.5.2.1 Mechanical requirements  ▶
        • 10.5.2.1.1 General construction
        • 10.5.2.1.2 Center conductor
        • 10.5.2.1.3 Dielectric material
        • 10.5.2.1.4 Shielding system
        • 10.5.2.1.5 Overall jacket
      • 10.5.2.2 Jacket marking
    • 10.5.3 Total segment dc loop resistance
  • 10.6 Coaxial trunk cable connectors  ▶
    • 10.6.1 In-line coaxial extension connector
    • 10.6.2 Coaxial cable terminator
    • 10.6.3 MAU-to-coaxial cable connection
  • 10.7 System considerations  ▶
    • 10.7.1 Transmission system model
    • 10.7.2 Transmission system requirements  ▶
      • 10.7.2.1 Cable sectioning
      • 10.7.2.2 MAU placement
      • 10.7.2.3 Trunk cable system earthing
      • 10.7.2.4 Static discharge path  ▶
        • 10.7.2.4.1 Installation environment
  • 10.8 Environmental specifications  ▶
    • 10.8.1 Safety requirements  ▶
      • 10.8.1.1 Installations
      • 10.8.1.2 Earthing
    • 10.8.2 Electromagnetic environment  ▶
      • 10.8.2.1 Susceptibility levels
      • 10.8.2.2 Emission levels
    • 10.8.3 Regulatory requirements
• 11 Broadband medium attachment unit and broadband medium specifications, type 10BROAD36  ▶
  • 11.1 Scope  ▶
    • 11.1.1 Overview
    • 11.1.2 Definitions
    • 11.1.3 MAU and medium objectives
    • 11.1.4 Compatibility considerations
    • 11.1.5 Relationship to PLS and AUI
    • 11.1.6 Mode of operation
  • 11.2 MAU functional specifications  ▶
    • 11.2.1 MAU functional requirements  ▶
      • 11.2.1.1 Transmit function requirements
      • 11.2.1.2 Receive function requirements
      • 11.2.1.3 Collision Detection function requirements  ▶
        • 11.2.1.3.1 Collision enforcement transmitter requirements
        • 11.2.1.3.2 Collision enforcement detection requirements
      • 11.2.1.4 Jabber function requirements
    • 11.2.2 DTE PLS to MAU and MAU to DTE PLS messages  ▶
      • 11.2.2.1 DTE Physical Layer to MAU Physical Layer messages
      • 11.2.2.2 MAU Physical Layer to DTE Physical Layer messages  ▶
        • 11.2.2.2.1 input message
        • 11.2.2.2.2 input_idle message
        • 11.2.2.2.3 mau_available message
      • 11.2.2.3 signal_quality_error message
    • 11.2.3 MAU state diagrams  ▶
      • 11.2.3.1 MAU state diagram messages
      • 11.2.3.2 MAU state diagram signal names
  • 11.3 MAU characteristics  ▶
    • 11.3.1 MAU-to-coaxial cable interface  ▶
      • 11.3.1.1 Receive interface  ▶
        • 11.3.1.1.1 Receive input impedance
        • 11.3.1.1.2 Receiver squelch requirements
        • 11.3.1.1.3 Receive level requirements
        • 11.3.1.1.4 Receiver selectivity and linearity requirements
        • 11.3.1.1.5 Receive input mechanical requirements
      • 11.3.1.2 Transmit interface  ▶
        • 11.3.1.2.1 Transmit output impedance
        • 11.3.1.2.2 Transmitted RF packet format
        • 11.3.1.2.3 Transmit spectrum and group delay characteristics
        • 11.3.1.2.4 Transmit out-of-band spectrum
        • 11.3.1.2.5 Transmit level requirements
        • 11.3.1.2.6 Nontransmitting signal leakage requirement
        • 11.3.1.2.7 Transmit spurious output requirement
        • 11.3.1.2.8 Collision enforcement signal leakage requirement
        • 11.3.1.2.9 Transmit output mechanical requirements
    • 11.3.2 MAU frequency allocations  ▶
      • 11.3.2.1 Single-cable systems frequency allocations
      • 11.3.2.2 Dual-cable systems frequency allocations
    • 11.3.3 AUI electrical characteristics  ▶
      • 11.3.3.1 Electrical isolation requirements
      • 11.3.3.2 Current consumption
      • 11.3.3.3 Driver and receiver requirements
      • 11.3.3.4 AUI mechanical connection
    • 11.3.4 MAU transfer characteristics  ▶
      • 11.3.4.1 AUI to coaxial cable framing characteristics.  ▶
        • 11.3.4.1.1 Scrambler and differential encoding requirements
      • 11.3.4.2 Coaxial cable to AUI framing characteristics
      • 11.3.4.3 Circuit DO to circuit DI framing characteristics
      • 11.3.4.4 AUI to coaxial cable delay characteristics  ▶
        • 11.3.4.4.1 Circuit DO to RF data signal delay
        • 11.3.4.4.2 Circuit DO to CE RF output delay
        • 11.3.4.4.3 Transmit postamble to SQE test signal delay
        • 11.3.4.4.4 SQE test signal length
      • 11.3.4.5 Coaxial cable to AUI delay characteristics  ▶
        • 11.3.4.5.1 Received RF to circuit DI delay
        • 11.3.4.5.2 Received RF to CE RF output and circuit CI delay
        • 11.3.4.5.3 Collision enforcement to circuit CI delay
        • 11.3.4.5.4 Receive data to SQE test delay
      • 11.3.4.6 Delay from circuit DO to circuit DI
      • 11.3.4.7 Interpacket gap requirement
      • 11.3.4.8 Bit error rate
    • 11.3.5 Reliability
  • 11.4 System considerations  ▶
    • 11.4.1 Delay budget and network diameter
    • 11.4.2 MAU operation with packets shorter than 512 bits
  • 11.5 Characteristics of the coaxial cable system  ▶
    • 11.5.1 Electrical requirements
    • 11.5.2 Mechanical requirements
    • 11.5.3 Delay requirements
  • 11.6 Frequency translator requirements for the single-cable version  ▶
    • 11.6.1 Electrical requirements
    • 11.6.2 Mechanical requirements
  • 11.7 Environmental specifications  ▶
    • 11.7.1 Safety requirements
    • 11.7.2 Electromagnetic environment  ▶
      • 11.7.2.1 Susceptibility levels
      • 11.7.2.2 Emission levels
    • 11.7.3 Temperature and humidity
• 12 Physical signaling, medium attachment, and baseband medium specifications, type 1BASE5  ▶
  • 12.1 Introduction  ▶
    • 12.1.1 Overview
    • 12.1.2 Scope
    • 12.1.3 Definitions
    • 12.1.4 General characteristics
    • 12.1.5 Compatibility
    • 12.1.6 Objectives of type 1BASE5 specification
  • 12.2 Architecture  ▶
    • 12.2.1 Major concepts
    • 12.2.2 Application perspective
    • 12.2.3 Packet structure  ▶
      • 12.2.3.1 Silence
      • 12.2.3.2 Preamble
      • 12.2.3.3 Start-of-frame delimiter
      • 12.2.3.4 Data
      • 12.2.3.5 End-of-transmission delimiter
  • 12.3 DTE physical signaling (PLS) specification  ▶
    • 12.3.1 Overview  ▶
      • 12.3.1.1 Summary of major concepts
      • 12.3.1.2 Application perspective
    • 12.3.2 Functional specification  ▶
      • 12.3.2.1 PLS-PMA interface  ▶
        • 12.3.2.1.1 output message
        • 12.3.2.1.2 output_idle message
        • 12.3.2.1.3 input message
        • 12.3.2.1.4 input_idle message
      • 12.3.2.2 PLS-MAC interface  ▶
        • 12.3.2.2.1 OUTPUT_UNIT
        • 12.3.2.2.2 OUTPUT_STATUS
        • 12.3.2.2.3 INPUT_UNIT
        • 12.3.2.2.4 CARRIER_STATUS
        • 12.3.2.2.5 SIGNAL_STATUS
      • 12.3.2.3 PLS functions  ▶
        • 12.3.2.3.1 State diagram variables
        • 12.3.2.3.2 Output function
        • 12.3.2.3.3 Input function
        • 12.3.2.3.4 Error Sense function
        • 12.3.2.3.5 Carrier Sense function
      • 12.3.2.4 Signal encoding  ▶
        • 12.3.2.4.1 Data transmission rate
        • 12.3.2.4.2 Data symbol encoding
        • 12.3.2.4.3 Collision presence encoding
        • 12.3.2.4.4 Idle line encoding
  • 12.4 Hub specification  ▶
    • 12.4.1 Overview  ▶
      • 12.4.1.1 Summary of major concepts
      • 12.4.1.2 Application perspective
    • 12.4.2 Hub structure  ▶
      • 12.4.2.1 Upward side
      • 12.4.2.2 Downward side
    • 12.4.3 Hub PLS functional specification  ▶
      • 12.4.3.1 Hub PLS to PMA interface
      • 12.4.3.2 Hub PLS functions  ▶
        • 12.4.3.2.1 State diagram variables
        • 12.4.3.2.2 Upward Signal Transfer function
        • 12.4.3.2.3 Jabber function
        • 12.4.3.2.4 Downward Signal Transfer function
        • 12.4.3.2.5 Retiming (jitter removal)
        • 12.4.3.2.6 Header hub wrap-around
        • 12.4.3.2.7 Collision presence startup
      • 12.4.3.3 Reliability
  • 12.5 Physical medium attachment (PMA) specification  ▶
    • 12.5.1 Overview
    • 12.5.2 PLS-PMA interface
    • 12.5.3 Signal characteristics  ▶
      • 12.5.3.1 Transmitter characteristics  ▶
        • 12.5.3.1.1 Differential output voltage
        • 12.5.3.1.2 Output timing jitter
        • 12.5.3.1.3 Transmitter impedance balance
        • 12.5.3.1.4 Common-mode output voltage
        • 12.5.3.1.5 Common-mode tolerance
        • 12.5.3.1.6 Transmitter fault tolerance
      • 12.5.3.2 Receiver characteristics  ▶
        • 12.5.3.2.1 Differential input voltage
        • 12.5.3.2.2 Input timing jitter
        • 12.5.3.2.3 Idle input behavior
        • 12.5.3.2.4 Differential input impedance
        • 12.5.3.2.5 Common-mode rejection
        • 12.5.3.2.6 Noise immunity
        • 12.5.3.2.7 Receiver fault tolerance
  • 12.6 Medium Dependent Interface (MDI) specification  ▶
    • 12.6.1 Line interface connector
    • 12.6.2 Connector contact assignments
    • 12.6.3 Labeling
  • 12.7 Cable medium characteristics  ▶
    • 12.7.1 Overview
    • 12.7.2 Transmission parameters  ▶
      • 12.7.2.1 Attenuation
      • 12.7.2.2 Differential characteristic impedance
      • 12.7.2.3 Medium timing jitter
      • 12.7.2.4 Dispersion
    • 12.7.3 Coupling parameters  ▶
      • 12.7.3.1 Pair-to-pair crosstalk
      • 12.7.3.2 Multiple-disturber crosstalk
      • 12.7.3.3 Balance
    • 12.7.4 Noise environment  ▶
      • 12.7.4.1 Impulse noise
      • 12.7.4.2 Crosstalk
  • 12.8 Special link specification  ▶
    • 12.8.1 Overview
    • 12.8.2 Transmission characteristics
    • 12.8.3 Permitted configurations
  • 12.9 Timing  ▶
    • 12.9.1 Overview
    • 12.9.2 DTE timing
    • 12.9.3 Medium timing
    • 12.9.4 Special link timing
    • 12.9.5 Hub timing
  • 12.10 Safety  ▶
    • 12.10.1 Isolation
    • 12.10.2 Telephony voltages
• 13 System considerations for multisegment 10 Mb/s baseband networks  ▶
  • 13.1 Overview  ▶
    • 13.1.1 Repeater usage
  • 13.2 Definitions
  • 13.3 Transmission System Model 1
  • 13.4 Transmission System Model 2  ▶
    • 13.4.1 Round-trip collision delay  ▶
      • 13.4.1.1 Worst-case path delay value (PDV) selection
      • 13.4.1.2 Worst-case PDV calculation
    • 13.4.2 Interpacket gap (IPG) shrinkage  ▶
      • 13.4.2.1 Worst-case path variability value (PVV) selection
      • 13.4.2.2 Worst-case path variability value (PVV) calculation
  • 13.5 Full duplex topology limitations
• 14 Twisted-pair medium attachment unit (MAU) and baseband medium, type 10BASE-T  ▶
  • 14.1 Scope  ▶
    • 14.1.1 Overview  ▶
      • 14.1.1.1 Medium Attachment Unit (MAU)
      • 14.1.1.2 Repeater unit
      • 14.1.1.3 Twisted-pair media
    • 14.1.2 Definitions
    • 14.1.3 Application perspective  ▶
      • 14.1.3.1 Objectives
      • 14.1.3.2 Compatibility considerations
      • 14.1.3.3 Modes of operation
    • 14.1.4 Relationship to PLS and AUI
  • 14.2 MAU functional specifications  ▶
    • 14.2.1 MAU functions  ▶
      • 14.2.1.1 Transmit function requirements
      • 14.2.1.2 Receive function requirements
      • 14.2.1.3 Loopback function requirements (half duplex mode only)
      • 14.2.1.4 Collision Presence function requirements (half duplex mode only)
      • 14.2.1.5 signal_quality_error Message (SQE) Test function requirements
      • 14.2.1.6 Jabber function requirements
      • 14.2.1.7 Link Integrity Test function requirements
      • 14.2.1.8 Auto-Negotiation
    • 14.2.2 PMA interface messages  ▶
      • 14.2.2.1 PLS to PMA messages  ▶
        • 14.2.2.1.1 PMA to PLS messages
      • 14.2.2.2 PMA to twisted-pair link segment messages
      • 14.2.2.3 Twisted-pair link segment to PMA messages
      • 14.2.2.4 Interface message time references
    • 14.2.3 MAU state diagrams  ▶
      • 14.2.3.1 State diagram variables
      • 14.2.3.2 State diagram timers
  • 14.3 MAU electrical specifications  ▶
    • 14.3.1 MAU-to-MDI interface characteristics  ▶
      • 14.3.1.1 Isolation requirement
      • 14.3.1.2 Transmitter specifications  ▶
        • 14.3.1.2.1 Differential output voltage
        • 14.3.1.2.2 Transmitter differential output impedance
        • 14.3.1.2.3 Output timing jitter
        • 14.3.1.2.4 Transmitter impedance balance
        • 14.3.1.2.5 Common-mode output voltage
        • 14.3.1.2.6 Transmitter common-mode rejection
        • 14.3.1.2.7 Transmitter fault tolerance
      • 14.3.1.3 Receiver specifications  ▶
        • 14.3.1.3.1 Receiver differential input signals
        • 14.3.1.3.2 Receiver differential noise immunity
        • 14.3.1.3.3 Idle input behavior
        • 14.3.1.3.4 Receiver differential input impedance
        • 14.3.1.3.5 Common-mode rejection
        • 14.3.1.3.6 Receiver fault tolerance
    • 14.3.2 MAU-to-AUI specification  ▶
      • 14.3.2.1 MAU-AUI electrical characteristics
      • 14.3.2.2 MAU-AUI mechanical connection
      • 14.3.2.3 Power consumption
  • 14.4 Characteristics of the simplex link segment  ▶
    • 14.4.1 Overview
    • 14.4.2 Transmission parameters  ▶
      • 14.4.2.1 Insertion loss
      • 14.4.2.2 Differential characteristic impedance
      • 14.4.2.3 Medium timing jitter
      • 14.4.2.4 Delay
    • 14.4.3 Coupling parameters  ▶
      • 14.4.3.1 Differential near-end crosstalk (NEXT) loss  ▶
        • 14.4.3.1.1 Twenty-five-pair cable and twenty-five-pair binder groups
        • 14.4.3.1.2 Four-pair cable
        • 14.4.3.1.3 Other cables
      • 14.4.3.2 Multiple-disturber NEXT (MDNEXT) loss
    • 14.4.4 Noise environment  ▶
      • 14.4.4.1 Impulse noise
      • 14.4.4.2 Crosstalk noise
  • 14.5 MDI specification  ▶
    • 14.5.1 MDI connectors
    • 14.5.2 Crossover function
  • 14.6 System considerations
  • 14.7 Environmental specifications  ▶
    • 14.7.1 General safety
    • 14.7.2 Network safety  ▶
      • 14.7.2.1 Installation
      • 14.7.2.2 Grounding
      • 14.7.2.3 Installation and maintenance guidelines
      • 14.7.2.4 Telephony voltages
    • 14.7.3 Environment  ▶
      • 14.7.3.1 Electromagnetic emission
      • 14.7.3.2 Temperature and humidity
  • 14.8 MAU labeling
  • 14.9 Timing summary
  • 14.10 Protocol Implementation Conformance Statement (PICS) proforma for Clause 14, Twisted-pair medium attachment unit (MAU) and baseband medium, type 10BASE-T  ▶
    • 14.10.1 Introduction  ▶
      • 14.10.1.1 Scope
      • 14.10.1.2 Reference
      • 14.10.1.3 Definitions
      • 14.10.1.4 Conformance
    • 14.10.2 Identification of implementation  ▶
      • 14.10.2.1 Supplier information
      • 14.10.2.2 Implementation information
    • 14.10.3 Identification of the protocol
    • 14.10.4 PICS proforma for 10BASE-T  ▶
      • 14.10.4.1 Abbreviations
      • 14.10.4.2 PICS Completion instructions and implementation statement
      • 14.10.4.3 Additional information
      • 14.10.4.4 References
      • 14.10.4.5 PICS proforma tables for MAU  ▶
        • 14.10.4.5.1 MAU functions
        • 14.10.4.5.2 Transmit function
        • 14.10.4.5.3 Receive function
        • 14.10.4.5.4 Loopback function
        • 14.10.4.5.5 Collision Detect function
        • 14.10.4.5.6 signal_quality_error Message Test function
        • 14.10.4.5.7 Jabber function
        • 14.10.4.5.8 Link Integrity Test function
        • 14.10.4.5.9 MAU state diagram requirements
        • 14.10.4.5.10 AUI requirements
        • 14.10.4.5.11 Isolation requirements
        • 14.10.4.5.12 Transmitter specification
        • 14.10.4.5.13 Receiver specification
        • 14.10.4.5.14 MDI requirements
        • 14.10.4.5.15 Safety requirements
      • 14.10.4.6 PICS proforma tables for MAU AUI characteristics  ▶
        • 14.10.4.6.1 Signal characteristics
        • 14.10.4.6.2 DI and CI driver characteristics
        • 14.10.4.6.3 DO receiver characteristics
        • 14.10.4.6.4 Power consumption
        • 14.10.4.6.5 Circuit termination
        • 14.10.4.6.6 Mechanical characteristics
      • 14.10.4.7 PICS proforma tables for 10BASE-T link segment  ▶
        • 14.10.4.7.1 10BASE-T link segment characteristics
      • 14.10.4.8 PICS proforma tables for Auto-Negotiation able MAUs
• 15 Fiber optic medium and common elements of medium attachment units and star, type 10BASE-F  ▶
  • 15.1 Scope  ▶
    • 15.1.1 Overview  ▶
      • 15.1.1.1 Fiber optic medium attachment units (MAUs)
      • 15.1.1.2 Fiber optic passive star
      • 15.1.1.3 Repeater unit
    • 15.1.2 Definitions
    • 15.1.3 Applications perspective: MAUs, stars, and fiber optic medium  ▶
      • 15.1.3.1 Objectives
      • 15.1.3.2 Compatibility considerations
      • 15.1.3.3 Relationship to PLS and AUI
      • 15.1.3.4 Guidelines for implementation of systems
      • 15.1.3.5 Modes of operation
  • 15.2 MDI optical characteristics  ▶
    • 15.2.1 Transmit optical parameters  ▶
      • 15.2.1.1 Center wavelength
      • 15.2.1.2 Spectral width
      • 15.2.1.3 Optical modulation extinction ratio
      • 15.2.1.4 Optical Idle Signal amplitude
      • 15.2.1.5 Optical transmit pulse logic polarity
      • 15.2.1.6 Optical transmit pulse rise and fall times
      • 15.2.1.7 Optical transmit pulse overshoot and undershoot
      • 15.2.1.8 Optical transmit pulse edge jitter
      • 15.2.1.9 Optical transmit pulse duty cycle distortion
      • 15.2.1.10 Optical transmit average power range
      • 15.2.1.11 Optical transmit signal templates  ▶
        • 15.2.1.11.1 10BASE-FP optical transmit signal template
        • 15.2.1.11.2 10BASE-FB optical transmit signal template
        • 15.2.1.11.3 10BASE-FL Optical transmit signal template
    • 15.2.2 Receive optical parameters  ▶
      • 15.2.2.1 Optical receive average power range
      • 15.2.2.2 Optical receive pulse edge jitter
      • 15.2.2.3 Optical receive pulse logic polarity
      • 15.2.2.4 Optical receive pulse rise and fall times
  • 15.3 Characteristics of the fiber optic medium  ▶
    • 15.3.1 Optical fiber and cable  ▶
      • 15.3.1.1 Attenuation
      • 15.3.1.2 Modal bandwidth
      • 15.3.1.3 Chromatic dispersion
      • 15.3.1.4 Propagation delay
    • 15.3.2 Optical medium connector plug and socket  ▶
      • 15.3.2.1 Optical connector insertion loss
      • 15.3.2.2 Optical connector return loss
    • 15.3.3 Fiber optic medium insertion loss  ▶
      • 15.3.3.1 10BASE-FP segment insertion loss
      • 15.3.3.2 10BASE-FB and 10BASE-FL segment insertion loss
    • 15.3.4 Electrical isolation
  • 15.4 MAU reliability
  • 15.5 MAU–AUI specification  ▶
    • 15.5.1 MAU–AUI electrical characteristics
    • 15.5.2 MAU–AUI mechanical connections
    • 15.5.3 Power consumption
    • 15.5.4 MAU–AUI messages  ▶
      • 15.5.4.1 PLS to PMA messages
      • 15.5.4.2 PMA to PLS messages  ▶
        • 15.5.4.2.1 signal_quality_error message
  • 15.6 Environmental specifications  ▶
    • 15.6.1 Safety requirements
    • 15.6.2 Electromagnetic environment
    • 15.6.3 Other environmental requirements
  • 15.7 MAU labeling  ▶
    • 15.7.1 10BASE-FP star labeling
  • 15.8 Protocol implementation conformance statement (PICS) proformafor Clause 15, Fiber optic medium and common elements of medium attachment units and star, type 10BASE-F  ▶
    • 15.8.1 Introduction
    • 15.8.2 Abbreviations and special symbols  ▶
      • 15.8.2.1 Status symbols
      • 15.8.2.2 Abbreviations
    • 15.8.3 Instructions for completing the pics proforma  ▶
      • 15.8.3.1 General structure of the PICS proforma
      • 15.8.3.2 Additional information
      • 15.8.3.3 Exception information
      • 15.8.3.4 Conditional items
    • 15.8.4 Identification  ▶
      • 15.8.4.1 Implementation identification
      • 15.8.4.2 Protocol summary
    • 15.8.5 Major capabilities/options
    • 15.8.6 PICS Proforma for the fiber optic medium  ▶
      • 15.8.6.1 Characteristics of the fiber optic medium
      • 15.8.6.2 Optical medium connector plug and socket
      • 15.8.6.3 Fiber optic medium insertion loss
      • 15.8.6.4 Electrical isolation requirements
• 16 Fiber optic passive star and medium attachment unit, type 10BASE-FP  ▶
  • 16.1 Scope  ▶
    • 16.1.1 Overview  ▶
      • 16.1.1.1 10BASE-FP medium attachment unit
      • 16.1.1.2 10BASE-FP Star
      • 16.1.1.3 Repeater unit
  • 16.2 PMA interface messages  ▶
    • 16.2.1 PMA-to-MDI interface signal encodings
    • 16.2.2 PMA-to-MDI OTD messages  ▶
      • 16.2.2.1 OTD_output
      • 16.2.2.2 OTD_idle
      • 16.2.2.3 OTD_manch_violation
    • 16.2.3 MDI ORD-to-PMA messages  ▶
      • 16.2.3.1 ORD_input
      • 16.2.3.2 ORD_idle
      • 16.2.3.3 ORD_crv
  • 16.3 10BASE-FP MAU functional specifications  ▶
    • 16.3.1 Transmit function requirements  ▶
      • 16.3.1.1 Preamble encoding  ▶
        • 16.3.1.1.1 Synchronization pattern
        • 16.3.1.1.2 Packet header code rule violation
        • 16.3.1.1.3 Unique word
      • 16.3.1.2 Data transmit
      • 16.3.1.3 Collision encoding (unique word jam)
    • 16.3.2 Receive function requirements  ▶
      • 16.3.2.1 Preamble reconstruction and alignment
      • 16.3.2.2 Data receive
      • 16.3.2.3 Signal presence during collision
    • 16.3.3 Loopback function requirements
    • 16.3.4 Collision presence function requirements  ▶
      • 16.3.4.1 CI Circuit signaling
      • 16.3.4.2 Collision detection
      • 16.3.4.3 End of collision
    • 16.3.5 signal_quality_error Message (SQE) Test function requirements
    • 16.3.6 Jabber function requirements
    • 16.3.7 Link fault detection and low light function requirements
    • 16.3.8 Interface message time references
    • 16.3.9 MAU state diagram  ▶
      • 16.3.9.1 MAU state diagram variables
      • 16.3.9.2 MAU state diagram timers
      • 16.3.9.3 MAU state diagram counters
  • 16.4 Timing summary
  • 16.5 10BASE-FP Star functional specifications  ▶
    • 16.5.1 Star functions  ▶
      • 16.5.1.1 Number of ports
      • 16.5.1.2 Optical power division
      • 16.5.1.3 Configuration
      • 16.5.1.4 Reliability
    • 16.5.2 Star optical characteristics  ▶
      • 16.5.2.1 Star insertion loss
      • 16.5.2.2 Star single output port uniformity
      • 16.5.2.3 Star directivity
  • 16.6 Protocol Implementation Conformance Statement (PICS) proforma for, Clause 16, Fiber optic passive star and medium attachment unit, type 10BASE-FP  ▶
    • 16.6.1 Introduction
    • 16.6.2 Abbreviations and special symbols  ▶
      • 16.6.2.1 Status symbols
      • 16.6.2.2 Abbreviations
    • 16.6.3 Instructions for completing the PICS proforma  ▶
      • 16.6.3.1 General structure of the PICS proforma
      • 16.6.3.2 Additional information
      • 16.6.3.3 Exception information
      • 16.6.3.4 Conditional items
    • 16.6.4 Identification  ▶
      • 16.6.4.1 Implementation identification
      • 16.6.4.2 Protocol summary
    • 16.6.5 Major capabilities/options
    • 16.6.6 PICS proforma for the type 10BASE-FP MAU  ▶
      • 16.6.6.1 Compatibility considerations
      • 16.6.6.2 Optical transmit parameters
      • 16.6.6.3 Optical receive parameters
      • 16.6.6.4 Optical medium connector plug and socket
      • 16.6.6.5 MAU functions
      • 16.6.6.6 PMA interface messages
      • 16.6.6.7 PMA to MDI OTD messages
      • 16.6.6.8 MDI ORD to PMA messages
      • 16.6.6.9 Transmit functions
      • 16.6.6.10 Collision Encoding (Unique Word Jam) function
      • 16.6.6.11 Receive functions
      • 16.6.6.12 Preamble reconstruction and alignment function
      • 16.6.6.13 Data receive function
      • 16.6.6.14 Signal presence during collision
      • 16.6.6.15 Loopback function
      • 16.6.6.16 Collision presence function
      • 16.6.6.17 signal_quality_error Message (SQE) test function
      • 16.6.6.18 Jabber function
      • 16.6.6.19 Link Fault Detect function
      • 16.6.6.20 MAU state diagram requirements
      • 16.6.6.21 MAU-to-AUI signal characteristics
      • 16.6.6.22 MAU-to-AUI DI and CI driver characteristics
      • 16.6.6.23 AUI-to-MAU DO receiver characteristics
      • 16.6.6.24 MAU-to-AUI circuit termination
      • 16.6.6.25 MAU-to-AUI mechanical connections
      • 16.6.6.26 MAU reliability
      • 16.6.6.27 Power consumption
      • 16.6.6.28 PLS–PMA requirements
      • 16.6.6.29 signal_quality_error message (SQE)
      • 16.6.6.30 Environmental requirements
      • 16.6.6.31 MAU labeling
    • 16.6.7 PICS proforma tables for 10BASE-FP stars  ▶
      • 16.6.7.1 Star basic functions
      • 16.6.7.2 Star optical characteristics
      • 16.6.7.3 Star environmental requirements
      • 16.6.7.4 10BASE-FP star labeling
• 17 Fiber optic medium attachment unit, type 10BASE-FB  ▶
  • 17.1 Scope  ▶
    • 17.1.1 Overview  ▶
      • 17.1.1.1 Medium attachment unit
      • 17.1.1.2 Relationship to repeater
      • 17.1.1.3 Remote diagnostic messages
    • 17.1.2 Relationship to AUI
  • 17.2 PMA interface messages  ▶
    • 17.2.1 PMA-to-MDI interface signal encodings
    • 17.2.2 PMA-to-MDI OTD messages  ▶
      • 17.2.2.1 OTD_output
      • 17.2.2.2 OTD_sync_idle
      • 17.2.2.3 OTD_remote_fault
    • 17.2.3 MDI ORD-to-PMA messages  ▶
      • 17.2.3.1 Status decoding
      • 17.2.3.2 ORD_input
      • 17.2.3.3 ORD_sync_idle
      • 17.2.3.4 ORD_remote_fault
      • 17.2.3.5 ORD_invalid_data
    • 17.2.4 Transitions between signals
    • 17.2.5 Signaling rate
  • 17.3 MAU functional specifications  ▶
    • 17.3.1 Transmit function requirements  ▶
      • 17.3.1.1 Data transmit
      • 17.3.1.2 Synchronous idle
      • 17.3.1.3 Fault signaling
    • 17.3.2 Receive function requirements  ▶
      • 17.3.2.1 Data receive
      • 17.3.2.2 Remote status message handling
    • 17.3.3 Collision function requirements  ▶
      • 17.3.3.1 Collision detection
      • 17.3.3.2 End of collision
    • 17.3.4 Loopback function requirements
    • 17.3.5 Fault-handling function requirements
    • 17.3.6 Jabber function requirements
    • 17.3.7 Low light level detection function requirements
    • 17.3.8 Synchronous qualification function requirements
    • 17.3.9 Interface message time references
    • 17.3.10 MAU state diagrams  ▶
      • 17.3.10.1 MAU state diagram variables
      • 17.3.10.2 MAU state diagram timers
  • 17.4 Timing summary
  • 17.5 Protocol implementation conformance statement (PICS) proforma for Clause , Fiber optic medium attachment unit, type 10BASE-FB  ▶
    • 17.5.1 Introduction
    • 17.5.2 Abbreviations and special symbols  ▶
      • 17.5.2.1 Status symbols  ▶
        • 17.5.2.1.1 Abbreviations
    • 17.5.3 Instructions for completing the PICS proforma  ▶
      • 17.5.3.1 General structure of the PICS proforma
      • 17.5.3.2 Additional information
      • 17.5.3.3 Exception information
      • 17.5.3.4 Conditional items
    • 17.5.4 Identification  ▶
      • 17.5.4.1 Implementation identification
      • 17.5.4.2 Protocol summary
    • 17.5.5 PICS proforma for the type 10BASE-FB MAU
    • 17.5.6 PICS proforma for the type 10BASE-FB MAU  ▶
      • 17.5.6.1 Compatibility considerations
      • 17.5.6.2 Optical transmit parameters
      • 17.5.6.3 Optical receive parameters
      • 17.5.6.4 Optical medium connector plug and socket
      • 17.5.6.5 MAU functions
      • 17.5.6.6 PMA-to-MDI OTD messages and signaling
      • 17.5.6.7 MDI ORD-to-PMA messages and signaling
      • 17.5.6.8 Transitions between signals
      • 17.5.6.9 Signaling rate
      • 17.5.6.10 Transmit functions
      • 17.5.6.11 Receive functions
      • 17.5.6.12 Data receive function
      • 17.5.6.13 Remote status message handling
      • 17.5.6.14 Collision function requirements
      • 17.5.6.15 End of collision
      • 17.5.6.16 Loopback function
      • 17.5.6.17 Fault-handling function
      • 17.5.6.18 Jabber-handling function
      • 17.5.6.19 Low light detection
      • 17.5.6.20 Synchronous qualification
      • 17.5.6.21 MAU state diagram requirements
      • 17.5.6.22 MAU reliability
      • 17.5.6.23 PLS–PMA requirements
      • 17.5.6.24 signal_quality_error message (SQE)
      • 17.5.6.25 Environmental requirements
      • 17.5.6.26 MAU labeling
• 18 Fiber optic medium attachment unit, type 10BASE-FL  ▶
  • 18.1 Scope  ▶
    • 18.1.1 Overview  ▶
      • 18.1.1.1 10BASE-FL medium attachment unit (MAU)
      • 18.1.1.2 Repeater unit
  • 18.2 PMA interface messages  ▶
    • 18.2.1 PMA to fiber optic link segment messages  ▶
      • 18.2.1.1 OTD_output.
      • 18.2.1.2 OTD_idle
    • 18.2.2 Fiber optic link segment to PMA messages  ▶
      • 18.2.2.1 ORD_input
      • 18.2.2.2 ORD_idle
    • 18.2.3 Interface message time references
  • 18.3 MAU functional specifications  ▶
    • 18.3.1 MAU functions  ▶
      • 18.3.1.1 Transmit function requirements
      • 18.3.1.2 Receive function requirements
      • 18.3.1.3 Loopback function requirements (half duplex mode only)
      • 18.3.1.4 Collision Presence function requirements (half duplex mode only)
      • 18.3.1.5 signal_quality_error Message (SQE) Test function requirements
      • 18.3.1.6 Jabber function requirements
      • 18.3.1.7 Link Integrity Test function requirements
      • 18.3.1.8 Auto-Negotiation
    • 18.3.2 MAU state diagrams  ▶
      • 18.3.2.1 MAU state diagram variables
      • 18.3.2.2 MAU state diagram timers
  • 18.4 Timing summary
  • 18.5 Protocol implementation conformance statement (PICS) proforma for Clause , Fiber optic medium attachment unit, type 10BASE-FL   ▶
    • 18.5.1 Introduction
    • 18.5.2 Abbreviations and special symbols  ▶
      • 18.5.2.1 Status symbols
      • 18.5.2.2 Abbreviations
    • 18.5.3 Instructions for completing the PICS proforma  ▶
      • 18.5.3.1 General structure of the PICS proforma
      • 18.5.3.2 Additional information
      • 18.5.3.3 Exception information
      • 18.5.3.4 Conditional items
    • 18.5.4 Identification  ▶
      • 18.5.4.1 Implementation identification
      • 18.5.4.2 Protocol summary
    • 18.5.5 Major capabilities/options
    • 18.5.6 PICS proforma tables for the type 10BASE-FL MAU  ▶
      • 18.5.6.1 Compatibility considerations
      • 18.5.6.2 Optical transmit parameter
      • 18.5.6.3 Optical receive parameters
      • 18.5.6.4 Optical medium connector plug and socket
      • 18.5.6.5 MAU functions
      • 18.5.6.6 PMA interface messages
      • 18.5.6.7 PMA-to-MDI OTD messages
      • 18.5.6.8 MDI ORD-to-PMA messages
      • 18.5.6.9 Transmit function
      • 18.5.6.10 Receive function
      • 18.5.6.11 Loopback function
      • 18.5.6.12 Collision Presence function
      • 18.5.6.13 signal_quality_error Message (SQE) Test function
      • 18.5.6.14 Jabber function
      • 18.5.6.15 Link Integrity Test function
      • 18.5.6.16 MAU state diagram requirements
      • 18.5.6.17 MAU-to-AUI signal characteristics
      • 18.5.6.18 MAU-to-AUI DI and CI driver characteristics
      • 18.5.6.19 AUI-to-MAU DO receiver characteristics
      • 18.5.6.20 AUI circuit termination
      • 18.5.6.21 MAU-to-AUI mechanical connections
      • 18.5.6.22 MAU reliability
      • 18.5.6.23 Power consumption
      • 18.5.6.24 PLS–PMA requirements
      • 18.5.6.25 signal_quality_error message (SQE)
      • 18.5.6.26 Environmental requirements
      • 18.5.6.27 MAU labeling
• 19 Layer Management for 10 Mb/s baseband repeaters  ▶
  • 19.1 Introduction  ▶
    • 19.1.1 Scope
    • 19.1.2 Relationship to objects in 802.1F-1993
    • 19.1.3 Definitions
    • 19.1.4 Symbols and abbreviations
    • 19.1.5 Management model
  • 19.2 Managed objects  ▶
    • 19.2.1 Introduction
    • 19.2.2 Overview of managed objects  ▶
      • 19.2.2.1 Text description of managed objects
      • 19.2.2.2 Port functions to support management
      • 19.2.2.3 Containment
      • 19.2.2.4 Naming
      • 19.2.2.5 Packages and capabilities
    • 19.2.3 Repeater managed object class  ▶
      • 19.2.3.1 Repeater attributes  ▶
        • 19.2.3.1.1 aRepeaterID
        • 19.2.3.1.2 aRepeaterGroupCapacity
        • 19.2.3.1.3 aGroupMap
        • 19.2.3.1.4 aRepeaterHealthState
        • 19.2.3.1.5 aRepeaterHealthText
        • 19.2.3.1.6 aRepeaterHealthData
        • 19.2.3.1.7 aTransmitCollisions
      • 19.2.3.2 Repeater actions  ▶
        • 19.2.3.2.1 acResetRepeater
        • 19.2.3.2.2 acExecuteNonDisruptiveSelfTest
      • 19.2.3.3 Repeater notifications  ▶
        • 19.2.3.3.1 nRepeaterHealth
        • 19.2.3.3.2 nRepeaterReset
        • 19.2.3.3.3 nGroupMapChange
    • 19.2.4 ResourceTypeID Managed Object Class
    • 19.2.5 Group managed object class  ▶
      • 19.2.5.1 Group attributes  ▶
        • 19.2.5.1.1 aGroupID
        • 19.2.5.1.2 aGroupPortCapacity
        • 19.2.5.1.3 aPortMap
      • 19.2.5.2 Group Notifications  ▶
        • 19.2.5.2.1 nPortMapChange
    • 19.2.6 Port managed object class  ▶
      • 19.2.6.1 Port Attributes  ▶
        • 19.2.6.1.1 aPortID
        • 19.2.6.1.2 aPortAdminState
        • 19.2.6.1.3 aAutoPartitionState
        • 19.2.6.1.4 aReadableFrames
        • 19.2.6.1.5 aReadableOctets
        • 19.2.6.1.6 aFrameCheckSequenceErrors
        • 19.2.6.1.7 aAlignmentErrors
        • 19.2.6.1.8 aFramesTooLong
        • 19.2.6.1.9 aShortEvents
        • 19.2.6.1.10 aRunts
        • 19.2.6.1.11 aCollisions
        • 19.2.6.1.12 aLateEvents
        • 19.2.6.1.13 aVeryLongEvents
        • 19.2.6.1.14 aDataRateMismatches
        • 19.2.6.1.15 aAutoPartitions
        • 19.2.6.1.16 aLastSourceAddress
        • 19.2.6.1.17 aSourceAddressChanges
      • 19.2.6.2 Port Actions  ▶
        • 19.2.6.2.1 acPortAdminControl
• 20 Layer Management for 10 Mb/s baseband medium attachment units  ▶
  • 20.1 Introduction  ▶
    • 20.1.1 Scope
    • 20.1.2 Management model
  • 20.2 Managed objects  ▶
    • 20.2.1 Text description of managed objects  ▶
      • 20.2.1.1 Naming
      • 20.2.1.2 Containment
      • 20.2.1.3 Packages
    • 20.2.2 MAU Managed object class  ▶
      • 20.2.2.1 MAU attributes  ▶
        • 20.2.2.1.1 aMAUID
        • 20.2.2.1.2 aMAUType
        • 20.2.2.1.3 aMediaAvailable
        • 20.2.2.1.4 aLoseMediaCounter
        • 20.2.2.1.5 aJabber
        • 20.2.2.1.6 aMAUAdminState
        • 20.2.2.1.7 aBbMAUXmitRcvSplitType
        • 20.2.2.1.8 aBroadbandFrequencies
      • 20.2.2.2 MAU actions  ▶
        • 20.2.2.2.1 acResetMAU
        • 20.2.2.2.2 acMAUAdminControl
      • 20.2.2.3 MAU notifications  ▶
        • 20.2.2.3.1 nJabber
• 21 Introduction to 100 Mb/s baseband networks, type 100BASE-T  ▶
  • 21.1 Overview  ▶
    • 21.1.1 Reconciliation Sublayer (RS) and Media Independent Interface (MII)
    • 21.1.2 Physical Layer signaling systems
    • 21.1.3 Repeater
    • 21.1.4 Auto-Negotiation
    • 21.1.5 Management
  • 21.2 References
  • 21.3 Definitions
  • 21.4 Abbreviations
  • 21.5 State diagrams  ▶
    • 21.5.1 Actions inside state blocks
    • 21.5.2 State diagram variables
    • 21.5.3 State transitions
    • 21.5.4 Operators
  • 21.6 Protocol Implementation Conformance Statement (PICS) proforma  ▶
    • 21.6.1 Introduction
    • 21.6.2 Abbreviations and special symbols
    • 21.6.3 Instructions for completing the PICS proforma
    • 21.6.4 Additional information
    • 21.6.5 Exceptional information
    • 21.6.6 Conditional items
  • 21.7 Relation of 100BASE-T to other standards
  • 21.8 MAC delay constraints (exposed MII)
• 22 Reconciliation Sublayer (RS) and Media Independent Interface (MII)  ▶
  • 22.1 Overview  ▶
    • 22.1.1 Summary of major concepts
    • 22.1.2 Application
    • 22.1.3 Rates of operation
    • 22.1.4 Allocation of functions
    • 22.1.5 Relationship of MII and GMII
  • 22.2 Functional specifications  ▶
    • 22.2.1 Mapping of MII signals to PLS service primitives and Station Management  ▶
      • 22.2.1.1 Mapping of PLS_DATA.request  ▶
        • 22.2.1.1.1 Function
        • 22.2.1.1.2 Semantics of the service primitive
        • 22.2.1.1.3 When generated
      • 22.2.1.2 Mapping of PLS_DATA.indicate  ▶
        • 22.2.1.2.1 Function
        • 22.2.1.2.2 Semantics of the service primitive
        • 22.2.1.2.3 When generated
      • 22.2.1.3 Mapping of PLS_CARRIER.indicate  ▶
        • 22.2.1.3.1 Function
        • 22.2.1.3.2 Semantics of the service primitive
        • 22.2.1.3.3 When generated
      • 22.2.1.4 Mapping of PLS_SIGNAL.indicate  ▶
        • 22.2.1.4.1 Function
        • 22.2.1.4.2 Semantics of the service primitive
        • 22.2.1.4.3 When generated
      • 22.2.1.5 Response to RX_ER indication from MII
      • 22.2.1.6 Conditions for generation of TX_ER
      • 22.2.1.7 Mapping of PLS_DATA_VALID.indicate  ▶
        • 22.2.1.7.1 Function
        • 22.2.1.7.2 Semantics of the service primitive
        • 22.2.1.7.3 When generated
    • 22.2.2 MII signal functional specifications  ▶
      • 22.2.2.1 TX_CLK (transmit clock)
      • 22.2.2.2 RX_CLK (receive clock)
      • 22.2.2.3 TX_EN (transmit enable)
      • 22.2.2.4 TXD (transmit data)
      • 22.2.2.5 TX_ER (transmit coding error)
      • 22.2.2.6 RX_DV (Receive Data Valid)
      • 22.2.2.7 RXD (receive data)
      • 22.2.2.8 RX_ER (receive error)
      • 22.2.2.9 CRS (carrier sense)
      • 22.2.2.10 COL (collision detected)
      • 22.2.2.11 MDC (management data clock)
      • 22.2.2.12 MDIO (management data input/output)
    • 22.2.3 Frame structure  ▶
      • 22.2.3.1 Inter-frame
      • 22.2.3.2 Preamble and start of frame delimiter  ▶
        • 22.2.3.2.1 Transmit case
        • 22.2.3.2.2 Receive case
      • 22.2.3.3 Data
      • 22.2.3.4 End-of-Frame delimiter (EFD)
      • 22.2.3.5 Handling of excess nibbles
    • 22.2.4 Management functions  ▶
      • 22.2.4.1 Control register (Register 0)  ▶
        • 22.2.4.1.1 Reset
        • 22.2.4.1.2 Loopback
        • 22.2.4.1.3 Speed selection
        • 22.2.4.1.4 Auto-Negotiation enable
        • 22.2.4.1.5 Power down
        • 22.2.4.1.6 Isolate
        • 22.2.4.1.7 Restart Auto-Negotiation
        • 22.2.4.1.8 Duplex mode
        • 22.2.4.1.9 Collision test
        • 22.2.4.1.10 Speed selection
        • 22.2.4.1.11 Reserved bits
      • 22.2.4.2 Status register (Register 1)  ▶
        • 22.2.4.2.1 100BASE-T4 ability
        • 22.2.4.2.2 100BASE-X full duplex ability
        • 22.2.4.2.3 100BASE-X half duplex ability
        • 22.2.4.2.4 10 Mb/s full duplex ability
        • 22.2.4.2.5 10 Mb/s half duplex ability
        • 22.2.4.2.6 100BASE-T2 full duplex ability
        • 22.2.4.2.7 100BASE-T2 half duplex ability
        • 22.2.4.2.8 Reserved bits
        • 22.2.4.2.9 MF preamble suppression ability
        • 22.2.4.2.10 Auto-Negotiation complete
        • 22.2.4.2.11 Remote fault
        • 22.2.4.2.12 Auto-Negotiation ability
        • 22.2.4.2.13 Link Status
        • 22.2.4.2.14 Jabber detect
        • 22.2.4.2.15 Extended capability
        • 22.2.4.2.16 Extended status
      • 22.2.4.3 Extended capability registers  ▶
        • 22.2.4.3.1 PHY Identifier (Registers 2 and 3)
        • 22.2.4.3.2 Auto-Negotiation advertisement (Register 4)
        • 22.2.4.3.3 Auto-Negotiation link partner ability (Register 5)
        • 22.2.4.3.4 Auto-Negotiation expansion (Register 6)
        • 22.2.4.3.5 Auto-Negotiation next page (Register 7)
        • 22.2.4.3.6 Auto-Negotiation link partner Received Next Page (Register 8)
        • 22.2.4.3.7 MASTER-SLAVE control register (Register 9)
        • 22.2.4.3.8 MASTER-SLAVE status register (Register 10)
        • 22.2.4.3.9 PHY specific registers
      • 22.2.4.4 Extended Status register (Register 15)  ▶
        • 22.2.4.4.1 1000BASE-X full duplex ability
        • 22.2.4.4.2 1000BASE-X half duplex ability
        • 22.2.4.4.3 1000BASE-T full duplex ability
        • 22.2.4.4.4 1000BASE-T half duplex ability
        • 22.2.4.4.5 Reserved bits
      • 22.2.4.5 Management frame structure  ▶
        • 22.2.4.5.1 IDLE (IDLE condition)
        • 22.2.4.5.2 PRE(preamble)
        • 22.2.4.5.3 ST (start of frame)
        • 22.2.4.5.4 OP (operation code)
        • 22.2.4.5.5 PHYAD (PHY Address)
        • 22.2.4.5.6 REGAD (Register Address)
        • 22.2.4.5.7 TA (turnaround)
        • 22.2.4.5.8 DATA (data)
  • 22.3 Signal timing characteristics  ▶
    • 22.3.1 Signals that are synchronous to TX_CLK  ▶
      • 22.3.1.1 TX_EN
      • 22.3.1.2 TXD<3:0>
      • 22.3.1.3 TX_ER
    • 22.3.2 Signals that are synchronous to RX_CLK  ▶
      • 22.3.2.1 RX_DV
      • 22.3.2.2 RXD<3:0>
      • 22.3.2.3 RX_ER
    • 22.3.3 Signals that have no required clock relationship  ▶
      • 22.3.3.1 CRS
      • 22.3.3.2 COL
    • 22.3.4 MDIO timing relationship to MDC
  • 22.4 Electrical characteristics  ▶
    • 22.4.1 Signal levels
    • 22.4.2 Signal paths
    • 22.4.3 Driver characteristics  ▶
      • 22.4.3.1 DC characteristics
      • 22.4.3.2 AC characteristics
    • 22.4.4 Receiver characteristics  ▶
      • 22.4.4.1 Voltage thresholds
      • 22.4.4.2 Input current
      • 22.4.4.3 Input capacitance
    • 22.4.5 Cable characteristics  ▶
      • 22.4.5.1 Conductor size
      • 22.4.5.2 Characteristic impedance
      • 22.4.5.3 Delay
      • 22.4.5.4 Delay variation
      • 22.4.5.5 Shielding
      • 22.4.5.6 DC resistance
    • 22.4.6 Hot insertion and removal
  • 22.5 Power supply  ▶
    • 22.5.1 Supply voltage
    • 22.5.2 Load current
    • 22.5.3 Short-circuit protection
  • 22.6 Mechanical characteristics  ▶
    • 22.6.1 Definition of mechanical interface
    • 22.6.2 Shielding effectiveness and transfer impedance
    • 22.6.3 Connector pin numbering
    • 22.6.4 Clearance dimensions
    • 22.6.5 Contact assignments
  • 22.7 Protocol Implementation Conformance Statement (PICS) proforma for Clause Reconciliation Sublayer (RS) and Media Independent Interface (MII)  ▶
    • 22.7.1 Introduction
    • 22.7.2 Identification  ▶
      • 22.7.2.1 Implementation identification
      • 22.7.2.2 Protocol summary
      • 22.7.2.3 Major capabilities/options
    • 22.7.3 PICS proforma tables for reconciliation sublayer and media independent interface  ▶
      • 22.7.3.1 Mapping of PLS service primitives
      • 22.7.3.2 MII signal functional specifications
      • 22.7.3.3 Frame structure
      • 22.7.3.4 Management functions
      • 22.7.3.5 Signal timing characteristics
      • 22.7.3.6 Electrical characteristics
      • 22.7.3.7 Power supply
      • 22.7.3.8 Mechanical characteristics
• 23 Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 100BASE-T4  ▶
  • 23.1 Overview  ▶
    • 23.1.1 Scope
    • 23.1.2 Objectives
    • 23.1.3 Relation of 100BASE-T4 to other standards
    • 23.1.4 Summary  ▶
      • 23.1.4.1 Summary of Physical Coding Sublayer (PCS) specification
      • 23.1.4.2 Summary of physical medium attachment (PMA) specification
    • 23.1.5 Application of 100BASE-T4  ▶
      • 23.1.5.1 Compatibility considerations
      • 23.1.5.2 Incorporating the 100BASE-T4 PHY into a DTE
      • 23.1.5.3 Use of 100BASE-T4 PHY for point-to-point communication
      • 23.1.5.4 Support for Auto-Negotiation
  • 23.2 PCS functional specifications  ▶
    • 23.2.1 PCS functions  ▶
      • 23.2.1.1 PCS Reset function
      • 23.2.1.2 PCS Transmit function  ▶
        • 23.2.1.2.1 DC balance encoding rules
      • 23.2.1.3 PCS Receive function  ▶
        • 23.2.1.3.1 Error-detecting rules
      • 23.2.1.4 PCS Error Sense function
      • 23.2.1.5 PCS Carrier Sense function
      • 23.2.1.6 PCS Collision Presence function
    • 23.2.2 PCS interfaces  ▶
      • 23.2.2.1 PCS-MII interface signals
      • 23.2.2.2 PCS—Management entity signals
    • 23.2.3 Frame structure
    • 23.2.4 PCS state diagrams  ▶
      • 23.2.4.1 PCS state diagram constants
      • 23.2.4.2 PCS state diagram variables
      • 23.2.4.3 PCS state diagram timer
      • 23.2.4.4 PCS state diagram functions
      • 23.2.4.5 PCS state diagrams
    • 23.2.5 PCS electrical specifications
  • 23.3 PMA service interface  ▶
    • 23.3.1 PMA_TYPE.indicate  ▶
      • 23.3.1.1 Semantics of the service primitive
      • 23.3.1.2 When generated
      • 23.3.1.3 Effect of receipt
    • 23.3.2 PMA_UNITDATA.request  ▶
      • 23.3.2.1 Semantics of the service primitive
      • 23.3.2.2 When generated
      • 23.3.2.3 Effect of receipt
    • 23.3.3 PMA_UNITDATA.indicate  ▶
      • 23.3.3.1 Semantics of the service primitive
      • 23.3.3.2 When generated
      • 23.3.3.3 Effect of receipt
    • 23.3.4 PMA_CARRIER.indicate  ▶
      • 23.3.4.1 Semantics of the service primitive
      • 23.3.4.2 When generated
      • 23.3.4.3 Effect of receipt
    • 23.3.5 PMA_LINK.indicate  ▶
      • 23.3.5.1 Semantics of the service primitive
      • 23.3.5.2 When generated
      • 23.3.5.3 Effect of receipt
    • 23.3.6 PMA_LINK.request  ▶
      • 23.3.6.1 Semantics of the service primitive
      • 23.3.6.2 Default value of parameter link_control
      • 23.3.6.3 When generated
      • 23.3.6.4 Effect of receipt
    • 23.3.7 PMA_RXERROR.indicate  ▶
      • 23.3.7.1 Semantics of the service primitive
      • 23.3.7.2 When generated
      • 23.3.7.3 Effect of receipt
  • 23.4 PMA functional specifications  ▶
    • 23.4.1 PMA functions  ▶
      • 23.4.1.1 PMA Reset function
      • 23.4.1.2 PMA Transmit function
      • 23.4.1.3 PMA Receive function
      • 23.4.1.4 PMA Carrier Sense function
      • 23.4.1.5 Link Integrity function
      • 23.4.1.6 PMA Align function
      • 23.4.1.7 Clock Recovery function
    • 23.4.2 PMA interface messages
    • 23.4.3 PMA state diagrams  ▶
      • 23.4.3.1 PMA constants
      • 23.4.3.2 State diagram variables
      • 23.4.3.3 State diagram timers
      • 23.4.3.4 State diagram counters
      • 23.4.3.5 Link Integrity state diagram
  • 23.5 PMA electrical specifications  ▶
    • 23.5.1 PMA-to-MDI interface characteristics  ▶
      • 23.5.1.1 Isolation requirement
      • 23.5.1.2 Transmitter specifications  ▶
        • 23.5.1.2.1 Peak differential output voltage
        • 23.5.1.2.2 Differential output templates
        • 23.5.1.2.3 Differential output ISI (intersymbol interference)
        • 23.5.1.2.4 Transmitter differential output impedance
        • 23.5.1.2.5 Output timing jitter
        • 23.5.1.2.6 Transmitter impedance balance
        • 23.5.1.2.7 Common-mode output voltage
        • 23.5.1.2.8 Transmitter common-mode rejection
        • 23.5.1.2.9 Transmitter fault tolerance
        • 23.5.1.2.10 Transmit clock frequency
      • 23.5.1.3 Receiver specifications  ▶
        • 23.5.1.3.1 Receiver differential input signals
        • 23.5.1.3.2 Receiver differential noise immunity
        • 23.5.1.3.3 Receiver differential input impedance
        • 23.5.1.3.4 Common-mode rejection
        • 23.5.1.3.5 Receiver fault tolerance
        • 23.5.1.3.6 Receiver frequency tolerance
    • 23.5.2 Power consumption
  • 23.6 Link segment characteristics  ▶
    • 23.6.1 Cabling
    • 23.6.2 Link transmission parameters  ▶
      • 23.6.2.1 Insertion loss
      • 23.6.2.2 Differential characteristic impedance
      • 23.6.2.3 Coupling parameters  ▶
        • 23.6.2.3.1 Differential Near-End Crosstalk (NEXT) loss
        • 23.6.2.3.2 Multiple-disturber NEXT (MDNEXT) loss
        • 23.6.2.3.3 Equal Level Far-End Crosstalk (ELFEXT) loss
        • 23.6.2.3.4 Multiple-disturber ELFEXT (MDELFEXT) loss
      • 23.6.2.4 Delay  ▶
        • 23.6.2.4.1 Maximum link delay
        • 23.6.2.4.2 Maximum link delay per meter
        • 23.6.2.4.3 Difference in link delays
    • 23.6.3 Noise  ▶
      • 23.6.3.1 Near-End Crosstalk
      • 23.6.3.2 Far-End Crosstalk
    • 23.6.4 Installation practice  ▶
      • 23.6.4.1 Connector installation practices
      • 23.6.4.2 Disallow use of Category 3 cable with more than four pairs
      • 23.6.4.3 Allow use of Category 5 jumpers with up to 25 pairs
  • 23.7 MDI specification  ▶
    • 23.7.1 MDI connectors
    • 23.7.2 Crossover function
  • 23.8 System considerations
  • 23.9 Environmental specifications  ▶
    • 23.9.1 General safety
    • 23.9.2 Network safety  ▶
      • 23.9.2.1 Installation
      • 23.9.2.2 Grounding
      • 23.9.2.3 Installation and maintenance guidelines
      • 23.9.2.4 Telephony voltages
    • 23.9.3 Environment  ▶
      • 23.9.3.1 Electromagnetic emission
      • 23.9.3.2 Temperature and humidity
  • 23.10 PHY labeling
  • 23.11 Timing summary  ▶
    • 23.11.1 Timing references
    • 23.11.2 Definitions of controlled parameters
    • 23.11.3 Table of required timing values
  • 23.12 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer, and baseband medium, type 100BASE-T4  ▶
    • 23.12.1 Introduction
    • 23.12.2 Identification  ▶
      • 23.12.2.1 Implementation identification
      • 23.12.2.2 Protocol summary
    • 23.12.3 Major capabilities/options
    • 23.12.4 PICS proforma tables for the Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 100BASE-T4  ▶
      • 23.12.4.1 Compatibility considerations
      • 23.12.4.2 PCS Transmit functions
      • 23.12.4.3 PCS Receive functions
      • 23.12.4.4 Other PCS functions
      • 23.12.4.5 PCS state diagram variables
      • 23.12.4.6 PMA service interface
      • 23.12.4.7 PMA Transmit functions
      • 23.12.4.8 PMA Receive functions
      • 23.12.4.9 Link Integrity functions
      • 23.12.4.10 PMA Align functions
      • 23.12.4.11 Other PMA functions
      • 23.12.4.12 Isolation requirements
      • 23.12.4.13 PMA electrical requirements
      • 23.12.4.14 Characteristics of the link segment
      • 23.12.4.15 MDI requirements
      • 23.12.4.16 General safety and environmental requirements
      • 23.12.4.17 Timing requirements
• 24 Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 100BASE-X  ▶
  • 24.1 Overview  ▶
    • 24.1.1 Scope
    • 24.1.2 Objectives
    • 24.1.3 Relationship of 100BASE-X to other standards
    • 24.1.4 Summary of 100BASE-X sublayers  ▶
      • 24.1.4.1 Physical Coding Sublayer (PCS)
      • 24.1.4.2 Physical Medium Attachment (PMA) sublayer
      • 24.1.4.3 Physical Medium Dependent (PMD) sublayer
    • 24.1.5 Inter-sublayer interfaces
    • 24.1.6 Functional block diagram
    • 24.1.7 State diagram conventions
  • 24.2 Physical Coding Sublayer (PCS)  ▶
    • 24.2.1 Service Interface (MII)
    • 24.2.2 Functional requirements  ▶
      • 24.2.2.1 Code-groups  ▶
        • 24.2.2.1.1 Data code-groups
        • 24.2.2.1.2 Idle code-groups
        • 24.2.2.1.3 Control code-groups
        • 24.2.2.1.4 Start-of-Stream Delimiter (/J/K/)
        • 24.2.2.1.5 End-of-Stream delimiter (/T/R/)
        • 24.2.2.1.6 Invalid code-groups
      • 24.2.2.2 Encapsulation
      • 24.2.2.3 Data delay
      • 24.2.2.4 Mapping between MII and PMA
    • 24.2.3 State variables  ▶
      • 24.2.3.1 Constants
      • 24.2.3.2 Variables
      • 24.2.3.3 Functions
      • 24.2.3.4 Timers
      • 24.2.3.5 Messages
    • 24.2.4 State diagrams  ▶
      • 24.2.4.1 Transmit Bits
      • 24.2.4.2 Transmit
      • 24.2.4.3 Receive Bits
      • 24.2.4.4 Receive  ▶
        • 24.2.4.4.1 Detecting channel activity
        • 24.2.4.4.2 Code-group alignment
        • 24.2.4.4.3 Stream decoding
        • 24.2.4.4.4 Stream termination
      • 24.2.4.5 Carrier Sense
  • 24.3 Physical Medium Attachment (PMA) sublayer  ▶
    • 24.3.1 Service interface  ▶
      • 24.3.1.1 PMA_TYPE.indicate  ▶
        • 24.3.1.1.1 Semantics of the service primitive
        • 24.3.1.1.2 When generated
        • 24.3.1.1.3 Effect of receipt
      • 24.3.1.2 PMA_UNITDATA.request  ▶
        • 24.3.1.2.1 Semantics of the service primitive
        • 24.3.1.2.2 When generated
        • 24.3.1.2.3 Effect of receipt
      • 24.3.1.3 PMA_UNITDATA.indicate  ▶
        • 24.3.1.3.1 Semantics of the service primitive
        • 24.3.1.3.2 When generated
        • 24.3.1.3.3 Effect of receipt
      • 24.3.1.4 PMA_CARRIER.indicate  ▶
        • 24.3.1.4.1 Semantics of the service primitive
        • 24.3.1.4.2 When generated
        • 24.3.1.4.3 Effect of receipt
      • 24.3.1.5 PMA_LINK.indicate  ▶
        • 24.3.1.5.1 Semantics of the service primitive
        • 24.3.1.5.2 When generated
        • 24.3.1.5.3 Effect of receipt
      • 24.3.1.6 PMA_LINK.request  ▶
        • 24.3.1.6.1 Semantics of the service primitive>
        • 24.3.1.6.2 When generated
        • 24.3.1.6.3 Effect of receipt
      • 24.3.1.7 PMA_RXERROR.indicate  ▶
        • 24.3.1.7.1 Semantics of the service primitive
        • 24.3.1.7.2 When generated
        • 24.3.1.7.3 Effect of receipt
    • 24.3.2 Functional requirements  ▶
      • 24.3.2.1 Far-End fault
      • 24.3.2.2 Comparison to previous 802.3 PMAs
    • 24.3.3 State variables  ▶
      • 24.3.3.1 Constants
      • 24.3.3.2 Variables
      • 24.3.3.3 Functions
      • 24.3.3.4 Timers
      • 24.3.3.5 Counters
      • 24.3.3.6 Messages
    • 24.3.4 Process specifications and state diagrams  ▶
      • 24.3.4.1 TX
      • 24.3.4.2 RX
      • 24.3.4.3 Carrier detect
      • 24.3.4.4 Link Monitor
      • 24.3.4.5 Far-End Fault Generate
      • 24.3.4.6 Far-End Fault Detect
  • 24.4 Physical Medium Dependent (PMD) sublayer service interface  ▶
    • 24.4.1 PMD service interface  ▶
      • 24.4.1.1 PMD_UNITDATA.request  ▶
        • 24.4.1.1.1 Semantics of the service primitive
        • 24.4.1.1.2 When generated
        • 24.4.1.1.3 Effect of receipt
      • 24.4.1.2 PMD_UNITDATA.indicate  ▶
        • 24.4.1.2.1 Semantics of the service primitive
        • 24.4.1.2.2 When generated
        • 24.4.1.2.3 Effect of receipt
      • 24.4.1.3 PMD_SIGNAL.indicate  ▶
        • 24.4.1.3.1 Semantics of the service primitive
        • 24.4.1.3.2 When generated
        • 24.4.1.3.3 Effect of receipt
    • 24.4.2 Medium Dependent Interface (MDI)
  • 24.5 Compatibility considerations
  • 24.6 Delay constraints  ▶
    • 24.6.1 PHY delay constraints (exposed MII)
    • 24.6.2 DTE delay constraints (unexposed MII)
    • 24.6.3 Carrier de-assertion/assertion constraint (half duplex mode only)
  • 24.7 Environmental specifications
  • 24.8 Protocol Implementation Conformance Statement (PICS) proforma for Clause 24, Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 100BASE-X  ▶
    • 24.8.1 Introduction
    • 24.8.2 Identification  ▶
      • 24.8.2.1 Implementation identification
      • 24.8.2.2 Protocol summary
      • 24.8.2.3 Major capabilities/options
    • 24.8.3 PICS proforma tables for the Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 100BASE-X  ▶
      • 24.8.3.1 General compatibility considerations
      • 24.8.3.2 PCS functions
      • 24.8.3.3 PMA functions
      • 24.8.3.4 Timing
• 25 Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-TX  ▶
  • 25.1 Overview
  • 25.2 Functional specifications
  • 25.3 General exceptions
  • 25.4 Specific requirements and exceptions  ▶
    • 25.4.1 Change to 7.2.3.1.1, “Line state patterns”
    • 25.4.2 Change to 7.2.3.3, “Loss of synchronization”
    • 25.4.3 Change to Table 8-1, “Contact assignments for unshielded twisted pair”
    • 25.4.4 Deletion of 8.3, “Station labelling”
    • 25.4.5 Change to 9.1.9, “Jitter”
    • 25.4.6 Replacement of 11.2, “Crossover function”
    • 25.4.7 Change to A.2, “DDJ test pattern for baseline wander measurements”
    • 25.4.8 Change to annex G, “Stream cipher scrambling function”
    • 25.4.9 Change to annex I, “Common mode cable termination”
  • 25.5 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-TX  ▶
    • 25.5.1 Introduction
    • 25.5.2 Identification  ▶
      • 25.5.2.1 Implementation identification
      • 25.5.2.2 Protocol summary
    • 25.5.3 Major capabilities/options
    • 25.5.4 PICS proforma tables for the Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-TX  ▶
      • 25.5.4.1 General compatibility considerations
      • 25.5.4.2 PMD compliance
• 26 Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-FX  ▶
  • 26.1 Overview
  • 26.2 Functional specifications
  • 26.3 General exceptions
  • 26.4 Specific requirements and exceptions  ▶
    • 26.4.1 Medium Dependent Interface (MDI)
    • 26.4.2 Crossover function
  • 26.5 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-FX  ▶
    • 26.5.1 Introduction
    • 26.5.2 Identification  ▶
      • 26.5.2.1 Implementation identification
    • 26.5.3 Protocol summary
    • 26.5.4 Major capabilities/options
    • 26.5.5 PICS proforma tables for Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-FX  ▶
      • 26.5.5.1 General compatibility considerations
      • 26.5.5.2 PMD compliance
• 27 Repeater for 100 Mb/s baseband networks  ▶
  • 27.1 Overview  ▶
    • 27.1.1 Scope  ▶
      • 27.1.1.1 Repeater set
      • 27.1.1.2 Repeater unit
      • 27.1.1.3 Repeater classes
    • 27.1.2 Application perspective  ▶
      • 27.1.2.1 Objectives
      • 27.1.2.2 Compatibility considerations  ▶
        • 27.1.2.2.1 Internal segment compatibility
    • 27.1.3 Relationship to PHY
  • 27.2 PMA interface messages
  • 27.3 Repeater functional specifications  ▶
    • 27.3.1 Repeater functions  ▶
      • 27.3.1.1 Signal restoration functional requirements  ▶
        • 27.3.1.1.1 Signal amplification
        • 27.3.1.1.2 Signal wave-shape restoration
        • 27.3.1.1.3 Signal retiming
      • 27.3.1.2 Data handling functional requirements  ▶
        • 27.3.1.2.1 Data frame forwarding
        • 27.3.1.2.2 Received code violations
      • 27.3.1.3 Received event handling functional requirements  ▶
        • 27.3.1.3.1 Received event handling
        • 27.3.1.3.2 Preamble regeneration
        • 27.3.1.3.3 Start-of-packet propagation delay
        • 27.3.1.3.4 Start-of-packet variability
      • 27.3.1.4 Collision handling functional requirements  ▶
        • 27.3.1.4.1 Collision detection
        • 27.3.1.4.2 Jam generation
        • 27.3.1.4.3 Collision-jam propagation delay
        • 27.3.1.4.4 Cessation-of-collision Jam propagation delay
      • 27.3.1.5 Error handling functional requirements  ▶
        • 27.3.1.5.1 100BASE-X and 100BASE-T2 carrier integrity functional requirements
        • 27.3.1.5.2 Speed handling
      • 27.3.1.6 Partition functional requirements
      • 27.3.1.7 Receive jabber functional requirements
    • 27.3.2 Detailed repeater functions and state diagrams  ▶
      • 27.3.2.1 State diagram variables  ▶
        • 27.3.2.1.1 Constants
        • 27.3.2.1.2 Variables
        • 27.3.2.1.3 Functions
        • 27.3.2.1.4 Timers
        • 27.3.2.1.5 Counters
        • 27.3.2.1.6 Port designation
      • 27.3.2.2 State diagrams
  • 27.4 Repeater electrical specifications  ▶
    • 27.4.1 Electrical isolation
  • 27.5 Environmental specifications  ▶
    • 27.5.1 General safety
    • 27.5.2 Network safety  ▶
      • 27.5.2.1 Installation
      • 27.5.2.2 Grounding
      • 27.5.2.3 Installation and maintenance guidelines
    • 27.5.3 Electrical isolation  ▶
      • 27.5.3.1 Environment A requirements
      • 27.5.3.2 Environment B requirements
    • 27.5.4 Reliability
    • 27.5.5 Environment  ▶
      • 27.5.5.1 Electromagnetic emission
      • 27.5.5.2 Temperature and humidity
  • 27.6 Repeater labeling
  • 27.7 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Repeater for 100 Mb/s baseband networks  ▶
    • 27.7.1 Introduction
    • 27.7.2 Identification  ▶
      • 27.7.2.1 Implementation identification
      • 27.7.2.2 Protocol summary
    • 27.7.3 Major capabilities/options
    • 27.7.4 PICS proforma tables for the repeater for 100 Mb/s baseband networks  ▶
      • 27.7.4.1 Compatibility considerations
      • 27.7.4.2 Repeater functions
      • 27.7.4.3 Signal Restoration function
      • 27.7.4.4 Data Handling function
      • 27.7.4.5 Receive Event Handling function
      • 27.7.4.6 Collision Handling function
      • 27.7.4.7 Error Handling function
      • 27.7.4.8 Partition functions
      • 27.7.4.9 Receive Jabber function
      • 27.7.4.10 Repeater state diagrams
      • 27.7.4.11 Repeater electrical
      • 27.7.4.12 Repeater labeling
• 28 Physical Layer link signaling for 10 Mb/s, 100 Mb/s, and 1000 Mb/s Auto-Negotiation on twisted pair  ▶
  • 28.1 Overview  ▶
    • 28.1.1 Scope
    • 28.1.2 Application perspective/objectives
    • 28.1.3 Relationship to ISO/IEC 8802-3
    • 28.1.4 Compatibility considerations  ▶
      • 28.1.4.1 Interoperability with existing 10BASE-T devices
      • 28.1.4.2 Interoperability with Auto-Negotiation compatible devices
      • 28.1.4.3 Cabling compatibility with Auto-Negotiation
  • 28.2 Functional specifications  ▶
    • 28.2.1 Transmit function requirements  ▶
      • 28.2.1.1 Link pulse transmission  ▶
        • 28.2.1.1.1 FLP burst encoding
        • 28.2.1.1.2 Transmit timing
      • 28.2.1.2 Link Code Word encoding  ▶
        • 28.2.1.2.1 Selector Field
        • 28.2.1.2.2 Technology Ability Field
        • 28.2.1.2.3 Remote Fault
        • 28.2.1.2.4 Acknowledge
        • 28.2.1.2.5 Next Page
      • 28.2.1.3 Transmit Switch function
    • 28.2.2 Receive function requirements  ▶
      • 28.2.2.1 FLP Burst ability detection and decoding
      • 28.2.2.2 NLP detection
      • 28.2.2.3 Receive Switch function
      • 28.2.2.4 Link Code Word matching
    • 28.2.3 Arbitration function requirements  ▶
      • 28.2.3.1 Parallel detection function
      • 28.2.3.2 Renegotiation function
      • 28.2.3.3 Priority Resolution function
      • 28.2.3.4 Next Page function  ▶
        • 28.2.3.4.1 Next Page encodings
        • 28.2.3.4.2 Next Page
        • 28.2.3.4.3 Acknowledge
        • 28.2.3.4.4 Message Page
        • 28.2.3.4.5 Acknowledge 2
        • 28.2.3.4.6 Toggle
        • 28.2.3.4.7 Message Page encoding
        • 28.2.3.4.8 Message Code Field
        • 28.2.3.4.9 Unformatted Page encoding
        • 28.2.3.4.10 Unformatted Code Field
        • 28.2.3.4.11 Use of Next Pages
        • 28.2.3.4.12 MII register requirements
      • 28.2.3.5 Remote fault sensing function
    • 28.2.4 Management function requirements  ▶
      • 28.2.4.1 Media Independent Interface  ▶
        • 28.2.4.1.1 MII control register
        • 28.2.4.1.2 MII status register
        • 28.2.4.1.3 Auto-Negotiation advertisement register (Register 4) (R/W)
        • 28.2.4.1.4 Auto-Negotiation link partner ability register (Register 5) (RO)
        • 28.2.4.1.5 Auto-Negotiation expansion register (Register 6) (RO)
        • 28.2.4.1.6 Auto-Negotiation Next Page transmit register (Register 7) (R/W)
        • 28.2.4.1.7 Auto-Negotiation Link Partner Ability register (Register 8) (RO)
        • 28.2.4.1.8 State diagram variable to MII register mapping
      • 28.2.4.2 Auto-Negotiation managed object class
    • 28.2.5 Absence of management function
    • 28.2.6 Technology-Dependent Interface  ▶
      • 28.2.6.1 PMA_LINK.indicate  ▶
        • 28.2.6.1.1 Semantics of the service primitive
        • 28.2.6.1.2 When generated
        • 28.2.6.1.3 Effect of receipt
      • 28.2.6.2 PMA_LINK.request  ▶
        • 28.2.6.2.1 Semantics of the service primitive
        • 28.2.6.2.2 When generated
        • 28.2.6.2.3 Effect of receipt.
      • 28.2.6.3 PMA_LINKPULSE.request  ▶
        • 28.2.6.3.1 Semantics of the service primitive
        • 28.2.6.3.2 When generated
        • 28.2.6.3.3 Effect of receipt
  • 28.3 State diagrams and variable definitions  ▶
    • 28.3.1 State diagram variables
    • 28.3.2 State diagram timers
    • 28.3.3 State diagram counters
    • 28.3.4 State diagrams
  • 28.4 Electrical specifications
  • 28.5 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Physical Layer link signaling for 10 Mb/s, 100 Mb/s, and 1000 Mb/s Auto-Negotiation on twisted pair  ▶
    • 28.5.1 Introduction
    • 28.5.2 Identification  ▶
      • 28.5.2.1 Implementation identification
      • 28.5.2.2 Protocol summary
    • 28.5.3 Major capabilities/options
    • 28.5.4 PICS proforma tables for Physical Layer link signaling for 10 Mb/s, 100 Mb/s, and 1000 Mb/s Auto-Negotiation on twisted pair  ▶
      • 28.5.4.1 Scope
      • 28.5.4.2 Auto-Negotiation functions
      • 28.5.4.3 Transmit function requirements
      • 28.5.4.4 Receive function requirements
      • 28.5.4.5 Arbitration functions
      • 28.5.4.6 Management function requirements
      • 28.5.4.7 Technology-dependent interface
      • 28.5.4.8 State diagrams
      • 28.5.4.9 Electrical characteristics
      • 28.5.4.10 Auto-Negotiation annexes
  • 28.6 Auto-Negotiation expansion
• 29 System considerations for multi segment 100BASE-T networks  ▶
  • 29.1 Overview  ▶
    • 29.1.1 Single collision domain multisegment networks
    • 29.1.2 Repeater usage
  • 29.2 Transmission System Model 1
  • 29.3 Transmission System Model 2  ▶
    • 29.3.1 Round-trip collision delay  ▶
      • 29.3.1.1 Worst-case path delay value (PDV) selection
      • 29.3.1.2 Worst-case PDV calculation
  • 29.4 Full duplex 100 Mb/s topology limitations
• 30 10 Mb/s, 100 Mb/s, 1000 Mb/s, MAC Control, and Link Aggregation Management  ▶
  • 30.1 Overview  ▶
    • 30.1.1 Scope
    • 30.1.2 Relationship to objects in IEEE 802.1F
    • 30.1.3 Systems management overview
    • 30.1.4 Management model
  • 30.2 Managed objects  ▶
    • 30.2.1 Introduction
    • 30.2.2 Overview of managed objects  ▶
      • 30.2.2.1 Text description of managed objects
      • 30.2.2.2 Functions to support management  ▶
        • 30.2.2.2.1 DTE MAC sublayer functions
        • 30.2.2.2.2 Repeater functions
    • 30.2.3 Containment
    • 30.2.4 Naming
    • 30.2.5 Capabilities
  • 30.3 Layer management for DTEs  ▶
    • 30.3.1 MAC entity managed object class  ▶
      • 30.3.1.1 MAC entity attributes  ▶
        • 30.3.1.1.1 aMACID
        • 30.3.1.1.2 aFramesTransmittedOK
        • 30.3.1.1.3 aSingleCollisionFrames
        • 30.3.1.1.4 aMultipleCollisionFrames
        • 30.3.1.1.5 aFramesReceivedOK
        • 30.3.1.1.6 aFrameCheckSequenceErrors
        • 30.3.1.1.7 aAlignmentErrors
        • 30.3.1.1.8 aOctetsTransmittedOK
        • 30.3.1.1.9 aFramesWithDeferredXmissions
        • 30.3.1.1.10 aLateCollisions
        • 30.3.1.1.11 aFramesAbortedDueToXSColls
        • 30.3.1.1.12 aFramesLostDueToIntMACXmitError
        • 30.3.1.1.13 aCarrierSenseErrors
        • 30.3.1.1.14 aOctetsReceivedOK
        • 30.3.1.1.15 aFramesLostDueToIntMACRcvError
        • 30.3.1.1.16 aPromiscuousStatus
        • 30.3.1.1.17 aReadMulticastAddressList
        • 30.3.1.1.18 aMulticastFramesXmittedOK
        • 30.3.1.1.19 aBroadcastFramesXmittedOK
        • 30.3.1.1.20 aFramesWithExcessiveDeferral
        • 30.3.1.1.21 aMulticastFramesReceivedOK
        • 30.3.1.1.22 aBroadcastFramesReceivedOK
        • 30.3.1.1.23 aInRangeLengthErrors
        • 30.3.1.1.24 aOutOfRangeLengthField
        • 30.3.1.1.25 aFrameTooLongErrors
        • 30.3.1.1.26 aMACEnableStatus
        • 30.3.1.1.27 aTransmitEnableStatus
        • 30.3.1.1.28 aMulticastReceiveStatus
        • 30.3.1.1.29 aReadWriteMACAddress
        • 30.3.1.1.30 aCollisionFrames
        • 30.3.1.1.31 aMACCapabilities
        • 30.3.1.1.32 aDuplexStatus
      • 30.3.1.2 MAC entity actions  ▶
        • 30.3.1.2.1 acInitializeMAC
        • 30.3.1.2.2 acAddGroupAddress
        • 30.3.1.2.3 acDeleteGroupAddress
        • 30.3.1.2.4 acExecuteSelfTest
    • 30.3.2 PHY devicePHY device managed object class  ▶
      • 30.3.2.1 PHY device attributes  ▶
        • 30.3.2.1.1 aPHYID
        • 30.3.2.1.2 aPhyType
        • 30.3.2.1.3 aPhyTypeList
        • 30.3.2.1.4 aSQETestErrors
        • 30.3.2.1.5 aSymbolErrorDuringCarrier
        • 30.3.2.1.6 aMIIDetect
        • 30.3.2.1.7 aPhyAdminState
      • 30.3.2.2 PHY device actions  ▶
        • 30.3.2.2.1 acPhyAdminControl
    • 30.3.3 MAC control entity object class  ▶
      • 30.3.3.1 aMACControlID
      • 30.3.3.2 aMACControlFunctionsSupported
      • 30.3.3.3 aMACControlFramesTransmitted
      • 30.3.3.4 aMACControlFramesReceived
      • 30.3.3.5 aUnsupportedOpcodesReceived
    • 30.3.4 PAUSE entity managed object class  ▶
      • 30.3.4.1 aPAUSELinkDelayAllowance
      • 30.3.4.2 aPAUSEMACCtrlFramesTransmitted
      • 30.3.4.3 aPAUSEMACCtrlFramesReceived
  • 30.4 Layer management for 10, 100, and 1000 Mb/s baseband repeaters  ▶
    • 30.4.1 Repeater managed object class  ▶
      • 30.4.1.1 Repeater attributes  ▶
        • 30.4.1.1.1 aRepeaterID
        • 30.4.1.1.2 aRepeaterType
        • 30.4.1.1.3 aRepeaterGroupCapacity
        • 30.4.1.1.4 aGroupMap
        • 30.4.1.1.5 aRepeaterHealthState
        • 30.4.1.1.6 aRepeaterHealthText
        • 30.4.1.1.7 aRepeaterHealthData
        • 30.4.1.1.8 aTransmitCollisions
      • 30.4.1.2 Repeater actions  ▶
        • 30.4.1.2.1 acResetRepeater
        • 30.4.1.2.2 acExecuteNonDisruptiveSelfTest
      • 30.4.1.3 Repeater notifications  ▶
        • 30.4.1.3.1 nRepeaterHealth
        • 30.4.1.3.2 RepeaterReset
        • 30.4.1.3.3 nGroupMapChange
    • 30.4.2 Group managed object class  ▶
      • 30.4.2.1 Group attributes  ▶
        • 30.4.2.1.1 aGroupID
        • 30.4.2.1.2 aGroupPortCapacity
        • 30.4.2.1.3 aPortMap
      • 30.4.2.2 Group notifications  ▶
        • 30.4.2.2.1 PortMapChange
    • 30.4.3 Repeater port managed object class  ▶
      • 30.4.3.1 Port attributes  ▶
        • 30.4.3.1.1 aPortID
        • 30.4.3.1.2 aPortAdminState
        • 30.4.3.1.3 aAutoPartitionState
        • 30.4.3.1.4 aReadableFrames
        • 30.4.3.1.5 aReadableOctets
        • 30.4.3.1.6 aFrameCheckSequenceErrors
        • 30.4.3.1.7 aAlignmentErrors
        • 30.4.3.1.8 aFramesTooLong
        • 30.4.3.1.9 aShortEvents
        • 30.4.3.1.10 aRunts
        • 30.4.3.1.11 aCollisions
        • 30.4.3.1.12 aLateEvents
        • 30.4.3.1.13 aVeryLongEvents
        • 30.4.3.1.14 aDataRateMismatches
        • 30.4.3.1.15 aAutoPartitions
        • 30.4.3.1.16 aIsolates
        • 30.4.3.1.17 aSymbolErrorDuringPacket
        • 30.4.3.1.18 aLastSourceAddress
        • 30.4.3.1.19 aSourceAddressChanges
        • 30.4.3.1.20 aBursts
      • 30.4.3.2 Port actions  ▶
        • 30.4.3.2.1 acPortAdminControl
  • 30.5 Layer management for 10, 100, and 1000 Mb/s medium attachment units (MAUs)  ▶
    • 30.5.1 MAU managed object class  ▶
      • 30.5.1.1 MAU attributes  ▶
        • 30.5.1.1.1 aMAUID
        • 30.5.1.1.2 aMAUType
        • 30.5.1.1.3 aMAUTypeList
        • 30.5.1.1.4 aMediaAvailable
        • 30.5.1.1.5 aLoseMediaCounter
        • 30.5.1.1.6 aJabber
        • 30.5.1.1.7 aMAUAdminState
        • 30.5.1.1.8 aBbMAUXmitRcvSplitType
        • 30.5.1.1.9 aBroadbandFrequencies
        • 30.5.1.1.10 aFalseCarriers
        • 30.5.1.1.11 aIdleErrorCount
      • 30.5.1.2 MAU actions  ▶
        • 30.5.1.2.1 acResetMAU
        • 30.5.1.2.2 acMAUAdminControl
      • 30.5.1.3 MAU notifications  ▶
        • 30.5.1.3.1 nJabber
  • 30.6 Management for link Auto-Negotiation  ▶
    • 30.6.1 Auto-Negotiation managed object class  ▶
      • 30.6.1.1 Auto-Negotiation attributes  ▶
        • 30.6.1.1.1 aAutoNegID
        • 30.6.1.1.2 aAutoNegAdminState
        • 30.6.1.1.3 aAutoNegRemoteSignaling
        • 30.6.1.1.4 aAutoNegAutoConfig
        • 30.6.1.1.5 aAutoNegLocalTechnologyAbility
        • 30.6.1.1.6 aAutoNegAdvertisedTechnologyAbility
        • 30.6.1.1.7 aAutoNegReceivedTechnologyAbility
        • 30.6.1.1.8 aAutoNegLocalSelectorAbility
        • 30.6.1.1.9 aAutoNegAdvertisedSelectorAbility
        • 30.6.1.1.10 aAutoNegReceivedSelectorAbility
      • 30.6.1.2 Auto-Negotiation actions  ▶
        • 30.6.1.2.1 acAutoNegRestartAutoConfig
        • 30.6.1.2.2 acAutoNegAdminControl
  • 30.7 Management for Link Aggregation  ▶
    • 30.7.1 Aggregator managed object class  ▶
      • 30.7.1.1 Aggregator attributes  ▶
        • 30.7.1.1.1 aAggID
        • 30.7.1.1.2 aAggDescription
        • 30.7.1.1.3 aAggPortDebugPartnerChangeCount
        • 30.7.1.1.4 aAggActorSystemID
        • 30.7.1.1.5 aAggActorSystemPriority
        • 30.7.1.1.6 aAggAggregateOrIndividual
        • 30.7.1.1.7 aAggActorAdminKey
        • 30.7.1.1.8 aAggActorOperKey
        • 30.7.1.1.9 aAggMACAddress
        • 30.7.1.1.10 aAggPartnerSystemID
        • 30.7.1.1.11 aAggPartnerSystemPriority
        • 30.7.1.1.12 aAggPartnerOperKey
        • 30.7.1.1.13 aAggAdminState
        • 30.7.1.1.14 aAggOperState
        • 30.7.1.1.15 aAggTimeOfLastOperChange
        • 30.7.1.1.16 aAggDataRate
        • 30.7.1.1.17 aAggOctetsTxOK
        • 30.7.1.1.18 aAggOctetsRxOK
        • 30.7.1.1.19 aAggFramesTxOK
        • 30.7.1.1.20 aAggFramesRxOK
        • 30.7.1.1.21 aAggMulticastFramesTxOK
        • 30.7.1.1.22 aAggMulticastFramesRxOK
        • 30.7.1.1.23 aAggBroadcastFramesTxOK
        • 30.7.1.1.24 aAggBroadcastFramesRxOK
        • 30.7.1.1.25 aAggFramesDiscardedOnTx
        • 30.7.1.1.26 aAggFramesDiscardedOnRx
        • 30.7.1.1.27 aAggFramesWithTxErrors
        • 30.7.1.1.28 aAggFramesWithRxErrors
        • 30.7.1.1.29 aAggUnknownProtocolFrames
        • 30.7.1.1.30 aAggPortList
        • 30.7.1.1.31 aAggLinkUpDownNotificationEnable
        • 30.7.1.1.32 aAggCollectorMaxDelay
      • 30.7.1.2 Aggregator Notifications  ▶
        • 30.7.1.2.1 nAggLinkUpNotification
        • 30.7.1.2.2 nAggLinkDownNotification
    • 30.7.2 Aggregation Port managed object class  ▶
      • 30.7.2.1 Aggregation Port Attributes  ▶
        • 30.7.2.1.1 aAggPortID
        • 30.7.2.1.2 aAggPortActorSystemPriority
        • 30.7.2.1.3 aAggPortActorSystemID
        • 30.7.2.1.4 aAggPortActorAdminKey
        • 30.7.2.1.5 aAggPortActorOperKey
        • 30.7.2.1.6 aAgg-PortPartnerAdminSystemPriority
        • 30.7.2.1.7 aAggPortPartnerOperSystemPriority
        • 30.7.2.1.8 aAggPortPartnerAdminSystemID
        • 30.7.2.1.9 aAggPortPartnerOperSystemID
        • 30.7.2.1.10 aAggPortPartnerAdminKey
        • 30.7.2.1.11 aAggPortPartnerOperKey
        • 30.7.2.1.12 aAggPortSelectedAggID
        • 30.7.2.1.13 aAggPortAttachedAggID
        • 30.7.2.1.14 aAggPortActorPort
        • 30.7.2.1.15 aAggPortActorPortPriority
        • 30.7.2.1.16 aAggPortPartnerAdminPort
        • 30.7.2.1.17 aAggPortPartnerOperPort
        • 30.7.2.1.18 aAggPortPartnerAdminPortPriority
        • 30.7.2.1.19 aAggPortPartnerOperPortPriority
        • 30.7.2.1.20 aAggPortActorAdminState
        • 30.7.2.1.21 aAggPortActorOperState
        • 30.7.2.1.22 aAggPortPartnerAdminState
        • 30.7.2.1.23 aAggPortPartnerOperState
        • 30.7.2.1.24 aAggPortAggregateOrIndividual
    • 30.7.3 Aggregation Port Statistics managed object class  ▶
      • 30.7.3.1 Aggregation Port Statistics attributes  ▶
        • 30.7.3.1.1 aAggPortStatsID
        • 30.7.3.1.2 aAggPortStatsLACPDUsRx
        • 30.7.3.1.3 aAggPortStatsMarkerPDUsRx
        • 30.7.3.1.4 aAggPortStatsMarkerResponsePDUsRx
        • 30.7.3.1.5 aAggPortStatsUnknownRx
        • 30.7.3.1.6 aAggPortStatsIllegalRx
        • 30.7.3.1.7 aAggPortStatsLACPDUsTx
        • 30.7.3.1.8 aAggPortStatsMarkerPDUsTx
        • 30.7.3.1.9 aAggPortStatsMarkerResponsePDUsTx
    • 30.7.4 Aggregation Port Debug Information managed object class  ▶
      • 30.7.4.1 Aggregation Port Debug Information attributes  ▶
        • 30.7.4.1.1 aAggPortDebugInformationID
        • 30.7.4.1.2 aAggPortDebugRxState
        • 30.7.4.1.3 aAggPortDebugLastRxTime
        • 30.7.4.1.4 aAggPortDebugMuxState
        • 30.7.4.1.5 aAggPortDebugMuxReason
        • 30.7.4.1.6 aAggPortDebugActorChurnState
        • 30.7.4.1.7 aAggPortDebugPartnerChurnState
        • 30.7.4.1.8 aAggPortDebugActorChurnCount
        • 30.7.4.1.9 aAggPortDebugPartnerChurnCount
        • 30.7.4.1.10 aAggPortDebugActorSyncTransitionCount
        • 30.7.4.1.11 aAggPortDebugPartnerSyncTransitionCount
        • 30.7.4.1.12 aAggPortDebugActorChangeCount
        • 30.7.4.1.13 aAggPortDebugPartnerChangeCount
• 31 MAC Control  ▶
  • 31.1 Overview
  • 31.2 Layer architecture
  • 31.3 Support by interlayer interfaces
  • 31.4 MAC Control frames  ▶
    • 31.4.1 MAC Control frame format  ▶
      • 31.4.1.1 Destination Address field
      • 31.4.1.2 Source Address field
      • 31.4.1.3 Length/Type field
      • 31.4.1.4 MAC Control Opcode field
      • 31.4.1.5 MAC Control Parameters field
      • 31.4.1.6 Reserved field
  • 31.5 Opcode-independent MAC Control sublayer operation  ▶
    • 31.5.1 Frame parsing and data frame reception
    • 31.5.2 Control frame reception
    • 31.5.3 Opcode-independent MAC Control receive state diagram  ▶
      • 31.5.3.1 Constants
      • 31.5.3.2 Variables
      • 31.5.3.3 Functions
      • 31.5.3.4 Messages
      • 31.5.3.5 Opcode-independent MAC Control Receive state diagram
  • 31.6 Compatibility requirements
  • 31.7 MAC Control client behavior
  • 31.8 Protocol Implementation Conformance Statement (PICS) proforma for Clause 31, MAC Control  ▶
    • 31.8.1 Introduction
    • 31.8.2 Identification  ▶
      • 31.8.2.1 Implementation identification
      • 31.8.2.2 Protocol summary
    • 31.8.3 PICS proforma for MAC Control frames  ▶
      • 31.8.3.1 Support by interlayer interfaces
      • 31.8.3.2 MAC Control frame format
      • 31.8.3.3 Opcode-independent MAC Control sublayer operation
      • 31.8.3.4 Control opcode assignments
• 32 Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 100BASE-T2  ▶
  • 32.1 Overview  ▶
    • 32.1.1 Relation of 100BASE-T2 to other standards
    • 32.1.2 Operation of 100BASE-T2  ▶
      • 32.1.2.1 Physical coding sublayer (PCS)
      • 32.1.2.2 PMA sublayer
      • 32.1.2.3 PHY Control function
    • 32.1.3 Application of 100BASE-T2  ▶
      • 32.1.3.1 Compatibility considerations
      • 32.1.3.2 Incorporating the 100BASE-T2 PHY into a DTE
      • 32.1.3.3 Use of 100BASE-T2 PHY for point-to-point communication
      • 32.1.3.4 Auto-Negotiation requirement
    • 32.1.4 State diagram conventions
  • 32.2 PHY Control functional specifications and service interface  ▶
    • 32.2.1 PHY Control function
    • 32.2.2 PHY Control Service interface  ▶
      • 32.2.2.1 PHYC_CONFIG.indicate  ▶
        • 32.2.2.1.1 Semantics of the primitive
        • 32.2.2.1.2 When generated
        • 32.2.2.1.3 Effect of receipt
      • 32.2.2.2 PHYC_TXMODE.indicate  ▶
        • 32.2.2.2.1 Semantics of the primitive
        • 32.2.2.2.2 When generated
        • 32.2.2.2.3 Effect of receipt
      • 32.2.2.3 PHYC_RXSTATUS.request  ▶
        • 32.2.2.3.1 Semantics of the primitive
        • 32.2.2.3.2 When generated
        • 32.2.2.3.3 Effect of receipt
      • 32.2.2.4 PHYC_REMRXSTATUS.request  ▶
        • 32.2.2.4.1 Semantics of the primitive
        • 32.2.2.4.2 When generated
        • 32.2.2.4.3 Effect of receipt
    • 32.2.3 State diagram variables
    • 32.2.4 State diagram timers
    • 32.2.5 PHY Control state diagram
  • 32.3 PCS functional specifications  ▶
    • 32.3.1 PCS functions  ▶
      • 32.3.1.1 PCS Reset function
      • 32.3.1.2 PCS Transmit function  ▶
        • 32.3.1.2.1 Side-stream scrambler polynomials
        • 32.3.1.2.2 Generation of bits San[2:0] and Sbn[2:0]
        • 32.3.1.2.3 Generation of sequences An and Bn
      • 32.3.1.3 PCS Receive function  ▶
        • 32.3.1.3.1 Receiver descrambler polynomials
        • 32.3.1.3.2 Decoding of quinary symbols
      • 32.3.1.4 PCS Carrier Sense function
      • 32.3.1.5 PCS Collision Presence function
    • 32.3.2 PCS interfaces  ▶
      • 32.3.2.1 PCS-MII interface signals
      • 32.3.2.2 PCS-management entity signals
    • 32.3.3 Frame structure
    • 32.3.4 State variables  ▶
      • 32.3.4.1 Variables
      • 32.3.4.2 Timer
      • 32.3.4.3 Messages
    • 32.3.5 State diagrams  ▶
      • 32.3.5.1 PCS Transmit
      • 32.3.5.2 PCS Receive
      • 32.3.5.3 PCS Carrier Sense
    • 32.3.6 PCS electrical specifications
  • 32.4 PMA functional specifications and service interface  ▶
    • 32.4.1 PMA functional specifications  ▶
      • 32.4.1.1 PMA functions  ▶
        • 32.4.1.1.1 PMA Reset function
        • 32.4.1.1.2 PMA Transmit function
        • 32.4.1.1.3 PMA Receive function
        • 32.4.1.1.4 Link Monitor function
        • 32.4.1.1.5 Clock Recovery function
      • 32.4.1.2 PMA interface messages  ▶
        • 32.4.1.2.1 MDI signals transmitted by the PHY
        • 32.4.1.2.2 Signals received at the MDI
      • 32.4.1.3 PMA state diagram  ▶
        • 32.4.1.3.1 State diagram variables
        • 32.4.1.3.2 Timers
        • 32.4.1.3.3 Link Monitor state diagram
    • 32.4.2 PMA service interface  ▶
      • 32.4.2.1 PMA_TYPE.indicate  ▶
        • 32.4.2.1.1 Semantics of the service primitive
        • 32.4.2.1.2 When generated
        • 32.4.2.1.3 Effect of receipt
      • 32.4.2.2 PMA_UNITDATA.request  ▶
        • 32.4.2.2.1 Semantics of the service primitive
        • 32.4.2.2.2 When generated
        • 32.4.2.2.3 Effect of receipt
      • 32.4.2.3 PMA_UNITDATA.indicate  ▶
        • 32.4.2.3.1 Semantics of the service primitive
        • 32.4.2.3.2 When generated
        • 32.4.2.3.3 Effect of receipt
      • 32.4.2.4 PMA_LINK.request  ▶
        • 32.4.2.4.1 Semantics of the service primitive
        • 32.4.2.4.2 When generated
        • 32.4.2.4.3 Effect of receipt
      • 32.4.2.5 PMA_LINK.indicate  ▶
        • 32.4.2.5.1 Semantics of the service primitive
        • 32.4.2.5.2 When generated
        • 32.4.2.5.3 Effect of receipt
      • 32.4.2.6 PMA_CARRIER.indicate
      • 32.4.2.7 PMA_RXERROR.indicate
      • 32.4.2.8 PMA_RXSTATUS.request
  • 32.5 Management functions  ▶
    • 32.5.1 100BASE-T2 Use of Auto-Negotiation and MII Registers 8, 9, and 10
    • 32.5.2 Management functions
    • 32.5.3 PHY specific registers for 100BASE-T2  ▶
      • 32.5.3.1 100BASE-T2 Control register (Register 9)  ▶
        • 32.5.3.1.1 Transmitter test mode
        • 32.5.3.1.2 Receive test mode
        • 32.5.3.1.3 MASTER-SLAVE Manual Configuration Enable
        • 32.5.3.1.4 MASTER-SLAVE Manual Configuration Value
        • 32.5.3.1.5 T2_Repeater/DTE Bit
        • 32.5.3.1.6 Reserved bits
      • 32.5.3.2 100BASE-T2 Status register (Register 10)  ▶
        • 32.5.3.2.1 MASTER-SLAVE Manual Configuration Fault
        • 32.5.3.2.2 MASTER-SLAVE Configuration Resolution Complete
        • 32.5.3.2.3 Local Receiver Status
        • 32.5.3.2.4 Remote Receiver Status
        • 32.5.3.2.5 Reserved bits
        • 32.5.3.2.6 Idle Error count
    • 32.5.4 Changes and additions to Auto-Negotiation (Clause 28)  ▶
      • 32.5.4.1 Change to 28.2.4.1.3 (Auto-Negotiation Advertisement register)
      • 32.5.4.2 Use of Auto-Negotiation Next Page codes for 100BASE-T2 PHYs
      • 32.5.4.3 MASTER-SLAVE Configuration Resolution
  • 32.6 PMA electrical specifications  ▶
    • 32.6.1 PMA-to-MDI interface characteristics  ▶
      • 32.6.1.1 Isolation requirement
      • 32.6.1.2 Transmitter electrical specifications  ▶
        • 32.6.1.2.1 Transmitter test modes
        • 32.6.1.2.2 Peak differential output voltage and level distortion
        • 32.6.1.2.3 Maximum output droop
        • 32.6.1.2.4 Differential output templates
        • 32.6.1.2.5 Transmitter timing jitter
        • 32.6.1.2.6 Transmit clock frequency
      • 32.6.1.3 Receiver electrical specifications  ▶
        • 32.6.1.3.1 Test channel
        • 32.6.1.3.2 Receiver test mode
        • 32.6.1.3.3 Receiver differential input signals
        • 32.6.1.3.4 Receiver Alien NEXT tolerance
        • 32.6.1.3.5 Receiver timing jitter
        • 32.6.1.3.6 Common-mode noise rejection
        • 32.6.1.3.7 Receiver frequency tolerance
      • 32.6.1.4 MDI Specifications  ▶
        • 32.6.1.4.1 MDI differential impedance
        • 32.6.1.4.2 MDI impedance balance
        • 32.6.1.4.3 MDI common-mode output voltage
        • 32.6.1.4.4 MDI fault tolerance
    • 32.6.2 Power consumption
  • 32.7 Link segment characteristics  ▶
    • 32.7.1 Cabling
    • 32.7.2 Link transmission parameters  ▶
      • 32.7.2.1 Insertion loss
      • 32.7.2.2 Differential characteristic impedance
      • 32.7.2.3 Coupling parameters  ▶
        • 32.7.2.3.1 Differential near-end crosstalk (NEXT) loss
        • 32.7.2.3.2 Multiple-disturber NEXT (MDNEXT) loss
        • 32.7.2.3.3 Equal level far-end crosstalk loss (ELFEXT)
        • 32.7.2.3.4 Multiple-disturber ELFEXT
        • 32.7.2.3.5 10BASE-T NEXT loss to insertion loss ratio requirement
      • 32.7.2.4 Delay  ▶
        • 32.7.2.4.1 Maximum link delay
        • 32.7.2.4.2 Difference in link delays
    • 32.7.3 Noise  ▶
      • 32.7.3.1 Near-end crosstalk noise
      • 32.7.3.2 Far-end crosstalk noise
      • 32.7.3.3 External coupled noise
    • 32.7.4 Installation practice  ▶
      • 32.7.4.1 Connector installation practices
      • 32.7.4.2 Restrictions on use of Category 3 cabling with more than four pairs
      • 32.7.4.3 Restrictions on use of Category 5 cabling with up to 25 pairs
  • 32.8 MDI specification  ▶
    • 32.8.1 MDI connectors
    • 32.8.2 Crossover function
  • 32.9 System considerations
  • 32.10 Environmental specifications  ▶
    • 32.10.1 General safety
    • 32.10.2 Network safety  ▶
      • 32.10.2.1 Installation
      • 32.10.2.2 Grounding
      • 32.10.2.3 Installation and maintenance guidelines
      • 32.10.2.4 Telephony voltages
    • 32.10.3 Environment  ▶
      • 32.10.3.1 Electromagnetic emission
      • 32.10.3.2 Temperature and humidity
    • 32.10.4 Cabling specifications
  • 32.11 PHY labeling
  • 32.12 Delay constraints  ▶
    • 32.12.1 PHY delay constraints (exposed MII)
    • 32.12.2 DTE delay constraints (unexposed MII)
  • 32.13 Protocol Implementation Conformance Statement (PICS) proforma for Clause 32, Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 100BASE-T2  ▶
    • 32.13.1 Identification  ▶
      • 32.13.1.1 Implementation identification
      • 32.13.1.2 Protocol summary
    • 32.13.2 Major capabilities/options
    • 32.13.3 Compatibility considerations
    • 32.13.4 PHY control function
    • 32.13.5 Physical Coding Sublayer (PCS) or Physical Medium Attachment (PMA) sublayer  ▶
      • 32.13.5.1 PCS transmit functions
      • 32.13.5.2 PCS receive functions
      • 32.13.5.3 Other PCS functions
      • 32.13.5.4 PMA functions
      • 32.13.5.5 PMA service interface
      • 32.13.5.6 Management functions
      • 32.13.5.7 100BASE-T2 specific Auto-Negotiation requirements
      • 32.13.5.8 PMA electrical specifications
      • 32.13.5.9 Characteristics of the link segment
      • 32.13.5.10 MDI requirements
      • 32.13.5.11 General safety and environmental requirements
      • 32.13.5.12 Timing requirements exposed MII
      • 32.13.5.13 Timing requirements unexposed MII
      • 32.13.5.14 Timing requirements: carrier assertion/deassertion constraint
• 33 Clause is reserved for future use.
• 34 Introduction to 1000 Mb/s baseband network  ▶
  • 34.1 Overview  ▶
    • 34.1.1 Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)
    • 34.1.2 Physical Layer signaling systems
    • 34.1.3 Repeater
    • 34.1.4 Auto-Negotiation, type 1000BASE-X
    • 34.1.5 Physical Layer line signaling for 10 Mb/s and 100 Mb/s Auto-Negotiation on twisted pair
    • 34.1.6 Management
  • 34.2 State diagrams
  • 34.3 Protocol Implementation Conformance Statement (PICS) proforma
  • 34.4 Relation of Gigabit Ethernet to other standards
• 35 Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)  ▶
  • 35.1 Overview  ▶
    • 35.1.1 Summary of major concepts
    • 35.1.2 Application
    • 35.1.3 Rate of operation
    • 35.1.4 Allocation of functions
  • 35.2 Functional specifications  ▶
    • 35.2.1 Mapping of GMII signals to PLS service primitives and Station Management  ▶
      • 35.2.1.1 Mapping of PLS_DATA.request  ▶
        • 35.2.1.1.1 Function
        • 35.2.1.1.2 Semantics of the service primitive
        • 35.2.1.1.3 When generated
      • 35.2.1.2 Mapping of PLS_DATA.indicate  ▶
        • 35.2.1.2.1 Function
        • 35.2.1.2.2 Semantics of the service primitive
        • 35.2.1.2.3 When generated
      • 35.2.1.3 Mapping of PLS_CARRIER.indicate  ▶
        • 35.2.1.3.1 Function
        • 35.2.1.3.2 Semantics of the service primitive
        • 35.2.1.3.3 When generated
      • 35.2.1.4 Mapping of PLS_SIGNAL.indicate  ▶
        • 35.2.1.4.1 Function
        • 35.2.1.4.2 Semantics of the service primitive
        • 35.2.1.4.3 When generated
      • 35.2.1.5 Response to error indications from GMII
      • 35.2.1.6 Conditions for generation of TX_ER
      • 35.2.1.7 Mapping of PLS_DATA_VALID.indicate  ▶
        • 35.2.1.7.1 Function
        • 35.2.1.7.2 Semantics of the service primitive
        • 35.2.1.7.3 When generated
    • 35.2.2 GMII signal functional specifications  ▶
      • 35.2.2.1 GTX_CLK (1000 Mb/s transmit clock)
      • 35.2.2.2 RX_CLK (receive clock)
      • 35.2.2.3 TX_EN (transmit enable)
      • 35.2.2.4 TXD (transmit data)
      • 35.2.2.5 TX_ER (transmit coding error)
      • 35.2.2.6 RX_DV (receive data valid)
      • 35.2.2.7 RXD (receive data)
      • 35.2.2.8 RX_ER (receive error)
      • 35.2.2.9 CRS (carrier sense)
      • 35.2.2.10 COL (collision detected)
      • 35.2.2.11 MDC (management data clock)
      • 35.2.2.12 MDIO (management data input/output)
    • 35.2.3 GMII data stream  ▶
      • 35.2.3.1 Inter-frame <inter-frame>
      • 35.2.3.2 Preamble <preamble> and start of frame delimiter <sfd>  ▶
        • 35.2.3.2.1 Transmit case
        • 35.2.3.2.2 Receive case
      • 35.2.3.3 Data <data>
      • 35.2.3.4 End-of-Frame delimiter <efd>
      • 35.2.3.5 Carrier extension <extend>
      • 35.2.3.6 Definition of Start of Packet and End of Packet Delimiters
    • 35.2.4 MAC delay constraints (with GMII)
    • 35.2.5 Management functions
  • 35.3 Signal mapping
  • 35.4 Electrical characteristics  ▶
    • 35.4.1 DC characteristics
    • 35.4.2 AC characteristics  ▶
      • 35.4.2.1 Signal Timing measurements
      • 35.4.2.2 GMII test circuit topology
      • 35.4.2.3 GMII ac specifications
  • 35.5 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)  ▶
    • 35.5.1 Introduction
    • 35.5.2 Identification  ▶
      • 35.5.2.1 Implementation identification
      • 35.5.2.2 Protocol summary
      • 35.5.2.3 Major capabilities/options
    • 35.5.3 PICS proforma tables for reconciliation sublayer and Gigabit Media Independent Interface  ▶
      • 35.5.3.1 Mapping of PLS service primitives
      • 35.5.3.2 GMII signal functional specifications
      • 35.5.3.3 Data stream structure
      • 35.5.3.4 Delay constraints
      • 35.5.3.5 Management functions
      • 35.5.3.6 Electrical characteristics
• 36 Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 1000BASE-X  ▶
  • 36.1 Overview  ▶
    • 36.1.1 Scope
    • 36.1.2 Objectives
    • 36.1.3 Relationship of 1000BASE-X to other standards
    • 36.1.4 Summary of 1000BASE-X sublayers  ▶
      • 36.1.4.1 Physical Coding Sublayer (PCS)
      • 36.1.4.2 Physical Medium Attachment (PMA) sublayer
      • 36.1.4.3 Physical Medium Dependent (PMD) sublayer
    • 36.1.5 Inter-sublayer interfaces
    • 36.1.6 Functional block diagram
    • 36.1.7 State diagram conventions
  • 36.2 Physical Coding Sublayer (PCS)  ▶
    • 36.2.1 PCS Interface (GMII)
    • 36.2.2 Functions within the PCS
    • 36.2.3 Use of code-groups
    • 36.2.4 8B/10B transmission code  ▶
      • 36.2.4.1 Notation conventions
      • 36.2.4.2 Transmission order
      • 36.2.4.3 Valid and invalid code-groups
      • 36.2.4.4 Running disparity rules
      • 36.2.4.5 Generating code-groups
      • 36.2.4.6 Checking the validity of received code-groups
      • 36.2.4.7 Ordered_sets  ▶
        • 36.2.4.7.1 Ordered_set rules
      • 36.2.4.8 /K28.5/ code-group considerations
      • 36.2.4.9 Comma considerations
      • 36.2.4.10 Configuration (/C/)
      • 36.2.4.11 Data (/D/)
      • 36.2.4.12 IDLE (/I/)
      • 36.2.4.13 Start_of_Packet (SPD) delimiter
      • 36.2.4.14 End_of_Packet delimiter (EPD)  ▶
        • 36.2.4.14.1 EPD rules
      • 36.2.4.15 Carrier_Extend (/R/)  ▶
        • 36.2.4.15.1 Carrier_Extend rules
      • 36.2.4.16 Error_Propagation (/V/)
      • 36.2.4.17 Encapsulation
      • 36.2.4.18 Mapping between GMII, PCS and PMA
    • 36.2.5 Detailed functions and state diagrams  ▶
      • 36.2.5.1 State variables  ▶
        • 36.2.5.1.1 Notation conventions
        • 36.2.5.1.2 Constants
        • 36.2.5.1.3 Variables
        • 36.2.5.1.4 Functions
        • 36.2.5.1.5 Counters
        • 36.2.5.1.6 Message
        • 36.2.5.1.7 Timer
      • 36.2.5.2 State diagrams  ▶
        • 36.2.5.2.1 Transmit
        • 36.2.5.2.2 Receive
        • 36.2.5.2.3 State variable function carrier_detect(x)
        • 36.2.5.2.4 Code-group stream decoding
        • 36.2.5.2.5 Carrier sense
        • 36.2.5.2.6 Synchronization
        • 36.2.5.2.7 Auto-Negotiation process
  • 36.3 Physical Medium Attachment (PMA)sublayer  ▶
    • 36.3.1 Service Interface  ▶
      • 36.3.1.1 PMA_UNITDATA.request  ▶
        • 36.3.1.1.1 Semantics of the service primitive
        • 36.3.1.1.2 When generated
        • 36.3.1.1.3 Effect of receipt
      • 36.3.1.2 PMA_UNITDATA.indicate  ▶
        • 36.3.1.2.1 Semantics of the service primitive
        • 36.3.1.2.2 When generated
        • 36.3.1.2.3 Effect of receipt
    • 36.3.2 Functions within the PMA  ▶
      • 36.3.2.1 Data delay
      • 36.3.2.2 PMA transmit function
      • 36.3.2.3 PMA receive function
      • 36.3.2.4 Code-group alignment
    • 36.3.3 A physical instantiation of the PMA Service Interface  ▶
      • 36.3.3.1 Required signals
      • 36.3.3.2 Summary of control signal usage
    • 36.3.4 General electrical characteristics of the TBI  ▶
      • 36.3.4.1 DC characteristics
      • 36.3.4.2 Valid signal levels
      • 36.3.4.3 Rise and fall time definition
      • 36.3.4.4 Output load
    • 36.3.5 TBI transmit interface electrical characteristics  ▶
      • 36.3.5.1 Transmit data (tx_code-group<9:0>)
      • 36.3.5.2 TBI transmit interface timing
    • 36.3.6 TBI receive interface electrical characteristics  ▶
      • 36.3.6.1 Receive data (rx_code-group<9:0>)
      • 36.3.6.2 Receive clock (PMA_RX_CLK<0>, PMA_RX_CLK<1>)
    • 36.3.7 Loopback mode  ▶
      • 36.3.7.1 Receiver considerations
      • 36.3.7.2 Transmitter considerations
    • 36.3.8 Test functions
  • 36.4 Compatibility considerations
  • 36.5 Delay constraints  ▶
    • 36.5.1 MDI to GMII delay constraints
    • 36.5.2 DTE delay constraints (half duplex mode)
    • 36.5.3 Carrier de-assertion/assertion constraint (half duplex mode)
  • 36.6 Environmental specifications
  • 36.7 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 1000BASE-X  ▶
    • 36.7.1 Introduction
    • 36.7.2 Identification  ▶
      • 36.7.2.1 Implementation identification
      • 36.7.2.2 Protocol summary
    • 36.7.3 Major Capabilities/Options
    • 36.7.4 PICS proforma tables for the PCS and PMA sublayer, type 1000BASE-X  ▶
      • 36.7.4.1 Compatibility considerations
      • 36.7.4.2 Code-group functions
      • 36.7.4.3 State diagrams
      • 36.7.4.4 PMA functions
      • 36.7.4.5 PMA transmit function
      • 36.7.4.6 PMA code-group alignment function
      • 36.7.4.7 TBI
      • 36.7.4.8 Delay constraints
• 37 Auto-Negotiation function, type 1000BASE-X  ▶
  • 37.1 Overview  ▶
    • 37.1.1 Scope
    • 37.1.2 Application perspective/objectives
    • 37.1.3 Relationship to ISO/IEC 8802-3
    • 37.1.4 Compatibility considerations  ▶
      • 37.1.4.1 Auto-Negotiation
      • 37.1.4.2 Management interface  ▶
        • 37.1.4.2.1 GMII management interface
      • 37.1.4.3 Interoperability between Auto-Negotiation compatible devices
      • 37.1.4.4 User Configuration with Auto-Negotiation
  • 37.2 Functional specifications  ▶
    • 37.2.1 Config_Reg encoding  ▶
      • 37.2.1.1 Base page to management register mapping
      • 37.2.1.2 Full duplex
      • 37.2.1.3 Half duplex
      • 37.2.1.4 Pause
      • 37.2.1.5 Remote fault  ▶
        • 37.2.1.5.1 No error, link OK
        • 37.2.1.5.2 Offline
        • 37.2.1.5.3 Link_Failure
        • 37.2.1.5.4 Auto-Negotiation_Error
      • 37.2.1.6 Acknowledge
      • 37.2.1.7 Next page
    • 37.2.2 Transmit function requirements  ▶
      • 37.2.2.1 Transmit function to Auto-Negotiation process interface requirements
    • 37.2.3 Receive function requirements  ▶
      • 37.2.3.1 Receive function to Auto-Negotiation process interface requirements
    • 37.2.4 Arbitration process requirements  ▶
      • 37.2.4.1 Renegotiation function
      • 37.2.4.2 Priority resolution function
      • 37.2.4.3 Next Page function  ▶
        • 37.2.4.3.1 Next page encodings
        • 37.2.4.3.2 Next page
        • 37.2.4.3.3 Acknowledge
        • 37.2.4.3.4 Message page
        • 37.2.4.3.5 Acknowledge 2
        • 37.2.4.3.6 Toggle
        • 37.2.4.3.7 Message page encoding
        • 37.2.4.3.8 Message Code Field
        • 37.2.4.3.9 Unformatted page encoding
        • 37.2.4.3.10 Unformatted Code Field
        • 37.2.4.3.11 Use of next pages
        • 37.2.4.3.12 Management register requirements
    • 37.2.5 Management function requirements  ▶
      • 37.2.5.1 Management registers  ▶
        • 37.2.5.1.1 Control register (Register 0)
        • 37.2.5.1.2 Status register (Register 1)
        • 37.2.5.1.3 AN advertisement register (Register 4) (R/W)
        • 37.2.5.1.4 AN link partner ability base page register (Register 5) (RO)
        • 37.2.5.1.5 AN expansion register (Register 6) (RO)
        • 37.2.5.1.6 AN next page transmit register (Register 7)
        • 37.2.5.1.7 AN link partner ability next page register (Register 8)
        • 37.2.5.1.8 Extended status register (Register 15)
        • 37.2.5.1.9 State diagram variable to management register mapping
      • 37.2.5.2 Auto-Negotiation managed object class
    • 37.2.6 Absence of management function
  • 37.3 Detailed functions and state diagrams  ▶
    • 37.3.1 State diagram variables  ▶
      • 37.3.1.1 Variables
      • 37.3.1.2 Functions
      • 37.3.1.3 Messages
      • 37.3.1.4 Timers
      • 37.3.1.5 State diagrams
  • 37.4 Environmental specifications
  • 37.5 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Auto-Negotiation function, type 1000BASE-X  ▶
    • 37.5.1 Introduction
    • 37.5.2 Identification  ▶
      • 37.5.2.1 Implementation identification
      • 37.5.2.2 Protocol summary
    • 37.5.3 Major Capabilities/Options
    • 37.5.4 PICS proforma tables for the Auto-Negotiation function, type 1000BASE-X  ▶
      • 37.5.4.1 Compatibility considerations
      • 37.5.4.2 Auto-Negotiation functions  ▶
        • 37.5.4.2.1 Config_Reg
        • 37.5.4.2.2 Remote Fault functions
        • 37.5.4.2.3 AN transmit functions
        • 37.5.4.2.4 AN receive functions
        • 37.5.4.2.5 Priority resolution functions
        • 37.5.4.2.6 Next page functions
        • 37.5.4.2.7 Management registers
• 38 Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE‐LX (Long Wavelength Laser) and 1000BASE‐SX (Short Wavelength Laser)  ▶
  • 38.1 Overview  ▶
    • 38.1.1 Physical Medium Dependent (PMD) sublayer service interface  ▶
      • 38.1.1.1 PMD_UNITDATA.request  ▶
        • 38.1.1.1.1 Semantics of the service primitive
        • 38.1.1.1.2 When generated
        • 38.1.1.1.3 Effect of receipt
      • 38.1.1.2 PMD_UNITDATA.indicate  ▶
        • 38.1.1.2.1 Semantics of the service primitive
        • 38.1.1.2.2 When generated
        • 38.1.1.2.3 Effect of receipt
      • 38.1.1.3 PMD_SIGNAL.indicate  ▶
        • 38.1.1.3.1 Semantics of the service primitive
        • 38.1.1.3.2 When generated
        • 38.1.1.3.3 Effect of receipt
    • 38.1.2 Medium Dependent Interface (MDI)
  • 38.2 PMD functional specifications  ▶
    • 38.2.1 PMD block diagram
    • 38.2.2 PMD transmit function
    • 38.2.3 PMD receive function
    • 38.2.4 PMD signal detect function
  • 38.3 PMD to MDI optical specifications for 1000BASE-SX  ▶
    • 38.3.1 Transmitter optical specifications
    • 38.3.2 Receive optical specifications
    • 38.3.3 Worst-case 1000BASE-SX link power budget and penalties (informative)
  • 38.4 PMD to MDI optical specifications for 1000BASE-LX  ▶
    • 38.4.1 Transmitter optical specifications
    • 38.4.2 Receive optical specifications
    • 38.4.3 Worst-case 1000BASE-LX link power budget and penalties (informative)
  • 38.5 Jitter specifications for 1000BASE-SX and 1000BASE-LX
  • 38.6 Optical measurement requirements  ▶
    • 38.6.1 Center wavelength and spectral width measurements
    • 38.6.2 Optical power measurements
    • 38.6.3 Extinction ratio measurements
    • 38.6.4 Relative Intensity Noise (RIN)
    • 38.6.5 Transmitter optical waveform (transmit eye)
    • 38.6.6 Transmit rise/fall characteristics
    • 38.6.7 Receive sensitivity measurements
    • 38.6.8 Total jitter measurements
    • 38.6.9 Deterministic jitter measurement (informative)
    • 38.6.10 Coupled Power Ratio (CPR) measurements
    • 38.6.11 Conformance test signal at TP3 for receiver testing
    • 38.6.12 Measurement of the receiver 3 dB electrical upper cutoff frequency
  • 38.7 Environmental specifications  ▶
    • 38.7.1 General safety
    • 38.7.2 Laser safety
    • 38.7.3 Installation
  • 38.8 Environment  ▶
    • 38.8.1 Electromagnetic emission
    • 38.8.2 Temperature, humidity, and handling
  • 38.9 PMD labeling requirements
  • 38.10 Fiber optic cabling model
  • 38.11 Characteristics of the fiber optic cabling  ▶
    • 38.11.1 Optical fiber and cable
    • 38.11.2 Optical fiber connection  ▶
      • 38.11.2.1 Connection insertion loss
      • 38.11.2.2 Connection return loss
    • 38.11.3 Medium Dependent Interface (MDI)
    • 38.11.4 single-mode fiber offset-launch mode-conditioning patch cord for MMF operation of 1000BASE-LX
  • 38.12 Protocol Implementation Conformance Statement (PICS) proforma for Clause , Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE-;LX (Long Wavelength Laser) and 1000BASE-;SX (Short Wavelength Laser)  ▶
    • 38.12.1 Introduction
    • 38.12.2 Identification  ▶
      • 38.12.2.1 Implementation identification
      • 38.12.2.2 Protocol summary
    • 38.12.3 Major capabilities/options
    • 38.12.4 PICS proforma tables for Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE-;LX (Long Wavelength Laser) and 1000BASE-;SX (Short Wavelength Laser)  ▶
      • 38.12.4.1 PMD functional specifications
      • 38.12.4.2 PMD to MDI optical specifications for 1000BASE-SX
      • 38.12.4.3 PMD to MDI optical specifications for 1000BASE-LX
      • 38.12.4.4 Jitter specifications
      • 38.12.4.5 Optical measurement requirements
      • 38.12.4.6 Characteristics of the fiber optic cabling
• 39 Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE-;CX (short-haul copper)  ▶
  • 39.1 Overview
  • 39.2 Functional specifications  ▶
    • 39.2.1 PMD transmit function
    • 39.2.2 PMD receive function
    • 39.2.3 PMD signal detect function
  • 39.3 PMD to MDI electrical specifications  ▶
    • 39.3.1 Transmitter electrical specifications
    • 39.3.2 Receiver electrical specifications
    • 39.3.3 Jitter specifications for 1000BASE-CX
  • 39.4 Jumper cable assembly characteristics  ▶
    • 39.4.1 Compensation networks
    • 39.4.2 Shielding
  • 39.5 MDI specification  ▶
    • 39.5.1 MDI connectors  ▶
      • 39.5.1.1 Style-1 connector specification
      • 39.5.1.2 Style-2 connector specification
      • 39.5.1.3 Style-2 connector example drawing (informative)
    • 39.5.2 Crossover function
  • 39.6 Electrical measurement requirements  ▶
    • 39.6.1 Transmit rise/fall time
    • 39.6.2 Transmit skew measurement
    • 39.6.3 Transmit eye (normalized and absolute)
    • 39.6.4 Through_connection impedance
    • 39.6.5 Jumper cable intra-pair differential skew
    • 39.6.6 Receiver link signal
    • 39.6.7 Near-End Cross Talk (NEXT)
    • 39.6.8 Differential time-domain reflectometry (TDR) measurement procedure  ▶
      • 39.6.8.1 Driving waveform
      • 39.6.8.2 Calibration of the test setup
  • 39.7 nvironmental specifications
  • 39.8 Protocol Implementation Conformance Statement (PICS) proforma for CLAUSE , Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE-CX  ▶
    • 39.8.1 Introduction
    • 39.8.2 Identification  ▶
      • 39.8.2.1 Implementation identification
      • 39.8.2.2 Protocol summary
    • 39.8.3 Major capabilities/options
    • 39.8.4 PICS proforma tables for Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE-CX (short-haul copper)  ▶
      • 39.8.4.1 PMD functional specifications
      • 39.8.4.2 PMD to MDI electrical specifications
      • 39.8.4.3 Jumper cable assembly characteristics
      • 39.8.4.4 Other requirements
• 40 Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 1000BASE-T  ▶
  • 40.1 Overview  ▶
    • 40.1.1 Objectives
    • 40.1.2 Relationship of 1000BASE-T to other standards
    • 40.1.3 Operation of 1000BASE-T  ▶
      • 40.1.3.1 Physical Coding Sublayer (PCS)
      • 40.1.3.2 Physical Medium Attachment (PMA) sublayer
    • 40.1.4 Signaling
    • 40.1.5 Inter-sublayer interfaces
    • 40.1.6 Conventions in this clause
  • 40.2 1000BASE-T Service Primitives and Interfaces  ▶
    • 40.2.1 Technology-Dependent Interface  ▶
      • 40.2.1.1 PMA_LINK.request  ▶
        • 40.2.1.1.1 Semantics of the primitive
        • 40.2.1.1.2 When generated
        • 40.2.1.1.3 Effect of receipt
      • 40.2.1.2 PMA_LINK.indicate  ▶
        • 40.2.1.2.1 Semantics of the primitive
        • 40.2.1.2.2 When generated
        • 40.2.1.2.3 Effect of receipt
    • 40.2.2 PMA Service Interface
    • 40.2.3 PMA_TXMODE.indicate  ▶
      • 40.2.3.1 Semantics of the primitive
      • 40.2.3.2 When generated
      • 40.2.3.3 Effect of receipt
    • 40.2.4 PMA_CONFIG.indicate  ▶
      • 40.2.4.1 Semantics of the primitive
      • 40.2.4.2 When generated
      • 40.2.4.3 Effect of receipt
    • 40.2.5 PMA_UNITDATA.request  ▶
      • 40.2.5.1 Semantics of the primitive
      • 40.2.5.2 When generated
      • 40.2.5.3 Effect of receipt
    • 40.2.6 PMA_UNITDATA.indicate  ▶
      • 40.2.6.1 Semantics of the primitive
      • 40.2.6.2 When generated
      • 40.2.6.3 Effect of receipt
    • 40.2.7 PMA_SCRSTATUS.request  ▶
      • 40.2.7.1 Semantics of the primitive
      • 40.2.7.2 When generated
      • 40.2.7.3 Effect of receipt
    • 40.2.8 PMA_RXSTATUS.indicate  ▶
      • 40.2.8.1 Semantics of the primitive
      • 40.2.8.2 When generated
      • 40.2.8.3 Effect of receipt
    • 40.2.9 PMA_REMRXSTATUS.request  ▶
      • 40.2.9.1 Semantics of the primitive
      • 40.2.9.2 When generated
      • 40.2.9.3 Effect of receipt
    • 40.2.10 PMA_RESET.indicate  ▶
      • 40.2.10.1 When generated
      • 40.2.10.2 Effect of receipt
  • 40.3 Physical Coding Sublayer (PCS)  ▶
    • 40.3.1 PCS functions  ▶
      • 40.3.1.1 PCS Reset function
      • 40.3.1.2 PCS Data Transmission Enable
      • 40.3.1.3 PCS Transmit function  ▶
        • 40.3.1.3.1 Side-stream scrambler polynomials
        • 40.3.1.3.2 Generation of bits Sxn[3:0], Syn[3:0], and Sgn[3:0]
        • 40.3.1.3.3 Generation of bits Scn[7:0]
        • 40.3.1.3.4 Generation of bits Sdn[8:0]
        • 40.3.1.3.5 Generation of quinary symbols TAn, TBn, TCn, TDn
        • 40.3.1.3.6 Generation of An, Bn, Cn, Dn
      • 40.3.1.4 PCS Receive function  ▶
        • 40.3.1.4.1 Decoding of code-groups
        • 40.3.1.4.2 Receiver descrambler polynomials
      • 40.3.1.5 PCS Carrier Sense function
    • 40.3.2 Stream structure
    • 40.3.3 State variables  ▶
      • 40.3.3.1 Variables
      • 40.3.3.2 Functions
      • 40.3.3.3 Timer
      • 40.3.3.4 Messages
    • 40.3.4 State diagrams  ▶
      • 40.3.4.1 Supplement to state diagram
  • 40.4 Physical Medium Attachment (PMA) sublayer  ▶
    • 40.4.1 PMA functional specifications
    • 40.4.2 PMA functions  ▶
      • 40.4.2.1 PMA Reset function
      • 40.4.2.2 PMA Transmit function
      • 40.4.2.3 PMA Receive function
      • 40.4.2.4 PHY Control function
      • 40.4.2.5 Link Monitor function
      • 40.4.2.6 Clock Recovery function
    • 40.4.3 MDI  ▶
      • 40.4.3.1 MDI signals transmitted by the PHY
      • 40.4.3.2 Signals received at the MDI
    • 40.4.4 Automatic MDI/MDI-X Configuration  ▶
      • 40.4.4.1 Description of Automatic MDI/MDI-X state machine
      • 40.4.4.2 Pseudo-random sequence generator
    • 40.4.5 State variables  ▶
      • 40.4.5.1 State diagram variables
      • 40.4.5.2 Timers
    • 40.4.6 State Diagrams  ▶
      • 40.4.6.1 PHY Control state diagram
      • 40.4.6.2 Link Monitor state diagram  ▶
        • 40.4.6.2.1 Auto Crossover state diagram
  • 40.5 Management interface  ▶
    • 40.5.1 Support for Auto-Negotiation  ▶
      • 40.5.1.1 1000BASE-T use of registers during Auto-Negotiation
      • 40.5.1.2 1000BASE-T Auto-Negotiation page use
      • 40.5.1.3 Sending Next Pages
    • 40.5.2 MASTER-SLAVE configuration resolution
  • 40.6 PMA electrical specifications  ▶
    • 40.6.1 PMA-to-MDI interface tests  ▶
      • 40.6.1.1 Isolation requirement  ▶
        • 40.6.1.1.1 Test channel
        • 40.6.1.1.2 Test modes
        • 40.6.1.1.3 Test Fixtures
      • 40.6.1.2 Transmitter electrical specifications  ▶
        • 40.6.1.2.1 Peak differential output voltage and level accuracy
        • 40.6.1.2.2 Maximum output droop
        • 40.6.1.2.3 Differential output templates
        • 40.6.1.2.4 Transmitter distortion
        • 40.6.1.2.5 Transmitter timing jitter
        • 40.6.1.2.6 Transmit clock frequency
      • 40.6.1.3 Receiver electrical specifications  ▶
        • 40.6.1.3.1 Receiver differential input signals
        • 40.6.1.3.2 Receiver frequency tolerance
        • 40.6.1.3.3 Common-mode noise rejection
        • 40.6.1.3.4 Alien Crosstalk noise rejection
  • 40.7 Link segment characteristics  ▶
    • 40.7.1 Cabling system characteristics
    • 40.7.2 Link transmission parameters  ▶
      • 40.7.2.1 Insertion loss
      • 40.7.2.2 Differential characteristic impedance
      • 40.7.2.3 Return loss
    • 40.7.3 Coupling parameters  ▶
      • 40.7.3.1 Near-End Crosstalk (NEXT)  ▶
        • 40.7.3.1.1 Differential Near-End Crosstalk
      • 40.7.3.2 Far-End Crosstalk (FEXT)  ▶
        • 40.7.3.2.1 Equal Level Far-End Crosstalk (ELFEXT) loss
        • 40.7.3.2.2 Multiple Disturber Equal Level Far-End Crosstalk (MDELFEXT) loss
        • 40.7.3.2.3 Multiple-Disturber Power Sum Equal Level Far-End Crosstalk (PSELFEXT) loss
    • 40.7.4 Delay  ▶
      • 40.7.4.1 Maximum link delay
      • 40.7.4.2 Link delay skew
    • 40.7.5 Noise environment
    • 40.7.6 External coupled noise
  • 40.8 MDI specification  ▶
    • 40.8.1 MDI connectors
    • 40.8.2 Crossover function
    • 40.8.3 MDI electrical specifications  ▶
      • 40.8.3.1 MDI return loss
      • 40.8.3.2 MDI impedance balance
      • 40.8.3.3 MDI common-mode output voltage
      • 40.8.3.4 MDI fault tolerance
  • 40.9 Environmental specifications  ▶
    • 40.9.1 General safety
    • 40.9.2 Network safety  ▶
      • 40.9.2.1 Installation
      • 40.9.2.2 Installation and maintenance guidelines
      • 40.9.2.3 Telephony voltages
    • 40.9.3 Environment  ▶
      • 40.9.3.1 Electromagnetic emission
      • 40.9.3.2 Temperature and humidity
  • 40.10 PHY labeling
  • 40.11 Delay constraints  ▶
    • 40.11.1 MDI to GMII delay constraints
    • 40.11.2 DTE delay constraints (half duplex only)
    • 40.11.3 Carrier de-assertion/assertion constraint (half duplex mode)
  • 40.12 Protocol implementation conformance statement (PICS) proforma for Clause 40—Physical coding sublayer (PCS), physical medium attachment (PMA) sublayer and baseband medium, type 1000BASE-T  ▶
    • 40.12.1 Identification  ▶
      • 40.12.1.1 Implementation identification
      • 40.12.1.2 Protocol summary
    • 40.12.2 Major capabilities/options
    • 40.12.3 Clause conventions
    • 40.12.4 Physical Coding Sublayer (PCS)  ▶
      • 40.12.4.1 PCS receive functions
      • 40.12.4.2 Other PCS functions
    • 40.12.5 Physical Medium Attachment (PMA)
    • 40.12.6 Management interface  ▶
      • 40.12.6.1 1000BASE-T Specific Auto-Negotiation Requirements
    • 40.12.7 PMA Electrical Specifications
    • 40.12.8 Characteristics of the link segment
    • 40.12.9 MDI requirements
    • 40.12.10 General safety and environmental requirements
    • 40.12.11 Timing requirements
• 41 Repeater for 1000 Mb/s baseband networks  ▶
  • 41.1 Overview  ▶
    • 41.1.1 Scope  ▶
      • 41.1.1.1 Repeater set
      • 41.1.1.2 Repeater unit
    • 41.1.2 Application perspective  ▶
      • 41.1.2.1 Objectives
      • 41.1.2.2 Compatibility considerations  ▶
        • 41.1.2.2.1 Internal segment compatibility
    • 41.1.3 Relationship to PHY
  • 41.2 Repeater functional specifications  ▶
    • 41.2.1 Repeater functions  ▶
      • 41.2.1.1 Signal restoration functional requirements  ▶
        • 41.2.1.1.1 Signal amplification
        • 41.2.1.1.2 Signal wave-shape restoration
        • 41.2.1.1.3 Signal retiming
      • 41.2.1.2 Data-handling functional requirements  ▶
        • 41.2.1.2.1 Data frame forwarding
        • 41.2.1.2.2 Received code violations
      • 41.2.1.3 Received event-handling functional requirements  ▶
        • 41.2.1.3.1 Received event handling
        • 41.2.1.3.2 Preamble regeneration
        • 41.2.1.3.3 Start-of-packet propagation delay
        • 41.2.1.3.4 Start-of-packet variability
      • 41.2.1.4 Collision-handling functional requirements  ▶
        • 41.2.1.4.1 Collision detection
        • 41.2.1.4.2 Jam generation
        • 41.2.1.4.3 Start-of-collision-jam propagation delay
        • 41.2.1.4.4 Cessation-of-collision Jam propagation delay
      • 41.2.1.5 Error-handling functional requirements  ▶
        • 41.2.1.5.1 Carrier integrity functional requirements
        • 41.2.1.5.2 Speed handling
      • 41.2.1.6 Partition functional requirements
      • 41.2.1.7 Receive jabber functional requirements
    • 41.2.2 Detailed repeater functions and state diagrams  ▶
      • 41.2.2.1 State diagram variables  ▶
        • 41.2.2.1.1 Constants
        • 41.2.2.1.2 Variables
        • 41.2.2.1.3 Functions
        • 41.2.2.1.4 Timers
        • 41.2.2.1.5 Counters
        • 41.2.2.1.6 Port designation
      • 41.2.2.2 State diagrams
  • 41.3 Repeater electrical specifications  ▶
    • 41.3.1 Electrical isolation
  • 41.4 Environmental specifications  ▶
    • 41.4.1 General safety
    • 41.4.2 Network safety  ▶
      • 41.4.2.1 Installation
      • 41.4.2.2 Grounding
      • 41.4.2.3 Installation and maintenance guidelines
    • 41.4.3 Electrical isolation  ▶
      • 41.4.3.1 Environment A requirements
      • 41.4.3.2 Environment B requirements
    • 41.4.4 Reliability
    • 41.4.5 Environment  ▶
      • 41.4.5.1 Electromagnetic emission
      • 41.4.5.2 Temperature and humidity
  • 41.5 Repeater labeling
  • 41.6 Protocol Implementation Conformance Statement (PICS) proforma for , Repeater for 1000 Mb/s baseband networks  ▶
    • 41.6.1 Introduction
    • 41.6.2 Identification  ▶
      • 41.6.2.1 Implementation identification
      • 41.6.2.2 Protocol summary
    • 41.6.3 Major capabilities/options
    • 41.6.4 PICS proforma tables for the Repeater for 1000 Mb/s baseband networks  ▶
      • 41.6.4.1 Compatibility considerations
      • 41.6.4.2 Repeater functions
      • 41.6.4.3 Signal restoration function
      • 41.6.4.4 Data-Handling function
      • 41.6.4.5 Receive Event-Handling function
      • 41.6.4.6 Collision-Handling function
      • 41.6.4.7 Error-Handling function
      • 41.6.4.8 Partition function
      • 41.6.4.9 Receive Jabber function
      • 41.6.4.10 Repeater state diagrams
      • 41.6.4.11 Repeater electrical
      • 41.6.4.12 Repeater labeling
• 42 System considerations for multisegment 1000 Mb/s networks  ▶
  • 42.1 Overview  ▶
    • 42.1.1 Single collision domain multisegment networks
    • 42.1.2 Repeater usage
  • 42.2 Transmission System Model 1
  • 42.3 Transmission System Model 2  ▶
    • 42.3.1 Round-trip collision delay  ▶
      • 42.3.1.1 Worst-case path delay value (PDV) selection
      • 42.3.1.2 Worst-case PDV calculation
  • 42.4 Full duplex 1000 Mb/s topology limitations
• 43 Link Aggregation  ▶
  • 43.1 Overview  ▶
    • 43.1.1 Terminology
    • 43.1.2 Goals and objectives
    • 43.1.3 Positioning of Link Aggregation within the IEEE 802.3 architecture
    • 43.1.4 State diagram conventions
  • 43.2 Link Aggregation operation  ▶
    • 43.2.1 Principles of Link Aggregation
    • 43.2.2 Service interfaces
    • 43.2.3 Frame Collector  ▶
      • 43.2.3.1 Frame Collector state diagram  ▶
        • 43.2.3.1.1 Constants
        • 43.2.3.1.2 Variables
        • 43.2.3.1.3 Messages
        • 43.2.3.1.4 State diagram
    • 43.2.4 Frame Distributor  ▶
      • 43.2.4.1 Frame Distributor state diagram  ▶
        • 43.2.4.1.1 Variables
        • 43.2.4.1.2 Messages
        • 43.2.4.1.3 State diagram
    • 43.2.5 Marker Generator/Receiver (optional)
    • 43.2.6 Marker Responder
    • 43.2.7 Aggregator Parser/Multiplexer  ▶
      • 43.2.7.1 Aggregator Parser state diagram  ▶
        • 43.2.7.1.1 Constants
        • 43.2.7.1.2 Variables
        • 43.2.7.1.3 Messages
    • 43.2.8 Aggregator  ▶
      • 43.2.8.1 State diagram
    • 43.2.9 Control Parser/Multiplexer  ▶
      • 43.2.9.1 Control Parser state diagram  ▶
        • 43.2.9.1.1 Constants
        • 43.2.9.1.2 Variables
        • 43.2.9.1.3 Messages
        • 43.2.9.1.4 State diagram
    • 43.2.10 Addressing
  • 43.3 Link Aggregation Control  ▶
    • 43.3.1 Characteristics of Link Aggregation Control
    • 43.3.2 System identification
    • 43.3.3 Aggregator identification
    • 43.3.4 Port identification
    • 43.3.5 Capability identification
    • 43.3.6 Link Aggregation Group identification  ▶
      • 43.3.6.1 Construction of the Link Aggregation Group Identifier
      • 43.3.6.2 Representation of the Link Aggregation Group Identifier
    • 43.3.7 Selecting a Link Aggregation Group
    • 43.3.8 Agreeing on a Link Aggregation Group
    • 43.3.9 Attaching a link to an Aggregator
    • 43.3.10 Signaling readiness to transfer user data
    • 43.3.11 Enabling Collection and Distribution
    • 43.3.12 Monitoring the membership of a Link Aggregation Group
    • 43.3.13 Detaching a link from an Aggregator
    • 43.3.14 Configuration and administrative control of Link Aggregation
    • 43.3.15 Link Aggregation Control state information
  • 43.4 Link Aggregation Control Protocol (LACP)  ▶
    • 43.4.1 LACP design elements
    • 43.4.2 LACPDU structure and encoding  ▶
      • 43.4.2.1 Transmission and representation of octets
      • 43.4.2.2 LACPDU structure
    • 43.4.3 LACP state machine overview
    • 43.4.4 Constants
    • 43.4.5 Variables associated with the System
    • 43.4.6 Variables associated with each Aggregator
    • 43.4.7 Variables associated with each port
    • 43.4.8 Variables used for managing the operation of the state machines
    • 43.4.9 Functions
    • 43.4.10 Timers
    • 43.4.11 Messages
    • 43.4.12 Receive machine
    • 43.4.13 Periodic Transmission machine
    • 43.4.14 Selection Logic  ▶
      • 43.4.14.1 Selection Logic—Requirements
      • 43.4.14.2 Selection Logic—Recommended default operation
    • 43.4.15 Mux machine
    • 43.4.16 Transmit machine
    • 43.4.17 Churn Detection machines
  • 43.5 Marker protocol  ▶
    • 43.5.1 Introduction
    • 43.5.2 Sequence of operations
    • 43.5.3 Marker and Marker Response PDU structure and encoding  ▶
      • 43.5.3.1 Transmission and representation of octets
      • 43.5.3.2 Marker and Marker Response PDU structure
    • 43.5.4 Protocol definition  ▶
      • 43.5.4.1 Operation of the marker protocol
      • 43.5.4.2 Marker Responder state diagram  ▶
        • 43.5.4.2.1 Constants
        • 43.5.4.2.2 Variables
        • 43.5.4.2.3 Messages
  • 43.6 Configuration capabilities and restrictions  ▶
    • 43.6.1 Use of system and port priorities
    • 43.6.2 Dynamic allocation of operational Keys
    • 43.6.3 Link Aggregation on shared-medium links
    • 43.6.4 Selection Logic variants  ▶
      • 43.6.4.1 Reduced reconfiguration
      • 43.6.4.2 Limited Aggregator availability
  • 43.7 Protocol Implementation Conformance Statement (PICS) proforma for Clause 43, Aggregation of Multiple Link Segments  ▶
    • 43.7.1 Introduction
    • 43.7.2 Identification  ▶
      • 43.7.2.1 Implementation identification
      • 43.7.2.2 Protocol summary
    • 43.7.3 Major capabilities/options
    • 43.7.4 Frame Collector
    • 43.7.5 Frame Distributor
    • 43.7.6 Marker protocol
    • 43.7.7 Aggregator Parser/Multiplexer
    • 43.7.8 Control Parser/Multiplexer
    • 43.7.9 System identification
    • 43.7.10 Aggregator identification
    • 43.7.11 Port identification
    • 43.7.12 Capability identification
    • 43.7.13 Link Aggregation Group identification
    • 43.7.14 Detaching a link from an Aggregator
    • 43.7.15 LACPDU structure
    • 43.7.16 State machine variables
    • 43.7.17 Receive machine
    • 43.7.18 Periodic Transmission machine
    • 43.7.19 Selection Logic
    • 43.7.20 Mux machine
    • 43.7.21 Transmit machine
    • 43.7.22 Churn Detection machine
    • 43.7.23 Marker protocol
    • 43.7.24 Configuration capabilities and restrictions
    • 43.7.25 Link Aggregation on shared-medium links
• A Additional reference material
• B System guidelines  ▶
  • B.1 Baseband system guidelines and concepts, 10 Mb/s  ▶
    • B.1.1 Overall system objectives
    • B.1.2 Analog system components and parameter values
    • B.1.3 Minimum frame length determination
    • B.1.4 System jitter budgets  ▶
      • B.1.4.1 Nominal jitter values
      • B.1.4.2 Decoder evaluation
    • B.1.5 Systems consideration calculations  ▶
      • B.1.5.1 Overview
      • B.1.5.2 Maximum collision fragment size  ▶
        • B.1.5.2.1 Left-end base SDV
        • B.1.5.2.2 Mid-base SDV
        • B.1.5.2.3 Right-end base SDV
      • B.1.5.3 Interpacket Gap (IPG) shrinkage  ▶
        • B.1.5.3.1 Transmitting end segment variability value
        • B.1.5.3.2 Mid-segment variability value
      • B.1.5.4 Timing parameters for round-trip delay and variability calculations  ▶
        • B.1.5.4.1 MAU parameters
        • B.1.5.4.2 Repeater parameters
        • B.1.5.4.3 Media parameters
        • B.1.5.4.4 DTE parameters
  • B.2 System parameters and budgets for 1BASE5  ▶
    • B.2.1 Delay budget
    • B.2.2 Minimum frame length determination
    • B.2.3 Jitter budget
  • B.3 Example crosstalk computation for multiple disturbers, balanced-pair cable
  • B.4 10BASE-T guidelines  ▶
    • B.4.1 System jitter budget
    • B.4.2 Filter characteristics
    • B.4.3 Notes for conformance testing  ▶
      • B.4.3.1 Notes for 14.3.1.2.1 on differential output voltage
      • B.4.3.2 Note for 14.3.1.2.2 on transmitter differential output impedance
      • B.4.3.3 Note for 14.3.1.2.3 on output timing jitter
      • B.4.3.4 General note on common-mode tests
      • B.4.3.5 Note for 14.3.1.3.4 on receiver differential input impedance
      • B.4.3.6 Note for 14.3.1.3.3 on receiver idle input behavior
      • B.4.3.7 Note for 14.3.1.3.5 on receiver common-mode rejection
  • B.5 10BASE-F  ▶
    • B.5.1 System jitter budget
    • B.5.2 10BASE-FP fiber optic segment loss budget
• C State diagram, MAC sublayer
• D Application context, selected medium specifications  ▶
  • D.1 Introduction
  • D.2 Type 10BASE5 applications
  • D.3 Type 10BASE2 applications
  • D.4 Type FOIRL and 10BASE-F Applications; alternative fiber optic medium applications  ▶
    • D.4.1 Alternative fiber types  ▶
      • D.4.1.1 Theoretical coupling losses
      • D.4.1.2 Maximum launch power
    • D.4.2 Type 10BASE-FP applications using 50/125 m fiber  ▶
      • D.4.2.1 Coupled transmit power
      • D.4.2.2 Star coupler loss
      • D.4.2.3 Collision detection
  • D.5 10BASE-T use of cabling systems with a nominal differential characteristic impedance of 120 ω
  • D.6 10BASE-T use of cabling systems with a nominal differential characteristic impedance of 150 ω
• E Receiver wavelength design considerations (FOIRL)
• F Additional attributes required for systems  ▶
  • F.1 Introduction  ▶
    • F.1.1 Scope
  • F.2 Objects/Attributes/Actions/Notifications  ▶
    • F.2.1 TimeSinceSystemReset attribute
    • F.2.2 RepeaterResetTimeStamp attribute
    • F.2.3 ResetSystemAction action
• G Additional material required for conformance testing  ▶
  • G.1 Introduction  ▶
    • G.1.1 Material in support of the aDataRateMismatches attribute
• H GDMO specifications for CSMA/CD managed objects  ▶
  • H.1 Use of MAC and PLS Sublayer Management Definitions with CMIS/CMIP and 15802-2: 1995 Management Protocols  ▶
    • H.1.1 DTE MAC sublayer managed object class  ▶
      • H.1.1.1 DTE MAC sublayer formal definition
      • H.1.1.2 DTE MAC sublayer attributes
      • H.1.1.3 DTE MAC sublayer actions
    • H.1.2 ResourceTypeID managed object class  ▶
      • H.1.2.1 ResourceTypeID, formal definition
    • H.1.3 DTE physical layer managed object class  ▶
      • H.1.3.1 DTE physical layer formal definition
      • H.1.3.2 DTE physical sublayer attributes
  • H.2 GDMO specification for Repeater Management Object Class  ▶
    • H.2.1 Repeater managed object class  ▶
      • H.2.1.1 Repeater, formal definition
      • H.2.1.2 Repeater attributes
      • H.2.1.3 Repeater actions
      • H.2.1.4 Repeater notifications
    • H.2.2 ResourceTypeID managed object class  ▶
      • H.2.2.1 ResourceTypeID formal definition
    • H.2.3 Group managed object class  ▶
      • H.2.3.1 Group formal definition
      • H.2.3.2 Group attributes
      • H.2.3.3 Group notifications
    • H.2.4 Port managed object class  ▶
      • H.2.4.1 Port formal definition
      • H.2.4.2 Port attributes
      • H.2.4.3 Port actions
    • H.2.5 Common Attributes Template
  • H.3 GDMO specification for MAU Management Objects  ▶
    • H.3.1 MAU Managed Object Class  ▶
      • H.3.1.1 MAU formal definition
      • H.3.1.2 MAU attributes
      • H.3.1.3 MAU actions
      • H.3.1.4 MAU notifications
  • H.4 GDMO and ASN.1 definitions for management  ▶
    • H.4.1 Common Attributes Template
    • H.4.2 ASN.1 module
• I MII output delay, setup, and hold time budget  ▶
  • I.1 System model
  • I.2 Signal transmission path characteristics
  • I.3 Budget calculation
• J MII driver ac characteristics  ▶
  • J.1 Implications of CMOS ASIC processes
  • J.2 Ro(min) and V, I values for operation from 5 V ± 10% supply
  • J.3 Ro(min) and V, I values for operation from 3.3 ± 0.3 V supply
• K Measurement techniques for MII signal timing characteristics  ▶
  • K.1 Measuring timing characteristics of source terminated signals
  • K.2 Measuring timing characteristics of transmit signals at the MII
  • K.3 Measuring timing characteristics of receive signals at the MII
  • K.4 Measuring timing characteristics of MDIO
• L 6T code words
• M Noise budget
• N Use of cabling systems with a nominal differential characteristic impedance of 120 Ω
• O Repeater delay consistency requirements
• P Selector Field definitions
• Q IEEE 802.3 Selector Base Page definition  ▶
  • Q.1 Selector field value
  • Q.2 Technology Ability Field bit assignments
  • Q.3 Priority resolution
  • Q.4 Message Page transmission convention
• R Next Page Message Code Field definitions  ▶
  • 28C.1 Message code #0—Auto-Negotiation reserved code 1
  • 28C.2 Message code #1—Null Message code
  • 28C.3 Message code #2—Technology Ability extension code 1
  • 28C.4 Message code #3—Technology Ability extension code 2
  • 28C.5 Message code #4—Remote fault number code
  • 28C.6 Message code #5—Organizationally Unique Identifier (OUI) tag code
  • 28C.7 Message code #6—PHY identifier tag code
  • 28C.8 Message code #2047—Auto-Negotiation reserved code 2
  • 28C.9 Message code #7—100BASE-T2 technology message code
  • 28C.10 Message Code #8 - 1000BASE-T technology message code
• S Description of extensions to Clause 28 and associated annexes  ▶
  • 28D.1 Introduction
  • 28D.2 Extensions to Clause 28  ▶
    • 28D.2.1 Extensions required for Clause 31 (full duplex)
    • 28D.2.2 Extensions required for Clause 32 (100BASE-T2)
  • 28D.3 Extensions for Clause 31
  • 28D.4 Extensions for Clause 32 (100BASE-T2)
  • 28D.5 Extensions required for Clause 40 (1000BASE-T)
• T DTE and repeater delay components  ▶
  • 29A.1 DTE delay
  • 29A.2 Repeater delay
• U Recommended topology documentation
• V GDMO specification for 802.3 managed object classes  ▶
  • 30A.1 DTE MAC entity managed object class  ▶
    • 30A.1.1 DTE MAC entity formal definition
    • 30A.1.2 DTE MAC entity attributes
    • 30A.1.3 DTE MAC entity actions
  • 30A.2 DTE physical entity managed object class
  • 30A.2 DTE physical entity formal definition  ▶
    • 30A.2.2 DTE physical entity attributes
    • 30A.2.3 DTE physical entity actions
  • 30A.3 DTE MAC control entity managed object class  ▶
    • 30A.3.1 DTE MAC control entity formal definition
    • 30A.3.2 DTE MAC Control entity attributes
  • 30A.4 DTE MAC Control function entity managed object class  ▶
    • 30A.4.1 DTE MAC Control function entity formal definition
    • 30A.4.2 DTE MAC Control function entity attributes
  • 30A.5 Repeater managed object class  ▶
    • 30A.5.1 Repeater, formal definition
    • 30A.5.2 Repeater attributes
    • 30A.5.3 Repeater actions
    • 30A.5.4 Repeater notifications
  • 30A.6 Group managed object class  ▶
    • 30A.6.1 Group, formal definition
    • 30A.6.2 Group attributes
    • 30A.6.3 Group notifications
  • 30A.7 Repeater port managed object class  ▶
    • 30A.7.1 Port, formal definition
    • 30A.7.2 Port attributes
    • 30A.7.3 Port actions
  • 30A.8 MAU managed object class  ▶
    • 30A.8.1 MAU, formal definition
    • 30A.8.2 MAU attributes
    • 30A.8.3 MAU actions
    • 30A.8.4 MAU notifications
  • 30A.9 AutoNegotiation managed object class  ▶
    • 30A.9.1 AutoNegotiation, formal definition
    • 30A.9.2 Auto-Negotiation attributes  ▶
      • 30.A.9.3 AutoNegotiation actions
  • 30A.10 ResourceTypeID managed object class  ▶
    • 30A.10.1 ResourceTypeID, formal definition
  • 30A.11 Aggregator managed object class  ▶
    • 30A.11.1 Aggregator, formal definition
    • 30A.11.2 Aggregator attributes
    • 30A.11.3 Aggregator notifications
  • 30A.12 Aggregation Port managed object class  ▶
    • 30A.12.1 Aggregation Port, formal definition
    • 30A.12.2 Aggregation Port attributes
  • 30A.13 Aggregation Port Statistics managed object class  ▶
    • 30A.13.1 Aggregation Port Statistics, formal definition
    • 30A.13.2 Aggregation Port Statistics attributes
  • 30A.14 Aggregation Port Debug Information managed object class  ▶
    • 30A.14.1 Aggregation Port Debug Information, formal definition
    • 30A.14.2 Aggregation Port Debug Information attributes
• 30B GDMO and ASN.1 definitions for management  ▶
  • 30B.1 Common attributes template
  • 30B.2 ASN.1 module for CSMA/CD managed objects
• 30C SNMP MIB definitions for Link Aggregation  ▶
  • 30C.1 Introduction
  • 30C.2 The SNMP Management Framework
  • 30C.3 Security considerations
  • 30C.4 Structure of the MIB  ▶
    • 30C.4.1 Relationship to the managed objects defined in Clause 30
    • 30C.4.2 The Aggregator Group
    • 30C.4.3 The Aggregator Port List Group
    • 30C.4.4 The Aggregation Port Group
    • 30C.4.5 The Aggregation Port Statistics Group
    • 30C.4.6 The Aggregation Port Debug Group
• 31A MAC Control opcode assignments
• 31B MAC Control PAUSE operation  ▶
  • 31B.1 PAUSE description
  • 31B.2 Parameter semantics
  • 31B.3 Detailed specification of PAUSE operation  ▶
    • 31B.3.1 Transmit operation
    • 31B.3.2 Transmit state diagram for PAUSE operation  ▶
      • 31B.3.2.1 Constants
      • 31B.3.2.2 Variables
      • 31B.3.2.3 Functions
      • 31B.3.2.4 Timers
      • 31B.3.2.5 Messages
      • 31B.3.2.6 Transmit state diagram for PAUSE operation
    • 31B.3.3 Receive operation
    • 31B.3.4 Receive state diagram for PAUSE operation  ▶
      • 31B.3.4.1 Constants
      • 31B.3.4.2 Variables
      • 31B.3.4.3 Timers
      • 31B.3.4.4 Receive state diagram (INITIATE MAC CONTROL FUNCTION) for PAUSE operation
    • 31B.3.5 Status indication operation
    • 31B.3.6 Indication state diagram for pause operation  ▶
      • 31B.3.6.1 Constants
      • 31B.3.6.2 Variables
      • 31B.3.6.3 Messages
      • 31B.3.6.4 Indication state diagram for PAUSE operation
    • 31B.3.7 Timing considerations for PAUSE operation
  • 31B.4 Protocol Conformance Statement (PICS) proforma for MAC Control PAUSE operation  ▶
    • 31B.4.1 Introduction
    • 31B.4.2 Identification  ▶
      • 31B.4.2.1 Implementation identification
      • 31B.4.2.2 Protocol summary
    • 31B.4.3 Major capabilities/options
    • 31B.4.4 PAUSE command requirements
    • 31B.4.5 PAUSE command state diagram requirements
    • 31B.4.6 PAUSE command MAC timing considerations
• 32A Use of cabling systems with nominal differential characteristic impedance of 120 ࡎ or 150 ࡎ
• 36A Jitter test patterns  ▶
  • 36.A High-frequency test pattern
  • 36A.2 Low-frequency test pattern
  • 36A.3 Mixed frequency test pattern
  • 36A.4 Long continuous random test pattern
  • 36A.5 Short continuous random test pattern
• 36B 8B/10B transmission code running disparity calculation examples
• 38A Fiber launch conditions  ▶
  • 38A.1 Overfilled Launch
  • 38A.2 Radial Overfilled Launch (ROFL)
• 40A Additional cabling design guidelines  ▶
  • 40A.1 Alien crosstalk  ▶
    • 40A.1.1 Multipair cabling (i.e., greater than 4-pair)
    • 40A.1.2 Bundled or hybrid cable configurations
  • 40A.2 Cabling configurations
• 40B Description of cable clamp  ▶
  • 40B.1 Cable clamp validation
• 40C Add-on interface for additional Next Pages  ▶
  • 40C.1 State variables
  • 40C.2 State diagrams  ▶
    • 40C.2.1 Auto-Negotiation Transmit state machine add-on for 1000BASE-T
    • 40C.2.2 Auto-Negotiation receive state diagram add-on for 1000BASE-T
• 43A Collection and Distribution functions  ▶
  • 43A.1 Introduction
  • 43A.2 Port selection
  • 43A.3 Dynamic reallocation of conversations to different ports
  • 43A.4 Topology considerations in the choice of distribution algorithm
• 1 Requirements for support of Slow Protocols  ▶
  • 1.1 Introduction and rationale
  • 1.2 Slow Protocol transmission characteristics
  • 1.3 Addressing
  • 1.4 Protocol identification
  • 1.5 Handling of Slow Protocol frames
  • 1.6 Protocol Implementation Conformance Statement (PICS) proforma for Annex 43B, Requirements for support of Slow Protocols  ▶
    • 1.6.1 Introduction
    • 1.6.2 Identification  ▶
      • 1.6.2.1 Implementation identification
      • 1.6.2.2 Protocol summary
      • 1.6.2.3 Transmission characteristics
      • 1.6.2.4 Frame handling
• 2 LACP standby link selection and dynamic Key management  ▶
  • 2.1 Introduction
  • 2.2 Goals
  • 2.3 Standby link selection
  • 2.4 Dynamic Key management
  • 2.5 A dynamic Key management algorithm
  • 2.6 Example 1
  • 2.7 Example 2