10 1109@ieeestd 2010 5621025

,(((6WDQGDUGIRU
,QIRUPDWLRQWHFKQRORJ\
7HOHFRPPXQLFDWLRQVDQGLQIRUPDWLRQ
H[FKDQJHEHWZHHQV\VWHPV
/RFDODQGPHWURSROLWDQDUHDQHWZRUNV
6SHFLFUHTXLUHPHQWV
3DUW&DUULHU6HQVH0XOWLSOH$FFHVVZLWK
70
&ROOLVLRQ'HWHFWLRQ&60$&'$FFHVV0HWKRG

D]
DQG3K\VLFDO/D\HU6SHFLFDWLRQV
$PHQGPHQW0HGLD$FFHVV&RQWURO3DUDPHWHUV
3K\VLFDO/D\HUVDQG0DQDJHPHQW3DUDPHWHUVIRU
(QHUJ\(IFLHQW(WKHUQHW
,(((&RPSXWHU6RFLHW\
6SRQVRUHGE\WKH
/$10$16WDQGDUGV&RPPLWWHH
,(((
3DUN$YHQXH
1HZ<RUN1<86$
,(((6WGD]1
$PHQGPHQWWR
2FWREHU ,(((6WG
Authorized licensed use limited to: UNIVERSITY OF SUSSEX. Downloaded on July 04,2016 at 02:52:02 UTC from IEEE Xplore. Restrictions apply.
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
Abstract: This amendment to IEEE Std 802.32008 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: ISBN 978-0-7381-6485-4 STD97031

Print: ISBN 978-0-7381-6486-1 STDPD97031
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 systemsLocal and metropolitan area networksSpecific
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 OneIncludes 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 TwoIncludes 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 ThreeIncludes 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 FourIncludes 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 FiveIncludes 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 12009

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.
Participants
The following individuals were officers and members of the IEEE 802.3 Working Group at the beginning of
the working group ballot. Individuals may have not voted, voted for approval, disapproval, or abstained on
this amendment:
David J. Law, Working Group Chair
Wael William Diab, Working Group Vice Chair
Steven B. Carlson, Working Group Executive Secretary

Adam Healey, Working Group Secretary
Bradley Booth, Working Group Treasurer
Michael Bennett, IEEE P802.3az Energy-Efficient Ethernet Task Force Chair

Sanjay Kasturia, IEEE P802.3az Energy-Efficient Ethernet Task Force Editor-in-Chief
IEEE P802.3az Energy-Efficient Ethernet Clause Editors

Hugh Barrass Wael William Diab Velu Pillai
Mandeep Chadha Adam Healey Dimitry Taich
Joseph Chou David Koenen Anoop Vetteth
Gavin Parnaby
Ghani Abbas Bill Delveaux Hideki Isono

John Abbott Bryan Dietz Hirotake Iwadate
Akira Agata Chris Diminico Qiaofeng Jiang
Arne Alping Thomas Dineen Wenbin Jiang
Yehuda Alush Thuyen Dinh Thomas K. Joergensen
Peter Anslow Daniel Dove Chad Jones
Vittal Balasubramanian Michael Dudek Bheom-Soon Joo
Thananya Baldwin Joseph Dupuis Yasuaki Kawatsu
Jaya Bandyopadhyay Frank Effenberger Seung-Hwan Kim
Jim Barnette George Eisler Yongbum Kim
Denis Beaudoin David Estes Mitsunobu Kimura
Jon Beckwith John Ewen Scott Kipp
Christian Beia Daniel Feldman Shoukei Kobayashi
Ernest Bergmann Dongning Feng Paul Kolesar
Ralf-Peter Braun Alan Flatman Seiji Kozaki
Dirk Breuer Howard M. Frazier Glen Kramer
Alan Brown Ilango S. Ganga Yasuyuki Kuroda
Matthew Brown Ali Ghiasi Toshihiko Kusano
Robert Busse Dimitrios Giannakopoulos Hans Lackner
Maurice Caldwell Larry Green Lowell Lamb
J. Martin Carroll Michael Grimwood D. Matthew Landry
David Chalupsky Robert Grow Jeff Lapak
Sun-Hyok Chang Mark Gustlin Ryan Latchman
Frank Chang Paul Gyugyi Kyusang Lee
Jian Chen Marek Hajduczenia Andreas Lenkisch
Hwan-Seok Chung Hiroshi Hamano Raymond W. K. Leung
Terry Cobb Bernie Hammond Mike Peng Li
Christopher R. Cole Jeffrey Heath Ru Jian Lin
Doug Coleman Ryan Hirth Robert Lingle
Herbert V. Congdon Rita Horner Raul Lozano
Charles Cook Dean Huumala Sharon Lutz
John DAmbrosia Thong Huynh Eric Lynskey
Fumio Daido Hiroki Ikeda Anthony Magee
Yair Darshan Kazuhiko Ishibe Valerie Maguire
Piers Dawe Osamu Ishida Jeffery J. Maki
Copyright 2010 IEEE. All rights reserved. vii
Jeff Mandin George Oulundsen Olaf Storaasli
Carlo Mariotti Thomas Palkert Alan Sugg
Arthur Marris Sesha Panguluri Ken-Ichi Suzuki
Phil McClay Shashi Patel Naoki Suzuki
Michael S. McCormack Martin Patoka Steve Swanson
John McDonough Petar Pepeljugoski Andre Szczepanek
Jim McGrath Gerald Pepper Akio Tajima
Greg McSorley John Petrilla Hidenori Takahashi
Richard Mellitz Rick Pimpinella Motoyuki Takizawa
Jeffrey Meyer Scott Powell Patricia Thaler
Brian Misek Holger Quast Sashi Thiagarajan
Merrick Moeller Rick Rabinovich Geoffrey Thompson
Andy Moorwood Randy Rannow Hidehiro Toyoda
Kazuyuki Mori Duane Remein Nathan Tracy
Shimon Muller Tamir Reshef Mario Traeber
Angela Muscat Michael Ressl Matthew Traverso
Gerard Nadeau June-Koo (Kevin) Rhee Stephen Trowbridge
Edward Nakamoto Sam Sambasivan Shinji Tsuji
Jay Neer Ramesh Sastry Eddie Tsumura
Gary Nicholl Olindo Savi Brad Turner
Paul Nikolich Edward Sayre Alexander Umnov
George Noh Frederick Schindler Sterling A. Vaden
Ronald Nordin Shawn Searles Paul Vanderlaan
Ahmad Nouri Khorvash (Kory) Sefidvash Albert Vareljian
Mark Nowell Murat Serbay Andrew Weitzner
Satoshi Obara Farhad Shafai Masaki Yasukawa
David Ofelt Masayuki Shigematsu George Young
Gourgen Oganessyan Jong-Yoon Shin George Zimmerman
Akihiro Otaka Jesse Simsarian Pavel Zivny
Bryan Sparrowhawk
viii Copyright 2010 IEEE. All rights reserved.
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
Thomas Alexander Marek Hajduczenia Avygdor Moise
Richard Alfvin Hiroshi Hamano Charles Moorwood
Peter Anslow Adam Healey Jose Morales
Butch Anton Rita Horner Michael S. Newman
Jacob Ben Ary David Hunter Nick S. A. Nikjoo
Hugh Barrass James Innis Paul Nikolich
Leslie Baxter Akio Iso Kevin Noll
Michael Bennett Atsushi Ito Satoshi Obara
Tomo Bogataj Raj Jain Thomas Palkert
Bradley Booth Thomas K. Joergensen Gavin Parnaby
Ralf-Peter Braun Shinkyo Kaku Glenn Parsons
Matthew Brown Piotr Karocki Petar Pepeljugoski
William Byrd Stuart J. Kerry Subburajan Ponnuswamy
Steven B. Carlson Yongbum Kim Venkatesha Prasad
Juan Carreon Mitsunobu Kimura Maximilian Riegel
Mandeep Chadha Scott Kipp Robert Robinson
Keith Chow Gerald L. Kolbe Randall Safier
Charles Cook Seiji Kozaki Bartien Sayogo
Fumio Daido Bruce P. Kraemer Benson Schliesser
John DAmbrosia Paul Lambert Rich Seifert
Wael William Diab D. Matthew Landry Oren Sela
Thomas Dineen Jeremy Landt Gil Shultz
Daniel Dove David J. Law Kapil Sood
Michael Dudek David Lewis Amjad Soomro
Sourav Dutta Li Li Matthew Squire
Frank Effenberger Ru Jian Lin Manikantan Srinivasan
C. Fitzgerald William Lumpkins Thomas Starai
Howard M. Frazier G. Luri Walter Struppler
Yukihiro Fujimoto Eric Lynskey Joseph Tardo
Ilango S. Ganga Elvis Maculuba Patricia Thaler
Devon Gayle Valerie Maguire David Thompson
Larry Green Mark Maloney Edward J. Turner
Randall Groves Arthur Marris Mark-Rene Uchida
Robert Grow Peter Martini Kunpeng Wu
Mark Gustlin Jonathon Mclendon Oren Yuen
C. Guy Richard Mellitz Janusz Zalewski
Stephen Haddock Zhen Zhou
Copyright 2010 IEEE. All rights reserved. ix
When the IEEE-SA Standards Board approved this amendment on 30 September 2010, it had the following
membership:
Robert M. Grow, Chair
Richard H. Hulett, Vice Chair
Steve M. Mills, Past Chair
Judith Gorman, Secretary
Karen Bartleson Young Kyun Kim Ronald C. Petersen
Victor Berman Joseph L. Koepfinger* Thomas Prevost
Ted Burse John Kulick Jon Walter Rosdahl
Clint Chaplin David J. Law Sam Sciacca
Andy Drozd Hung Ling Mike Seavey
Alexander Gelman Oleg Logvinov Curtis Siller
Jim Hughes Ted Olsen Don Wright
*Member Emeritus
Also included are the following nonvoting IEEE-SA Standards Board liaisons:
Satish K. Aggarwal, NRC Representative

Richard DeBlasio, DOE Representative
Michael Janezic, NIST Representative
Michelle Turner
IEEE Standards Program Manager, Document Development
Kathryn Bennet
IEEE Standards Program Manager, Technical Program Development
x Copyright 2010 IEEE. All rights reserved.
List of special symbols
For the benefit of those who have received this document by electronic means, what follows is a list of special symbols
and operators. If any of these symbols or operators fail to print out correctly on your machine, the editors apologize, and
hope that this table will at least help you to sort out the meaning of the resulting funny-shaped blobs and strokes.
Special symbols and operators
Printed character Meaning Font

Boolean AND Symbol
+ Boolean OR, arithmetic addition Symbol
^ Boolean XOR Times New Roman
! Boolean NOT Symbol
Multiplication Symbol
< Less than Symbol
Less than or equal to Symbol
> Greater than Symbol
Greater than or equal to Symbol
= Equal to Symbol
Approximately equal to Symbol
Not equal to Symbol
Assignment operator Symbol
Indicates membership Symbol
Indicates nonmembership Symbol
Plus or minus (a tolerance) Symbol
Degrees Symbol
Summation Symbol
Square root Symbol
Big dash (em dash) Times New Roman
Little dash (en dash), subtraction Times New Roman
| Vertical bar Times New Roman
Dagger Times New Roman
Double dagger Times New Roman
Lower case alpha Symbol
Lower case beta Symbol
Lower case gamma Symbol
Lower case delta Symbol
Lower case epsilon Symbol
Lower case lambda Symbol
Lower case mu Times New Roman
Upper case pi Symbol
Upper case omega Symbol
Copyright 2010 IEEE. All rights reserved. xi
xii Copyright 2010 IEEE. All rights reserved.
Contents
1. Introduction.......................................................................................................................................... 2
1.4 Definitions ............................................................................................................................... 2

1.5 Abbreviations........................................................................................................................... 2
14. Twisted-pair medium attachment unit (MAU) and baseband medium, type 10BASE-T
including type 10BASE-Te.................................................................................................................. 3
14.1 Scope........................................................................................................................................ 3
14.1.1 Overview.................................................................................................................... 3
14.1.1.1 Medium Attachment Unit (MAU) ........................................................... 3
14.1.1.3 Twisted-pair media .................................................................................. 3
14.3.1 MAU-to-MDI interface characteristics...................................................................... 4
14.3.1.2 Transmitter specifications........................................................................ 4
14.3.1.2.1 Differential output voltage................................................... 5
14.4 Characteristics of the simplex link segment ............................................................................ 7
14.4.1 Overview.................................................................................................................... 7
14.4.2 Transmission parameters ........................................................................................... 7
14.4.2.1 Insertion loss ............................................................................................ 7
14.5 MDI specification .................................................................................................................... 7
14.5.2 Crossover function ..................................................................................................... 7
14.8 MAU labeling .......................................................................................................................... 7
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 .................................................................................... 8
14.10.3 Identification of the protocol ..................................................................................... 8
14.10.4 PICS proforma for 10BASE-T .................................................................................. 8
14.10.4.5 PICS proforma tables for MAU............................................................... 8
14.10.4.5.12 Transmitter specification .................................................... 8
14.10.4.7 PICS proforma tables for 10BASE-T link segment................................. 9
14.10.4.7.1 10BASE-T link segment characteristics ............................. 9
22. Reconciliation Sublayer (RS) and Media Independent Interface (MII)............................................. 11
22.2 Functional specifications ....................................................................................................... 11

22.2.1 Mapping of MII signals to PLS service primitives and Station Management......... 11
22.2.1.3 Mapping of PLS_CARRIER.indication ................................................ 12
22.2.1.3.1 Semantics of the service primitive..................................... 12
22.2.1.3.2 When generated ................................................................. 12
22.2.2 MII signal functional specifications ........................................................................ 12
22.2.2.2 RX_CLK (receive clock) ....................................................................... 12
22.2.2.4 TXD (transmit data)............................................................................... 13
22.2.2.5 TX/ER (transmit coding error) .............................................................. 13
22.2.2.5a Transmit direction LPI transition........................................................... 13
22.2.2.7 RXD (receive data) ................................................................................ 14
22.2.2.8 RX_ER (receive error)........................................................................... 15
22.2.2.8a Receive direction LPI transition ............................................................ 15
22.6 Mechanical characteristics ..................................................................................................... 15
22.6a LPI assertion and detection.................................................................................................... 15
22.6a.1 LPI messages ........................................................................................................... 16
22.6a.2 Transmit LPI state diagram...................................................................................... 16
Copyright 2010 IEEE. All rights reserved. xiii
22.6a.2.1 Conventions ........................................................................................... 17
22.6a.2.2 Variables and counters........................................................................... 17
22.6a.2.3 State diagram ......................................................................................... 17
22.6a.3 Considerations for transmit system behavior........................................................... 18
22.6a.3.1 Considerations for receive system behavior .......................................... 18
Reconciliation Sublayer (RS) and Media Independent Interface (MII) ................................ 18
22.7.2 Identification ............................................................................................................ 18
22.7.2.3 Major capabilities/options ..................................................................... 18
22.7.3 PICS proforma tables for reconciliation sublayer and
media independent interface .................................................................................... 19
22.7.3.2 MII signal functional specifications ...................................................... 19
22.7.3.2a LPI functions.......................................................................................... 19
24. Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer,
type 100BASE-X ............................................................................................................................... 21
24.1 Overview................................................................................................................................ 21
24.1.1 Scope........................................................................................................................ 21
24.1.2 Objectives ................................................................................................................ 21
24.1.3 Relationship of 100BASE-X to other standards ...................................................... 22
24.1.4 Summary of 100BASE-X sublayers ........................................................................ 22
24.1.4.1 Physical Coding Sublayer (PCS) ........................................................... 22
24.1.4.2 Physical Medium Attachment (PMA) sublayer..................................... 22
24.1.4.4 Auto-Negotiation ................................................................................... 23
24.1.6 Functional block diagram ........................................................................................ 23
24.2 Physical Coding Sublayer (PCS) ........................................................................................... 25
24.2.2 Functional requirements .......................................................................................... 25
24.2.2.1 Code-groups........................................................................................... 25
24.2.2.1.1 Data code-groups ............................................................... 26
24.2.2.1.5a SLEEP code-groups (/P/)................................................... 26
24.2.3 State variables .......................................................................................................... 26
24.2.3.1 Constants................................................................................................ 26
24.2.3.2 Variables ................................................................................................ 26
24.2.3.4 Timers .................................................................................................... 27
24.2.4 State diagrams.......................................................................................................... 28
24.2.4.2 Transmit ................................................................................................. 28
24.2.4.4 Receive................................................................................................... 30
24.3 Physical Medium Attachment (PMA) sublayer..................................................................... 33
24.3.1 Service interface ...................................................................................................... 33
24.3.1.8 PMA_LPILINKFAIL.request................................................................ 33
24.3.1.8.2 When generated ................................................................. 33
24.3.1.8.3 Effect of receipt.................................................................. 33
24.3.1.9 PMA_RXLPI.request............................................................................. 33
24.3.1.9.2 When generated ................................................................. 33
24.3.2 Functional requirements .......................................................................................... 34
24.3.2.1 Far-End fault .......................................................................................... 34
24.3.2.3 EEE capability ....................................................................................... 34
24.3.3 State variables .......................................................................................................... 34
24.3.3.2 Variables ................................................................................................ 34
24.3.4 Process specifications and state diagrams ............................................................... 35
xiv Copyright 2010 IEEE. All rights reserved.
24.3.4.4 Link Monitor.......................................................................................... 35
24.3.4.5 Far-End Fault Generation ...................................................................... 36
24.4 Physical Medium Dependent (PMD) sublayer service interface........................................... 37
24.4.1 PMD service Interface ............................................................................................. 37
24.4.1.4 PMD_RXQUIET.request....................................................................... 37
24.4.1.4.2 When generated ................................................................. 37
24.4.1.5 PMD_TXQUIET.request ....................................................................... 37
24.4.1.5.2 When generated ................................................................. 38
Physical Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer,
type 100BASE-X ................................................................................................................... 38
24.8.2 Identification ............................................................................................................ 38
24.8.2.3 Major capabilities/options...................................................................... 38
24.8.3 PICS proforma tables for the Physical Coding Sublayer (PCS) and
Physical Medium Attachment (PMA) sublayer, type 100BASE-X ........................ 39
24.8.3.5 LPI functions.......................................................................................... 39
25. Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-TX............. 41
25.1 Overview................................................................................................................................ 41
25.1.1 State diagram conventions ....................................................................................... 41
25.3 General exceptions................................................................................................................. 41
25.4 Specific requirements and exceptions.................................................................................... 41
25.4.6 Change to 9.1.9, Jitter........................................................................................... 41
25.4a EEE capability ....................................................................................................................... 41
25.4a.1 Change to TP-PMD 7.1.2 Encoder....................................................................... 42
25.4a.1.1 State variables ........................................................................................ 42
25.4a.1.1.1 Variables ............................................................................ 42
25.4a.1.1.2 Messages............................................................................ 43
25.4a.1.2 State diagram ......................................................................................... 43
25.4a.2 Change to TP-PMD 7.2.2 Decoder ...................................................................... 43
25.4a.2.1 State variables ........................................................................................ 43
25.4a.2.1.1 Variables ............................................................................ 43
25.4a.2.1.2 Messages............................................................................ 44
25.4a.2.2 State diagram ......................................................................................... 45
25.4a.3 Changes to 10.1.1.1 Signal_Detect assertion threshold ....................................... 45
25.4a.4 Changes to 10.1.1.2 Signal_Detect de-assertion threshold .................................. 45
25.4a.5 Change to 10.1.2 Signal_Detect timing requirements on assertion ..................... 45
25.4a.6 Change to 10.1.3 Signal_Detect timing requirements on de-assertion ................ 45
25.4a.7 Changes to TP-PMD 10.2 Transmitter................................................................. 46
25.4a.8 Replace TP-PMD Table 4 Signal_Detect summary with Table 25-3 .................. 46
Physical Medium Dependent (PMD) sublayer and baseband medium, type 100BASE-TX. 47
25.5.3 Major capabilities/options........................................................................................ 47
25.5.4 PICS proforma tables for the Physical Medium Dependent (PMD) sublayer
and baseband medium, type 100BASE-TX ............................................................. 47
25.5.4.5 LPI functions.......................................................................................... 47
Copyright 2010 IEEE. All rights reserved. xv
30. Management....................................................................................................................................... 49
30.2 Managed objects .................................................................................................................... 49

30.2.5 Capabilities .............................................................................................................. 50
30.3 Layer management for DTEs................................................................................................. 50
30.3.1 MAC entity managed object class ........................................................................... 50
30.3.1.1 MAC entity attributes ............................................................................ 50
30.3.1.1.38 aTransmitLPIMicroseconds............................................... 50
30.3.1.1.39 aReceiveLPIMicroseconds ................................................ 51
30.3.1.1.40 aTransmitLPITransitions ................................................... 51
30.3.1.1.41 aReceiveLPITransitions..................................................... 51
30.3.1.1.42 aLDFastRetrainCount ........................................................ 51
30.3.1.1.43 aLPFastRetrainCount......................................................... 52
30.5 Layer management for medium attachment units (MAUs) ................................................... 52
30.5.1 MAU managed object class ..................................................................................... 52
30.5.1.1 MAU attributes ...................................................................................... 52
30.5.1.1.20 aSNROpMarginChnlD....................................................... 52
30.5.1.1.21 aEEESupportList ............................................................... 52
30.12 Layer Management for Link Layer Discovery Protocol (LLDP) .......................................... 52
30.12.2 LLDP Local System Group managed object class .................................................. 52
30.12.2.1 LLDP Local System Group attributes ................................................... 52
30.12.2.1.14a LldpXdot3LocTxTwSys ................................................. 52
30.12.2.1.15a LldpXdot3LocTxTwSysEcho ......................................... 53
30.12.2.1.16a LldpXdot3LocRxTwSys ................................................. 53
30.12.2.1.17a LldpXdot3LocRxTwSysEcho......................................... 53
30.12.2.1.18a LldpXdot3LocFbTwSys.................................................. 53
30.12.2.1.19a LldpXdot3TxDllReady ................................................... 53
30.12.2.1.20a LldpXdot3RxDllReady ................................................... 54
30.12.2.1.21a LldpXdot3LocDllEnabled............................................... 54
30.12.3 LLDP Remote System Group managed object class ............................................... 54
30.12.3.1 LLDP Remote System Group attributes ................................................ 54
30.12.3.1.13a LldpXdot3RemMaxFrameSize ....................................... 54
30.12.3.1.14a LldpXdot3RemTxTwSys ................................................ 54
30.12.3.1.15a LldpXdot3RemTxTwSysEcho........................................ 55
30.12.3.1.16a LldpXdot3RemRxTwSys................................................ 55
30.12.3.1.17a LldpXdot3RemRxTwSysEcho........................................ 55
30.12.3.1.18a LldpXdot3RemFbTwSys ................................................ 55
35. Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)............................. 57
35.1 Overview................................................................................................................................ 57
35.1.1 Summary of major concepts .................................................................................... 57
35.2 Functional specifications ....................................................................................................... 57
35.2.1 Mapping of GMII signals to PLS service primitives and Station Management ...... 57
35.2.2 GMII signal functional specifications...................................................................... 57
35.2.2.1 GTX_CLK (1000 Mb/s transmit clock)................................................. 57
35.2.2.2 RX_CLC (receive clock) ....................................................................... 57
35.2.2.4 TXD (transmit data)............................................................................... 58
35.2.2.5 TX_ER (transmit coding error).............................................................. 58
35.2.2.5a Transmit direction LPI transition........................................................... 59
35.2.2.7 RXD (receive data) ................................................................................ 59
35.2.2.8 RX_ER (receive error)........................................................................... 60
35.2.2.8a Receive direction LPI transition ............................................................ 60
35.3 Signal mapping ...................................................................................................................... 61
xvi Copyright 2010 IEEE. All rights reserved.
35.3a LPI Assertion and Detection.................................................................................................. 61
35.3a.1 LPI messages ........................................................................................................... 62
35.3a.2 Transmit LPI state diagram...................................................................................... 62
35.3a.2.1 Conventions ........................................................................................... 62
35.3a.2.2 Variables and counters........................................................................... 63
35.3a.2.3 State diagram ......................................................................................... 63
35.3a.3 Considerations for transmit system behavior........................................................... 63
35.3a.3.1 Considerations for receive system behavior .......................................... 64
Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)................. 64
35.5.2 Identification ............................................................................................................ 64
35.5.2.3 Major capabilities/options ..................................................................... 64
35.5.3 PICS proforma tables for reconciliation sublayer and Gigabit Media
independent interface ............................................................................................... 64
35.5.3.3 Data stream structure ............................................................................. 64
35.5.3.3a LPI functions.......................................................................................... 64
type 1000BASE-X ............................................................................................................................. 65

36.2.4 8B/10B transmission code ....................................................................................... 65
36.2.4.7 Ordered_sets .......................................................................................... 65
36.2.4.12 IDLE (/I/) ............................................................................................... 65
36.2.4.12a Low Power Idle (LPI) ............................................................................ 65
36.2.5 Detailed functions and state diagrams ..................................................................... 65
36.2.5.1 State variables ........................................................................................ 65
36.2.5.1.2 Constants............................................................................ 65
36.2.5.1.3 Variables ............................................................................ 66
36.2.5.1.5 Counters ............................................................................. 67
36.2.5.1.6 Messages............................................................................ 67
36.2.5.1.7 Timers ................................................................................ 67
36.2.5.2.1 Transmit ............................................................................. 68
36.2.5.2.2 Receive............................................................................... 71
36.2.5.2.6 Synchronization ................................................................. 74
36.2.5.2.8 LPI state diagram ............................................................... 76
36.2.5.2.9 LPI status and management ............................................... 77
type 1000BASE-X ................................................................................................................. 77
36.7.3 Major capabilities/options........................................................................................ 77
36.7.4 PICS proforma tables for the PCS and PMA sublayer, type 1000BASE-X............ 78
36.7.4.9 LPI functions.......................................................................................... 78
40. Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and
baseband medium, type 1000BASE-T............................................................................................... 79
40.1 Overview................................................................................................................................ 79
40.1.3 Operation of 1000BASE-T ...................................................................................... 79
40.1.3.1 Physical Coding Sublayer (PCS) ........................................................... 81
40.1.3.2 Physical Medium Attachment (PMA) sublayer..................................... 81
40.1.4 Signaling .................................................................................................................. 81
40.2 1000BASE-T Service Primitives and Interfaces ................................................................... 81
40.2.2 PMA Service Interface............................................................................................. 81
Copyright 2010 IEEE. All rights reserved. xvii
40.2.10 PMA_RESET.indication.......................................................................................... 82
40.2.11 PMA_LPIMODE.indication .................................................................................... 82
40.2.11.1 Semantics of the primitive ..................................................................... 82
40.2.11.2 When generated ..................................................................................... 83
40.2.11.3 Effect of receipt ..................................................................................... 83
40.2.12 PMA_LPIREQ.request ............................................................................................ 83
40.2.12.2 When generated ..................................................................................... 83
40.2.13 PMA_REMLPIREQ.request.................................................................................... 83
40.2.13.2 When generated ..................................................................................... 84
40.2.14 PMA_UPDATE.indication ...................................................................................... 84
40.2.14.2 When generated ..................................................................................... 84
40.2.15 PMA_REMUPDATE.request.................................................................................. 84
40.2.15.2 When generated ..................................................................................... 85
40.3.1 PCS functions .......................................................................................................... 87
40.3.1.3 PCS Transmit function........................................................................... 87
40.3.1.3.4 Generation of bits Sdn[8:0]................................................ 87
40.3.1.4 PCS Receive function ............................................................................ 88
40.3.1.6 PCS Local LPI Request function ........................................................... 88
40.3.3 State variables .......................................................................................................... 88
40.3.3.1 Variables ................................................................................................ 88
40.3.4 State diagrams.......................................................................................................... 89
40.4 Physical Medium Attachment (PMA) sublayer..................................................................... 91
40.4.2 PMA functions ......................................................................................................... 91
40.4.2.4 PHY Control function............................................................................ 92
40.4.5 State variables .......................................................................................................... 93
40.4.5.1 State diagram variables .......................................................................... 93
40.4.5.2 Timers .................................................................................................... 94
40.4.6 State diagrams.......................................................................................................... 95
40.4.6.1 PHY Control state diagram.................................................................... 95
40.4.6.2 Link Monitor state diagram ................................................................... 97
40.5 Management interface............................................................................................................ 98
40.5.1 Support for Auto-Negotiation .................................................................................. 98
40.5.1.1 1000BASE-T use of registers during Auto-Negotiation........................ 99
40.5.1.2 1000BASE-T Auto-Negotiation page use ........................................... 100
40.6 PMA electrical specifications .............................................................................................. 100
40.6.1 PMA-to-MDI interface tests .................................................................................. 100
40.6.1.2 Transmitter electrical specifications .................................................... 100
40.6.1.2.5 Transmitter timing jitter................................................... 100
40.6.1.2.6 Transmit clock frequency ................................................ 100
40.6.1.2.7 Transmitter operation following a transition from
the QUIET to the WAKE state ........................................ 100
40.6.1.3.5 Signal_detect.................................................................... 101
Physical coding sublayer (PCS), physical medium attachment (PMA) sublayer and
baseband medium, type 1000BASE-T................................................................................. 101
xviii Copyright 2010 IEEE. All rights reserved.
40.12.2 Major capabilities/options...................................................................................... 101
40.12.4 Physical Coding Sublayer (PCS) ........................................................................... 101
40.12.4.1 PCS receive functions.......................................................................... 102
40.12.5 Physical Medium Attachment (PMA) ................................................................... 102
40.12.6 Management interface............................................................................................ 103
40.12.6.1 1000BASE-T Specific Auto-Negotiation Requirements ..................... 103
40.12.7 PMA Electrical Specifications............................................................................... 103
45. Management Data Input/Output (MDIO) Interface......................................................................... 105
45.2 MDIO Interface Registers.................................................................................................... 105

45.2.1 PMA/PMD registers .............................................................................................. 105
45.2.1.76 10GBASE-KR PMD control register (Register 1.150) ....................... 105
45.2.1.76a 10GBASE-T fast retrain status and control register (Register 1.147) . 105
45.2.1.76a.1 LP fast retrain count (1.147.15:11) ................................. 105
45.2.1.76a.2 LD fast retrain count (1.147.10:6) .................................. 106
45.2.1.76a.3 Fast retrain ability (1.147.4) ........................................... 106
45.2.1.76a.4 Fast retrain negotiated (1.147.3) ..................................... 106
45.2.1.76a.5 Fast retrain signal type (1.147.2:1) ................................. 106
45.2.1.76a.6 Fast retrain enable (1.147.0) ........................................... 106
45.2.3 PCS registers.......................................................................................................... 106
45.2.3.1 PCS control 1 register (Register 3.0) ................................................... 107
45.2.3.1.3a Clock stop enable (3.0.10) ............................................... 107
45.2.3.2 PCS status 1 register (Register 3.1) ..................................................... 107
45.2.3.2a Transmit LPI received (3.1.11)........................................ 108
45.2.3.2b Receive LPI received (3.1.10) ......................................... 108
45.2.3.2c Transmit LPI indication (3.1.9) ....................................... 108
45.2.3.2d Receive LPI indication (3.1.8) ......................................... 108
45.2.3.2.2a Clock stop capable (3.1.6) ............................................... 108
45.2.3.8 PCS package identifier (Registers 3.14 and 3.15) ............................... 108
45.2.3.8a EEE capability (Register 3.20) ............................................................ 108
45.2.3.8a.1 10GBASE-KR EEE supported (3.20.6)........................... 109
45.2.3.8a.2 10GBASE-KX4 EEE supported (3.20.5) ........................ 109
45.2.3.8a.3 1000BASE-KX EEE supported (3.20.4) ......................... 109
45.2.3.8a.4 10GBASE-T EEE supported (3.20.3).............................. 109
45.2.3.8a.5 1000BASE-T EEE supported (3.20.2)............................. 109
45.2.3.8a.6 100BASE-TX EEE supported (3.20.1)............................ 109
45.2.3.8b EEE wake error counter (Register 3.22) .............................................. 110
45.2.4 PHY XS registers................................................................................................... 110
45.2.4.1 PHY XS control 1 register (Register 4.0) ............................................ 110
45.2.4.1.3 Low power (4.0.11) ......................................................... 110
45.2.4.1.3b XAUI stop enable (4.0.9)................................................. 111
45.2.4.2 PHY XS status 1 register (Register 4.1) .............................................. 111
45.2.4.7 PHY XS package identifier (Registers 4.14 and 4.15) ........................ 112
45.2.4.7a.2 PHY XS EEE supported (4.20.4)..................................... 113
45.2.4.7a.3 XAUI stop capable (4.20.0) ............................................. 113
Copyright 2010 IEEE. All rights reserved. xix
45.2.5 DTE XS registers ................................................................................................... 113
45.2.5.1 DTE XS control 1 register (Register 5.0) ............................................ 113
45.2.5.1.3 Low power (50.1.11) ....................................................... 114
45.2.5.1.3b XAUI stop enable (5.0.9)................................................. 114
45.2.5.2 DTE XS status 1 register (Register 5.1) .............................................. 114
45.2.5.7 DTE XS package identifier (Registers 5.14 and 5.15) ........................ 115
45.2.5.7a.1 PHY XS EEE supported (5.20.4)..................................... 116
45.2.5.7a.2 XAUI stop capable (5.20.0) ............................................. 116
45.2.7 Auto-Negotiation registers..................................................................................... 116
45.2.7.10 10GBASE-T AN control register (Register 7.32) ............................... 116
45.2.7.10.5 LD PMA training reset request (7.32.2) ......................... 117
45.2.7.10.5a Fast retrain ability ........................................................... 117
45.2.7.11 10GBASE-T AN status register (Register 7.33).................................. 117
45.2.7.11.7 Link partner PMA training reset request (7.33.9)............ 117
45.2.7.11.8 Fast retrain ability ............................................................ 117
45.2.7.12 Backplane Ethernet statue (Register 7.48)........................................... 117
45.2.7.13 EEE advertisement (Register 7.60)...................................................... 117
45.2.7.13.1 10GBASE-KR EEE supported (7.60.6)........................... 118
45.2.7.13.2 10GBASE-KX4 EEE supported (7.60.5) ........................ 118
45.2.7.13.3 1000BASE-KX EEE supported (7.60.4) ......................... 118
45.2.7.13.4 10GBASE-T EEE supported (7.60.3).............................. 119
45.2.7.13.5 1000BASE-T EEE supported (7.60.2)............................. 119
45.2.7.13.6 100BASE-TX EEE supported (7.60.1)............................ 119
45.2.7.14 EEE link partner ability (Register 7.61) .............................................. 119
MDIO interface.................................................................................................................... 120
45.5.3.6 PCS options.......................................................................................... 120
45.5.3.7 PCS management functions ................................................................. 120
45.5.3.8 Auto-Negotiation options .................................................................... 121
45.5.3.9 Auto-Negotiation management functions ............................................ 121
46. Reconciliation Sublayer (RS) and 10 Gigabit Media Independent Interface (XGMII)................... 123
46.1 Overview.............................................................................................................................. 123

46.1.1 Summary of major concepts .................................................................................. 123
46.1.7 Mapping of XGMII signals to PLS service primitives .......................................... 123
46.1.7.3 Mapping of PLS_CARRIER.indication .............................................. 123
46.3 XGMII functional specifications ......................................................................................... 124
46.3.1 Transmit ................................................................................................................. 124
46.3.1.1 TX_CLK (10 Gb/s transmit clock) ...................................................... 124
46.3.1.2 TXC<3:0> (transmit control)............................................................... 124
46.3.1.5 Transmit direction LPI transition......................................................... 124
46.3.2 Receive................................................................................................................... 125
46.3.2.1 RX_CLK (receive clock) ..................................................................... 125
46.3.2.2 RXC<3:0> (receive control) ................................................................ 125
46.3.2.4 Receive direction LPI transition .......................................................... 125
xx Copyright 2010 IEEE. All rights reserved.
46.3.4
Link fault signaling ................................................................................................ 126
46.3.4.2 Variables and counters......................................................................... 127
46.3.4.3 State diagram ....................................................................................... 128
46.3a LPI Assertion and Detection................................................................................................ 128
46.3a.1 LPI messages ......................................................................................................... 129
46.3a.2 Transmit LPI state diagram.................................................................................... 129
46.3a.2.1 Variables and counters......................................................................... 129
46.3a.2.2 State diagram ....................................................................................... 130
46.3a.3 Considerations for transmit system behavior......................................................... 130
46.3a.3.1 Considerations for receive system behavior ........................................ 131
Reconciliation Sublayer (RS) and 10 Gigabit Media Independent Interface (XGMII)....... 131
46.5.2 Identification .......................................................................................................... 131
46.5.2.3 Major capabilities/options ................................................................... 131
46.5.3 PICS proforma Tables for Reconciliation Sublayer and 10 Gigabit
Media Independent Interface ................................................................................. 131
46.5.3.3 Data stream structure ........................................................................... 131
46.5.3.3a LPI functions........................................................................................ 132
46.5.3.3b Link Interruption.................................................................................. 132
47. XGMII Extender Sublayer (XGXS) and 10 Gigabit Attachment Unit Interface (XAUI)............... 133
47.1 Overview.............................................................................................................................. 133

47.1.4 Allocation of functions .......................................................................................... 133
47.1.5 Global signal detect function ................................................................................. 133
47.1.6 Global transmit disable function............................................................................ 133
47.3 XAUI Electrical characteristics ........................................................................................... 134
47.3.3 Driver characteristics ............................................................................................. 134
47.3.3.2 Amplitude and swing ........................................................................... 134
47.3.4 Receiver characteristics ......................................................................................... 134
47.3.4.7 EEE receiver timing............................................................................. 134
XGMII Extender (XGMII) and 10 Gigabit Attachment Unit Interface (XAUI) ................. 135
47.6.4 PICS Proforma tables for XGXS and XAUI ......................................................... 135
47.6.4.4 LPI functions........................................................................................ 135
type 10GBASE-X ............................................................................................................................ 137
48.1 Overview.............................................................................................................................. 137

48.1.5 Allocation of functions .......................................................................................... 137
48.2 Physical Coding Sublayer (PCS) ......................................................................................... 137
48.2.3 Use of code-groups ................................................................................................ 137
48.2.4 Ordered_sets and special code-groups................................................................... 138
48.2.4.2 Idle (||I||) and Low Power Idle (||LPIDLE||)......................................... 139
48.2.4.2.3 Skip ||R|| ........................................................................... 140
48.2.6 Detailed functions and state diagrams ................................................................... 140
48.2.6.1 State variables ...................................................................................... 140
48.2.6.1.2 Constants.......................................................................... 140
48.2.6.1.3 Variables .......................................................................... 141
48.2.6.1.5 Counters ........................................................................... 141
48.2.6.1.5a Timers .............................................................................. 141
48.2.6.1.6 Message ........................................................................... 142
Copyright 2010 IEEE. All rights reserved. xxi
48.2.6.2
State diagrams...................................................................................... 142
48.2.6.2.2 Synchronization ............................................................... 145
48.2.6.2.3 Deskew............................................................................. 145
48.2.6.2.4 Receive............................................................................. 146
48.2.6.2.5 LPI state diagrams ........................................................... 146
48.2.6.2.6 LPI status and management ............................................. 148
48.7 Protocol implementation conformance statement (PICS) proforma for
type 10GBASE-X ................................................................................................................ 149
48.7.4 PICS proforma tables for the PCS and PMA sublayer, type 10GBASE-X ........... 149
48.7.4.5 LPI functions........................................................................................ 149
49. Physical Coding Sublayer (PCS) for 64B/66B, type 10GBASE-R ................................................. 151
49.1 Overview.............................................................................................................................. 151

49.1.5 Inter-sublayer interfaces ........................................................................................ 151
49.1.6 Functional block diagram ...................................................................................... 151
49.2.4 64B/66B transmission code ................................................................................... 152
49.2.4.4 Control codes ....................................................................................... 152
49.2.4.5 Ordered sets ......................................................................................... 152
49.2.4.7 Idle /I/ and Low Power Idle /LI/ .......................................................... 153
49.2.6 Scrambler ............................................................................................................... 153
49.2.9 Block synchronization ........................................................................................... 154
49.2.13.2.2 Variables .......................................................................... 156
49.2.13.2.3 Functions.......................................................................... 157
49.2.13.2.4 Counters ........................................................................... 159
49.2.13.2.5 Timers .............................................................................. 159
49.2.13.3 State diagrams...................................................................................... 160
49.2.13.3.1 LPI state diagrams ........................................................... 161
49.2.14.1 Status.................................................................................................... 164
Physical Coding Sublayer (PCS) type 10GBASE-R ........................................................... 165
49.3.3 Major Capabilities/Options.................................................................................... 165
49.3.6 Management........................................................................................................... 165
49.3.6.5 Auto-Negotiation for Backplane Ethernet functions ........................... 165
49.3.6.6 LPI functions........................................................................................ 166
51. Physical Medium Attachment (PMA) sublayer, type Serial............................................................ 167
51.2 PMA Service Interface......................................................................................................... 167

51.2.3 PMA_SIGNAL.indication ..................................................................................... 167
51.2.4 PMA_RXMODE.request ....................................................................................... 167
51.2.4.1 Semantics of the service primitive....................................................... 167
51.2.4.2 When generated ................................................................................... 167
51.2.4.3 Effect of receipt ................................................................................... 167
51.2.5 PMA_TXMODE.request ....................................................................................... 167
51.2.5.2 When generated ................................................................................... 167
51.2.6 PMA_ENERGY.indication.................................................................................... 168
51.2.6.2 When generated ................................................................................... 168
xxii Copyright 2010 IEEE. All rights reserved.
51.4 Sixteen-Bit Interface (XSBI) ............................................................................................... 168
51.4.2 Optional Signals..................................................................................................... 170
Physical Medium Attachment (PMA) sublayer, type Serial................................................ 170
55. Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and
baseband medium, type 10GBASE-T.............................................................................................. 171
55.1 Overview.............................................................................................................................. 171

55.1.1 Objectives .............................................................................................................. 171
55.1.3 Operation of 10GBASE-T ..................................................................................... 171
55.1.3.2 Physical Medium Attachment (PMA) sublayer................................... 173
55.1.3.3 EEE capability ..................................................................................... 173
55.1.4 Signaling ................................................................................................................ 174
55.2 10GBASE-T service primitives and interfaces.................................................................... 174
55.2.2 PMA service interface ........................................................................................... 174
55.2.2.3 PMA_UNITDATA.request.................................................................. 175
55.2.2.3.1 Semantics of the primitive ............................................... 175
55.2.2.8 PMA REMRX_STATUS.request ........................................................ 176
55.2.2.9 PMA_ALERTDETECT.indication...................................................... 176
55.2.2.9.2 When generated ............................................................... 176
55.2.2.9.3 Effect of receipt ............................................................... 176
55.2.2.10 PCS_RX_LPI_STATUS.request ......................................................... 176
55.2.2.10.2 When generated ............................................................... 177
55.2.2.11 PMA_PCSDATAMODE.indication.................................................... 177
55.2.2.11.2 When generated ............................................................... 177
55.2.2.12 PMA_FR_ACTIVE.indication ............................................................ 177
55.2.2.12.2 When generated ............................................................... 177
55.3.2 PCS Functions........................................................................................................ 178
55.3.2.2 PCS Transmit function......................................................................... 178
55.3.2.2.1 Use of blocks ................................................................... 179
55.3.2.2.9 Idle (/I/) ............................................................................ 180
55.3.2.2.9a LPI (/LI/).......................................................................... 181
55.3.2.2.20 65B-LDPC framer............................................................ 181
55.3.2.2.21 EEE capability ................................................................. 181
55.3.2.3 PCS Receive function .......................................................................... 182
55.3.4 PMA training side-stream scrambler polynomials ................................................ 183
55.3.4a LPI signaling.......................................................................................................... 183
55.3.4a.1 LPI Synchronization ............................................................................ 183
55.3.4a.2 Quiet period signaling.......................................................................... 185
55.3.4a.3 Refresh period signaling ...................................................................... 185
55.3.5 Detailed functions and state diagrams ................................................................... 186
55.3.5.2 State diagram parameters..................................................................... 186
55.3.5.2.1 Constants.......................................................................... 186
Copyright 2010 IEEE. All rights reserved. xxiii
55.3.5.2.2 Variables .......................................................................... 186
55.3.5.2.3 Timers .............................................................................. 188
55.3.5.2.4 Functions.......................................................................... 188
55.3.5.2.5 Counters ........................................................................... 189
55.3.5.4 State diagrams...................................................................................... 190
55.3.6 PCS management ................................................................................................... 197
55.3.6.1 Status.................................................................................................... 197
55.4 Physical Medium Attachment (PMA) sublayer................................................................... 197
55.4.1 PMA functional specifications............................................................................... 197
55.4.2 PMA functions ....................................................................................................... 198
55.4.2.2 PMA Transmit function ....................................................................... 198
55.4.2.2.1 Alert signal....................................................................... 199
55.4.2.2.2 Link failure signal............................................................ 200
55.4.2.4 PMA Receive function......................................................................... 200
55.4.2.5 PHY Control function.......................................................................... 201
55.4.2.5.14 Startup sequence .............................................................. 201
55.4.2.5.15 Fast retrain function ......................................................... 201
55.4.2.6 Link Monitor function ......................................................................... 202
55.4.2.6a Refresh Monitor function..................................................................... 202
55.4.4 Automatic MDI/MDI-X configuration .................................................................. 202
55.4.5 State variables ........................................................................................................ 202
55.4.5.1 State diagram variables ........................................................................ 202
55.4.5.2 Timers .................................................................................................. 204
55.4.5.4 Counters ............................................................................................... 204
55.4.6 State diagrams........................................................................................................ 205
55.4.6.1 PHY Control state diagram.................................................................. 205
55.4.6.2 Transition counter state diagrams ........................................................ 206
55.4.6.3 Link Monitor state diagram ................................................................. 207
55.4.6.4 EEE Refresh monitor state diagram..................................................... 208
55.4.6.5 Fast retrain state diagram ..................................................................... 209
55.5 PMA electrical specifications .............................................................................................. 209
55.5.3 Transmitter electrical specifications ...................................................................... 209
55.5.3.5 Transmit clock frequency .................................................................... 209
55.6 Management interfaces ........................................................................................................ 209
55.6.1 Support for Auto-Negotiation ................................................................................ 209
55.6.1.2 10GBASE-T Auto-Negotiation page use ............................................ 210
55.10 PHY labeling........................................................................................................................ 210
Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA) sublayer and
baseband medium, type 10GBASE-T.............................................................................. 211
55.12.3 Physical Coding Sublayer (PCS) ........................................................................... 211
55.12.4 Physical Medium Attachment (PMA) ................................................................... 213
55.12.5 Management interface............................................................................................ 213
55.12.6 PMA Electrical Specifications............................................................................... 214
69. Introduction to Ethernet operation over electrical backplanes ........................................................ 215
69.1 Overview.............................................................................................................................. 215

69.1.1 Scope...................................................................................................................... 215
69.1.2 Objectives .............................................................................................................. 215
69.2 Summary of Backplane Ethernet Sublayers ........................................................................ 215
69.2.3 Physical Layer signaling systems .......................................................................... 215
69.2.6 Low-Power Idle ..................................................................................................... 216
xxiv Copyright 2010 IEEE. All rights reserved.
70. Physical Medium Dependent Sublayer and Baseband Medium, Type 1000BASE-KX ................. 217
70.1 Overview.............................................................................................................................. 217

70.2 Physical Medium Dependent (PMD) service interface ....................................................... 217
70.2.1 PMD_RXQUIET.request....................................................................................... 217
70.2.1.2 When generated ................................................................................... 218
70.2.2 PMD_TXQUIET.request ....................................................................................... 218
70.2.2.2 When generated ................................................................................... 218
70.6 PMD functional specifications............................................................................................. 218
70.6.4 PMD signal detect function ................................................................................... 218
70.6.5 PMD transmit disable function .............................................................................. 219
70.6.10 PMD LPI function ................................................................................................. 219
70.7 1000BASE-KX electrical characteristics............................................................................. 219
70.7.1 Transmitter characteristics ..................................................................................... 219
70.7.1.5 Output amplitude ................................................................................. 220
Physical Medium Dependent (PMD) sublayer and baseband medium,
type 1000BASE-KX ............................................................................................................ 221
70.10.4 PICS proforma tables for Clause 70, Physical Medium Dependent (PMD)
sublayer and baseband medium, type 1000BASE-KX .......................................... 221
70.10.4.1 PMD functional specifications............................................................. 221
70.10.4.3 Transmitter electrical characteristics ................................................... 222
71. Physical Medium Dependent Sublayer and Baseband Medium, Type 10GBASE-KX4 ................ 223
71.1 Overview.............................................................................................................................. 223

71.2.1 PMD_RXQUIET.request....................................................................................... 223
71.2.1.2 When generated ................................................................................... 224
71.2.2 PMD_TXQUIET.request ....................................................................................... 224
71.2.2.2 When generated ................................................................................... 224
71.6.4 Global PMD signal detect function ....................................................................... 224
71.6.6 Global PMD transmit disable function .................................................................. 225
71.6.12 PMD LPI function ................................................................................................. 225
71.7 Electrical characteristics for 10GBASE-KX4 ..................................................................... 225
71.7.1.4 Output amplitude ................................................................................. 226
71.7.2 Receiver characteristics ......................................................................................... 226
type 10GBASE-KX4 ........................................................................................................... 227
sublayer and baseband medium, type 10GBASE-KX4 ......................................... 228
Copyright 2010 IEEE. All rights reserved. xxv
72. Physical Medium Dependent Sublayer and Baseband Medium, Type 10GBASE-KR................... 229
72.1 Overview.............................................................................................................................. 229

72.2.1 PMD_RX_MODE.request ..................................................................................... 229
72.2.1.2 When generated ................................................................................... 230
72.2.2 PMD_TX_MODE.request ..................................................................................... 230
72.2.2.2 When generated ................................................................................... 230
72.6.2 PMD transmit function .......................................................................................... 230
72.6.4 PMD signal detect function ................................................................................... 231
72.6.5 PMD transmit disable function .............................................................................. 231
72.6.10 PMD control function ............................................................................................ 231
72.6.10.1 Overview.............................................................................................. 231
72.6.11. PMD LPI function ............................................................................... 232
72.7 10GBASE-KR electrical characteristics .............................................................................. 232
72.7.1.4 Output Amplitude ................................................................................ 233
type 10GBASE-KR.............................................................................................................. 233
sublayer and baseband medium, type 10GBASE-KR ........................................... 233
73. Auto-Negotiation for Backplane Ethernet ....................................................................................... 235
Auto-Negotiation for Backplane Ethernet ........................................................................... 235
73.11.4 PICS proforma tables for Auto-Negotiation for Backplane Ethernet.................... 235
73.11.4.9 Auto-Negotiation annexes ................................................................... 235
74. Forward Error Correction (FEC) sublayer for BASE-R PHYs ....................................................... 237
74.4 Inter-sublayer interfaces ...................................................................................................... 237

74.4.1 Functional Block Diagram for 10GBASE-R PHYs .............................................. 237
74.5 FEC service interface........................................................................................................... 238
74.5.1 10GBASE-R Service primitives ............................................................................ 238
74.5.1.3 FEC_SIGNAL.indication .................................................................... 238
74.5.1.4 FEC_ENERGY.indication (optional) .................................................. 238
74.5.1.5 FEC_LPI_ACTIVE.request (optional) ................................................ 238
74.5.1.5.1 When generated ............................................................... 238
74.5.1.6 FEC_RX_MODE.request (optional) ................................................... 239
xxvi Copyright 2010 IEEE. All rights reserved.
74.5.1.6.1 When generated ............................................................... 239
74.5.1.7 FEC_TX_MODE.request (optional).................................................... 239
74.5.1.7.1 When generated ............................................................... 239
74.7 FEC principle of operation .................................................................................................. 239
74.7.4 Functions within FEC sublayer.............................................................................. 239
74.7.4.7 FEC block synchronization.................................................................. 239
74.7.4.8 FEC rapid block synchronization for EEE (optional).......................... 239
74.8 FEC MDIO function mapping ............................................................................................. 240
74.8.4 FEC Error monitoring capability ........................................................................... 240
74.10 Detailed functions and state diagrams ................................................................................. 240
74.10.2 State variables ........................................................................................................ 240
74.10.2.3 Functions.............................................................................................. 240
Forward Error Correction (FEC) sublayer for BASE-R PHYs ........................................... 241
74.11.6 FEC Error Monitoring ........................................................................................... 241
78. Energy-Efficient Ethernet (EEE) ..................................................................................................... 243
78.1 Overview.............................................................................................................................. 243

78.1.1 LPI Signaling ......................................................................................................... 243
78.1.1.1 Interlayer service interfaces ................................................................. 244
78.1.1.2 Responsibilities of LPI Client.............................................................. 244
78.1.2 LPI Client service interface ................................................................................... 244
78.1.2.1 LP_IDLE.request ................................................................................. 244
78.1.2.1.1 Function ........................................................................... 244
78.1.2.1.2 Semantics of the service primitive................................... 245
78.1.2.1.3 When generated ............................................................... 245
78.1.2.2 LP_IDLE.indication............................................................................. 245
78.1.2.2.1 Function ........................................................................... 245
78.1.2.2.2 Semantics of the service primitive................................... 245
78.1.2.2.3 When generated ............................................................... 245
78.1.3 Reconciliation sublayer operation ......................................................................... 246
78.1.3.1 RS LPI assert function ......................................................................... 246
78.1.3.2 LPI detect function............................................................................... 247
78.1.3.3 PHY LPI operation .............................................................................. 247
78.1.3.3.1 PHY LPI transmit operation ............................................ 247
78.1.3.3.2 PHY LPI receive operation.............................................. 248
78.1.4 EEE Supported PHY types .................................................................................... 248
78.2 LPI mode timing parameters description............................................................................. 248
78.3 Capabilities Negotiation ...................................................................................................... 249
78.4 Data Link Layer Capabilities ............................................................................................... 250
78.4.1 Data Link Layer capabilities timing requirements ................................................ 251
78.4.2 Control state diagrams ........................................................................................... 251
78.4.2.1 Conventions ......................................................................................... 251
78.4.2.2 Constants.............................................................................................. 251
78.4.2.3 Variables .............................................................................................. 251
78.4.2.4 Functions.............................................................................................. 253
78.4.2.5 State diagrams...................................................................................... 254
78.4.3 State change procedure across a link ..................................................................... 256
Copyright 2010 IEEE. All rights reserved. xxvii
78.4.3.1 Transmitting link partners state change procedure across a link........ 257
78.4.3.2 Receiving link partners state change procedure across a link ............ 257
78.5 Communication link access latency..................................................................................... 258
78.5.1 10 Gb/s PHY extension using XGXS .................................................................... 259
EEE Data Link Layer Capabilities....................................................................................... 259
78.6.1 Introduction............................................................................................................ 259
78.6.2 Identification .......................................................................................................... 260
78.6.2.1 Implementation identification.............................................................. 260
78.6.2.2 Protocol summary ................................................................................ 260
78.6.4 DLL requirements.................................................................................................. 261
79. IEEE 802.3 Organizationally Specific Link Layer Discovery Protocol (LLDP) type, length,
and values (TLV) information elements ......................................................................................... 263
79.3 IEEE 802.3 Organizationally Specific TLVs ...................................................................... 263

79.3.5 EEE TLV ............................................................................................................... 263
79.3.5.1 Transmit Tw......................................................................................... 264
79.3.5.2 Receive Tw .......................................................................................... 264
79.3.5.3 Fallback Tw ......................................................................................... 264
79.3.5.4 Echo Transmit and Receive Tw........................................................... 264
79.3.5.5 EEE TLV usage rules .......................................................................... 264
79.4 IEEE 802.3 Organizationally Specific TLV selection management ................................... 264
79.4.2 IEEE 802.3 Organizationally Specific TLV/LLDP Local and Remote System
group managed object class cross references ........................................................ 264
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..................................................................................... 266
79.5a EEE TLV ............................................................................................................... 266
Annex 28C (normative) Next page Message Code field definitions ........................................................... 267
28C.12 Message code 10EEE technology message code ....................................................... 267
Annex 28D (normative) Description of extensions to Clause 28 and associated annexes .......................... 268
28D.7 Extensions required for Energy-Efficient Ethernet (Clause 78) ...................................... 268
Annex 73A (normative) Next page Message Code field definitions........................................................... 269
73A.4 Message code 10EEE technology message code......................................................... 269
Annex 74A (informative) FEC block coding examples .............................................................................. 271
74A.4 Output of the PN-2112 sequence generator ..................................................................... 271
xxviii Copyright 2010 IEEE. All rights reserved.
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
IMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, or
environmental protection. Implementers of the standard are responsible for determining appropriate
safety, security, environmental, and health practices or regulatory requirements.
This IEEE document is made available for use subject to important notices and legal disclaimers. These
notices and disclaimers appear in all publications containing this document and may be found under the
heading Important Notice or Important Notices and Disclaimers Concerning IEEE Documents.
They can also be obtained on request from IEEE or viewed at http://standards.ieee.org/IPR/
disclaimers.html.
(This amendment is based on IEEE Std 802.3-2008.)
NOTEThe editing instructions contained in this amendment define how to merge the material contained therein into
the existing base standard and its amendments to form the comprehensive standard.1
The editing instructions are shown in bold italic. Four editing instructions are used: change, delete, insert,
and replace. Change is used to make corrections in existing text or tables. The editing instruction specifies
the location of the change and describes what is being changed by using strikethrough (to remove old
material) and underscore (to add new material). Delete removes existing material. Insert adds new material
without disturbing the existing material. Insertions may require renumbering. If so, renumbering instructions
are given in the editing instruction. Replace is used to make changes in figures or equations by removing the
existing figure or equation and replacing it with a new one. Editing instructions, change markings, and this
NOTE will not be carried over into future editions because the changes will be incorporated into the base
standard.
1
Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the standard.
Copyright 2010 IEEE. All rights reserved. 1
IEEE Std 802.3az-2010 AMENDMENT TO IEEE Std 802.3-2008: CSMA/CD
1. Introduction
1.4 Definitions
Insert the following new definitions into the definitions list, in alphanumeric order, as follows:
10BASE-Te: IEEE 802.3 Physical Layer specification for an energy-efficient version of 10BASE-T for a
10 Mb/s CSMA/CD local area network over two pairs of Category 5 or better-balanced cabling. (See
IEEE Std 802.3, Clause 14.)
Low Power Idle (LPI) mode: An optional mode intended to save power that may be enabled during periods
of low link utilization in which either side of a link may disable portions of device or system functionality.
1.5 Abbreviations
Insert the following new abbreviations into the abbreviations list, in alphabetical order, as follows:
EEE Energy-Efficient Ethernet
LPI Low Power Idle
2 Copyright 2010 IEEE. All rights reserved.
AMENDMENT TO IEEE Std 802.3-2008: CSMA/CD IEEE Std 802.3az-2010
Change the clause heading as follows:
14.Twisted-pair medium attachment unit (MAU) and baseband medium,

type 10BASE-T including type 10BASE-Te
14.1 Scope
14.1.1 Overview
Change the first paragraph of 14.1.1 as follows and insert a NOTE after the first paragraph:
Clause 14 defines the functional, electrical, and mechanical characteristics of the type 10BASE-T MAU and
one specific medium for use with that MAU. This clause also specifies the functional, electrical, and
mechanical characteristics of the energy-efficient version of 10BASE-T, the type 10BASE-Te MAU, and
one specific medium for use with that MAU. The relationship of this clause to the entire ISO/IEC
8802-3IEEE 802.3 LAN International Standard is shown in Figure 141. The purpose of the MAU is to
provide a simple, inexpensive, and flexible means of attaching devices to the medium.
NOTESupport for both 10BASE-T and 10BASE-Te signal levels in a single device is not required.
This MAU and medium specification is aimed primarily at office applications where twisted-pair cable is
often installed. Installation and reconfiguration simplicity is allowed by the type of cable and connectors
used.
The 10BASE-T specification builds upon Clause 1 through Clause 7 and Clause 9 of this standard.
14.1.1.1 Medium Attachment Unit (MAU)
Insert items i) and j) into the lettered list of general characteristics in 14.1.1.1 as follows:
The MAU has the following general characteristics:
a) Enables coupling the Physical Signaling (PLS) sublayer by way of the Attachment Unit Interface
(AUI) to the baseband twisted-pair link defined in Clause 14.
b) Supports message traffic at a data rate of 10 Mb/s.
c) Provides for operating over 0 m to at least 100 m of twisted pair without the use of a repeater.
d) Permits the Data Terminal Equipment (DTE) or repeater to confirm operation of the MAU and avail-
ability of the medium.
e) Supports network configurations using the CSMA/CD access method defined in this standard with
baseband signaling.
f) Supports a point-to-point interconnection between MAUs and, when used with repeaters having
multiple ports, supports a star wiring topology.
g) Allows incorporation of the MAU within the physical bounds of a DTE or repeater.
h) Allows for either half duplex operation, full duplex operation, or both.
i) Provides for operation with reduced peak differential voltage on the TD circuit for type 10BASE-Te.
A 10BASE-Te MAU interoperates with a 10BASE-T MAU if the minimum cabling requirements of
a 10BASE-Te MAU are met.
j) All references to 10BASE-T include 10BASE-Te unless otherwise stated.
14.1.1.3 Twisted-pair media
Change the first paragraph of 14.1.1.3 as follows:
The medium for 10BASE-T is twisted-pair wire. The performance specifications of the 10BASE-T except
10BASE-Te simplex link segment are contained in 14.4. This wiring normally consists of 0.4 mm to 0.6 mm
diameter [26 AWG to 22 AWG] unshielded wire in a multipair cable. The performance specifications are
generally met by 100 m of 0.5 mm telephone twisted pair. Longer lengths are permitted providing the
simplex link segment meets the requirements of 14.4. A length of 100 m, the design objective, will be used
when referring to the length of a twisted-pair link segment.
Insert the following paragraph and NOTE in 14.1.1.3 after the first paragraph:
The medium for 10BASE-Te is twisted-pair wire. The performance specifications of the 10BASE-Te
simplex link segment (either pure 10BASE-Te or mixed 10BASE-T, 10BASE-Te) is a channel meeting or
exceeding the requirements of the Class D channel specified by ISO/IEC 11801:1995. These channel
requirements can also be met by the Category 5 channel specified by ANSI/TIA/EIA-568-B:2001.
NOTEISO/IEC 11801:2002 provides a specification for media that exceeds the minimum requirements of this
standard.
14.3.1 MAU-to-MDI interface characteristics
14.3.1.2 Transmitter specifications
Change the third paragraph of 14.3.1.2 as follows:
Some tests in this subclause require the use of an equivalent circuit that models the distortion introduced by
a simplex link segment. This twisted-pair model shall be constructed according to Figure 147 for a type
10BASE-T MAU that is not a type 10BASE-Te MAU and according to Figure 147a for a type 10BASE-Te
MAU with component tolerances as follows: Resistors, 1%; capacitors, 5%; inductors, 10%.
Component tolerance specifications shall be met from 5.0 MHz to 15 MHz. For all measurements, the TD
circuit shall be connected through a balun to section 1 and the signal measured across a load connected to
section 4 of the model. The balun shall not affect the peak differential output voltage specified in 14.3.1.2.1
by more than 1% when inserted between the 100 resistive load and the TD circuit. Also, the value of the
resistor that is in series with the inductors includes the series resistance of the inductor itself. The actual
value of the resistor that is used is computed by subtracting the series resistance of the inductor from the
resistor value shown in the figure.
The For a type 10BASE-T MAU that is not a type 10BASE-Te MAU, the insertion loss of the twisted-pair
model when measured with a 100 source and 100 load shall be between 9.70 dB and 10.45 dB at
10 MHz, and between 6.50 dB and 7.05 dB at 5 MHz.
Insert the following paragraph and Figure 147a (showing new twisted-pair model) after Figure 147 as
follows:
For a type 10BASE-Te MAU, the insertion loss of the twisted-pair model when measured with a 100
source and 100 load shall be between 6.8 dB and 7.4 dB at 10 MHz, and between 4.75 dB and 5.25 dB at
5 MHz.
Section 1 Section 2 Section 3 Section 4
133 2.32 K 14 K 22.6 K
5.6 0.68 0.82 0.82

14 1.0 1.0 1.0
95.3 95.3 95.3 95.3 95.3 95.3 95.3 95.3
68.1 3.83 1.0 0
560 649 68 11.3 K 82 10 K 82 11.8 K
NOTE: Care must be taken that layout and parasitics Resistances are in :
do not exceed R, C, and L tolerance values. Capacitances are in pF
Inductances are in PH
Figure 147Twisted-pair model for 10BASE-T
Section 1 Section 4
84.5 511
2.7 1.0
17.01 15.96
100 100 100 100
118 19.6
270 590 100 619
NOTECare must be taken that layout and parasitics Resistances are in

do not exceed R, C, and L tolerance values. Capacitances are in pF
Inductances are in H
Figure 147aTwisted-pair model for 10BASE-Te
14.3.1.2.1 Differential output voltage
Some of the text and figures of this subclause describe the differential voltage in terms of magnitudes. These
requirements apply to negative as well as positive pulses.
Change the second and third paragraphs of 14.3.1.2.1 as follows:
The peak differential voltage on the TD circuit when terminated with a 100 resistive load shall be between
2.2 V and 2.8 V for all data sequences for a type 10BASE-T MAU that is not a type 10BASE-Te MAU. For
a type 10BASE-Te MAU, the peak differential voltage on the TD circuit when terminated with a 100
resistive load shall be between 1.54 V and 1.96 V for all data sequences. When the DO circuit is driven by
an all-ones Manchester-encoded signal, any harmonic measured on the TD circuit shall be at least 27 dB
below the fundamental.
NOTEThe specification on maximum spectral components is not intended to ensure compliance with regulations
concerning RF emissions. The implementor should consider any applicable local, national, or international regulations.
Additional filtering of spectral components may therefore be necessary.
The output signal Vo, is defined at the output of the twisted-pair model as shown in Figure 14-8. The specific
twisted-pair model used in Figure 148 shall be the equivalent circuit shown in Figure 147 for 10BASE-T
except 10BASE-Te and shall be the equivalent circuit shown in Figure 147a for 10BASE-Te. The TD
transmitter shall provide equalization such that the output waveform shall fall within the template shown in
Figure 149 for all data sequences. Voltage and time coordinates for inflection points on Figure 149 are
given in Table 141. (Zero crossing points are different for external and internal MAUs. The zero crossings
depicted in Figure 149 apply to an external MAU.) The template voltage may be scaled by a factor of 0.9 to
1.1 but any scaling below 0.9 or above 1.1 shall not be allowed. The recommended measurement procedure
is described in B.4.3.1. Time t = 0 on the template represents a zero crossing, with positive slope, of the
output waveform. During this test the twisted-pair model shall be terminated in 100 and driven by a
transmitter with a Manchester-encoded pseudo-random sequence with a minimum repetition period of
511 bits.
Change the fifth, sixth, and seventh paragraphs of 14.3.1.2.1 as follows:
The TP_IDL shall always start with a positive waveform when a waveform conforming to Figure 7-12 is
applied to the DO circuit. If the last bit transmitted was a CD1, the last transition will be at the bit cell center
of the CD1. If the last bit transmitted was a CD0, the PLS will generate an additional transition at the bit cell
boundary following the CD0. After the zero crossing of the last transition, the differential voltage shall
remain within the shaded area of Figure 1410. Once the differential voltage has gone more negative than
50 mV, it shall not exceed +50 mV. The template requirements of Figure 1410 shall be met when
measured across each of the test loads defined in Figure 1411, both with the load connected directly to the
TD circuit and with the load connected through the twisted-pair model as defined in Figure 147
and Figure 148 for 10BASE-T except 10BASE-Te, and Figure 147a and Figure 148 for 10BASE-Te.
The link test pulse shall be a single positive (TD+ lead positive with respect to TD lead) pulse, which falls within
the shaded area of Figure 1412. Once the differential output voltage has become more negative than 50 mV, it
shall remain less than +50 mV. The template requirements of Figure 1412 shall be met when measured across
each of the test loads defined in Figure 1411; both with the load connected directly to the TD circuit and with the
load connected through the twisted-pair model as defined in Figure 147 and Figure 148 for 10BASE-T
except 10BASE-Te, and Figure 147a and Figure 148 for 10BASE-Te.
For a MAU that implements the Auto-Negotiation algorithm defined in Clause 28, the FLP Burst Sequence
will consist of multiple link test pulses. All link test pulses in the FLP Burst sequence shall meet the
template requirements of Figure 1412 when measured across each of the test loads defined in Figure 1411;
both with the load connected directly to the TD circuit and with the load connected through the twisted-pair
model as defined in Figure 147 and Figure 148 for 10BASE-T except 10BASE-Te, and Figure 147a
and Figure 148 for 10BASE-Te.
14.4 Characteristics of the simplex link segment
14.4.1 Overview
Change the first paragraph of 14.4.1 as follows:
The medium for 10BASE-T is twisted-pair wiring. Since aA significant number of 10BASE-T networks are
expected to be installed utilizing in-place unshielded telephone wiring and typical telephony installation
practices, the end-to-end path including different types of wiring, cable connectors, and cross connects must
be considered. Typically, a DTE connects to a wall outlet using a twisted-pair patch cord. Wall outlets
connect through building wiring and a cross connect to the repeater MAU in a wiring closet.
Insert a new paragraph after the first paragraph of 14.4.1, before the NOTE, as follows:
The medium for 10BASE-Te is twisted-pair wire. The requirements of the 10BASE-Te simplex link
segment (either pure 10BASE-Te or mixed 10BASE-T, 10BASE-Te) are equivalent to the requirements of
the Class D channel specified by ISO/IEC 11801:1995. This requirement can also be met by Category 5
cable and components as specified in ANSI/TIA/EIA-568-B:2001.
14.4.2 Transmission parameters
14.4.2.1 Insertion loss
The insertion loss of a simplex link segment shall be no more than 11.5 dB at all frequencies between
5.0 MHz and 10 MHz for a 10BASE-T MAU that is not a 10BASE-Te MAU. For a 10BASE-Te MAU, the
insertion loss of a simplex link segment shall be no more than 8.5 dB at all frequencies between 5.0 MHz
and 10 MHz. This consists of the attenuation of the twisted pairs, connector losses, and reflection losses due
to impedance mismatches between the various components of the simplex link segment. The insertion loss
specification shall be met when the simplex link segment is terminated in source and load impedances that
satisfy 14.3.1.2.2 and 14.3.1.3.4.
14.5 MDI specification
14.5.2 Crossover function
Change the last sentence of the first paragraph of 14.5.2 as follows:
Additionally, the MDI connector for a MAU that implements the a fixed crossover function shall be marked
with the graphical symbol X. Internal and external crossover functions are shown in Figure 1422.
14.8 MAU labeling
Change lettered list items c) and d) and insert a new item e) as follows:
It is recommended that each MAU (and supporting documentation) be labeled in a manner visible to the user
with at least these parameters:
a) Data rate capability in Mb/s,

b) Power level in terms of maximum current drain (for external MAUs),
c) Any applicable safety warnings, and
d) Duplex capabilities., and

e) Which of the two specifications is implemented, i.e., 10BASE-T or 10BASE-Te (not both).
Change the title of 14.10 as follows:

Clause 14, twisted-pair medium attachment unit (MAU) and baseband medium,
type 10BASE-T and type 10BASE-Te2
14.10.3 Identification of the protocol
Change the first row of the table in 14.10.3 as follows:
IEEE Std 802.3-2008, Clause 14, Twisted-pair medium attachment unit (MAU) Y[] N[]
and baseband medium, type 10BASE-T except type 10BASE-Te
Insert the following text in the table after the first row:
IEEE Std 802.3-2008, Clause 14, Twisted-pair medium attachment unit (MAU) Y[] N[]
and baseband medium, type 10BASE-Te
14.10.4 PICS proforma for 10BASE-T
14.10.4.5 PICS proforma tables for MAU
14.10.4.5.12 Transmitter specification
Change TS1 and insert TS2 into the table, renumbering subsequent entries in the PICS, as follows:
Parameter Subclause Req Imp Value/Comment
TS1 Peak differential output 14.3.1.2.1 CM Conditional on whether it is a type

voltage on TD circuit for a 10BASE-T MAU that is not a type
type 10BASE-T MAU that 10BASE-Te MAU, 2.2 to 2.8 V
is not a type 10BASE-Te
MAU
TS2 Peak differential output 14.3.1.2.1 C Conditional on whether it is a type

voltage on TD circuit for a 10BASE-Te MAU, 1.54 to 1.96 V
type 10BASE-Te MAU
2
Copyright release for PICS proformas: Users of this standard may freely reproduce the PICS proforma in this subclause so that it can
be used for its intended purpose and may further publish the completed PICS.
14.10.4.7 PICS proforma tables for 10BASE-T link segment
14.10.4.7.1 10BASE-T link segment characteristics
Change LS4 and insert LS5 into the table, renumbering the subsequent entries in the PICS, as follows:
Parameter Subclause Req Imp Value/Comment
LS4 Insertion loss, 5.0 to 14.4.2.1 CM Conditional on whether it is a type

10 MHz for a type 10BASE-T MAU that is not a type
10BASE-T MAU that is 10BASE-Te MAU, 11.5 dB
not a type 10BASE-Te
MAU
LS5 Insertion loss, 5.0 to 14.4.2.1 C Conditional on whether it is a type

10 MHz for a type 10BASE-Te MAU, 8.5 dB
10BASE-Te MAU
22. Reconciliation Sublayer (RS) and Media Independent Interface (MII)
22.2 Functional specifications
Change 22.2.1 for LPI function as follows:
22.2.1 Mapping of MII signals to PLS service primitives and Station Management
The Reconciliation sublayer maps the signals provided at the MII to the PLS service primitives defined in
Clause 6. The PLS service primitives provided by the Reconciliation sublayer behave in exactly the same
manner as defined in Clause 6. The MII signals are defined in detail in 22.2.2. The mapping is changed if
EEE capability is supported (see 78.3), as described in 22.6a. EEE capability requires the use of the MAC
defined in Annex 4A for simplified full duplex operation (with carrier sense deferral). This provides full
duplex operation but uses the carrier sense signal to defer transmission when the PHY is in its low power
state.
Figure 223 depicts a schematic view of the Reconciliation sublayer inputs and outputs, and demonstrates
that the MII management interface is controlled by the station management entity (STA).
PLS_Service Primitives Reconciliation sublayer MII Signals
TX_ER
TXD<3:0>
PLS_DATA.request
TX_EN
TX_CLK
PLS_SIGNAL.indication COL
RXD<3:0>
PLS_DATA.indication RX_ER
RX_CLK
PLS_CARRIER.indication CRS
PLS_DATA_VALID.indication RX_DV
Station Management
MDC
MDIO
Figure 223Reconciliation Sublayer (RS) inputs and outputs,

and STA connections to MII
22.2.1.3 Mapping of PLS_CARRIER.indication
Change 22.2.1.3.1 and 22.2.1.3.2 as follows:
22.2.1.3.1 Semantics of the service primitive
PLS_CARRIER.indication (CARRIER_STATUS)
The CARRIER_STATUS parameter can take one of two values: CARRIER_ON or CARRIER_OFF. The
values CARRIER_ON and CARRIER_OFF are derived from the MII signal CRS, and the LPI assert
function if the EEE capability supported (see 22.6a.2).
22.2.1.3.2 When generated
The PLS_CARRIER.indication service primitive is generated by the Reconciliation sublayer whenever the
CARRIER_STATUS parameter changes from CARRIER_ON to CARRIER_OFF or vice versa.
While the RX_DV signal is de-asserted, any transition of the CRS signal from de-asserted to asserted must
cause a transition of CARRIER_STATUS from the CARRIER_OFF to the CARRIER_ON value, and any
transition of the CRS signal from asserted to de-asserted must cause a transition of CARRIER_STATUS
from the CARRIER_ON to the CARRIER_OFF value. Any transition of the CRS signal from de-asserted to
asserted must cause a transition of CARRIER_STATUS from the CARRIER_OFF to the CARRIER_ON
value, and any transition of the CRS signal from asserted to de-asserted must cause a transition of
CARRIER_STATUS from the CARRIER_ON to the CARRIER_OFF value.
NOTEThe behavior of the CRS signal is specified within this clause so that it can be mapped directly (with the
appropriate implementation-specific synchronization) to the carrierSense variable in the MAC process Deference, which
is described in 4.2.8. The behavior of the RX_DV signal is specified within this clause so that it can be mapped directly
to the receiveDataValid variable in the MAC process BitReceiver, which is described in 4.2.9, provided that the MAC
processBitReceiver is implemented to receive a nibble of data on each cycle through the inner loop.
For EEE capability, CARRIER_STATUS is overridden according to the behavior of the LPI transmit state
diagram (see Figure 2219b). The signal CRS has no effect on CARRIER_STATUS while in states
LPI_ASSERTED and LPI_WAIT. A transition to the LPI_ASSERTED state in the transmit LPI state
diagram shall cause a transition of CARRIER_STATUS from the CARRIER_OFF to the CARRIER_ON
value, and a transition to the LPI_DEASSERTED state in the transmit LPI state diagram shall cause a
transition of CARRIER_STATUS from the CARRIER_ON to the CARRIER_OFF value.
22.2.2 MII signal functional specifications
Change the last paragraph of 22.2.2.2 and NOTE as follows:
22.2.2.2 RX_CLK (receive clock)
Transitions from nominal clock to recovered clock or from recovered clock to nominal clock shall be made
only while RX_DV is de-asserted. During the interval between the assertion of CRS and the assertion of
RX_DV at the beginning of a frame, the PHY may extend a cycle of RX_CLK by holding it in either the
high or low condition until the PHY has successfully locked onto the recovered clock. Following the de-
assertion of RX_DV at the end of a frame or while the PHY is asserting LPI, the PHY may extend a cycle of
RX_CLK by holding it in either the high or low condition for an interval that shall not exceed twice the
nominal clock period. For EEE capability, RX_CLK may be stopped by the PHY during LPI when the Clock
stop enable bit is asserted (see 22.2.2.8a and 45.2.3.1.3a).
NOTEThis standard neither requires nor assumes a guaranteed phase relationship between the RX_CLK and
TX_CLK signals. See additional information in 22.2.4.1.5 and 22.2.2.8a.
Change 22.2.2.4 for TXD definition as follows:
22.2.2.4 TXD (transmit data)
TXD is a bundle of 4 data signals (TXD<3:0>) that are driven by the Reconciliation sublayer. TXD<3:0>
shall transition synchronously with respect to the TX_CLK. For each TX_CLK period in which TX_EN is
asserted, TXD<3:0> are accepted for transmission by the PHY. TXD<0 >is the least significant bit. While
TX_EN and TX_ER are both is de-asserted, TXD<3:0> shall have no effect upon the PHY.
For EEE capability, the RS shall use the combination of TX_EN de-asserted, TX_ER asserted, and
TXD<3:0> equal to 0001 as shown in Table 221 as a request to enter, or remain in a low power state. Other
values of TXD<3:0> with this combination of TX_EN and TX_ER shall have no effect upon the PHY.
Figure 224 depicts TXD<3:0> behavior during the transmission of a frame.
Table 221 summarizes the permissible encodings of TXD<3:0>, TX_EN, and TX_ER.
Table 221Permissible encodings of TXD<3:0>, TX_EN, and TX_ER
TX_EN TX_ER TXD<3:0> Indication
0 0 0000 through 1111 Normal interframe
0 1 0000 through 1111 Reserved
0 1 0000 Reserved
0 1 0001 Assert LPI
1 0 0000 through 1111 Normal data transmission
1 1 0000 through 1111 Transmit error propagation
22.2.2.5 TX/ER (transmit coding error)
Insert a new subclause 22.2.2.5a after 22.2.2.5 as follows:
22.2.2.5a Transmit direction LPI transition
When the transmit LPI state diagram is in state LPI_ASSERTED, the LPI client requests the PHY to
transition to the LPI state by de-asserting TX_EN, asserting TX_ER, and setting TXD<3:0> to 0001. The
LPI client maintains the same state for these signals for the entire time that the PHY is to remain in the LPI
state.
The LPI client requests the PHY to transition out of the LPI state by de-asserting TX_ER and TXD. The LPI
client should not assert TX_EN for valid transmit data until after the resolved wake up time specified for the
PHY.
Figure 226a shows the behavior of TX_EN, TX_ER, and TXD<3:0> during the transition into and out of
the LPI state.
TX_CLK
TX_EN
0001 x x x x
TXD<3:0>
wake time
TX_ER enter low exit low

power state power state
PLS_CARRIER.indication
(representation)
CARRIER_ON CARRIER_OFF
Figure 226aLPI transition
Insert the following between the second and third paragraphs of 22.2.2.7:
22.2.2.7 RXD (receive data)
For EEE capability, the PHY indicates that it is receiving LPI by asserting the RX_ER signal and driving the
value 0001 onto RXD<3:0> while RX_DV is de-asserted.
Change Table 22-2 as follows:
Table 222Permissible encoding of RXD<3:0>, RX_ER, and RX_DV
RX_DV RX_ER RXD<3:0> Indication
0 0 0000 through 1111 Normal interframe
0 1 0000 Normal interframe
0 1 0001 Assert LPI
0 1 1110 False Carrier indication
0 1 1111 Reserved
1 0 0000 through 1111 Normal data reception
1 1 0000 through 1111 Data reception with errors
22.2.2.8 RX_ER (receive error)
22.2.2.8a Receive direction LPI transition
When the PHY receives signals from the link partner to indicate transition into the low power state, it
indicates this to the LPI client by asserting RX_ER and setting RXD<3:0> to 0001 while keeping RX_DV
de-asserted. The PHY maintains these signals in this state while it remains in the low power state. When the
PHY receives signals from the link partner to indicate transition out of the low power state, it indicates this
to the LPI client by de-asserting RX_ER and returning to a normal interframe state.
While the PHY device is indicating LPI, it may halt the RX_CLK at any time more than 9 clock cycles after
the start of the low power state as shown in (Figure 229a) if and only if the Clock stop enable bit is asserted
(see 45.2.3.1.3a). The PHY may restart RX_CLK at any time while it is asserting LPI, but shall restart
RX_CLK so that at least one positive transition occurs before it de-asserts LPI.
Figure 229a shows the behavior of RX_ER, RX_DV and RXD<3:0> during LPI transitions.
9 cycles
RX_CLK
RX_DV
RXD<3:0> XX XX XX 0001 XX XX XX XX
RX_ER
Figure 229aLPI transitions (receiver)
22.6 Mechanical characteristics
Insert a new subclause 22.6a before 22.7 as follows:
22.6a LPI assertion and detection
Certain PHYs support Energy-Efficient Ethernet (EEF) (see Clause 78). PHYs with EEE capability support
LPI assertion and detection. LPI operation and the LPI client are described in 78.1. LPI signaling allows the
LPI client to signal to the PHY and to the link partner that an interruption in the data stream is expected and
components may use this information to enter power-saving modes that require additional time to resume
normal operation. Similarly, it allows the LPI client to understand that the link partner has sent such an
indication. LPI signaling on the MII is specified only for 100 Mb/s operation.
The LPI assertion and detection mechanism fits conceptually between the PLS Service Primitives and the
MII signals as shown in Figure 2219a.
PLS_Service Primitives MII Signals
Reconciliation sublayer
(LPI client service interface)
TX_ER
LP_IDLE.request
re-mapping for LPI TXD<3:0>
PLS_DATA.request TX_EN
TX_CLK
MAC
RXD<3:0>
re-mapping for LPI
RX_CLK
LP_IDLE.indication CRS
Figure 2219aLPI assertion and detection mechanism
The definition of TX_EN, TX_ER and TXD<3:0> is derived from the state of PLS_DATA.request
(22.2.1.1), except when it is overridden by an assertion of LP_IDLE.request. Similarly, RX_ER and
RXD<3:0> are mapped to PLS_DATA.indication except when LP_IDLE is detected. CRS is mapped to
PLS_CARRIER.indication except when LP_IDLE.request is asserted or the wake timer has yet to expire.
The timing of PLS_CARRIER.indication when used for the LPI function is controlled by the LPI transmit
state diagram.
22.6a.1 LPI messages
LP_IDLE.indication(LPI_INDICATION)
A primitive that indicates to the LPI client that the PHY has detected the assertion or de-assertion
of LPI from the link partner.
Values:DEASSERT: The link partner is operating with normal interframe behavior (default).
ASSERT: The link partner has asserted LPI.
LP_IDLE.request(LPI_REQUEST)
The LPI_REQUEST parameter can take one of two values: ASSERT or DE-ASSERT. ASSERT
initiates the signaling of LPI to the link partner. DE-ASSERT stops the signaling of LPI to the link
partner. The effect of receipt of this primitive is undefined if link_status is not OK (see 28.2.6.1.1)
or if LPI_REQUEST=ASSERT within 1 second of the change of link_status to OK.
22.6a.2 Transmit LPI state diagram
The operation of LPI in the PHY requires that the MAC does not send valid data for a time after LPI has
been de-asserted as governed by resolved Transmit Tw_sys defined in 78.4.2.3.
This wake up time is enforced by the transmit LPI state diagram and the rules mapping
CARRIER_SENSE.indication defined in 22.2.1.3. The implementation shall conform to the behavior
described by the transmit LPI state diagram shown in Figure 2219b.
22.6a.2.1 Conventions
The notation used in the state diagram follows the conventions of 21.5.
22.6a.2.2 Variables and counters
The transmit LPI state diagram uses the following variables and counters:
power_on
Condition that is true until such time as the power supply for the device that contains the RS has
reached the operating region.
Values:FALSE: The device is completely powered (default).
TRUE: The device has not been completely powered.
rs_reset
Used by management to control the resetting of the RS.
Values:FALSE: Do not reset the RS (default).
TRUE: Reset the RS.
tw_timer
A timer that counts the time since the de-assertion of LPI. The terminal count of the timer shall be
the value of the resolved Tw_sys_tx as defined in 78.2 and 78.4. The minimum value of Tw_sys_tx
shall be 30 s for 100BASE-TX. Signal tw_timer_done is asserted on reaching its terminal count.
22.6a.2.3 State diagram
rs_reset + power_on
LPI_DEASSERTED
tw_timer 0
CARRIER_STATUS OFF
LPI_REQUEST = ASSERT
LPI_ASSERTED
CARRIER_STATUS ON
LPI_REQUEST = DEASSERT
LPI_WAIT
start_tw_timer
tw_timer_done
Figure 2219bTransmit LPI state diagram
22.6a.3 Considerations for transmit system behavior
The transmit system should expect that egress data flow will be halted for at least resolved Tw_sys_tx (see
78.2) time, in microseconds, after it requests the de-assertion of LPI. Buffering and queue management
should be designed to accommodate this.
22.6a.3.1 Considerations for receive system behavior
The mapping function of the Reconciliation Sublayer shall continue to signal IDLE on PLS_DATA.indicate
while it is detecting LP_IDLE on the MII. The receive system should be aware that data frames may arrive
at the MII following the de-assertion of LPI_INDICATION with a delay corresponding to the link partners
resolved Tw_sys_rx (as specified in 78.5) time, in microseconds.
Reconciliation Sublayer (RS) and Media Independent Interface (MII)3
22.7.2 Identification
Insert the following row at the end of the table in 22.7.2.3:
22.7.2.3 Major capabilities/options
Item Feature Subclause Status Support Value/Comment
*LPI Implementation of LPI 22.6a O
3
22.7.3 PICS proforma tables for reconciliation sublayer and media independent interface
22.7.3.2 MII signal functional specifications
Insert a new subclause 22.7.3.2a after 22.7.3.2:
22.7.3.2a LPI functions
L1 Transitions to 22.2.1.3.2 LPI:M

LPI_ASSERTED and
LPI_DEASSERTED reflected
in CARRIER_STATUS
L2 RX_CLK max high/low time 22.2.2.2 LPI:M Max 2 times the nominal
while the PHY is asserting LPI period
L3 Assertion of LPI as defined in 22.2.2.4 LPI:M

Table 221
L4 RX_CLK stoppable during LPI 22.2.2.8a LPI:O At least 9 cycles after LPI
assertion
L5 RX_CLK restart before LPI 22.2.2.8a LPI:O At least 1 positive edge before
deasserted LPI de-assertion
L6 Behavior matches the transmit 22.6a.2 LPI:M

LPI state diagram
L7 Terminal count for tw_timer 22.6a.2.2 LPI:M Based on resolved Tw_sys_tx
L8 RS continues to indicate IDLE 22.6a.3.1 LPI:M

on PLS_DATA.indicate
24. Physical Coding Sublayer (PCS) and Physical Medium Attachment

(PMA) sublayer, type 100BASE-X
24.1 Overview
24.1.1 Scope
Insert the following new paragraph after the second paragraph in 24.1.1:
The 100BASE-X may support the capability of Energy-Efficient Ethernet (EEE) as described in Clause 78.
When a transmitting station of a link with this capability detects low link utilization, it can request the local
PHY transmitter to enter the Low Power Idle (LPI) mode and send appropriate symbols over the link. Upon
receiving and decoding those symbols, the link partners receiver can enter the LPI mode. The transmit and
receive paths can enter and exit low power states independently. Energy is conserved by deactivating the
corresponding functional blocks of individual path. Only 100BASE-TX supports this optional capability.
24.1.2 Objectives
Insert item g) after item f) and change items d) and e1) in the lettered list as follows:
a) Support the CSMA/CD MAC in the half duplex and the full duplex modes of operation.
b) Support the 100BASE-T MII, repeater, and optional Auto-Negotiation.
c) Provide 100 Mb/s data rate at the MII.
d) Support cable plants using Category 5 UTP4, 150 STP or optical fiber, compliant with ISO/IEC
11801.
e) Allow for a nominal network extent of 200400 m, including
1) Unshielded4 twisted-pair links of 100 m;
2) Two repeater networks of approximately 200 m span;
3) One repeater network of approximately 300 m span (using fiber); and
4) DTE/DTE links of approximately 400 m (half duplex mode using fiber) and 2 km (full duplex
mode using multimode fiber).
f) Preserve full duplex behavior of underlying PMD channels.
g) Optionally support EEE through the function of LPI (see Clause 78), available only for 100BASE-
TX.
4
ISO/IEC 11801:1995 makes no distinction between shielded or unshielded twisted-pair cables, referring to both as balanced cables.
24.1.3 Relationship of 100BASE-X to other standards
Replace Figure 24-1 with a new figure as follows:
OSI LAN
REFERENCE CSMA/CD
MODEL LAYERS
LAYERS
HIGHER LAYERS
LLC (LOGICAL LINK CONTROL)

APPLICATION
OR OTHER MAC CLIENT
PRESENTATION
MACMEDIA ACCESS CONTROL
SESSION RECONCILIATION
TRANSPORT * MII
PCS
NETWORK
PMA PHY
**
DATA LINK PMD
***AUTONEG
PHYSICAL MDI
MEDIUM To 100 Mb/s baseband repeater set
or to 100BASE-X PHY (point-to-point link)
MDI = MEDIUM DEPENDENT INTERFACE PCS = PHYSICAL CODING SUBLAYER

MII = MEDIA INDEPENDENT INTERFACE PMA = PHYSICAL MEDIUM ATTACHMENT
PHY = PHYSICAL LAYER DEVICE
PMD = PHYSICAL MEDIUM DEPENDENT
* MII is optional.
** AUTONEG communicates with the PMA sublayer through the PMA service interface messages
PMA_LINK.request and PMA_LINK.indicate.
*** AUTONEG is mandatory for EEE capability and optional otherwise.
Figure 241Type 100BASE-X PHY relationship to the ISO/IEC Open Systems

Interconnection (OSI) reference model and the IEEE 802.3 CSMA/CD LAN model
24.1.4 Summary of 100BASE-X sublayers
24.1.4.1 Physical Coding Sublayer (PCS)
Change 24.1.4.1 by inserting item e) and changing items c) and d) in the lettered list as follows:
a) Encoding (decoding) of MII data nibbles to (from) five-bit code-groups (4B/5B);

b) Generating Carrier Sense and Collision Detect indications;
c) Serialization (deserialization) of code-groups for transmission (reception) on the underlying serial
PMA, and;
d) Mapping of Transmit, Receive, Carrier Sense and Collision Detection between the MII and the
underlying PMA.,and
e) Optionally, interpreting and generating MII data signals to enable or disable the LPI mode.
24.1.4.2 Physical Medium Attachment (PMA) sublayer
Change the lettered list in 24.1.4.2 by inserting item e), changing item e), and renumbering the last item
as follows:
d) Optionally, sensing receive channel failures and transmitting the Far-End Fault Indication; and
detecting the Far-End Fault Indication; and
e) Optionally, receiving and processing LPI control signals from the PCS; and
f) Recovery of clock from the NRZI data supplied by the PMD.
Insert a new subclause 24.1.4.4 after 24.1.4.3 as follows.
24.1.4.4 Auto-Negotiation
Auto-Negotiation shall be implemented for EEE capability. See Clause 28.
24.1.6 Functional block diagram
Change 24.1.6 as follows:
Figure 244 provides a functional block diagram of the 100BASE-X PHY. Signals or functions shown with
dashed lines are optional.
MII
TXD<3:0> RXD<3:0>
TX_CLK RX_DV
TX_EN CRS
COL
TX_ER RX_ER
RX_CLK
PCS
CARRIER
SENSE
transmitting
receiving
TRANSMIT RECEIVE
tx_bits [4:0]
rx_bits [9:0]
TRANSMIT BITS RECEIVE BITS
signal_status lpi_link_fail
tx_quiet tx_code-bit rx_code-bit rx_quiet
link_status rx_lpi carrier_status
rxerror_status
PMA
CARRIER
DETECT
faulting
FAR-END FAULT
GENERATE FAR-END FAULT
LINK MONITOR
DETECT
TX RX
rx_lpi link_control
tx_quiet tx_nrzi-bit signal_status rx_nrzi-bit rx_quiet
Auto-negotiation
(Clause 28)
PMD x
Transmit Receive
MDI
Figure 244Functional block diagram
24.2 Physical Coding Sublayer (PCS)
24.2.2 Functional requirements
Change the third and fourth paragraphs of 24.2.2, and insert two new paragraphs after the third and
fourth paragraphs, respectively, as follows:
The Receive Bits process accepts continuous code-bits via the PMA_UNITDATA.indicate primitive.
Receive monitors these bits and generates RXD <3:0>RXD<3:0>, RX_DV and RX_ER on the MII, and the
internal flag, receiving, used by the Carrier Sense and Transmit processes.
Upon receiving proper code-groups via rx_code_bits from the link partner as described in 24.2.2.1.5, the
Receive process may support the LPI function by deactivating all or part of receive functional blocks of the
PCS, PMA, and PMD to conserve energy during the low link utilization period, and generate commands
through the MII as described in 22.2.2.7. By interacting with the Link Monitor of the PMA, a link failure
detection mechanism is included to differentiate two conditions of link failure due to signal off: the loss of
channel signal during the normal operation and the loss of refresh signal in the LPI mode.
The Transmit process generates continuous code-groups based upon the TXD <3:0>TXD<3:0>, TX_EN,
and TX_ER signals on the MII. These code-groups are transmitted by Transmit Bits via the
PMA_UNITDATA.request primitive. The Transmit process generates the MII signal COL based on whether
a reception is occurring simultaneously with transmission. Additionally, it generates the internal flag,
transmitting, for use by the Carrier Sense process.
The Transmit process may support the LPI function by deactivating all or part of the transmit functional
blocks of the PCS, PMA, and PMD to conserve energy during the low link utilization period upon receiving
the proper command from MII as described in 22.2.2.4. In this mode, the Transmit process is periodically
activated to transmit refresh signal through tx_code_bits in order to allow the remote receiver to keep track
of the long-term variation of channel characteristics and the clock drift between link partners.
The Carrier Sense process asserts the MII signal CRS when either transmitting or receiving is TRUE. Both
the Transmit and Receive processes monitor link_status via the PMA_LINK.indicate primitive, to account
for potential link failure conditions.
24.2.2.1 Code-groups
Change the last paragraph of 24.2.2.1 and insert a new list item e) as follows:
The indicated code-group mapping is identical to ISO/IEC 9314-1:1989, with fourfive exceptions:
a) The FDDI term symbol is avoided in order to prevent confusion with other 100BASE-T
terminology. In general, the term code-group is used in its place.
b) The /S/ and /Q/ code-groups are not used by 100BASE-X and are interpreted as INVALID.
c) The /R/ code-group is used in 100BASE-X as the second code-group of the End-of-Stream delimiter
rather than to indicate a Reset condition.
d) The /H/ code-group is used to propagate receive errors rather than to indicate the Halt Line State.
e) The /P/ code-group is used to indicate LPI.
24.2.2.1.1 Data code-groups
Change Table 241 by inserting the new code-groups SLEEP below existing code-groups IDLE as
follows.
Table 2414B/5B code-groups
PCS code-group MII (TXD/RXD)

[4:0] Name <3:0> Interpretation
43210 3210
1 1 1 1 1 I undefined IDLE;
used as inter-stream fill code
0 0 0 0 0 P 0 0 0 1 SLEEP; LPI code only for the EEE capability.
Otherwise, Invalid code;
refer to Table 221 and Table 222
Insert a new subclause 24.2.2.1.5a after 24.2.2.1.5 as follows:
24.2.2.1.5a SLEEP code-groups (/P/)
The SLEEP code-group (/P/) is used to delineate the boundary of an LPI sequence and to deliver a refresh
signal to maintain clock synchronization and verify the link status. The SLEEP code-groups are emitted
from, and interpreted by, the PCS.
24.2.3 State variables
24.2.3.1 Constants
Insert the following text at the end of the list, right before 24.2.3.2 Variables:
The following constants are required only for the optional EEE capability:
SLEEP
The SLEEP code-group (/P/) used by the LPI state delineator, as specified in 24.2.2.1.
TX_LP_IDLE
A binary value 0001 of transmit nibble-wide Data signals (TXD), together with the de-assertion of
TX_EN and the assertion of TX_ER on the MII, used to indicate Assert LPI, as specified in
22.2.2.
RX_LP_IDLE
A binary value 0001 of receive nibble-wide Data signals (RXD), together with the de-assertion of
RX_DV and the assertion of RX_ER on the MII, used to indicate Assert LPI, as specified in
22.2.2.
24.2.3.2 Variables
Insert the following text at the end of the list, right before 24.2.3.3 Functions:
The following variables are required only for the optional EEE capability:
lpi_link_fail
A Boolean set by the Receive process to control the transition to a Link Down state when in the
LPI mode. Used by the Link Monitor process of the PMA as communicated through the
PMA_LPILINKFAIL.request primitive.
Values: TRUE; local receiver has detected a link failure status when in the LPI mode
FALSE; local receiver is functioning normally when in the LPI mode
rx_lpi
A Boolean set by the Receive process to indicate the LPI mode. Used by the Link Monitor process
of the PMA as communicated through the PMA_RXLPI.request primitive. This parameter is used
to alter the signal detection time as shown in Table 253. It can also be used to halt the clock RXC
of MII as described in Clause 22.
Values: TRUE; local receiver is in the LPI mode
FALSE; local receiver is in the normal mode
rx_quiet
A Boolean set by the Receive process to indicate a Quiet state of the receiver in the LPI mode as
communicated through the PMD_RXQUIET.request primitive. Also may be used to control the
power-saving function of various receive blocks (PCS, PMA, and PMD).
Values: TRUE; the local receiver is in the Quiet state
FALSE; the local receiver is not in the Quiet state
tx_quiet
A Boolean set by the Transmit process to indicate a Quiet state of the transmitter in the LPI mode
as communicated through the PMD_TXQUIET.request primitive. Also may be used to control the
power-saving function of various transmit blocks (PCS, PMA, and PMD).
Values: TRUE; the local transmitter is in the Quiet state
FALSE; the local transmitter is not in the Quiet state
signal_status
The signal_status parameter as communicated by the PMD_SIGNAL.indicate primitive.
Values: ON; the quality and level of the received signal is satisfactory
OFF; the quality and level of the received signal is not satisfactory
24.2.3.4 Timers
Insert the following text at the end of the list in 24.2.3.4:
The following timers are required only for the optional EEE capability:
lpi_link_fail_timer
In the LPI mode, the receiver in Wake state is checking if valid symbols are properly received. This
timer defines the maximum time allowed for the PHY between entry into the Wake state and
subsequent entry into the Quiet, Sleep, or Idle states before assuming a link failure. The timer shall
have a period between 90 s and 110 s.
lpi_rx_ti_timer
In the LPI mode, the receiver can move to the Idle state when it receives consecutive IDLE
symbols. In order to distinguish the intended IDLE symbols sent by the link partner from ones
falsely decoded during the transition from the Sleep state to the Quiet state before the signal status
is de-asserted, this receiver timer counts the minimum duration of received IDLE symbols. During
this period of time, the receiver stays in an intermediate state. The timer shall have a period
between 0.8 s and 0.9 s.
lpi_rx_tq_timer
In the LPI mode, this receiver timer counts the maximum duration the PHY stays in the Quiet state
before it expects a Refresh signal. If the PHY fails to receive a valid Refresh signal or Wake signal
before this timer expires, the receiver shall assume a link failure. The timer shall have a period
between 24 ms and 26 ms.
lpi_rx_ts_timer
In the LPI mode, this receiver timer counts the maximum duration the PHY is allowed to stay in
the Sleep state before assuming a link failure. The timer shall have a period between 240 s and
260 s.
lpi_rx_tw_timer
In the LPI mode, the receiver in the Quiet state is woken up by the receiving signal. This receiver
timer counts the expected duration for the PHY to identify if valid SLEEP symbols for the Refresh
state or valid IDLES for the Wake state have been properly received. If none of the SLEEP or
IDLE symbols are received when the timer expires, the wake error counter as defined in MDIO
manageable device (MMD) register 3.22 (see 45.2.3.8b) shall be incremented. The timer shall have
a period that does not exceed 20.5 s.
lpi_tx_tq_timer
In the LPI mode, this transmitter timer counts the duration the PHY remains in the Quiet state
before it must wake to send a refresh signal. The timer shall have a period between 20 ms and
22 ms.
lpi_tx_ts_timer
In the LPI mode, this transmitter timer counts the duration the PHY is sending continuous SLEEP
symbols in the Sleep state before going into the Quiet state. The timer shall have a period between
200 s and 220 s.
24.2.4 State diagrams
24.2.4.2 Transmit
Change the first paragraph in 24.2.4.2 and insert a new paragraph as follows:
The Transmit process sends code-groups to the PMA via tx_bits and the Transmit Bits process. When
initially invoked, and between streams (delimited by TX_EN on the MII), except in the LPI mode for the
optional EEE capability, the Transmit process sources continuous Idle code-groups (/I/) to the PMA. Upon
the assertion of TX_EN by the MII, the Transmit process passes an SSD (/J/K/) to the PMA, ignoring the
TXD <3:0> TXD<3:0> nibbles during these two code-group times. Following the SSD, each TXD <3:0>
TXD<3:0> nibble is encoded into a five-bit code-group until TX_EN is de-asserted. If, while TX_EN is
asserted, the TX_ER signal is asserted, the Transmit process passes Transmit Error code-groups (/H/) to the
PMA. Following the de-assertion of TX_EN, an ESD (/T/R/) is generated, after which the transmission of
Idle code-groups is resumed by the IDLE state.
If EEE Capability is supported, upon the assertion of LPI on the MII (a binary value 0001 of TXD, together
with the de-assertion of TX_EN and the assertion of TX_ER, see 22.2.2), the Transmit process enters the
LPI mode and starts to source SLEEP (/P/) code-groups to the PMA. In the LPI mode, the Transmit process
is controlled by timers to switch between the TX_SLEEP and TX_QUIET states. The Transmit process
returns to the IDLE state whenever the MII de-asserts LPI.
Replace Figure 248 with a new figure as follows:
BEGIN link_status OK
IDLE sentCodeGroup.indicate
transmitting FALSE sentCodeGroup.indicate TX_EN = FALSE
COL FALSE TX_EN = TRUE TX_ER = TRUE *
tx_bits [4:0] IDLE TX_ER = TRUE TXD[3:0] = TX_LP_IDLE
tx_quiet FALSE
sentCodeGroup.indicate TX_SLEEP
BackToIDLE TX_EN = TRUE START ERROR J tx_quiet FALSE

(NOTE) TX_ER = FALSE Start lpi_tx_ts_timer
transmitting TRUE
tx_bits [4:0] SLEEP
START STREAM J COL receiving
tx_bits [4:0] SSD1 sentCodeGroup.indicate
transmitting TRUE
COL receiving sentCodeGroup.indicate (TX_EN = TRUE +
tx_bits [4:0] SSD1 TX_ER = FALSE +
TXD[3:0] != TX_LP_IDLE)
sentCodeGroup.indicate sentCodeGroup.indicate
TX_ER = FALSE TX_ER = TRUE sentCodeGroup.indicate
START STREAM K START ERROR K lpi_tx_ts_timer_done
TX_EN = FALSE *
COL receiving COL receiving
tx_bits [4:0] SSD2 tx_bits [4:0] SSD2 TX_ER = TRUE *
TXD[3:0] = LP_IDLE
TX_QUIET
tx_quiet TRUE
Start lpi_tx_tq_timer
ERROR CHECK
sentCodeGroup.indicate
(TX_EN = TRUE +
TX_EN = TRUE TX_EN = TRUE TX_ER = FALSE +
TX_ER = FALSE TX_EN = FALSE TX_ER = TRUE TXD[3:0] != TX_LP_IDLE)
TRANSMIT DATA END STREAM T TRANSMIT ERROR
COL receiving transmitting FALSE COL receiving lpi_tx_tq_timer_done
tx_bits [4:0] COL FALSE tx_bits [4:0] HALT
ENCODE (TXD<3:0>) tx_bits [4:0] ESD1
END STREAM R
tx_bits [4:0] ESD2
NOTE 1BackToIDLE represents the following branch condition:

If the EEE capability is supported,
sentCodeGroup.indicate * TX_EN = FALSE * (TX_E R= FALSE + (TX_ER = TRUE * TXD[3:0] TX_LP_IDLE))
Otherwise,
sentCodeGroup.indicate * TX_EN = FALSE
NOTE 2States and state transitions shown within the dashed box are only required for the EEE capability
Figure 248Transmit state diagram
24.2.4.4 Receive
Change the first paragraph in 24.2.4.4 and insert a new paragraph as follows:
The Receive process state diagram can be viewed as comprising two sections: prealigned and aligned. In the
prealigned states, IDLE, CARRIER DETECT, and CONFIRM K IDENTIFY JK, except for the detection of
SLEEP code-groups when supporting the optional EEE capability, the Receive process is waiting for an
indication of channel activity followed by a an SSD. After successful alignment, the incoming code-groups
are decoded while waiting for stream termination.
If EEE Capability is supported, when the Receive process successfully aligns and decodes two consecutive
SLEEP (/P/) code-groups, it enters the LPI mode and stays in LPI states until either the IDLE code-groups
are received, where it leads the Receive process to the IDLE state, or a link failure condition in the LPI mode
occurs, where it causes the Receive process to enter the RX_LPI_LINK_FAIL state and eventually move to
the IDLE state.
Replace the Receive state diagram (Figure 2411) with two new figures, Figure 2411a and
Figure 2411b:
BEGIN link_status OK
link_status OK RX_DV = FALSE
receiving = TRUE
RX_DV = TRUE A
gotCodeGroup.indicate
IDLE
gotCodeGroup
.indicate receiving FALSE
RX_ER FALSE
LINK FAILED
RX_DV FALSE
RX_ER TRUE rx_lpi FALSE
receiving FALSE Stop lpi_rx_tw_timer
rx_bits [9:0] = IDLES link_status = OK

rx_bits [0] = 0
rx_bits [9:2] 11111111
rx_bits [9:0] = /P/P/ rx_bits [9:0] CARRIER DETECT
/I/J/
BAD SSD receiving TRUE
B
RX_ER TRUE
rx_bits [9:0] = /I/J/
RXD<3:0> 1110
(rx_bits [9:5] = /J/)

IDENTIFY JK
(rx_bits [4:0] /K/)
rx_bits [9:0] = /I/P/

(rx_bits [9:5] = /J/)
(rx_bits [4:0] = /K/)
WAIT_SLEEP
START OF STREAM J
rx_bits [9:0] = /P/P/
(rx_bits [9:5] = /P/) RX_DV TRUE
(rx_bits [4:0] /P/) B RXD<3:0> 0101
END OF STREAM START OF STREAM K

UCT
rx_bits [9:0]
RXD<3:0> 0101
11111 11111
UCT rx_bits [9:5] DATA
gotCodeGroup.indicate rx_bits [9:0] ESD
rx_bits [9:0] IDLES
rx_bits [9:0] = ESD RECEIVE DATA ERROR
RX_ER TRUE
UCT
gotCodeGroup.indicate gotCodeGroup.indicate
rx_bits [9:0] = IDLES rx_bits [9:5] DATA
DATA
PREMATURE END RX_ER FALSE
RX_ER TRUE RXD<3:0>
UCT
DECODE (rx_bits [9:5])
NOTEStates and state transitions shown within the dashed box are only required for the EEE capability
Figure 2411aReceive state diagram, part a
START_RX_SLEEP
Start lpi_rx_ts_timer
Stop lpi_rx_tw_timer
UCT
RX_SLEEP
rx_lpi TRUE
lpi_link_fail FALSE
RX_ER TRUE
RX_DV FALSE
RXD<3:0> RX_LP_IDLE signal_status = ON *
rx_bits [9:0] =IDLES
signal_status = OFF
lpi_rx_ts_timer_done
START_RX_QUIET
WAIT_IDLE
Start lpi_rx_tq_timer
Start lpi_rx_ti_timer
UCT
RX_QUIET signal_status = OFF +

rx_quiet TRUE rx_bits [9:0] IDLES *
lpi_rx_ti_timer_not_done
Stop lpi_rx_tw_timer
signal_status = ON signal_status = OFF signal_status = ON

lpi_rx_tq_timer_done lpi_rx_ti_timer_done
RX_WAKE
rx_quiet FALSE
Start lpi_rx_tw_timer
Start lpi_link_fail_timer
lpi_link_fail_timer_done
signal_status = OFF
rx_bits [9:0] = /P/P/
rx_bits [9:0] = IDLES
RX_LPI_LINK_FAIL
rx_quiet FALSE
lpi_link_fail TRUE
link_status OK*
RX_DV = FALSE
Figure 2411bReceive state diagram, part b (only required for the EEE capability)
24.3 Physical Medium Attachment (PMA) sublayer
24.3.1 Service interface
Insert new primitives in 24.3.1 after the third paragraph, at the end of the list, as follows:
PMA_LPILINKFAIL.request
PMA_RXLPI.request
Insert the following new subclause 24.3.1.8 after 24.3.1.7.3 as follows:
24.3.1.8 PMA_LPILINKFAIL.request
This primitive is generated by the Receive Process of the PCS only if EEE is supported to control one of the
link failure conditions of the Link Monitor in the PMA (see 24.2.4.4 and Figure 2411b).
PMA_LPILINKFAIL.request (lpi_link_fail)
The lpi_link_fail parameter takes on one of two values, TRUE or FALSE, indicating whether a link failure
condition has been set (TRUE) or not (FALSE). The value of TRUE, when in the LPI mode, sets the
link_status of the Link Monitor to FAIL (see 24.3.4.4 and Figure 2415).
The PCS generates this primitive to indicate a link failure condition caused by the loss of Refresh signal
when in the LPI mode.
24.3.1.8.3 Effect of receipt
This primitive affects operation of the PMA Link Monitor function as described in 24.3.4.4.
24.3.1.9 PMA_RXLPI.request
This primitive is generated by the Receive Process of the PCS only if EEE is supported to indicate that the
receiver is in the LPI mode (see 24.2.4.4 and Figure 2411b).
PMA_RXLPI.request (rx_lpi)
The rx_lpi parameter takes on one of two values, TRUE or FALSE, indicating whether the receiver is in the
LPI mode (TRUE) or not (FALSE).
The PCS generates this primitive to indicate the LPI mode.
This primitive affects the operation of the PMA Link Monitor function as described in 24.3.4.4. Other use of
receipt of this primitive by the client is unspecified by the PMA sublayer.
24.3.2 Functional requirements
Insert item e) after item d) in the lettered list of 24.3.2 as follows:
e) EEE capability, which disables the Far-End Fault function and modifies the link down condition
with the PMA_RXLPI.request primitive.
24.3.2.1 Far-End fault
Change the sixth paragraph of 24.3.2.1 as follows:
The Far-End Fault Generate process, which is interposed between the incoming tx_code-bit stream and the
TX process, is responsible for sensing a receive channel failure (signal_status=OFF during the normal
operation) and transmitting the Far-End Fault Indication in response. The transmission of the Far-End Fault
Indication may start or stop at any time depending only on signal_status. The Far-End Fault shall not be
generated when in the LPI mode.
Insert a new subclause 24.3.2.3 after 24.3.2.2 as follows:
24.3.2.3 EEE capability
EEE capability, when communicated by the PMA_RXLPI.request primitive, affects the PMA in two ways.
It disables the operation of the Far-End Fault processes to ignore the frequent on and off activity of
signal_status. It receives link failure detection as communicated by the PMA_LPILINKFAIL.request
primitive and changes the Link Monitor process to allow an exit from the LPI mode to a link down state. The
EEE capability of the PMA is required only if the PCS supports EEE. If LPI is implemented, the operation
of the PMA shall comply with the requirements in this subclause.
24.3.3.2 Variables
Insert the following text at the end of the list, right before 24.3.3.3 Functions:
The following variables are required only for the optional EEE capability:
lpi_link_fail
The lpi_link_fail parameter is communicated by the PMA_LPILINKFAIL.request primitive. In
the LPI mode, this variable is generated by the Receive process of the PCS to control the transition
to a Link Down state. In the absence of the optional EEE capability, the PHY shall operate as if
the value of this variable is FALSE.
Values: TRUE; local receiver has detected a link failure status when in an LPI state
FALSE; local receiver is functioning normally when in an LPI state
rx_lpi
The rx_lpi parameter is communicated by the PMA_RXLPI.request primitive. This variable is
generated by the Receive process of the PCS to indicate the LPI mode. In the absence of the
optional EEE capability, the PHY shall operate as if the value of this variable is FALSE.
Values: TRUE; local receiver is in the LPI mode
FALSE; local receiver is in the normal operation mode
24.3.4 Process specifications and state diagrams
24.3.4.4 Link Monitor
Change the second paragraph of 24.3.4.4 as follows:
The Link Monitor process monitors signal_status, setting link_status to FAIL whenever signal_status is OFF
during the normal operation or when Auto-Negotiation sets link_control to DISABLE. If the EEE capability
is supported, when the receiver is in the LPI mode, the assertion of lpi_link_fail shall set the link_status to
FAIL and eventually brings the receiver out of the LPI mode. The link is deemed to be reliably operating
when signal_status has been continuously ON for a period of time. This period is implementation dependent
but not less than 330 s or greater than 1000 s. If so qualified, Link Monitor sets link_status to READY in
order to synchronize with Auto-Negotiation, when implemented. Auto-Negotiation permits full operation by
setting link_control to ENABLE. When Auto-Negotiation is not implemented, Link Monitor operates with
link_control always set to ENABLE.
Replace the Link Monitor diagram (Figure 2415) with a new figure as follows:
(rx_lpi = FALSE * signal_status = OFF) +

BEGIN (rx_lpi = TRUE * lpi_link_fail = TRUE) +
(link_control = DISABLE) +
(faulting = TRUE)
LINK DOWN
link_status FAIL
signal_status = ON
HYSTERESIS
Start stablize_timer
stablize_timer_done
LINK READY
link_status READY
link_control = ENABLE
link_control =
LINK UP
SCAN_FOR_CARRIER
link_status OK
NOTE 1The variables link_control and link_status are designated as link_control_[TX] and
link_status_[TX], respectively, by the Auto-Negotiation Arbitration state diagram (Figure 2818).
NOTE 2The variables rx_lpi and lpi_link_fail are only required for the EEE capability and should be
treated as if the value of these two variables is FALSE otherwise.
Figure 2415Link Monitor state diagram
24.3.4.5 Far-End Fault Generation
Far-End Fault Generate simply passes tx_code-bits to the TX process when signal_status=ON. When
signal_status=OFF and not in the LPI mode, it repetitively generates each cycle of the Far-End Fault
Indication until signal_status is reasserted.
Replace the Far-End Fault diagram (Figure 2416) with a new figure as follows:
BEGIN
INITIALIZE
num_ones 0
CHECK SIGNAL DETECT
UCT UCT
SEND FEF ONE FORWARD
tx_code-bit_out ONE tx_code-bit_out tx_code_bit_in
num_ones num_ones + 1 num_ones 0
PMD_UNITDATA.request
signal_status = OFF
num_ones < FEF_ONES *
rx_lpi = FALSE PMD_UNITDATA.request
signal_status = ON
signal_status = OFF
num_ones = FEF_ONES *
rx_lpi = FALSE UCT
SEND FEF ZERO
tx_code-bit_out ZERO
num_ones 0
NOTEThe variable rx_lpi is only required for the EEE capability and should be treated as if the value
of this variable is FALSE otherwise.
Figure 2416Far-End Fault Generation state diagram
24.4 Physical Medium Dependent (PMD) sublayer service interface
24.4.1 PMD service Interface
Change the first paragraph of 24.4.1, and insert a new exception item c) in the lettered list as follows:
The following specifies the services provided by the PMD. The PMD is a sublayer within 100BASE-X and
may not be present in other 100BASE-T PHY specifications. PMD services are described in an abstract
manner and do not imply any particular implementation. It should be noted that these services are
functionally identical to those defined in the FDDI standards, such as ISO/IEC 9314-3:1990 and ANSI
X3.263-1995, with two three exceptions:
a) 100BASE-X does not include a Station Management (SMT) function; therefore the PMD-to-SMT
interface defined in ISO/IEC 9314-3:1990 and ANSI X3.263-1995.
b) 100BASE-X does not support multiple instances of a PMD in service to a single PMA; therefore, no
qualifiers are needed to identify the unique PMD being referenced.
c) 100BASE-X may support LPI for the EEE capability.
Insert the following text and primitives at the end of 24.4.1 right before 24.4.1.1 as follows:
The following primitives are defined only for the optional EEE capability:
PMD_RXQUIET.request
PMD_TXQUIET.request
Insert the following new subclause 24.4.1.4 after 24.4.1.3.3 as follows:
24.4.1.4 PMD_RXQUIET.request
This primitive is generated by the Receive Process of the PCS only if EEE is supported to indicate that the
receiver is in the LPI mode and the line is in the Quiet state (see 24.2.4.4 and Figure 2411b).
PMD_RXQUIET.request(rx_quiet)
The rx_quiet parameter takes on one of two values, TRUE or FALSE, indicating whether the receiver is in
the Quiet state (TRUE) or not (FALSE).
The PCS generates this primitive to indicate a Quiet state of the transmitter in the LPI mode.
This primitive affects operation of the PMD function of type 100BASE-TX as described in 25.4a.2. Other
use of receipt of this primitive by the client is unspecified by the PMD sublayer.
24.4.1.5 PMD_TXQUIET.request
This primitive is generated by the Transmit Process of the PCS only if EEE is supported to indicate that the
transmitter is in the LPI mode and the line is in the Quiet state (see 24.2.4.2 and Figure 248).
PMD_TXQUIETrequest(tx_quiet)
The tx_quiet parameter takes on one of two values, TRUE or FALSE, indicating whether the transmitter is in
the Quiet state (TRUE) or not (FALSE).
The PCS generates this primitive to indicate a Quiet state of the transmitter in the LPI mode.
This primitive affects operation of the PMD function of type 100BASE-TX as described in 25.4a.1. Other
use of receipt of this primitive by the client is unspecified by the PMD sublayer.
type 100BASE-X5
Insert the following rows after item PMA in the table of 24.8.2.3:
*LPC PCS implementation of LPI 24.2 PCS:O
*LPM PMA implementation of LPI 24.3 LPC:M
Change item *FEF in the table of 24.8.2.3 as follows:
*FEF Implements Far-End Fault 24.3.2.1 NWC:X

LPM:X
Change item NWY in the table of 24.8.2.3 as follows:
NWY Supports Auto-Negotiation 24.1.4.4 NWC:O See Clause 28

(Clause 28) LPC:M
5
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
LF1 lpi_rx_ti_timer 24.2.3.4 LPC:M The timer has a period between

0.80.9 s.
LF2 lpi_rx_tq_timer 24.2.3.4 LPC:M The timer has a period between

2426 ms.
LF3 lpi_rx_ts_timer 24.2.3.4 LPC:M The timer has a period between

240260 s.
LF4 lpi_rx_tw_timer 24.2.3.4 LPC:M The timer has a period that

does not exceed 20.5 s.
LF5 LPI wake error counter 24.2.3.4 LPC:M Increment the wake error
counter for each transition of
lpi_rx_tw_timer_done from
false to true.
LF6 lpi_tx_tq_timer 24.2.3.4 LPC:M The timer has a period between

2022 ms.
LF7 link failure caused by 24.2.3.4 LPC:M The receiver assumes a link
lpi_rx_tq_timer failure if the PHY fails to
receive a valid Refresh or
Wake signal before the
lpi_rx_tq_timer expires.
LF8 lpi_tx_ts_timer 24.2.3.4 LPC:M The timer has a period between

200220 s.
LF9 lpi_link_fail_timer 24.2.3.4 LPC:M The timer has a period between

90110 s.
LF11 lpi_link_fail 24.3.3.2 LPM:M The PHY operates as if the

value of this variable is FALSE
in the absence of the optional
EEE capability.
LF12 rx_lpi 24.3.3.2 LPM:M The PHY operates as if the

value of this variable is FALSE
in the absence of the optional
EEE capability.
LF13 link_status affected by 24.3.4.4 LPM:M The assertion of lpi_link_fail

lpi_link_fail sets the link_status to FAIL if
the EEE is supported and the
receiver is in the LPI mode.
25. Physical Medium Dependent (PMD) sublayer and baseband medium,

type 100BASE-TX
25.1 Overview
Insert a new subclause 25.1.1 after 25.1 as follows:
25.1.1 State diagram conventions
The body of this standard is comprised of state diagrams, including the associated definitions of variables,
constants, and functions. Should there be a discrepancy between a state diagram and descriptive text, the
state diagram prevails. The notation used in the state diagrams follows the conventions of 21.5; state
diagram timers follow the conventions of 14.2.3.2.
25.3 General exceptions
Change item d), insert a new item e), and reletter f) in the lettered list in 25.3, as follows:
d) The cable plant specifications for untwisted shielded unshielded twisted pair (UTP) of TP-PMD 11.1
are replaced by those specified in 25.4.7.
e) 100BASE-TX optionally supports Energy-Efficient Ethernet (EEE), as described in Clause 78, with
its Low Power Idle (LPI). Two new service primitives PMD_RXQUIET.request(rx_quiet) (see
24.4.1.4) and PMD_TXQUIET.request(tx_quiet) (see 24.4.1.5) are generated by the PCS to pass the
energy saving requests.
f) There are minor terminology differences between this standard and TP-PMD that do not cause
ambiguity. The terminology used in 100BASE-X was chosen to be consistent with other IEEE 802
standards, rather than with FDDI. Terminology is both defined and consistent within each standard.
Special note should be made of the interpretations shown in Table 251.
25.4 Specific requirements and exceptions
25.4.6 Change to 9.1.9, Jitter
Insert a new paragraph at the end of 25.4.6 as follows:
In the LPI mode, jitter shall be measured using scrambled SLEEP code-groups transmitted during the
TX_SLEEP state (see Figure 248). Total transmit jitter with respect to a continuous unjittered reference
shall not exceed 1.4 ns peak-to-peak with the exception that the jitter contributions from the clock transitions
occurring during the TX_QUIET state and the first 5 s of the TX_SLEEP state or the first 5 s of the IDLE
state following a TX_QUIET state are ignored. The jitter measurement time period shall be not less than
100 ms and not greater than 1 s.
Insert a new subclause 25.4a after 25.4 as follows:
25.4a EEE capability
TP-PMD does not have an option to support EEE. In order to add this capability to existing TP-PMD
specification, the TP-PMD 7.1.2, 7.2.2, 10.1.2, 10.1.3, and Table 4 are modified to incorporate the LPI
function. This subclause only applies to the optional EEE capability. If LPI is implemented, the operation of
the PMD shall comply with the requirements in this subclause.
25.4a.1 Change to TP-PMD 7.1.2 Encoder
The Encoder receives the scrambled NRZ data stream from the scrambler (see TP-PMD 7.1.1) and encodes
the stream into MLT3 code for presentation to the driver (see TP-PMD 7.1.3). MLT3 coding is similar to
NRZI coding, but three instead of two levels are transmitted. The Encoder can be deactivated when in the
LPI mode. The PMD Encoder function of the 100BASE-TX with EEE capability is identical to that of the
TP-PMD except that the output of the Encoder is set to a value ZERO_VOLTAGE when the transmitter is in
the Quiet state of the LPI mode (TX_QUIET, see Figure 248).
The PMD in the LPI mode shall implement the Encoder state diagram as depicted in Figure 251.
25.4a.1.1 State variables
25.4a.1.1.1 Variables
encoder_input
Indicates the value of each scrambled NRZ bit to be encoded.
Values: ZERO; the NRZ bit from the scrambler has a logical value 0
ONE; the NRZ bit from the scrambler has a logical value 1
encoder_output
Indicates the value from the encoder for each MLT-3 encoded bit.
Values: POSITIVE_VOLTAGE; the output indicates a positive value of voltage to TP-PMD
driver
ZERO_VOLTAGE; the output indicates a zero value of voltage to TP-PMD driver
NEGATIVE_VOLTAGE; the output indicates a negative value of voltage to TP-PMD
driver
link_status
The link_status parameter as communicated by the PMA_LINK.indicate primitive.
Values: FAIL; the receive channel is not intact
READY; the receive channel is intact and ready to be enabled by Auto-Negotiation
OK; the receive channel is intact and enabled for reception
tx_quiet
The tx_quiet parameter as communicated by the PMD_TXQUIET.request (tx_quiet) primitive.
This variable is generated by the Transmit process of the PCS to control the power-saving function
of the local transmitter. It sets the Encoder state diagram to an initial state of ZERO_V.
Values: TRUE; the local transmitter is in the Quiet state
FALSE; the local transmitter is not in the Quiet state
le_flag
A Boolean set by the Encoder process to indicate whether the last non-zero value of
encoder_output was POSITIVE_VOLTAGE. The flag le_flag is set upon entry to the PLUS_V
state and is cleared upon entry to the MINUS_V state.
Values: ONE; the encoder is in the PLUS_V state
ZERO; the encoder is in the MINUS_V state
25.4a.1.1.2 Messages
gotNRZbit.indicate
A signal sent to the Encoder process by the scrambler after a scrambled NRZ text bit has been
generated using recursive linear function by the scrambler from plaintext bit stream and is ready
to transmit.
link_status OK +
BEGIN tx_quiet = TRUE * gotNRZbit.indicate
ZERO_V
encoder_output ZERO_VOLTAGE
gotNRZbit.indicate * gotNRZbit.indicate *
encoder_input = ONE * encoder_input = ONE *
le_flag = ZERO le_flag = ONE
PLUS_V MINUS_V
encoder_output POSITIVE_VOLTAGE encoder_output NEGATIVE_VOLTAGE
le_flag ONE le_flag ZERO
gotNRZbit.indicate * gotNRZbit.indicate *
encoder_input = ONE encoder_input = ONE
Figure 251Encoder state diagram
25.4a.2 Change to TP-PMD 7.2.2 Decoder
The Decoder receives the MLT3 encoded bit stream from the receiver (see TP-PMD 7.2.1), and decodes it
into a NRZ encoded bit stream for presentation to the descrambler (see TP-PMD 7.2.3). The Decoder can be
deactivated when in the LPI mode. The PMD Decoder function of the 100BASE-TX with EEE capability is
identical to that of the TP-PMD except that the output of the Decoder is set to a value ZERO when the
receiver is in the Quiet state of the LPI mode (RX_QUIET, Figure 2411b).
The PMD in the LPI mode shall implement the Decoder state diagram as depicted in Figure 252.
25.4a.2.1 State variables
25.4a.2.1.1 Variables
decoder_input
Indicates the value of the MLT-3 encoded bit from the receiver.
Values: ZERO; the MLT3 bit from the receiver has a logical value 0
NONZERO; the MLT3 bit from the receiver has a non-zero logical value
decoder_output
Indicates the value of the NRZ encoded bit.
Values: ZERO; the output indicates a logical value of 0 to the descrambler
ONE; the output indicates a logical value of 1 to the descrambler
link_status
The link_status parameter as communicated by the PMA_LINK.indicate primitive.
Values: FAIL; the receive channel is not intact
READY; the receive channel is intact and ready to be enabled by Auto-Negotiation
OK; the receive channel is intact and enabled for reception
rx_quiet
The rx_quiet parameter as communicated by the PMD_RXQUIET.request (rx_quiet) primitive.
This variable is generated by the Receive process of the PCS to control the power-saving function
of local receiver. It sets the Decoder state diagram to an initial state of ZERO_VALUE.
Values: TRUE; the local receiver is in the Quiet state
FALSE; the local receiver is not in the Quiet state
prev_data
Indicates whether the last value of decoder_input was ZERO or NONZERO.
Values: ZERO; the last value of MLT3 bit of decoder_input has a logical value 0
NONZERO; the last value of MLT3 bit of decoder_input has a non-zero logical value
25.4a.2.1.2 Messages
sentNRZbit.indicate
A signal sent to the Decoder process by the descrambler after an NRZ bit from ciphertext bit
stream has been processed using recursive linear function and is ready to process the next bit from
Decoder.
link_status OK +
BEGIN rx_quiet = TRUE
ZERO_VALUE
decoder_output ZERO
prev_data decoder_input
sentNRZbit.indicate *
decoder_input prev_data
ONE_VALUE
decoder_output ONE
prev_data decoder_input
sentNRZbit.indicate *
decoder_input =prev_data
Figure 252Decoder state diagram
25.4a.3 Changes to 10.1.1.1 Signal_Detect assertion threshold
The TP-PMD 10.1.1.1 is applicable to the normal operation. In the LPI mode, when rx_lpi as communicated
by the PMA_RXLPI.request primitive is asserted, Signal_Detect shall be asserted per 25.4a.5 for any valid
peak-to-peak signal, VSDA, of greater than 400 mV.
25.4a.4 Changes to 10.1.1.2 Signal_Detect de-assertion threshold
The TP-PMD 10.1.1.2 is applicable to the normal operation. In the LPI mode, when rx_lpi is de-asserted,
Signal_Detect shall be de-asserted per 25.4a.6 for any valid peak-to-peak signal, VSDD, of smaller than
200 mV.
25.4a.5 Change to 10.1.2 Signal_Detect timing requirements on assertion
The TP-PMD 10.1.2 is applicable to the normal operation. In the LPI mode, when rx_lpi is asserted,
Signal_Detect output shall be asserted within 5 s under the same quality requirement of the received signal
as in normal operation. The new definition of conditional parameter AS_Max is inserted in TP-PMD Table 4
as depicted in Table 253.
25.4a.6 Change to 10.1.3 Signal_Detect timing requirements on de-assertion
The TP-PMD 10.1.3 is applicable to the normal operation. In the LPI mode, when rx_lpi is asserted,
Signal_Detect output shall be de-asserted within 5 s under the same quality requirement of the received
signal as in normal operation. The new definition of conditional parameter ANS_Max is inserted in TP-
PMD Table 4 as depicted in Table 253.
25.4a.7 Changes to TP-PMD 10.2 Transmitter
For the optional EEE capability, when tx_quiet (as communicated by the PMD_TXQUIET.request
primitive) is set to FALSE, the transmitter output shall deliver a signal that exceeds Signal_Detect assertion
threshold within 2 s. The scrambler shall continue to operate for the first 5 s following tx_quiet = TRUE.
Transmit functions may be deactivated after this period. The transmitter shall deliver a fully compliant
signal when tx_quiet is set to FALSE less than 5 s after being set to TRUE. If tx_quiet is set to FALSE
more than 5 s after being set to TRUE, then the transmitter shall deliver a fully compliant signal within
5 s (see 25.4.6).
25.4a.8 Replace TP-PMD Table 4 Signal_Detect summary with Table 25-3
The requirement of signal detection time and threshold are different between the normal operation mode and
the LPI mode. In order to share one Signal_Detect, the timing and threshold characteristics may be qualified
by LPI signal rx_lpi as communicated by the PMA_RXLPI.request primitive.
Table 253Signal_Detect summary
Characteristic Minimum Maximum Units
Assert time 1000 s

Normal operation mode
De-assert time 350 s

Assert time 5 s
LPI mode
De-assert time 5 s
LPI mode
Assert threshold VSDA 1000 mV

100 balanced cable peak to peak
De-assert threshold VSDD 200 mV

100 balanced cable peak to peak
150 balanced shielded cable peak to peak

150 balanced shielded cable peak to peak

LPI mode peak to peak

LPI mode peak to peak
Physical Medium Dependent (PMD) sublayer and baseband medium, type
100BASE-TX6
25.5.3 Major capabilities/options
Insert the following row at the end of the table of 25.5.3:
*LPI Implementation of LPI 25.4a O
Insert a new subclause 25.5.4.5 LPI Functions after 25.5.4.4 as follows:
25.5.4 PICS proforma tables for the Physical Medium Dependent (PMD) sublayer and
baseband medium, type 100BASE-TX
LP1 Jitter measurement in the LPI 25.4.6 LPI:M Yes [ ] 1.4 ns peak to peak
mode
LP2 Code-groups used to measure 25.4.6 LPI:M Yes [ ] Scrambled SLEEP code-
jitter in the LPI mode groups
LP3 Jitter measurement time 25.4.6 LPI:M Yes [ ] No less than 100 ms and no
interval in the LPI mode greater than 1 s.
LP4 Encoder function in the LPI 25.4a.1 LPI:M Yes [ ] Comply with the state diagram
mode shown in Figure 25-1.
LP5 Decoder function in the LPI 25.4a.2 LPI:M Yes [ ] Comply with the state diagram
mode shown in Figure 25-2.
LP6 Signal_Detect assertion 25.4a.3 LPI:M Yes [ ] Minimum 400 mV

threshold in the LPI mode peak to peak
LP7 Signal_Detect deassertion 25.4a.4 LPI:M Yes [ ] Maximum 200 mV

threshold in the LPI mode peak to peak
LP8 Signal_Detect assertion time in 25.4a.5 LPI:M Yes [ ] Maximum 5 s

the LPI mode
LP9 Signal_Detect deassertion time 25.4a.6 LPI:M Yes [ ] Maximum 5 s

in the LPI mode
LP10 Scrambler and transmit 25.4a.7 LPI:M Yes [ ] The scrambler and transmit
functions deactivation time functions continue to operate
for the first 5 s following
tx_quiet = TRUE.
6
LP11 Transmitter output amplitude 25.4a.7 LPI:M Yes [ ] The transmitter output delivers
initial ramp up time a signal that exceeds
Signal_Detect assertion
threshold within 2 s when
tx_quiet is set to TRUE.
LP12 Transmitter output recovery 25.4a.7 LPI:M Yes [ ] The transmitter delivers a fully
time after a short Quiet state compliant signal promptly if
tx_quiet is set to FALSE less
than 5 s after being set to
TRUE.
LP13 Transmitter output recovery 25.4a.7 LPI:M Yes [ ] The transmitter delivers a fully
time after a long Quiet state compliant signal within 5 s if
tx_quiet is set to FALSE more
than 5 s after being set to
TRUE.
30. Management
30.2 Managed objects
Change Table 30-1b by appending the following (after aDeferControlStatus):
Table 301bCapabilities
D
T
E
Energy-Efficient Ethernet (optional)

oMACEntity managed object class (cond.)
aTransmitLPIMicroseconds ATTRIBUTE GET
aReceiveLPIMicroseconds ATTRIBUTE GET
aTransmitLPITransitions ATTRIBUTE GET
aReceiveLPITransitions ATTRIBUTE GET
aLDFastRetrainCount ATTRIBUTE GET
aLPFastRetrainCount ATTRIBUTE GET
30.2.5 Capabilities
Change Table 30-5 by appending the following:
Table 305LLDP Capabilities
LLDP EEE Remote Package (optional)

LLDP EEE Local Package (optional)
oLldpXdot3Config managed object class (30.12.1)
oLldpXdot3LocSystemsGroup managed object class (30.12.2)
aLldpXdot3LocTxTwSys ATTRIBUTE GET X
aLldpXdot3LocTxTwSysEcho ATTRIBUTE GET X
aLldpXdot3LocRxTwSys ATTRIBUTE GET X
aLldpXdot3LocRxTwSysEcho ATTRIBUTE GET X
aLldpXdot3LocFbTwSys ATTRIBUTE GET X
aLldpXdot3TxDllReady ATTRIBUTE GET X
aLldpXdot3RxDllReady ATTRIBUTE GET X
aLldpXdot3LocDllEnabled ATTRIBUTE GET X
oLldpXdot3RemSystemsGroup managed object class (30.12.3)
aLldpXdot3RemTxTwSys ATTRIBUTE GET X
aLldpXdot3RemTxTwSysEcho ATTRIBUTE GET X
aLldpXdot3RemRxTwSys ATTRIBUTE GET X
aLldpXdot3RemRxTwSysEcho ATTRIBUTE GET X
aLldpXdot3RemFbTwSys ATTRIBUTE GET X
30.3 Layer management for DTEs
30.3.1 MAC entity managed object class
30.3.1.1 MAC entity attributes
Insert the following new subclauses, 30.3.1.1.38 through 30.3.1.1.43, after 30.3.1.1.37:
30.3.1.1.38 aTransmitLPIMicroseconds
ATTRIBUTE
APPROPRIATE SYNTAX:
Generalized nonresetable counter. This counter has a maximum increment rate of 1 000 000
counts per second
BEHAVIOUR DEFINED AS:
A count reflecting the amount of time that the LPI_REQUEST parameter has the value ASSERT.
The request is indicated to the PHY according to the requirements of the RS (see 22.7a, 35.4a,
46.4a.).;
30.3.1.1.39 aReceiveLPIMicroseconds
ATTRIBUTE
APPROPRIATE SYNTAX:
Generalized nonresetable counter. This counter has a maximum increment rate of 1 000 000
counts per second
A count reflecting the amount of time that the LPI_INDICATION parameter has the value
ASSERT. The indication reflects the state of the PHY according to the requirements of the RS (see
22.7a, 35.4a, 46.4a.).;
30.3.1.1.40 aTransmitLPITransitions
ATTRIBUTE
APPROPRIATE SYNTAX:
Generalized nonresetable counter. This counter has a maximum increment rate of 50 000 counts
per second at 100 Mb/s; 90 000 counts per second at 1000 Mb/s; and 230 000 counts per second
at 10 Gb/s
A count of occurrences of the transition from state LPI_DEASSERTED to state LPI_ASSERTED
of the LPI transmit state diagram is the RS. The state transition corresponds to the assertion of the
LPI_REQUEST parameter. The request is indicated to the PHY according to the requirements of
the RS (see 22.7a, 35.4a, 46.4a.).;
30.3.1.1.41 aReceiveLPITransitions
ATTRIBUTE
APPROPRIATE SYNTAX:
Generalized nonresetable counter. This counter has a maximum increment rate of 50 000 counts
per second at 100 Mb/s; 90 000 counts per second at 1000 Mb/s; and 230 000 counts per second
at 10 Gb/s
A count of occurrences of the transition from DEASSERT to ASSERT of the LPI_INDICATE
parameter. The indication reflects the state of the PHY according to the requirements of the RS
(see 22.7a, 35.4a, 46.4a.).;
30.3.1.1.42 aLDFastRetrainCount
ATTRIBUTE
APPROPRIATE SYNTAX:
Generalized nonresetable counter. This counter has a maximum increment rate of 1000 counts per
second
A count of the number of 10GBASE-T fast retrains initiated by the local device. The indication
reflects the state of the PHY event counter (see 45.2.1.76a.2 and 55.4.5.1.).;
30.3.1.1.43 aLPFastRetrainCount
ATTRIBUTE
APPROPRIATE SYNTAX:
Generalized nonresetable counter. This counter has a maximum increment rate of 1000 counts per
second
A count of the number of 10GBASE-T fast retrains initiated by the link partner. The indication
reflects the state of the PHY event counter (see 45.2.1.76a.2 and 55.4.5.1.).;
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
Insert new subclause 30.5.1.1.21 after 30.5.1.1.20 as follows:
30.5.1.1.21 aEEESupportList
ATTRIBUTE
APPROPRIATE SYNTAX:
A SEQUENCE of ENUMERATIONS that match the syntax of aMAUType
A read-only list of the possible PHY types for which the underlying system supports Energy-
Efficient Ethernet (EEE) as defined in Clause 78. If Clause 28 or Clause 73 Auto-Negotiation is
present, then this attribute will map to the local technology ability or advertised ability of the local
device;
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
Insert new subclauses 30.12.2.1.14 through 30.12.2.1.21 after 30.12.2.1.13 as follows:
30.12.2.1.14 aLldpXdot3LocTxTwSys
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of Tw_sys_tx that the local system can support in the transmit
direction. This attribute maps to the variable LocTxSystemValue as defined in 78.4.2.3;
30.12.2.1.15 aLldpXdot3LocTxTwSysEcho
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of Tw_sys_tx that the remote system is advertising that it can
support in the transmit direction and is echoed by the local system under the control of the EEE
DLL receiver state diagram. This attribute maps to the variable LocTxSystemValueEcho as
defined in 78.4.2.3;
30.12.2.1.16 aLldpXdot3LocRxTwSys
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of Tw_sys_tx that the local system is requesting in the receive
direction. This attribute maps to the variable LocRxSystemValue as defined in 78.4.2.3;
30.12.2.1.17 aLldpXdot3LocRxTwSysEcho
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of Tw_sys_tx that the remote system is advertising that it is
requesting in the receive direction and is echoed by the local system under the control of the EEE
DLL transmitter state diagram. This attribute maps to the variable LocRxSystemValueEcho as
30.12.2.1.18 aLldpXdot3LocFbTwSys
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of the fallback Tw_sys_tx that the local system is advertising
to the remote system. This attribute maps to the variable LocFbSystemValue as defined in
78.4.2.3;
30.12.2.1.19 aLldpXdot3TxDllReady
ATTRIBUTE
APPROPRIATE SYNTAX:
A BOOLEAN value:
FALSE: Local system has not completed initialization of the EEE transmit Data Link
Layer management function and is not ready to receive/transmit an LLDPDU
containing a EEE TLV.
TRUE: Local system has initialized the EEE transmit Data Link Layer management
function and is ready to receive/transmit an LLDPDU containing a EEE TLV.
A GET operation returns the initialization status of the EEE transmit Data Link Layer management
function on the local system.;
30.12.2.1.20 aLldpXdot3RxDllReady
ATTRIBUTE
APPROPRIATE SYNTAX:
A BOOLEAN value:
FALSE: Local system has not completed initialization of the EEE receive Data Link
Layer management function and is not ready to receive/transmit an LLDPDU
containing a EEE TLV.
TRUE: Local system has initialized the EEE receive Data Link Layer management
function and is ready to receive/transmit an LLDPDU containing a EEE TLV.
A GET operation returns the initialization status of the EEE receive Data Link Layer management
function on the local system.;
30.12.2.1.21 aLldpXdot3LocDllEnabled
ATTRIBUTE
APPROPRIATE SYNTAX:
A BOOLEAN value:
FALSE: Local system has not completed auto-negotiation with a link partner that has
indicated at least one EEE capability.
TRUE: Local system has completed auto-negotiation with a link partner that has indi-
cated at least one EEE capability.
A GET operation returns the status of the EEE capability negotiation on the local system.;
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
Insert new subclauses 30.12.3.1.14 through 30.12.3.1.18 after 30.12.3.1.13 as follows:
30.12.3.1.14 aLldpXdot3RemTxTwSys
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER

A GET attribute that returns the value of Tw_sys_tx that the remote system can support in the
transmit direction. This attribute maps to the variable RemTxSystemValue as defined in 78.4.2.3;
30.12.3.1.15 aLldpXdot3RemTxTwSysEcho
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of Tw_sys_tx that the local system is advertising that it can
support in the transmit direction as echoed by the remote system under the control of the EEE DLL
receiver state diagram. This attribute maps to the variable RemTxSystemValueEcho as defined in
78.4.2.3;
30.12.3.1.16 aLldpXdot3RemRxTwSys
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of Tw_sys_tx that the remote system is requesting in the
receive direction. This attribute maps to the variable RemRxSystemValue as defined in 78.4.2.3;
30.12.3.1.17 aLldpXdot3RemRxTwSysEcho
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of Tw_sys_tx that the local system is advertising that it is
requesting in the receive direction as echoed by the remote system under the control of the EEE
DLL transmitter state diagram. This attribute maps to the variable RemRxSystemValueEcho as
30.12.3.1.18 aLldpXdot3RemFbTwSys
ATTRIBUTE
APPROPRIATE SYNTAX:
INTEGER
A GET attribute that returns the value of fallback Tw_sys_tx that the remote system is advertising.
This attribute maps to the variable RemFbSystemValue as defined in 78.4.2.3;
35. Reconciliation Sublayer (RS) and Gigabit Media Independent Interface

(GMII)
35.1 Overview
Insert item h) into the lettered list in 35.1.1 as follows:
35.1.1 Summary of major concepts
h) The GMII may also support Low Power Idle (LPI) signaling as defined for Energy-Efficient
Ethernet in Clause 78 for certain PHY types.
35.2 Functional specifications
35.2.1 Mapping of GMII signals to PLS service primitives and Station Management
The Reconciliation sublayer maps the signals provided at the GMII to the PLS service primitives defined in
Clause 6. The PLS service primitives provided by the Reconciliation sublayer behave, as described here, in
exactly the same manner as defined in Clause 6. The mapping is changed for EEE capability (see 78.3), as
described in 35.3a.
An LPI_IDLE.request primitive with value ASSERT shall not be generated unless the attached link is
operational (i.e., link_status = OK, according to the underlying PCS/PMA). The PHY shall not cause an
LP_IDLE.request primitive with value ASSERT to be generated for at least one second following a
link_status change to OK (see 78.1.2.1.2).
EEE capability requires the use of the MAC defined in Annex 4A for simplified full duplex operation (with
carrier sense deferral). This provides full duplex operation but uses the carrier sense signal to defer
transmission when the PHY is in its low power state.
Figure 352 depicts a schematic view of the Reconciliation sublayer inputs and outputs, and demonstrates
that the GMII management interface is controlled by the station management entity (STA).
Change 35.2.2 to show LPI signaling as follows:
35.2.2 GMII signal functional specifications
35.2.2.1 GTX_CLK (1000 Mb/s transmit clock)
Insert a NOTE at the end of 35.2.2.1 as follows:
NOTEFor EEE capability, GTX_CLK may be halted according to 35.2.2.5a.
35.2.2.2 RX_CLC (receive clock)
Insert a NOTE at the end of 35.2.2.2 as follows:
NOTEFor EEE capability, RX_CLK may be halted during periods of low utilization according to 35.2.2.8a.
IEEE Std 802.3az-2010 AMENDMENT TO IEEE STD 802.3-2008: CSMA/CD
Change 35.2.2.4 as follows:
35.2.2.4 TXD (transmit data)
TXD is a bundle of eight data signals (TXD<7:0>) that are driven by the Reconciliation sublayer.
TXD<7:0> shall transition synchronously with respect to the GTX_CLK. For each GTX_CLK period in
which TX_EN is asserted and TX_ER is de-asserted, data are presented on TXD<7:0> to the PHY for
transmission. TXD<0> is the least significant bit. While TX_EN and TX_ER are both de-asserted,
TXD<7:0> shall have no effect upon the PHY.
While TX_EN is de-asserted and TX_ER is asserted, TXD<7:0> are used to request the PHY to generate
LPI, Carrier Extend or Carrier Extend Error code-groups. The use of TXD<7:0> during the transmission of a
frame with carrier extension is described in 35.2.2.5. Carrier extension shall only be signaled immediately
following the data portion of a frame. The use of TXD<7:0> to signal LPI transitions is described in
35.2.2.5a.
For EEE capability, the RS shall use the combination of TX_EN de-asserted, TX_ER asserted, and
TXD<7:0> equal to 0x01 as shown in Table 351 as a request to enter, or remain in the LPI state. Transition
into and out of the LPI state is shown in Figure 357a.
Table 351 specifies the permissible encodings of TXD<7:0>, TX_EN, and TX_ER.
Table 351Permissible encodings of TXD<7:0>, TX_EN, and TX_ER
PLS_DATA.request
TX_EN TX_ER TXD<7:0> Description
parameter
0 0 00 through FF Normal interframe TRANSMIT_COMPLETE

0 1 00 Reserved
0 1 01 Assert LPI
0 1 02 through 0E Reserved
0 1 0F Carrier Extend EXTEND (eight bits)
0 1 1F Carrier Extend Error EXTEND_ERROR (eight bits)
0 1 20 through FF Reserved
1 0 00 through FF Normal data transmission ZERO, ONE (eight bits)
1 1 00 through FF Transmit error propagation No applicable parameter
NOTEValues in TXD<7:0> column are in hexadecimal.
35.2.2.5 TX_ER (transmit coding error)
35.2.2.5a Transmit direction LPI transition
EEE capability and the LPI client are described in 78.1. The LPI client requests the PHY to transition to its
low power state by asserting TX_ER and setting TXD<7:0> to 0x01. The LPI client maintains the same state
for these signals for the entire time that the PHY is to remain in the low power state.
The LPI client may halt GTX_CLK at any time more than 9 clock cycles after the start of the LPI state as
shown in Figure 357a if and only if the Clock stop capable bit is asserted (45.2.3.1.3a).
The LPI client requests the PHY to transition out of its low power state by de-asserting TX_ER and TXD.
The LPI client should not assert TX_EN for valid transmit data until after the wake-up time specified for the
PHY.
Figure 357a shows the behavior of TX_EN, TX_ER and TXD<7:0> during the transition into and out of
the LPI state.
at least 9 clock cycles
GTX_CLK
TX_EN
0x01 x x x x
TXD<7:0>
wake time
TX_ER enter low exit low

power idle power idle
mode mode
Change the second paragraph and insert a new paragraph in 35.2.2.7 as follows:
35.2.2.7 RXD (receive data)
While RX_DV is de-asserted, the PHY may provide a False Carrier indication by asserting the RX_ER
signal while driving the specific value listed in Table 352 onto RXD<7:0>. See 36.2.5.2.3 for a description
of the conditions under which a PHY will provide a False Carrier indication. LPI transitions are described in
35.2.2.8a.
While RX_DV is de-asserted, the PHY may indicate that it is receiving LPI by asserting the RX_ER signal
while driving the value 0x01 onto RXD<7:0>.
Table 352 specifies the permissible encoding of RXD<7:0>, RX_ER, and RX_DV, along with the specific
indication provided by each code that shall be interpreted by the RS.
Table 352Permissible encoding of RXD<7:0>, RX_ER, and RX_DV
RX_DV RX_ER RXD<7:0> Description PLS_DATA.indication parameter
0 0 00 through FF Normal interframe No applicable parameter
0 1 00 Normal interframe No applicable parameter
0 1 01 Assert LPI No applicable parameter
0 1 01 through 0D Reserved
0 1 02 through 0D Reserved
0 1 0E False Carrier indication No applicable parameter
0 1 0F Carrier Extend EXTEND (eight bits)
0 1 1F Carrier Extend Error ZERO, ONE (eight bits)
0 1 20 through FF Reserved
1 0 00 through FF Normal data reception ZERO, ONE (eight bits)
1 1 00 through FF Data reception error ZERO, ONE (eight bits)
NOTEValues in RXD<7:0> column are in hexadecimal.
35.2.2.8 RX_ER (receive error)
35.2.2.8a Receive direction LPI transition
EEE capability and the LPI client are described in 78.1. When the PHY receives signals from the link
partner indicating LPI, it signals this to the LPI client by asserting RX_ER and setting RXD<7:0> to 0x01
while keeping RX_DV de-asserted. The PHY maintains these signals in this state while it remains in the low
power state. When the PHY receives signals from the link partner indicating its transition out of the low
power state, it signals this to the LPI client by de-asserting RX_ER and returning to normal interframe
encoding.
While the PHY device is indicating LPI, the PHY device may halt the RX_CLK as shown in Figure 3512a
if and only if the Clock stop enable bit is asserted (see 45.2.3.1.3a). The PHY may restart RX_CLK at any
time while it is asserting LPI, but shall restart RX_CLK so that at least one positive transition occurs before
it de-asserts LPI.
Figure 3512a shows the behavior of RX_ER, RX_DV, and RXD<7:0> during LPI transitions.
RX_CLK
RX_DV
0x01 x x x x
RXD<7:0>
wake time
RX_ER enter low exit low

mode mode
Figure 3512aLPI transitions (receive)
35.3 Signal mapping
Insert a subclause 35.3a after 35.3 as follows:
35.3a LPI Assertion and Detection
Certain PHYs support Energy-Efficient Ethernet (see Clause 78). PHYs with EEE capability support LPI
assertion and detection. LPI operation and the LPI client are described in 78.1. LPI signaling allows the LPI
client to signal to the PHY and to the link partner that a break in the data stream is expected and components
may use this information to enter power-saving modes that require additional time to resume normal
operation. Similarly, it allows the LPI client to understand that the link partner has sent such an indication.
GMII signals as shown in Figure 3516a.
The definition of TX_EN, TX_ER and TXD<7:0> is derived from the state of PLS_DATA.request
(35.2.1.1), except when it is overridden by an assertion of LP_IDLE.request.
Similarly, RX_ER and RXD<7:0> are mapped to PLS_DATA.indication except when LP_IDLE is
detected
CRS is mapped to PLS_CARRIER.indication except when LP_IDLE.request is asserted or the wake
timer has yet to expire.
state diagram.
PLS_Service Primitives GMII Signals

Reconciliation sublayer
TX_ER
LP_IDLE.request
re-mapping for LPI TXD<7:0>
PLS_DATA.request TX_EN
GTX_CLK
MAC
RXD<7:0>
re-mapping for LPI
RX_CLK
LP_IDLE.indication CRS
or if LPI_REQUEST=ASSERT within 1 s of the change of link_status to OK.
This wake-up time is enforced by the transmit LPI state diagram and the rules mapping
CARRIER_SENSE.indication defined in 35.2.1. The implementation shall conform to the behavior
described by the transmit LPI state diagram shown in Figure 3516b.
35.3a.2.1 Conventions
The notation used in the state diagram follows the conventions of 34.2.
rs_reset + power_on
LPI_DEASSERTED
tw_timer 0
CARRIER_STATUS OFF
LPI_REQUEST = ASSERT.
LPI_ASSERTED
CARRIER_STATUS ON
LPI_WAIT
start_tw_timer
tw_timer_done
Figure 3516bTransmit LPI state diagram
power_on
rs_reset
TRUE: Reset the RS.
tw_timer
A timer that counts the time since the de-assertion of LPI. The terminal count of the timer is the
value of the resolved Tw_sys_tx as defined in 78.2 and 78.4. The minimum value of Tw_sys_tx shall
be 16.5 s for 1000BASE-T and 13.26 s for 1000BASE-KX. Signal tw_timer_done is asserted on
reaching its terminal count.
while it is detecting LP_IDLE on the GMII. The receive system should be aware that data frames may arrive
at the GMII following the de-assertion of LPI_INDICATION with a delay corresponding to the link
partners resolved Tw_sys_rx (as specified in 78.5) time, in microseconds.
Reconciliation Sublayer (RS) and Gigabit Media Independent Interface (GMII)7
Insert the following row at the end of the table in 35.5.2.3:
Item Feature Subclause Value/Comment Status Support
*LPI Implementation of LPI 35.2.2 O Yes [ ]

No [ ]
35.5.3 PICS proforma tables for reconciliation sublayer and Gigabit Media independent
interface
35.5.3.3 Data stream structure
Insert the new subclause 35.5.3.3a after 35.5.3.3 as follows:
L1 Assertion of LPI in Tx 35.2.2.4 As defined in Table 351 LPI:M Yes [ ]

direction
L2 Assertion of LPI in Rx 35.2.2.7 As defined in Table 352 LPI:M Yes [ ]

direction
L3 GTX_CLK stoppable during 35.2.2.5a At least 9 cycles after LPI LPI:O Yes [ ]
LPI assertion
L4 RX_CLK stoppable during 35.2.2.8a LPI:O Yes [ ]

LPI
L5 Terminal count for tw_timer 35.3a.2.2 Based on resolved Tw_sys_tx LPI:M Yes [ ]
7

(PMA) sublayer, type 1000BASE-X
36.2.4 8B/10B transmission code
Change 36.2.4.7 for LPI signaling as follows:
36.2.4.7 Ordered_sets
Eight ordered_sets, consisting of a single special code-group or combinations of special and data code-
groups are specifically defined. Ordered_sets which include /K28.5/ provide the ability to obtain bit and
code-group synchronization and establish ordered_set alignment (see 36.2.4.9 and 36.3.2.4). Ordered_sets
provide for the delineation of a packet and synchronization between the transmitter and receiver circuits at
opposite ends of a link. Table 363 lists the defined ordered_sets. Certain PHYs include an option (see 78.3)
to transmit or receive /LI/, /LI1/ and /LI2/ to support Energy-Efficient Ethernet (see Clause 78).
Insert the following rows into Table 36-3, below row /I2/:
Table 363Defined ordered_sets
Number of
Code Ordered_Set Encoding
Code-Groups
/LI/ LPI Correcting /LI1/, Preserving /LI2/

/LI1/ LPI 1 2 /K28.5/D6.5/
/LI2/ LPI 2 2 /K28.5/D26.4/
36.2.4.12 IDLE (/I/)
Insert a new subclause 36.2.4.12a after 36.2.4.12 to describe LPI signaling as follows:
36.2.4.12a Low Power Idle (LPI)
LPI is transmitted in the same manner as IDLE. LPI ordered sets (\LI\) are transmitted continuously and
repetitively whenever the GMII is indicating Assert LPI. See 35.2.2.5a and 35.2.2.8a for corresponding
GMII definitions.
36.2.5 Detailed functions and state diagrams
36.2.5.1 State variables
Insert new constants into 36.2.5.1.2 at the end of the existing subclause as follows:
36.2.5.1.2 Constants
The following constant is used only for the EEE capability:
/LI/
The LP_IDLE ordered_set group, comprising either the /LI1/ or /LI2/ ordered_sets, as specified in
36.2.4.12a.
36.2.5.1.3 Variables
Change the definition in 36.2.5.1.3 for sync_status and insert a NOTE as follows:
sync_status
A parameter set by the PCS Synchronization process to reflect the status of the link as viewed by
the receiver. The values of the parameter are defined for code_sync_status. The equation for this
parameter is:
sync_status = code_sync_status + rx_lpi_active
Values: FAIL; The receiver is not synchronized to code-group boundaries.

OK; The receiver is synchronized to code-group boundaries.
NOTEIf EEE is not supported, the variable rx_lpi_active is always false, and this variable is identical to
code_sync_status controlled by the synchronization state diagram.
Insert new variables into 36.2.5.1.3 at the end of the existing subclause as follows:
The following variables are used only for the EEE capability:
assert_lpidle
Alias used for the optional LPI function, consisting of the following terms:
(TX_EN=FALSE * TX_ER=TRUE * (TXD<7:0>=0x01))
code_sync_status
A parameter set by the PCS Synchronization process to reflect the status of the link as viewed by
the receiver.
Values: FAIL; The receiver is not synchronized to code-group boundaries.

OK; The receiver is synchronized to code-group boundaries.
idle_d
Alias for the following terms:
SUDI( ![/D21.5/] * ![/D2.2/])

that uses an alternate form to support the EEE capability:
SUDI(![/D21.5/] * ![/D2.2/] * ![/D6.5/] * ![/D26.4/] )
rx_lpi_active
A Boolean variable that is set to TRUE when the receiver is in a low power state and set to FALSE
when it is in an active state and capable of receiving data.
rx_quiet
A Boolean variable set to TRUE while in the RX_QUIET state and set to FALSE otherwise.
tx_quiet
A Boolean variable set to TRUE when the transmitter is in the TX_QUIET state and set to FALSE
otherwise. When set to TRUE, the PMD will disable the transmitter as described in 70.6.5.
Insert new counters into 36.2.5.1.5 at the end of the existing subclause as follows:
36.2.5.1.5 Counters
The following counter is used only for the EEE capability:
wake_error_counter
A counter that is incremented each time that the LPI receive state diagram enters the RX_WTF
state indicating that a wake time fault has been detected. The counter is reflected in register 3.22
(see 45.2.3.8b).
Insert new messages into 36.2.5.1.6 at the end of the existing subclause and change the heading as
follows:
36.2.5.1.6 Messages
The following messages are used only for the EEE capability:
A signal sent by the PCS/PMA LPI receive state diagram to the PMD. Note that this message is
ignored by devices that do not support EEE capability.
Values: TRUE: The receiver is in a quiet state and is not expecting incoming data.
FALSE: The receiver is ready to receive data.
PMD_TXQUIET.request(tx_quiet)
A signal sent by the PCS/PMA LPI transmit state diagram to the PMD. Note that this message is
ignored by devices that do not support the optional LPI mechanism.
Values: TRUE: The transmitter is in a quiet state and may cease to transmit a signal on the
medium.
FALSE: The transmitter is ready to transmit data.
Insert new timers into 36.2.5.1.7 at the end of the existing subclause and change the heading as follows:
36.2.5.1.7 Timers
The following timers are used only for the EEE capability:
rx_tq_timer
This timer is started when the PCS receiver enters the START_TQ_TIMER state. The timer
terminal count is set to TQR. When the timer reaches terminal count, it will set the
rx_tq_timer_done = TRUE.
rx_tw_timer
This timer is started when the PCS receiver enters the RX_WAKE state. The timer terminal count
shall not exceed the maximum value of TWR in Table 363b. When the timer reaches terminal
count, it will set the rx_tw_timer_done = TRUE.
rx_wf_timer
This timer is started when the PCS receiver enters the RX_WTF state, indicating that the receiver
has encountered a wake time fault. The rx_wf_timer allows the receiver an additional period in
which to synchronize or return to the quiescent state before a link failure is indicated. The timer
terminal count is set to TWTF. When the timer reaches terminal count, it will set the
rx_wf_timer_done = TRUE.
tx_ts_timer
This timer is started when the PCS transmitter enters the TX_SLEEP state. The timer terminal
count is set to TSL. When the timer reaches terminal count, it will set the tx_ts_timer_done =
TRUE.
tx_tq_timer
This timer is started when the PCS transmitter enters the TX_QUIET state. The timer terminal
count is set to TQL. When the timer reaches terminal count, it will set the tx_tq_timer_done =
TRUE.
tx_tr_timer
This timer is started when the PCS transmitter enters the TX_REFRESH state. The timer terminal
count is set to TUL. When the timer reaches terminal count, it will set the tx_tr_timer_done =
TRUE.
36.2.5.2.1 Transmit
Change Figure 365 (new states and transitions are in dotted boxes) and Figure 366 in 36.2.5.2.1 as
follows:
power_on=TRUE + TX_EN=FALSE
mr_main_reset=TRUE + TX_ER=FALSE
(xmitCHANGE=TRUE xmit=DATA
TX_OSET.indicate tx_even=FALSE) A C TX_EN=FALSE
TX_OSET.indicate TX_EN=TRUE
TX_ER=TRUE
TX_TEST_XMIT
transmitting FALSE XMIT_DATA ALIGN_ERR_START
COL FALSE tx_o_set /I/

xmit= TX_OSET.indicate
CONFIGURATION B
assert_lpidle * START_ERROR
CONFIGURATION TX_OSET.indicate transmitting TRUE
TX_EN=TRUE COL receiving
tx_o_set /C/
TX_ER=FALSE tx_o_set /S/
TX_OSET.indicate
xmit=IDLE + (xmit=DATA TX_OSET.indicate
(TX_EN=TRUE + TX_ER=TRUE))
IDLE START_OF_PACKET
tx_o_set /I/ transmitting TRUE TX_DATA_ERROR
COL receiving
xmit=DATA TX_OSET.indicate COL receiving
tx_o_set /S/
TX_EN=FALSE TX_ER=FALSE tx_o_set /V/
TX_OSET.indicate TX_OSET.indicate
TX_DATA
TX_PACKET
COL receiving
tx_o_set VOID(/D/) TX_EN=FALSE
TX_ER=TRUE
TX_OSET.indicate
TX_EN=TRUE
END_OF_PACKET_EXT
COL receiving
TX_EN=FALSE TX_ER=FALSE tx_o_set VOID(/T/)
TX_ER=FALSE
END_OF_PACKET_NOEXT TX_OSET.indicate TX_ER=TRUE
TX_OSET.indicate
IF (tx_even=FALSE)
THEN TX_EN=FALSE
transmitting FALSE TX_ER=TRUE
EXTEND_BY_1 TX_OSET.indicate
COL FALSE
tx_o_set /T/ IF (tx_even=FALSE)
THEN
TX_OSET.indicate CARRIER_EXTEND
transmitting FALSE
COL FALSE COL receiving
tx_o_set /R/ tx_o_set VOID(/R/)
EPD2_NOEXT
TX_OSET.indicate
transmitting FALSE
tx_o_set /R/ TX_EN=FALSE
TX_ER=FALSE TX_EN=TRUE
tx_even=FALSE tx_even=TRUE TX_ER=FALSE
TX_OSET.indicate
TX_OSET.indicate A TX_OSET.indicate TX_OSET.indicate
B
TX_EN=TRUE
EPD3 TX_ER=TRUE
TX_OSET.indicate
tx_o_set /R/ XMIT_LPIDLE
TX_OSET.indicate tx_o_set /LI/
C
!assert_lpidle * assert_lpidle *
TX_OSET.indicate TX_OSET.indicate
NOTETransitions B and C are only required for the EEE capability.
Figure 365PCS transmit ordered_set state diagram
power_on=TRUE + mr_main_reset=TRUE
CONFIGURATION_C1A
tx_code-group /K28.5/ GENERATE_CODE_GROUPS
tx_even TRUE
PUDR
tx_o_set=/D/
cg_timer_done
tx_o_set= tx_o_set=/C/
/V/ + /S/ + /T/ + /R/
CONFIGURATION_C1B
SPECIAL_GO
tx_code-group /D21.5/
tx_code-group tx_o_set
tx_even FALSE
PUDR tx_even ! tx_even tx_o_set=/I/ + /LI/
TX_OSET.indicate
cg_timer_done PUDR
CONFIGURATION_C1C cg_timer_done
tx_code-group ENCODE
(tx_Config_Reg<D7:D0>) IDLE_DISPARITY_TEST
tx_even TRUE
PUDR tx_disparity= tx_disparity=
DATA_GO
cg_timer_done POSITIVE NEGATIVE
tx_code-group
ENCODE(TXD<7:0>) IDLE_DISPARITY_WRONG
CONFIGURATION_C1D
tx_even ! tx_even tx_code-group /K28.5/
tx_code-group ENCODE TX_OSET.indicate tx_even TRUE
(tx_Config_Reg<D15:D8>) PUDR PUDR
tx_even FALSE
TX_OSET.indicate cg_timer_done
cg_timer_done
PUDR
IDLE_I1B
tx_o_set/C/
cg_timer_done if tx_oset=/LI/
then (tx_code-group /D6.5/)
tx_o_set=/C/
else (tx_code-group /D5.6/)
cg_timer_done
tx_even FALSE
TX_OSET.indicate
CONFIGURATION_C2A PUDR
tx_code-group /K28.5/
cg_timer_done
tx_even TRUE
PUDR
cg_timer_done
IDLE_DISPARITY_OK
CONFIGURATION_C2B
tx_code-group /K28.5/
tx_code-group /D2.2/ tx_even TRUE
tx_even FALSE PUDR
PUDR
cg_timer_done cg_timer_done
CONFIGURATION_C2C IDLE_I2B
tx_code-group ENCODE if tx_oset=/LI/

(tx_Config_Reg<D7:D0>) then (tx_code-group /D26.4/)
tx_even TRUE else (tx_code-group /D16.2/)
PUDR tx_even FALSE
TX_OSET.indicate
cg_timer_done PUDR
CONFIGURATION_C2D cg_timer_done
tx_code-group ENCODE
(tx_Config_Reg<D15:D8>)
tx_even FALSE
TX_OSET.indicate
PUDR
cg_timer_done
Figure 366PCS transmit code-group state diagram
36.2.5.2.2 Receive
Change Figure 367a (new states and transitions are in dotted boxes), and insert Figure 367c in
36.2.5.2.2 as follows:
sync_status=FAIL SUDI G
LINK_FAILED
power_on=TRUE
mr_main_reset=TRUE rx_lpi_active FALSE;
IF xmitzDATA,
THEN RUDI(INVALID)
IF receiving=TRUE,
THEN
receiving FALSE;
RX_ER TRUE.
ELSE
RX_DV FALSE;
RX_ER FALSE.
SUDI
WAIT_FOR_K
receiving FALSE
RX_DV FALSE
RX_ER FALSE
SUDI([/K28.5/] EVEN)
B
RX_K
receiving FALSE
(xmitzDATA
RX_DV FALSE
SUDI(>/D/] [/D21.5/] [/D2.2/])) +
RX_ER FALSE
(xmit DATA idle_d )
D SUDI([/D21.5/] [/D2.2/]) SUDI([/D21.5/] [/D2.2/])) C
RX_CB SUDI>/D/]) IDLE_D

xmitzDATA E receiving FALSE
receiving FALSE
RX_DV FALSE RX_DV FALSE
xmit DATA
RX_ER FALSE RX_ER FALSE
(SUDI([/D6.5/] +
rx_lpi_active FALSE [/D26.4/])) RUDI(/I/)
rx_lpi_active FALSE
SUDI>/D/]) SUDI>/D/])
SUDI([/K28.5/]) SUDI xmit DATA

RX_CC xmitzDATA carrier_detect FALSE +
rx_Config_Reg<D7:D0> SUDI([/K28.5/])
DECODE([/x/])
SUDI xmit DATA
SUDI>/D/]) SUDI>/D/]) carrier_detect TRUE
CARRIER_DETECT
RX_CD
rx_Config_Reg<D15:D8> receiving TRUE
DECODE([/x/]) ![/S/] [/S/]
RUDI/C/) A
SUDI(![/K28.5/] + ODD) F
FALSE_CARRIER
RX_ER TRUE
RX_INVALID
RXD<7:0> 0000 1110
IF xmit=CONFIGURATION
THEN RUDI(INVALID)
IF xmit=DATA THEN receiving TRUE
rx_lpi_active FALSE
SUDI(!([/K28.5/] EVEN))
NOTEOutgoing arcs leading to labeled polygons flow offpage to corresponding incoming arcs leading
from labeled circles on Figure 367b and Figure 367c, and vice versa.
Figure 367aPCS receive state diagram, part a
START_OF_PACKET
RX_DV TRUE
RX_ER FALSE
RXD<7:0> 0101 0101
SUDI
RECEIVE
check_end=(/K28.5/D/K28.5/ +
/K28.5/(D21.5 + D2.2)/D0.0/) * ELSE
EVEN
EARLY_END RX_DATA_ERROR
RX_ER TRUE RX_ER TRUE
SUDI(![/D21.5/] SUDI([/D21.5/] + SUDI
![/D2.2/]) C D [/D2.2/])
EVEN
check_end=/T/R/K28.5/ [/D/]
TRI+RRI RX_DATA
receiving FALSE RX_ER FALSE
RX_DV FALSE RXD<7:0> DECODE([/x/])
RX_ER FALSE
SUDI
SUDI([/K28.5/])
B
check_end=/T/R/R/ check_end=/R/R/R/
TRR+EXTEND EARLY_END_EXT
RX_DV FALSE RX_ER TRUE
RX_ER TRUE
SUDI
RXD<7:0> 0000 1111
SUDI SUDI(![/S/] !([/K28.5/] EVEN))
EPD2_CHECK_END
check_end=/R/R/R/ ELSE
check_end=/R/R/K28.5/ EVEN
EXTEND_ERR
check_end=/R/R/S/
RX_DV FALSE
RXD<7:0> 0001 1111
PACKET_BURST_RRS
RX_DV FALSE B
SUDI([/S/])
RXD<7:0> 0000 1111
SUDI([/S/])
NOTE 1Outgoing arcs leading to labeled polygons flow offpage to corresponding incoming arcs leading
from labeled circles on Figure 367a, and vice versa.
NOTE 2In the transition from RECEIVE to RX_DATA state the transition condition is a test against the
code-group obtained from the SUDI that caused the transition to RECEIVE state.
Figure 367bPCS receive state diagram, part b
RX_SLEEP
rx_lpi_active TRUE
receiving FALSE
J RX_DV FALSE
RX_ER TRUE
RXD 0000 0001
START_TQ_TIMER
Start rx_tq_timer UCT
UCT
LP_IDLE_D signal_detect=OK *
!rx_tq_timer_done *
(xmit=DATA SUDI +
signal_detect=OK * SUDI( [/K28.5/] ) )
rx_tq_timer_done H
signal_detect=OK * LPI_K
!rx_tq_timer_done * F signal_detect=FAIL
xmitDATA
SUDI( ![/K28.5/] )
signal_detect=FAIL
signal_detect=OK *
D
signal_detect=OK * (xmitDATA
RX_QUIET SUDI([/D21.5/] + [/D2.2/]) SUDI([/D/]![/D21.5/]![/D2.2/]
rx_quiet TRUE ![/D5.6/]![/D16.2/]) +
signal_detect=OK * F xmit=DATA
xmitDATA SUDI(![/D21.5/]![/D2.2/]*![/D5.6/]*
SUDI( [/D/]) ![/D16.2/]*![/D6.5)]*![D26.4]))
signal_detect=OK
J signal_detect=OK *
I
xmit=DATA
signal_detect=FAIL * SUDI([/D6.5/] + [/D26.4/])
RX_WAKE rx_tq_timer_done
rx_quiet FALSE
Start rx_tw_timer
C signal_detect=OK *
SUDI([/D5.6/] + [/D16.2/])
signal_detect=OK *
signal_detect=FAIL
rx_tw_timer_done
RX_WTF
wake_error_counter++ signal_detect=OK *
Start rx_wf_timer signal_detect=OK *
!rx_wf_timer_done * !rx_tw_timer_done *
code_sync_status = OK * code_sync_status = OK *
signal_detect=FAIL SUDI( [/K28.5/]*EVEN ) SUDI( [/K28.5/]*EVEN )
I signal_detect=OK *
rx_wf_timer_done
RX_LINK_FAIL RX_WAKE_DONE
rx_quiet FALSE Start rx_tq_timer
rx_lpi_active FALSE
SUDI UCT
G H
NOTEOutgoing arcs leading to labeled polygons flow off page to corresponding incoming arcs leading
from labeled circles on Figure 367a, and vice versa.
Figure 367cPCS Receive state diagram, part c

(only required for the optional EEE capability)
36.2.5.2.6 Synchronization
Insert the following paragraph between the third and fourth paragraphs of 36.2.5.2.6:
For EEE capability the relationship between sync_status and code_sync_status is given by Figure 367c;
otherwise sync_status is identical to code_sync_status.
Change Figure 369 as follows:
power_on=TRUE + mr_main_reset=TRUE +
(signal_detectCHANGE=TRUE
mr_loopback=FALSE PUDI)
LOSS_OF_SYNC
code_sync_status FAIL
rx_even ! rx_even
(PUDI signal_detect=FAIL
SUDI
mr_loopback=FALSE) +
PUDI(![/COMMA/]) (signal_detect=OK + mr_loopback=TRUE)
PUDI([/COMMA/])
COMMA_DETECT_1
rx_even TRUE
SUDI
PUDI(![/D/]) PUDI([/D/])
ACQUIRE_SYNC_1
PUDI(![/COMMA/] [/INVALID/])
rx_even ! rx_even
SUDI
cgbad
rx_even=FALSE PUDI([/COMMA/])
COMMA_DETECT_2
rx_even TRUE
SUDI
PUDI(![/D/]) PUDI([/D/])
ACQUIRE_SYNC_2
PUDI(![/COMMA/] [/INVALID/])
rx_even ! rx_even
SUDI
cgbad
rx_even=FALSE PUDI([/COMMA/])
COMMA_DETECT_3
rx_even TRUE SYNC_ACQUIRED_1
SUDI
code_sync_status OK
PUDI(![/D/]) PUDI([/D/]) rx_even ! rx_even
SUDI
cgbad
2
cggood
cggood
SYNC_ACQUIRED_2 SYNC_ACQUIRED_2A
rx_even ! rx_even rx_even ! rx_even cggood
SUDI SUDI good_cgs 3
good_cgs 0 good_cgs good_cgs + 1
cgbad
cgbad good_cgs = 3 cggood
3
cggood
cgbad
cgbad
2 cggood good_cgs = 3
cggood
cgbad
cgbad
3 cggood good_cgs = 3
Figure 369Synchronization state diagram
Insert two new subclauses (36.2.5.2.8 and 36.2.5.2.9) after 36.2.5.2.7 as follows:
36.2.5.2.8 LPI state diagram
A PCS that supports the EEE capability shall implement the LPI transmit process as shown in Figure 369a.
The transmit LPI state diagram controls tx_quiet, which disables the transmitter when true.
power_on=TRUE +
mr_main_reset=TRUE +
xmitDATA
TX_ACTIVE
tx_quiet FALSE
TX_OSET.indicate *
TX_OSET.indicate * tx_oset /LI/
tx_oset = /LI/
TX_SLEEP
Start tx_ts_timer
TX_OSET.indicate *
tx_oset /LI/
TX_OSET.indicate * tx_oset = /LI/ *

tx_ts_timer_done
TX_QUIET
tx_quiet TRUE
Start tx_tq_timer
TX_OSET.indicate *
tx_oset /LI/
TX_OSET.indicate * tx_oset = /LI/ *
tx_tq_timer_done
TX_REFRESH
tx_quiet FALSE
Start tx_tr_timer
TX_OSET.indicate *
TX_OSET.indicate * tx_oset = /LI/ * tx_oset /LI/
tx_tr_timer_done
Figure 369aLPI Transmit state diagram
The timer values for these state diagrams are shown in Table 363a for transmit and Table 363b for receive.
Table 363aTransmitter LPI timing parameters
Parameter Description Min Max Units
TSL Local Sleep Time from entering the TX_SLEEP state to when tx_quiet is 19.9 20.1 s
set to TRUE
TQL Local Quiet Time from when tx_quiet is set to TRUE to entry into the 2.5 2.6 ms
TX_REFRESH state
TUL Local Refresh Time from entry into the TX_REFRESH state to entry into 19.9 20.1 s
the TX_QUIET state
Table 363bReceiver LPI timing parameters
TQR The time the receiver waits for signal detect to be set to OK while in the 3 4 ms
LP_IDLE_D, LPI_K and RX_QUIET states before asserting a rx_fault
TWR Time the receiver waits in the RX_WAKE state before indicating a wake 11 s
time fault (WTF)
TWTF Wake time fault recovery time 1 ms
36.2.5.2.9 LPI status and management
For EEE capability, the PCS indicates to the management system that LPI is currently active in the receive
and transmit directions using the status variables shown in Table 363c.
Table 363cMDIO status indications
Register
MDIO status variable Register name Note
address
Tx LPI received PCS status register 1 3.1.11 Latched version of 3.1.9

Rx LPI received PCS status register 1 3.1.10 Latched version of 3.1.8
Tx LPI indication PCS status register 1 3.1.9 TRUE when not in state TX_ACTIVE
Rx LPI indication PCS status register 1 3.1.8 TRUE when not in state RX_ACTIVE
type 1000BASE-X8
Insert the following new row at the end of the table in 36.7.3:
*LPI Implementation of LPI 36.2.4.12a O Yes [ ]

No [ ]
8
36.7.4 PICS proforma tables for the PCS and PMA sublayer, type 1000BASE-X
Insert a new subclause 36.7.4.9 after 36.7.4.8 for LPI functions as follows:
LP-01 Transmit ordered set state 36.2.5.2.1 Support additions to LPI:M Yes [ ]
diagram Figure 365 for LPI operation No [ ]
LP-02 Receive state diagram 36.2.5.2.2 Support additions to LPI:M Yes [ ]

Figure 367a, Figure 367b No [ ]
for LPI operation
LP-03 LPI transmit state diagram 36.2.5.2.8 Meets the requirements of LPI:M Yes [ ]
Figure 369a No [ ]
LP-04 LPI receive state diagram 36.2.5.2.8 Meets the requirements of LPI:M Yes [ ]
Figure 367c No [ ]
LP-03 LPI transmit timing 36.2.5.2.8 Meets the requirements of LPI:M Yes [ ]
Table 363a No [ ]
LP-04 LPI receive timing 36.2.5.2.8 Meets the requirements of LPI:M Yes [ ]
Table 363b No [ ]
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
Insert two paragraphs before the last paragraph of 40.1.3 as follows:
A 1000BASE-T PHY with the optional Energy-Efficient Ethernet (EEE) capability may optionally enter the
Low Power Idle (LPI) mode to conserve energy during periods of low link utilization. The Assert LPI
request at the GMII is encoded in the transmitted symbols. Detection of LPI signaling in the received
symbols is indicated as Assert LPI at the GMII. When LPI signaling is simultaneously transmitted and
received, an energy-efficient 1000BASE-T PHY ceases transmission and deactivates transmit and receive
functions to conserve energy. The PHY periodically transmits during this quiet period to allow the remote
PHY to refresh its receiver state (e.g., timing recovery, adaptive filter coefficients) and thereby track long-
term variation in the timing of the link or the underlying channel characteristics. If, during the quiet or
refresh periods, normal interframe is asserted at the GMII, the PHY reactivates transmit and receive
functions and initiates transmission. This transmission will be detected by the remote PHY, causing it to also
exit the LPI mode.
The conditions for supporting the optional EEE capability are defined in 78.3.
Technology Dependent Interface (Clause 28)
PMA_Link.indication
PMA_Link.request
(link_control)
(link_status)
PMA_UNITDATA.request
COL (tx_symb_vector)
GTX_CLK PCS
TRANSMIT
TXD<7:0>
loc_update_done
tx_mode
loc_lpi_req
1000BTtransmit
tx_enable
tx_error
PHY
config CONTROL
TX_EN
PCS DATA
TX_ER TRANSMISSION
ENABLE LINK
MONITOR
LOCAL
LPI
REQUEST PMA
link_status
TRANSMIT
CRS PCS
CARRIER BI_DA +
SENSE BI_DA -
recovered_clock
signal_detect
BI_DB +
1000BTreceive BI_DB -
BI_DC +
RX_CLK BI_DC -
BI_DD +
rem_lpi_req BI_DD -
RXD<7:0>
lpi_mode
PCS
RX_DV rem_update_done
RECEIVE
rem_rcvr_status
PMA
RX_ER loc_rcvr_status
RECEIVE
scr_status
PMA_UNITDATA.indication
(rx_symb_vector)
received_clock
CLOCK
GIGABIT MEDIA PMA SERVICE RECOVERY MEDIUM
INDEPENDENT INTERFACE DEPENDENT
INTERFACE INTERFACE
(GMII) (MDI)
PCS PMA
PHY
(INCLUDES PCS AND PMA)
NOTEThe recovered_clock arc is shown to indicate delivery of the received clock signal back the PMA TRANSMIT for loop timing
NOTESignals and functions shown with dashed lines are only required for the EEE capability.
40.1.3.1 Physical Coding Sublayer (PCS)
Insert the following paragraph after the fourth paragraph is 40.1.3.1:
When the PHY supports the optional EEE capability, Idle mode encoding also conveys to the remote PHY
information of whether the local PHY is requesting entry into the LPI mode or not. Such requests are a direct
translation of Assert LPI at the GMII. In addition, Idle mode encoding conveys to the remote PHY
whether the local PHY has completed the update of its receiver state or not, as indicated by the PMA PHY
Control function.
Insert the following paragraph before the last paragraph of 40.1.3.2:
When the PHY supports the optional EEE capability, the PMA PHY Control function also coordinates
transitions between the LPI mode and the normal operating mode.
40.1.4 Signaling
Insert new items j) and k) into the lettered list in 40.1.4, and renumber subsequent items in the list:
j) Optionally, ability to signal to the remote PHY a request to enter the LPI mode and to exit the LPI
mode and return to normal operation.
k) Optionally, ability to signal to the remote PHY that the update of the local receiver state (e.g., timing
recovery, adaptive filter coefficients) has completed.
Change the last paragraph of 40.1.4 as follows:
The PHY operates may operate in two three basic modes, normal mode, or training mode, or an optional LPI
mode. In normal mode, PCS generates code-groups that represent data, control, or idles for transmission by
the PMA. In training mode, the PCS is directed to generate only idle code-groups for transmission by the
PMA, which enable the receiver at the other end to train until it is ready to operate in normal mode. In LPI
mode, the PCS is directed to generate only idle code-groups encoded with LPI request and update status
indications, or zeros as dictated by the PMA PHY Control function. (See the PCS reference diagram in
40.2.)
40.2 1000BASE-T Service Primitives and Interfaces
40.2.2 PMA Service Interface
Insert new items at the end of the existing list of service primitives in the first paragraph, as follows:
PMA_LPIMODE.indication(lpi_mode)
PMA_LPIREQ.request(loc_lpi_req)
PMA_REMLPIREQ.request(rem_lpi_req)
PMA_UPDATE.indication(loc_update_done)
PMA_REMUPDATE.request(rem_update_done)
Replace Figure 404 with the new figure as follows:
PMA_LINK.indication
MDC
PMA_LINK.request
MDIO MANAGEMENT
GTX_CLK PMA_TXMODE.indication
TXD<7:0> PMA_CONFIG.indication
TX_EN
TX_ER
COL
PMA_RXSTATUS.indication
CRS PCS PMA
PMA_REMRXSTATUS.request
RX_CLK
BI_DA +
PMA_SCRSTATUS.request BI_DA -
RXD<7:0>
PMA_RESET.indication BI_DB +
RX_DV
BI_DB -
RX_ER
BI_DC +
PMA_LPIMODE.indication BI_DC -
PMA_LPIREQ.request BI_DD +
BI_DD -
PMA_REMLPIREQ.request
PMA_UPDATE.indication
PMA_REMUPDATE.request
GIGABIT MEDIA PMA SERVICE MEDIUM

INDEPENDENT INTERFACE DEPENDENT
INTERFACE INTERFACE
(GMII) (MDI)
PHY
NOTEService interface primitives shown with dashed lines are only required for the EEE capability.
Figure 4041000BASE-T service interfaces
40.2.10 PMA_RESET.indication
Insert the following new subclauses 40.2.11 through 40.2.15 after 40.2.10 as follows:
40.2.11 PMA_LPIMODE.indication
This primitive is generated by the PMA to indicate that the PHY has entered the LPI mode of operation.
40.2.11.1 Semantics of the primitive
PMA_LPIMODE.indication(lpi_mode)
PMA_LPIMODE.indication specifies to the PCS Receive function, via the parameter lpi_mode, whether or
not the PHY has entered LPI mode. The parameter lpi_mode can take on one of the following values of the
form:
ON This value is asserted with the PHY is operating in LPI mode.

OFF This value is asserted during normal operation.
40.2.11.2 When generated
The PMA PHY Control function generates PMA_LPIMODE.indication messages continuously.
40.2.11.3 Effect of receipt
Upon receipt of this primitive, the PCS performs its Receive function as described in 40.3.1.4.
40.2.12 PMA_LPIREQ.request
This primitive is generated by the PCS to indicate a request to enter the LPI mode.
PMA_LPIREQ.request (loc_lpi_req)
PMA_LPIREQ.request specifies to the PMA PHY Control, via the parameter loc_lpi_req, whether or not
the PHY is requested to enter the LPI mode. The parameter loc_lpi_req can take on one of the following
values of the form:
TRUE This value is continuously asserted when Assert LPI is present on the
GMII. Note that Assert LPI at the GMII implies that no frame transmission
is in progress hence 1000BTtransmit (see 40.3.3.1) will be set to FALSE by the
PCS Transmit state diagram.
FALSE This value is continuously asserted when Assert LPI is not present at
the GMII.
The PCS Local LPI Request function generates PMA_LPIREQ.request messages continuously.
Upon receipt of this primitive, the PMA performs its PHY Control function as described in 40.4.2.4.
40.2.13 PMA_REMLPIREQ.request
This primitive is generated by the PCS to indicate a request to enter LPI mode as communicated by the
remote PHY via its encoding of its loc_lpi_req parameter.
PMA_REMLPIREQ.request (rem_lpi_req)
PMA_REMLPIREQ.request specifies to the PMA PHY Control, via the parameter rem_lpi_req, whether or
not the remote PHY is requesting entry into the LPI mode. The parameter rem_lpi_req can take on one of the
following values of the form:
TRUE This value is continuously asserted when LPI is encoded in the received
symbols.
FALSE This value is continuously asserted when LPI is not encoded in the received
symbols.
The PCS Receive function generates PMA_REMLPIREQ.request messages continuously on the basis of the
signals received at the MDI.
40.2.14 PMA_UPDATE.indication
This primitive is generated by the PMA to indicate that the PHY has completed the update of its receiver
state (e.g., timing recovery, adaptive filter coefficients).
PMA_UPDATE.indication(loc_update_done)
PMA_UPDATE.indication specifies to the PCS Transmit functions, via the parameter loc_update_done,
whether or not the PHY has completed the update of its receiver state. The parameter loc_update_done can
take on one of the following values of the form:
TRUE This value is asserted when the PHY has completed the current update.
FALSE This value is asserted when the PHY is ready for the next update or when
the current update is still in progress.
The PMA PHY Control function generates PMA_UPDATE.indication messages continuously.
Upon receipt of this primitive, the PCS performs its Transmit function as described in 40.3.1.3 and 40.3.1.4.
40.2.15 PMA_REMUPDATE.request
This primitive is generated by the PCS to indicate that the remote PHY has completed the update of its
receiver state (e.g., timing recovery, adaptive filter coefficients).
PMA_REMUPDATE.request(rem_update_done)
PMA_REMUPDATE.indication specifies to the PMA PHY Control function, via the parameter
rem_update_done, whether or not the remote PHY has completed the update of its receiver state. The
parameter rem_update_done can take on one of the following values of the form:
TRUE This value is asserted when the remote PHY has completed the current update.
FALSE This value is asserted to when the remote PHY is ready for the next update or when
the current update is still in progress.
The PCS Receive function generates PMA_REMUDPATE.request messages continuously.
PMA_UNITDATA.request(tx_symb_vector)
loc_update_done
COL
GTX_CLK PCS
TRANSMIT
TXD<7:0>
tx_mode
1000BTtransmit
tx_enable
tx_error
config
TX_EN
PCS DATA
TX_ER TRANSMISSION link_status
ENABLE
loc_lpi_req
LOCAL
LPI
REQUEST
CRS PCS
CARRIER
SENSE
1000BTreceive
RX_CLK
rem_lpi_req
RXD<7:0>
PCS lpi_mode
RX_DV rem_update_done
RECEIVE
rem_rcvr_status
RX_ER loc_rcvr_status
scr_status
(rx_symb_vector)
GIGABIT MEDIA PMA SERVICE

INDEPENDENT INTERFACE
INTERFACE
PCS
Figure 405PCS reference diagram
40.3.1 PCS functions
40.3.1.3 PCS Transmit function
Insert a new paragraph between paragraphs five and six as follows:
When the PHY supports the optional EEE capability, the LPI mode encoding also takes into account the
value of the parameter loc_lpi_req. By this mechanism, the PHY indicates whether it requests to operate in
LPI mode or return to the normal mode of operation. In addition, LPI mode encoding takes into account the
value of loc_update_done. By this mechanism, the PHY indicates whether it has completed the update of its
receiver state (e.g., timing recovery, adaptive filter coefficients) or not, as indicated by the PMA PHY
Control function.
40.3.1.3.4 Generation of bits Sdn[8:0]
Change the paragraph following the equation for Sdn[6] as follows:
The bits Sdn[5:4][5:3] are derived from the bits Scn[5:4][5:3] and the GMII data bits TXDn[5:4][5:3] as
Replace the equation for Sdn[5:3] with the equation for Sdn[5:4] as follows:
Scn[5:4] ^ TXDn[5:4] if (tx_enablen-2 = 1)

Sdn[5:4] =
Scn[5:4] else
Insert a new paragraph and equation for Sdn[3] following the new equation for Sdn[5:4] (formerly the
equation for Sdn[5:3]), as follows:
The bit Sdn[3] is used to scramble the GMII data bit TXDn[3] during data mode and to encode loc_lpi_req
otherwise. It is defined as
Scn[3] ^ TXDn[3] if (tx_enablen-2 = 1)

Sdn[3] = Scn[3] ^ 1 else if ((loc_lpi_req = TRUE) and (tx_mode SEND_Z))
Scn[3] else
Replace the equation for Sdn[2] with a new equation as follows:

Sdn[2] = Scn[2] ^ 1 else if ((loc_rcvr_status = OK) and (tx_mode SEND_Z))
Scn[2] else
Change the paragraph following the equation for Sdn[2] as follows:
The bits Sdn[1:0] are used to transmit carrier extension information during tx_mode=SEND_N and are thus
dependent upon the bits cextn and cext_errn. In addition, bit Sdn[1] is used to encode loc_update_done.
These bits are dependent on the variable tx_errorn, which is defined in Figure 408. These bits are defined as
Replace the equations for cext_errn and Sdn[1] with the following equations:
tx_errorn if ((tx_enablen = 0) and (TXDn[7:0] 0x0F) and (loc_lpi_req = FALSE))

cext_errn =
0 else

Sdn[1] = Scn[1] ^ 1 else if ((loc_update_done = TRUE) and (tx_mode SEND_Z))
Scn[1] ^ cext_errn else
40.3.1.4 PCS Receive function
Insert a new paragraph below the second paragraph in 40.3.1.4:
When the PHY supports the optional EEE capability, the PCS Receive uses the knowledge of the encoding
rules that are employed in the idle mode to derive the values of the variables rem_lpi_req and
rem_update_done.
Insert a new subclause 40.3.1.6 following 40.3.1.5 as shown:
40.3.1.6 PCS Local LPI Request function
The PCS Local LPI Request function generates the signal loc_lpi_req, which indicates to the PMA PHY
Control function whether or not the local PHY is requested to enter the LPI mode. When the PHY supports
the optional EEE capability, the PCS shall conform to the Local LPI Request state diagram as depicted in
Figure 408a including compliance with the associated state variables as specified in 40.3.3.
40.3.3.1 Variables
Change the variable definition as follows:
1000BTtransmit
A Boolean used by the PCS Transmit Process to indicate whether a frame transmission is in
progress. Also Uused by the Carrier Sense and Local LPI Request processes.
Values: TRUE: The PCS is transmitting a stream
FALSE: The PCS is not transmitting a stream
Insert the following text at the end of the existing list of variables in 4.3.3.1 as shown:
The following state variables are only required for the optional EEE capability:
loc_lpi_req
The loc_lpi_req variable is set by the PCS Local LPI Request function and indicates whether
or not the local PHY is requested to enter the LPI mode. It is passed to the PMA PHY
Control function via the PMA_LPIREQ.request primitive. In the absence of the optional EEE
capability, the PHY shall operate as if the value of this variable is FALSE.
Values: TRUE or FALSE
lpi_mode
The lpi_mode variable is generated by the PMA PHY Control function and indicates whether or
not the local PHY has entered LPI mode. It is passed to the PCS Receive function via the
PMA_LPIMODE.indication primitive. In the absence of the optional EEE capability, the PHY
operates as if the value of this variable is OFF.
Values: ON or OFF
rem_lpi_req
The rem_lpi_req variable is generated by the PCS Receive function and indicates whether or not
the remote PHY is requesting entry into LPI mode. It is passed to the PMA PHY Control
function via the PMA_REMLPIREQ.request primitive. In the absence of the optional EEE
capability, the PHY shall operate as if the value of this variable is FALSE.
Values: TRUE or FALSE
Insert a new figure (Figure 40-8a) after Figure 40-8 as follows:
pcs_reset = ON +
link_status OK
LOC LPI REQ OFF

loc_lpi_req FALSE
TX_EN = FALSE * TX_EN = TRUE +

TX_ER = TRUE * TX_ER = FALSE +
TXD<7:0> = 0x01 * TXD<7:0> 0x01 +
1000BTtransmit = FALSE 1000BTtransmit = TRUE
LOC LPI REQ ON

loc_lpi_req TRUE
Figure 408aPCS Local LPI Request state diagram (optional)
Replace Figure 40-10a with a new figure as follows:

(PMA_RXSTATUS.indication (NOT_OK) +
pcs_reset = ON + link_status = FAIL) *
(PMA_RXSTATUS.indication (NOT_OK) * 1000BTreceive = TRUE
lpi_mode = OFF +
link_status = FAIL) *
1000BTreceive = FALSE * LINK FAILED
PUDI
RX_ER TRUE
1000BTreceive FALSE
A
PUDI
IDLE
Optional Implementation 1000BTreceive FALSE
rxerror_status NO_ERROR
(Rxn) IDLE) * RX_ER FALSE
(rem_lpi_req = TRUE + RX_DV FALSE
lpi_mode = ON)
(Rxn) IDLE
LP_IDLE NON-IDLE DETECT CARRIER EXTENSION

with ERROR
RX_ER TRUE
1000BTreceive TRUE RXD<7:0> 0x1F
RXD<7:0> 0x01
rem_lpi_req = FALSE * PUDI

PUDI
lpi_mode = OFF B
CONFIRM
SSD2 VECTOR
EXTENDING
(Rxn-1) = SSD1 *
(Rxn-1) SSD1 +
(Rxn) = SSD2
(Rxn) SSD2
ELSE
(Rxn-1) = SSD1 *
(Rxn) = SSD2
SSD1 VECTOR (Rxn-1) CEXT (Rxn-1) IDLE
RX_ER FALSE
RX_DV TRUE
BAD SSD RXD<7:0> 0x55
rxerror_status ERROR CARRIER EXTENSION
PUDI
RX_ER TRUE
RXD<7:0> 0x0E RXD<7:0> 0x0F
SSD2 VECTOR
PUDI
PUDI * check_idle=TRUE
PUDI
RECEIVE
check_end = FALSE * check_end = FALSE *
(Rxn-1) xmt_err (Rxn-1) DATA
ELSE
DATA ERROR PREMATURE END DATA
RX_ER FALSE
RX_ER TRUE RX_ER TRUE
RXD<7:0> DECODE(RXn-1)
PUDI * check_idle=TRUE
PUDI
PUDI
check_end = TRUE * check_end = TRUE *

(Rxn-1) CSReset * check_end = TRUE *
(Rxn) CSReset * (Rxn-1) CSReset * (Rxn-1) CSExtend
(Rxn+1) ESD1 * (Rxn-1) CSExtend
(Rxn+2) ESD2_Ext_0
C D E
Figure 4010aPCS Receive state diagram, part a
40.4.2 PMA functions
PMA_LINK.indication
PMA_LINK.request
(link_control)
(link_status)
loc_lpi_req
tx_mode
loc_update_done
rem_rcvr_status
PHY
config CONTROL
rem_lpi_req
rem_update_done
lpi_mode
link_status LINK
MONITOR
PMA_UNITDATA.request PMA
(tx_symb_vector) TRANSMIT
recovered_clock
BI_DA +
signal_detect
BI_DA -
BI_DB +
BI_DB -
BI_DC +
BI_DC -
BI_DD +
BI_DD -
loc_rcvr_status PMA
scr_status RECEIVE
(rx_symb_vector)
received_clock
CLOCK
RECOVERY
MEDIUM
PMA SERVICE DEPENDENT
INTERFACE INTERFACE
(MDI)
NOTE 1The recovered_clock arc is shown to indicate delivery of the received clock signal back the PMA
TRANSMIT for loop timing.
NOTE 2Signals and functions shown with dashed lines are only required for the EEE capability.
Figure 4013PMA reference diagram
40.4.2.4 PHY Control function
Change the last sentence in the first paragraph of 40.4.2.4 as follows:
PHY Control generates the control actions that are needed to bring the PHY into a mode of operation during
which frames can be exchanged with the link partner. PHY Control shall comply with the state diagram
description given in Figure 4015a and Figure 4015bFigure 40-15.
Insert the following text before the last paragraph of 40.4.2.4 as follows:
When the PHY supports the optional EEE capability, PHY Control will transition to the LPI mode in
response to concurrent requests for LPI mode from the local PHY (loc_lpi_req = TRUE) and remote PHY
(rem_lpi_req = TRUE).
Upon activation of the LPI mode, the PHY Control asserts tx_mode = SEND_I for a period of time defined
by lpi_update_timer, which allows the remote PHY to prepare for cessation of transmission. When
lpi_update_timer expires, PHY Control transitions to the POST_UPDATE state, signals to the remote PHY
that is has completed the update by setting loc_update_done = TRUE, and starts the lpi_postupdate_timer.
When lpi_postupdate_timer expires, PHY Control transitions to the WAIT_QUIET state. If there is a request
to wake (loc_lpi_req = FALSE or rem_lpi_req = FALSE) while in the POST_UPDATE state, PHY Control
will wait for confirmation that the remote PHY has completed the update (rem_update_done = TRUE) and is
prepared for cessation of transmission before proceeding to the WAIT_QUIET state.
Upon entry into the WAIT_QUIET state, PHY Control asserts tx_mode = SEND_Z and transmission ceases.
During the WAIT_QUIET and QUIET states, the PHY may deactivate transmit and receive functions in
order to conserve energy. However, in the WAIT_QUIET state, the PHY shall be capable of correctly
decoding rem_lpi_req. The PHY will remain in the QUIET state no longer than the time implied by
lpi_quiet_timer.
When lpi_quiet_timer expires, the PHY initiates a wake sequence. The wake sequence begins with a
transition to the WAKE state where the PHY will transmit (tx_mode = SEND_I) for the period
lpi_waketx_timer and simultaneously start a parallel timer, lpi_wakemz_timer. Since it is likely that transmit
circuits were deactivated while in the QUIET state, this transmission is not expected to be compliant
1000BASE-T signaling, but rather of sufficient quality and duration to be detected by the remote PHY
receiver and initiate the wake sequence in the remote PHY.
Upon expiration of lpi_waketx_timer, the PHY will enter the WAKE_SILENT state and cease transmission
(tx_mode = SEND_Z). The PHY will remain in the WAKE_SILENT state until lpi_wakemz_timer has
expired, at which point it is assumed that the transmitter circuits have stabilized and compliant 1000BASE-
T signaling can be transmitted. At this point the MASTER transitions to the WAKE_TRAINING state and
transmits to the SLAVE PHY.
The remaining wake sequence is essentially an accelerated training mode sequence leading to entry into the
UPDATE state.
Once scrambler synchronization is achieved, the incoming value of rem_lpi_req can be determined. If the
LPI mode is no longer requested by either the local or remote PHY, then both PHYs return to the SEND
IDLE OR DATA state and the normal mode of operation (tx_mode = SEND_N). If both PHYs continue to
request the LPI mode, then both PHYs remain in the UPDATE state and continue to transmit for a time
defined by lpi_update_timer. This time is intended to allow the remote PHY to refresh its receiver state (e.g.,
timing recovery, adaptive filter coefficients) and thereby track long-term variation in the timing of the link or
the underlying channel characteristics. If lpi_update_timer expires and both PHYs continue to request the
LPI mode, then the PHY transitions to the POST_UPDATE state.
40.4.5.1 State diagram variables
Change definition of scr_status as follows:
scr_status
The scr_status parameter as communicated by the PMA_SCRSTATUS.request primitive.
Values: OK: The descrambler has achieved synchronization.
NOT_OK: The descrambler is not synchronized. Note that when the PHY supports
the optional EEE capability and signal_detect is FALSE, scr_status is set to NOT_OK.
Insert the following text after the existing list of variables as shown:
The following state variables are only required for the optional EEE capability:
loc_lpi_req
The loc_lpi_req variable is set by the PCS Local LPI Request function and indicates whether
or not the local PHY is requested to enter the LPI mode. It is passed to the PMA PHY
Control function via the PMA_LPIREQ.request primitive. In the absence of the optional EEE
capability, the PHY operates as if the value of this variable is FALSE.
Values: TRUE: Assert LPI is present at the GMII.
FALSE: Assert LPI is not present at the GMII.
loc_udpate_done
The loc_update_done variable is generated by the PMA PHY Control function and indicates
whether or not the local PHY has completed the update of its receiver state. It is passed to the
PCS Transmit function via the PMA_UPDATE.indication primitive. In the absence of the
optional EEE capability, the PHY shall operate as if the value of this variable is FALSE.
Values: TRUE: The PHY has completed the current update.
FALSE: The PHY is ready for the next update or the current update is still in progress.
lpi_mode
The lpi_mode variable is generated by the PMA PHY Control function and indicates whether or
not the local PHY has entered the LPI mode. It is passed to the PCS Receive function via the
PMA_LPIMODE.indication primitive. In the absence of the optional EEE capability, the PHY
shall operate as if the value of this variable is OFF.
Values: ON: The PHY is operating in LPI mode.
OFF: The PHY is in normal operation.
rem_lpi_req
The rem_lpi_req variable is generated by the PCS Receive function and indicates whether or not
the remote PHY is requesting entry into LPI mode. It is passed to the PMA PHY Control
function via the PMA_REMLPIREQ.request primitive. In the absence of the optional EEE
capability, the PHY operates as if the value of this variable is FALSE.
Values: TRUE: LPI is encoded in the received symbols.
FALSE: LPI is not encoded in the received symbols.
rem_update_done
The rem_update_done variable is generated by the PCS Receive function and indicates whether
or not the remote PHY has completed the update of its receiver state. It is passed to the PMA
PHY Control function via the PMA_REMUPDATE.request primitive. In the absence of
the optional EEE capability, the PHY shall operate as if the value of this variable is FALSE.
Values: TRUE: The remote PHY has completed the current update.
FALSE: The remote PHY is ready for the next update or the current update is still in
progress.
signal_detect
The signal_detect variable is set by the PMA Receive function and indicates the presence of a
signal at the MDI, as defined in 40.6.1.3.5.
Values: TRUE: There is a signal present at the MDI.
FALSE: There is no signal present at the MDI.
40.4.5.2 Timers
Insert the following text after the existing list of timers as shown:
The following timers are only required for the optional EEE capability:
lpi_link_fail_timer
This timer defines the maximum time the PHY allows between entry into the WAKE state
and subsequent entry into the UPDATE or SEND IDLE OR DATA states before forcing the link
to restart.
Values: The condition lpi_link_fail_timer_done becomes true upon timer expiration.

Duration: This timer shall have a period between 90 s and 110 s.
lpi_postupdate_timer
This timer defines the maximum time the PHY dwells in the POST_UPDATE state before
proceeding to the WAIT_QUIET state.
Values: The condition lpi_postupdate_timer_done becomes true upon timer expiration.

Duration: This timer shall have a period between 2.0 s and 3.2 s.
lpi_quiet_timer
This timer defines the maximum time the PHY remains quiet before initiating transmission to
refresh the remote PHY.
Values: The condition lpi_quiet_timer_done becomes true upon timer expiration.

Duration: This timer shall have a period between 20 ms and 24 ms.
lpi_waitwq_timer
This timer defines the maximum time the PHY dwells in the WAIT_QUIET state before
forcing the link to restart.
Values: The condition lpi_waitwq_timer_done becomes true upon timer expiration.

Duration: This timer shall have a period between 10 s and 12 s.
lpi_wake_timer
This timer defines the expected time for the PHY to transition from the LPI mode to normal
operation.
Values: The condition lpi_wake_timer_done becomes true upon timer expiration. For each
transition of lpi_wake_timer_done from false to true, the wake error counter (see 40.5.1.1)
shall be incremented.
Duration: This timer shall have a period that does not exceed 16.5 s.
lpi_waketx_timer
This timer defines the time the PHY transmits to ensure detection by the remote PHY receiver
and trigger an exit from the low power state.
Values: The condition lpi_waketx_timer_done becomes true upon timer expiration.

lpi_wakemz_timer
This timer defines the time allowed for the PHY transmitter to achieve compliant operation
following activation.
Values: The condition lpi_wakemz_timer_done becomes true upon timer expiration.

lpi_update_timer
This timer defines the time the PHY transmits to facilitate a refresh of the remote PHY receiver.
Values: The condition lpi_update_timer_done becomes true upon timer expiration.

Duration: For a PHY configured as the MASTER, this timer shall have a period between 0.23 ms
and 0.25 ms. For a PHY configured as the SLAVE, this timer shall have a period between 0.18 ms
and 0.20 ms.
40.4.6.1 PHY Control state diagram
Replace existing PHY Control state diagram (Figure 40-15) with two new figures (Figure 4015a and
Figure 4015b) as follows:
link_control = DISABLE + pma_reset = ON
DISABLE 1000BASE-T TRANSMITTER
B
SLAVE SILENT
start maxwait_timer
tx_mode SEND_Z
lpi_mode OFF
loc_update_done FALSE
config = MASTER +
scr_status = OK
TRAINING
start minwait_timer
minwait_timer_done * tx_mode SEND_I minwait_timer_done *
loc_rcvr_status = OK * loc_rcvr_status = OK *
rem_rcvr_status = OK rem_rcvr_status = NOT_OK
minwait_timer_done *
loc_rcvr_status = OK *
C rem_rcvr_status = OK
SEND IDLE OR DATA SEND IDLE

stop maxwait_timer stop maxwait_timer
start minwait_timer start minwait_timer
tx_mode SEND_N tx_mode SEND_I
lpi_mode OFF
loc_update_done FALSE
minwait_timer_done * minwait_timer_done * loc_rcvr_status = NOT_OK
loc_rcvr_status = NOT_OK * loc_rcvr_status = OK *
tx_enable = FALSE rem_rcvr_status = NOT_OK
A
rem_rcvr_status = OK *
loc_lpi_req = TRUE *
rem_lpi_req = TRUE
Figure 4015aPHY Control state diagram, part a
UPDATE
WAKE
tx_mode SEND_I
lpi_mode ON tx_mode SEND_I
start lpi_update_timer start lpi_wake_timer
stop lpi_wake_timer start lpi_waketx_timer
start lpi_wakemz_timer
loc_lpi_req = TRUE * loc_lpi_req = FALSE + start lpi_link_fail_timer
(lpi_update_timer_done * (rem_lpi_req = FALSE *
lpi_waketx_timer_done
rem_lpi_req = TRUE + rem_update_done = FALSE)
rem_update_done = TRUE)
POST_UPDATE C
loc_update_done TRUE
start lpi_postupdate_timer
WAKE_SILENT
tx_mode SEND_Z
lpi_postupdate_timer_done + rem_update_done = FALSE * loc_update_done FALSE
signal_detect = FALSE + rem_lpi_req = FALSE
(rem_update_done = TRUE *
(loc_lpi_req =FALSE + (config = MASTER + lpi_link_fail_timer_done
rem_lpi_req = FALSE)) scr_status = OK) *
C
lpi_wakemz_timer_done
WAIT_QUIET
tx_mode SEND_Z WAKE_TRAINING
start lpi_waitwq_timer tx_mode SEND_I B
signal_detect = FALSE + lpi_waitwq_timer_done

loc_lpi_req = FALSE +
rem_lpi_req = FALSE
QUIET loc_rcvr_status = OK * lpi_link_fail_timer_done
rem_rcvr_status = OK
start lpi_quiet_timer B
lpi_quiet_timer_done +
loc_lpi_req = FALSE +
signal_detect = TRUE
Figure 4015bPHY Control state diagram, part b (optional)
40.4.6.2 Link Monitor state diagram
Change NOTE 1 in Figure 4016 to cite the new PHY Control state diagram part a (Figure 4015a) as
follows:
pma_reset = ON +
link_control ENABLE
LINK DOWN
link_status FAIL
loc_rcvr_status = OK
HYSTERESIS
start stabilize_timer
loc_rcvr_status = NOT_OK stabilize_timer_done *

loc_rcvr_status = OK
LINK UP
link_status OK
loc_rcvr_status = NOT_OK *
maxwait_timer_done = TRUE
NOTE 1maxwait_timer is started in PHY Control state diagram (see Figure 4015a).
NOTE 2The variables link_control and link_status are designated as link_control_(1GigT)
and link_status_(1GigT), respectively, by the Auto-Negotiation Arbitration state diagram
(Figure 2818).
Figure 4016Link Monitor state diagram
40.5 Management interface
40.5.1 Support for Auto-Negotiation
Insert a new item c) at the end of the lettered list in 40.5.1 as follows:
c) To negotiate EEE capabilities as specified in 28C.12.
40.5.1.1 1000BASE-T use of registers during Auto-Negotiation
Insert rows at the end of Table 403 (following Register 15), and add Footnote b as shown:
Table 4031000BASE-T Registers

Register Bit Name Description Typea
3.0b 3.0.10 Clock stop enable Defined in 45.2.3.1.3a. When the PHY supports the R/W
optional EEE capability, it may stop the derived GMII
receive clock while it is signaling LPI in the receive
direction. If this bit is set to 1, then the PHY may stop
the receive GMII clock while it is signaling LPI;
otherwise it keeps the clock active.
3.1 3.1.11 Transmit LPI Defined in 45.2.3.2a. RO/LH
received
3.1 3.1.10 Receive LPI Defined in 45.2.3.2b. RO/LH
received
3.1 3.1.9 Transmit LPI Defined in 45.2.3.2c. RO
indication
3.1 3.1.8 Receive LPI Defined in 45.2.3.2d. RO
indication
3.1 3.1.6 Clock stop capable Defined in 45.2.3.2.2a. When the PHY supports the RO
optional EEE capability, this bit may be set to 1 to allow
the MAC to stop the GMII clock while it is signaling
LPI in the transmit direction. If this bit is 0, then the
MAC keeps the clock active.
3.20 3.20.2 1000BASE-T EEE If the local device supports the optional EEE capability RO
supported for 1000BASE-T, this bit is set to 1.
3.22 3.22.15:0 EEE wake error This counter is incremented for each transition of RO, NR
counter lpi_wake_timer_done from FALSE to TRUE (see
40.4.5.2).
7.60 7.60.2 1000BASE-T EEE If the local device supports the optional EEE capability R/W
advertisement for 1000BASE-T and EEE is desired, this bit is set to 1.
7.61 7.61.2 LP 1000BASE-T If the link partner supports the optional EEE capability RO
EEE advertisement for 1000BASE-T and EEE is desired, this bit is set to 1.
bThis
register resides in the Clause 45 management space and is designated by the format M.R.B where M is the
MDIO manageable device address (MMD), R is the register address, and B is the bit.
40.5.1.2 1000BASE-T Auto-Negotiation page use
Insert the following paragraph after the last paragraph of 40.5.1.2:
When the PHY supports the optional EEE capability, a 1000BASE-T PHY shall exchange an additional
formatted next page and unformatted next page in sequence, without interruption, as specified in
Table 404.
Insert rows in Table 404 following PAGE 2 (Unformatted next page) and Footnote a as follows:
Table 4041000BASE-T Base and Next Pages bit assignments
Bit Bit definition Register location

PAGE 3 (Message page)
M10:M0 10
PAGE 4 (Unformatted next page)
U10:U3 As specified in 45.2.7.13.
U2 1000BASE-T EEE Management register 7.60.2a
(1 = EEE is supported for 1000BASE-T, 0 = EEE is not sup-
ported for 1000BASE-T)
U1:U0 As specified in 45.2.7.13.
a
This register resides in the Clause 45 management space and is designated by the format M.R.B where M is the MDIO
manageable device address (MMD), R is the register address, and B is the bit.
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
Insert a new paragraph after the last paragraph of 40.6.1.2.5 as follows:
When the PHY supports the optional EEE capability, the unfiltered jitter requirements shall also be satisfied
during the LPI mode, with the exception that clock edges corresponding to the WAIT_QUIET, QUIET,
WAKE, and WAKE_SILENT states are not considered in the measurement. The PHY may turn off
TX_TCLK during these states. For a MASTER PHY operating in the LPI mode, the unjittered reference
shall be continuous.
40.6.1.2.6 Transmit clock frequency
Insert a new subclause 40.6.1.2.7 after 40.6.1.2.6 as follows:
40.6.1.2.7 Transmitter operation following a transition from the QUIET to the WAKE state
When the PHY supports the optional EEE capability, it transmits Idle symbols while in the WAKE state (see
Figure 4015b). This signal may be transmitted during reactivation of the PHY analog front-end and is not
guaranteed or intended to be compliant.
The transmit levels of the Idle symbols transmitted during the WAKE state shall exceed 65% of the transmit
levels of compliant Idle symbols for a period of at least 500 ns.
The PHY shall achieve compliant operation upon entry to the WAKE_TRAINING state (see
Figure 4015b).
40.6.1.3.5 Signal_detect
When the PHY supports the optional EEE capability, the PMA Receive function shall convey an indicator of
signal presence, referred to as signal_detect, to the PMA PHY Control function. The value of signal_detect
shall be set to TRUE within 0.5 s of the receipt of a wake signal meeting the requirements of 40.6.1.2.7.
The value of signal_detect shall be set to FALSE within 0.5 s of the receipt of a continuous sequence of
zeros.

Clause 40, Physical coding sublayer (PCS), physical medium attachment (PMA)
sublayer and baseband medium, type 1000BASE-T9
Insert *EEE option after *DTE in the table as follows:

*EEE EEE 40.1.3 O Yes [ ]
No [ ]
40.12.4 Physical Coding Sublayer (PCS)
Insert PCT18 and PCT19 at the end of the table as follows:
PCT18 The PCS shall 40.3.1.6 EEE:M Yes [ ] Conform to the Local LPI
Request state diagram as
depicted in Figure 408a
including compliance with the
associated state variables
specified in 40.3.3.
PCT19 In the absence of the optional 40.3.3.1 !EEE:M Yes [ ] Operate as if the value of
EEE capability, the PHY shall loc_lpi_req is FALSE.
9
40.12.4.1 PCS receive functions
Insert PCR5 at the end of the table as follows:
PCR5 In the absence of the optional 40.3.3.1 !EEE:M Yes [ ] Operate as if the value of
EEE capability, the PHY shall rem_lpi_req is FALSE.
40.12.5 Physical Medium Attachment (PMA)
Insert PMF24 through PMF37 at the end of the table as follows:
PMF24 PHY Control shall 40.4.2.4 EEE:M Yes [ ] Comply with the state diagram
description given in
Figure 4015a and
Figure 4015b.
PMF25 In the WAIT_QUIET state, the 40.4.2.4 EEE:M Yes [ ] Be capable of correctly
PHY shall decoding rem_lpi_req.
PMF26 In the absence of the optional 40.4.5.1 EEE:M Yes [ ] Operate as if the value of
EEE capability, the PHY shall loc_update_done is FALSE.
EEE capability, the PHY shall lpi_mode is OFF.
EEE capability, the PHY shall rem_lpi_req is FALSE.
PMF29 lpi_link_fail_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period between 90 s
and 110 s.
PMF30 lpi_postupdate_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period between 2.0 s
and 3.2 s.
PMF31 lpi_quiet_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period between 20 ms

and 24 ms.
PMF32 lpi_waitwq_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period between 10 s
and 12 s.
PMF33 For each transition of 40.4.5.2 EEE:M Yes [ ] Be incremented.

lpi_wake_timer_done from
false to true, the wake error
counter shall
PMF34 lpi_wake_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period that does not
exceed 16.5 s.
PMF35 lpi_waketx_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period between 1.2_s
and 1.4 s.
PMF36 lpi_wakemz_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period between 4.25 s
and 5.00 s.
PMF37 lpi_update_timer shall 40.4.5.2 EEE:M Yes [ ] Have a period between 0.23 ms
and 0.25 ms for a PHY
configured as the MASTER
and a period between 0.18 ms
and 0.20 ms for a PHY
configured as the SLAVE.
40.12.6 Management interface
40.12.6.1 1000BASE-T Specific Auto-Negotiation Requirements
Insert AN15 at the end of the table as follows:
AN15 When EEE is supported, a 40.5.1.2 EEE:M Yes [ ] Exchange an additional

1000BASE-T PHY shall formatted next page and
unformatted next page in
sequence, without interruption,
as specified in Table 404.
40.12.7 PMA Electrical Specifications
Insert PME71 through PME77 at the end of the table as follows:
PME71 The unfiltered jitter 40.6 EEE:M Yes [ ] Be satisfied during the LPI
requirements shall mode, with the exception that
clock edges corresponding to
the WAIT_QUIET, QUIET,
WAKE, and WAKE_SILENT
states are not considered in the
measurement.
PME72 For a MASTER PHY 40.6 EEE:M Yes [ ] Be continuous.

operating in the LPI mode, the
unjittered reference shall
PME73 The transmit levels of the Idle 40.6.1.2.7 EEE:M Yes [ ] Exceed 65% of the transmit
symbols transmitted during levels of compliant Idle
the WAKE state shall symbols for a period of at least
500 ns.
PME74 The PHY shall 40.6.1.2.7 EEE:M Yes [ ] Achieve compliant operation
upon entry to the
WAKE_TRAINING state (see
Figure 4015b).
PME75 PMA Receive function shall 40.6.1.3.5 EEE:M Yes [ ] Convey an indicator of signal
presence, referred to as
signal_detect, to the PMA PHY
Control function.
PME76 The value of signal_detect 40.6.1.3.5 EEE:M Yes [ ] Be set to TRUE within 0.5 s
shall of the receipt of a wake signal
meeting the requirements of
40.6.1.2.7.
PME77 The value of signal_detect 40.6.1.3.5 EEE:M Yes [ ] Be set to FALSE within 0.5 s
shall of the receipt of a continuous
sequence of zeros.
45. Management Data Input/Output (MDIO) Interface
45.2 MDIO Interface Registers
45.2.1 PMA/PMD registers
Change Table 45-3 by adding a new row and changing the reserved row as follows:
Table 453PMA/PMD registers
Register address Register name
1.147 10GBASE-T fast retrain status and control register

1.1478 through 1.149 Reserved
45.2.1.76 10GBASE-KR PMD control register (Register 1.150)
Insert 45.2.1.76a after 45.2.1.76 (as renumbered by IEEE Std 802.3av-2009) as follows:
45.2.1.76a 10GBASE-T fast retrain status and control register (Register 1.147)
Table 4553a10GBASE-T fast retrain status and control register bit definitions
Bit(s) Name Description R/Wa
1.147.15:11 LP fast retrain count Counts the number of fast retrains requested by the link partner RO/NR
1.147.10:6 LD fast retrain count Counts the number of fast retrains requested by the local device RO/NR
1.147.5 Reserved Ignore on read RO
1 = Fast retrain capability is supported

1.147.4 Fast retrain ability RO
0 = Fast retrain capability is not supported
Fast retrain negoti- 1 = Fast retrain capability was negotiated

1.147.3 RO
ated 0 = Fast retrain capability was not negotiated
11 = Reserved
Fast retrain signal 10 = PHY signals Link Interruption during fast retrain
1.147.2:1 R/W
type 01 = PHY signals Local Fault during fast retrain
00 = PHY signals IDLE during fast retrain
1 = Fast retrain capability is enabled

1.147.0 Fast retrain enable R/W
0 = Fast retrain capability is disabled
a
RO = Read only, R/W = Read/Write, NR = Non Roll-over
45.2.1.76a.1 LP fast retrain count (1.147.15:11)
These bits map to fr_rx_counter as defined in 55.4.5.1. The counter is a 5-bit count of the number of
10GBASE-T fast retrains requested by the link partner. These bits shall be reset to all zeros when read or
upon execution of the PMA reset. These bits shall be held at all ones in the case of overflow.
45.2.1.76a.2 LD fast retrain count (1.147.10:6)
These bits map to fr_tx_counter as defined in 55.4.5.1. The counter is a 5-bit count of the number of
10GBASE-T fast retrains requested by the local device. These bits shall be reset to all zeros when read or
upon execution of the PMA reset. These bits shall be held at all ones in the case of overflow.
45.2.1.76a.3 Fast retrain ability (1.147.4)
When read as a one, bit 1.147.4 indicates that the PHY supports fast retrain, as defined in 55.4.2.5.15. When
read as a zero, bit 1.147.4 indicates that the PHY does not support fast retrain.
45.2.1.76a.4 Fast retrain negotiated (1.147.3)
When read as a one, bit 1.147.3 indicates that the PHY negotiated fast retrain, as defined in 55.4.2.5.15
during the most recent auto-negotiation. When read as a zero, bit 1.147.3 indicates that the PHY did not
negotiate fast retrain. See 45.2.7.10.5a.
45.2.1.76a.5 Fast retrain signal type (1.147.2:1)
For PHYs that support fast retrain, these bits map to fr_sigtype as defined in 55.3.5.2.2. When Fast retrain
signal type is set to 00, the PMA sends IDLE characters on the receive path during fast retrain. When Fast
retrain signal type is set to 01, the PMA sends Local Fault on the receive path during fast retrain. When Fast
retrain signal type is set to 10, the PMA sends Link Interruption on the receive path during fast retrain.
45.2.1.76a.6 Fast retrain enable (1.147.0)
For PHYs that support fast retrain, this bit controls fr_enable as defined in 55.4.5.1. When PMA reset is
executed, this bit is set to one.
NOTESetting this bit to zero while a link is up will cause the PHY to stop supporting fast retrain, and the link will
drop if the link partner initiates a fast retrain.
45.2.3 PCS registers
Change Table 45-83 (as renumbered by IEEE Std 802.3av-2009) by adding new rows and changing the
reserved rows as follows:
Table 4583PCS registers
Register address Register name Clause

3.20 EEE capability register 45.2.3.8a
3.21 Reserved
3.22 EEE wake error counter 45.2.3.8b
45.2.3.1 PCS control 1 register (Register 3.0)
Change Table 45-84 (as renumbered by IEEE Std 802.3av-2009) by adding a new row and changing the
reserved row as follows:
Table 4584PCS control 1 register bit definitions
3.0.10 Clock stop enable 1 = The PHY may stop the clock during LPI R/W
0 = Clock not stoppable
3.0.109:7 Reserved Value always 0, writes ignored R/W

a
R/W = Read/Write, SC = Self-clearing
45.2.3.1.3a Clock stop enable (3.0.10)
If bit 3.0.10 is set to 1 then the PHY may stop the receive xMII clock while it is signaling LPI otherwise it
shall keep the clock active. If the PHY does not support EEE capability or is not able to stop the receive
clock then this bit has no effect (see 22.2.2.2, 35.2.2.8a, and 46.3.2.4).
45.2.3.2 PCS status 1 register (Register 3.1)
Change Table 45-85 (as renumbered by IEEE Std 802.3av-2009) to insert new rows and change the
reserved row and footnote as follows:
Table 4585PCS status 1 register bit definitions
3.1.15:812 Reserved Ignore when read RO
3.1.11 Tx LPI received 1 = Tx PCS has received LPI RO/LH

0 = LPI not received
3.1.10 Rx LPI received 1 = Rx PCS has received LPI RO/LH

3.1.9 Tx LPI indication 1 = Tx PCS is currently receiving LPI RO

0 = PCS is not currently receiving LPI
3.1.8 Rx LPI indication 1 = Rx PCS is currently receiving LPI RO

3.1.6 Clock stop capable 1 = The MAC may stop the clock during LPI RO

a
RO = Read only, LL = Latching low, LH = Latching high
Insert new subclauses 45.2.3.2a, b, c, and d before 45.2.3.2.1 as follows:
45.2.3.2a Transmit LPI received (3.1.11)
When read as a one, bit 3.1.11 indicates that the transmit PCS has received LPI signaling one or more times
since the register was last read. When read as a zero, bit 3.1.11 indicates that the PCS has not received LPI
signaling. This bit shall be implemented with latching high behavior.
45.2.3.2b Receive LPI received (3.1.10)
When read as a one, bit 3.1.10 indicates that the receive PCS has received LPI signaling one or more times
since the register was last read. When read as a zero, bit 3.1.10 indicates that the PCS has not received LPI
signaling. This bit shall be implemented with latching high behavior.
45.2.3.2c Transmit LPI indication (3.1.9)
When read as a one, bit 3.1.9 indicates that the transmit PCS is currently receiving LPI signals. When read as
a zero, bit 3.1.9 indicates that the PCS is not currently receiving LPI signals. The behavior if read during a
state transition is undefined.
45.2.3.2d Receive LPI indication (3.1.8)
When read as a one, bit 3.1.8 indicates that the receive PCS is currently receiving LPI signals. When read as
a zero, bit 3.1.8 indicates that the PCS is not currently receiving LPI signals. The behavior if read during a
state transition is undefined.
Insert a new subclause 45.2.3.2.2a before 45.2.3.2.3 as follows:
45.2.3.2.2a Clock stop capable (3.1.6)
If bit 3.1.6 is set to one then the RS may stop the transmit xMII clock while it is signaling LPI otherwise it
shall keep the clock active. If the RS does not support EEE capability or is not able to stop the transmit clock
then this bit has no effect (see 22.2.2.5a, 35.2.2.5a, and 46.3.2.4).
45.2.3.8 PCS package identifier (Registers 3.14 and 3.15)
Insert new subclauses 45.2.3.8a and b after 45.2.3.8 as follows:
45.2.3.8a EEE capability (Register 3.20)
This register is used to indicate the capability of the PCS to support EEE functions for each PHY type. The
assignment of bits in the EEE capability register is shown in Table 4588a.
Table 4588aEEE capability register (Register 3.20) bit definitions
3.20.15:7 Reserved Ignore on read RO
1 = EEE is supported for 10GBASE-KR

3.20.6 10GBASE-KR EEE RO
0 = EEE is not supported for 10GBASE-KR
1 = EEE is supported for 10GBASE-KX4

3.20.5 10GBASE-KX4 EEE RO
0 = EEE is not supported for 10GBASE-KX4
1 = EEE is supported for 1000BASE-KX

3.20.4 1000BASE-KX EEE RO
0 = EEE is not supported for 1000BASE-KX
1 = EEE is supported for 10GBASE-T

3.20.3 10GBASE-T EEE RO
0 = EEE is not supported for 10GBASE-T
1 = EEE is supported for 1000BASE-T
3.20.2 1000BASE-T EEE RO
0 = EEE is not supported for 1000BASE-T
1 = EEE is supported for 100BASE-TX

3.20.1 100BASE-TX EEE RO
0 = EEE is not supported for 100BASE-TX

a RO = Read only
45.2.3.8a.1 10GBASE-KR EEE supported (3.20.6)
If the device supports EEE operation for 10GBASE-KR as defined in 72.1, this bit shall be set to one.
45.2.3.8a.2 10GBASE-KX4 EEE supported (3.20.5)
If the device supports EEE operation for 10GBASE-KX4 as defined in 71.2, this bit shall be set to one.
45.2.3.8a.3 1000BASE-KX EEE supported (3.20.4)
If the device supports EEE operation for 1000BASE-KX as defined in 70.1, this bit shall be set to one.
45.2.3.8a.4 10GBASE-T EEE supported (3.20.3)
If the device supports EEE operation for 10GBASE-T as defined in 55.1.3.3, this bit shall be set to one.
45.2.3.8a.5 1000BASE-T EEE supported (3.20.2)
If the device supports EEE operation for 1000BASE-T as defined in 40.1.3, this bit shall be set to one.
45.2.3.8a.6 100BASE-TX EEE supported (3.20.1)
If the device supports EEE operation for 100BASE-TX as defined in 24.1.1, this bit shall be set to one.
45.2.3.8b EEE wake error counter (Register 3.22)
This register is used by PHY types that support EEE to count wake time faults where the PHY fails to
complete its normal wake sequence within the time required for the specific PHY type. The definition of the
fault event to be counted is defined for each PHY and may occur during a refresh or a wake-up as defined by
the PHY. This 16-bit counter shall be reset to all zeros when the EEE wake error counter is read by the
management function or upon execution of the PCS reset. This counter shall be held at all ones in the case of
overflow.
45.2.4 PHY XS registers
Change Table 45-116 (as renumbered by IEEE Std 802.3av-2009) by adding new rows and changing the
reserved rows as follows:
Table 45116PHY XS registers

4.20 EEE capability register
4.21 Reserved
4.22 EEE wake error counter
45.2.4.1 PHY XS control 1 register (Register 4.0)
Change Table 45-117 (as renumbered by IEEE Std 802.3av-2009) by inserting new rows and changing
the reserved row as follows:
Table 45117PHY XS control 1 register bit definitions
4.0.10 Clock stop enable 1 = The PHY XS may stop the clock during LPI R/W
4.0.9 XAUI stop enable 1 = The PHY XS may stop XAUI signals during R/W
LPI
0 = XAUI not stoppable

a
R/W = Read/Write, SC = Self-clearing
45.2.4.1.3 Low power (4.0.11)
Insert new subclauses 45.2.4.1.3a and b after 45.2.4.1.3 as follows:
If bit 4.0.10 is set to 1, then the PHY XS may stop the transmit direction xMII clock while it is signaling
LPI, otherwise it shall keep the clock active. If the PHY XS does not support EEE capability or is not able to
stop the transmit clock, then this bit has no effect (see 46.3.2.4).
45.2.4.1.3b XAUI stop enable (4.0.9)
If bit 4.0.9 is set to 1, then the PHY XS may stop signaling on the XAUI in the receive direction during LPI,
otherwise the PHY XS shall keep the XAUI signals active. If the PHY XS does not support EEE capability
or is not able to stop the receive path XAUI signals, then this bit has no effect.
45.2.4.2 PHY XS status 1 register (Register 4.1)
the reserved rows and footnote as follows:.
Table 45118PHY XS status 1 register bit definitions
4.1.11 Tx LPI received 1 = Tx PHY XS has received LPI RO/LH

4.1.10 Rx LPI received 1 = Rx PHY XS has received LPI RO/LH

4.1.9 Tx LPI indication 1 = Tx PHY XS is currently receiving LPI RO

4.1.8 Rx LPI indication 1 = Rx PHY XS is currently receiving LPI RO

4.1.6 Clock stop capable 1 = The attached PHY may stop the clock during LPI RO

a
When read as a one, bit 4.1.11 indicates that the transmit PHY XS has received LPI signaling one or more
times since the register was last read. When read as a zero, bit 4.1.11 indicates that the PHY XS has not
received LPI signaling. This bit shall be implemented with latching high behavior.
When read as a one, bit 4.1.10 indicates that the receive PHY XS has received LPI signaling one or more
times since the register was last read. When read as a zero, bit 4.1.10 indicates that the PHY XS has not
When read as a one, bit 4.1.9 indicates that the transmit PHY XS is currently receiving LPI signals. When
read as a zero, bit 4.1.9 indicates that the PHY XS is not currently receiving LPI signals. The behavior if
read during a state transition is undefined.
When read as a one, bit 4.1.8 indicates that the receive PHY XS is currently receiving LPI signals. When
read as a zero, bit 4.1.8 indicates that the PHY XS is not currently receiving LPI signals. The behavior if
read during a state transition is undefined.
Insert new subclause 45.2.4.2.2a before 45.2.4.2.3 as follows:
If bit 4.1.6 is set to one then the PHY XS is indicating that the attached PHY is permitted to stop the receive
direction xMII clock while it is signaling LPI. If the bit is set to zero then the PHY XS is indicating that the
attached PHY is not permitted to stop the receive xMII clock while it is signaling LPI. If the attached PHY
does not support EEE capability or is not able to stop the receive direction xMII clock then this bit has no
effect (see 46.3.2.4).
45.2.4.7 PHY XS package identifier (Registers 4.14 and 4.15)
This register is used to indicate the capability of the PHY XS to support EEE functions. The assignment of
bits in the EEE capability register is shown in Table 45122a.
1 = EEE is supported for PHY XS

4.20.4 PHY XS EEE RO
0 = EEE is not supported for PHY XS
1 = The DTE XS may stop XAUI signals during LPI

4.20.0 XAUI stop capable RO
0 = XAUI signals not stoppable
a
RO = Read only
45.2.4.7a.2 PHY XS EEE supported (4.20.4)
If the device supports EEE operation for PHY XS as defined in 48.2, this bit shall be set to one.
45.2.4.7a.3 XAUI stop capable (4.20.0)
If bit 4.20.0 is set to one, then the PHY XS is indicating that the attached DTE XS is permitted to stop
transmitting XAUI signals during LPI. If the bit is set to zero then the PHY XS is indicating that the attached
DTE XS is not permitted to stop transmitting XAUI signals during LPI. If the DTE XS does not support
EEE capability or is not able to stop the transmit direction XAUI, then this bit has no effect.
This register is used by PHY XS that support EEE to count wake time faults where the PHY XS fails to
complete its normal wake sequence after a period of quiescence for XAUI transmit signals. The fault event
to be counted may occur during a refresh or a wake-up. This 16-bit counter shall be reset to all zeros when
the EEE wake error counter is read by the management function or upon execution of the PHY XS reset.
This counter shall be held at all ones in the case of overflow.
45.2.5 DTE XS registers
Change Table 45-123 (as renumbered by IEEE Std 802.3av-2009) by inserting the following rows and
changing the reserved rows as follows:
Table 45123DTE XS registers

5.20 EEE capability register
5.21 Reserved
5.22 EEE wake error counter
45.2.5.1 DTE XS control 1 register (Register 5.0)
the reserved row as follows:
Table 45124DTE XS control 1 register bit definitions
5.0.10 Clock stop enable 1 = The DTE XS may stop the clock during LPI R/W
5.0.9 XAUI stop enable 1 = The DTE XS may stop XAUI signals during R/W
LPI
0 = XAUI not stoppable

aR/W = Read/Write, SC = Self-clearing
45.2.5.1.3 Low power (50.1.11)
Insert new subclauses 45.2.5.1.3a and b after 45.2.5.1.3 as follows:
If bit 5.0.10 is set to 1, then the DTE XS may stop the receive xMII clock while it is signaling LPI, otherwise
it shall keep the clock active. If the DTE XS does not support EEE capability or is not able to stop the
receive clock, then this bit has no effect (see 46.3.2.4).
45.2.5.1.3b XAUI stop enable (5.0.9)
If bit 5.0.9 is set to 1, then the DTE XS may stop signaling on the XAUI in the transmit direction during LPI,
otherwise the DTE XS shall keep the XAUI signals active. If the DTE XS does not support EEE capability
or is not able to stop the transmit path XAUI signals, then this bit has no effect.
45.2.5.2 DTE XS status 1 register (Register 5.1)
the reserved rows as follows:
Table 45125DTE XS status 1 register bit definitions
5.1.11 Tx LPI received 1 = Tx PCS has received LPI RO/LH

5.1.10 Rx LPI received 1 = Rx PCS has received LPI RO/LH

5.1.9 Tx LPI indication 1 = Tx PCS is currently receiving LPI RO

5.1.8 Rx LPI indication 1 = Rx PCS is currently receiving LPI RO

5.1.6 Clock stop capable 1 = The MAC may stop the clock during LPI RO

a
When read as a one, bit 5.1.11 indicates that the transmit DTE XS has received LPI signaling one or more
times since the register was last read. When read as a zero, bit 5.1.11 indicates that the DTE XS has not
When read as a one, bit 5.1.10 indicates that the receive DTE XS has received LPI signaling one or more
times since the register was last read. When read as a zero, bit 5.1.10 indicates that the DTE XS has not
When read as a one, bit 5.1.9 indicates that the transmit DTE XS is currently receiving LPI signals. When
read as a zero, bit 5.1.9 indicates that the DTE XS is not currently receiving LPI signals. The behavior if read
during a state transition is undefined.
When read as a one, bit 5.1.8 indicates that the receive DTE XS is currently receiving LPI signals. When
read as a zero, bit 5.1.8 indicates that the DTE XS is not currently receiving LPI signals. The behavior if read
during a state transition is undefined.
Insert new subclause 45.2.5.2.2a before 45.2.5.2.3 as follows:
If bit 5.1.6 is set to one, then the DTE XS is indicating that the attached RS is permitted to stop the transmit
xMII clock while it is signaling LPI. If the bit is set to zero, then the DTE XS is indicating that the attached
RS is not permitted to stop the transmit xMII clock while it is signaling LPI. If the RS does not support EEE
capability or is not able to stop the transmit direction xMII clock, then this bit has no effect (see 46.3.2.4).
45.2.5.7 DTE XS package identifier (Registers 5.14 and 5.15)
This register is used to indicate the capability of the DTE XS to support EEE functions. The assignment of
bits in the EEE capability register is shown in Table 45127a.
1 = EEE is supported for DTE XS

5.20.4 DTE XS EEE RO
0 = EEE is not supported for DTE XS
1 = The PHY XS may stop XAUI signals during LPI

5.20.0 XAUI stop capable RO
0 = XAUI signals not stoppable
a
RO = Read only
45.2.5.7a.1 PHY XS EEE supported (5.20.4)
If the device supports EEE operation for DTE XS as defined in 48.2, this bit shall be set to one.
45.2.5.7a.2 XAUI stop capable (5.20.0)
If bit 5.20.0 is set to one, then the DTE XS is indicating that the attached PHY XS is permitted to stop
signalling the XAUI in the receive direction during LPI. If the bit is set to zero, then the DTE XS is
indicating that the attached PHY XS is not permitted to stop signalling the XAUI in the receive direction
during LPI. If the PHY XS does not support EEE capability or is not able to stop the receive direction XAUI,
then this bit has no effect.
This register is used by DTE XS that support EEE to count wake time faults where the DTE XS fails to
complete its normal wake sequence after a period of quiescence for XAUI receive signals. The fault event to
be counted may occur during a refresh or a wake-up. This 16-bit counter shall be reset to all zeros when the
EEE wake error counter is read by the management function or upon execution of the DTE XS reset. This
counter shall be held at all ones in the case of overflow.
45.2.7 Auto-Negotiation registers
the reserved rows as follows:.
Table 45141Auto-Negotiation MMD registers
7.49 through 7.32 767 Reserved
7.60 EEE advertisement

7.61 EEE LP ability
7.62 through 7.32 767 Reserved
45.2.7.10 10GBASE-T AN control register (Register 7.32)
Change the reserved row of Table 45-148 (as renumbered by IEEE Std 802.3av-2009) as follows:
Table 4514810GBASE-T AN control register
Value always 0, writes ignored

Reserved RO
7.32.1 1 = Advertise PHY as 10GBASE-T fast retrain capable
Fast retrain ability R/W
0 = Do not advertise PHY as 10GBASE-T fast retrain capable
a
R/W = Read/Write, R/O = Read only
45.2.7.10.5 LD PMA training reset request (7.32.2)
Insert new subclause 45.2.7.10.5a after 45.2.7.10.5:
45.2.7.10.5a Fast retrain ability
Bit 7.32.1 is used to select whether or not Auto-Negotiation advertises the ability to support 10GBASE-T
fast retrain. If bit 7.32.1 is set to one, the PHY shall advertise fast retrain ability. If bit 7.32.1 is set to zero,
the PHY shall not advertise fast retrain ability.
45.2.7.11 10GBASE-T AN status register (Register 7.33)
Change Table 45-149 (as renumbered by IEEE Std 802.3av-2009) by inserting a new row and changing
the reserved rows as follows:
Table 4514910GBASE-T AN status register
7.33.8:02 Reserved Value always 0, writes ignored RO
1 = Link partner is capable of 10GBASE-T fast retrain

7.33.1 Fast retrain ability RO
0 = Link partner is not capable of 10GBASE-T fast retrain
7.33.0 Reserved Value always 0, writes ignored RO

a RO = Read only, SC = Self-clearing, LH = Latching high
45.2.7.11.7 Link partner PMA training reset request (7.33.9)
Insert a new subclause 45.2.7.11.8 after 45.2.7.11.7:
45.2.7.11.8 Fast retrain ability
When read as a one, bit 7.33.1 is used to indicate that the link partner has the ability to support the fast
retrain capability as specified in 55.4.2.5.15. When read as a zero, bit 7.33.1 indicates that the PHY lacks the
ability to support the fast retrain capability.
45.2.7.12 Backplane Ethernet statue (Register 7.48)
Insert new subclauses 45.2.7.13 and 45.2.7.14 after 45.2.7.12 as follows:
45.2.7.13 EEE advertisement (Register 7.60)
This register defines the EEE advertisement that is sent in the unformatted next page following a EEE
technology message code as defined in 28C.12 or sent in the unformatted next page following a EEE
technology message code as defined in 73A.4 or sent as part of the 10GBASE-T extended next page as
defined in 55.6.1. The assignment of bits in the EEE advertisement register and the correspondence with the
bits in the next page messages are shown in Table 45150a.
Bits 10:0 of register 7.60 map to bits U10 through U0 respectively of the unformatted next page following a
EEE technology message code as defined in 28C.12. Bits 15:0 of register 7.60 map to bits U15 through U0
respectively of the unformatted next page following a EEE technology message code as defined in 73A.4.
Devices using Clause 28 auto-negotiation may ignore bits defined for Clause 73 auto-negotiation, and
devices using Clause 73 auto-negotiation may ignore bits defined for Clause 28 auto-negotiation.
Table 45150aEEE advertisement register (Register 7.60) bit definitions
Clause reference; next

page bit number
1 = Advertise that the 10GBASE-KR has

10GBASE-KR EEE capability
7.60.6 73.7.7.1; U6 R/W
EEE 0 = Do not advertise that the 10GBASE-
KR has EEE capability
1 = Advertise that the 10GBASE-KX4 has
10GBASE- EEE capability
7.60.5 73.7.7.1; U5 R/W
KX4 EEE 0 = Do not advertise that the 10GBASE-
KX4 has EEE capability
1 = Advertise that the 1000BASE-KX has
1000BASE- EEE capability
7.60.4 73.7.7.1; U4 R/W
KX EEE 0 = Do not advertise that the 1000BASE-
KX has EEE capability
1 = Advertise that the 10GBASE-T has
10GBASE-T EEE capability
7.60.3 28.2.3.4.1; U3 / 55.6.1; U24 R/W
EEE 0 = Do not advertise that the 10GBASE-T
has EEE capability
1 = Advertise that the 1000BASE-T has
1000BASE-T EEE capability
7.60.2 28.2.3.4.1; U2 / 55.6.1; U23 R/W
EEE 0 = Do not advertise that the 1000BASE-T
has EEE capability
1 = Advertise that the 100BASE-TX has
100BASE-TX EEE capability
7.60.1 28.2.3.4.1; U1 / 55.6.1; U22 R/W
EEE 0 = Do not advertise that the 100BASE-
TX has EEE capability

aR/W
= Read/Write, RO = Read only
45.2.7.13.1 10GBASE-KR EEE supported (7.60.6)
If the device supports EEE operation for 10GBASE-KR as defined in 72.1, and EEE operation is desired,
this bit shall be set to one.
45.2.7.13.2 10GBASE-KX4 EEE supported (7.60.5)
If the device supports EEE operation for 10GBASE-KX4 as defined in 71.2, and EEE operation is desired,
45.2.7.13.3 1000BASE-KX EEE supported (7.60.4)
If the device supports EEE operation for 1000BASE-KX as defined in 70.1, and EEE operation is desired,
45.2.7.13.4 10GBASE-T EEE supported (7.60.3)
If the device supports EEE operation for 10GBASE-T as defined in 55.1.3.3, and EEE operation is desired,
45.2.7.13.5 1000BASE-T EEE supported (7.60.2)
If the device supports EEE operation for 1000BASE-T as defined in 40.2.11, and EEE operation is desired,
45.2.7.13.6 100BASE-TX EEE supported (7.60.1)
If the device supports EEE operation for 100BASE-TX as defined in 25.4a, and EEE operation is desired,
45.2.7.14 EEE link partner ability (Register 7.61)
All of the bits in the EEE LP ability register are read-only. A write to the EEE LP ability register shall have
no effect. When the AN process has been completed, this register shall reflect the contents of the link
partners EEE advertisement register. The assignment of bits in the EEE link partner ability register and the
correspondence with the bits in the next page messages are shown in Table 45150b.
Table 45150bEEE link partner ability (Register 7.61) bit definitions

page bit number
1 = Link partner is advertising EEE

10GBASE-KR capability for 10GBASE-KR
7.61.6 73.7.7.1; U6 RO
EEE 0 = Link partner is not advertising EEE
capability for 10GBASE-KR
10GBASE-KX4 capability for 10GBASE-KX4
7.61.5 73.7.7.1; U5 RO
capability for 10GBASE-KX4
1000BASE-KX capability for 1000BASE-KX
7.61.4 73.7.7.1; U4 RO
capability for 1000BASE-KX
10GBASE-T capability for 10GBASE-T
7.61.3 28.2.3.4.1; U3 / 55.6.1; U24 RO
capability for 10GBASE-T
Table 45150bEEE link partner ability (Register 7.61) bit definitions (continued)

page bit number

1000BASE-T capability for 1000BASE-T
7.61.2 28.2.3.4.1; U2 / 55.6.1; U23 RO
capability for 1000BASE-T

100BASE-TX capability for 100BASE-TX
7.61.1 28.2.3.4.1; U1 / 55.6.1; U22 RO
capability for 100BASE-TX

a
R/W = Read/Write, RO = Read only
The definitions for the contents of the EEE LP ability register are given by the definitions for the contents on
the link partners EEE advertisement register, 7.60 (see 45.2.7.13).

Clause 45, MDIO interface10
Insert the following row into table 45.5.3.6:
45.5.3.6 PCS options
*EEE Implementation of EEE O Yes [ ]

N/A [ ]
Insert the following rows into table 45.5.3.7:
45.5.3.7 PCS management functions
RM30a EEE capability indicated for 45.2.3.8a EEE:M Yes [ ]

each port type N/A [ ]
RM30b EEE wake error counter 45.2.5.7b EEE:M Yes [ ]

behavior as specified N/A [ ]
10
Insert the following row into table 45.5.3.8:
45.5.3.8 Auto-Negotiation options
*EEE Implementation of EEE O Yes [ ]

N/A [ ]
Insert the following rows into table 45.5.3.9:
45.5.3.9 Auto-Negotiation management functions
AM58 EEE capability in advertisement 45.2.7.13 AN:EEE:M Yes [ ]

register for each port type N/A [ ]
AM59 EEE LP advertisement register 45.2.7.14 AN:EEE:M Yes [ ]

reflects link partners N/A [ ]
capabilities
AM60 Writes to EEE LP advertisement 45.2.7.14 AN:EEE:M Yes [ ]
register have no effect N/A [ ]
46. Reconciliation Sublayer (RS) and 10 Gigabit Media Independent

Interface (XGMII)
46.1 Overview
46.1.1 Summary of major concepts
Insert a new item h) at the end of the lettered list in 46.1.1 as follows:
h) The XGMII may also support Low Power Idle (LPI) signaling for PHY types supporting Energy-
Efficient Ethernet (EEE) (see Clause 78).
46.1.7 Mapping of XGMII signals to PLS service primitives
The Reconciliation Sublayer (RS) shall map the signals provided at the XGMII to the PLS service primitives
defined in Clause 6. The PLS service primitives provided by the RS and described here behave in exactly the
same manner as defined in Clause 6. Full duplex operation only is implemented at 10 Gb/s; therefore, PLS
service primitives supporting CSMA/CD operation are not mapped through the RS to the XGMII. The
mapping is changed if EEE capability is supported (see 78.3). This behavior and restrictions are the same as
described in 22.6a, with the details of the signaling described in 46.3. LPI_REQUEST shall not be set to
ASSERT unless the attached link has been operational for at least one second (i.e., link_status = OK,
according to the underlying PCS/PMA).
EEE capability requires the use of the MAC defined in Annex 4A for simplified full duplex operation (with
carrier sense deferral). This provides full duplex operation but uses the carrier sense signal to defer
transmission when the PHY is in its low power state.
Mappings for the following primitives are defined for 10 Gb/s operation:
PLS_DATA.request
PLS_DATA.indication
PLS_SIGNAL.indication
PLS_DATA_VALID.indication
Change 46.1.7.3 for carrier indication definition as follows:
46.1.7.3 Mapping of PLS_CARRIER.indication
10 Gb/s operation supports full duplex operation only. The RS never generates this primitive for PHYs that
do not support EEE or Link Interruption.
For PHYs that support EEE capability, CARRIER_STATUS is set in response to LPI_REQUEST as shown
in Figure 4610a. For PHYs that support Link Interruption, CARRIER_STATUS may be set in response to
link_fault. CARRIER_STATUS is set to CARRIER_ON if LPI_CARRIER_STATUS is TRUE or if
link_fault is Link Interruption. CARRIER_STATUS is otherwise set to CARRIER_OFF. The deferral
mechanism based upon the Link Interruption signal may be enabled or disabled by management.
Change 46.3 to show LPI signaling as follows:
46.3 XGMII functional specifications
46.3.1 Transmit
46.3.1.1 TX_CLK (10 Gb/s transmit clock)
Insert a NOTE in 46.3.1.1 for clock definitions as follows:
NOTEFor EEE capability, TX_CLK may be halted according to 46.3.1.5.
Insert the following text at the end of 46.3.1.2:
46.3.1.2 TXC<3:0> (transmit control)
A PHY with EEE capability shall interpret the combination of TXC and TXD as shown in Table 463 as an
assertion of LPI. Transition into and out of the LPI state is shown in Figure 467a.
Table 463Permissible encodings of TXC and TXD
TXC TXD Description PLS_DATA.request parameter
1 00 through 06 Reserved
1 06 Only valid on all four lanes No applicable parameter

simultaneously to request LPI (normal interframe)
NOTEValues in TXD column are in hexadecimal, most significant bit to least significant bit (i.e., <7:0>).
Insert a new subclause 46.3.1.5 after 46.3.1.4 for transmit LPI transition as follows:
46.3.1.5 Transmit direction LPI transition
LPI operation and the LPI client are described in 78.1. The RS requests the PHY to transition to the LPI state
by asserting TXC and setting TXD to 0x06 (in all lanes). The RS maintains the same state for these signals
for the entire time that the PHY is to remain in the LPI state.
The RS may halt TX_CLK at any time more than 128 clock cycles after the start of the LPI state as shown in
Figure 467a if the clock stop capable bit of the attached sublayer is asserted (see 45.2.3.2.a and 45.2.5.2.a).
It is the responsibility of the management entity to ensure that the RS does not halt the TX_CLK if the
attached device does not have its stop clock capable bit set. The RS shall restart TX_CLK so that at least one
positive transition occurs before it deaserts LPI.
The RS asserts TXC and asserts IDLE on lanes 03 in order to make the PHY transition out of the LPI state.
The RS should not present a start code for valid transmit data until after the wake-up time specified for the
PHY.
Figure 467a shows the behavior of TXC and TXD<7:0> during the transition into and out of the LPI state.
TX_CLK
07 06 07 FB x x x
TXD<7:0>
wake time
TXC enter low exit low

mode mode
NOTETXC and TXD are shown for one lane, all four lanes behave identically during LPI.
Table 463 summarizes the permissible encodings of TXD<31:0>, TXC<3:0>.
46.3.2 Receive
46.3.2.1 RX_CLK (receive clock)
Change the NOTE in 46.3.2.1 for clock definitions as follows:
NOTEThis standard neither requires nor assumes a guaranteed phase relationship between the RX_CLK and
TX_CLK signals. For EEE capability, RX_CLK may be halted according to 46.3.2.4.
Change Table 46-4 in 46.3.2.2 as follows:
46.3.2.2 RXC<3:0> (receive control)
Table 464Permissible lane encodings of RXD and RXC
RXC RXD Description PLS_DATA.indication parameter
1 06 Only valid on all four lanes simultaneously No applicable parameter
to indicate LP_IDLE is asserted (Normal interframe)
NOTEValues in RXD column are in hexadecimal, most significant bit to least significant bit (i.e., <7:0>).
Insert a new subclause 46.3.2.4 after 46.3.2.3 for receive LPI transition as follows:
46.3.2.4 Receive direction LPI transition
LPI operation and the LPI client are described in 78.1. When the PHY receives signals from the link partner
to indicate transition into the low power state, it indicates this to the RS by asserting RXC and setting RXD
to 0x06 (in all lanes). The PHY maintains these signals in this state while it remains in the LPI state. When
the PHY receives signals from the link partner to indicate transition out of the LPI state, it indicates this to
the RS by asserting RXC and asserting idle on lanes 03 to return to a normal interframe state. The RS shall
interpret the LPI coding as shown in Table 464.
The PHY or DTE XS may halt RX_CLK at any time more than 128 clock cycles after the start of the LPI
state as shown in Figure 468a if the clock stop enable bit is asserted (see 45.2.3.1.3a and 45.2.5.1.3a). The
PHY shall restart RX_CLK so that at least one positive transition occurs before it deasserts LPI.
Figure 468a shows the behavior of RXC and RXD<7:0> during LPI transitions.
RX_CLK
07 06 07 FB x x x
RXD<7:0>
wake time
RXC enter low exit low

mode mode
NOTE 1RXC and RXD are shown for one lane, all 4 lanes behave identically during LPI.
NOTE 2In some instances, LPI may be followed by characters other than IDLE during wake time.
46.3.4 Link fault signaling
Link fault signaling operates between the remote RS and the local RS. Faults detected between the remote
RS and the local RS are received by the local RS as Local Fault. Only an RS originates Remote Fault
signals.
Sublayers within the PHY are capable of detecting faults that render a link unreliable for communication.
Upon recognition of a fault condition a PHY sublayer indicates Local Fault status on the data path. When
this Local Fault status reaches an RS, the RS stops sending MAC data or LPI, and continuously generates a
Remote Fault status on the transmit data path (possibly truncating a MAC frame being transmitted). When
Remote Fault or Link Interruption status is received by an RS, the RS stops sending MAC data or LPI, and
continuously generates Idle control characters. When the RS no longer receives fault status messages, it
returns to normal operation, sending MAC data or LPI.
Status is signaled in a four byte Sequence ordered_set as shown in Table 465. The PHY indicates Local
Fault with a Sequence control character in lane 0 and data characters of 0x00 in lanes 1 and 2 plus a data
character of 0x01 in lane 3. The RS indicates a Remote Fault with a Sequence control character in lane 0 and
data characters of 0x00 in lanes 1 and 2 plus a data character of 0x02 in lane 3. Though most fault detection
is on the receive data path of a PHY, in some specific sublayers, faults can be detected on the transmit side of
the PHY. This is also indicated by the PHY with a Local Fault status.
For operation with links that may be temporarily interrupted, optional detection of a third fault condition,
Link Interruption, is provided. Link Interruption is indicated by the PHY receive function by continuously
sending the Link Interruption ordered_set as defined in Table 46-5.
Table 465Sequence ordered_sets
Lane 0 Lane 1 Lane 2 Lane 3 Description
Sequence 0x00 0x00 0x00 Reserved
Sequence 0x00 0x00 0x01 Local Fault
Sequence 0x00 0x00 0x02 Remote Fault
Sequence 0x00 0x00 0x03 Link Interruption
Sequence 0x00 0x00 0x034 Reserved
NOTEValues in Lane 1, Lane 2, and Lane 3 columns are in hexadecimal, most sig-
nificant bit to least significant bit (i.e., <7:0>). The link fault signaling state diagram
allows future standardization of reserved Sequence ordered sets for functions other
than link fault indications
The RS reports the fault status of the link. Local Fault indicates a fault detected on the receive data path
between the remote RS and the local RS. Remote Fault indicates a fault on the transmit path between the
local RS and the remote RS. The RS shall implement the link fault signaling state diagram (see
Figure 46-9).
Change 46.3.4.2 as follows:
46.3.4.2 Variables and counters
The link fault signaling state diagram uses the following variables and counters:
col_cnt
A count of the number of columns received not containing a fault_sequence. This counter
increments at RX_CLK rate (on both the rising and falling clock transitions) unless reset.
fault_sequence
A new column received on RXC<3:0> and RXD<31:0> comprising a Sequence ordered_set of
four bytes and consisting of a Sequence control character in lane 0 and a seq_type in lanes 1, 2, and
3 indicating either Local Fault, or Remote Fault, or Link Interruption.
last_seq_type
The seq_type of the previous Sequence ordered_set received
Values:Local Fault; 0x00 in lane 1, 0x00 in lane 2, 0x01 in lane 3.
Remote Fault; 0x00 in lane 1, 0x00 in lane 2, 0x02 in lane 3.
Link Interruption; 0x00 in lane 1, 0x00 in lane 2, 0x03 in lane 3.
link_fault
An indicator of the fault status.
Values:OK; No fault.
Local Fault; fault detected by the PHY.
Remote Fault; fault detection signaled by the remote RS.
Link Interruption; link temporarily unavailable, signaled by the PHY.
reset
Values:FALSE: The device is completely powered and has not been reset (default).
TRUE: The device has not been completely powered or has been reset.
seq_cnt
A count of the number of received Sequence ordered_sets of the same type.
seq_type
The value received in the current Sequence ordered_set
Values:Local Fault; 0x00 in lane 1, 0x00 in lane 2, 0x01 in lane 3.
Remote Fault; 0x00 in lane 1, 0x00 in lane 2, 0x02 in lane 3.
Link Interruption; 0x00 in lane 1, 0x00 in lane 2, 0x03 in lane 3.
Change the last two paragraphs of 46.3.4.3 as follows:
46.3.4.3 State diagram
The variable link_fault is set to OK following any interval of 128 columns not containing a Remote Fault, or
Local Fault, or Link Interruption Sequence ordered_set.
The RS output onto TXC<3:0> and TXD<31:0> is controlled by the variable link_fault.
a) link_fault = OK
The RS shall send MAC frames as requested through the PLS service interface. In the absence of
MAC frames, the RS shall generate Idle control characters.
b) link_fault = Local Fault
The RS shall continuously generate Remote Fault Sequence ordered_sets.
c) link_fault = Remote Fault or link_fault = Link Interruption
The RS shall continuously generate Idle control characters.
Insert a new subclause 46.3a before 46.4 as follows:
46.3a LPI Assertion and Detection
Certain PHYs support Energy-Efficient Ethernet (see Clause 78). PHYs with EEE capability support LPI
assertion and detection. LPI operation and the LPI client are described in 78.1. LPI signaling allows the RS
to signal to the PHY and to the link partner that a break in the data stream is expected and components may
use this information to enter power-saving modes that require additional time to resume normal operation.
Similarly, it allows the LPI client to understand that the link partner has sent such an indication.
XGMII signals as shown in Figure 469a.
The definition of TXC<3:0> and TXD<31:0> is derived from the state of PLS_DATA.request
(46.1.7), except when it is overridden by an assertion of LP_IDLE.request.
Similarly, RXC<3:0> and RXD<31:0> are mapped to PLS_DATA.indication except when
LP_IDLE is detected
PLS_CARRIER.indication(CARRIER_STATUS) will be set to CARRIER_ON when the link is in
LPI mode. See 46.1.7.3.
state diagram.
XGMII Signals
(LPI client service interface) Reconciliation sublayer
LP_IDLE.request
PLS Service Primitives re-mapping for LPI TXD<31:0>
PLS_DATA.request TXC<3:0>
TX_CLK
MAC
PLS_SIGNAL.indication
RXD<31:0>
PLS_DATA.indication RXC<3:0>
re-mapping for LPI
RX_CLK
PLS_DATA_VALID.indication
LP_IDLE.indication
or within 1 s of the change of link_status to OK.
This wake-up time is enforced by the transmit LPI state diagram using CARRIER_SENSE.indication. The
implementation shall conform to the behavior described by the transmit LPI state diagram shown in
Figure 4610a.
LPI_CARRIER_STATUS
The LPI_CARRIER_STATUS variable indicates how the CARRIER_STATUS parameter is
controlled by the LPI_REQUEST parameter. The LPI_CARRIER_STATUS is either TRUE or

FALSE as determined by the Transmit LPI state diagram in Figure 46-10a.
power_on
rs_reset
TRUE: Reset the RS.
tw_timer
A timer that counts, in microseconds, the time since the de-assertion of LPI. The terminal count of
the timer is the value of the resolved Tw_sys_tx as defined in 78.2. If DTE XS XAUI stop enable bit
is asserted (5.0.9), the terminal count of the timer is the value of the resolved Tw_sys_tx as defined
in 78.2 plus additional time equal to Tw_sys_tx Tw_sys_rx for the XGXS as shown in Table 784.
The signal tw_timer_done is asserted when tw_timer reaches its terminal count.

rs_reset + power_on
LPI_DEASSERTED
tw_timer 0
LPI_CARRIER_STATUS FALSE
LPI_REQUEST = ASSERT.
LPI_ASSERTED
LPI_CARRIER_STATUS TRUE
LPI_WAIT
start_tw_timer
tw_timer_done
Figure 4610aTransmit LPI state diagram
while it is detecting LP_IDLE on the XGMII. The receive system should be aware that data frames may
arrive at the XGMII following the de-assertion of LPI_INDICATION with a delay corresponding to the link
partners resolved Tw_sys_rx (as specified in 78.5) time, in microseconds.
If the PHY XS XAUI stop enable bit (4.0.9) is asserted, the PHY XS may stop signaling on the XAUI in the
receive direction to conserve energy. The receiver should negotiate an additional 9.5 s for the remote Tw_sys
(equal to Tw_sys_tx Tw_sys_rx for the XGXS as shown in Table 784) before setting the PHY XS XAUI stop
enable bit.
Reconciliation Sublayer (RS) and 10 Gigabit Media Independent Interface (XGMII)11
Insert a row into table 46.5.2.3 as follows:
*LPI Implementation of LPI 46.1.7 O Yes [ ]

No [ ]
46.5.3 PICS proforma Tables for Reconciliation Sublayer and 10 Gigabit Media Independent
Interface
46.5.3.3 Data stream structure
11
L1 Assertion of LPI in Tx 46.3.1.2 As defined in Table 463 LPI:M Yes [ ]

direction N/A [ ]
L2 Assertion of LPI in Rx 46.3.2.2 As defined in Table 464 LPI:M Yes [ ]

direction N/A [ ]
*L3 TX_CLK stoppable during LPI 46.3.1.5 At least 128 cycles after LPI LPI:O Yes [ ]
assertion No [ ]
L4 TX_CLK restart before LPI 46.3.1.5 At least 1 positive edge before L3:M Yes [ ]
deassert LPI deassertion N/A [ ]
L5 RX_CLK stoppable during LPI 46.3.2.4 LPI:O Yes [ ]

No [ ]
46.5.3.3b Link Interruption
LINT Detection of Link Interruption 46.3.4 O Yes [ ]

No [ ]
LINT1 CARRIER_STATUS response 46.1.7.3 Set to CARRIER_ON if LINT:O Yes [ ]

to Link Interruption link_fault is Link Interruption No [ ]
47. XGMII Extender Sublayer (XGXS) and 10 Gigabit Attachment Unit

Interface (XAUI)
Insert the following after the second paragraph of 47.1
47.1 Overview
An XGMII Extender with the optional Energy-Efficient Ethernet (EEE) capability (see 78.3) may enter a
low power state to conserve energy during periods of low link utilization. The ability to support transition to
a low power state is indicated by register 4.20.0 (for a PHY XS) or 5.20.0 (for a DTE XS). Transition to the
low power state is enabled by register 4.0.9 (for a PHY XS) or 5.0.9 (for a DTE XS). The assertion of Low
Power Idle (LPI) at the XGMII is encoded in the transmitted symbols. Detection of LPI encoding in the
received symbols is indicated as LPI at the XGMII. When LPI is received on the transmit XGMII, an
energy-efficient XGMII Extender sends sleep symbols, then, if enabled, ceases transmission and deactivates
XAUI transmit signals to conserve energy. When the receiver sees the sleep symbols it transitions to a quiet
state. The XGMII Extender periodically transmits during the quiet period to allow the attached XGMII
Extender to refresh its receiver state (e.g., timing recovery, adaptive filter coefficients) and thereby track
long-term variation in the timing of the link or the underlying channel characteristics. If, during the quiet or
refresh periods, normal interframe idle is asserted at the transmit XGMII, the XGMII Extender reactivates
transmit functions and initiates transmission. This transmission will be detected by the attached XGMII
Extender, causing it to also exit the low power state.
Insert items i) and j) into the lettered list of characteristics in 47.1 as follows:
i) Optionally extend LPI signaling to PHY for EEE

j) Optionally conserve energy during periods of low utilization
47.1.4 Allocation of functions
Insert the following new subclauses 47.1.5 and 47.1.6 after 47.1.4 as follows:
47.1.5 Global signal detect function
Global signal detect is mandatory for EEE capability, otherwise it is optional and its definition is beyond the
scope of this standard. When global signal detect is not implemented, the value of SIGNAL_DETECT shall
be set to OK for purposes of management and signaling of the primitive.
For EEE capability, the global signal detect function shall control the PMA SIGNAL_DETECT parameter.
The SIGNAL_DETECT parameter can take on one of two values, OK or FAIL, indicating whether the
XGXS is detecting electrical energy at the XAUI receiver (OK) or not (FAIL). When SIGNAL_DETECT =
FAIL, PMA parameter rx_lane<3:0> is undefined.
47.1.6 Global transmit disable function
Global transmit disable is mandatory for EEE capability. The transmit disable function shall turn off all
transmitter lanes after tx_mode changes to QUIET within a time and voltage level specified in 47.3.3.2. The
transmit disable function shall turn on all transmitter lanes after tx_mode changes to DATA within a time
and voltage level specified in 47.3.3.2.
47.3 XAUI Electrical characteristics
47.3.3 Driver characteristics
47.3.3.2 Amplitude and swing
Insert the following at the end of 47.3.3.2:
For EEE capability, the transmitter lanes differential peak-to-peak output voltage shall be less than 30 mV
within 500 ns of tx_quiet being asserted. Furthermore, the transmitter lanes differential peak-to-peak output
voltage shall be greater than 800 mV within 500 ns of tx_quiet being de-asserted.
Change Table 47-3 in 47.3.4 as follows:
47.3.4 Receiver characteristics
Receiver characteristics are summarized in Table 473 and detailed in the following subclauses.
Table 473Receiver characteristics
Parameter Value Units
Baud rate 3.125 GBd

tolerance 100 ppm
Unit interval (UI) nominal 320 ps

Receiver coupling AC
EEE Signal Detect deactivation time (TSD) from active to LPI quiet 750 ns
EEE Signal Detect activation time (TSA) from LPI quiet to active 750 ns
Return lossa
differential 10 dB
common-mode 6 dB
Jitter amplitude toleranceb 0.65 UIp-p

aRelative to 100 differential and 25 common-mode. See 47.3.4.5 for input impedance details.
bSee 47.3.4.6 for jitter tolerance details.
47.3.4.7 EEE receiver timing
For EEE capability, the receiver shall meet the timing requirements shown in Table 473 for Signal_Detect
activation and deactivation.
XGMII Extender (XGMII) and 10 Gigabit Attachment Unit Interface (XAUI)12
Insert the following row into table 48.6.3:
Yes [ ]
LPI Implementation of LPI 47.1 O
No [ ]
47.6.4 PICS Proforma tables for XGXS and XAUI
LP-01 Global signal detect 47.1.5 Meets the requirements of LPI:M Yes [ ]
47.1.5 No [ ]
LP-02 Global transmit disable 47.1.6 Meets the requirements of LPI:M Yes [ ]
47.1.6 No [ ]
LP-03 Transmit amplitude 47.3.3.2 Meets the requirements of LPI:M Yes [ ]

47.3.3.2 No [ ]
LP-04 Signal detect timing 47.3.4 Meets the requirements of LPI:M Yes [ ]
Table 473 No [ ]
12

(PMA) sublayer, type 10GBASE-X
48.1 Overview
Insert a new paragraph at the end of 48.1.5 as follows:
48.1.5 Allocation of functions
Certain PHYs support Energy-Efficient Ethernet (EEE) (see Clause 78). PHYs that support EEE (see 78.3)
use Low Power Idle (LPI) signaling to allow systems on both sides of the link to save power during periods
of low link utilization. LPI signaling may optionally be used by XGXS to extend the EEE function to
attached PHYs. Both PHY and DTE XGXS may optionally use LPI signaling to control the shutdown of
signals on the XAUI to reduce power for PHY attachments.
Change 48.2.3 for LPI code-groups and insert a new Figure 48-3a after Figure 48-3 as follows:
48.2.3 Use of code-groups
The transmission code used by the PCS, referred to as 8B/10B, is identical to that specified in Clause 36.
The PCS maps XGMII characters into 10-bit code-groups, and vice versa, using the 8B/10B block coding
scheme. Implicit in the definition of a code-group is an establishment of code-group boundaries by a PCS
Synchronization process. The 8B/10B transmission code as well as the rules by which the PCS ENCODE
and DECODE functions generate, manipulate, and interpret code-groups are specified in 36.2.4. A
10GBASE-X PCS shall meet the requirements specified in 36.2.4.1 through 36.2.4.6, 36.2.4.8, and 36.2.4.9.
PCS lanes are independent of one another. All code-group rules specified in 36.2.4 are applicable to each
lane. The mapping of XGMII characters to PCS code-groups is specified in Table 482. The mapping of
PCS code-groups to XGMII characters is specified in Table 483. PHYs that support EEE are able to
transmit and receive LPI characters.
Figure 483 illustrates the mapping of an example XGMII character stream into a PCS code-group stream.
Figure 483a illustrates the mapping during LPI.
The relationship of code-group bit positions to XGMII, PCS and PMA constructs and PMD bit transmission
order, exemplified for lane 0, is illustrated in Figure 484.
LPI sleep/quiet/refresh wake time

XGMII
T/RXD<7:0> I I LI LI LI LI LI --- LI LI LI I I --- I S Dp D
T/RXD<15:8> I I LI LI LI LI LI --- LI LI LI I I --- I Dp Dp D
T/RXD<23:16> I I LI LI LI LI LI --- LI LI LI I I --- I Dp Dp D
T/RXD<31:24> I I LI LI LI LI LI --- LI LI LI I I --- I Dp Ds D
active time active time
PCS
LANE 0 K R R K R A K --- LL R K K A --- R S Dp D
LANE 1 K R LL K R A K --- R R K K A --- R Dp Dp D
LANE 2 K R R K LL A LL --- R R LL K A --- R Dp Dp D
LANE 3 K R R LL R A K --- R LL K K A --- R Dp Ds D
Legend:
LI represents the data character containing the XGMII LPI pattern (06)
LL represents the LPI indication code-group /D20.5/
Dp represents a data character containing the preamble pattern
Ds represents a data character containing the SFD pattern
Figure 483aXGMII and PCS mapping example with optional LPI
In 48.2.4, insert a row in Table 48-2 below Normal data transmission; insert a row in Table 48-3 below
Normal data reception; and change rows in Link Status section of Table 48-4 as follows:
48.2.4 Ordered_sets and special code-groups.
Table 482XGMII character to PCS code-group mapping
XGMII
XGMII TXD PCS code-group Description
TXC
1 06 K28.0 or K28.3 or K28.5 or D20.5a Assert LPI
NOTEValues in TXD column are in hexadecimal.

aInsertion of /D20.5/ is per the rules described in 48.2.4.2.
Table 483PCS code-group to XGMII character mapping
XGMII
XGMII RXD PCS code-group Description
RXC
1 06 K28.0 or K28.3 or K28.5 or D20.5a Assert LPI
NOTEValues in RXD column are in hexadecimal.

a
Insertion of /D20.5/ is per the rules described in 48.2.4.2.
Table 484Defined ordered_sets and special code-groups
Number of
Code Ordered_Set Encoding
code-groups
Link Status
||Q|| Sequence ordered_set 4 /K28.4/Dx.y/Dx.y/Dx.y/a
||LF|| Local Fault signal 4 /K28.4/D0.0/D0.0/D1.0/
||RF|| Remote Fault signal 4 /K28.4/D0.0/D0.0/D2.0/
||LINT|| Link Interruption signal 4 /K28.4/D0.0/D0.0/D3.0/
||Qrsvd|| Reserved 4 !||LF|| and !||RF|| and !||LINT||

a/Dx.y/
indicates any data code-group.
Change 48.2.4.2 for LPI definitions as follows:
48.2.4.2 Idle (||I||) and Low Power Idle (||LPIDLE||)
Idle ordered_sets (||I||) are transmitted in full columns continuously and repetitively whenever the XGMII is
idle (TXD<31:0>=0x07070707 and TXC<3:0>=0xF). ||I|| provides a continuous fill pattern to establish and
maintain lane synchronization, perform lane-to-lane deskew and perform PHY clock rate compensation. ||I||
is emitted from, and interpreted by, the PCS.
A sequence of ||I|| ordered_sets consists of one or more consecutively transmitted ||K||, ||R|| or ||A||
ordered_sets, as defined in Table 484. Rules for ||I|| ordered_set sequencing shall be as follows:
a) ||I|| sequencing starts with the first column following a ||T||.

b) The first ||I|| following ||T|| alternates between ||A|| or ||K|| except if an ||A|| is to be sent and less than
r [see item d)] columns have been sent since the last ||A||, a ||K|| is sent instead.
c) ||R|| is chosen as the second ||I|| following ||T||.
d) Each ||A|| is sent after r non-||A|| columns where r is a randomly distributed number between 16 and
31, inclusive. The corresponding minimum spacing of 16 non-||A|| columns between two ||A|| col-
umns provides a theoretical 85-bit deskew capability.
e) When not sending an ||A||, either ||K|| or ||R|| is sent with a random uniform distribution between the
two.
f) Whenever sync_status=OK, all ||I|| received during idle are translated to XGMII Idle control charac-
ters for transmission over the XGMII. All other !||I|| received during idle are mapped directly to
XGMII data or control characters on a lane by lane basis, with the following exceptions for PHYs
with EEE capability:
1) /D20.5/ (LPI) being detected in any lane and the rest of the lanes in the same column being
detected /K/ only or /R/ only, which will result in reporting LP_IDLE characters in all lanes.
2) ||A|| being detected and /D20.5/ (LPI) being detected in any lane of the previous column and the
rest of the lanes in the previous column being detected /K/ only or /R/ only, which will result in
reporting LP_IDLE characters in all lanes.
The purpose of randomizing the ||I|| sequence is to reduce 10GBASE-X electromagnetic interference (EMI)
during idle. The randomized ||I|| sequence produces no discrete spectrum. Both ||A|| spacing as well as ||K||,
||R||, or ||A|| selection shall be based on the generation of a random integer r generated by a PRBS based on
one of the 7th order polynomials listed in Figure 485. ||A|| spacing is set to the next generated value of r.
The rate of generation of r is once per column, 312.5 MHz 100 ppm. Once the ||A|| spacing count goes to
zero (A_CNT=0), ||A|| is selected for transmission at the next opportunity during the Idle sequence. ||K|| and
||R|| selection follows the value of code_sel, which is continuously set according to the even or odd value of
r. The method of generating the random integer r is left to the implementor. PCS Idle randomizer logic is
illustrated in Figure 48-5.
||LPIDLE|| is coded in the same manner as ||I|| except that the /D20.5/ code-group replaces one code-group in
each ||K|| or ||R|| (not ||A||) column with a random uniform distribution across the lanes. Insertion of /D20.5/
does not alter the distribution of ||A||, ||K|| or ||R||. Clock compensation may be performed during LPI
according to the rules described in 48.2.4.2.3.
Insert the following at the end of 48.2.4.2.3:
48.2.4.2.3 Skip ||R||
For EEE capability, a column containing three /R/ code-groups and one /D20.5/ code-group may be inserted
or deleted in the same manner as four /R/ code-groups.
48.2.6.1 State variables
Change the following constant definitions in 48.2.6.1.2 as follows:
||K||
The column of four identical Idle Sync code-groups corresponding to the Idle Sync function
specified in 48.2.4.2.1. For EEE capability, one lane of ||K|| is replaced by /D20.5/ during the
assertion of LPI as defined in 48.2.4.2.
||R||
The column of four identical Idle Skip code-groups corresponding to the Idle Skip function
specified in 48.2.4.2.3. For EEE capability, one lane of ||R|| is replaced by /D20.5/ during the
assertion of LPI as defined in 48.2.4.2.
Insert the following text into 48.2.6.1.2 at the end of the existing subclause:
The following constants are used only for the EEE capability:
||LPIDLE||
The column consisting of three /K/ characters and one of /D20.5/, or three /R/ characters and one
/D20.5/, or a column of ||A|| preceded by a column containing three /K/ characters and one /D20.5/
or three /R/ characters and one /D20.5/ as specified in 48.2.4.2.
Insert a NOTE in 48.2.6.1.3 below the definition for align_status as follows:
NOTEFor EEE capability, this variable is affected by the LPI receive state diagram. Without EEE capability this
variable is identical to deskew_align_status controlled by the deskew state diagram.
Insert new variables into 48.2.6.1.3 at the end of the existing subclause as follows:
deskew_align_status
Variable used by the deskew state diagram to reflect the status of the lane-to-lane code-group
alignment.
Values: FAIL; The deskew process is not complete.

OK; All lanes are synchronized and aligned.
rx_lpi_active
when it is in an active state and is not restricted by the LPI receive state diagram.
rx_quiet
A Boolean variable set to TRUE while in the RX_QUIET state and set to FALSE otherwise. When
this variable is TRUE it indicates that receive PCS and PMD may power-down nonessential
functions.
tx_quiet
A Boolean variable set to TRUE when the transmitter is in the TX_QUIET state and set to FALSE
otherwise. When set to TRUE, the PMD will disable the transmitter as described in 71.6.6. When
this variable is TRUE it indicates that transmit PCS and PMD may power-down nonessential
functions.
Insert new timers into 48.2.6.1.5 at the end of the existing subclause as follows:
48.2.6.1.5 Counters
The following counter is used only for the EEE capability:
wake_error_counter
(see 45.2.3.8b)
48.2.6.1.5a Timers
The following timers are used only for the EEE capability.
rx_tq_timer
This timer is started when the PCS receiver enters the RX_SLEEP state. The timer terminal count
is set to TQR. When the timer reaches terminal count it will set the rx_tq_timer_done = TRUE.
rx_tw_timer
shall be set to a value no larger than the maximum value given for TWR in Table 4810. When the
timer reaches terminal count it will set the rx_tw_timer_done = TRUE.
rx_wf_timer
which to synchronize or return to the QUIET state before a link failure is indicated. The timer
terminal count is set to TWTF. When the timer reaches terminal count it will set the
tx_ts_timer
count is set to TSL. When the timer reaches terminal count it will set the tx_ts_timer_done =
TRUE.
tx_tq_timer
count is set to TQL. When the timer reaches terminal count it will set the tx_tq_timer_done =
TRUE.
tx_tr_timer
This timer is started when the PCS transmitter enters the TX_REFRESH state. The timer terminal
count is set to TUL. When the timer reaches terminal count it will set the tx_tr_timer_done =
TRUE.
48.2.6.1.6 Message
Insert new messages into 48.2.6.1.6 at the end of the existing subclause as follows:
The following messages are used only for the EEE capability:
A signal sent by the PCS LPI receive state diagram to the PMD. When TRUE this indicates that
the receiver is in a quiet state and is not expecting incoming data.
A signal sent by the PCS LPI transmit state diagram to the PMD. When TRUE this indicates that
the transmitter is in a quiet state and may cease to transmit a signal on the medium.
48.2.6.2 State diagrams
Change Figure 48-6 (PCS transmit source state diagram), Figure 48-8 (PCS deskew state diagram), and
Figure 48-9 (PCS receive state diagram), as follows:
!reset *
!(TX=||IDLE|| + TX=||LPIDLE|| + TX=||Q||)
SEND_DATA
IF TX=||T|| THEN cvtx_terminate

tx_code-group<39:0>
ENCODE(TX)
PUDR
next_ifg=A * A_CNT=0 (next_ifg=K + A_CNT0) reset
SEND_A
TX_CLK *
SEND_K
tx_code-group<39:0> ||A||
next_ifg K tx_code-group<39:0> ||K||
PUDR next_ifg A
PUDR
Q_det !Q_det
UCT
B
SEND_Q
tx_code-group<39:0> TQMSG
Q_det false
A_CNT0 * A
PUDR
code_sel=1
UCT B
SEND_RANDOM_K
tx_code-group<39:0> ||K||
a
SEND_RANDOM_R
PUDR
tx_code-group<39:0> ||R||
a
PUDR A_CNT0 *
code_sel=1
A_CNT0 * B
code_sel=0 A
A_CNT=0
A_CNT=0
A_CNT0 *
A
SEND_RANDOM_A code_sel=0
tx_code-group<39:0> ||A||
PUDR
Q_det
!Q_det *
B
code_sel=1
SEND_RANDOM_Q
tx_code-group<39:0> TQMSG
Q_det false !Q_det *
PUDR A
code_sel=0
B code_sel=1
A code_sel=0
a
If TX=||LPIDLE|| one lane is replaced by /D20.5/ as defined in 48.2.4.2.
NOTEThe state diagram makes exactly one transition for each transmit code-group processed.
Figure 486PCS transmit source state diagram
reset + (sync_status=FAIL * SUDI)
LOSS_OF_ALIGNMENT
SUDI(![||A||]) deskew_align_status FAIL

enable_deskew TRUE
AUDI
sync_status=OK * SUDI([||A||])
ALIGN_DETECT_1
!deskew_error
enable_deskew FALSE * SUDI(![||A||])
AUDI
deskew_error * SUDI
SUDI([||A||])
ALIGN_DETECT_2
!deskew_error
AUDI * SUDI(![||A||])
deskew_error * SUDI
SUDI([||A||])
ALIGN_DETECT_3
!deskew_error
deskew_error * SUDI
SUDI([||A||])
A
ALIGN_ACQUIRED_1
!deskew_error *
deskew_align_status OK SUDI
AUDI
deskew_error
* SUDI
B
ALIGN_ACQUIRED_2
!deskew_error
deskew_error
* SUDI
SUDI([||A||])
A
C
ALIGN_ACQUIRED_3 !deskew_error
deskew_error
* SUDI
SUDI([||A||])
ALIGN_ACQUIRED_4 !deskew_error
deskew_error * SUDI
SUDI([||A||])
Figure 488PCS deskew state diagram
reset + align_status=FAIL
LOCAL_FAULT_INDICATE
RXLFAULT
align_status=OK * AUDI
RECEIVE
ELSE [||IDLE||]
[||LPIDLE||]
DATA_MODE
IDLE_MODE
RX DECODE([||y||])
check_end RXIDLE
IF RX=||T|| THEN cvrx_terminate
LPIDLE_MODE
AUDI AUDI
RXLPIDLE
AUDI *
!rx_lpi_active
NOTEOptional state to support LPI is shown inside the dotted box. The transition to the optional state is only
possible with EEE capability.
Figure 489PCS receive state diagram
Change the last paragraph 48.2.6.2.2 as follows:
48.2.6.2.2 Synchronization
Once synchronization is acquired, the Synchronization process tests received code-groups in sets of four
code-groups and employs multiple sub-states, effecting hysteresis, to move between the
SYNC_ACQUIRED_1 and LOSS_OF_SYNC states. The Synchronization process sets the
lane_sync_status <3:0> flags to indicate whether the PMA is functioning dependably (as well as can be
determined without exhaustive error-rate analysis). Whenever any PMA lane is not operating dependably, as
indicated by the setting of lane_sync_status <3:0>, the align_status deskew_align_status flag is set to FAIL.
Change the first paragraph of 48.2.6.2.3 as follows:
48.2.6.2.3 Deskew
The PCS shall implement the Deskew process as depicted in Figure 488 including compliance with the
associated state variables as specified in 48.2.6.1. The Deskew process is responsible for determining
whether the underlying receive channel is capable of presenting coherent data to the XGMII. The Deskew
process asserts the deskew_align_status align_status flag to indicate that the PCS has successfully deskewed
and aligned code-groups on all lanes. The Deskew process attempts deskew and alignment whenever the
deskew_align_status align_status flag is de-asserted. The Deskew process is otherwise idle. For the EEE
capability the relationship between align_status and deskew_align_status is given by Figure 489b,
otherwise align_status is identical to deskew_align_status. Whenever the align_status flag is set to FAIL the
condition is indicated as a link_status=FAIL condition in the status register bit 4.1.2 or 5.1.2.
Change the first paragraph of 48.2.6.2.4 as follows:
48.2.6.2.4 Receive
The PCS shall implement its Receive process as depicted in Figure 489, including compliance with the
associated state variables as specified in 48.2.6.1 and including the optional EEE capability.
Insert two new subclauses 48.2.6.2.5 and 48.2.6.2.6 after 48.2.6.2.4 as follows:
48.2.6.2.5 LPI state diagrams
A PCS that supports the EEE capability shall implement the LPI transmit and receive processes as shown in
Figure 489a and Figure 489b. The transmit LPI state diagram controls tx_quiet, which disables the
transmitter when TRUE. The receive LPI state diagram controls align_status during LPI and synchronizes
the receive state diagram with the end of the LPI.
reset
TX_ACTIVE
tx_quiet FALSE
TX ||LPIDLE||
TX = ||LPIDLE||
TX_SLEEP
Start tx_ts_timer
TX ||LPIDLE||
TX = ||LPIDLE|| *
tx_ts_timer_done
TX_QUIET
tx_quiet TRUE
Start tx_tq_timer
TX ||LPIDLE||
TX = ||LPIDLE|| *
tx_tq_timer_done
TX_REFRESH
tx_quiet FALSE
Start tx_tr_timer
TX = ||LPIDLE|| * TX ||LPIDLE||
tx_tr_timer_done
Figure 489aLPI Transmit state diagram
reset A
RX_ACTIVE
rx_lpi_active FALSE
rx_quiet FALSE
align_status deskew_align_status
align_status deskew_align_status
||LPIDLE|| *
align_status = deskew_align_status
signal_detect=OK * RX_SLEEP
||LPIDLE|| * rx_lpi_active TRUE
!rx_tq_timer_done Start rx_tq_timer
||IDLE|| * !rx_tq_timer_done *
signal_detect=OK * deskew_align_status=OK
B
(signal_detect=FAIL) * rx_tq_timer_done
!rx_tq_timer_done
RX_QUIET
rx_quiet TRUE
signal_detect=FAIL *
signal_detect=OK
rx_tq_timer_done
RX_WAKE
signal_detect=OK *
!rx_tw_timer_done * rx_quiet FALSE
Start rx_tw_timer
deskew_align_status = OK *
||LPIDLE|| rx_tw_timer_done
B RX_WTF
!rx_tw_timer_done * wake_error_counter++
start rx_wf_timer
signal_detect=FAIL
A
signal_detect=OK *
!rx_tw_timer_done * signal_detect=OK *
deskew_align_status = OK * rx_wf_timer_done
||IDLE||
signal_detect=OK * RX_LINK_FAIL
!rx_wf_timer_done * B
rx_quiet FALSE
deskew_align_status = OK * align_status FAIL
signal_detect
||LPIDLE|| =FAIL
UCT
signal_detect=OK *
!rx_wf_timer_done *
deskew_align_status = OK *
! ||LPIDLE||
Figure 489bLPI Receive state diagram
The LPI functions shall use timer values for these state diagrams as shown in Table 489 for transmit and
Table 4810 for receive.
Table 489Transmitter LPI timing parameters
TSL Local Sleep Time from entering the TX_SLEEP state to when tx_quiet is 19.9 20.1 s
set to TRUE
TQL Local Quiet Time from when tx_quiet is set to TRUE to entry into the 2.5 2.6 ms
TX_REFRESH state
TUL Local Refresh Time from entry into the TX_REFRESH state to entry into 19.9 20.1 s
the TX_QUIET state
Table 4810Receiver LPI timing parameters
TQR The time the receiver waits for signal detect to be set to OK while in the 3 4 ms
RX_SLEEP and RX_QUIET states before asserting rx_fault
TWR Time the receiver waits in the RX_WAKE state before indicating a wake 9 s
time fault
48.2.6.2.6 LPI status and management
For EEE capability, the PCS indicates to the management system that LPI is currently active in the receive
and transmit directions using the status variable shown in Table 4811.
Table 4811MDIO status indications
Register
address
Tx LPI received PCS status register 1 3.1.11 Latched version of 3.1.9

Rx LPI received PCS status register 1 3.1.10 Latched version of 3.1.8
Tx LPI indication PCS status register 1 3.1.9 TRUE when not in state TX_ACTIVE
Rx LPI indication PCS status register 1 3.1.8 TRUE when not in state RX_ACTIVE
Tx LPI received PHY XS status register 1 4.1.11 Latched version of 4.1.9
Rx LPI received PHY XS status register 1 4.1.10 Latched version of 4.1.8
Tx LPI indication PHY XS status register 1 4.1.9 TRUE when not in state TX_ACTIVE
Rx LPI indication PHY XS status register 1 4.1.8 TRUE when not in state RX_ACTIVE
Tx LPI received DTE XS status register 1 5.1.11 Latched version of 5.1.9
Table 4811MDIO status indications (continued)
Register
address
Rx LPI received DTE XS status register 1 5.1.10 Latched version of 5.1.8

Tx LPI indication DTE XS status register 1 5.1.9 TRUE when not in state TX_ACTIVE
Rx LPI indication DTE XS status register 1 5.1.8 TRUE when not in state RX_ACTIVE
48.7 Protocol implementation conformance statement (PICS) proforma for Physical

Coding Sublayer (PCS) and Physical Medium Attachment (PMA) sublayer, type
10GBASE-X13
Yes [ ]
LPI Implementation of LPI 48.2.3 O
No [ ]
48.7.4 PICS proforma tables for the PCS and PMA sublayer, type 10GBASE-X
LP-01 Receive state diagrams 48.2.6.2 Support additions to LPI:M Yes [ ]

Figure 489 for LPI operation No [ ]
LP-01 LPI transmit state diagrams 48.2.6.2.5 Meet the requirements of LPI:M Yes [ ]
Figure 489a No [ ]
LP-01 LPI receive state diagrams 48.2.6.2.5 Meet the requirements of LPI:M Yes [ ]
Figure 489b No [ ]
LP-01 LPI transmit timing 48.2.6.2.5 Meet the requirements of LPI:M Yes [ ]
Table 489 No [ ]
LP-01 LPI receive timing 48.2.6.2.5 Meet the requirements of LPI:M Yes [ ]
Table 4810 No [ ]
13
49. Physical Coding Sublayer (PCS) for 64B/66B, type 10GBASE-R
49.1 Overview
49.1.5 Inter-sublayer interfaces
Insert the new following paragraph after the second paragraph in 49.1.5:
If the optional Energy-Efficient Ethernet (EEE) capability is supported (see Clause 78, 78.3) then the
interface with the PMA sublayer (or FEC sublayer) includes rx_mode and tx_mode to control power states
in lower sublayers and energy_detect that indicates whether the PMD sublayer has detected a signal at the
receiver. If the PHY includes an FEC sublayer, the interface includes rx_lpi_active to indicate that the LPI
receive state diagram is not in RX_ACTIVE state.
It is important to note that, while this specification defines interfaces in terms of bits, octets, and frames,
implementations may choose other data-path widths for implementation convenience.
49.1.6 Functional block diagram
Replace existing Figure 494 with a new figure as follows:
XGMII
TXD<31:0> RXD<31:0>
TXC<3:0> RXC<3:0>
TX_CLK RX_CLK
PCS
PCS TRANSMIT PCS RECEIVE
ENCODE DECODE
SCRAMBLE DESCRAMBLE
GEAR BOX BER & SYNC HEADER BLOCK SYNC LPI

MONITOR
PCS_R_STATUS rx_data-unit<15:0> (for WIS) or

(WIS only) rx_data-group<15:0> (for PMA)
tx_data-unit<15:0> (for WIS) or
tx_data-group<15:0> (for PMA)
signal_ok energy_detect
tx_mode
(EEE only)
rx_mode
rx_lpi_active (FEC only)
PMA, FEC sublayer or WIS
49.2.4 64B/66B transmission code
49.2.4.4 Control codes
Change the second paragraph of 49.2.4.4 for LPI function as follows:
The control characters and their mappings to 10GBASE-R control codes and XGMII control codes are
specified in Table 491. All XGMII and 10GBASE-R control code values that do not appear in the table
shall not be transmitted and shall be treated as an error if received. The ability to transmit or receive Low
Power Idle (LPI) is required for PHYs that support EEE (see Clause 78). If EEE is not supported, LPI shall
not be transmitted and shall be treated as an error if received.
49.2.4.5 Ordered sets
Change Table 49-1 for LPI encoding as follows:
Table 491Control codes
Control XGMII control 10GBASE-R 10GBASE-R

Notation 8B/10B codea
character code control code O code
Idle /I/ 0x07 0x00 K28.0 or

K28.3 or
K28.5
LPI /LI/ 0x06 0x06 K28.0 with D20.5 in

one row or K28.3 or
K28.5 with D20.5 in
one rowb
Start /S/ 0xfb Encoded by block K27.7

type field
a
For information only.The 8B/10B code is specified in Clause 36. Usage of the 8B/10B code for 10 Gb/s operation is
specified in Clause 48.
b
See 48.2.4.2.
Change 49.2.4.7 for LPI definitions as follows:
49.2.4.7 Idle /I/ and Low Power Idle /LI/
Idle control characters (/I/) are transmitted when idle control characters are received from the XGMII. Idle
characters may be added or deleted by the PCS to adapt between clock rates. /I/ insertion and deletion shall
occur in groups of 4. /I/s may be added following idle or ordered sets. They shall not be added while data is
being received. When deleting /I/s, the first four characters after a /T/ shall not be deleted.
To communicate LPI, LPI control character /LI/ is sent continuously in place of /I/. LPI control characters
are transmitted when LPI control characters are received from the XGMII. LPI characters may be added or
deleted by the PCS to adapt between clock rates in a similar manner to idle control characters. /LI/ insertion
and deletion shall occur in groups of four. /LI/s may only be added following other LPI characters.
Change 49.2.6 for scrambler bypass as follows:
49.2.6 Scrambler
The payload of the block is scrambled with a self-synchronizing scrambler. The scrambler shall produce the
same result as the implementation shown in Figure 495. This implements the scrambler polynomial:14
39 58
G(x) = 1 + x +x (491)
There is no requirement on the initial value for the scrambler. The scrambler is run continuously on all
payload bits. The sync header bits bypass the scrambler.
14
The convention here, which considers the most recent bit into the scrambler to be the lowest order term, is consistent with most
references and with other scramblers shown in this standard. Some references consider the most recent bit into the scrambler to be the
highest order term and would therefore identify this as the inverse of the polynomial in Equation (491). In case of doubt, note that the
conformance requirement is based on the representation of the scrambler in the figure rather than the polynomial equation.
Serial Data Input
S0 S1 S2 S38 S39 S56 S57
Scrambled Data Output
Data output when scrambler_bypass is TRUE
NOTEScrambler_bypass is only required to support EEE capability.
Figure 495Scrambler
To aid block synchronization in the receiver for EEE capability when Clause 74 FEC is in use, when
scrambler_bypass is TRUE the PCS shall pass the unscrambled data from the scrambler input rather than the
scrambled data from the scrambler output. The scrambler shall continue to advance normally.
Change 49.2.9 and replace Figure 49-12 as follows:
49.2.9 Block synchronization
When the receive channel is operating in normal mode, the block synchronization function receives data via
16-bit PMA_UNITDATA.request or WIS_UNITDATA.request primitives. It shall form a bit stream from
the primitives by concatenating requests with the bits of each primitive in order from rx_data-group<0> to
rx_data-group<15> (see Figure 496). It obtains lock to the 66-bit blocks in the bit stream using the sync
headers and outputs 66-bit blocks. Lock is obtained as specified in the block lock state diagram shown in
Figure 4912.
If EEE is not supported then block_lock is identical to rx_block_lock. Otherwise the relationship between
block_lock and rx_block_lock is given by Figure 4915.
reset +
!signal_ok
LOCK_INIT
rx_block_lock FALSE
test_sh FALSE
UCT
RESET_CNT
sh_cnt 0
sh_invalid_cnt 0
slip_done FALSE
test_sh
TEST_SH
test_sh
FALSE
sh_valid !sh_valid
VALID_SH INVALID_SH
sh_cnt ++ sh_cnt ++
sh_invalid_cnt ++
test_sh sh_cnt = 64 sh_cnt = 64 test_sh sh_cnt < 64

sh_cnt < 64 sh_invalid_cnt > 0 sh_invalid_cnt < 16 sh_invalid_cnt < 16
rx_block_lock rx_block_lock
sh_cnt = 64
sh_invalid_cnt = 0 sh_invalid_cnt = 16
+ !rx_block_lock
64_GOOD SLIP
rx_block_lock TRUE rx_block_lock FALSE
SLIP
UCT slip_done
Figure 4912Lock state diagram
Change Figure 4913 for BER monitor as follows:
reset + r_test_mode +
!rx_block_lock + rx_lpi_active
BER_MT_INIT
hi_ber FALSE
ber_test_sh FALSE
UCT
START_TIMER
ber_cnt 0
start 125s_timer
ber_test_sh
BER_TEST_SH
ber_test_sh
!sh_valid sh_valid
125s_timer_done
BER_BAD_SH
ber_cnt ++
ber_test_sh ber_cnt < 16

ber_cnt < 16 125s_timer_done
125s_timer_not_done
ber_cnt =16
HI_BER GOOD_BER
hi_ber TRUE hi_ber FALSE
125s_timer_done UCT
Figure 4913BER monitor state diagram
Insert a NOTE in 49.2.13.2.2 below the definition for block_lock as follows:
NOTEIf the EEE capability is supported, then this variable is affected by the LPI receive state diagram. If the EEE
capability is not supported then this variable is identical to rx_block_lock controlled by the lock state diagram.
Insert new variables and text at the end of the existing subclause as follows:
energy_detect
A Boolean variable sent from the PMD that is set to TRUE when signal energy is detected at the
receiver and is set to FALSE otherwise
rx_block_lock
Variable used by the lock state diagram to reflect the status of the code-group delineation. This
variable is set TRUE when the receiver acquires block delineation.
rx_lpi_active
when it is in an active state and capable of receiving data.
rx_mode
A variable set to QUIET while the receiver is in the RX_QUIET state and set to DATA otherwise
tx_mode
A variable set to QUIET when the transmitter is in the TX_QUIET state, set to ALERT when the
transmitter is in the TX_ALERT state, and set to DATA otherwise. When set to QUIET, the PMD
disables the transmitter as described in 72.6.5. When set to ALERT, the PMD transmits a repeating
pattern of eight ones and eight zeroes as described in 72.6.2. When set to DATA the PMD passes
data as normal.
scrambler_bypass
This Boolean variable is used to bypass the Tx PCS scrambler in order to assist rapid
synchronization following low power idle. When set to TRUE, the PCS will pass the unscrambled
data from the scrambler input rather than the scrambled data from the scrambler output. The
scrambler will continue to operate normally, shifting input data into the delay line. When
scrambler_bypass is set to FALSE the PCS will pass scrambled data from the scrambler output.
scr_bypass_enable
A Boolean variable used to indicate to the transmit LPI state diagram that the scrambler bypass
option is required. The PHY shall set scr_bypass_enable = TRUE if Clause 74 FEC is in use. The
PHY shall set scr_bypass_enable = FALSE if this FEC is not in use.
Change 49.2.13.2.3 function definitions for LPI block types as follows:
49.2.13.2.3 Functions
DECODE(rx_coded<65:0>)
Decodes the 66-bit vector returning rx_raw<71:0> which is sent to the XGMII. The DECODE
function shall decode the block as specified in 49.2.4.
ENCODE(tx_raw<71:0>)
Encodes the 72-bit vector returning tx_coded<65:0> of which tx_coded<63:0> is sent to the
scrambler. The two high order sync bits bypass the scrambler. The ENCODE function shall encode
the block as specified in 49.2.4.
R_BLOCK_TYPE = {C, S, T, D, E, LI}
This function classifies each 66-bit rx_coded vector as belonging to one of the five following types
depending on its contents.
Values: C; The vector contains a sync header of 10 and one of the following:
a) A block type field of 0x1e and eight valid control characters other than /E/ and, if
the EEE capability is supported, zero or four of the characters are /LI/;
b) A block type field of 0x2d or 0x4b, a valid O code, and four valid control
characters;
c) A block type field of 0x55 and two valid O codes.
LI; For EEE capability, the LI type is supported where the vector contains a sync header
of 10, a block type field of 0x1e, and eight control characters of 0x06 (/LI/).
S; The vector contains a sync header of 10 and one of the following:
a) A block type field of 0x33 and four valid control characters;
b) A block type field of 0x66 and a valid O code;
c) A block type field of 0x78.
T; The vector contains a sync header of 10, a block type field of 0x87, 0x99, 0xaa, 0xb4,
0xcc, 0xd2, 0xe1 or 0xff and all control characters are valid.
D; The vector contains a sync header of 01.
E; The vector does not meet the criteria for any other value.
A valid control character is one containing a 10GBASE-R control code specified in Table 491. A
valid O code is one containing an O code specified in Table 491.
NOTEA PCS that does not support EEE classifies vectors containing one or more /LI/ control characters as
type E.
R_TYPE(rx_coded<65:0>)
Returns the R_BLOCK_TYPE of the rx_coded<65:0> bit vector.
R_TYPE_NEXT
Prescient end of packet check function. It returns the R_BLOCK_TYPE of the rx_coded vector
immediately following the current rx_coded vector.
SLIP
Causes the next candidate block sync position to be tested. The precise method for determining the
next candidate block sync position is not specified and is implementation dependent. However, an
implementation shall ensure that all possible bit positions are evaluated.
T_BLOCK_TYPE = {C, S, T, D, E, LI}
This function classifies each 72-bit tx_raw vector as belonging to one of the five following types
depending on its contents.
Values: C; The vector contains one of the following:

a) eight valid control characters other than /O/, /S/, /T/, /E/ and, if the EEE capability
is supported, zero or four of the characters are /LI/;
b) one valid ordered_set and four valid control characters other than /O/, /S/ and /T/;
c) two valid ordered sets.
LI; For EEE capability, this vector contains eight /LI/ characters.
S; The vector contains an /S/ in its first or fifth character, any characters before the S
character are valid control characters other than /O/, /S/ and /T/ or form a valid
ordered_set, and all characters following the /S/ are data characters.
T; The vector contains a /T/ in one of its characters, all characters before the /T/ are data
characters, and all characters following the /T/ are valid control characters other
than /O/, /S/ and /T/.
D; The vector contains eight data characters.
A tx_raw character is a control character if its associated TXC bit is asserted. A valid control
character is one containing an XGMII control code specified in Table 491. A valid ordered_set
consists of a valid /O/ character in the first or fifth characters and data characters in the three
characters following the /O/. A valid /O/ is any character with a value for O code in Table 491.
NOTEA PCS that does not support EEE, classifies vectors containing one or more /LI/ control characters as
type E.
T_TYPE(tx_raw<71:0>)
Returns the T_BLOCK_TYPE of the tx_raw<71:0> bit vector.
Insert new counters into 49.2.13.2.4 at the end of the existing subclause:
49.2.13.2.4 Counters
The following counter is used only for the EEE capability.
wake_error_counter
(see 45.2.3.8b).
Insert new timers into 49.2.13.2.5 at the end of the existing subclause:
49.2.13.2.5 Timers
The following timers are used only for the EEE capability:
one_us_timer
A timer used to count approximately 1 s intervals. The timer terminal count is set to T1U. When
the timer reaches terminal count it will set the one_us_timer_done = TRUE.
rx_tq_timer
This timer is started when the PCS receiver enters the RX_SLEEP state. The timer terminal count
is set to TQR. When the timer reaches terminal count it will set the rx_tq_timer_done = TRUE.
rx_tw_timer
shall be set to a value no larger than the maximum value given for TWR in Table 493. When the
timer reaches terminal count it will set the rx_tw_timer_done = TRUE.
rx_wf_timer
which to synchronize or return to the QUIET state before a link failure is indicated. The timer
terminal count is set to TWTF. When the timer reaches terminal count it will set the
tx_ts_timer
count is set to TSL. When the timer reaches terminal count it will set the tx_ts_timer_done =
TRUE.
tx_tq_timer
count is set to TQL. When the timer reaches terminal count it will set the tx_tq_timer_done =
TRUE.
tx_tw_timer
This timer is started when the PCS transmitter enters the TX_WAKE state. The timer terminal
count is set to TWL. When the timer reaches terminal count it will set the tx_tw_timer_done =
TRUE.
Change the final paragraph of 49.2.13.3 and replace Figure 49-14 and Figure 49-15 with new figures as
follows:
The PCS shall perform the functions of Lock, BER Monitor, Transmit and Receive as specified in these state
diagrams, including the optional EEE capability if implemented.
E
reset
TX_LI
TX_INIT
tx_coded ENCODE(tx_raw)
tx_coded LBLOCK_T
T_TYPE(tx_raw) = LI
T_TYPE(tx_raw) = S T_TYPE(tx_raw) = (E + D + T + LI)
D C
T_TYPE(tx_raw) = C
T_TYPE(tx_raw) = C
TX_C
T_TYPE(tx_raw) =
tx_coded ENCODE(tx_raw) (E + D + S +T)
T_TYPE(tx_raw) = C T_TYPE(tx_raw) = (E + D + T)
T_TYPE(tx_raw) = S E T_TYPE(tx_raw) = LI
TX_D
T_TYPE(tx_raw) = D T_TYPE(tx_raw) = (E + C + S + LI)
TX_E
T_TYPE(tx_raw) = T)
tx_coded EBLOCK_T
T_TYPE(tx_raw) = T T_TYPE(tx_raw) = (E + S)
T_TYPE(tx_raw) = LI
TX_T
T_TYPE(tx_raw) = D T_TYPE(tx_raw) = C
D C E
T_TYPE(tx_raw) = C T_TYPE(tx_raw) = (E + D + T)
T_TYPE(tx_raw) = LI
C
E
T_TYPE(tx_raw) = S
NOTEOptional state (inside the dotted box) and transition E
D are only required to support EEE capability.
Figure 4914Transmit state diagram
reset+ r_test_mode +
hi_ber + !block_lock E
RX_INIT RX_LI
rx_raw LBLOCK_R rx_raw LI
R_TYPE(rx_coded) = S R_TYPE(rx_coded) = (E + D + T + LI)
D C
R_TYPE(rx_coded) = C
!rx_lpi_active *
R_TYPE(rx_coded) = C
C
RX_C !rx_lpi_active *
R_TYPE(rx_coded) =
rx_raw DECODE(rx_coded) (E + D + S +T)
R_TYPE(rx_coded) = C R_TYPE(rx_coded) = (E + D + T)
R_TYPE(rx_coded) = S E R_TYPE(rx_coded) = LI
RX_D
rx_raw DECODE(rx_coded)
R_TYPE(rx_coded) = D (R_TYPE(rx_coded) = T
R_TYPE_NEXT = (E + D + T)) +
R_TYPE(rx_coded) = (E + C + S + LI)
R_TYPE(rx_coded) = T
R_TYPE_NEXT = (S + C + LI) RX_E
rx_raw EBLOCK_R
R_TYPE(rx_coded) = T (R_TYPE(rx_coded) = T
R_TYPE_NEXT = (S + C + LI) R_TYPE_NEXT = (E + D + T))
+ R_TYPE(rx_coded) = (E + S)
RX_T R_TYPE(rx_coded) = LI
E
R_TYPE(rx_coded) = C R_TYPE(rx_coded)= S
R_TYPE(rx_coded) = D R_TYPE(rx_coded) = C
C D
R_TYPE(rx_coded) = LI D C
E
Figure 4915Receive state diagram
Insert a new subclause 49.2.13.3.1 after 49.2.13.3 as follows:
49.2.13.3.1 LPI state diagrams
A PCS that supports the EEE capability shall implement the LPI transmit and receive processes as shown in
Figure 4916 and Figure 4917. The transmit LPI state diagram controls tx_mode, which disables the
transmitter when it is set to QUIET. The receive LPI state diagram controls block_lock during LPI and
signals the end of LPI to the receive state diagram.
reset
TX_ACTIVE
tx_mode DATA
scrambler_bypass FALSE
T_TYPE(tx_raw) = LI
T_TYPE(tx_raw) LI
TX_SLEEP
Start tx_ts_timer
scrambler_bypass FALSE
T_TYPE(tx_raw) = LI *
tx_ts_timer_done
T_TYPE(tx_raw) LI
TX_QUIET
tx_mode QUIET
Start tx_tq_timer
tx_tq_timer_done +
T_TYPE(tx_raw) LI
TX_ALERT
tx_mode ALERT
Start one_us_timer
one_us_timer_done
TX_WAKE
tx_mode DATA
Start tx_tw_timer
T_TYPE(tx_raw) = LI * T_TYPE(tx_raw) LI *
tx_tw_timer_done * tx_tw_timer_done *
!scr_bypass_enable !scr_bypass_enable
tx_tw_timer_done *
scr_bypass_enable
TX_SCR_BYPASS
scrambler_bypass TRUE
Start one_us_timer
T_TYPE(tx_raw) = LI * T_TYPE(tx_raw) LI *
one_us_timer_done one_us_timer_done
Figure 4916LPI Transmit state diagram
A
reset
RX_ACTIVE
rx_lpi_active FALSE
rx_mode DATA
block_lock rx_block_lock
block_lock rx_block_lock
rx_block_lock * block_lock *
R_TYPE(rx_coded) = LI
RX_SLEEP
rx_lpi_active TRUE
Start rx_tq_timer rx_block_lock *
rx_block_lock *
!rx_tq_timer_done *
!rx_tq_timer_done *
R_TYPE(rx_coded) = IDLE
!rx_tq_timer_done
* !rx_block_lock rx_tq_timer_done
RX_QUIET
rx_mode QUIET
!energy_detect *
energy_detect rx_tq_timer_done
RX_WAKE
!rx_tw_timer_done * rx_mode DATA
rx_block_lock * Start rx_tw_timer
rx_tw_timer_done
!rx_tw_timer_done *
A
rx_block_lock *
R_TYPE(rx_coded) = IDLE
RX_WTF
wake_error_counter++
Start rx_wf_timer
!rx_wf_timer_done * rx_wf_timer_done
rx_block_lock *
RX_LINK_FAIL
block_lock FALSE
!rx_wf_timer_done *
rx_block_lock * UCT
R_TYPE(rx_coded) LI A
A
Figure 4917LPI Receive state diagram
Following a period of LPI, the receiver is required to achieve block synchronization within the wake-up time
specified (see Figure 4917). The implementation of the block synchronization state diagram should use
techniques to ensure that block lock is achieved with minimal numbers of slip attempts. When the Clause 74
FEC is enabled, the receiver may use the knowledge that the link partners transmitter will bypass the
scrambler as part of the wake sequence. The idle sequence following this event will form a fixed pattern for
the duration of the wake period.
The LPI functions shall use timer values for these state diagrams as shown in Table 492 for transmit and
Table 493 for receive.
Table 492Transmitter LPI timing parameters
TSL Local Sleep Time from entering the TX_SLEEP state to when tx_mode is 4.9 5.1 s
set to QUIET
TQL Local Quiet Time from when tx_mode is set to QUIET to entry into the 1.7 1.8 ms
TX_ALERT state
TWL Time spent in the TX_WAKE state 10.9 11.1 s
T1U Time spent in the TX_ALERT and TX_SCR_BYPASS states 1.1 1.3 s
Table 493Receiver LPI timing parameters
TQR The time the receiver waits for energy_detect to be set to TRUE while in the 2 3 ms
RX_SLEEP and RX_QUIET states before asserting receive fault
TWR Time the receiver waits in the RX_WAKE state before indicating a wake 11.5 s
time fault (when scr_bypass_enable = FALSE)
TWR Time the receiver waits in the RX_WAKE state before indicating a wake 13.7 s
time fault (when scr_bypass_enable = TRUE)
49.2.14.1 Status
Rx LPI indication:
For EEE capability, this variable indicates the current state of the receive LPI function. This flag is
set to TRUE (register bit set to one) when the LPI receive state diagram is in any state other than
RX_ACTIVE. This status is reflected in MDIO register 3.1.8. A latch high view of this status is
reflected in MDIO register 3.1.10 (Rx LPI received).
Tx LPI indication:
For EEE capability, this variable indicates the current state of the transmit LPI function. This flag
is set to TRUE (register bit set to one) when the LPI transmit state diagram is in any state other
than TX_ACTIVE. This status is reflected in MDIO register 3.1.9. A latch high view of this status
is reflected in MDIO register 3.1.11 (Tx LPI received).
Physical Coding Sublayer (PCS) type 10GBASE-R15
49.3.3 Major Capabilities/Options
Yes [ ]
LPI Implementation of LPI 49.2.4.4 O
No [ ]
49.3.6 Management
49.3.6.5 Auto-Negotiation for Backplane Ethernet functions
15
LP-01 Insertion and deletion of LPIs 49.2.4.7 LPI:M Yes [ ]

in groups of four No [ ]
LP-02 Unscrambled data transmitted 49.2.6 LPI:M Yes [ ]

when scrambler_bypass = No [ ]
TRUE
LP-03 Scrambler continues to operate 49.2.6 LPI:M Yes [ ]

as normal when No [ ]
scrambler_bypass = TRUE
LP-04 scr_bypass_enable = TRUE 49.2.13.2.2 LPI:M Yes [ ]
when FEC is in use No [ ]
LP-05 Transmit state diagrams 49.2.13.3 Support additions to LPI:M Yes [ ]

Figure 4914 for LPI operation No [ ]
LP-06 Receive state diagrams 49.2.13.3 Support additions to LPI:M Yes [ ]

for LPI operation No [ ]
LP-07 LPI transmit state diagrams 49.2.13.3.1 Meets the requirements of LPI:M Yes [ ]
Figure 4916 No [ ]
LP-08 LPI receive state diagrams 49.2.13.3.1 Meets the requirements of LPI:M Yes [ ]
Figure 4917 No [ ]
LP-09 LPI transmit timing 49.2.13.3.1 Meets the requirements of LPI:M Yes [ ]
Table 492 No [ ]
LP-10 LPI receive timing 49.2.13.3.1 Meets the requirements of LPI:M Yes [ ]
Table 493 No [ ]
51. Physical Medium Attachment (PMA) sublayer, type Serial
51.2 PMA Service Interface
Insert primitives into 51.2 as follows:
PMA_RXMODE.request(rx_mode)
PMA_TXMODE.request(tx_mode)
PMA_ENERGY.indication(energy_detect)
51.2.3 PMA_SIGNAL.indication
Add new subclauses 51.2.4 through 51.2.6 after 51.2.3 as follows:
51.2.4 PMA_RXMODE.request
This primitive is generated by the PCS Receive Process for EEE capability (see 78.3) to indicate when the
PMA and PMD receive functions may go into a low power mode, see 49.3.6.6. Without EEE capability, the
primitive is never invoked and the PMA behaves as if rx_mode = DATA.
51.2.4.1 Semantics of the service primitive
PMA_RXMODE.request(rx_mode)
The rx_mode parameter takes on one of two values: QUIET or DATA.
The PCS generates this primitive to indicate the low power mode of the receive path.
When received the PMA receive is configured appropriately for the indicated state and the value is
propagated to PMD_RX_MODE.request(rx_mode). When rx_mode is DATA, the PMA operates normally.
When rx_mode is QUIET, the PMA may go into a low power mode.
51.2.5 PMA_TXMODE.request
This primitive is generated by the PCS Transmit Process for EEE capability to invoke the appropriate PMA
and PMD transmit EEE states, see 49.2.13.3.1. Without EEE capability, the primitive is never invoked and
the PMA behaves as if tx_mode = DATA.
PMA_TXMODE.request(tx_mode)
The tx_mode parameter takes on one of three values: QUIET, ALERT, or DATA.
The PCS generates this primitive to indicate the low power mode of the transmit path.
When received the PMA transmit is configured appropriately for the indicated state and the value is
propagated to PMD_TX_MODE.request(tx_mode). When tx_mode is DATA, the PMA operates normally.
When tx_mode is QUIET, the PMA may go into a low power mode. When tx_mode is ALERT, the PMA
operation is not defined.
51.2.6 PMA_ENERGY.indication
This primitive is sent by the PMA to its client to indicate the status of the receive process for EEE capability.
PMA_ENERGY.indication is generated by the PMA receive process to propagate the energy detection
indication from the PMD to the PMA client.
PMA_ENERGY.indication(energy_detect)
The energy_detect parameter is Boolean and reflects the state of the PMD_SIGNAL.-
indication(SIGNAL_OK) received from the PMD.
The PMA generates this primitive whenever there is a change in the value of the SIGNAL_OK parameter.
The effect of receipt of this primitive by the client is unspecified by the PMA sublayer.
51.4 Sixteen-Bit Interface (XSBI)
Change Figure 513 for EEE signals across XSBI as follows:
PMA Service Interface PMD Service Interface

REFCLK
(XSBI when implemented)
PMA_TXCLK_SRC<P,N>
TXCGU
PMA_TX_CLK<P,N>
xsbi_tx<15:0> PISO
xsbi_rx<15:0>
SIPO
PMA_UNITDATA.indication PMD_UNITDATA.indication
PMA_RX_CLK<P,N>
RXCRU
Sync_Err<P> (Ooptional)
PMA_SI<P>
SIL
PMA_SIGNAL.indication PMD_SIGNAL.indication
PMA_ENERGY.indication EEE only

see 51.8a
PMA_RXMODE.request PMD_RX_MODE.request
PMA_TXMODE.request PMD_TX_MODE.request
TXCGU = Transmit Clock Generation Unit

PISO = Parallel In Serial Out
SIPO = Serial In Parallel Out
RXCRU = Receiver Clock Recovery Unit
SIL = Signal Indicate Logic
Figure 513XSBI reference diagram
51.4.2 Optional Signals
Insert new optional signals into 51.4.2 as follows:
energy_detect
If the optional Energy-Efficient Ethernet (EEE) function is supported (see Clause 78) then the
XSBI interface includes energy_detect as described in 51.2.
rx_quiet
If the optional EEE function is supported (see Clause 78) then the XSBI interface includes rx_quiet
as described in 51.2.
tx_quiet
If the optional EEE function is supported (see Clause 78) then the XSBI interface includes tx_quiet
as described in 51.2.
Physical Medium Attachment (PMA) sublayer, type Serial16
Insert the following row at the end of the table in 51.10.3:
Yes [ ]
LPI Implementation of LPI 51.2 O
No [ ]
16
55. Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA)

sublayer and baseband medium, type 10GBASE-T
55.1 Overview
Insert the following text after the last paragraph of 55.1:
This clause also specifies 10GBASE-T Low Power Idle (LPI) as part of Energy-Efficient Ethernet (EEE).
This allows the PHY to enter a low power mode of operation during periods of low link utilization as
described in Clause 78. 10GBASE-T PHYs may optionally support a fast retrain mechanism.
55.1.1 Objectives
Insert the following objective l) at the end of the lettered list in 55.1.1:
l) Support a EEE capability as part of Energy-Efficient Ethernet (Clause 78)
55.1.3 Operation of 10GBASE-T
Insert the following text before the last paragraph of 55.1.3 as follows:
10GBASE-T PHYs optionally provide support for LPI as part of EEE (see Clause 78). This extension allows
PHYs to enter an LPI mode when either the local or link partner system requests low power operation. The
transmit and receive functions may enter and leave the LPI mode independently so that both symmetric and
asymmetric operation is supported. While the PHY is in the LPI mode, the PHY periodically transmits a
refresh signal to allow the remote PHY to refresh its receiver state (e.g., timing recovery, adaptive filter
coefficients) and thereby track long-term variation in the timing of the link or the underlying channel
characteristics. An easily detectable alert signal is transmitted to signal an end to the LPI mode. The alert
signal is followed by a wake signal to enable a rapid transition back to the normal operational mode.
10GBASE-T PHYs may optionally support a fast retrain mechanism. This function allows PHYs to quickly
recover from link degradation without a normal two second retrain.
Change the last paragraph of 55.1.3 by inserting a sentence as follows:
The PCS and PMA subclauses of this document are summarized in 55.1.3.1 and 55.1.3.2. The EEE
capability is summarized in 55.1.3.3. Figure 553 shows the functional block diagram.
Replace Figure 55-3 with the following new figure:
TXD<31:0>
TX_CLK
TEN GIGABIT MEDIA
RXD<31:0>
TXC<3:0>
RXC<3:0>
INDEPENDENT
RX_CLK
INTERFACE
(XGMII)
PCS
PCS
PCS TRANSMIT &
RECEIVE
TRANSMIT CONTROL
PMA_UNITDATA.indication (rx_symb_vector)
pcs_data_mode
link_status
tx_mode
PMA_UNITDATA.request (tx_symb_vector)

PMA SERVICE config
INTERFACE
fr_active
rx_lpi_active
alert_detect
PMA
rem_rcvr_status
loc_rcvr_status
scr_status / pcs_status
recovered_
clock
PMA
CLOCK PMA LINK PHY
RECOVERY RECEIVE TRANSMIT MONITOR CONTROL
received_
clock
PMA_LINK.request
(link_control)
PMA_LINK.indication
MEDIUM (link_status)
DEPENDENT
BI_DD -
BI_DD +
BI_DC -
BI_DC +
BI_DB -
BI_DB +
BI_DA -
BI_DA +
INTERFACE
(MDI)
NOTE 1The recovered_clock arc is shown to indicate delivery of the received clock signal back to PMA TRANSMIT for loop timing.
NOTE 2pcs_data_mode is required only for the EEE or fast retrain capabilities; alert_detect and rx_lpi_active are only required for
the EEE capability; fr_active is only required for the fast retrain capability.
Insert the following sentence at the end of 55.1.3.2:
The PMA sublayer may also support a fast retrain function. The fast retrain function is specified in
55.4.2.5.15.
55.1.3.3 EEE capability
A 10GBASE-T PHY may optionally support the EEE capability, as described in 78.3. The EEE capability is
a mechanism by which 10GBASE-T PHYs are able to reduce power consumption during periods of low link
utilization. PHYs can enter this mode of operation after reaching PCS data mode. Each direction of the full
duplex link is able to enter and exit the LPI mode independently, supporting symmetric and asymmetric LPI
operation. This allows power savings when only one side of the full duplex link is in a period of low
utilization. No data frames are lost or corrupted during the transition to or from the LPI mode.
In the transmit direction the transition to the LPI transmit mode begins when the PCS transmit function
detects an LPI control character in all four lanes of two consecutive transfers of TXD[31:0] that will be
mapped into a single 64B/65B block. Following this event a sleep signal is transmitted by the PMA. The
sleep signal is composed of LDPC frames that contain only LP_IDLE 64B/65B blocks. The sleep signal
indicates to the link partner that the transmit function of the PHY is entering the LPI transmit mode.
Immediately after the transmission of the sleep frames, the transmit function of the local PHY enters the LPI
transmit mode. While the transmit function is in the LPI mode the PHY may disable data path and control
logic to save additional power. Periodically the transmit function of the local PHY transmits refresh frames
that are used by the link partner to update adaptive filters and timing circuits in order to maintain link
integrity. The LPI mode begins with quiet signaling or with a full refresh period. Partial refreshes (defined as
a refresh signal shorter than 4 LDPC frames) that immediately follow the transition to the LPI mode are
replaced with quiet signaling. The quiet-refresh cycle continues until the PCS function detects IDLE
characters on the XGMII. These characters signal to the PHY that the LPI transmit mode should end. The
PMA Transmit function in the PHY then sends an alert message to the link partner. The alert signal begins
on a LDPC frame boundary, but has no fixed relationship to the quiet-refresh cycle. The alert signal wakes
the link partner from sleep. The alert signal is followed by a wake signal, composed of LDPC frames
containing only IDLE 64B/65B blocks. After a short recovery time the normal operational mode is resumed.
In the receive direction the transition to the LPI mode is triggered when the PCS Receive function detects
LPI control characters within received LDPC frames. This indicates that the link partner is about to enter the
LPI transmit mode. Following these frames the link partner ceases transmission and begins quiet-refresh
signaling. During the quiet time it is highly recommended that the local receiver power off circuits to reduce
power consumption. Periodically the link partner transmits refresh frames that are used by the receiver to
update adaptive coefficients and timing circuits. This quiet-refresh cycle continues until the link partner
transmits the alert signal, initiating a transition back to the normal operational mode. The alert signal is
detected in the PMA and signals that normal data frames will follow. The alert signal is followed by a wake
signal that allows the local receiver time to prepare for the normal operational mode. The wake signal is
composed of repeated IDLE 64B/65B blocks. After a short recovery time the normal operational mode is
resumed.
Support for the EEE capability is advertised during Auto-Negotiation. Transitions to and from the LPI
transmit mode are controlled via XGMII signaling. Transitions to and from the LPI receive mode are
controlled by the link partner using sleep, alert, and wake signaling.
The PCS 64B/65B Transmit state diagram in Figure 5515 and Figure 5515a includes additional states for
EEE. The PCS 64B/65B Receive state diagram in Figure 5516 and Figure 5516a includes additional states
for EEE. The EEE Transmit state diagram is contained in the PCS Transmit function and is specified in
Figure 5516b.
55.1.4 Signaling
Insert the following objective l) to the end of the lettered list in 55.1.4:
l) Ability to support refresh, quiet and alert signaling during LPI operation
Insert the following text at the end of the last paragraph in 55.1.4:
PHYs may also support the EEE capability as described in 55.1.3.3. Transitions to the LPI mode are
supported after reaching normal mode.
55.2 10GBASE-T service primitives and interfaces
55.2.2 PMA service interface
Insert the following text at the end of the last paragraph in 55.2.2:
EEE-capable PHYs additionally support the following service primitives:
PMA_ALERTDETECT.indication (alert_detect)
PCS_RX_LPI_STATUS.request (rx_lpi_active)
PMA_PCSDATAMODE.indication (pcs_data_mode)
Fast retrain capable PHYs additionally support the following service primitive:
PMA_FR_ACTIVE.indication (fr_active)
10 GIGABIT MEDIA
RXC<3:0>
RXD<31:0>
RX_CLK
TXC<3:0>
TXD<31:0>
TX_CLK
INDEPENDENT
INTERFACE
(XGMII)
PCS
PMA_PCSDATAMODE.indication
PMA_ALERTDETECT.indication
PCS_RX_LPI_STATUS.request
PMA_REMRXSTATUS.request
PMA_FR_ACTIVE.indication
PMA_RXSTATUS.indication
PMA_SCRSTATUS.request
PMA_PCSSTATUS.request
PMA_TXMODE.indication
PMA_CONFIG.indication
PHY
PMA SERVICE
INTERFACE

PMA
PMA_LINK.request
PMA_LINK.indication
MEDIUM
DEPENDENT
INTERFACE
(MDI)
BI_DD -
BI_DD +
BI_DC -
BI_DC +
BI_DB -
BI_DB +
BI_DA -
BI_DA +
NOTE
PMA_PCSDATAMODE.indication is required only for the EEE or fast retrain capabilities.
PMA_ALERTDETECT.indication and PCS_RX_LPI_STATUS.request are only required for the EEE capability.
PMA_FR_ACTIVE.indication is only required for the fast retrain capability.
Figure 55410GBASE-T service interfaces
55.2.2.3 PMA_UNITDATA.request
55.2.2.3.1 Semantics of the primitive
Change the tx_sym_vector parameter options in 55.2.2.3.1 as follows:
During transmission, the PMA_UNITDATA.request simultaneously conveys to the PMA via the parameter
tx_symb_vector the value of the symbols to be sent over each of the four transmit pairs BI_DA, BI_DB,
BI_DC, and BI_DD. For EEE-capable PHYs, the vector also requests the PMA to send the ALERT signal
during LPI. The tx_symb_vector parameter takes on the form:
SYMB_4D A vector of four multi-level symbols, one for each of the four transmit pairs
BI_DA, BI_DB, BI_DC, and BI_DD. In normal operation Eeach symbol
may take on one of the values in the set {15, 13, 11, 9, 7, 5, 3, 1, 1, 3, 5, 7,
9, 11, 13, 15}. The symbols may additionally take the value 0 when zeros are to be
transmitted in the following two cases: 1) when PMA_TXMODE.indication is
SEND_Z during PMA training, and 2) after data mode is reached, the transmit
function is in the LPI transmit mode and lpi_tx_mode is QUIET
ALERT A vector used to indicate that the PMA should transmit the alert sequence.
ALERT will be asserted for a time equal to 4 LDPC frames.
55.2.2.8 PMA REMRX_STATUS.request
Insert new subclauses 55.2.2.9 through 55.2.2.12 after 55.2.2.8 as follows:
55.2.2.9 PMA_ALERTDETECT.indication
This primitive is generated by PMA Receive to indicate the status of the receive link at the local PHY when
rx_lpi_active is TRUE. The parameter alert_detect conveys to the PCS receive function information
regarding the detection of the LPI alert signal by the PMA receive function. The criterion for setting the
parameter alert_detect is left to the implementor.
PMA_ALERTDETECT.indication (alert_detect)
The alert_detect parameter can take on one of two values of the form:
TRUE The alert signal has been reliably detected at the local receiver.
FALSE The alert signal at the local receiver has not been detected.
The PMA generates PMA_ALERTDETECT.indication messages to indicate a change in the alert_detect

status.
The effect of receipt of this primitive is specified in 55.3.2.3, Figure 5516, and Figure 5516a.
55.2.2.10 PCS_RX_LPI_STATUS.request
When the PHY supports the EEE capability this primitive is generated by the PCS receive function to
indicate the status of the receive link at the local PHY. The parameter PCS_RX_LPI_STATUS.request
conveys to the PCS transmit and PMA receive functions information regarding whether the receive function
is in the LPI receive mode. The parameter is generated by the Receive 64B/65B state diagram in
Figure 55-16.
PCS_RX_LPI_STATUS.request (rx_lpi_active)
The rx_lpi_active parameter can take on one of two values of the form:
TRUE The receive function is in the LPI receive mode.

FALSE The receive function is not in the LPI receive mode.
The PCS generates PCS_RX_LPI_STATUS.request messages to indicate a change in the rx_lpi_active

variable as determined by the receive state diagram in Figure 55-16.
The effect of receipt of this primitive is specified in 55.3.2.3 and Figure 5527a.
55.2.2.11 PMA_PCSDATAMODE.indication
This primitive indicates whether or not the PCS state diagrams are able to transition from their initialization
states. The pcs_data_mode variable is generated by the PMA PHY Control function. It is passed to the PCS
Control function via the PMA_PCSDATAMODE.indication primitive.
PMA_PCSDATAMODE.indication (pcs_data_mode)
The PMA PHY Control function generates PMA_PCSDATAMODE.indication messages continuously.
Upon receipt of this primitive, the PCS performs its transmit function as described in 55.3.2.2.
55.2.2.12 PMA_FR_ACTIVE.indication
This primitive indicates whether or not the PMA is currently performing a fast retrain. The fr_active variable
is generated by the PMA PHY Control function. It is passed to the PCS Receive Control function via the
PMA_FR_ACTIVE.indication primitive. This primitive is only supported by PHYs with the fast retrain
capability.
PMA_FR_ACTIVE.indication (fr_active)
The PMA PHY Control function generates PMA_FR_ACTIVE.indication messages continuously.
The effect of receipt of this primitive is specified in Figure 5516.
55.3.2 PCS Functions
10 GIGABIT MEDIA
RX_CLK
RXC<3:0>
RXD<31:0>
TXD<31:0>
TXC<3:0>
MEDIA INDEPENDENT
TX_CLK
INTERFACE (XGMII)
PCS
PCS PCS
RECEIVE TRANSMIT
PMA_UNITDATA.indication (rx_symb_vector)
tx_mode
PMA SERVICE
rem_rcvr_status
pcs_data_mode
INTERFACE
alert_detect
link_status
loc_rcvr_status
rx_lpi_active
fr_active
config
NOTE
pcs_data_mode is required only for the EEE or fast retrain capabilities.
alert_detect and rx_lpi_active are only required for the EEE capability.
fr_active is only required for the fast retrain capability.
Figure 555PCS reference diagram
55.3.2.2 PCS Transmit function
Insert the following text after the first paragraph in 55.3.2.2:
Dashed rectangles in Figure 5515 and Figure 5515a are used to indicate states and state transitions in the
transmit process state diagram that shall be supported by PHYs with the EEE capability. PHYs without the
EEE capability do not support these transitions.
Insert the following text after the last paragraph in 55.3.2.2:
After reaching the normal mode of operation, EEE-capable PHYs may enter the LPI transmit mode under
the control of the MAC via the XGMII. The EEE Transmit state diagram is contained within the PCS
Transmit function. The EEE capability is described in 55.3.2.2.21.
55.3.2.2.1 Use of blocks
Change 55.3.2.2.1 as follows:
The PCS maps XGMII signals into 65-bit blocks inserted into an LDPC frame, and vice versa, using a 65B-
LDPC coding scheme. The PAM2 PMA training frame synchronization allow establishment of LDPC frame
and 65B boundaries by the PCS Synchronization process. Blocks and frames are unobservable and have no
meaning outside the PCS. During the LPI mode, LDPC frame boundaries delimit sleep, wake, refresh, quiet,
and alert cycles. The PCS functions ENCODE and DECODE generate, manipulate, and interpret blocks and
frames as provided by the rules in 55.3.2.2.2.
55.3.2.2.9 Idle (/I/)
Replace Table 55-1 and footnotes with the following new table and footnotes:.
Table 551Control Codes
XGMII 10GBASE-T 10GBASE-T

Control character Notation 8B/10B codea
control codes control codes O code
idle /I/ 0x07 0x00 K28.0 or

K28.3 or
K28.5
without
D20.5b
LPI /LI/ 0x06 0x06 K28.0 or

K28.3 or
K28.5
with D20.5b
start /S/ 0xFB Encoded by block type K27.7

field
terminate /T/ 0xFD Encoded by block type K29.7

field
error /E/ 0xFE 0x1E K30.7
Sequence ordered_set /Q/ 0x9C Encoded by block type 0x0 K28.4

field plus O code
reserved0 /R/c 0x1C 0x2D K28.0
reserved1 0x3C 0x33 K28.1
reserved2 /A/ 0x7C 0x4B K28.3
reserved3 /K/ 0xBC 0x55 K28.5
reserved4 0xDC 0x66 K28.6
reserved5 0xF7 0x78 K23.7
Signal ordered_setd /Fsig/ 0x5C Encoded by block type 0xF K28.2

field plus O code
aFor information only. The 8B/10B code is specified in Clause 36. Usage of the 8B/10B code for 10 Gb/s operation is
specified in Clause 48.
bUse of idle and LPI ordered sets per 48.2.4.2.
cThe codes for /A/, /K/, and /R/ are used on the XAUI interface to signal idle. They are not present on the XGMII when
no errors have occurred, but certain bit errors cause the XGXS to send them on the XGMII.
d
Reserved for INCITS T11 Fibre Channel use.
55.3.2.2.9a LPI (/LI/)
Low power idle (LPI) control characters (/LI/) on the XGMII indicate that the LPI client is requesting
operation in the LPI transmit mode. A continuous stream of LPI control characters (/LI/) is used to maintain
a link in the LPI transmit mode. Idle control characters (/I/) are used to transition from the LPI transmit
mode to the normal mode. EEE compliant PHYs respond to the LPI XGMII control characters using the
procedure outlined in 55.1.3.3. LPI characters may be added or deleted by the PCS to adapt between clock
rates. /LI/ insertion and deletion shall occur in groups of four. /LI/s may be added following low power idle
characters. They shall not be added while data is being received.
If EEE is not supported, then /LI/ is not a valid control character.
55.3.2.2.20 65B-LDPC framer
55.3.2.2.21 EEE capability
The optional 10GBASE-T EEE capability allows compliant PHYs to transition to an LPI mode of operation
when link utilization is low.
EEE compliant PHYs shall implement the EEE transmit state diagram, shown in Figure 5516b, within the
PCS.
When PCS_Reset is asserted or pcs_data_mode is not asserted, the state diagram enters the TX_NORMAL
state.
When a complete 64B/65B block of LPI characters is generated by the PCS transmit function, the PHY
transmits the sleep signal to indicate to the link partner that it is transitioning to the LPI transmit mode. If the
sleep signal begins on an LDPC frame boundary, then it contains 9 full LDPC frames each composed
entirely of 64B/65B LDPC-encoded LP_IDLE blocks. If the sleep signal does not begin on an LDPC frame
boundary, then it contains one LDPC frame partially composed of LP_IDLE blocks followed by 9 LDPC
frames fully composed of LP_IDLE blocks.
Following the transmission of the sleep signal, quiet-refresh signaling begins, as described in 55.3.4a.
After the sleep signal is transmitted LPI control characters shall be input to the PCS scrambler continuously
until the PCS Transmit Function exits the LPI transmit mode.
While the PMA asserts SEND_N, the lpi_tx_mode variable shall control the transmit signal through the
PMA_UNITDATA.request primitive described as follows:
When the PHY is not in the PCS_Data state, the lpi_tx_mode variable is ignored.
When the lpi_tx_mode variable takes the value NORMAL and the PMA asserts SEND_N, the PCS
passes coded data to the PMA via the PMA_UNITDATA.request primitive as described in 55.3.2.2.
When the lpi_tx_mode variable takes the value QUIET and the PMA asserts SEND_N, the PCS
passes zeros to the PMA through the PMA_UNITDATA.request primitive.
When the lpi_tx_mode variable takes the value REFRESH_A and the PMA asserts SEND_N, the
PCS passes the PMA training signal to the PMA on pair A, to allow both the local and remote PHY
to refresh adaptive filters and timing loops. The PCS passes zeros to all other pairs in this condition.
REFRESH_B, REFRESH_C and REFRESH_D operate in a analogous manner for the other pairs.
When the lpi_tx_mode variable takes the value ALERT and the PMA asserts SEND_N, the PCS
passes the ALERT vector to the PMA.
The quiet-refresh cycle is repeated until codewords other than LP_IDLE are detected at the XGMII. These
codewords indicate that the local system is requesting a transition back to the normal operational mode.
Following this event, the PMA_UNITDATA.request message is set to the value ALERT. The alert signal is
not synchronized with respect to the quiet-refresh cycle but shall be synchronized so that the alert signal
from the PMA begins on a LDPC frame boundary.
The PHY will also transition back to the normal operation mode if an error condition occurs. This error
condition is defined as the detection of any characters other than LPI or IDLE at the XGMII.
After the alert signal the PCS completes the transition from LPI mode to normal mode by sending a wake
signal containing lpi_wake_time LDPC frames composed of IDLE 64B/65B blocks.
lpi_wake_time is a fixed parameter that is defined as 9 LDPC frames as shown in Table 551a. The
maximum PHY wake time when wake is requested before sleep has been completely transmitted is 7.36 s
(lpi_wake_timer=Tw_phy as defined by Clause 78). The maximum PHY wake time when wake is requested
after sleep has been completely transmitted is 4.48 s.
Table 551aLPI wake time
lpi_wake_timer when wake starts lpi_wake_timer when wake starts

lpi_wake_time
before sleep signal is complete after sleep signal is complete
(frames) (frames) (s) (frames) (s)
9 23 7.36 14 4.48
55.3.2.3 PCS Receive function
Insert the following paragraphs after 55.3.2.3 as follows:
PHYs with the EEE capability support transition to the LPI mode when the PHY has successfully completed
training and pcs_data_mode is TRUE. Transitions to and from the LPI mode are allowed to occur
independently in the transmit and receive functions. The PCS receive function is responsible for detecting
transitions to and from the LPI receive mode and indicating these transitions using signals defined in 55.2.2.
The link partner signals a transition to the LPI mode of operation by transmitting 9 LDPC frames composed
entirely of 64B/65B blocks of /LI/. When blocks of /LI/ are detected at the output of the 64B/65B decoder,
rx_lpi_active is asserted by the PCS receive function and the /LI/ character is continuously asserted at the
receive XGMII. These frames may be preceded by a frame composed partially of /LI/ characters. After these
frames the link partner begins transmitting zeros, and it is recommended that the receiver power down
receive circuits to reduce power consumption. The receive function uses LDPC frame counters to maintain
synchronization with the remote PHY and receives periodic refresh signals that are used to update
coefficients, so that the integrity of adaptive filters and timing loops in the PMA is maintained. LPI signaling
is defined in 55.3.4a. The quiet-refresh cycle continues until the PMA asserts alert_detect to indicate that the
alert signal has been reliably detected. After the alert signal the link partner transmits repeated /I/ characters,
representing a wake signal. The PHY receive function sends /I/ to the XGMII for 9 LDPC frame periods and
then resumes normal operation.
55.3.4 PMA training side-stream scrambler polynomials
Insert the following new subclause 55.3.4a after 55.3.4.3 as follows:
55.3.4a LPI signaling
PHYs with EEE capability have transmit and receive functions that can enter and leave the LPI mode
independently. The PHY can transition to the LPI mode when the PHY has successfully completed training
and pcs_data_mode is TRUE. The transmit function of the PHY initiates a transition to the LPI transmit
mode when it generates 64B/65B blocks composed entirely of LPI control characters, as described in
55.3.2.2.21. The transmit function of the link partner signals the transition using the sleep signal. When the
transmitter begins to send the sleep signal, it asserts tx_lpi_active and the transmit function enters the LPI
transmit mode.
Within the LPI mode PHYs use a repeating quiet-refresh cycle (see Figure 5513a). The first part of this
cycle is known as the quiet period and lasts for a time lpi_quiet_time equal to 124 LDPC frame periods. The
quiet period is defined in 55.3.4a.2. The second part of this cycle is known as the refresh period and lasts for
a time lpi_refresh_time equal to 4 LDPC frame periods. The refresh period is defined in 55.3.4a.3. A cycle
composed of one quiet period and one refresh period is known as a single pair LPI cycle and lasts for a time
lpi_qr_time equal to 128 LDPC frame periods. The time taken to complete a quiet-refresh cycle for all four
pairs is known as a complete LPI cycle.
lpi_offset, lpi_quiet_time, lpi_refresh_time, lpi_qr_time, and lpi_allpairs_qr_time are timing parameters

that are integer multiples of the LDPC frame period. lpi_offset is a fixed value equal to lpi_qr_time/2 that is
used to ensure refresh signals are appropriately offset by the link partners.
refresh
quiet quiet R
Pair A
lpi_quiet_time
lpi_refresh_time
lpi_qr_time
lpi_allpairs_qr_time
Pair B R
Pair C R
Pair D R
active_pair A B C D A
Figure 5513aTiming periods for LPI signals
PHYs begin the transition from the LPI receive mode when the alert signal is detected by the PMA as
defined in 55.4.2.4.
55.3.4a.1 LPI Synchronization
To maximize power savings, maintain link integrity, and ensure interoperability, EEE-capable PHYs must
synchronize refresh intervals during the LPI mode. The transition to PCS_Test is used as a fixed timing
reference for the link partners. Refresh signaling is derived by counting LDPC frames from the transition to
PCS_Test. An EEE-capable PHY shall support loop timing and loop timing shall be enabled on the slave
PHY.
In initial training, normal retraining, and fast retraining, with or without the EEE capability being supported,
the master and slave signal when they will transition to PCS_Test using the transition counter following the
procedure described in 55.4.2.5.14.
A EEE-capable PHY in slave mode is responsible for synchronizing its PMA training frame to the masters
PMA training frame during the transition to PMA_Training_Init_S. The slave shall ensure that its PMA
training frames are synchronized to the masters PMA training frames within 1 LDPC frame, measured at
the slave MDI on pair A. In addition, the slave shall initialize its transition counter so that it transitions to
PCS_Test within 1 LDPC frame of the master PHY's transition to PCS_Test, measured at the slave PHYs
MDI on pair A. This mechanism ensures that the refresh offset is bounded to a small value at both MDI
interfaces, thus ensuring there is no overlap of master and slave signals when both transmit and receive are
in the LPI mode.
Following the transition to PCS_Test, the PCS counts transmitted and received LDPC frames, and uses these
counters to generate refresh and pair control signals for the transmit and receive functions. The transmitted
LDPC frame count is named tx_ldpc_frame_cnt. The received LDPC frame count is named
rx_ldpc_frame_cnt.
The master and slave shall derive the active pair and refresh_active signals from the LDPC frame counters
as shown in Table 551b and Table 551c.
Table 551bSynchronization logic derived from slave signal LDPC frame count
for master u=rx_ldpc_frame_cnt

Slave-side variable Master-side variable
for slave u=tx_ldpc_frame_cnt
tx_refresh_active=true rx_refresh_active=true lpi_offset lpi_refresh_time

mod(u,lpi_qr_time) < lpi_offset
tx_lpi_full_refresh=true N/A lpi_offset lpi_refresh_time =

mod(u,lpi_qr_time)
tx_active_pair=PAIR_A rx_active_pair=PAIR_A lpi_offset + lpi_qr_time u < lpi_offset

+ 2 x lpi_qr_time
tx_active_pair=PAIR_B rx_active_pair=PAIR_B lpi_offset + 2 x lpi_qr_time u <

lpi_offset + 3 x lpi_qr_time
tx_active_pair=PAIR_C rx_active_pair=PAIR_C lpi_offset + 3 x lpi_qr_time u < 4 x

lpi_qr_time OR
0 u < lpi_offset
tx_active_pair=PAIR_D rx_active_pair=PAIR_D lpi_offset u < lpi_offset + lpi_qr_time
Table 551cSynchronization logic derived from master signal LDPC frame count
for master v=tx_ldpc_frame_cnt

Slave-side variable Master-side variable
for slave v=rx_ldpc_frame_cnt
rx_refresh_active=true tx_refresh_active=true lpi_quiet_time

mod(v,lpi_qr_time)
N/A tx_lpi_full_refresh=true lpi_quiet_time =

mod(v,lpi_qr_time)
rx_active_pair=PAIR_A tx_active_pair=PAIR_A 0 v < lpi_qr_time
rx_active_pair=PAIR_B tx_active_pair=PAIR_B lpi_qr_time v < 2 x lpi_qr_time
rx_active_pair=PAIR_C tx_active_pair=PAIR_C 2 x lpi_qr_time v < 3 x

lpi_qr_time
rx_active_pair=PAIR_D tx_active_pair=PAIR_D 3 x lpi_qr_time v < 4 x

lpi_qr_time
55.3.4a.2 Quiet period signaling
During the quiet period the transmitters on all four pairs should be turned off. Average launch power (as
measured from 28 LDPC frames after a refresh period to 28 LDPC frames before the next refresh period on
the same lane) for each Transmitter shall be less than 41dBm. This requirement does not apply to the
periods when the alert signal is transmitted as defined in 55.4.2.2.1.
55.3.4a.3 Refresh period signaling
During the LPI mode 10GBASE-T PHYs use staggered, out-of-phase refresh signaling to maximize power
savings. Two-level PAM refresh symbols are generated using the PMA side-stream scrambler polynomials
described in 55.3.4 and exactly as is shown in Figure 55-13 with the exception that the InfoField consists of
a sequence of 128 zeros. The training sequence without periodic reinitialization described in 55.3.4 shall be
used during the LPI mode, with the scramblers free-running from PCS Reset. If scrambler reinitialization is
used for normal training, it shall be disabled and the scramblers shall begin free-running when the PHY
Control state diagram enters the PCS_Test state.
Refresh signals shall be sent using the THP filter as described in 55.4.3.1. At the start of each refresh signal
the THP feedback delay line shall be initialized with zeros.
While a transmit function is in the LPI transmit mode only one of the transmit pairs will be active during a
refresh period. tx_symb_vector for all transmit pairs that are not active shall be set to zero.
When tx_symb_vector has the value ALERT and the PHY is master, the transmitter on pair A shall be active
and all other pairs shall be quiet. When tx_symb_vector has the value ALERT and the PHY is slave, the
transmitter on pair C shall be active and all other pairs shall be quiet. If lpi_tx_mode=REFRESH_A on a
MASTER PHY or lpi_tx_mode=REFRESH_C on a SLAVE PHY, and tx_symb_vector has the value
ALERT, then the alert signalling shall be transmitted in place of the refresh signalling where the signals
overlap.
55.3.5.2 State diagram parameters
Insert the following constant definitions after all existing constant definitions in 55.3.5.2.1:
LPBLOCK_R<71:0>
72 bit vector to be sent to the XGMII containing /LI/ in all the eight character locations.
LPBLOCK_T<64:0>
65 bit vector to be sent to the LDPC encoder containing /LI/ in all the eight character locations.
IBLOCK_R<71:0>
72 bit vector to be sent to the XGMII containing /I/ in all the eight character locations.
IBLOCK_T<64:0>
65 bit vector to be sent to the LDPC encoder containing /I/ in all the eight character locations.
UBLOCK_R<71:0>
72 bit vector to be sent to the XGMII containing two Link Interruption ordered_sets. The Link
Interruption ordered_set is defined in 46.3.4.
Insert the following variable definitions after all existing variable definitions in 55.3.5.2.2:
The following variables are required for PHYs that support the EEE capability:
tx_lpi_active
A Boolean variable that is set true when the PHY transmit function is operating in the LPI transmit
mode and during transitions to and from the LPI transmit mode (i.e., at any time when the PHY is
transmitting sleep, alert, wake, or quiet-refresh signaling). It is set false otherwise.
tx_lpi_qr_active
A Boolean variable that is set true during the LPI transmit mode, when the PHY is transmitting
quiet-refresh signaling. Set false otherwise.
rx_lpi_active
A Boolean variable that is set true when the PHY receive function is operating in the LPI receive
mode and set false otherwise. The LPI receive mode begins when the sleep signal is detected and lasts until
the alert signal is detected. When the EEE capability is not supported, rx_lpi_active is set false.
tx_lpi_req
A Boolean variable that is set true when the LPI client indicates that it is requesting operation in the
LPI transmit mode via the XGMII and set false otherwise.
alert_detect
Indicates that an alert signal from the link partner has been received at the MDI as indicated by
PMA_ALERTDETECT.indication(alert_detect).
tx_lpi_alert_active
A Boolean variable that is set true when the PHY is transmitting ALERT signaling. Set false
otherwise.
rx_lpi_wake
A Boolean variable that is set true when the PHY receiver is in the WAKE state and sending IDLE
to the XGMII. Set false otherwise. When the EEE capability is not supported, rx_lpi_wake is set false.
tx_active_pair
A variable indicating the transmit active pair during the LPI transmit mode. The variable may take
the values PAIR_A, PAIR_B, PAIR_C, PAIR_D. This variable is defined in 55.3.4a.1.
lpi_tx_mode
A variable indicating the signaling to be used from the PCS to the PMA across the
PMA_UNITDATA.request (tx_symb_vector) interface.
lpi_tx_mode controls tx_symb_vector only when tx_mode is set to SEND_N.
The variable is set to NORMAL when (!tx_lpi_qr_active * !tx_lpi_alert_active), indicating that the
PCS is in the normal mode of operation and will encode code-groups as described in Figures 55-15 and
Figure 55-15a.
The variable is set to REFRESH_A when (tx_lpi_qr_active * (tx_active_pair==PAIR_A) *
tx_refresh active).
The variable is set to REFRESH_B when (tx_lpi_qr_active * (tx_active_pair==PAIR_B) *
tx_refresh active).
The variable is set to REFRESH_C when (tx_lpi_qr_active * (tx_active_pair==PAIR_C) *
tx_refresh active).
The variable is set to REFRESH_D when (tx_lpi_qr_active * (tx_active_pair==PAIR_D) *
tx_refresh active).
The variable is set to QUIET when (tx_lpi_qr_active * (!tx _refresh_active + tx_lpi_initial_quiet))
The variable is set to ALERT when (tx_lpi_alert_active)
tx_refresh_active
A Boolean value. This variable is set true following the logic described in 55.3.4a.1.
tx_lpi_full_refresh
A Boolean value. This variable is set true following the logic described in 55.3.4a.1.
tx_lpi_initial_quiet
A Boolean value. This variable is set true when the transmit function enters the LPI transmit mode and a
partial refresh will be replaced by quiet signaling.
ldpc_frame_done
A Boolean value. This variable is set true when the final symbol of each LDPC frame is transmitted and is
set false otherwise.
The following variable is only required for PHYs that support the fast retrain capability:
fr_sigtype
If fast retrain is supported, this variable is set based on the value in 1.147.2:1 as follows:
00 IBLOCK_R
01 LBLOCK_R
10 UBLOCK_R
11 Reserved
55.3.5.2.3 Timers
Insert four additional timers after the existing timer definitions in 55.3.5.2.3 as follows:
The following timers are required for PHYs that support the EEE capability:
lpi_tx_sleep_timer
This timer defines the time the local transmitter sends the sleep signal to the link partner.
Values: The condition lpi_tx_sleep_timer_done becomes true upon timer expiration.
Duration: This timer shall have a period equal to 9 LDPC frame periods.
lpi_tx_alert_timer
This timer defines the time the local transmitter transmits the alert signal.
Values: The condition lpi_tx_alert_timer_done becomes true upon timer expiration.
lpi_tx_wake_timer:
This timer defines the time the local transmitter transmits the wake signal.
Values: The condition lpi_tx_wake_timer_done becomes true upon timer expiration.
Duration: This timer shall have a period equal to lpi_wake_time LDPC frame periods.
lpi_rx_wake_timer:
This timer defines the time the receiver sends IDLE blocks to the XGMII after the alert signal is
detected.
Values: The condition lpi_rx_wake_timer_done becomes true upon timer expiration.
Duration: This timer shall have a period equal to lpi_wake_time LDPC frame periods.
55.3.5.2.4 Functions
Change the text in 55.3.5.2.4 as follows:
R_BLOCK_TYPE = {C, S, T, D, E, I, LI, LII}

When the EEE capability is not supported, thisThis function classifies each 65 bit rx_coded vector
as belonging to one of the five types {C, S, T, D, E} depending on its contents.
When the EEE capability is supported, this function classifies each 65 bit rx_coded vector as
belonging to the eight types depending on its contents. A vector may simultaneously belong to the
C and I types when it contains eight valid control characters that are all /I/, but in every other case
the vector belongs to only one type.
Values: C; The vector contains a data/ctrl header of 1 and one of the following:
a) A block type field of 0x1E and eight valid control characters other than /E/ and /
LI/;
b) A block type field of 0x2D or 0x4B, a valid O code, and four valid control
characters;
c) A block type field of 0x55 and two valid O codes.
S; The vector contains a data/ctrl header of 1 and one of the following:
a) A block type field of 0x33 and four valid control characters;
b) A block type field of 0x66 and a valid O code;
c) A block type field of 0x78.
T; The vector contains a data/ctrl header of 1, a block type field of 0x87, 0x99, 0xAA,
0xB4, 0xCC, 0xD2, 0xE1 or 0xFF and all control characters are valid.
D; The vector contains a data/ctrl header of 0.
I; If the optional EEE capability is supported, then the I type is a special case of the C
type where the vector contains a data/ctrl header of 1, a block type field of 0x1e, and
eight control characters of /I/.
LI: If the optional EEE capability is supported, then the LI type occurs when the vector
contains a data/ctrl header of 1, a block type field of 0x1e, and eight control
characters of /LI/.
LII: If the optional EEE capability is supported, then the LII type occurs when the vector
contains a data/ctrl header of 1, a block type field of 0x1E, and one of the following:
a) four control characters of /LI/ followed by four control characters of /I/;
b) four control characters of /I/ followed by four control characters of /LI/
A valid control character is one containing a 10GBASE-T control code specified in Table 551. A
valid O code is one containing an O code specified in Table 551.
R_TYPE(rx_coded<64:0>)
Returns the R_BLOCK_TYPE of the rx_coded<64:0> bit vector.
R_TYPE_NEXT
Prescient end of packet check function. It returns the R_BLOCK_TYPE of the rx_coded vector
immediately following the current rx_coded vector.
T_BLOCK_TYPE = {C, S, T, D, E, I, LI, LII}
When the EEE capability is not supported, thisThis function classifies each 72-bit tx_raw vector as
belonging to one of the five types {C, S, T, D, E} depending on its contents.
When the EEE capability is supported, this function classifies each 72-bit tx_raw vector as
belonging to the eight types depending on its contents. A vector may simultaneously belong to the
C and I types when it contains eight valid control characters that are all /I/, but in every other case
the vector belongs to only one type.
Values: C; The vector contains one of the following:
a) eight valid control characters other than /O/, /S/, /T/, and/E/ and /LI/;
b) one valid ordered_set and four valid control characters other than /O/, /S/ and /T/;
c) two valid ordered sets.
S; The vector contains an /S/ in its first or fifth character, any characters before the S
character are valid control characters other than /O/, /S/ and /T/ or form a valid
ordered_set, and all characters following the /S/ are data characters.
T; The vector contains a /T/ in one of its characters, all characters before the /T/ are data
characters, and all characters following the /T/ are valid control characters other
than /O/, /S/ and /T/.
D; The vector contains eight data characters.
I; If the optional EEE capability is supported, then the I type is a special case of the C
type where the vector contains eight control characters of /I/.
LI: If the optional EEE capability is supported, then the LI type occurs when the vector
contains eight control characters of /LI/.
LII: If the optional EEE capability is supported, then the LII type occurs when the vector
contains one of the following:
a) four control characters of /LI/ followed by four control characters of /I/;
b) four control characters of /I/ followed by four control characters of /LI/.
A tx_raw character is a control character if its associated TXC bit is asserted. A valid control
character is one containing an XGMII control code specified in Table 551. A valid ordered_set
consists of a valid /O/ character in the first or fifth characters and data characters in the three
characters following the /O/. A valid /O/ is any character with a value for O code in Table 551.
55.3.5.2.5 Counters
Insert the following text after the existing text in 55.3.5.2.5:
The following counters are required for PHYs that support the EEE capability:
tx_ldpc_frame_cnt
An integer value that counts transmit LDPC frame periods. The counter is reset when the first
symbol of the first LDPC frame crosses the MDI on pair A in the transmit direction after normal
training or fast retraining. It is incremented after the last symbol of each transmitted LDPC frame.
tx_ldpc_frame_cnt is reset to 0 when tx_ldpc_frame_cnt = lpi_qr_time x 4.
rx_ldpc_frame_cnt
An integer value that counts receive LDPC frame periods. The counter is reset when the first
symbol of the first LDPC frame crosses the MDI on pair A in the receive direction after normal
training or fast retraining. It is incremented after the last symbol of each received LDPC frame.
rx_ldpc_frame_cnt is reset to 0 when rx_ldpc_frame_cnt = lpi_qr_time x 4.
lpi_rxw_err_cnt
An integer value that counts the number of receive wake on error conditions. lpi_rxw_err_cnt is
reset to zero during PCS_Test. The counter is reflected in register 3.22 (see 45.2.3.8b).
Change the third paragraph in 55.3.5.4 as follows:
The 64B/65B Receive state diagram shown in Figure 55-16 controls the encoding of 65B transmitted blocks.
It makes exactly one transition for each 65B receive block processed except for the transition from RX_WE
to RX_E, which occurs immediately after the RX_WE processes are complete.
Change the last paragraph of 55.3.5.4 as follows:
The PCS shall perform the functions of LFER Monitor, Transmit, and Receive as specified in these state
diagrams. The PCS shall not perform the LFER Monitor function during LPI receive operation from the
time that the PCS 64B/65B Receiver enters the state RX_L, until the state RX_W is exited.
Insert the following text at the end of 55.3.5.4 as follows:
Transitions surrounded by dashed rectangles indicate requirements for 10GBASE-T EEE-capable

implementations.
Replace Figure 55-14, Figure 55-15, and Figure 55-16 with new figures, and insert new Figure 55-15a,
Figure 55-16a, Figure 55-16b as follows:
pcs_reset + !block_lock + rx_lpi_active

+ rx_lpi_wake
LFER_MT_INIT
hi_lfer false
lfer_test_lf false
UCT
START_TIMER
lfer_cnt 0
start 125s_timer
lfer_test_lf
LFER_TEST_LF
lfer_test_lf false
!lf_valid lf_valid
125s_timer_done
LFER_BAD_LF
lfer_cnt ++
lfer_test_lf lfer_cnt < 16

lfer_cnt < 16 125s_timer_done
125s_timer_not_done
lfer_cnt =16
HI_LFER GOOD_LFER
hi_lfer true hi_lfer false
125s_timer_done UCT
Figure 5514LFER monitor state diagram
pcs_reset+!pcs_data_mode
TX_INIT
tx_coded LBLOCK_T
T_TYPE(tx_raw) = S T_TYPE(tx_raw) = (E + D + LI +T)
D
T_TYPE(tx_raw) = C + LII
TX_C
(T_TYPE(tx_raw) = C+LII) T_TYPE(tx_raw) = (E + D +T)
T_TYPE(tx_raw) = LI
T_TYPE(tx_raw) = S
L
D
TX_D
T_TYPE(tx_raw) = D T_TYPE(tx_raw) = (E + C + LI + LII + S) E
TX_E
T_TYPE(tx_raw) = T)
tx_coded EBLOCK_T
T_TYPE(tx_raw) = T T_TYPE(tx_raw) = (E + S)
T_TYPE(tx_raw) = LI
L
TX_T (T_TYPE(tx_raw) = C+LII) +
C
T_TYPE(tx_raw) = D
(T_TYPE(tx_raw) = C + LII) D
C T_TYPE(tx_raw) = (E + D + T)
T_TYPE(tx_raw) = S
(T_TYPE(tx_raw) = LI)
L
D
NOTETransitions inside dashed boxes are only required for the EEE capability.
Figure 5515PCS 64B/65B Transmit state diagram, part a
TX_L
tx_lpi_req true
tx_coded LPBLOCK_T
T_TYPE(tx_raw) = LI+LII
T_TYPE(tx_raw) = (C + D + E + S + T )
TX_WN
tx_lpi_req false
tx_coded IBLOCK_T
tx_lpi_active
!tx_lpi_active
NOTEThis figure is mandatory for PHYs with the EEE capability.
Figure 5515aPCS 64B/65B Transmit state diagram, part b
pcs_reset+ hi_lfer + !block_lock +

!pcs_data_mode
RX_INIT
if !fr_active
rx_raw LBLOCK_R
else
rx_raw fr_sigtype
end
rx_lpi_wake false
rx_lpi_active false
R_TYPE(rx_coded) = S R_TYPE(rx_coded) = (E + D + LI + T)
D R_TYPE(rx_coded) = C+LII
C
RX_C
rx_lpi_wake false
R_TYPE(rx_coded) = C + LII R_TYPE(rx_coded) = (E + D + T)
L R_TYPE(rx_coded) = S
RX_D
R_TYPE(rx_coded) = D (R_TYPE(rx_coded) = T
R_TYPE_NEXT = (E + D + T)) +
R_TYPE(rx_coded) = (E + C + LI + LII + S) E
R_TYPE(rx_coded) = T
R_TYPE_NEXT = (S + C + LI RX_E
+ LII)
rx_raw EBLOCK_R
R_TYPE(rx_coded) = T (R_TYPE(rx_coded) = T
R_TYPE_NEXT = (S + C+ LI + LII ) R_TYPE_NEXT = (E + D + T)) +
R_TYPE(rx_coded) = (E + S)
RX_T
L
rx_raw DECODE(rx_coded) R_TYPE(rx_coded) = C+ LII
R_TYPE(rx_coded) = C + LII R_TYPE(rx_coded)= S C
R_TYPE(rx_coded) = D
C D
L R_TYPE(rx_coded) = LI D
Figure 5516PCS 64B/65B Receive state diagram, part a
RX_L
rx_raw LP_BLOCK_R
rx_lpi_active true
!alert_detect
alert_detect
RX_W
rx_raw I_BLOCK_R
start lpi_rx_wake_timer
rx_lpi_active false
rx_lpi_wake true
lpi_rx_wake_timer_done*
!(R_TYPE(rx_coded)=I)
lpi_rx_wake_timer_done*
R_TYPE(rx_coded)=I RX_WE
lpi_rxw_err_cnt++
rx_lpi_wake false
UCT
C E
Figure 5516aPCS 64B/65B Receive state diagram, part b
pcs_reset+!pcs_data_mode
TX_NORMAL
tx_lpi_active false
tx_lpi_qr_active false
tx_lpi_alert_active false
tx_lpi_req *
!ldpc_frame_done
PARTIAL_SLEEP
tx_lpi_active true
tx_lpi_req *
ldpc_frame_done
ldpc_frame_done
SEND_SLEEP
start lpi_tx_sleep_timer
tx_lpi_active true
lpi_tx_sleep_timer_done* lpi_tx_sleep_timer_done* lpi_tx_sleep_timer_done*

tx_lpi_req* tx_lpi_req* !tx_lpi_req
(tx_lpi_full_refresh + !tx_lpi_full_refresh*
!tx_refresh_active ) tx_refresh_active
SEND_INITIAL_QUIET
tx_lpi_qr_active true
tx_lpi_initial_quiet true
tx_lpi_req* !tx_lpi_req*
!tx_refresh_active ldpc_frame_done
SEND_QR
tx_lpi_qr_active true
tx_lpi_initial_quiet false
!tx_lpi_req *
ldpc_frame_done
SEND_ALERT
start lpi_tx_alert_timer
tx_lpi_qr_active false
tx_lpi_alert_active true
lpi_tx_alert_timer_done
SEND_WAKE
start lpi_tx_wake_timer
tx_lpi_alert_active false
lpi_tx_wake_timer_done
Figure 5516bEEE transmit state diagram
55.3.6 PCS management
55.3.6.1 Status
Insert the following text after the existing text in 55.3.6.1 as follows:
Rx LPI indication:
For EEE capability, this variable indicates the current state of the receive LPI function. This flag is
set to TRUE (register bit set to one) when the PCS 64B/65B Receive state diagram (Figure 5516a)
is in the RX_L or RX_W states. This status is reflected in MDIO register 3.1.8. A latch high view
of this status is reflected in MDIO register 3.1.10 (Rx LPI received).
Tx LPI indication
For EEE capability, this variable indicates the current state of the transmit LPI function. This flag
is set to TRUE (register bit set to one) when the PCS 64B/65B Transmit state diagram
(Figure 5515a) is in the TX_L or TX_W states. This status is reflected in MDIO register 3.1.9.
A latch high view of this status is reflected in MDIO register 3.1.11 (Tx LPI received).
55.4.1 PMA functional specifications
PMA SERVICE
INTERFACE
(rx_symb_vector)
(tx_symb_vector)
rem_rcvr_status
pcs_data_mode
loc_rcvr_status
alert_detect
link_status
rx_lpi_active
tx_mode
fr_active
config
recovered_clock

MONITOR
CLOCK PMA PMA PHY
LINK
RECOVERY RECEIVE TRANSMIT CONTROL
received_
clock
PMA_LINK.request
(link_control)
PMA_LINK.indication
(link_status)
MEDIUM
DEPENDENT
INTERFACE
BI_DD -
BI_DD +
BI_DC -
BI_DC +
BI_DB -
BI_DB +
BI_DA -
BI_DA +
(MDI)
NOTE 1The recovered_clock arc is shown to indicate delivery of the recovered clock signal back to PMA TRANSMIT for loop timing.
NOTE 2pcs_data_mode is required only for the EEE or fast retrain capabilities alert_detect and rx_lpi_active are only required for
the EEE capability fr_active is only required for the fast retrain capability
Figure 5517 PMA reference diagram
55.4.2 PMA functions
55.4.2.2 PMA Transmit function
Change the text in 55.4.2.2 as follows:
The PMA Transmit function comprises four synchronous transmitters to generate four pulse-amplitude
modulated signals on each of the four pairs BI_DA, BI_DB, BI_DC, and BI_DD. While send_fail is FALSE
and ALERT is not indicated by tx_symb_vector, PMA transmit shall continuously transmit onto the MDI
pulses modulated by the symbols given by tx_symb_vector[BI_DA], tx_symb_vector[BI_DB],
tx_symb_vector[BI_DC], and tx_symb_vector[BI_DD], respectively after processing with the THP,
optional transmit filtering, digital to analog conversion (DAC) and subsequent analog filtering. When
ALERT is indicated by tx_symb_vector, the alert signal is transmitted as specified in 55.4.2.2.1. When
send_fail is TRUE, the link failure signal is transmitted as specified in 55.4.2.2.2. The four transmitters shall
be driven by the same transmit clock, TX_TCLK. The signals generated by PMA Transmit shall follow the
mathematical description given in 55.4.3.1, and shall comply with the electrical specifications given in 55.5.
When the PMA_CONFIG.indication parameter config is MASTER, for both normal and LPI operation, the
PMA Transmit function shall continuously source TX_TCLK from a local clock source while meeting the
transmit jitter requirements of 55.5.3.3. The MASTER/SLAVE relationship may include loop timing. If loop
timing is implemented and the PMA_CONFIG.indication parameter config is SLAVE, the PMA Transmit
function shall source TX_TCLK from the recovered clock of 55.4.2.7 while meeting the jitter requirements
of 55.5.3.3. If loop timing is not implemented, the SLAVE PHY transmit clocking is identical to the
MASTER PHY transmit clocking. An EEE-capable PHY shall operate with loop timing when configured as
SLAVE.
Insert the following text after the existing text in 55.4.2.2:
EEE-capable PHYs shall implement a PMA Transmit function that generates the alert signal as defined in
55.4.2.2.1. PHYs that support the fast retrain capability shall implement a PMA Transmit function that
generates the link failure signal as defined in 55.4.2.2.2. If ALERT is indicated by tx_symb_vector at the
same time as send_fail is TRUE, then link failure signaling is transmitted.
Insert new subclauses 55.4.2.2.1 and 55.4.2.2.2 after 55.4.2.2 as follows:
55.4.2.2.1 Alert signal
PHYs that support the optional EEE capability will transmit the following PAM2 sequence when the
PMA_UNITDATA.request parameter is set to ALERT. The alert signal is sent for a total of 4 LDPC frame
periods and begins on a LDPC frame boundary. The alert signal is transmitted without THP filtering. The
alert signal is transmitted on pair A when the PHY operates as a MASTER. The alert signal is transmitted on
pair C when the PHY operates as a SLAVE. All other pairs transmit quiet as described in 55.3.4a.
When the PMA_CONFIG.indication(config) is MASTER the alert signal is composed of 7 repetitions of the
following 128 symbol PAM2 sequence, followed by 128 zero symbols.
xpr_master =
9 9 -9 -9 -9 -9 -9 -9 9 9 -9 -9 9 9 9 9
9 9 9 9 -9 -9 9 9 9 9 -9 -9 9 9 -9 -9
-9 -9 -9 -9 -9 -9 9 9 -9 -9 -9 -9 -9 -9 9 9
-9 -9 -9 -9 -9 -9 -9 -9 9 9 -9 -9 9 9 -9 -9
-9 -9 9 9 9 9 9 9 9 9 9 9 -9 -9 -9 -9
9 9 -9 -9 -9 -9 9 9 9 9 -9 -9 9 9 -9 -9
-9 -9 -9 -9 -9 -9 -9 -9 9 9 9 9 -9 -9 9 9
9 9 -9 -9 9 9 -9 -9 9 9 9 9 -9 -9 -9 -9
When the PMA_CONFIG.indication(config) is SLAVE the alert signal is composed of 7 repetitions of the
following 128 symbol PAM2 sequence, followed by 128 zero symbols.
xpr_slave =
-9 -9 -9 -9 9 9 9 9 -9 -9 9 9 -9 -9 9 9
9 9 -9 -9 9 9 9 9 -9 -9 -9 -9 -9 -9 -9 -9
-9 -9 9 9 -9 -9 9 9 9 9 -9 -9 -9 -9 9 9
-9 -9 -9 -9 9 9 9 9 9 9 9 9 9 9 -9 -9
-9 -9 9 9 -9 -9 9 9 -9 -9 -9 -9 -9 -9 -9 -9
9 9 -9 -9 -9 -9 -9 -9 9 9 -9 -9 -9 -9 -9 -9
-9 -9 9 9 -9 -9 9 9 9 9 -9 -9 9 9 9 9
9 9 9 9 -9 -9 9 9 -9 -9 -9 -9 -9 -9 9 9
The alert signal is followed by a wake signal composed of repeated IDLE characters encoded using the 64B/
65B encoding technique. At the start of the wake signal all THP feedback delay lines are initialized with
zeros.
55.4.2.2.2 Link failure signal
PHYs that support the fast retrain capability transmit the link failure signal under the control of the Fast
Retrain state diagram. The link failure signal indicates to the link partner that a link failure has been detected
and that the link partners should begin the fast retrain procedure.
The link failure signal is sent for 4 LDPC frames and begins on a LDPC frame boundary. The link failure
signal is transmitted without THP filtering. The link failure signal is transmitted on pair A when the PHY
operates as a MASTER. The link failure signal is transmitted on pair C when the PHY operates as a SLAVE.
All other pairs transmit quiet as described in subclause 55.3.4a.
When the PMA_CONFIG.indication(config) is MASTER, the link failure signal is composed of 7

repetitions of the following 128 symbol PAM2 sequence, followed by 128 zero symbols.
xfr_master = xpr_master (1)
When the PMA_CONFIG.indication(config) is SLAVE the link failure signal is composed of 7 repetitions of
the following 128 symbol PAM2 sequence, followed by 128 zero symbols.
xfr_slave = xpr_slave (1)
55.4.2.4 PMA Receive function
Change the third paragraph in 55.4.2.4 as follows:
The PMA Receive function uses the scr_status parameter and the state of the equalization, cancellation, and
estimation, and LPI functions to determine the quality of the receiver performance, and generates the
loc_rcvr_status variable accordingly. The precise algorithm for generation of loc_rcvr_status is
implementation dependent.
Insert the following text after the existing text in 55.4.2.4:
PMA receive functions that support the optional EEE capability shall generate alert_detect when the alert
signal is detected at the receiver. The PMA receive function asserts alert_detect after the entire alert signal
(3.5 LDPC frame periods of the xpr_master or xpr_slave sequence and 0.5 frames of silence) has been
detected. The alert signal is specified in 55.4.2.2.1. The criterion used to generate alert_detect is left to the
implementor.
PHYs that support the fast retrain capability shall set link_fail_detect to TRUE when the link failure signal is
reliably detected at the receiver. The PMA receive function asserts link_fail_detect after the entire link
failure signal (3.5 LDPC frame periods of the xfr_master or xfr_slave sequence and 0.5 frames of silence)
has been detected. The link failure signal is specified in 55.4.2.2.2. The criterion used to generate
link_fail_detect is left to the implementor. It is highly recommended that the generation of link_fail_detect is
qualified with repeated errored frames at the LDPC decoder output.
55.4.2.5 PHY Control function
55.4.2.5.14 Startup sequence
Insert the following sentence at the end of the second paragraph of 55.4.2.5.14:
During normal training, prior to enabling the transmitter, the THP coefficients are set to zero.
Change the eighth paragraph of 55.4.2.5.14 as follows:
In SLAVE mode, PHY Control transitions to the PMA_Training_Init_S state only after the SLAVE PHY
acquires timing, converges its equalizers, acquires its descrambler state and sets loc_SNR_margin=OK. The
SLAVE shall respond using the fixed PBO transmit power level, PBO=4 (corresponding to a power backoff
of 8 dB). For PHYs with the EEE capability, further requirements for this transition are described in
55.3.4a.1.
Change the fifteenth paragraph of 55.4.2.5.14 as follows:
After the PHY completes successful training and establishes proper receiver operations, PCS Transmit
conveys this information to the link partner via transmission of the parameter InfoField value
loc_rcvr_status. The link partners value for loc_rcvr_status is stored in the local device parameter rem_rcvr
status. When the condition loc_rcvr_status=OK and rem_rcvr_status=OK is satisfied, each PHY announces
a transition to the PCS_Test (trans_to_PCS_Test=1) and starts the transition counter as described in 55.4.5.1.
For PHYs with the EEE capability, further requirements for this transition are described in 55.3.4a.1.
Insert the following text after the existing text in 55.4.2.5.14:
After reaching the PCS_Data state PHYs with the EEE capability can transition to the LPI receive mode
under the control of the link partner and to the LPI transmit mode under control of the local LPI client.
55.4.2.5.15 Fast retrain function
PHYs that support the fast retrain capability shall implement the fast retrain state diagram shown in
Figure 5527b. PHYs may request a fast retrain by setting the variable loc_fr_req to TRUE. This causes the
transmission of an easily-detected link failure signal specified in 55.4.2.2.2. After completing the link failure
signal the PHY shall transition to the PMA_Coeff_Exch state, keep its THP turned on with its previously
exchanged coefficients, and send PAM2 signaling within a time period equivalent to 9 LDPC frame periods.
After the detection of the link failure signal, a PHY shall transition to the PMA_Coeff_Exch state and
respond with PAM2 signaling within a time period equivalent to 9 LDPC frame periods after receiving the
link failure signal.
The PAM2 symbols are generated using the PMA sidestream scrambler polynomials shown in Figure 55-13.
The training sequence without periodic re-initialization described in 55.3.4 shall be used during fast
retraining, with the scramblers free-running from PCS Reset. If scrambler re-initialization is used for normal
training, it shall be disabled and the scramblers shall begin free-running when the PHY Control state
diagram enters the PCS_Test state and the variable fr_active is FALSE.
Note that reliable traffic on the transmitter may be interrupted when the local receiver requests a fast retrain.
Following the link failure signal, the two link partners transition back to the PMA_Coeff_Exch state and
follow the training procedure described in 55.4.2.5.14, with the exception that the initial infofield
countdown values are reduced as indicated in Figure 55-25 and Figure 55-26.
To ensure interoperability the training times in Table 556a should be observed during the fast retrain.
Table 556aRecommended fast retrain sequence timing
Recommended
State
maximum time (ms)
PMA_Coeff_Exch state 20
PMA_Fine_Adjust state 10
55.4.2.6 Link Monitor function
55.4.2.6a Refresh Monitor function
The Refresh monitor is required for PHYs that support the EEE capability. The Refresh monitor operates
when the PHY is in the LPI receive mode. The Refresh monitor shall comply with the state diagram of
Figure 5516a. The function forces a link retrain if a refresh signal is not reliably detected within a moving
time window equivalent to 50 complete quiet-refresh cycles (nominally equal to 8.192 ms), when the PHY is
in the lower power receive mode.
55.4.4 Automatic MDI/MDI-X configuration
Insert the following text after the existing text in 55.4.4:
For EEE-capable PHYs, the MDI/MDIX function configuration shall apply to refresh and alert signaling.
For PHYs with the fast retrain capability, the MDI/MDIX function configuration shall apply to link failure
signaling.
55.4.5.1 State diagram variables
Change the text in 55.4.5.1 as follows:
transition_count
This variable reports the value of the transition counter contained in the InfoField sent
to the remote device. Transition_count must comply with the state diagram description
given in 55.4.6.2. When the message field contains a flag for a state transition,
the transition counter denotes the remaining number of InfoField until the next state
transition. MASTER initiates the transition to PMA_Coeff_Exch count with the
trans_to_Coeff_Exch=1 flag and a counter value of 29 (10 ms). The SLAVE responds
prior to the counter reaching 26 (1 ms) with the same flag and a count value matching
the MASTER. Then both PHYs transition to PMA_Coeff_Exch within one PMA frame.
The same sequence is performed in the transition to PMA_Fine_Adjust state and PCS_Test state
using the trans_to_Fine_Adjust=1 and trans_to_PCS_Test=1 flags respectively. In EEE-capable
PHYs, synchronization of the PMA frames is tightly controlled as described in 55.3.4a.1.
When the message field does not contain a flag for a state transition, the transition counter
is set to zero and ignored by the receiver.
Values: 0 to 29
Insert the following variable definitions after all existing variable definitions in 55.4.5.1:
The following variables are required only for PHYs that support the EEE capability:
lpi_refresh_detect
Set TRUE when the receiver has reliably detected refresh signaling and FALSE otherwise. The
exact criteria left to the implementor.
pcs_data_mode
Generated by the PMA PHY Control function and indicates whether or not the local PHY may
transition its PCS state diagrams out of their initialization states. The current value of the pcs_data_mode is
passed to the PCS via the PMA_PCSDATAMODE.indicate primitive. In the absence of the optional EEE
and fast retrain capabilities, the PHY operates as if the value of this variable is TRUE.
mtc
mtc is the transition count for a MASTER PHY during normal training and fast retraining. mtc
shall be equal to 29 for normal training and 25 for fast retrain.
stc
stc is the transition count for a SLAVE PHY during normal training and fast retraining. stc shall be
equal to 26 for normal training and 24 for fast retrain.
The following six variables are required only for PHYs that support the fast retrain capability:
fr_enable
This variable is set to TRUE if 1.147.0 is set to 1 and fast retrain is supported. The variable is set to
FALSE otherwise.
loc_fr_req
Set TRUE when the receiver has detected a link failure condition and is requesting a fast retrain; set
FALSE otherwise.
loc_fr_detect
Set TRUE when the receiver has reliably detected the link failure signal. It is highly recommended
that loc_fr_detect is qualified with the reception of errored blocks at the LDPC decoder output. Set FALSE
when the link failure signal is not detected.
send_link_fail
When TRUE indicates that the PMA should send the link failure signal. When FALSE the variable
has no effect.
fr_active
Set TRUE when the PHY is performing a fast retrain and set FALSE otherwise.
fast_retrain_flag
Set TRUE after the PHY generates or detects a link failure signal and set FALSE otherwise.
55.4.5.2 Timers
Insert the following timer definitions after all existing timer definitions in 55.4.5.2:
The following timer is required only for PHYs that support the EEE capability:
lpi_refresh_rx_timer
This timer is used to monitor link quality during the LPI receive mode. If the PHY does not reliably
detect reliable refresh signaling before this timer expires then a full retrain is performed.
Values: The condition lpi_refresh_rx_timer_done becomes true upon timer expiration.
Duration: This timer shall have a period equal to 50 complete quiet-refresh signal periods,
equivalent to 8.192 ms.
The following two timers are required only for PHYs that support the fast retrain capability:
link_fail_sig_timer
Determines the period of time the PHY sends the link failure signal.
Values: The condition link_fail_sig_timer_done becomes true upon timer expiration.
fr_maxwait_timer
Determines the period of time the PHY has to transition its PCS Control State to PCS_Test
following a fast retrain before the fast retrain is aborted and a full retrain performed.
Values: The condition fr_maxwait_timer_done becomes true upon timer expiration.
Duration: This timer shall have a period equal to 30 ms.
55.4.5.4 Counters
Insert the following counter definitions after all existing counter definitions in 55.4.5.4:
The following two counters are required only for PHYs that support the fast retrain capability:
fr_tx_counter
Counts the number of times the PHY initiates a fast link retrain by transmitting the link
failure signal. This counter is reflected in MDIO register 1.147.10:6 specified in 45.2.1.76a.2.
fr_rx_counter
Counts the number of times the PHY begins a fast link retrain in response to the detection of
link failure signalling from the link partner. This counter is reflected in MDIO register 1.147.15:11
specified in 45.2.1.76a.1.
55.4.6.1 PHY Control state diagram

link_control ENABLE +
pma_reset = ON
DISABLE_10GBASE-T
I
TRANSMITTER
INIT_MAXWAIT_TIMER
NOTEFor PHYs that start maxwait_timer
do not support the fast
retrain capability, UCT
the variable SILENT
fast_retrain_flag is set start minwait_timer
to FALSE. tx_mode SEND_Z
fr_active false
pcs_data_mode false
THP_tx zeros
config = SLAVE *
config = MASTER * loc_SNR_margin = OK *
minwait_timer_done en_slave_tx = 1 *
minwait_timer_done
PMA_Training_Init_M PMA_Training_Init_S
start minwait_timer
PBO_tx 4
tx_mode SEND_T PBO_tx 4
tx_mode SEND_T
loc_SNR_margin = OK loc_SNR_margin = OK *
minwait_timer_done
PMA_PBO_Exch
Exchange_Final_PBO
trans_to_Coeff_Exch = 1 *
transition_count = 0
PMA_Coeff_Exch
PBO_tx PBO_next
Exchange_THP_coefficients
fr_maxwait_timer_done * trans_to_Fine_Adjust = 1 *
UCT fr_active transition_count = 0
PMA_Fine_Adjust
PMA_INIT_FR
I THP_tx THP_next
fr_active true
fast_retrain_flag false fr_maxwait_timer_done * trans_to_PCS_Test = 1 *
tx_mode SEND_T fr_active transition_count = 0
pcs_data_mode false PCS_Test
I start minwait_timer
tx_mode SEND_N
lpi_rxw_err_cnt 0
!fr_active *
( loc_rcvr_status = NOT_OK +
(minwait_timer_done *
fr_active * loc_rcvr_status = OK * PCS_status = NOT_OK) )
( loc_rcvr_status = NOT_OK + minwait_timer_done *
(minwait_timer_done * I PCS_status = OK
PCS_status = NOT_OK) ) PCS_Data
stop maxwait_timer
start minwait_timer
tx_mode SEND_N minwait_timer_done*
stop fr_maxwait_timer loc_rcvr_status = NOT_OK
minwait_timer_done* pcs_data_mode true
fast_retrain_flag fr_active false
Figure 5524PHY Control state diagram
55.4.6.2 Transition counter state diagrams
Replace Figure 55-25 and Figure 55-26 with the following new figures:
NOTEFor PHYs that do

min_wait_timer_done not support the fast retrain
INIT capability, the variable
fast_retrain_flag is set to
FALSE.
PBO_exchange_done = TRUE
START_COUNTER PMA_Coeff_Exch
transition_count <= mtc
fast_retrain_flag = TRUE
trans_to_Coeff_Exch <= 1
STOP_COUNTER PMA_Coeff_Exch
trans_to_Coeff_Exch <=0
coeff_exchange_done = TRUE
START_COUNTER PMA_Fine_Adjust
trans_to_Fine_Adjust <= 1
STOP_COUNTER PMA_Fine_Adjust
rem_rcvr_status = OK
START_COUNTER_PCS_Test
trans_to_PCS_Test <= 1
STOP_COUNTER_PCS_Test
Figure 5525MASTER transition counter state diagram
NOTEFor PHYs
MessageField_IF = trans_to_Coeff_Exch *
that do not support
master_transition_counter > 26 the fast retrain
capability,
the variable
fast_retrain_flag is
START_COUNTER_PMA_Coeff_Exch set to FALSE.
transition_count <= master_transition_counter
fast_retrain_flag = TRUE
STOP_COUNTER_ PMA_Coeff_Exch
MessageField_IF = trans_to_Fine_Adjust *
master_transition_counter > stc
START_COUNTER_PMA_Fine_Adjust
STOP_COUNTER_ PMA_Fine_Adjust
rem_rcvr_status = OK *
MessageField_IF = trans_to_PCS_Test *
master_transition_counter > stc
START_COUNTER_PCS_Test
STOP_COUNTER_PCS_Test
Figure 5526SLAVE transition counter state diagram
55.4.6.3 Link Monitor state diagram
Insert two new subclauses 55.4.6.4 and 55.4.6.5 after 55.4.6.3 as follows:
55.4.6.4 EEE Refresh monitor state diagram
!rx_lpi_active
LPI_OK
rx_lpi_active
!lpi_refresh_rx_timer_done *
LPI_MON_REFRESH lpi_refresh_detect
start lpi_refresh_rx_timer
lpi_refresh_rx_timer_done
LPI_REFRESH_TIMEOUT
loc_rcvr_status NOT_OK
NOTEThis state diagram is only required when the PHY supports the EEE capability.
Figure 5527aEEE Refresh monitor state diagram
55.4.6.5 Fast retrain state diagram
( tx_mode=SEND_N * !loc_fr_req *
!loc_fr_detect ) + !fr_enable
FR_LINK_OK
fast_retrain_flag false
send_link_fail false
fr_enable * fr_enable *
loc_fr_req *
ldpc_frame_done loc_fr_detect
FR_SEND_FAIL FR_INC_RX_CNT
send_link_fail true fr_rx_counter++

start_link_fail_sig_timer
fr_tx_counter++
link_fail_sig_timer_done UCT
FR_START_TIMER
send_link_fail false
fast_retrain_flag true
start fr_maxwait_timer
loc_fr_req false
NOTEThis state diagram is only required when the PHY supports the fast retrain capability.
Figure 5527bFast retrain control state diagram
55.5 PMA electrical specifications
55.5.3 Transmitter electrical specifications
55.5.3.5 Transmit clock frequency
Insert the following paragraph after the existing text in 55.5.3.5:
When the transmitter is in the LPI transmit mode or when the receiver is in the LPI receive mode the
transmitter clock short-term rate of frequency variation shall be less than 0.1 ppm/second. The short-term
frequency variation limit shall also apply when switching to and from the LPI mode.
55.6 Management interfaces
55.6.1 Support for Auto-Negotiation
Insert new items d) and e) into the lettered list in 55.6.1 as follows:
a) To negotiate that the PHY is capable of supporting 10GBASE-T transmission.

b) To determine the MASTER-SLAVE relationship between the PHYs at each end of the link.
c) To determine whether the local PHY performs PMA training pattern reset.
d) To determine whether the local PHY supports the EEE capability.
e) To determine whether the local PHY supports the fast retrain capability.
55.6.1.2 10GBASE-T Auto-Negotiation page use
Change Table 55-11 by inserting new rows for bits U24, U23, U22, and U21, and changing bit U19 and
reserved rows as follows (only changes to table are shown):
Table 55-1110GBASE-T Base and next pages bit assignments
Extended next page (Unformatted Message Code Field)

U31:U25 Reserved, transmit as 0
21
U24 10GBASE-T EEE Defined in 45.2.7.13.4
(1 = Advertise EEE capability for 10GBASE-T
0 = Do not advertise EEE capability for 10GBASE-T)
U23 1000BASE-T EEE Defined in 45.2.7.13.5
(1 = Advertise EEE capability for 1000BASE-T
0 = Do not advertise EEE capability for 1000BASE-T)
U22 100BASE-TX EEE Defined in 45.2.7.13.6
(1 = Advertise EEE capability for100BASE-TX
0 = Do not advertise EEE capability for 100BASE-TX)
U21 Reserved
U20 LD PMA training reset request
(1 = Local Device requests that Link Partner reset PMA
training PRBS every frame Defined in 45.2.7.10.5
0 = Local Device requests that Link Partner run PMA training
PRBS continuously)
U19 Fast retrain ability Defined in 45.2.7.10.5a
(1 = Advertise PHY as supporting fast retrain,
0 = Advertise PHY as not supporting fast retrain)
Reserved, transmit as 0
55.10 PHY labeling
Insert new items e) and f) in the lettered list in 55.10 as follows:
It is recommended that each PHY (and supporting documentation) be labeled in a manner visible to the user
with at least the following parameters:
a) Data rate capability and units thereof
b) Power level in terms of maximum current drain (for external PHYs)
c) Port type (i.e., 10GBASE-T)
d) Any applicable safety warnings
e) EEE support
f) Fast retrain support

Clause 55, Physical Coding Sublayer (PCS), Physical Medium Attachment (PMA)
sublayer and baseband medium, type 10GBASE-T17
Insert two new rows as the last two rows in the table in 55.12.2 as follows:

*EEE Support of EEE capability O Yes [ ] 55.1.3.3
No [ ]
*FR Support of Fast Retrain O Yes [ ] 55.4.2.5.15
capability No [ ]
55.12.3 Physical Coding Sublayer (PCS)
Change the table in 55.12.3 as follows:
PCT1 PCS Transmit function state 55.3.2.2 M Yes [ ] See Figure 5515
diagram
PCT1a PCS Transmit function state 55.3.2.2 EEE:M Yes [ ] See Figure 5515 and
diagram with EEE states Figure 5515a
PCT2 PCS Transmit bit ordering 55.3.2.2.4 M Yes [ ] See Figure 556 and
Figure 558
PCT3 Invalid control code handling 55.3.2.2.6 M Yes [ ]
PCT4 /I/ insertion and deletion 55.3.2.2.9 M Yes [ ]
PCT4a /LI/ insertion and deletion 55.3.2.2.10 EEE:M Yes [ ]

PCT5 /O/ deletion 55.3.2.2.12 M Yes [ ]
PCT6 Scrambler as MASTER 55.3.2.2.15 M Yes [ ]
PCT7 Scrambler as SLAVE 55.3.2.2.15 M Yes [ ]
PCT8 CRC8 55.3.2.2.16 M Yes [ ] See Figure 5511
PCT9 LDPC encoding 55.3.2.2.17 M Yes [ ] Generator matrix is described

in Annex 55A
PCT10 DSQ128 mapping 55.3.2.2.18 M Yes [ ]
PCT10a EEE Transmit function state 55.3.2.2.21 EEE:M Yes [ ] See Figure 5516b
diagram
PCT10b LP_IDLE input to scrambler 55.3.2.2.21 EEE:M Yes [ ]

during LPI mode
PCT10c lpi_tx_mode control 55.3.2.2.21 EEE:M Yes [ ]
17
PCT11 PCS test pattern mode 55.3.3 M Yes [ ] See Figure 556
PCT12 PMA trainingMASTER 55.3.4 M Yes [ ]

scrambler
PCT13 PMA trainingSLAVE 55.3.4 M Yes [ ]

scrambler
PCT14 PMA training scrambler reset 55.3.4 M Yes [ ] If requested by Link Partner
during Auto Negotiation
PCT15 PMA training scrambler initial 55.3.4 M Yes [ ] In no case shall the scrambler
state state be initialized to all zeros
PCT15a LPI active pair and 55.3.4a.1 EEE:M Yes [ ]
refresh_active signals
PCT15b Alert signaling in place of 55.3.4a.3 EEE:M Yes [ ]

refresh signaling
PCT15c Slave synchronization 55.3.4a.1 EEE:M Yes [ ]
PCT15d Quiet launch power 55.3.4a.2 EEE:M Yes [ ]
PCT15e LPI sleep timer 55.3.5.2.3 EEE:M Yes [ ]
PCT15f LPI alert timer 55.3.5.2.3 EEE:M Yes [ ]
PCT15g LPI wake timer 55.3.5.2.3 EEE:M Yes [ ]
PCT15h LPI rx wake timer 55.3.5.2.3 EEE:M Yes [ ]
PCT15i LPI tx wake timer 55.3.5.2.3 EEE:M Yes [ ]
PCT15j LPI scrambler 55.3.4a.3 EEE:M Yes [ ] The training sequence without
periodic re-initialization
described in 55.3.4 shall be
used
PCT15k Disable scrambler 55.3.4a.3 EEE:M Yes [ ]

reinitialization
PCT15l Refresh using THP 55.3.4a.3 EEE:M Yes [ ]
PCT15m Reset THP at the start of 55.3.4a.3 EEE:M Yes [ ]

refresh
PCT15n Master alert on pair A, other 55.3.4a.3 EEE:M Yes [ ]

pairs silent
PCT15o Slave alert on pair C, other 55.3.4a.3 EEE:M Yes [ ]

pairs silent
PCT15p Inactive pairs transmit zeros 55.3.4a.3 EEE:M Yes [ ]
PCT16 ENCODE function 55.3.5.2.4 M Yes [ ] Encode the block as specified

in 55.3.2.2.2
PCT17 PCS loopback setup 55.3.6.3 M Yes [ ]
55.12.4 Physical Medium Attachment (PMA)
Insert rows PMF8a and PMF8b; PMF10a and PMF10b; PMF16b, PMF16c, and PMF16d; PMF17a
and PMF17b; and PMA18a after existing rows PMF8, PMF10, PMF16, PMF17, and PMF18,
respectively, as follows:
PMF8a Generates alert signal 55.4.2.2 EEE:M Yes [ ] Generates the alert signal
defined in 55.4.2.2.1
PMF8b Generates link failure signaling 55.4.2.2 FR:M Yes [ ] Generates the link failure signal
No [ ] defined in 55.4.2.2.2
PMF10a Implement alert_detect 55.4.2.4 EEE:M Yes [ ] Generates alert_detect when the
alert signal is detected at the
receiver
PMF10b Detect link failure signaling 55.4.2.4 FR:M Yes [ ] Sets link_fail_detect to true
No [ ] when the link failure signal is
detected
PMF16b Implements fast retrain state 55.4.2.5.15 FR:M Yes [ ]

diagram No [ ]
PMF16c Behavior after fast retrain 55.4.2.5.15 FR:M Yes [ ] Transmit PAM2 within 9 LDPC
request No [ ] frame periods following link
failure request
PMF16d Behavior after fast retrain signal 55.4.2.5.15 FR:M Yes [ ] Transmit PAM2 within 9 LDPC
detection No [ ] frame periods following link
failure signal detection
PMF17a Refresh monitor state diagram 55.4.2.6a EEE:M Yes [ ] Implements state diagram of
No [ ] Figure 5516a
PMF17b Recommended fast retrain 55.4.2.5.15 FR:O Yes [ ] See Table 556
sequence timing No [ ]
PMF18a MDIX for EEE refreshes and 55.4.4 EEE:M Yes [ ]

alert
55.12.5 Management interface
Insert rows MF6a and MF6b after row MF6 as follows:
MF6a EEE advertisement 55.6.1.2 EEE:M Yes [ ] As defined in Table 55-11
MF6b Fast retrain ability advertisement 55.6.1.2 FR:M Yes [ ] As defined in Table 55-11
55.12.6 PMA Electrical Specifications
Insert rows PME25a and PME25b after row PMA25 as follows:
PME25a Maximum short term rate of 55.5.3.5 EEE:M Yes [ ] Less than 0.1 ppm/s
frequency variation during LPI
PME25b Maximum short term rate of 55.5.3.5 EEE:M Yes [ ] Less than 0.1 ppm/s
frequency variation when
switching to and from LPI
69. Introduction to Ethernet operation over electrical backplanes
69.1 Overview
69.1.1 Scope
Insert the following text as the last paragraph in 69.1.1:
Backplane Ethernet optionally supports Energy-Efficient Ethernet (EEE) to reduce energy consumption.
The EEE capabilities are advertised during Auto-Negotiation.
69.1.2 Objectives
Insert item f) at end of the lettered list of objectives in 69.1.2 as follows:
f) Optionally support EEE for 10 Gb/s rates or lower.
69.2 Summary of Backplane Ethernet Sublayers
69.2.3 Physical Layer signaling systems
Replace Table 69-1 with the following new table:
Table 691Nomenclature and clause correlation
Clause
35 36 46 48 49 51 70 71 72 73 74 78 81 82 83 83A 84
Energy-Efficient Ethernet (EEE)
1000BASE-X PCS/PMA
10GBASE-X PCS/PMA
10GBASE-KX4 PMD
40GBASE-KR4 PMD
1000BASE-KX PMD
10GBASE-KR PMD
40GBASE-R PMA
10GBASE-R PCS
40GBASE-R PCS
Auto-Negotiation
Nomenclature
BASE-R FEC
Serial PMA
XLGMII
XGMII
XLAUI
GMII
RS
RS
RS
1000BASE-KX Ma Oa M M M O
10GBASE-KX4 M O M M M O
10GBASE-KR M O M M M M O O
40GBASE-KR4 M O M O M M O M
aO = Optional, M = Mandatory
Insert new subclause 69.2.6 after 69.2.5 as follows:
69.2.6 Low-Power Idle
With the optional EEE feature, described in Clause 78, Backplane Ethernet PHYs for 10Gb/s or lower can
achieve lower power consumption during periods of low link utilization. The EEE capabilities are advertised
during Auto-Negotiation for Backplane Ethernet. The Backplane Ethernet LPI allows each link direction to
enter sleep, refresh, or wake states asymmetric from the other direction.
70. Physical Medium Dependent Sublayer and Baseband Medium, Type

1000BASE-KX
70.1 Overview
Change Table 70-1 by inserting a new row below the last row as follows:
Table 701PHY (Physical Layer) clauses associated with the 1000BASE-KX PMD
Associated clause 1000BASE-KX
78Energy-Efficient Ethernet Optional
Insert the following paragraph at the end of 70.1:
A 1000BASE-KX PHY with the optional Energy-Efficient Ethernet (EEE) capability may optionally enter
the Low Power Idle (LPI) mode to conserve energy during periods of low link utilization. The Assert LPI
request at the GMII is encoded in the transmitted symbols. Detection of LPI signaling in the received
symbols is indicated as Assert LPI at the GMII. Upon the detection of Assert LPI at the GMII, an
energy-efficient 1000BASE-KX PHY continues transmitting for a predefined period, then ceases
transmission and deactivates transmit functions to conserve energy. The PHY periodically transmits during
this quiet period to allow the remote PHY to refresh its receiver state (e.g., timing recovery, adaptive filter
coefficients) and thereby track long-term variations in the timing of the link or the underlying channel
characteristics. If, during the quiet or refresh periods, normal interframes resume at the GMII, the PHY
reactivates transmit functions and initiates transmission. This transmission will be detected by the remote
PHY, causing it to also exit the .
70.2 Physical Medium Dependent (PMD) service interface
Insert the following text at the end of 70.2:
The PMD provides the following service interface signals if EEE is supported:
These messages signals are defined for the PCS in 36.2.5.1.6.
70.2.1 PMD_RXQUIET.request
This primitive is generated by the PCS Receive Process when EEE is supported to indicate that the input
signal is quiet and the PMA and PMD receiver may go into low power mode. See 36.2.4.12a. When EEE is
not supported, the primitive is never invoked and the PMD behaves as if rx_quiet = FALSE.
PMD_RXQUIET.request (rx_quiet)
The rx_quiet parameter takes on one of two values: TRUE or FALSE.
The PCS generates this primitive to request the appropriate PMD receive LPI state.
This variable is from the receive process of the PCS to control the power-saving function of the local PMD
receiver. The 1000BASE-KX PHY receiver should put unused functional blocks into a low power state to
save energy.
70.2.2 PMD_TXQUIET.request
This primitive is generated by the PCS Transmit Process when EEE is supported to indicate that the PMA
and PMD transmit functions may go into a and to disable the PMD transmitter. See 70.6.5. When EEE is not
supported, the primitive is never invoked and the PMD behaves as if tx_quiet = FALSE.
PMD_TXQUIET.request (tx_quiet)
The tx_quiet parameter takes on one of two values: TRUE or FALSE.
The PCS generates this primitive to request the appropriate PMD transmit LPI state.
This primitive affects operation of the PMD Transmit disable function as described in 70.6.5. The
1000BASE-KX PHY transmitter should put unused functional blocks into a lower power state to save
energy.
70.6 PMD functional specifications
Change the 70.6.4 as follows:
70.6.4 PMD signal detect function
For 1000BASE-KX operation PMD signal detect is mandatory if EEE is supported. When EEE is not
supported, the PMD signal detect is optional and its definition is beyond the scope of this specification.
When PMD signal detect is not implemented, the value of SIGNAL_DETECT shall be set to OK for
purposes of management and signaling of the primitive.
If EEE is supported, a local PMD signal detect function shall report to the PMD service interface using the
message PMD_SIGNAL.indication(SIGNAL_DETECT). This message is signaled continuously. For EEE,
the SIGNAL_DETECT parameter can take on one of two values, OK or FAIL, indicating whether the PMD
is detecting electrical energy at the receiver (OK) or not (FAIL). When SIGNAL_DETECT = FAIL,
PMD_UNITDATA.indication is undefined. The signal energy from a compliant transmitter shall set
SIGNAL_DETECT to OK within 750 ns when transitioning from LPI quiet to active and set
SIGNAL_DETECT to FAIL within 750 ns when transitioning from active to LPI quiet.
70.6.5 PMD transmit disable function
The PMD transmit disable function is mandatory if EEE is supported and is otherwise optional. When
implemented, it allows the transmitter to be disabled with a single variable.
a) When the PMD_transmit_disable variable is set to ONE, this function shall turn off the transmitter
such that it drives a constant level (i.e., no transitions) and does not exceed the maximum differential
peak-to-peak output voltage specified in Table 704.
b) If a PMD_fault (70.6.7) is detected, then the PMD may turn off the electrical transmitter.
c) Loopback, as defined in 70.6.6, shall not be affected by PMD_transmit_disable.
d) For EEE capability, the PMD_transmit_disable function shall turn off the transmitter after tx_quiet
is asserted within the time and voltage level specified in 70.7.1.5. The PMD_transmit_disable
function shall turn on the transmitter after tx_quiet is de-asserted within a time and voltage level
specified in 70.7.1.5.
Insert a new subclause 70.6.10 after 70.6.9 as follows:
70.6.10 PMD LPI function
The PMD LPI function responds to the transitions between Active, Sleep, Quiet, Refresh, and Wake states
via the PMD_TXQUIET and PMD_RXQUIET requests. Implementation of the function is optional. EEE
capabilities and parameters are advertised during the Backplane Auto-negotiation as described in 45.2.7.13.
The transmitter on the local device informs the link partners receiver when to sleep, refresh, and wake. The
local receivers transitions are controlled by the link partners transmitter and change independently from
the local transmitters states and transitions.
The transmitter sends /LI/ ordered sets during the sleep and refresh states, disables the transmitter during
quiet, and forwards /I/ during the wake phase.
If EEE is supported, the PMD transmit function enters into a when tx_quiet is set to TRUE and exits when
tx_quiet is set to FALSE. While tx_quiet is TRUE the PMD transmitter functional blocks should be
deactivated to conserve energy. The PMD receive function enters into a low power mode when rx_quiet is
set to TRUE and exits when rx_quiet is set to FALSE. While rx_quiet is TRUE the PMD receiver functional
blocks should be deactivated to conserve energy.
70.7 1000BASE-KX electrical characteristics
70.7.1 Transmitter characteristics
Change Table 70-4 by inserting a new row as follows:
Table 704Transmitter characteristics for 1000BASE-KX
Subclause
reference
Signaling speed 70.7.1.3 1.25 100 ppm GBd
Differential peak-to-peak output voltage 70.7.1.5 800 to 1600 mV
Differential peak-to-peak output voltage (max.) with TX disabled 70.6.5 30 mV
DC common-mode voltage limits 70.7.1.5 0.4 to 1.9 V
Common-mode voltage deviation (max) during LPI 70.7.1.5 150 mV
[See Equation (701)

Differential output return loss (min.) 70.7.1.6 dB
and Equation (702)]
Transition timea (20%80%) 70.7.1.7 60 to 320 ps
Output jitter (max. peak-to-peak)

Deterministic jitterb 0.10 UI
70.7.1.8
Random jitter 0.15 UI
Total jitterc 0.25 UI
aTransition time parameters are recommended values, not compliance values.
bDeterministic jitter is already incorporated into the differential output template.
cAt BER 1012.
70.7.1.5 Output amplitude
Insert the following paragraph at the end of 70.7.1.5:
For EEE capability, the transmitters differential peak-to-peak output voltage shall be less than 30 mV
within 500 ns of tx_quiet being asserted. Furthermore, the transmitters differential peak-to-peak output
voltage shall be greater than 720 mV within 500 ns of tx_quiet being de-asserted. The transmitter output
shall be fully compliant within 5 s after tx_quiet is set to FALSE. During LPI, the common mode shall be
maintained to within 150 mV of the pre-LPI value.

Clause 70, Physical Medium Dependent (PMD) sublayer and baseband medium,
type 1000BASE-KX18
LPI LPI 70.6.10 Capable of LPI O Yes [ ]

No [ ]
70.10.4 PICS proforma tables for Clause 70, Physical Medium Dependent (PMD) sublayer
and baseband medium, type 1000BASE-KX
Insert rows FS5ad and FS7a after rows FS5 and FS7, respectively, in the table in 70.10.4.1:
70.10.4.1 PMD functional specifications
FS5a PMD Signal Detect during LPI 70.6.4 Indicate signal energy during LPI:M Yes [ ]
LPI N/A [ ]
FS5b Transmit Disable during LPI 70.6.5 Disable transmitter during LPI:M Yes [ ]
tx_quiet N/A [ ]
FS5c Signal Detect for EEE 70.6.4 Transition timing to set LPI:M Yes[ ]
SIGNAL_DETECT N/A [ ]
FS5d Transmit Disable 70.6.5 Disables Transmitter when TD:M Yes [ ]

PMD_Transmit_disable set to N/A [ ]
ONE
FS7a tx_quiet disabled transmitter 70.7.1 Disables Transmitter when LPI:M Yes [ ]
tx_quiet is asserted as specified N/A [ ]
in 70.7.1.5
18
Insert the following new rows TC8ab after TC8 in the table in 70.10.4.3:
70.10.4.3 Transmitter electrical characteristics
TC8a Output Amplitude LPI voltage 70.7.1.5 Less than 30 mV within 500 ns LPI:M Yes [ ]
of tx_quiet N/A [ ]
TC8b Output Amplitude ON voltage 70.7.1.5 Greater than 720 mV within LPI:M Yes [ ]
500 ns of tx_quiet de-asserted N/A [ ]

10GBASE-KX4
71.1 Overview
A 10GBASE-KX4 PHY with the optional Energy-Efficient Ethernet (EEE) capability may optionally enter
request at the XGMII is encoded in the transmitted symbols. Detection of LPI signaling in the received
symbols is indicated as Assert LPI at the XGMII. Upon the detection of Assert LPI at the XGMII, an
energy-efficient 10GBASE-KX4 PHY continues transmitting for a predefined period, then ceases
characteristics. If, during the quiet or refresh periods, normal interframes resume at the XGMII, the PHY
PHY, causing it to also exit the LPI mode.
Change Table 71-1 by inserting a new row at the end of the table:
Table 711PHY (Physical Layer) clauses associated with the 10GBASE-KX4 PMD
Associated clause 10GBASE-KX4
78EEE Optional
Insert the following at the end of 71.2:
The following primitives are defined on the PMD Service Interface when EEE is supported:
These messages are defined for the PCS in 48.2.6.1.6.
71.2.1 PMD_RXQUIET.request
signal is quiet and the PMA and PMD receiver may go into a low power mode. When EEE is not supported,
the primitive is never invoked and the PMD behaves as if rx_quiet = FALSE.
PMD_RXQUIET.request (rx_quiet)
The rx_quiet parameter takes on one of two values: TRUE or FALSE.
This variable is from the Receive process of the PCS to control the power-saving function of the local
receiver. The 10GBASE-KX4 PHY receiver should put unused functional blocks into a low power state to
save energy.
71.2.2 PMD_TXQUIET.request
and PMD transmit functions may go into a low power mode and to disable the PMD transmitter. When EEE
is not supported, the primitive is never invoked and the PMD behaves as if tx_quiet = FALSE.
PMD_TXQUIET.request (tx_quiet)
The tx_quiet parameter takes on one of two values: TRUE or FALSE.
The PCS generates this primitive to request the appropriate PMD transmit LPI state.
This primitive affects operation of the PMD Transmit disable function as described in 71.6.6. The
10GBASE-KX4 PHY transmitter should put unused functional blocks into a lower power state to save
energy.
71.6.4 Global PMD signal detect function
For 10GBASE-KX4 operation Global PMD signal detect is mandatory if EEE is supported. When EEE is
not implemented, the PMD signal detect is optional and its definition is beyond the scope of this standard.
When Global PMD signal detect is not implemented, the value of SIGNAL_DETECT shall be set to OK for
purposes of management and signaling of the primitive.
If EEE is supported, a local PMD signal detect function shall report to the PMD service interface using the
message PMD_SIGNAL.indication(SIGNAL_DETECT). This message is signaled continuously. For EEE,
the SIGNAL_DETECT parameter can take on one of two values, OK or FAIL, indicating whether the PMD
is detecting electrical energy at the receiver (OK) or not (FAIL). When SIGNAL_DETECT = FAIL,
PMD_UNITDATA.indication(rx_lane<3:0>) is undefined. The signal energy from a compliant transmitter
shall set SIGNAL_DETECT to OK within 750 ns when transitioning from LPI quiet to active and set
SIGNAL_DETECT to FAIL within 750 ns when transitioning from active to LPI quiet.
71.6.6 Global PMD transmit disable function
The Global_PMD_transmit_disable function is mandatory if EEE is supported and is otherwise optional.

When implemented for normal operation, it allows all of the transmitters to be disabled with a single
variable.
a) When the Global_PMD_transmit_disable variable is set to ONE, this function shall turn off all of
the transmitters such that each transmitter drives a constant level (i.e., no transitions) and does not
exceed the maximum differential peak-to-peak output voltage specified in Table 714.
b) If a PMD_fault (71.6.9) is detected, then the PMD may turn off the electrical transmitter in all lanes.
c) Loopback, as defined in 71.6.8, shall not be affected by Global_PMD_transmit_disable.
d) For EEE capability, the PMD_transmit_disable function shall turn off all transmitter lanes after
tx_quiet is asserted within a time and voltage level specified in 71.7.1.4. The PMD_transmit_disable
function shall turn on all transmitter lanes after tx_quiet is de-asserted within a time and voltage
level specified in 71.7.1.4.
Insert the following new subclause 71.6.12 after 71.6.11:
71.6.12 PMD LPI function
The PMD LPI function responds to transitions between Active, Sleep, Quiet, Refresh, and Wake states via
the PMD_TXQUIET and PMD_RXQUIET requests. Implementation of the function is optional. EEE
capabilities and parameters, as described in 45.2.7, is advertised during the Backplane Auto-negotiation. The
transmitter on the local device will inform the link partners receiver when to sleep, refresh, and wake. The
local receiver transitions are controlled by the link partners transmitter and can change independent of the
local transmitter states and transitions.
The transmitter sends /LI/ ordered sets during the sleep and refresh states, disables the transmitter during
quiet, and forwards ||I|| during the wake phase.
If EEE is supported, the PMD transmit function enters into a low power mode when tx_quiet is set to TRUE
and exits when tx_quiet is set to FALSE. While tx_quiet is TRUE the PMD transmitter functional blocks
should be deactivated to conserve energy. The PMD receive function enters into a low power mode when
rx_quiet is set to TRUE and exits when rx_quiet is set to FALSE. While rx_quiet is TRUE the PMD receiver
functional blocks should be deactivated to conserve energy.
71.7 Electrical characteristics for 10GBASE-KX4
Change Table 71-4 by inserting a row as follows:
Table 714Transmitter characteristics for 10GBASE-KX4
Subclause
reference
Signaling speed, per lane 71.7.1.3 3.125 100 ppm GBd
Differential peak-to-peak output voltage 71.7.1.4 800 to 1200 mV
71.6.6,
Differential peak-to-peak output voltage (max.) with TX disabled 30 mV
71.6.7
Common-mode voltage limits 71.7.1.4 0.4 to 1.9 V
[See Equation (711)

and Equation (712)]
[See Figure 715 and

Differential output template 71.7.1.6 V
Table 715]
Transition timea (20%-80%) 71.7.1.7 60 to 130 ps
Output jitter (max. peak-to-peak)

Random jitter 0.27 UI
71.7.1.8
Deterministic jitter 0.17 UI
Total jitterb 0.35 UI
aTransition time
parameters are recommended values, not compliance values.
b
At BER 1012.
71.7.1.4 Output amplitude
For EEE capability, the transmitter lanes differential peak-to-peak output voltage shall be less than 30 mV
within 500 ns of tx_quiet being asserted. Furthermore, the transmitter lanes differential peak-to-peak output
voltage shall be greater than 720 mV within 500 ns of tx_quiet being de-asserted. The transmitter output
shall be fully compliant within 5 s after tx_quiet is set to FALSE. During LPI, the common mode shall be
maintained to within 150 mV of the pre-LPI value.
71.7.2 Receiver characteristics
Change Table 71-6 by inserting two rows as follows:
Table 716Receiver characteristics
Subclause
reference
Bit error ratio 71.7.2.1 1012
Signaling speed, per lane 71.7.2.2 3.125 100 ppm GBd
Unit interval (UI) nominal 71.7.2.2 320 ps
Receiver coupling 71.7.2.3 AC
Differential input peak-to-peak amplitude (maximum) 71.7.2.4 1600 mV
EEE Signal Detect deactivation time (TSD) from active

71.6.4a 750 ns
to LPI quiet
EEE Signal Detect activation time (TSA) from LPI

71.6.4a 750 ns
quiet to active
[See Equation (711)

Differential input return lossa (minimum) 71.7.2.5 dB
and Equation (712)]
aRelative
to 100 differential.

type 10GBASE-KX419
LPI LPI function 71.6.10 LPI supported O Yes [ ]

No [ ]
19
and baseband medium, type 10GBASE-KX4
Insert the following rows into the table in 71.10.4.2:
FS9a Global_PMD_signal_detect 71.6.4 Detect signal energy during LPI LPI:M Yes [ ]
during LPI N/A [ ]
FS9b Signal Detect for EEE 71.6.4 Transition timing to set LPI:M Yes [ ]
FS12a Global_PMD_transmit_disable 71.6.6 Disable transmitters during LPI:M Yes [ ]

during LPI tx_quiet N/A [ ]
FS18 LPI function 71.6.12 PMD_RXQUIET.request and LPI:M Yes [ ]

PMD_TXQUIET.request No [ ]
supported N/A [ ]
TC6a Output Amplitude LPI voltage 71.7.1.4 Less than 30 mV within 500 ns LPI:M Yes [ ]
of tx_quiet N/A [ ]
TC6b Output Amplitude ON voltage 71.7.1.4 Greater than 720 mV within LPI:M Yes [ ]
500 ns of tx_quiet de-asserted N/A [ ]

10GBASE-KR
72.1 Overview
Insert a new row in Table 72-1 at the end of the table:
Table 721PHY (Physical Layer) clauses associated with the 10GBASE-KR PMD
Associated clause 10GBASE-KR
78Energy-Efficient Ethernet Optional
A 10GBASE-KR PHY with the optional Energy-Efficient Ethernet (EEE) capability may optionally enter
request at the XGMII is encoded in the transmitted symbols. Detection of LPI signaling in the received
symbols is indicated as Assert LPI at the XGMII. Upon the detection of Assert LPI at the XGMII, an
energy-efficient 10GBASE-KR PHY continues transmitting for a predefined period, then ceases
characteristics. If, during the quiet or refresh periods, normal interframes resume at the XGMII, the PHY
PHY, causing it to also exit the LPI mode.
Change existing 72.2 and insert new subclauses 7.2.1 through 7.2.2.3 at the end of 7.2.2 as follows:
The 10GBASE-KR GMD utilizes the PMD service interface defined in 52.1.1. The PMD service interface is
summarized as follows:
a) PMD_UNITDATA.request (as defined in 52.1.1)

b) PMD_UNITDATA.indication (as defined in 52.1.1)
c) PMD_SIGNAL.indication
If EEE is supported, the following primitives are also defined on the PMD Service Interface:
PMD_RX_MODE.request(rx_mode)
PMD_TX_MODE.request(tx_mode)
These messages are defined for the PCS in 49.2.13.2.6.
72.2.1 PMD_RX_MODE.request
signal is quiet and the PMA and PMD receiver may go into a low power mode. When EEE is not supported,
the primitive is never invoked and the PMD behaves as if rx_mode = DATA.
PMD_RX_MODE.request (rx_mode)
The rx_mode parameter takes on one of two values: QUIET or DATA.
When rx_mode is QUIET, the PMD receive function may deactivate functional blocks to conserve energy.
When rx_mode is DATA, the PMD receive function operates normally.
72.2.2 PMD_TX_MODE.request
and PMD transmit functions may go into a low power mode and to disable the PMD transmitter. See
subclause 72.6.5. When EEE is not supported, the primitive is never invoked and the PMD behaves as if
tx_mode = DATA.
PMD_TX_MODE.request (tx_mode)
The tx_mode parameter takes on one of three values: QUIET, ALERT, or DATA.
The PCS generates this primitive to request appropriate PMD transmit LPI state.
When tx_mode is QUIET, the PMD Transmit function may deactivate functional blocks to conserve energy.
When tx_mode is ALERT, the PMD Transmit function transmits the alert pattern. And when it is DATA, the
PMD Transmit function operates normally.
72.6.2 PMD transmit function
Insert the following paragraph at the end of 72.6.2:
If the optional Energy-Efficient Ethernet (EEE) capability is supported (see Clause 78) then when tx_mode
is set to ALERT, the PMD will transmit a repeating 16-bit pattern, hexadecimal 0xFF00. When tx_mode is
ALERT, the transmitter equalizer taps are set to the preset state specified in 72.6.10.2.3.1. When tx_mode is
DATA, the driver coeffcients are restored to their states resolved during training.
72.6.4 PMD signal detect function
Change the text in 72.6.4 as follows:
The Global PMD signal detect function shall report to the PMD service interface, using the message
PMD_SIGNAL.indication(SIGNAL_DETECT), which is signaled continuously. PMD_SIGNAL.indication
is used by 10GBASE-KR to indicate the successful completion of the start-up protocol. When the PHY
supports the optional EEE capability, PMD_SIGNAL.indication is also used to indicate when the ALERT
signal is detected, which corresponds to the beginning of a refresh or a wake. PMD_SIGNAL.indication,
while normally intended to be an indicator of signal presence, is used by 10GBASE-KR to indicate the
successful completion of the start-up protocol. If the MDIO interface is implemented, then
Global_PMD_signal_detect (1.10.0) shall be continuously set to the value of SIGNAL_DETECT as
described in 45.2.1.9.5.
The value of the SIGNAL_DETECT is defined by the training state diagram shown in Figure 725 when the
PHY does not support the EEE capability or if the PHY supports the EEE capability and rx_mode is set to
DATA. When the PHY supports the EEE capability, SIGNAL_DETECT is set to FAIL following a transition
from rx_mode = DATA to rx_mode = QUIET. When rx_mode = QUIET, SIGNAL_DETECT shall be set to
OK within 500 ns following the application of a signal at the receiver input that is the output of a channel
that satisfies the requirements of all the parameters of both interference tolerance test channels defined in
72.7.2.1 when driven by a square wave pattern with a period of 16 unit intervals and peak-to-peak
differential output amplitude of 720 mV. While rx_mode = QUIET, SIGNAL_DETECT changes from FAIL
to OK only after a valid ALERT signal is applied to the channel.
SIGNAL_DETECT shall be set to FAIL following system reset or the manual reset of the training state
diagram. Upon completion of training, SIGNAL_DETECT shall be set to OK.
If training is disabled by management and EEE is not implemented, SIGNAL_DETECT shall be set to OK.
Change the text in 72.6.5 as follows:
72.6.5 PMD transmit disable function
The Global_PMD_transmit_disable function is mandatory if EEE is supported and is otherwise optional.

When this function is supported, it shall meet the requirements of this subclause.
a) When the Global_PMD_transmit_disable variable is set to ONE, this function shall turn off the
transmitter such that it drives a constant level (i.e., no transitions) and does not exceed the maximum
differential peak-to-peak output voltage specified in Table 726.
b) If a PMD_fault (72.6.7) is detected, then the PMD may turn off the electrical transmitter.
c) Loopback, as defined in 72.6.6, shall not be affected by Global_PMD_transmit_disable.
d) For EEE capability, the PMD_transmit_disable function shall turn off the transmitter after tx_mode
is set to QUIET within a time and voltage level specified in 72.7.1.4. The PMD_transmit_disable
function shall turn on the transmitter after tx_mode is set to DATA or ALERT within the time and
voltage level specified in 72.7.1.4.
If the MDIO interface is implemented, then this function shall map to the Global_PMD_transmit_disable bit
as specified in 45.2.1.8.5.
72.6.10 PMD control function
72.6.10.1 Overview
If EEE is supported, the PMD control function responds to PCS requests to transition in and out of quiet
states.
Insert a new subclause 72.6.11 after 72.6.10 as follows:
72.6.11. PMD LPI function
The PMD LPI function responds to the transitions between Active, Sleep, Quiet, Refresh, and Wake states
via the PMD_TX_MODE and PMD_RX_MODE requests. Implementation of the function is optional. EEE
capabilities and parameters will be advertised during the Backplane Auto-negotiation, as described in
45.2.7.13. The transmitter on the local device will inform the link partners receiver when to sleep, refresh
and wake. The local receiver transitions are controlled by the link partners transmitter and can change
independent of the local transmitter states and transitions.
72.7 10GBASE-KR electrical characteristics
Change Table 72-6 by inserting a row as follows:
Table 726Transmitter characteristics for 10GBASE-KR
Subclause
reference
Signaling speed 72.7.1.3 10.3125 100 ppm GBd
Differential peak-to-peak output voltage (max.) 72.7.1.4 1200 mV
Differential peak-to-peak output voltage (max.) with TX disabled 72.6.5 30 mV
Common-mode voltage limits 72.7.1.4 01.9 V
[See Equation (724)

and Equation (725)]
[See Equation (726)

Common-mode output return loss (min.) 72.7.1.6 dB
and Equation (727)]
Transition time (20%80%) 72.7.1.7 2447 ps
Max output jitter (peak-to-peak)

Random jittera 0.15 UI
Deterministic jitter 72.7.1.8 0.15 UI
Duty Cycle Distortionb 0.035 UI
Total jitter 0.28 UI
aJitter
is specified at BER 1012.
b
Duty Cycle Distortion is considered part of the deterministic jitter distribution.
72.7.1.4 Output Amplitude
For EEE capability, the transmitters differential peak-to-peak output voltage shall be less than 30 mV
within 500 ns of tx_mode being set to QUIET and remain so while tx_mode is set to QUIET. Furthermore,
the transmitters differential peak-to-peak output voltage shall be greater than 720 mV within 500 ns of
tx_mode being set to ALERT. The transmitter output shall be fully compliant within 5 s after tx_mode is
set to DATA. During LPI mode, the common mode shall be maintained to within 150 mV of the pre-LPI
value.

type 10GBASE-KR20
Change the row for item FEC and insert a row for item LPI at the end of the table in 72.10.3:
FEC Forward Error Correction 72.1, 74 Device implements O Yes [ ]

10GBASE-R Forward Error No [ ]
Correction
LPI LPI 72.6.11 LPI O Yes [ ]

No [ ]
and baseband medium, type 10GBASE-KR
FS9a Signal detect during LPI 72.6.4 Detect signal energy during LPI LPI:M Yes [ ]
N/A[ ]
FS9b Signal detect for EEE 72.6.4 Transition timing to set LPI:M Yes [ ]
FS10a Transmit disable during LPI 72.6.5 Disable transmitter during LPI:M Yes [ ]
tx_mode = QUIET N/A[ ]
20
TC6a Output Amplitude LPI 72.7.1.4 Less than 30 mV within 500 ns LPI:M Yes [ ]
voltage of tx_quiet N/A [ ]
TC6b Output Amplitude ON 72.7.1.4 Greater than 90% of previous LPI:M Yes [ ]
voltage level within 500 ns of tx_quiet N/A [ ]
de-asserted
73. Auto-Negotiation for Backplane Ethernet

Clause 73, Auto-Negotiation for Backplane Ethernet21
73.11.4 PICS proforma tables for Auto-Negotiation for Backplane Ethernet
73.11.4.9 Auto-Negotiation annexes
Insert a new row at the end of the table in 73.11.4.9 as follows:
AN13 AN message code 10 73A.4 EEE technology message code M Yes [ ]
21
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
In 74.4.1, as modified by IEEE Std 802.3ba-2010, replace Figure 742 as follows:
Figure 742 shows the functional block diagram of FEC for 10BASE-R PHY and the relationship between
the PCS and PMA sublayers.
XGMII
TXD<31:0> RXD<31:0>
TXC<3:0> RXC<3:0>
TX_CLK PCS service interface RX_CLK
PCS PCS Transmit PCS Receive
Encode Decode
Scramble Descramble
Gearbox
BER & Sync Header Block Sync
LPI
Monitor
rx_data-group<15:0> FEC_TXMODE.request
tx_data-group<15:0> FEC_RXMODE.request
FEC_SIGNAL.indication FEC_LPIACTIVE.request
(EEE only)
FEC service interface FEC_ENERGY.indication
FEC sublayer
Reverse Gearbox & FEC Decoder &

FEC Encoder Block Synchronization
rx_data-group<15:0> PMA_TX_MODE.request
PMA_RX_MODE.request
tx_data-group<15:0> PMA_SIGNAL.indication
(EEE only)
PMA service interface PMA_ENERGY.indication
PMA sublayer
Figure 742Functional block diagram for 10GBASE-R PHYs
74.5 FEC service interface
74.5.1 10GBASE-R Service primitives

.
Change 74.5.1 by inserting list items d) through g) and the following text in 74.5.1 as shown:
The following primitives are defined within the FEC service interface:
a) FEC_UNITDATA.request(tx_data-group<15:0>)
b) FEC_UNITDATA.indication(rx_data-group<15:0>)
c) FEC_SIGNAL.indication(SIGNAL_OK)
d) FEC_TX_MODE.request(tx_mode)
e) FEC_RX_MODE.request(rx_mode)
f) FEC_ENERGY.indication(energy_detect)
g) FEC_LPI_ACTIVE.request(rx_lpi_active)
Items d), e), f), and g) are only required for the optional EEE capability.
The FEC service interface directly maps to the PMA service interface of the 10GBASE-R PCS defined in
Clause 49. The FEC_UNITDATA.request maps to the PMA_UNITDATA.request primitive, the
FEC_UNITDATA.indication maps to the PMA_UNITDATA.indication primitive, and the
FEC_SIGNAL.indication maps to the PMA_SIGNAL.indication primitive of the 10GBASE-R PCS.
If the optional Energy-Efficient Ethernet (EEE) capability is supported (see Clause 78) then the interface
with the PMA sublayer (or FEC sublayer) includes rx_mode and tx_mode to control power states in lower
sublayers and energy_detect that indicates whether the PMD sublayer has detected a signal at the receiver.
74.5.1.3 FEC_SIGNAL.indication
Insert new subclauses 74.5.1.4 through 74.5.1.7 after 74.5.1.3 as follows:
74.5.1.4 FEC_ENERGY.indication (optional)
FEC_ENERGY.indication(energy_detect)
A Boolean variable that reflects the value of the energy detection primitive PMA_ENERGY.indication.
The effect of receipt of this primitive by the FEC client is unspecified by the FEC sublayer.
74.5.1.5 FEC_LPI_ACTIVE.request (optional)
FEC_LPI_ACTIVE.request(rx_lpi_active)
The rx_lpi_active parameter is a Boolean variable sent from the PCS that is set to TRUE when LPI mode is
active at the receiver and set to FALSE otherwise.
The generation of this primitive by the FEC client is unspecified by the FEC sublayer.
When rx_lpi_active is TRUE, rapid block lock as specified in 74.7.4.8 will be used to quickly determine the
start of the FEC block during EEE REFRESH or WAKE. When rx_lpi_active is FALSE, rapid block lock
will not be used.
74.5.1.6 FEC_RX_MODE.request (optional)
FEC_RX_MODE.request(rx_mode)
The rx_mode parameter is a variable sent from the PCS. It is set to QUIET while the receiver is in the
RX_QUIET state and is set to DATA otherwise.
When rx_mode is QUIET, the FEC decoder logic may deactivate functional blocks to conserve energy.
When rx_mode is DATA, the FEC decoder logic operates normally. The value rx_mode is passed to the
client layer through PMA_RX_MODE(rx_mode).request.
74.5.1.7 FEC_TX_MODE.request (optional)
FEC_TX_MODE.request(tx_mode)
The tx_mode parameter is a variable sent from the PCS. It is set to QUIET while the transmitter is in the
TX_QUIET state, it is set to ALERT while the transmitter is in the TX_ALERT state and is set to DATA
otherwise.
When tx_mode is QUIET or ALERT, the FEC encoder logic may deactivate functional blocks to conserve
energy. When tx_mode is DATA, the FEC encoder logic operates normally. The value tx_mode is passed to
the client layer through PMA_TX_MODE(tx_mode).request.
74.7 FEC principle of operation
74.7.4 Functions within FEC sublayer
74.7.4.7 FEC block synchronization
Insert new subclause 74.7.4.8 after 74.7.4.7 as follows:
74.7.4.8 FEC rapid block synchronization for EEE (optional)
If the optional EEE capability is supported then during the wake and refresh states the FEC decoder will be
receiving one of the two types of deterministic blocks to achieve rapid block synchronization. During these
states the reverse gearbox of the remote FEC encoder will be receiving unscrambled data from the PCS
sublayer via 16-bit FEC_UNITDATA.request primitive. PCS sublayer will be encoding /I/ during the wake
state and /LI/ during the refresh state, which produces the two types of deterministic FEC blocks.
When rx_lpi_active is TRUE and rx_mode is set to DATA, start a hold-off timer whose duration is greater
than or equal to 13.7 s and enable the FEC Rapid block lock mechanism, which will attempt to determine
the FEC start of block location based on the deterministic pattern. When the rapid block lock is locked, the
determined start of block location is used as the FEC lock state diagram candidate start of block location
until the rapid block lock loses lock. Assuming the rapid block lock determined the correct start of block
location, the FEC lock state diagram will achieve lock without requiring subsequent slips. The rapid block
lock mechanism is implementation dependent and outside the scope of this standard. The FEC sublayer shall
hold off asserting SIGNAL_OK until one of the following two events occurs:
1) Two 65b payload blocks after the transition from deterministic FEC block to normal scrambled FEC
block
2) Expiration of the hold-off timer
74.8 FEC MDIO function mapping
74.8.4 FEC Error monitoring capability
Insert a sentence after the first paragraph in 74.8.4 as follows:
The following counters apply to FEC sublayer management and error monitoring. If an MDIO interface is
provided (see Clause 45), it is accessed via that interface. If not, it is recommended that an equivalent access
be provided. These counters are reset to zero upon read or upon reset of the FEC sublayer. When a counter
reaches all ones, it stops counting. The counters purpose is to help monitor the quality of the link.
These counters shall be disabled if FEC_LPI_ACTIVE.request(rx_lpi_active) is TRUE.
74.10 Detailed functions and state diagrams
74.10.2.3 Functions
Delete the third paragraph of 74.10.2.3 as follows:
T_TYPE_NEXT
Prescient end of packet check function. It returns the FRAME_TYPE of the tx_raw vector
immediately following the current tx_raw vector.

Clause 74, Forward Error Correction (FEC) sublayer for BASE-R PHYs22
Insert a new row into the table in 74.11.3 after the last row as follows:
EEE Rapid Block Lock 74.7.4.8 Device implements Rapid O Yes[]/

block lock mechanism to No[]
support EEE
74.11.6 FEC Error Monitoring
Insert a new row into the table in 74.11.6 after the last row as follows:
FEM4 FEC Error Monitoring during 74.8.4 Disables FEC Error Monitoring EEE:M Yes[]
EEE during EEE as specified in
74.8.4
22
Insert a new Clause 78 after Clause 77 as follows:
78. Energy-Efficient Ethernet (EEE)
78.1 Overview
The optional EEE capability combines the IEEE 802.3 Media Access Control (MAC) Sublayer with a
family of Physical Layers defined to support operation in the Low Power Idle (LPI) mode. When the LPI
mode is enabled, systems on both sides of the link can save power during periods of low link utilization.
EEE also provides a protocol to coordinate transitions to or from a lower level of power consumption and
does this without changing the link status and without dropping or corrupting frames. The transition time in
to and out of the lower level of power consumption is kept small enough to be transparent to upper layer
protocols and applications.
For operation over twisted-pair cabling systems, EEE supports the 100BASE-TX PHY, the 1000BASE-T
PHY, and the 10GBASE-T PHY. For operation over electrical backplanes, EEE supports the 1000BASE-KX
PHY, the 10GBASE-KX4 PHY, and the 10GBASE-KR PHY. EEE also supports XGMII extension using the
XGXS for 10 Gb/s PHYs.
In addition to the above, EEE defines a 10 Mb/s MAU (10BASE-Te) with reduced transmit amplitude
requirements. The 10BASE-Te MAU is fully interoperable with 10BASE-T MAUs over 100 m of class D
(Category 5) or better cabling as specified in ISO/IEC 11801:1995. These requirements can also be met by
Category 5 cable and components as specified in ANSI/TIA/EIA-568-B-1995. The definition of 10BASE-
Te allows a reduction in power consumption.
EEE also specifies means to exchange capabilities between link partners to determine whether EEE is
supported and to select the best set of parameters common to both devices. Clause 78 provides an overview
of EEE operation. PICS for the optional EEE capability for each specific PHY type are specified in the
respective PHY clauses. Normative requirements for Data Link Layer capabilities are contained in 78.4.
78.1.1 LPI Signaling
LPI signaling allows the LPI Client to indicate to the PHY, and to the link partner, that a break in the data
stream is expected, and the LPI Client can use this information to enter power-saving modes that require
additional time to resume normal operation. LPI signaling also informs the LPI Client when the link partner
has sent such an indication.
The definition of LPI signaling assumes the use of the MAC defined in Annex 4A for simplified full duplex
operation (with carrier sense deferral). This provides full duplex operation but uses the carrier sense signal
to defer transmission when the PHY is in the LPI mode.
78.1.1.1 Interlayer service interfaces
Figure 781 depicts the LPI Client and the RS interlayer service interfaces.
Low Power
Media Access Control (MAC)
Idle (LPI) Client
LP_IDLE.request PLS_DATA.request PLS_SIGNAL.indication PLS_CARRIER.indication
LP_IDLE.indication PLS_DATA.indication PLS_DATA_VALID.indication

Low Power Physical Layer
Idle (LPI) Client Signaling (PLS)
service service
interface interface
Reconciliation Sublayer (RS)
xMII
PHY
Figure 781LPI Client and RS interlayer service interfaces
78.1.1.2 Responsibilities of LPI Client
The decision on when to signal LPI to the link partner is made by the LPI Client and communicated to the
PHY through the RS. The LPI Client is also informed when the link partner is signaling LPI by the RS.
The conditions under which the LPI Client decides to send LPI, and what action are taken by the LPI Client
when it receives LPI from the link partner, are implementation specific and beyond the scope of this
standard.
78.1.2 LPI Client service interface
The following specifies the service interface provided by the RS to the LPI Client. These services are
described in an abstract manner and do not imply any particular implementation.
The following primitives are defined:
LP_IDLE.request
LP_IDLE.indication
78.1.2.1 LP_IDLE.request
78.1.2.1.1 Function
A primitive used by the LPI Client to start or stop the signaling of LPI to the link partner.
The semantics of the service primitive are as follows:
LP_IDLE.request (LPI_REQUEST)
The LPI_REQUEST parameter can take one of two values: ASSERT or DE-ASSERT. ASSERT initiates the
signaling of LPI to the link partner. DE-ASSERT stops the signaling of LPI to the link partner. The effect of
receipt of this primitive is undefined in any of the following cases:
a) link_status is not OK (see 28.2.6.1.1)

b) LPI_REQUEST=ASSERT within 1 s of the change of link_status to OK
c) The PHY is indicating LOCAL FAULT
d) The PHY is indicating REMOTE FAULT
Specification of the time when this primitive is generated by the LPI client is out of the scope of this
standard.
The receipt of this primitive will cause the RS to start or stop signaling LPI to the link partner.
78.1.2.2 LP_IDLE.indication
78.1.2.2.1 Function
A primitive that is used to indicate to the LPI Client that the link partner has started or stopped signaling
LPI.
The semantics of the service primitive are as follows:
LP_IDLE.indication (LPI_INDICATION)
The LPI_INDICATION parameter can take one of two values: ASSERT or DE-ASSERT. ASSERT indicates
that the link partner has started signaling LPI. DE-ASSERT indicates that the link partner has stopped
signaling LPI.
This primitive is generated by the PHY when it receives an LPI signal or a wake signal from its link partner.
The effect of receipt of this primitive by the LPI client is unspecified.
78.1.3 Reconciliation sublayer operation
LPI assert and detect functions are contained in the Reconciliation Sublayer as shown in Figure 782. The
xMII interface in this diagram represents any of the family of medium independent interfaces supported by
EEE.
Reconciliation Sublayer
Physical Layer Signaling
(PLS)
xMII
PLS_DATA.request transmit signals
LPI
PLS_CARRIER.indication assert function
PLS_DATA.indication
xMII
PLS_DATA_VALID.indication receive signals
LPI
PLS_SIGNAL.indication detect function
LPI Client
service interface
LP_IDLE.request
LP_IDLE.indication
Figure 782RS LPI assert and detect functions
The following provides an overview of RS LPI operation. The actual specification of RS LPI operation can
be found in the respective RS clauses.
78.1.3.1 RS LPI assert function
In the absence of an LPI request, indicated by the LPI_REQUEST parameter set to DE-ASSERT in the
LP_IDLE.request primitive of the LPI Client interface, the LPI assert function maps the PLS service
interface to the transmit xMII signals as under normal conditions.
When an LPI request is asserted, indicated by the LPI_REQUEST parameter set to ASSERT in the
LP_IDLE.request primitive of the LPI Client interface, the LPI assert function starts to transmit the
Assert LPI encoding on the xMII. The LPI assert function also sets the CARRIER_STATUS parameter to
CARRIER_ON in the PLS_CARRIER.indication primitive of the PLS service interface. This will prevent
the MAC from transmitting.
When the LPI request is de-asserted, indicated by the LPI_REQUEST parameter set to DE-ASSERT in the
LP_IDLE.request primitive of the LPI Client interface, the LPI assert function starts to transmit the
normal interframe encoding on the xMII. After a delay, the LPI assert function sets the CARRIER_STATUS
parameter to CARRIER_OFF in the PLS_CARRIER.indication primitive of the PLS service interface,
allowing the MAC to start transmitting again. This delay is provided to allow the link partner to prepare for
normal operation. This delay has a PHY dependent default value but this value can be adjusted using the
Data Link Layer capabilities defined in 78.4.
78.1.3.2 LPI detect function
In the absence of LPI, indicated by an encoding other than Assert LPI on the receive xMII, the LPI detect
function maps the receive xMII signals to the PLS service interface as under normal conditions.
At the start of LPI, indicated by the transition from normal interframe encoding to the Assert LPI
encoding on the receive xMII, the LPI detect function continues to indicate idle on the PLS service interface,
but sets LP_IDLE.indication(LPI_INDICATION) to ASSERT.
At the end of LPI, indicated by the transition from the Assert LPI encoding to any other encoding on the
receive xMII, LP_IDLE.indication(LPI_INDICATION) is set to DE-ASSERT and the RS receive function
resumes normal decode operation.
78.1.3.3 PHY LPI operation
The following provides an overview of PHY LPI operation. The specification of PHY LPI operation can be
found in the respective PHY clauses (see Table 781).
78.1.3.3.1 PHY LPI transmit operation
When the start of Assert LPI encoding on the xMII is detected, the PHY signals sleep to its link partner to
indicate that the local transmitter is entering LPI mode.
The EEE capability in most PHYs (for example, 100BASE-TX, 10GBASE-T, 1000BASE-KX, 10GBASE-
KR, and 10GBASE-KX4) requires the local PHY transmitter to go quiet after sleep is signalled.
In the 1000BASE-T LPI mode, the local PHY transmitter goes quiet only after the local PHY signals sleep
and receives a sleep signal from the remote PHY. If the remote PHY chooses not to signal LPI, then neither
PHY can go into a low power mode; however, LPI requests are passed from one end of the link to the other
regardless and system energy savings can be achieved even if the PHY link does not go into a low power
mode.
The transmit function of the local PHY is enabled periodically to transmit refresh signals that are used by the
link partner to update adaptive filters and timing circuits in order to maintain link integrity.
This quiet-refresh cycle continues until the reception of the normal interframe encoding on the xMII. The
transmit function in the PHY communicates this to the link partner by sending a wake signal for a predefined
period of time. The PHY then enters the normal operating state.
Figure 783 illustrates general principles of the EEE-capable transmitter operation.
Active Low-Power Idle Active

Refresh
Refresh
Active
Active
Sleep
Wake
Quiet Quiet Quiet
Ts Tq Tr
Figure 783Overview of EEE LPI operation
No data frames are lost or corrupted during the transition to or from the LPI mode.
78.1.3.3.2 PHY LPI receive operation
In the receive direction, entering the LPI mode is triggered by the reception of a sleep signal from the link
partner, which indicates that the link partner is about to enter the LPI mode. After sending the sleep signal,
the link partner ceases transmission. When the receiver detects the sleep signal, the local PHY indicates
Assert LPI on the xMII and the local receiver can disable some functionality to reduce power
consumption.
The link partner periodically transmits refresh signals that are used by the local PHY to update adaptive
coefficients and timing circuits. This quiet-refresh cycle continues until the link partner initiates transition
back to normal mode by transmitting the wake signal for a predetermined period of time controlled by the
LPI assert function in the RS. This allows the local receiver to prepare for normal operation and transition
from the Assert LPI encoding to the normal interframe encoding on the xMII. After a system specified
recovery time, the link supports the nominal operational data rate.
78.1.4 EEE Supported PHY types
EEE defines a low power mode of operation for the IEEE 802.3 PHYs listed in Table 781. The table also
lists the clauses associated with each PHY. Normative requirements for the EEE capability for each PHY
type are in the associated clauses.
Table 781Clauses associated with each PHY type
PHY type Clause
10BASE-Te 14
100BASE-TX 24, 25
1000BASE-T 40
XGXS (XAUI) 47
1000BASE-KX 70, 35
10GBASE-T 55
10GBASE-KX4 71, 48
10GBASE-KR 72, 51, 49
78.2 LPI mode timing parameters description
Ts The period of time that the PHY transmits the sleep signal before turning all
transmitters off
Tq The period of time that the PHY remains quiet before sending the refresh signal
Tr Duration of the refresh signal
Tphy_prop_tx The propagation delay of a given unit of data from the xMII to the MDI
Tphy_prop_rx The propagation delay of a given unit of data from the MDI to the xMII
Tphy_shrink_tx Transmitter shrinkage time, defined as the absolute time difference between the
following two timing parameters:
Delay between a transition from the Assert LPI to Normal Idle at the xMII
interface and the corresponding start of the wake signal at the MDI
Tphy_prop_tx
Tphy_shrink_rx Receiver shrinkage time, defined as the absolute time difference between the
following two timing parameters:
Delay between start of the wake signal at the MDI and the corresponding transition
from Assert LPI to Normal Idle at the xMII
Tphy_prop_rx
Tw_phy Parameter employed by the system that corresponds to the behavior of the PHY. It is
the period of time between reception of an IDLE signal on the xMII interface and
when the first data codewords are permitted on the xMII interface. The wake time of a
compliant PHY does not exceed Tw_phy (min).
Tw_sys_tx Parameter employed by the system that corresponds to its requirements. It is the
longest period of time the system has to wait between a request to transmit and its
readiness to transmit.
Tw_sys_rx Parameter employed by the system that corresponds to its requirements. It is the
minimum time required by the system between a request to wake and its readiness to
receive data.
Table 782 summarizes three key EEE parameters (Ts, Tq, and Tr) for supported PHYs.
Table 782Summary of the key EEE parameters for supported PHY
Ts Tq Tr
(s) (s) (s)
Protocol
Min Max Min Max Min Max
100BASE-TX 200 220 20 000 22 000 200 220
1000BASE-T 182.0 202.0 20 000 24 000 198.0 218.2
1000BASE-KX 19.9 20.1 2 500 2 600 19.9 20.1
XGXS (XAUI) 19.9 20.1 2 500 2 600 19.9 20.1
10GBASE-KX4 19.9 20.1 2 500 2 600 19.9 20.1
10GBASE-KR 4.9 5.1 1 700 1 800 16.9 17.5
10GBASE-T 2.88 3.2 39.68 39.68 1.28 1.28
Figure 784 illustrates the relationship between the LPI mode timing parameters and the minimum system
wake time.
78.3 Capabilities Negotiation
The EEE capability shall be advertised during the Auto-Negotiation stage. Auto-Negotiation provides a
linked device with the capability to detect the abilities (modes of operation) supported by the device at the
other end of the link, determine common abilities, and configure for joint operation. Auto-Negotiation is
performed at power up, on command from management, due to link failure, or due to user intervention.
During Auto-Negotiation, both link partners indicate their EEE capabilities. EEE is supported only if during
Auto-Negotiation both the local device and link partner advertise the EEE capability for the resolved PHY
type. If EEE is not supported, all EEE functionality is disabled and the LPI client does not assert LPI. If EEE
is supported by both link partners for the negotiated PHY type, then the EEE function can be used
independently in either direction.
Tw_sys_tx
Idle
TX xMII Assert low power Idle Idle Data Idle
Tphy_wake_tx T phy_prop_tx
Idle
Medium Sleep LPI Wake Data Idle
Tphy_wake
Tphy_wake_rx Tphy_prop_rx
RX xMII Data Idle Assert low power Idle Idle Data
Tw_sys_rx
Tw_sys_tx (min) = Tw_sys_rx (min) + Tphy_shrink_tx (max) + Tphy_shrink_rx (max)

Tw_phy (min) = Tphy_wake (min) + Tphy_shrink_tx
Tw_sys_res (min) is greater of Tw_sys_tx (min) and Tw_phy (min)
Tphy_shrink_tx (max) = (Tphy_wake_tx (max) Tphy_prop_tx (min))
Tphy_shrink_rx (max) = (Tphy_wake_rx(max) Tphy_prop_rx (min))
where
Tphy_wake_tx = xMII start of wake to MDI start of wake delay
Tphy_prop_tx = xMII to MDI data propagation delay
Tphy_wake_rx = MDI start of wake to xMII start of wake delay
Tphy_prop_rx = MDI to xMII data propagation delay
Tphy_wake = Minimum wake duration required by PHY
Figure 784LPI mode timing parameters and their relationship to

minimum system wake time
Additional capabilities and settings using L2 protocol frames, including the adjustment of the Tw_sys_tx
parameter, are described in 78.4.
78.4 Data Link Layer Capabilities
Additional capabilities and settings are supported using frames based on the IEEE 802.3 Organizationally
Specific TLVs are defined in Annex F of IEEE Std 802.1AB-2009. Devices that require longer wake-up
times prior to being able to accept data on their receive paths may use the Data Link Layer capabilities
defined in this subclause to negotiate for extended system wake-up times from the transmitting link partner.
This mechanism may allow for more or less aggressive energy saving modes.
The Data Link Layer capabilities shall be implemented for devices with an operating speed equal to or
greater than 10 Gb/s and may be implemented for all other devices.
Implementations that use the Data Link Layer capabilities shall comply with all mandatory parts of
IEEE Std 802.1AB-2009; shall support the EEE Type, Length, Value (TLV) defined in 79.3.5; timing
requirement in 78.4.1; and shall support the control state diagrams defined in 78.4.2.
The Data Link Layer capabilities are described from a unidirectional perspective on the link between
transmitting and receiving link partners. For duplex EEE links that implement the Data Link Layer
capabilities, each link partner shall implement the TLV, control and state diagrams for a transmitter as well
as a receiver.
For purposes of Data Link Layer capabilities, all values that are negotiated and/or exchanged that have a
fractional value shall be rounded up to the nearest integer number in microseconds.
78.4.1 Data Link Layer capabilities timing requirements
An EEE link partner shall send an LLDPDU containing an EEE TLV within 10 s of the Link Layer
capability exchange being enabled when both the variables dll_enabled and dll_ready are asserted.
An LLDPDU containing an EEE TLV with an updated value for the Echo Transmit Tw_sys_tx field shall be
sent within 10 s of receipt of an LLDPDU containing an EEE TLV where the value of Transmit Tw_sys_tx
field is different from the previously communicated value.
An LLDPDU containing an EEE TLV with an updated value for the Echo Receive Tw_sys_tx field shall be
sent within 10 s of receipt of an LLDPDU containing an EEE TLV where the value of Receive Tw_sys_tx
field is different from the previously communicated value.
78.4.2 Control state diagrams
The control state diagrams for an EEE transmitting link partner and an EEE receiving link partner specify
the externally observable behavior of an EEE transmitting link partner and an EEE receiving link partner
implementing Data Link Layer capabilities respectively. EEE transmitting link partners implementing Data
Link Layer capabilities shall provide the behavior of the state diagram as shown in Figure 785. EEE
receiving link partners implementing Data Link Layer capabilities shall provide the behavior of the state
diagram as shown in Figure 786.
78.4.2.1 Conventions
The body of this subclause is comprised of state diagrams, including the associated definitions of variables,
constants, and functions. Should there be a discrepancy between a state diagram and descriptive text, the
state diagram prevails.
The notation used in the state diagrams follows the conventions of state diagrams as described in 21.5.
78.4.2.2 Constants
PHY WAKE VALUE

Integer (2 octets wide) representing the Tw_sys_tx (min) defined for the PHY that is in use for the
link. This parameter should be rounded up to the nearest integer number when it is calculated and
examined according to 78.2 and Table 784.
78.4.2.3 Variables
Unless otherwise specified, all integers are assumed to be 2 octets wide.
LocTxSystemValue
Integer that indicates the value of Tw_sys_tx that the local system can support. This value is updated
by the EEE DLL Transmitter state diagram. This variable maps into the aLldpXdot3LocTxTwSys
attribute.
RemTxSystemValueEcho
Integer that indicates the value Transmit Tw_sys_tx echoed back by the remote system. This value
maps from the aLldpXdot3RemTxTwSysEcho attribute.
LocRxSystemValue
Integer that indicates the value of Tw_sys_tx that the local system requests from the remote system.
This value is updated by the EEE Receiver L2 state diagram. This variable maps into the
aLldpXdot3LocRxTwSys attribute.
RemRxSystemValueEcho
Integer that indicates the value of Receive Tw_sys_tx echoed back by the remote system. This value
maps from the aLldpXdot3RemRxTwSysEcho attribute.
LocFbSystemValue
Integer that indicates the value of fallback Tw_sys_tx that the local system requests from the remote
system. This value is updated by the local system software.
RemTxSystemValue
Integer that indicates the value of Tw_sys_tx that the remote system can support. This value maps
from the aLldpXdot3RemTxTwSys attribute.
LocTxSystemValueEcho
Integer that indicates the remote systems Transmit Tw_sys_tx that was used by the local system to
compute the Tw_sys_tx that it wants to request from the remote system. This value maps into the
aLldpXdot3LocTxTwSysEcho attribute.
RemRxSystemValue
Integer that indicates the value of Tw_sys_tx that the remote system requests from the local system.
This value maps from the aLldpXdot3RemRxTwSys attribute.
LocRxSystemValueEcho
Integer that indicates the remote systems Receive Tw_sys_tx that was used by the local system to
compute the Tw_sys_tx that it can support. This value maps into the aLldpXdot3LocRxTwSysEcho
attribute.
LocResolvedTxSystemValue
Integer that indicates the current Tw_sys_tx supported by the local system.
LocResolvedRxSystemValue
Integer that indicates the current Tw_sys_tx supported by the remote system.
TempTxVar
Integer used to store the value of Tw_sys_tx.
TempRxVar
Integer used to store the value of Tw_sys_tx.
local_system_change
An implementation specific control variable that indicates that the local system wants to change
either the Transmit Tw_sys_tx or the Receive Tw_sys_tx.
tx_dll_ready
Data Link Layer ready: This variable indicates that the tx system initialization is complete and is
ready to update/receive LLDPDU containing EEE TLV. This variable is updated by the local
system software.
rx_dll_ready
Data Link Layer ready: This variable indicates that the rx system initialization is complete and is
ready to update/receive LLDPDU containing EEE TLV. This variable is updated by the local
system software.
NEW_TX_VALUE
Integer that indicates the value of Tw_sys_tx that the local system can support.
NEW_RX_VALUE
Integer that indicates the value of Tw_sys_tx that the local system wants the remote system to
support.
A summary of cross-references between the EEE object class attributes and the transmit and receive control
state diagrams, including the direction of the mapping, is provided in Table 783.
Table 783Attribute to state diagram variable cross-reference
Entity Object class Attribute Mapping State diagram variable
TX oLldpXdot3Loc- aLldpXdot3LocTxTwSys LocTxSystemValue

SystemsGroup
aLldpXdot3LocRxTwSysEcho LocRxSystemValueEcho
aLldpXdot3LocDllEnabled tx_dll_enabled
aLldpXdot3LocTxDllReady tx_dll_ready
oLldpXdot3Rem- aLldpXdot3RemRxTwSys RemRxSystemValue
SystemsGroup
aLldpXdot3RemTxTwSysEcho RemTxSystemValueEcho
RX oLldpXdot3Loc- aLldpXdot3LocRxTwSys LocRxSystemValue

SystemsGroup
aLldpXdot3LocTxTwSysEcho LocTxSystemValueEcho
aLldpXdot3LocFbTwSys LocFbSystemValue
aLldpXdot3LocDllEnabled rx_dll_enabled
aLldpXdot3LocRxDllReady rx_dll_ready
oLldpXdot3Rem- aLldpXdot3RemTxTwSys RemTxSystemValue
SystemsGroup
aLldpXdot3RemRxTwSysEcho RemRxSystemValueEcho
78.4.2.4 Functions
examine_Tx_change
This function computes the new value of Tw_sys_tx that the local system can support when there is
as updated request from the remote system or if local system conditions require a change in the
value of the presently supported Tw_sys_tx.
examine_Rx_change
This function computes the new value of Tw_sys_tx that the local system wants the remote system to
support. This function is called when the remote system wants to change its presently allocated
Tw_sys_tx or if local system conditions require a change in the value of Tw_sys_tx presently
supported by the remote system.
Control for placing data on the medium rests with the transmitting side, hence Tw_sys_tx is enforced by the
transmitter. For a given path between link partners (i.e., a transmitter and its associated receiver), the
transmitting link partner shall wait for the time indicated by the Transmit Tw_sys_tx after de-asserting LPI (at
the xMII) before sending data frames. The receiving link partner shall be ready to accept data based on its
echoed value of Transmit link partner's Tw_sys_tx. This ensures that the link partners transition out of LPI
mode and receive frames without loss or corruption.
The general state change procedure for transmitter is shown in Figure 785.
!tx_dll_enabled +
!tx_dll_ready
INITIALIZE
LocTxSystemValue PHY WAKE VALUE
RemTxSystemValueEcho PHY WAKE VALUE
RemRxSystemValue PHY WAKE VALUE
LocRxSystemValueEcho PHY WAKE VALUE
LocResolvedTxSystemValue PHY WAKE VALUE
TempRxVar PHY WAKE VALUE
tx_dll_ready
RUNNING
!local_system_change *
(RemRxSystemValue TempRxVar) * local_system_change
(LocTxSystemValue = RemTxSystemValueEcho)
REMOTE CHANGE LOCAL CHANGE

TempRxVar RemRxSystemValue TempRxVar RemRxSystemValue
examine_Tx_change examine_Tx_change
(LocTxSystemValue =
UCT RemTxSystemValueEcho) +
(NEW_TX_VALUE < LocTxSystemValue)
TX UPDATE
LocTxSystemValue NEW_TX_VALUE
(NEW_TX_VALUE (NEW_TX_VALUE LocTxSystemValue) *

LocResolvedTxSystemValue) + (LocTxSystemValue RemTxSystemValueEcho)
(NEW_TX_VALUE TempRxVar)
(NEW_TX_VALUE < LocResolvedTxSystem-

SYSTEM REALLOCATION Value)
* (NEW_TX_VALUE < TempRxVar)
LocResolvedTxSystemValue NEW_TX_VALUE
UCT
MIRROR UPDATE
LocRxSystemValueEcho TempRxVar
UCT
Figure 785EEE DLL Transmitter state diagram
The general state change procedure for receiver is shown in Figure 786.
!rx_dll_enabled +
!rx_dll_ready
INITIALIZE
LocRxSystemValue PHY WAKE VALUE
RemRxSystemValueEcho PHY WAKE VALUE
RemTxSystemValue PHY WAKE VALUE
LocTxSystemValueEcho PHY WAKE VALUE
LocResolvedRxSystemValue PHY WAKE VALUE
LocFbSystemValue PHY WAKE VALUE
TempTxVar PHY WAKE VALUE
rx_dll_ready
RUNNING
local_system_change +
RemTxSystemValue TempTxVar
CHANGE
TempTxVar RemTxSystemValue
examine_Rx_change
(NEW_RX_VALUE
LocResolvedRxSystemValue) +
(NEW_RX_VALUE > (NEW_RX_VALUE TempTxVar)
LocResolvedRxSystemValue) *
(NEW_RX_VALUE > TempTxVar)
SYSTEM REALLOCATION
LocResolvedRxSystemValue NEW_RX_VALUE
UCT
RX UPDATE
LocRxSystemValue NEW_RX_VALUE
UCT
UPDATE MIRROR
LocTxSystemValueEcho TempTxVar
UCT
Figure 786EEE DLL Receiver state diagram
78.4.3 State change procedure across a link
The transmitting and receiving link partners utilize the LLDP mechanism to advertise their various attributes
to the other entity.
The initial Tw_sys_tx defaults governing the EEE operation of the link default to the wake values required by
the PHYs. This provides for EEE operation and functionality on initialization and prior to the exchange and
processing of the TLVs.
The receiving link partner may request a new Tw_sys_tx value through the aLldpXdot3LocRxTwSys
(30.12.2.1.16) attribute in the LldpXdot3LocSystemsGroup managed object class (30.12.2). The request
appears to the transmitting link partner as a change to the aLldpXdot3RemRxTwSys (30.12.3.1.16) attribute
in the LldpXdot3RemSystemsGroup managed (30.12.3) object class. The transmitting link partner responds
to its receiving partners request through the aLldpXdot3LocTxTwSys (30.12.2.1.14) attribute in the
LldpXdot3LocSystemsGroup managed object class (30.12.2). The transmitting link partner also copies the
value of the aLldpXdot3RemRxTwSys (30.12.3.1.16) attribute in the LldpXdot3RemSystemsGroup
managed (30.12.3) object class to the aLldpXdot3LocRxTwSysEcho (30.12.2.1.17) attribute in the
LldpXdot3LocSystemsGroup managed object class (30.12.2).
The transmitting link partner may advertise new value of Tw_sys_tx through the aLldpXdot3LocTxTwSys
(30.12.2.1.14) attribute in the LldpXdot3LocSystemsGroup managed object class (30.12.2). This appears to
the receiving link partner as a change to the aLldpXdot3RemTxTwSys (30.12.3.1.14) attribute in the
LldpXdot3RemSystemsGroup managed (30.12.3) object class. The receiving link partner responds to a
transmitters request through the aLldpXdot3LocRxTwSys (30.12.2.1.16) attribute in the
LldpXdot3LocSystemsGroup managed object class (30.12.2). The receiving link partner also copies the
value of the aLldpXdot3RemTxTwSys (30.12.3.1.14) attribute in the LldpXdot3RemSystemsGroup
managed (30.12.3) object class to the aLldpXdot3LocTxTwSysEcho (30.12.2.1.15) attribute in the
LldpXdot3LocSystemsGroup managed object class (30.12.2). This appears to the transmitting link partner
as a change to the aLldpXdot3RemTxTwSysEcho (30.12.3.1.15) attribute in the
LldpXdot3RemSystemsGroup managed (30.12.3).
The state diagrams in Figure 785 and Figure 786 describe the preceding behavior.
78.4.3.1 Transmitting link partners state change procedure across a link
A transmitting link partner is said to be in sync with the receiving link partner if the presently advertised
value of Transmit Tw_sys_tx and the corresponding echoed value are equal.
During normal operation, the transmitting link partner is in the RUNNING state. If the transmitting link
partner wants to initiate a change to the presently resolved value of Tw_sys_tx, the local_system_change is
asserted and the transmitting link partner enters the LOCAL CHANGE state where NEW_TX_VALUE is
computed. If the new value is smaller than the presently advertised value of Tw_sys_tx or if the transmitting
link partner is in sync with the receiving link partner, then it enters TX UPDATE state. Otherwise, it returns
to the RUNNING state.
If the transmitting link partner sees a change in the Tw_sys_tx requested by the receiving link partner, it
recognizes the request only if it is in sync with the transmitting link partner. The transmitting link partner
examines the request by entering the REMOTE CHANGE state where a NEW TX VALUE is computed and
it then enters the TX UPDATE state.
Upon entering the TX UPDATE state, the transmitter updates the advertised value of Transmit Tw_sys_tx with
NEW_TX_VALUE. If the NEW_TX_VALUE is equal to or greater than either the resolved Tw_sys_tx value
or the value requested by the receiving link partner then it enters the SYSTEM REALLOCATION state
where it updates the value of resolved Tw_sys_tx with NEW_TX_VALUE. The transmitting link partner
enters the MIRROR UPDATE state either from the SYSTEM REALLOCATION state or directly from the
TX UPDATE state. The UPDATE MIRROR state then updates the echo for the Receive Tw_sys_tx and
returns to the RUNNING state.
78.4.3.2 Receiving link partners state change procedure across a link
A receiving link partner is said to be in sync with the transmitting link partner if the presently requested
value of Receive Tw_sys_tx and the corresponding echoed value are equal.
During normal operation, the receiving link partner is in the RUNNING state. If the receiving link partner
wants to request a change to the presently resolved value of Tw_sys_tx, the local_system_change is asserted.
When local_system_change is asserted or when the receiving link partner sees a change in the Tw_sys_tx
advertised by the transmitting link partner, it enters the CHANGE state where NEW_RX_VALUE is
computed. If NEW_RX_VALUE is less than either the presently resolved value of Tw_sys_tx or the presently
advertised value by the transmitting link partner, it enters the SYSTEM REALLOCATION state where it
updates the resolved value of Tw_sys_tx to NEW_RX_VALUE. The receiving link partner ultimately enters
the RX UPDATE state, either from the SYSTEM REALLOCATION state or directly from the CHANGE
state.
In the RX UPDATE state, it updates the presently requested value to NEW_RX_VALUE, then it updates the
echo for the Transmit Tw_sys_tx in the UPDATE MIRROR state and finally goes back to the RUNNING
state.
78.5 Communication link access latency
In the full duplex mode, predictable operation of the MAC Control PAUSE operation (Clause 31, Annex
31B) demands that there be an upper bound on the propagation delay through the network. This implies that
MAC, MAC Control sublayer, and PHY implementors conform to certain delay maxima, and that network
planners and administrators conform to constraints regarding the cable topology and the concatenation of
devices.
The EEE capability adds latency that has to be considered by the network designer. When in the LPI mode,
the PHY link is not available immediately for transmission of data. The system has to wake it up by sending
the normal IDLE code on the MAC interface. Following the reception of an IDLE code on the MAC
interface, the PHY starts the wake-up process. The maximal PHY recovery time, Tw_phy is defined for each
PHY.
Transmit and/or Receive wait time shrinkage can happen when Tphy_shrink_rx or Tphy_shrink_tx (as defined in
78.1.3) are not zero. This has to be taken into consideration in designing or configuring the network.
Table 784 summarizes critical timing parameters for supported PHYs. These are listed here to assist the
system designer in assessing the impact of EEE on the operation of the link.
Case-1 of the 1000BASE-T PHY applies to PHYs in Master mode. Case-2 of the 1000BASE-T PHY applies
to PHYs in Slave mode.
Case-1 of the 10GBASE-KR PHY applies to PHYs without FEC. Case-2 of the 10GBASE-KR PHY applies
to PHYs with FEC.
Case-1 of the 10GBASE-T PHY applies when the PHY is requested to transmit the Wake signal before
transmission of the Sleep signal to the Link Partner is complete. Case-2 of the 10GBASE-T PHY applies
when the PHY is requested to transmit the Wake signal after transmission of the Sleep signal to the Link
Partner is complete and if the PHY has not indicated LOCAL FAULT at any time during the previous 10 ms.
Table 784Summary of the LPI timing parameters for supported PHYs
Tw_sys_tx Tw_phy Tphy_shrink_tx Tphy_shrink_rx Tw_sys_rx

PHY Type Case (min) (min) (max) (max) (min)
(s) (s) (s) (s) (s)
100BASE-TX 30 20.5 5.0 15 10
Case-1 16.5 16.5 5.0 2.5 1.76

1000BASE-T
Case-2 16.5 16.5 12.24 9.74 1.76
1000BASE-KX 13.26 11.25 5.0 6.5 1.76
XGXS (XAUI) 12.38 9.25 5.0 4.5 2.88
Case-1 7.36 7.36 4.48 0 2.88

10GBASE-T
Case-2 4.48 4.48 1.6 0 2.88
10GBASE-KX4 12.38 9.25 5.0 4.5 2.88
Case-1 15.38 12.25 5.0 7.5 2.88

10GBASE-KR
Case-2 17.38 14.25 5.0 9.5 2.88
78.5.1 10 Gb/s PHY extension using XGXS
The XGXS can be inserted between the RS and a 10 Gb/s PHY to transparently extend the physical reach of
the XGMII. The LPI signaling can operate through the XGXS with no change to the PHY timing parameters
described in Table 784 or the operation of the Data Link Layer Capabilities negotiation described in 78.4.
If the DTE XS XAUI stop enable bit (5.0.9) is asserted, the DTE XS may stop signaling on the XAUI in the
transmit direction to conserve energy. If the DTE XS XAUI stop enable bit is asserted, the RS defers
sending data following deassertion of LPI by an additional time equal to Tw_sys_tx Tw_sys_rx for the XGXS
as shown in Table 784 (see 46.3a.2.1).
If the PHY XS XAUI stop enable bit (4.0.9) is asserted, the PHY XS may stop signaling on the XAUI in the
receive direction to conserve energy. The receiver negotiates an additional time for the remote Tw_sys equal
to Tw_sys_tx Tw_sys_rx for the XGXS as shown in Table 784 before setting the PHY XS XAUI stop enable
bit.
78.6 Protocol implementation conformance statement (PICS) proforma for EEE Data
Link Layer Capabilities23
78.6.1 Introduction
The supplier of a protocol implementation that is claimed to conform to 78.4 shall complete the following
protocol implementation conformance statement (PICS) proforma.
A detailed description of the symbols used in the PICS proforma, along with instructions for completing the
PICS proforma, can be found in Clause 21.
23
78.6.2.1 Implementation identification
Suppliera
Contact point for enquiries about the PICSa
Implementation Name(s) and Version(s)a, c
Other information necessary for full identification

e.g., name(s) and version(s) for machines and/or
operating systems; System Name(s)b
a
Required for all implementations
b
May be completed as appropriate
in meeting the requirements for the identification.
c
The terms Name and Version should be interpreted appropriately to correspond with a suppliers terminology
(e.g., Type, Series, Model).
78.6.2.2 Protocol summary
Identification of protocol standard IEEE Std 802.3az-2010, 78.4, EEE Data Link Layer
Capabilities
Identification of amendments and corrigenda to this

PICS proforma that have been completed as part of this
PICS
Have any Exception items been required? No [ ] Yes [ ]
(See Clause 21; the answer yes means that the implementation does not conform to IEEE Std 802.3az-2010,
Clause 78, including 78.4, EEE Data Link Layer Capabilities.)
Date of Statement
10G Support 10G or higher 78.4 Support for 10 Gb/s or higher O Yes [ ]
operation operation No [ ]
DLL1 DLL 78.4 DLL 10G:M Yes [ ]

N/A [ ]
DLL2 DLL 78.4 DLL !10G:O Yes [ ]

No [ ]
In addition, the following predicate name is defined for use when different implementations from the
preceding set have common parameters:
DLL = DLL1 OR DLL 2
78.6.4 DLL requirements
DLR1 DLL Timing 78.4.1 Timing requirements DLL:M Yes [ ]

N/A [ ]
DLR2 DLL Control state 78.4.2 State machines for TX and RX DLL:M Yes [ ]
diagrams N/A [ ]
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
Replace Table 79-1 with the following new table:
Table 791IEEE 802.3 Organizationally Specific TLVs
IEEE 802.3 subtype TLV name Subclause reference
1 MAC/PHY Configuration/Status 79.3.1
2 Power Via Medium Dependent Interface (MDI) 79.3.2
3 Link Aggregation (deprecated) 79.3.3
4 Maximum Frame Size 79.3.4
5 Energy-Efficient Ethernet 79.3.5
6255 Reserved
Insert the following subclause 79.3.5 after the last subclause in 79.3:
79.3.5 EEE TLV
The EEE TLV is used to exchange information about the EEE Data Link Layer capabilities. Figure 795a
shows the format of this TLV.
TLV TLV information 802.3 OUI 802.3 Transmit Receive

Tw Tw
type = 127 string length = 14 00-12-0F subtype = 5
...
7 bits 9 bits 3 octets 1 octet 2 octets 2 octets
TLV header TLV information string
Fallback Echo Echo

... Receive
Tw
Transmit
Tw
Receive
Tw
2 octets 2 octets 2 octets
TLV information string (contd)
Figure 795aEEE TLV format
79.3.5.1 Transmit Tw
Transmit Tw_sys_tx (2 octets wide) shall be defined as the time (expressed in microseconds) that the
transmitting link partner will wait before it starts transmitting data after leaving the Low Power Idle (LPI)
mode. This is a function of the transmit system design and may be constrained, for example, by the transmit
path buffering. The default value for Transmit Tw_sys_tx is the Tw_phy defined for the PHY that is in use for
the link. The Transmitting link partner expects that the Receiving link partner will be able to accept data
after the time delay Transmit Tw_sys_tx (expressed in microseconds).
79.3.5.2 Receive Tw
Receive Tw_sys_tx (2 octets wide) shall be defined as the time (expressed in microseconds) that the receiving
link partner is requesting the transmitting link partner to wait before starting the transmission data following
the LPI. The default value for Receive Tw_sys_tx is the Tw_phy defined for the PHY that is in use for the link.
The Receive Tw_sys_tx value can be larger but not smaller than the default. The extra wait time may be used
by the receive link partner for power-saving mechanisms that require a longer wake-up time than the PHY-
layer definitions.
79.3.5.3 Fallback Tw
A receiving link partner may inform the transmitter of an alternate desired Tw_sys_tx. Since a receiving link
partner is likely to have discrete levels for savings, this provides the transmitter with additional information
that it may use for a more efficient allocation. As with the Receive Tw_sys_tx, this is 2 octets wide. Systems
that do not implement this option default the value to be the same as that of the Receive Tw_sys_tx.
79.3.5.4 Echo Transmit and Receive Tw
The respective echo values shall be defined as the local link partners reflection (echo) of the remote link
partners respective values. When a local link partner receives its echoed values from the remote link partner
it can determine whether or not the remote link partner has received, registered, and processed its most
recent values. For example, if the local link partner receives echoed parameters that do not match the values
in its local MIB, then the local link partner infers that the remote link partners request was based on stale
information.
79.3.5.5 EEE TLV usage rules
An LLDPDU should contain no more than one EEE TLV.
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
Change 79.4.2 by inserting a sentence and new rows at the end of Table 796 and Table 797 as follows:
The cross-references between the EEE TLV and the EEE local (30.12.2) and remote (30.12.3) object class
attributes are listed in Table 796 and Table 797.
Table 796IEEE 802.3 Organizationally Specific TLV/LLDP Local System Group managed
object class cross references
LLDP Local System Group

TLV name TLV variable
managed object class attribute
EEE Transmit Tw_sys_tx aLldpXdot3LocTxTwSys
Receive Tw_sys_tx aLldpXdot3LocRxTwSys
Echo Transmit Tw_sys_tx aLldpXdot3LocTxTwSysEcho
Echo Receive Tw_sys_tx aLldpXdot3LocRxTwSysEcho
Fallback Tw_sys_tx aLldpXdot3LocFbTwSys
Table 797IEEE 802.3 Organizationally Specific TLV/LLDP Remote System Group

managed object class cross references
LLDP Remote System Group

TLV name TLV variable
managed object class attribute
EEE Transmit Tw_sys_tx aLldpXdot3RemTxTwSys
Receive Tw_sys_tx aLldpXdot3RemRxTwSys
Echo Transmit Tw_sys_tx aLldpXdot3RemTxTwSysEcho
Echo Receive Tw_sys_tx aLldpXdot3RemRxTwSysEcho
Fallback Tw_sys_tx aLldpXdot3RemFbTwSys
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 elements24
Insert the following row at the end of the table in 79.5.3 as follows:
*EE EEE TLV 79.5a O Yes [ ]

No [ ]
Insert the following new subclause 79.5a after the last subclause in 79.5:
79.5a EEE TLV
EET1 Transmit Tw field 79.3.5.1 2 octets representing time EE:M Yes [ ]

(expressed in microseconds) N/A [ ]
that the transmitting link part-
ner will wait before it starts
transmitting data after leaving
the LPI mode
EET2 Receive Tw field 79.3.5.2 2 octets representing time EE:M Yes [ ]

that the receiving link partner is
requesting the transmitting link
partner to wait before it starts
transmitting data following the
LPI
EET3 Fallback field 79.3.5.3 2 octets representing time EE:O Yes [ ]
Echo Transmit and Receive 2 octets representing time Yes [ ]
EET4 79.3.5.4 EE:M
Tw fields (expressed in microseconds) N/A [ ]
EET5 Usage rules 79.3.5.5 LLDPDU contains no more EE:O Yes [ ]

than one EEE TLV No [ ]
N/A [ ]
24
Annex 28C
(normative)
Next page Message Code field definitions

Change Table 28C-1 as follows:
Table 28C1Message code field values
Message M M M M M M M M M M M
Message code description
code 10 9 8 7 6 5 4 3 2 1 0
10 0 0 0 0 0 0 0 1 0 1 0 EEE Technology Message Code.

EEE capability to follow using
unformatted next page.
1011..... 0 0 0 0 0 0 0 1 01 0 10 Reserved for future

Auto-Negotiation use
......2047 1 1 1 1 1 1 1 1 1 1 1 Reserved for future
Auto-Negotiation use
Insert a new subclause 28C.12 after 28.C11 as follows:
28C.12 Message code 10EEE technology message code
Multiple clauses use next page message code 10 to indicate that EEE technology messages will follow the
transmission of this page [the initial, Message (formatted) next page] with one unformatted next page. The
contents of the unformatted code field bits (U10:U0) shall be as defined in 45.2.7.13.
EEE capability negotiation is defined in 78.3.
Annex 28D
(normative)
Description of extensions to Clause 28 and associated annexes

Insert a new subclause 28D.7 for extensions required for EEE after 28D.6 as follows:
28D.7 Extensions required for Energy-Efficient Ethernet (Clause 78)
Energy-Efficient Ethernet (Clause 78) makes use of Auto-Negotiation and requires additional MDIO
registers. Auto-negotiation is mandatory for all EEE PHYs that support LPI. Details are provided in 78.3.
Annex 73A
(normative)
Next page Message Code field definitions

Change Table 73A-1 by inserting a new row as follows:
Table 73A1Message code field values
Message M M M M M M M M M M M
Message code description
code 10 9 8 7 6 5 4 3 2 1 0
10 0 0 0 0 0 0 0 1 0 1 0 EEE Technology Message Code.

EEE capability to follow using
unformatted next page.
Insert a new subclause 73A.4 for message code definition after 73A.3 as follows:
73A.4 Message code 10EEE technology message code
Multiple clauses use next page message code 10 as an identifier for EEE technology. The EEE technology
code message shall consist of only a Message next page. The message code field, 000 0000 1010, shall be
contained in bits 10:0. The contents of the unformatted code bits (D47:D16) shall be as defined in 45.2.7.13.
EEE capability negotiation is defined in 78.3.
Annex 74A
(informative)
FEC block coding examples
74A.4 Output of the PN-2112 sequence generator
Insert 74A.5, Table 74A-5, 74A.6, and Table 74A-6 after 74A.4 as follows:
74A.5 Output of the FEC (2112, 2080) Encoder to Support Rapid Block during the wake
state in EEE (optional)
If the optional EEE function is supported (see Clause 78) then the reverse gearbox of the remote FEC
encoder will be receiving unscrambled data. PCS sublayer will be encoding /I/ during the wake state, which
produces the deterministic FEC frame.
Table 74A5 provides the data stream at the output of the FEC (2112, 2080) encoder after the data is
scrambled with the PN-2112 sequence as described in 74.7.4.4.1. The example shows the stream of data in
64 bit format (33 64b symbols) generated from the output of the FEC (2112, 2080) encoder after the PN-
2112 scrambler.
Table 74A5FEC block scrambled with PN-2112 sequence for the wake state
64 bit stream 64 bit stream 64 bit stream 64 bit stream

hex [0:63] hex [0:63] hex [0:63] hex [0:63]
c3ffffffff555540 1e015555555552aa a5fffff000015555 587ffeaaaaeaaaaa
a96a7fffeffffe55 54a0000755551555 5e5aabfffff80000 552d0ffffeaaaa0a
aa82aaabbfffffff f8cb5510000e5554 155a58aaabbfffb4 0006d55587ffefaa
ab596abeaaad5fff abfe151554000000 d555b55501aaaabf ff52781515540bff
feaa9152aaffaaa5 0ffeb5fff5f55414 00411a555555872a baeff9db00141552
0dffbd2aa11eabfe aaad861fbaffa4a5 54140057f5410154 4aeaab87f8d58045
455b54c2bfeaa7f8 abaaeafe0bfeabff 2aad455a01ffa540 0152aa0d7febf554
41555556927fffba fff1aaaa0a000dea abbeaae1a55407ff 2d00105ad35bffeb
f552a155abb5586a
74A.6 Output of the FEC (2112, 2080) Encoder to Support Rapid Block during the
refresh state in EEE (optional)
If the optional EEE capability is supported (see Clause 78) then the reverse gearbox of the remote FEC
encoder will be receiving unscrambled data. PCS sublayer will be encoding /LI/ during the refresh state,
which produces the deterministic FEC frame.
Table 74A6 provides the data stream at the output of the FEC (2112, 2080) encoder after the data is
scrambled with the PN-2112 sequence as described in 74.7.4.4.1. The example shows the stream of data in
64 bit format (33 64b symbols) generated from the output of the FEC (2112, 2080) encoder after the PN-
2112 scrambler.
Table 74A6FEC block scrambled with PN-2112 sequence for the refresh state
64 bit stream 64 bit stream 64 bit stream 64 bit stream

hex [0:63] hex [0:63] hex [0:63] hex [0:63]
c3cf9f3e7c535958 1e19653594d654a6 a5f3e7c060c0d653 5879f2b29a8a6b29
a96979f3f7cf9e94 d4a18301594d2535 9e5a6a7cf9f41830 352d6f3e7daca612
9a829acb7e7cf9f3 e0cb4d2060cfd652 195a54b29bdf3e37 0606d3599fcf8f6b
285969b8a6b56f9f 6a7e1496520c1830 b595b59482aca6a7 cf327875d4d70df3
e69a9162ca3e29a3 03e6b5e7c5959597 064d1a594d65e7eb 39e9f9dd0c0c2532
cc7cbd29a712b3ce ca6c061e39f9a8bd 6474c05734c20758 52dacb8798140343
494364c28f8a667b ada6f2fe13cecb3e a9ab495a0de79520 c0d1ac0d79e7ed64
2194d6569179f3a2 cf916b2a0b830be6 b38eca21a59584f9 2118203ad33b3e68
f35eb9658ed5d943

10 1109@ieeestd 2010 5621025

Uploaded by

Copyright:

Available Formats

10 1109@ieeestd 2010 5621025

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

10 1109@ieeestd 2010 5621025

Uploaded by

Copyright:

Available Formats

,(((6WDQGDUGIRU

&ROOLVLRQ'HWHFWLRQ &60$&' $FFHVV0HWKRG

IEEE Standard for

Part 3: Carrier Sense Multiple Access with

LAN/MAN Standards Committee

Approved 30 September 2010

The Institute of Electrical and Electronics Engineers, Inc.

Copyright 2010 by the Institute of Electrical and Electronics Engineers, Inc.

PDF: ISBN 978-0-7381-6485-4 STD97031

Secretary, IEEE-SA Standards Board

IEEE Std 802.3-2008

iv Copyright 2010 IEEE. All rights reserved.

IEEE Std 802.3av-2009

IEEE Std 802.3bc-2009

IEEE Std 802.3at-2009

IEEE Std 802.3-2008/Cor 12009

IEEE Std 802.3ba-2010

IEEE Std 802.3az-2010

Laws and regulations

Copyright 2010 IEEE. All rights reserved. v

Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/

vi Copyright 2010 IEEE. All rights reserved.

Steven B. Carlson, Working Group Executive Secretary

Michael Bennett, IEEE P802.3az Energy-Efficient Ethernet Task Force Chair

IEEE P802.3az Energy-Efficient Ethernet Clause Editors

Ghani Abbas Bill Delveaux Hideki Isono

Copyright 2010 IEEE. All rights reserved. vii

viii Copyright 2010 IEEE. All rights reserved.

Copyright 2010 IEEE. All rights reserved. ix

Satish K. Aggarwal, NRC Representative

x Copyright 2010 IEEE. All rights reserved.

Special symbols and operators

Printed character Meaning Font

Copyright 2010 IEEE. All rights reserved. xi

1.4 Definitions ............................................................................................................................... 2

22. Reconciliation Sublayer (RS) and Media Independent Interface (MII)............................................. 11

22.2 Functional specifications ....................................................................................................... 11

Copyright 2010 IEEE. All rights reserved. xiii

xiv Copyright 2010 IEEE. All rights reserved.

Copyright 2010 IEEE. All rights reserved. xv

30.2 Managed objects .................................................................................................................... 49

xvi Copyright 2010 IEEE. All rights reserved.

36.2 Physical Coding Sublayer (PCS) ........................................................................................... 65

Copyright 2010 IEEE. All rights reserved. xvii

xviii Copyright 2010 IEEE. All rights reserved.

45. Management Data Input/Output (MDIO) Interface......................................................................... 105

45.2 MDIO Interface Registers.................................................................................................... 105

Copyright 2010 IEEE. All rights reserved. xix

46.1 Overview.............................................................................................................................. 123

xx Copyright 2010 IEEE. All rights reserved.

47.1 Overview.............................................................................................................................. 133

48.1 Overview.............................................................................................................................. 137

Copyright 2010 IEEE. All rights reserved. xxi

49.1 Overview.............................................................................................................................. 151

51. Physical Medium Attachment (PMA) sublayer, type Serial............................................................ 167

51.2 PMA Service Interface......................................................................................................... 167

xxii Copyright 2010 IEEE. All rights reserved.

55.1 Overview.............................................................................................................................. 171

Copyright 2010 IEEE. All rights reserved. xxiii

&ROOLVLRQ'HWHFWLRQ&60$&'$FFHVV0HWKRG