logo资料库

IEEE Std 802.3az™-2010.pdf

第1页 / 共302页
第2页 / 共302页
第3页 / 共302页
第4页 / 共302页
第5页 / 共302页
第6页 / 共302页
第7页 / 共302页
第8页 / 共302页
资料共302页,剩余部分请下载后查看
IEEE Std 802.3az-2010 (Amendment to IEEE Std 802.3-2008) Front cover
Title page
Introduction
Notice to users
Laws and regulations
Copyrights
Updating of IEEE documents
Errata
Downloads
Interpretations
Patents
Participants
List of special symbols
Contents
Important notice
1. Introduction
1.4 Definitions
1.5 Abbreviations
14. Twisted-pair medium attachment unit (MAU) and baseband medium, type 10BASE-T including type 10BASE-Te
14.1 Scope
14.1.1 Overview
14.1.1.1 Medium Attachment Unit (MAU)
14.1.1.3 Twisted-pair media
14.3.1 MAU-to-MDI interface characteristics
14.3.1.2 Transmitter specifications
14.3.1.2.1 Differential output voltage
14.4 Characteristics of the simplex link segment
14.4.1 Overview
14.4.2 Transmission parameters
14.4.2.1 Insertion loss
14.5 MDI specification
14.5.2 Crossover function
14.8 MAU labeling
14.10 Protocol implementation conformance statement (PICS) proforma for Clause 14, twisted-pair medium attachment unit (MAU) and baseband medium, type 10BASE-T and type 10BASE-Te
14.10.3 Identification of the protocol
14.10.4 PICS proforma for 10BASE-T
14.10.4.5 PICS proforma tables for MAU
14.10.4.5.12 Transmitter specification
14.10.4.7 PICS proforma tables for 10BASE-T link segment
14.10.4.7.1 10BASE-T link segment characteristics
22. Reconciliation Sublayer (RS) and Media Independent Interface (MII)
22.2 Functional specifications
22.2.1 Mapping of MII signals to PLS service primitives and Station Management
22.2.1.3 Mapping of PLS_CARRIER.indication
22.2.1.3.1 Semantics of the service primitive
22.2.1.3.2 When generated
22.2.2 MII signal functional specifications
22.2.2.2 RX_CLK (receive clock)
22.2.2.4 TXD (transmit data)
22.2.2.5 TX/ER (transmit coding error)
22.2.2.5a Transmit direction LPI transition
22.2.2.7 RXD (receive data)
22.2.2.8 RX_ER (receive error)
22.2.2.8a Receive direction LPI transition
22.6 Mechanical characteristics
22.6a LPI assertion and detection
22.6a.1 LPI messages
22.6a.2 Transmit LPI state diagram
22.6a.2.1 Conventions
22.6a.2.2 Variables and counters
22.6a.2.3 State diagram
22.6a.3 Considerations for transmit system behavior
22.6a.3.1 Considerations for receive system behavior
22.7 Protocol implementation conformance statement (PICS) proforma for Clause 22, Reconciliation Sublayer (RS) and Media Independent Interface (MII)
22.7.2 Identification
22.7.2.3 Major capabilities/options
22.7.3 PICS proforma tables for reconciliation sublayer and media independent interface
22.7.3.2 MII signal functional specifications
22.7.3.2a LPI functions
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.4 Auto-Negotiation
24.1.6 Functional block diagram
24.2 Physical Coding Sublayer (PCS)
24.2.2 Functional requirements
24.2.2.1 Code-groups
24.2.2.1.1 Data code-groups
24.2.2.1.5a SLEEP code-groups (/P/)
24.2.3 State variables
24.2.3.1 Constants
24.2.3.2 Variables
24.2.3.4 Timers
24.2.4 State diagrams
24.2.4.2 Transmit
24.2.4.4 Receive
24.3 Physical Medium Attachment (PMA) sublayer
24.3.1 Service interface
24.3.1.8 PMA_LPILINKFAIL.request
24.3.1.8.1 Semantics of the service primitive
24.3.1.8.2 When generated
24.3.1.8.3 Effect of receipt
24.3.1.9 PMA_RXLPI.request
24.3.1.9.1 Semantics of the service primitive
24.3.1.9.2 When generated
24.3.1.9.3 Effect of receipt
24.3.2 Functional requirements
24.3.2.1 Far-End fault
24.3.2.3 EEE capability
24.3.3 State variables
24.3.3.2 Variables
24.3.4 Process specifications and state diagrams
24.3.4.4 Link Monitor
24.3.4.5 Far-End Fault Generation
24.4 Physical Medium Dependent (PMD) sublayer service interface
24.4.1 PMD service Interface
24.4.1.4 PMD_RXQUIET.request
24.4.1.4.1 Semantics of the service primitive
24.4.1.4.2 When generated
24.4.1.4.3 Effect of receipt
24.4.1.5 PMD_TXQUIET.request
24.4.1.5.1 Semantics of the service primitive
24.4.1.5.2 When generated
24.4.1.5.3 Effect of receipt
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.2 Identification
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.5 LPI functions
25. Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-TX
25.1 Overview
25.1.1 State diagram conventions
25.3 General exceptions
25.4 Specific requirements and exceptions
25.4.6 Change to 9.1.9, “Jitter”
25.4a EEE capability
25.4a.1 Change to TP-PMD 7.1.2 “Encoder”
25.4a.1.1 State variables
25.4a.1.1.1 Variables
25.4a.1.1.2 Messages
25.4a.1.2 State diagram
25.4a.2 Change to TP-PMD 7.2.2 “Decoder”
25.4a.2.1 State variables
25.4a.2.1.1 Variables
25.4a.2.1.2 Messages
25.4a.2.2 State diagram
25.4a.3 Changes to 10.1.1.1 “Signal_Detect assertion threshold”
25.4a.4 Changes to 10.1.1.2 “Signal_Detect de-assertion threshold”
25.4a.5 Change to 10.1.2 “Signal_Detect timing requirements on assertion”
25.4a.6 Change to 10.1.3 “Signal_Detect timing requirements on de-assertion”
25.4a.7 Changes to TP-PMD 10.2 “Transmitter”
25.4a.8 Replace TP-PMD Table 4 “Signal_Detect summary” with Table 25-3
25.5 Protocol implementation conformance statement (PICS) proforma for Clause 25, Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-TX
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.5 LPI functions
30. Management
30.2 Managed objects
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.38 aTransmitLPIMicroseconds
30.3.1.1.39 aReceiveLPIMicroseconds
30.3.1.1.40 aTransmitLPITransitions
30.3.1.1.41 aReceiveLPITransitions
30.3.1.1.42 aLDFastRetrainCount
30.3.1.1.43 aLPFastRetrainCount
30.5 Layer management for medium attachment units (MAUs)
30.5.1 MAU managed object class
30.5.1.1 MAU attributes
30.5.1.1.20 aSNROpMarginChnlD
30.5.1.1.21 aEEESupportList
30.12 Layer Management for Link Layer Discovery Protocol (LLDP)
30.12.2 LLDP Local System Group managed object class
30.12.2.1 LLDP Local System Group attributes
30.12.2.1.14 aLldpXdot3LocTxTwSys
30.12.2.1.15 aLldpXdot3LocTxTwSysEcho
30.12.2.1.16 aLldpXdot3LocRxTwSys
30.12.2.1.17 aLldpXdot3LocRxTwSysEcho
30.12.2.1.18 aLldpXdot3LocFbTwSys
30.12.2.1.19 aLldpXdot3TxDllReady
30.12.2.1.20 aLldpXdot3RxDllReady
30.12.2.1.21 aLldpXdot3LocDllEnabled
30.12.3 LLDP Remote System Group managed object class
30.12.3.1 LLDP Remote System Group attributes
30.12.3.1.13 aLldpXdot3RemMaxFrameSize
30.12.3.1.14 aLldpXdot3RemTxTwSys
30.12.3.1.15 aLldpXdot3RemTxTwSysEcho
30.12.3.1.16 aLldpXdot3RemRxTwSys
30.12.3.1.17 aLldpXdot3RemRxTwSysEcho
30.12.3.1.18 aLldpXdot3RemFbTwSys
35. Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)
35.1 Overview
35.1.1 Summary of major concepts
35.2 Functional specifications
35.2.1 Mapping of GMII signals to PLS service primitives and Station Management
35.2.2 GMII signal functional specifications
35.2.2.1 GTX_CLK (1000 Mb/s transmit clock)
35.2.2.2 RX_CLC (receive clock)
35.2.2.4 TXD (transmit data)
35.2.2.5 TX_ER (transmit coding error)
35.2.2.5a Transmit direction LPI transition
35.2.2.7 RXD (receive data)
35.2.2.8 RX_ER (receive error)
35.2.2.8a Receive direction LPI transition
35.3 Signal mapping
35.3a LPI Assertion and Detection
35.3a.1 LPI messages
35.3a.2 Transmit LPI state diagram
35.3a.2.1 Conventions
35.3a.2.2 Variables and counters
35.3a.2.3 State diagram
35.3a.3 Considerations for transmit system behavior
35.3a.3.1 Considerations for receive system behavior
35.5 Protocol implementation conformance statement (PICS) proforma for Clause 35, Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)
35.5.2 Identification
35.5.2.3 Major capabilities/options
35.5.3 PICS proforma tables for reconciliation sublayer and Gigabit Media independent interface
35.5.3.3 Data stream structure
35.5.3.3a LPI functions
36. Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 1000BASE-X
36.2 Physical Coding Sublayer (PCS)
36.2.4 8B/10B transmission code
36.2.4.7 Ordered_sets
36.2.4.12 IDLE (/I/)
36.2.4.12a Low Power Idle (LPI)
36.2.5 Detailed functions and state diagrams
36.2.5.1 State variables
36.2.5.1.2 Constants
36.2.5.1.3 Variables
36.2.5.1.5 Counters
36.2.5.1.6 Messages
36.2.5.1.7 Timers
36.2.5.2.1 Transmit
36.2.5.2.2 Receive
36.2.5.2.6 Synchronization
36.2.5.2.8 LPI state diagram
36.2.5.2.9 LPI status and management
36.7 Protocol implementation conformance statement (PICS) proforma for Clause 36, Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 1000BASE-X
36.7.3 Major capabilities/options
36.7.4 PICS proforma tables for the PCS and PMA sublayer, type 1000BASE-X
36.7.4.9 LPI functions
40. Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 1000BASE-T
40.1 Overview
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.2 1000BASE-T Service Primitives and Interfaces
40.2.2 PMA Service Interface
40.2.10 PMA_RESET.indication
40.2.11 PMA_LPIMODE.indication
40.2.11.1 Semantics of the primitive
40.2.11.2 When generated
40.2.11.3 Effect of receipt
40.2.12 PMA_LPIREQ.request
40.2.12.1 Semantics of the primitive
40.2.12.2 When generated
40.2.12.3 Effect of receipt
40.2.13 PMA_REMLPIREQ.request
40.2.13.1 Semantics of the primitive
40.2.13.2 When generated
40.2.13.3 Effect of receipt
40.2.14 PMA_UPDATE.indication
40.2.14.1 Semantics of the primitive
40.2.14.2 When generated
40.2.14.3 Effect of receipt
40.2.15 PMA_REMUPDATE.request
40.2.15.1 Semantics of the primitive
40.2.15.2 When generated
40.2.15.3 Effect of receipt
40.3 Physical Coding Sublayer (PCS)
40.3.1 PCS functions
40.3.1.3 PCS Transmit function
40.3.1.3.4 Generation of bits Sdn[8:0]
40.3.1.4 PCS Receive function
40.3.1.6 PCS Local LPI Request function
40.3.3 State variables
40.3.3.1 Variables
40.3.4 State diagrams
40.4 Physical Medium Attachment (PMA) sublayer
40.4.2 PMA functions
40.4.2.4 PHY Control function
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.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.6 PMA electrical specifications
40.6.1 PMA-to-MDI interface tests
40.6.1.2 Transmitter electrical specifications
40.6.1.2.5 Transmitter timing jitter
40.6.1.2.6 Transmit clock frequency
40.6.1.2.7 Transmitter operation following a transition from the QUIET to the WAKE state
40.6.1.3.5 Signal_detect
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.2 Major capabilities/options
40.12.4 Physical Coding Sublayer (PCS)
40.12.4.1 PCS receive 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
45. Management Data Input/Output (MDIO) Interface
45.2 MDIO Interface Registers
45.2.1 PMA/PMD registers
45.2.1.76 10GBASE-KR PMD control register (Register 1.150)
45.2.1.76a 10GBASE-T fast retrain status and control register (Register 1.147)
45.2.1.76a.1 LP fast retrain count (1.147.15:11)
45.2.1.76a.2 LD fast retrain count (1.147.10:6)
45.2.1.76a.3 Fast retrain ability (1.147.4)
45.2.1.76a.4 Fast retrain negotiated (1.147.3)
45.2.1.76a.5 Fast retrain signal type (1.147.2:1)
45.2.1.76a.6 Fast retrain enable (1.147.0)
45.2.3 PCS registers
45.2.3.1 PCS control 1 register (Register 3.0)
45.2.3.1.3a Clock stop enable (3.0.10)
45.2.3.2 PCS status 1 register (Register 3.1)
45.2.3.2a Transmit LPI received (3.1.11)
45.2.3.2b Receive LPI received (3.1.10)
45.2.3.2c Transmit LPI indication (3.1.9)
45.2.3.2d Receive LPI indication (3.1.8)
45.2.3.2.2a Clock stop capable (3.1.6)
45.2.3.8 PCS package identifier (Registers 3.14 and 3.15)
45.2.3.8a EEE capability (Register 3.20)
45.2.3.8a.1 10GBASE-KR EEE supported (3.20.6)
45.2.3.8a.2 10GBASE-KX4 EEE supported (3.20.5)
45.2.3.8a.3 1000BASE-KX EEE supported (3.20.4)
45.2.3.8a.4 10GBASE-T EEE supported (3.20.3)
45.2.3.8a.5 1000BASE-T EEE supported (3.20.2)
45.2.3.8a.6 100BASE-TX EEE supported (3.20.1)
45.2.3.8b EEE wake error counter (Register 3.22)
45.2.4 PHY XS registers
45.2.4.1 PHY XS control 1 register (Register 4.0)
45.2.4.1.3 Low power (4.0.11)
45.2.4.1.3a Clock stop enable (4.0.10)
45.2.4.1.3b XAUI stop enable (4.0.9)
45.2.4.2 PHY XS status 1 register (Register 4.1)
45.2.4.2a Transmit LPI received (4.1.11)
45.2.4.2b Receive LPI received (4.1.10)
45.2.4.2c Transmit LPI indication (4.1.9)
45.2.4.2d Receive LPI indication (4.1.8)
45.2.4.2.2a Clock stop capable (4.1.6)
45.2.4.7 PHY XS package identifier (Registers 4.14 and 4.15)
45.2.4.7a EEE capability (Register 4.20)
45.2.4.7a.2 PHY XS EEE supported (4.20.4)
45.2.4.7a.3 XAUI stop capable (4.20.0)
45.2.4.7b EEE wake error counter (Register 4.22)
45.2.5 DTE XS registers
45.2.5.1 DTE XS control 1 register (Register 5.0)
45.2.5.1.3 Low power (50.1.11)
45.2.5.1.3a Clock stop enable (5.0.10)
45.2.5.1.3b XAUI stop enable (5.0.9)
45.2.5.2 DTE XS status 1 register (Register 5.1)
45.2.5.2a Transmit LPI received (5.1.11)
45.2.5.2b Receive LPI received (5.1.10)
45.2.5.2c Transmit LPI indication (5.1.9)
45.2.5.2d Receive LPI indication (5.1.8)
45.2.5.2.2a Clock stop capable (5.1.6)
45.2.5.7 DTE XS package identifier (Registers 5.14 and 5.15)
45.2.5.7a EEE capability (Register 5.20)
45.2.5.7a.1 PHY XS EEE supported (5.20.4)
45.2.5.7a.2 XAUI stop capable (5.20.0)
45.2.5.7b EEE wake error counter (Register 5.22)
45.2.7 Auto-Negotiation registers
45.2.7.10 10GBASE-T AN control register (Register 7.32)
45.2.7.10.5 LD PMA training reset request (7.32.2)
45.2.7.10.5a Fast retrain ability
45.2.7.11 10GBASE-T AN status register (Register 7.33)
45.2.7.11.7 Link partner PMA training reset request (7.33.9)
45.2.7.11.8 Fast retrain ability
45.2.7.12 Backplane Ethernet statue (Register 7.48)
45.2.7.13 EEE advertisement (Register 7.60)
45.2.7.13.1 10GBASE-KR EEE supported (7.60.6)
45.2.7.13.2 10GBASE-KX4 EEE supported (7.60.5)
45.2.7.13.3 1000BASE-KX EEE supported (7.60.4)
45.2.7.13.4 10GBASE-T EEE supported (7.60.3)
45.2.7.13.5 1000BASE-T EEE supported (7.60.2)
45.2.7.13.6 100BASE-TX EEE supported (7.60.1)
45.2.7.14 EEE link partner ability (Register 7.61)
45.5 Protocol implementation conformance statement (PICS) proforma for Clause 45, MDIO interface
45.5.3.6 PCS options
45.5.3.7 PCS management functions
45.5.3.8 Auto-Negotiation options
45.5.3.9 Auto-Negotiation management functions
46. Reconciliation Sublayer (RS) and 10 Gigabit Media Independent Interface (XGMII)
46.1 Overview
46.1.1 Summary of major concepts
46.1.7 Mapping of XGMII signals to PLS service primitives
46.1.7.3 Mapping of PLS_CARRIER.indication
46.3 XGMII functional specifications
46.3.1 Transmit
46.3.1.1 TX_CLK (10 Gb/s transmit clock)
46.3.1.2 TXC<3:0> (transmit control)
46.3.1.5 Transmit direction LPI transition
46.3.2 Receive
46.3.2.1 RX_CLK (receive clock)
46.3.2.2 RXC<3:0> (receive control)
46.3.2.4 Receive direction LPI transition
46.3.4 Link fault signaling
46.3.4.2 Variables and counters
46.3.4.3 State diagram
46.3a LPI Assertion and Detection
46.3a.1 LPI messages
46.3a.2 Transmit LPI state diagram
46.3a.2.1 Variables and counters
46.3a.2.2 State diagram
46.3a.3 Considerations for transmit system behavior
46.3a.3.1 Considerations for receive system behavior
46.5 Protocol implementation conformance statement (PICS) proforma for Clause 46, Reconciliation Sublayer (RS) and 10 Gigabit Media Independent Interface (XGMII)
46.5.2 Identification
46.5.2.3 Major capabilities/options
46.5.3 PICS proforma Tables for Reconciliation Sublayer and 10 Gigabit Media Independent Interface
46.5.3.3 Data stream structure
46.5.3.3a LPI functions
46.5.3.3b Link Interruption
47. XGMII Extender Sublayer (XGXS) and 10 Gigabit Attachment Unit Interface (XAUI)
47.1 Overview
47.1.4 Allocation of functions
47.1.5 Global signal detect function
47.1.6 Global transmit disable function
47.3 XAUI Electrical characteristics
47.3.3 Driver characteristics
47.3.3.2 Amplitude and swing
47.3.4 Receiver characteristics
47.3.4.7 EEE receiver timing
47.6 Protocol implementation conformance statement (PICS) proforma for Clause 47, XGMII Extender (XGMII) and 10 Gigabit Attachment Unit Interface (XAUI)
47.6.3 Major capabilities/options
47.6.4 PICS Proforma tables for XGXS and XAUI
47.6.4.4 LPI functions
48. Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 10GBASE-X
48.1 Overview
48.1.5 Allocation of functions
48.2 Physical Coding Sublayer (PCS)
48.2.3 Use of code-groups
48.2.4 Ordered_sets and special code-groups.
48.2.4.2 Idle (||I||) and Low Power Idle (||LPIDLE||)
48.2.4.2.3 Skip ||R||
48.2.6 Detailed functions and state diagrams
48.2.6.1 State variables
48.2.6.1.2 Constants
48.2.6.1.3 Variables
48.2.6.1.5 Counters
48.2.6.1.5a Timers
48.2.6.1.6 Message
48.2.6.2 State diagrams
48.2.6.2.2 Synchronization
48.2.6.2.3 Deskew
48.2.6.2.4 Receive
48.2.6.2.5 LPI state diagrams
48.2.6.2.6 LPI status and management
48.7 Protocol implementation conformance statement (PICS) proforma for Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type 10GBASE-X
48.7.3 Major capabilities/options
48.7.4 PICS proforma tables for the PCS and PMA sublayer, type 10GBASE-X
48.7.4.5 LPI functions
49. Physical Coding Sublayer (PCS) for 64B/66B, type 10GBASE-R
49.1 Overview
49.1.5 Inter-sublayer interfaces
49.1.6 Functional block diagram
49.2 Physical Coding Sublayer (PCS)
49.2.4 64B/66B transmission code
49.2.4.4 Control codes
49.2.4.5 Ordered sets
49.2.4.7 Idle /I/ and Low Power Idle /LI/
49.2.6 Scrambler
49.2.9 Block synchronization
49.2.13.2.2 Variables
49.2.13.2.3 Functions
49.2.13.2.4 Counters
49.2.13.2.5 Timers
49.2.13.3 State diagrams
49.2.13.3.1 LPI state diagrams
49.2.14.1 Status
49.3 Protocol implementation conformance statement (PICS) proforma for Clause 49, Physical Coding Sublayer (PCS) type 10GBASE-R
49.3.3 Major Capabilities/Options
49.3.6 Management
49.3.6.5 Auto-Negotiation for Backplane Ethernet functions
49.3.6.6 LPI functions
51. Physical Medium Attachment (PMA) sublayer, type Serial
51.2 PMA Service Interface
51.2.3 PMA_SIGNAL.indication
51.2.4 PMA_RXMODE.request
51.2.4.1 Semantics of the service primitive
51.2.4.2 When generated
51.2.4.3 Effect of receipt
51.2.5 PMA_TXMODE.request
51.2.5.1 Semantics of the service primitive
51.2.5.2 When generated
51.2.5.3 Effect of receipt
51.2.6 PMA_ENERGY.indication
51.2.6.1 Semantics of the service primitive
51.2.6.2 When generated
51.2.6.3 Effect of receipt
51.4 Sixteen-Bit Interface (XSBI)
51.4.2 Optional Signals
51.10 Protocol implementation conformance statement (PICS) proforma for Clause 51, Physical Medium Attachment (PMA) sublayer, type Serial
51.10.3 Major capabilities/options
55. Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 10GBASE-T
55.1 Overview
55.1.1 Objectives
55.1.3 Operation of 10GBASE-T
55.1.3.2 Physical Medium Attachment (PMA) sublayer
55.1.3.3 EEE capability
55.1.4 Signaling
55.2 10GBASE-T service primitives and interfaces
55.2.2 PMA service interface
55.2.2.3 PMA_UNITDATA.request
55.2.2.3.1 Semantics of the primitive
55.2.2.8 PMA REMRX_STATUS.request
55.2.2.9 PMA_ALERTDETECT.indication
55.2.2.9.1 Semantics of the primitive
55.2.2.9.2 When generated
55.2.2.9.3 Effect of receipt
55.2.2.10 PCS_RX_LPI_STATUS.request
55.2.2.10.1 Semantics of the primitive
55.2.2.10.2 When generated
55.2.2.10.3 Effect of receipt
55.2.2.11 PMA_PCSDATAMODE.indication
55.2.2.11.1 Semantics of the primitive
55.2.2.11.2 When generated
55.2.2.11.3 Effect of receipt
55.2.2.12 PMA_FR_ACTIVE.indication
55.2.2.12.1 Semantics of the primitive
55.2.2.12.2 When generated
55.2.2.12.3 Effect of receipt
55.3 Physical Coding Sublayer (PCS)
55.3.2 PCS Functions
55.3.2.2 PCS Transmit function
55.3.2.2.1 Use of blocks
55.3.2.2.9 Idle (/I/)
55.3.2.2.9a LPI (/LI/)
55.3.2.2.20 65B-LDPC framer
55.3.2.2.21 EEE capability
55.3.2.3 PCS Receive function
55.3.4 PMA training side-stream scrambler polynomials
55.3.4a LPI signaling
55.3.4a.1 LPI Synchronization
55.3.4a.2 Quiet period signaling
55.3.4a.3 Refresh period signaling
55.3.5 Detailed functions and state diagrams
55.3.5.2 State diagram parameters
55.3.5.2.1 Constants
55.3.5.2.2 Variables
55.3.5.2.3 Timers
55.3.5.2.4 Functions
55.3.5.2.5 Counters
55.3.5.4 State diagrams
55.3.6 PCS management
55.3.6.1 Status
55.4 Physical Medium Attachment (PMA) sublayer
55.4.1 PMA functional specifications
55.4.2 PMA functions
55.4.2.2 PMA Transmit function
55.4.2.2.1 Alert signal
55.4.2.2.2 Link failure signal
55.4.2.4 PMA Receive function
55.4.2.5 PHY Control function
55.4.2.5.14 Startup sequence
55.4.2.5.15 Fast retrain function
55.4.2.6 Link Monitor function
55.4.2.6a Refresh Monitor function
55.4.4 Automatic MDI/MDI-X configuration
55.4.5 State variables
55.4.5.1 State diagram variables
55.4.5.2 Timers
55.4.5.4 Counters
55.4.6 State diagrams
55.4.6.1 PHY Control state diagram
55.4.6.2 Transition counter state diagrams
55.4.6.3 Link Monitor state diagram
55.4.6.4 EEE Refresh monitor state diagram
55.4.6.5 Fast retrain state diagram
55.5 PMA electrical specifications
55.5.3 Transmitter electrical specifications
55.5.3.5 Transmit clock frequency
55.6 Management interfaces
55.6.1 Support for Auto-Negotiation
55.6.1.2 10GBASE-T Auto-Negotiation page use
55.10 PHY labeling
55.12 Protocol implementation conformance statement (PICS) proforma for Clause 55, Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and baseband medium, type 10GBASE-T
55.12.2 Major capabilities/options
55.12.3 Physical Coding Sublayer (PCS)
55.12.4 Physical Medium Attachment (PMA)
55.12.5 Management interface
55.12.6 PMA Electrical Specifications
69. Introduction to Ethernet operation over electrical backplanes
69.1 Overview
69.1.1 Scope
69.1.2 Objectives
69.2 Summary of Backplane Ethernet Sublayers
69.2.3 Physical Layer signaling systems
69.2.6 Low-Power Idle
70. Physical Medium Dependent Sublayer and Baseband Medium, Type 1000BASE-KX
70.1 Overview
70.2 Physical Medium Dependent (PMD) service interface
70.2.1 PMD_RXQUIET.request
70.2.1.1 Semantics of the service primitive
70.2.1.2 When generated
70.2.1.3 Effect of receipt
70.2.2 PMD_TXQUIET.request
70.2.2.1 Semantics of the service primitive
70.2.2.2 When generated
70.2.2.3 Effect of receipt
70.6 PMD functional specifications
70.6.4 PMD signal detect function
70.6.5 PMD transmit disable function
70.6.10 PMD LPI function
70.7 1000BASE-KX electrical characteristics
70.7.1 Transmitter characteristics
70.7.1.5 Output amplitude
70.10 Protocol implementation conformance statement (PICS) proforma for Clause 70, Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE-KX
70.10.3 Major capabilities/options
70.10.4 PICS proforma tables for Clause 70, Physical Medium Dependent (PMD) sublayer and baseband medium, type 1000BASE-KX
70.10.4.1 PMD functional specifications
70.10.4.3 Transmitter electrical characteristics
71. Physical Medium Dependent Sublayer and Baseband Medium, Type 10GBASE-KX4
71.1 Overview
71.2 Physical Medium Dependent (PMD) service interface
71.2.1 PMD_RXQUIET.request
71.2.1.1 Semantics of the service primitive
71.2.1.2 When generated
71.2.1.3 Effect of receipt
71.2.2 PMD_TXQUIET.request
71.2.2.1 Semantics of the service primitive
71.2.2.2 When generated
71.2.2.3 Effect of receipt
71.6 PMD functional specifications
71.6.4 Global PMD signal detect function
71.6.6 Global PMD transmit disable function
71.6.12 PMD LPI function
71.7 Electrical characteristics for 10GBASE-KX4
71.7.1 Transmitter characteristics
71.7.1.4 Output amplitude
71.7.2 Receiver characteristics
71.10 Protocol implementation conformance statement (PICS) proforma for Clause 71, Physical Medium Dependent (PMD) sublayer and baseband medium, type 10GBASE-KX4
71.10.3 Major capabilities/options
71.10.4 PICS proforma tables for Clause 71, Physical Medium Dependent (PMD) sublayer and baseband medium, type 10GBASE-KX4
71.10.4.2 PMD functional specifications
71.10.4.4 Transmitter electrical characteristics
72. Physical Medium Dependent Sublayer and Baseband Medium, Type 10GBASE-KR
72.1 Overview
72.2 Physical Medium Dependent (PMD) service interface
72.2.1 PMD_RX_MODE.request
72.2.1.1 Semantics of the service primitive
72.2.1.2 When generated
72.2.1.3 Effect of receipt
72.2.2 PMD_TX_MODE.request
72.2.2.1 Semantics of the service primitive
72.2.2.2 When generated
72.2.2.3 Effect of receipt
72.6 PMD functional specifications
72.6.2 PMD transmit function
72.6.4 PMD signal detect function
72.6.5 PMD transmit disable function
72.6.10 PMD control function
72.6.10.1 Overview
72.6.11. PMD LPI function
72.7 10GBASE-KR electrical characteristics
72.7.1 Transmitter characteristics
72.7.1.4 Output Amplitude
72.10 Protocol implementation conformance statement (PICS) proforma for Clause 72, Physical Medium Dependent (PMD) sublayer and baseband medium, type 10GBASE-KR
72.10.3 Major capabilities/options
72.10.4 PICS proforma tables for Clause 72, Physical Medium Dependent (PMD) sublayer and baseband medium, type 10GBASE-KR
72.10.4.2 PMD functional specifications
72.10.4.5 Transmitter electrical characteristics
73. Auto-Negotiation for Backplane Ethernet
73.11 Protocol implementation conformance statement (PICS) proforma for Clause 73, Auto-Negotiation for Backplane Ethernet
73.11.4 PICS proforma tables for Auto-Negotiation for Backplane Ethernet
73.11.4.9 Auto-Negotiation annexes
74. Forward Error Correction (FEC) sublayer for BASE-R PHYs
74.4 Inter-sublayer interfaces
74.4.1 Functional Block Diagram for 10GBASE-R PHYs
74.5 FEC service interface
74.5.1 10GBASE-R Service primitives
74.5.1.3 FEC_SIGNAL.indication
74.5.1.4 FEC_ENERGY.indication (optional)
74.5.1.4.1 Effect of receipt
74.5.1.5 FEC_LPI_ACTIVE.request (optional)
74.5.1.5.1 When generated
74.5.1.5.2 Effect of receipt
74.5.1.6 FEC_RX_MODE.request (optional)
74.5.1.6.1 When generated
74.5.1.6.2 Effect of receipt
74.5.1.7 FEC_TX_MODE.request (optional)
74.5.1.7.1 When generated
74.5.1.7.2 Effect of receipt
74.7 FEC principle of operation
74.7.4 Functions within FEC sublayer
74.7.4.7 FEC block synchronization
74.7.4.8 FEC rapid block synchronization for EEE (optional)
74.8 FEC MDIO function mapping
74.8.4 FEC Error monitoring capability
74.10 Detailed functions and state diagrams
74.10.2 State variables
74.10.2.3 Functions
74.11 Protocol implementation conformance statement (PICS) proforma for Clause 74, Forward Error Correction (FEC) sublayer for BASE-R PHYs
74.11.3 Major capabilities/options
74.11.6 FEC Error Monitoring
78. Energy-Efficient Ethernet (EEE)
78.1 Overview
78.1.1 LPI Signaling
78.1.1.1 Interlayer service interfaces
78.1.1.2 Responsibilities of LPI Client
78.1.2 LPI Client service interface
78.1.2.1 LP_IDLE.request
78.1.2.1.1 Function
78.1.2.1.2 Semantics of the service primitive
78.1.2.1.3 When generated
78.1.2.1.4 Effect of receipt
78.1.2.2 LP_IDLE.indication
78.1.2.2.1 Function
78.1.2.2.2 Semantics of the service primitive
78.1.2.2.3 When generated
78.1.2.2.4 Effect of receipt
78.1.3 Reconciliation sublayer operation
78.1.3.1 RS LPI assert function
78.1.3.2 LPI detect function
78.1.3.3 PHY LPI operation
78.1.3.3.1 PHY LPI transmit operation
78.1.3.3.2 PHY LPI receive operation
78.1.4 EEE Supported PHY types
78.2 LPI mode timing parameters description
78.3 Capabilities Negotiation
78.4 Data Link Layer Capabilities
78.4.1 Data Link Layer capabilities timing requirements
78.4.2 Control state diagrams
78.4.2.1 Conventions
78.4.2.2 Constants
78.4.2.3 Variables
78.4.2.4 Functions
78.4.2.5 State diagrams
78.4.3 State change procedure across a link
78.4.3.1 Transmitting link partner’s state change procedure across a link
78.4.3.2 Receiving link partner’s state change procedure across a link
78.5 Communication link access latency
78.5.1 10 Gb/s PHY extension using XGXS
78.6 Protocol implementation conformance statement (PICS) proforma for EEE Data Link Layer Capabilities
78.6.1 Introduction
78.6.2 Identification
78.6.2.1 Implementation identification
78.6.2.2 Protocol summary
78.6.3 Major capabilities/options
78.6.4 DLL requirements
79. IEEE 802.3 Organizationally Specific Link Layer Discovery Protocol (LLDP) type, length, and values (TLV) information elements
79.3 IEEE 802.3 Organizationally Specific TLVs
79.3.5 EEE TLV
79.3.5.1 Transmit Tw
79.3.5.2 Receive Tw
79.3.5.3 Fallback Tw
79.3.5.4 Echo Transmit and Receive Tw
79.3.5.5 EEE TLV usage rules
79.4 IEEE 802.3 Organizationally Specific TLV selection management
79.4.2 IEEE 802.3 Organizationally Specific TLV/LLDP Local and Remote System group managed object class cross references
79.5 Protocol implementation conformance statement (PICS) proforma for IEEE 802.3 Organizationally Specific Link Layer Discovery Protocol (LLDP) type, length, and values (TLV) information elements
79.5.3 Major capabilities/options
79.5a EEE TLV
Annex 28C (normative) Next page Message Code field definitions
28C.12 Message code 10-EEE technology message code
Annex 28D (normative) Description of extensions to Clause 28 and associated annexes
28D.7 Extensions required for Energy-Efficient Ethernet (Clause 78)
Annex 73A (normative) Next page Message Code field definitions
73A.4 Message code 10-EEE technology message code
Annex 74A (informative) FEC block coding examples
74A.4 Output of the PN-2112 sequence generator
,QIRUPDWLRQWHFKQRORJ\³ ,(((6WDQGDUGIRU  7HOHFRPPXQLFDWLRQVDQGLQIRUPDWLRQ  /RFDODQGPHWURSROLWDQDUHDQHWZRUNV³ 6SHFLÀFUHTXLUHPHQWV H[FKDQJHEHWZHHQV\VWHPV³ 0 7 ] D      3DUW&DUULHU6HQVH0XOWLSOH$FFHVVZLWK &ROOLVLRQ'HWHFWLRQ &60$&' $FFHVV0HWKRG DQG3K\VLFDO/D\HU6SHFLÀFDWLRQV $PHQGPHQW0HGLD$FFHVV&RQWURO3DUDPHWHUV 3K\VLFDO/D\HUVDQG0DQDJHPHQW3DUDPHWHUVIRU (QHUJ\(IÀFLHQW(WKHUQHW ,(((&RPSXWHU6RFLHW\ 6SRQVRUHGE\WKH /$10$16WDQGDUGV&RPPLWWHH ,((( 3DUN$YHQXH 1HZ
IEEE Std 802.3az™-2010 (Amendment to IEEE Std 802.3™-2008) IEEE Standard for Information technology— Telecommunications and information exchange between systems— Local and metropolitan area networks— Specific requirements Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications Amendment 5: Media Access Control Parameters, Physical Layers, and Management Parameters for Energy-Efficient Ethernet LAN/MAN Standards Committee of the IEEE Computer Society Approved 30 September 2010 IEEE SA-Standards Board Approved 7 June 2010 American National Standards Institute
Abstract: This amendment to IEEE Std 802.3–2008 specifies changes to several existing physical layers to enable energy-efficient operation of Ethernet. Changes to 10BASE-T include a reduction in transmit voltage requirements. Changes to 100BASE-TX, 1000BASE-T, 10GBASE-T, 1000BASE-KX, 10GBASE-KX4 and 10GBASE-KR include the definition of a Low Power Idle (LPI) mode and mechanisms to communicate and manage the entry and exit into and out of LPI and the operation of this mode. New Link Layer Discovery Protocol (LLDP) TLVs are defined for negotiating system level energy-efficiency parameters. Keywords: 10BASE-T, 100BASE-TX, 1000BASE-KX, 1000BASE-T, 10GBASE-KR, 10GBASE- KX4, 10GBASE-T, Backplane Ethernet, Energy-Efficient Ethernet (EEE), IEEE 802.3az, LLDP, Low Power Idle Mode (LPI), TLV The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright © 2010 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 27 October 2010. Printed in the United States of America. IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and Electronics Engineers, Incorporated. PDF: Print: ISBN 978-0-7381-6485-4 ISBN 978-0-7381-6486-1 STDPD97031 STD97031 IEEE prohibits discrimination, harassment and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained in its standards. Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon this, or any other IEEE Standard document. The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied “AS IS.” The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation, or every ten years for stabilization. When a document is more than five years old and has not been reaffirmed, or more than ten years old and has not been stabilized, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. In publishing and making this document available, the IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon his or her independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that any interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests except in those cases where the matter has previously received formal consideration. A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be relied upon as, a formal interpretation of the IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the formal position, explanation, or interpretation of the IEEE. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Recommendations to change the status of a stabilized standard should include a rationale as to why a revision or withdrawal is required. Comments and recommendations on standards, and requests for interpretations should be addressed to: Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USA Authorization to photocopy portions of any individual standard for internal or personal use is granted by The Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center.
Introduction This introduction is not part of IEEE Std 802.3az-2010, IEEE Standard for Information technology— Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements, Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, Amendment 5: Media Access Control Parameters, Physical Layers, and Management Parameters for Energy-Efficient Ethernet. IEEE Std 802.3 was first published in 1985. Since the initial publication, many projects have added functionality or provided maintenance updates to the specifications and text included in the standard. Each IEEE 802.3 project/amendment is identified with a suffix (e.g., IEEE 802.3az-2010). The Media Access Control (MAC) protocol specified in IEEE Std 802.3 is Carrier Sense Multiple Access with Collision Detection (CSMA/CD). This MAC protocol was included in the experimental Ethernet developed at Xerox Palo Alto Research Center. While the experimental Ethernet had a 2.94 Mb/s data rate, IEEE Std 802.3-1985 specified operation at 10 Mb/s. Since 1985 new media options, new speeds of operation, and new capabilities have been added to IEEE Std 802.3. Some of the major additions to IEEE Std 802.3 are identified in the marketplace with their project number. This is most common for projects adding higher speeds of operation or new protocols. For example, IEEE Std 802.3u™ added 100 Mb/s operation (also called Fast Ethernet); IEEE Std 802.3x™ specified full duplex operation and a flow control protocol; IEEE Std 802.3z™ added 1000 Mb/s operation (also called Gigabit Ethernet); IEEE Std 802.3ae™ added 10 Gb/s operation (also called 10 Gigabit Ethernet); and IEEE Std 802.3ah™ specified access network Ethernet (also called Ethernet in the First Mile). These major additions are all now included in, and are superseded by, IEEE Std 802.3-2008 and are not maintained as separate documents. At the time of publication of IEEE Std 802.3az-2010, IEEE Std 802.3 consists of the following documents: IEEE Std 802.3-2008 Section One—Includes Clause 1 through Clause 20, Annex A through Annex H, and Annex 4A. Section One includes the specifications for 10 Mb/s operation and the MAC, frame formats, and service interfaces used for all speeds of operation. Section Two—Includes Clause 21 through Clause 33 and Annex 22A through Annex 33E. Section Two includes management attributes for multiple protocols and speed of operation as well as specifications for providing power over twisted-pair cabling for multiple operational speeds. It also includes general information on 100 Mb/s operation as well as most of the 100 Mb/s Physical Layer specifications. Section Three—Includes Clause 34 through Clause 43 and Annex 36A through Annex 43C. Section Three includes general information on 1000 Mb/s operation as well as most of the 1000 Mb/s Physical Layer specifications. Section Four—Includes Clause 44 through Clause 55 and Annex 44A through Annex 55B. Section Four includes general information on 10 Gb/s operation as well as most of the 10 Gb/s Physical Layer specifications. Section Five—Includes Clause 56 through Clause 74 and Annex 57A through Annex 74A. Clause 56 through Clause 67 and associated annexes specify subscriber access and other Physical Layers and sublayers for operation from 512 kb/s to 1000 Mb/s, and defines services and protocol elements that enable the exchange of IEEE 802.3 format frames between stations in a subscriber access network. Clause 68 specifies a 10 Gb/s Physical Layer specification. Clause 69 through iv Copyright © 2010 IEEE. All rights reserved.
Clause 74 and associated annexes specify Ethernet operation over electrical backplanes at speeds of 1000 Mb/s and 10 Gb/s. IEEE Std 802.3av™-2009 This amendment includes changes to IEEE Std 802.3-2008 and adds Clause 75 through Clause 77 and Annex 75A through Annex 76A. This amendment adds new Physical Layers for 10 Gb/s operation on point-to-multipoint passive optical networks. IEEE Std 802.3bc™-2009 This amendment includes changes to IEEE Std 802.3-2008 and adds Clause 79. This amendment moves the Ethernet Organizationally Specific Type, Length, Value (TLV) information elements that were specified in IEEE Std 802.1AB™ to IEEE Std 802.3. IEEE Std 802.3at™-2009 This amendment includes changes to IEEE Std 802.3-2008. This amendment augments the capabilities of IEEE Std 802.3-2008 with higher power levels and improved power management information. IEEE Std 802.3™-2008/Cor 1–2009 This corrigendum corrects the PAUSE reaction timing delay value for the 10GBASE-T PHY type. IEEE Std 802.3ba™-2010 This amendment includes changes to IEEE Std 802.3-2008 and adds Clause 80 through Clause 88 and Annex 83A through Annex 83C, Annex 85A, and Annex 86A. This amendment adds MAC parameters, Physical Layers, and management parameters for the transfer of IEEE 802.3 format frames at 40 Gb/s and 100 Gb/s. IEEE Std 802.3az-2010 This amendment includes changes to IEEE Std 802.3-2008 and adds Clause 78. This amendment adds changes required to enable energy-efficient operation of several existing Physical Layers. IEEE Std 802.3 will continue to evolve. New Ethernet capabilities are anticipated to be added within the next few years as amendments to this standard. Notice to users Laws and regulations Users of these documents should consult all applicable laws and regulations. Compliance with the provisions of this standard does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so. Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document. Copyright © 2010 IEEE. All rights reserved. v
Updating of IEEE documents Users of IEEE standards should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE Standards Association website at http:// ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit the IEEE-SA website at http://standards.ieee.org. Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:// standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Downloads Portions of this standard can be downloaded from the Internet. Materials include PICS tables, data tables, and code. URLs are listed in the text in the appropriate sections. Interpretations Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/ index.html. Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. A patent holder or patent applicant has filed a statement of assurance that it will grant licenses under these rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses. Other Essential Patent Claims may exist for which a statement of assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. vi Copyright © 2010 IEEE. All rights reserved.
分享到:
收藏