640
IEEE Std 802.3ah -2004 (Amendment to IEEE Std 802.3 -2002 as amended by IEEE Stds 802.3ae -2002, 802.3af -2002, 802.3aj-2003 and 802.3ak-2004) IEEE Standards 802.3ah TM 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: Media Access Control Parameters, Physical Layers, and Management Parameters for Subscriber Access Networks 3 Park Avenue, New York, NY 10016-5997, USA IEEE Computer Society Sponsored by the LAN/MAN Standards Committee IEEE Standards 7 September 2004 Print: SH95249 PDF: SS95249

IEEE Standard for Information technologyŠ ......IEEE Std 802.3ahŽ-2004 (Amendment to IEEE Std 802.3Ž-2002 as amended by IEEE Stds 802.3aeŽ-2002, 802.3afŽ-2002, 802.3ajŽ-2003

  • Upload
    others

  • View
    8

  • Download
    0

Embed Size (px)

Citation preview

  • IEEE Std 802.3ah-2004(Amendment to IEEE Std 802.3-2002

    as amended byIEEE Stds 802.3ae-2002, 802.3af-2002,

    802.3aj-2003 and 802.3ak-2004)IE

    EE

    Sta

    nd

    ard

    s 802.3ahTM

    IEEE Standard for Information technologyTelecommunications and information exchange between systemsLocal and metropolitan area networksSpecific requirements

    Part 3: Carrier Sense Multiple Access withCollision Detection (CSMA/CD) Access Methodand Physical Layer Specifications

    Amendment: Media Access ControlParameters, Physical Layers, and ManagementParameters for Subscriber Access Networks

    3 Park Avenue, New York, NY 10016-5997, USA

    IEEE Computer Society

    Sponsored by theLAN/MAN Standards Committee

    IEE

    E S

    tan

    dar

    ds

    7 September 2004

    Print: SH95249PDF: SS95249

  • IEEE Std 802.3ah™-2004(Amendment to IEEE Std 802.3™-2002

    as amended byIEEE Stds 802.3ae™-2002, 802.3af™-2002,

    802.3aj™-2003, and 802.3ak™-2004)

    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: Media Access Control Parameters, Physical Layers, and Management Parameters for Subscriber Access Networks

    Sponsor

    LAN/MAN Standards Committeeof theIEEE Computer Society

    Approved 24 June 2004

    IEEE-SA Standards Board

  • The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USA

    Copyright © 2004 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 7 September 2004. Printed in the United States of America.

    IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and ElectronicsEngineers, Incorporated.

    Print: ISBN 0-7381-4075-9 SH95249PDF: ISBN 0-7381-4076-7 SS95249

    No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the priorwritten permission of the publisher.

    Abstract: This amendment to IEEE Std 802.3-2002 as amended by IEEE Std 802.3ae-2002, IEEEStd 802.3af-2003, IEEE Std 802.3aj-2003, and IEEE Std 802.3ak-2004 combines a minimal set ofextensions to the IEEE 802.3 Media Access Control (MAC) and MAC Control sublayers with afamily of Physical (PHY) Layers. These Physical Layers include optical fiber and voice grade coppercable Physical Medium Dependent sublayers (PMDs) for point-to-point connections in subscriberaccess networks. This amendment also introduces the concept of Ethernet Passive OpticalNetworks (EPONs), in which a point to multi-point (P2MP) network topology is implemented withpassive optical splitters, along with optical fiber PMDs that support this topology. In addition, amechanism for network Operations, Administration and Maintenance (OAM) is included to facilitatenetwork operation and troubleshooting. To support these innovations, options for unidirectionaltransmission of frames are provided for 100BASE-X, 1000BASE-X, 10GBASE-R, 10GBASE-W,and 10GBASE-X.Keywords: Ethernet in the First Mile, EFM, Ethernet Passive Optical Network, EPON, Ethernetover DSL, Multi-point MAC Control, MPMC, Operations, Administration, Maintenance, OAM, fullduplex MAC, P2MP, P2P, 100BASE-LX10, 100BASE-BX10, 1000BASE-LX10, 1000BASE-BX10,1000BASE-PX10, 1000BASE-PX20, 10PASS-TS, 2BASE-TL, last mile

  • IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of theIEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensusdevelopment process, approved by the American National Standards Institute, which brings together volunteersrepresenting varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of theInstitute and serve without compensation. While the IEEE administers the process and establishes rules to promote fairnessin the consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of theinformation contained in its standards.

    Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or otherdamage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resultingfrom 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 disclaimsany express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or thatthe 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 thetime a standard is approved and issued is subject to change brought about through developments in the state of the art andcomments received from users of the standard. Every IEEE Standard is subjected to review at least every five years forrevision or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable toconclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautionedto 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 servicesfor, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person orentity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of acompetent professional in determining the exercise of reasonable care in any given circumstances.

    Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specificapplications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepareappropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that anyinterpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of itssocieties and Standards Coordinating Committees are not able to provide an instant response to interpretation requests exceptin those cases where the matter has previously received formal consideration. At lectures, symposia, seminars, or educationalcourses, an individual presenting information on IEEE standards shall make it clear that his or her views should be consideredthe 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 withIEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriatesupporting comments. Comments on standards and requests for interpretations should be addressed to:

    Secretary, IEEE-SA Standards Board

    445 Hoes Lane

    P.O. Box 1331

    Piscataway, NJ 08855-1331USA

    Authorization to photocopy portions of any individual standard for internal or personal use is granted by the Institute ofElectrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. Toarrange 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 educationalclassroom use can also be obtained through the Copyright Clearance Center.

    NOTE−Attention is called to the possibility that implementation of this standard may require use of subjectmatter covered by patent rights. By publication of this standard, no position is taken with respect to theexistence or validity of any patent rights in connection therewith. The IEEE shall not be responsible foridentifying patents for which a license may be required by an IEEE standard or for conducting inquiries into thelegal validity or scope of those patents that are brought to its attention.

  • Introduction

    (This introduction is not part of IEEE Std 802.3ah-2004, IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements— CSMA/CD Access Method and Physical Layer Specifications Amendment: MediaAccess Control Parameters, Physical Layers, and Management Parameters for Subscriber Access Networks).

    IEEE Std 802.3™ was first published in 1985. Since the initial publication, many projects have addedfunctionality or provided maintenance updates to the specifications and text included in the standard. EachIEEE 802.3 project/amendment is identified with a suffix (e.g., IEEE 802.3ae). A historical listing of allprojects that have added to or modified IEEE Std 802.3 follows as a part of this introductory material. Thelisting is in chronological order of project initiation and for each project describes: subject, clauses added (ifany), approval dates, and committee officers.

    The media access control (MAC) protocol specified in IEEE Std 802.3 is Carrier Sense Multiple Accesswith Collision Detection (CSMA/CD). This MAC protocol was included in the experimental Ethernetdeveloped 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 ofoperation, and new protocol 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, IEEEStd 802.3u™ added 100 Mb/s operation (also called Fast Ethernet), IEEE Std 802.3x™ specified full duplexoperation and a flow control protocol, IEEE Std 802.3z™ added 1000 Mb/s operation (also called GigabitEthernet) and IEEE Std 802.3ad™ specified link aggregation. These major additions are all now included inIEEE Std 802.3-2002 and are not available as separate documents.

    Recent additions such as IEEE Std 802.3ae (also called 10 Gigabit Ethernet) and IEEE Std 802.3af (also calledPower over Ethernet) are currently published as separate documents. These recent amendments are part ofIEEE Std 802.3 and they are dependent on and reference information published in IEEE Std 802.3-2002.

    At the date of IEEE Std 802.3ah publication, IEEE Std 802.3 is comprised of the following documents:

    IEEE Std 802.3-2002Section One—Includes Clause 1 through Clause 20 and Annexes A through H. Section Oneincludes the specifications for 10 Mb/s operation and the MAC, frame formats and serviceinterfaces used for all speeds of operation.Section Two—Includes Clause 21 through Clause 32 and Annexes 22A through 32A. Section Twoincludes the specifications for 100 Mb/s operation and management attributes for multipleprotocols and operational speeds.Section Three—Includes Clause 34 through Clause 43 and Annexes 36A through 43C. SectionThree includes the specifications for 1000 Mb/s operation.

    IEEE Std 802.3ae-2002Includes changes to IEEE Std 802.3-2002, and adds Clause 44 through Clause 53 and Annexes 44Athrough 50A. This amendment includes specifications for 10 Gb/s operation.

    IEEE Std 802.3af-2003Includes changes to IEEE Std 802.3-2002, and adds Clause 33 and Annexes 33A through 33E. Thisamendment includes specifications for the provision of power over 10BASE-T, 100BASE-TX, and1000BASE-T cabling.

    iv Copyright © 2004 IEEE. All rights reserved.

  • IEEE Std 802.3aj-2003 Includes changes to IEEE Std 802.3-2002 and IEEE Std 802.3ae-2002.

    IEEE Std 802.3ak-2004Includes changes to IEEE Std 802.3-2002, and IEEE Std 802.3ae-2002, and adds Clause 54. Thisamendment adds 10GBASE-CX4 specifications for 10 Gb/s operation over balanced shieldedcabling.

    IEEE Std 802.3ah-2004Includes changes to IEEE Std 802.3-2002, IEEE Std 802.3ae-2002, and IEEE Std 802.3af-2003,and adds Clause 56 through Clause 67 and Annex 58A through Annex 67A. This amendmentdefines services and protocol elements that permit the exchange of IEEE Std 802.3 format framesbetween stations in a subscriber access network.

    IEEE Std 802.3 will continue to evolve. Revisions are anticipated to the above standards within the next fewyears to integrate approved changes into IEEE Std 802.3, to clarify existing material, to correct possibleerrors, and to incorporate new related material.

    Conformance test methodology

    An additional standard, IEEE Std 1802.3™-2001, provides conformance test information for 10BASE-T.

    IEEE Std 802.3ah-2004

    IEEE Std 802.3ah-2004, Ethernet in the First Mile is an amendment to IEEE Std 802.3. The standard includeschanges to IEEE Std 802.3, and these changes are marked in comparison to the last published standard. Insome cases, text included in IEEE Std 802.3-2002 has been modified by IEEE Std 802.3ae-2002, IEEE Std802.3af-2003, then IEEE Std 802.3aj-2003 and again by IEEE Std 802.3ah-2004.

    This document defines services and protocol elements that permit the exchange IEEE Std 802.3 format frames between stations in a subscriber access network.

    Copyright © 2004 IEEE. All rights reserved. v

  • Notice to users

    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 forerrata periodically.

    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 mattercovered by patent rights. By publication of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for identifyingpatents or patent applications for which a license may be required to implement an IEEE standard or forconducting inquiries into the legal validity or scope of those patents that are brought to its attention. A patentholder or patent applicant has filed a statement of assurance that it will grant licenses under these rightswithout compensation or under reasonable rates and nondiscriminatory, reasonable terms and conditions toapplicants desiring to obtain such licenses. The IEEE makes no representation as to the reasonableness ofrates, terms, and conditions of the license agreements offered by patent holders or patent applicants. Furtherinformation may be obtained from the IEEE Standards Department.

    Participants

    The following is a list of voting members when the IEEE 802.3 Working Group balloted this standard.

    Robert M. Grow, ChairDavid Law, Vice-Chair

    Steve Carlson, SecretaryHoward Frazier, Chair, EFM Task Force

    Wael William Diab, Editor-in-Chief, EFM Task ForceHugh Barrass, Vice-Chair, EFM Task Force

    Scott Simon, Recording Secretary, EFM Task ForceBehrooz Rezvani, Executive Secretary, EFM Task Force

    Vipul Bhatt, Chair, EFM Optics Sub Task ForcePiers Dawe, Vice-Chair, EFM Optics Sub Task Force

    Barry O'Mahony, Chair, EFM Copper Sub Task ForceGerry Pesavento, Chair, EFM P2MP Sub Task Force

    Matt Squire, Chair, EFM OAM Sub Task ForceMichaël Beck, Editor, EFM Copper Sub Task ForceKevin Q Daines, Editor, EFM OAM Sub Task ForceAriel Maislos, Editor, EFM P2MP Sub Task Force

    vi Copyright © 2004 IEEE. All rights reserved.

  • Thomas Murphy, Editor, EFM Optics Sub Task ForceBen Brown, Logic Editor, EFM Task Force

    Glen Kramer, P2MP Protocol Editor, EFM Task Force

    Ali AbayeDon AlderrouBrian ArnoldSimcha AronsonDoug ArtmanIlan AtiasEyal BarneaBob BarrettMeir BarturDenis BeaudoinEdward BeiliRandy J. BelowVincent BemmelMike BennettBrad BoothPeter BradshawAl BragaRichard BrandKevin BrownScott BurtonRobert BusseJeff CainRichard CamJames T. CarloDan CarnineXiaopeng ChenJacky ChowGuss ClaessenGeorge ClasemanTerry CobbCharles I. CookGeorge CravensChris CullinJohn DallesasseYair DarshanJohn De AndreaBernard O. DebbaschChris Di MinicoThomas DineenDan DoveDavid DwelleyJ. Craig EasleyEdward J. EckertJohn EganGeorge EislerKent EnglishJohn F. Ewen Sabina FanfoniRobert G. FinchAlan FlatmanBrian FordYukihiro FujimotoRobert D. GaglianelloJustin GaitherJohn George

    Floyd GerhardtGeorge GinisMoty GoldisRich GrahamAjay GummallaJonas GustafssonRuss GyurekSteven HaasStephen HaddockChris HansenOnn HaranAdam HealeyJim HeckrothHenry HinrichsRyan HirthMichael HorvatThong HuynhSteve JacksonKrista S. JacobsenJohn JetztWenbin JiangChad JonesWilliam W. JonesUlf JonssonThomas K. JørgensenShinkyo KakuHadriel KaplanRoger KaramJohn J. KennyLior KhermoshChan KimJin H. KimSu-Hyung KimMarc KimpeNeal KingPaul KolesarHans LacknerDaun LangstonEric LawrenceYannick Le GoffYing LeeAmir LehrAmir LeshemSeyoun LimEric R. LynskeyBrian MacLeodArthur MarrisDavid W. MartinThomas MatheyKent McCammonMichael S. McCormackChris McGuganJohn MessengerTremont MiaoSimon Moseley

    Robert MuirShimon MullerKen MurakamiGerard NadeauKen NaganumaHari NaiduNersi NazariErwan NedellecTrung NguyenKazuhiro NojimaRon NordinBob NoseworthySatoshi ObaraJohn OberstarVladimir OksmanAidan O’RourkeDon PannellGlenn ParsonsAntti PietilainenTimothy R. PlunkettPetre PopescuCarl R. PosthumaWilliam QuackenbushRick RabinovichJerry K. RadcliffeTed RadoNaresh RamanRobert ReedMaurice ReintjesDuane RemeinLawrence RennieShawn RogersDan RomascanuFloyd RossDolors SalaSam SambasivanConcita SaracinoRaj SavaraSabit Say-OtunFred SchindlerLee SendelbachKoichiro SetoSunil ShahBen SheppardCheng-Chung ShihTsuji ShinjiZion ShohetAvadhani ShridharRan SofferJaeyeon SongMassimo SorbaraWalt SotoRichard Stuart

    Copyright © 2004 IEEE. All rights reserved.

    vii

  • The following members of the individual balloting committee voted on this standard. Balloters may havevoted for approval, disapproval, or abstention.

    Steve SwansonRich TaborekMike TateJim TatumPat ThalerR. Jonathan ThatcherWalter ThirionGeoffrey ThompsonDavid ThorneBruce Tolley

    Bor-long TwuMarcos TzannesSterling A. VadenSchelto van DoornKumaran VeerayahGérard VergnaudChiung Hung WangJeff WarrenDong WeiAlan Weissberger

    Erica WilliamsonDarin WintertonTae-Whan YooOsamu YoshiharaHong YuNelson ZagalskyGeorge ZimmermanPavel ZivnyBob Zona

    Roy BynumJohn BarnettHugh BarrassLes BaxterMichael BeckEdward BeiliJacob Ben AryRahul BhushanBrad BoothBenjamin BrownSteve CarlsonKeith ChowGeorge CravensGuru Dutt DhingraPiers DaweWael DiabThomas DineenDaniel DoveSourav DuttaEdward EckertJohn EwenPaul FitzgeraldDavid FratturaHoward FrazierYukihiro FujimotoJustin GaitherRobert GrowChris GuyStephen Haddock

    Marian HargisAdam HealeyAtsus HitoStephen JacksonRaj JainDavid JamesTony JeffreeStanley JohnsonPeter JonesJohn KennyStuart KerryMarc KimpeNeal KingDavid LawPi-Cheng LawJohn LemonKhermosh LiorRandolph LittleRobert LoveEric LynskeyGeorge MiaoJose MoralesAriel MaislosRoger MarksArthur MarrisJohn MessengerSteve MethleyRobert MuirCharles NgetheTrung Nguyen

    Paul NikolichDonald O’ConnorBob O’HaraSatoshi ObaraPeter ÖhlenStephen PalmRoger PandandaGlenn ParsonsGerry PesaventoSubbu PonnuswamyVikram PunjMaximilian RiegelFloyd RossGyurek RussellKevin SchneiderBurkart SchneiderheinzeMarco ScorranoGil ShultzScott SimonGerd SokoliesMatt SquireSteven SwansonGeoffrey ThompsonScott ValcourtFrederick WenigerOren YuenSchelto van Doorn

    viii

    Copyrig

    ht © 2004 IEEE. All rights reserved.

  • When the IEEE-SA Standards Board approved this standard on 24 June 2004, it had the followingmembership:

    Don Wright, ChairSteve M. Mills, Vice ChairJudith Gorman, Secretary

    *Member Emeritus

    Also included are the following nonvoting IEEE-SA Standards Board liaisons:

    Satish K. Aggarwal, NRC RepresentativeRichard DeBlasio, DOE Representative

    Alan Cookson, NIST Representative

    Michelle D. TurnerIEEE Standards Project Editor

    Chuck AdamsH. Stephen BergerMark D. BowmanJoseph A. BruderBob DavisRoberto de BoissonJulian Forster*Arnold M. Greenspan

    Mark S. HalpinRaymond HapemanRichard J. HollemanRichard H. HulettLowell G. JohnsonJoseph L. Koepfinger*Hermann KochThomas J. McGeanDaleep C. Mohla

    Paul NikolichT. W. OlsenRonald C. PetersenGary S. RobinsonFrank StoneMalcolm V. ThadenDoug ToppingJoe D. Watson

    Copyright © 2004 IEEE. All rights reserved

    .

    ix

  • x Copyright © 2004 IEEE. All rights reserved.

  • Contents

    1. (Changes to) Introduction .................................................................................................................... 2

    1.2 Notation ....................................................................................................................................... 21.3 Normative References.................................................................................................................. 21.4 Definitions ................................................................................................................................... 31.5 Abbreviations............................................................................................................................... 5

    22. (Changes to) Reconciliation Sublayer (RS) and Media Independent Interface (MII) ......................... 7

    30. (Changes to) 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Management .......................................... 15

    30.1 Overview.................................................................................................................................... 1530.11Layer Management for Physical Medium Entity (PME).......................................................... 57

    45. (Changes to) Management Data Input/Output (MDIO) Interface ..................................................... 65

    45.1 Overview.................................................................................................................................... 6545.2 MDIO interface registers ........................................................................................................... 6545.5 Protocol Implementation Conformance Statement (PICS) proforma for Clause 45,

    MDIO/MDC management interface ........................................................................................ 124

    (Changes to) Annex A (informative) Bibliography..................................................................................... 133

    (Changes to) Annex 30A (normative) GDMO specification for IEEE 802.3 managed object classes ....... 135

    (Changes to) Annex 30B (normative) GDMO and ASN.1 definitions for management............................. 167

    (Changes to) Annex 31A (normative) MAC Control opcode assignments ................................................. 173

    (Changes to) Annex 43B (normative) Requirements for support of Slow Protocols .................................. 177

    56. Introduction to Ethernet for subscriber access networks ................................................................. 179

    56.1 Overview.................................................................................................................................. 17956.2 State diagrams.......................................................................................................................... 18456.3 Protocol Implementation Conformance Statement (PICS) proforma...................................... 184

    57. Operations, Administration, and Maintenance (OAM) ................................................................... 185

    57.1 Overview.................................................................................................................................. 18557.2 Functional specifications ......................................................................................................... 18757.3 Detailed functions and state diagrams ..................................................................................... 19857.4 OAMPDUs............................................................................................................................... 20957.5 OAM TLVs.............................................................................................................................. 21557.6 Variables .................................................................................................................................. 22457.7 Protocol Implementation Conformance Statement (PICS) proforma for Clause 57,

    Operations, Administration, and Maintenance (OAM) ........................................................... 228

    Copyright © 2004 IEEE. All rights reserved. xi

  • 58. Physical Medium Dependent (PMD) sublayer and medium, type 100BASE-LX10 (LongWavelength) and 100BASE-BX10 (BiDirectional Long Wavelength) ........................................... 235

    58.1 Overview.................................................................................................................................. 23558.2 PMD functional specifications................................................................................................. 23758.3 PMD to MDI optical specifications for 100BASE-LX10 ....................................................... 23958.4 PMD to MDI optical specifications for 100BASE-BX10 ....................................................... 24158.5 Illustrative 100BASE-LX10 and 100BASE-BX10 channels and penalties (informative) ...... 24358.6 Jitter at TP1 and TP4 for 100BASE-LX10 and 100BASE-BX10 (informative)..................... 24458.7 Optical measurement requirements ......................................................................................... 24458.8 Environmental, safety and labeling ......................................................................................... 26458.9 Characteristics of the fiber optic cabling ................................................................................. 26558.10Protocol Implementation Conformance Statement (PICS) proforma for Clause 58,

    Physical Medium Dependent (PMD) sublayer and medium, type 100BASE-LX10(Long Wavelength) and 100BASE-BX10 (BiDirectional Long Wavelength)........................ 267

    59. Physical Medium Dependent (PMD) sublayer and medium, type 1000BASE-LX10(Long Wavelength) and 1000BASE-BX10 (BiDirectional Long Wavelength) .............................. 271

    59.1 Overview.................................................................................................................................. 27159.2 PMD functional specifications................................................................................................. 27459.3 PMD to MDI optical specifications for 1000BASE-LX10 ..................................................... 27559.4 PMD to MDI optical specifications for 1000BASE-BX10-D and 1000BASE-BX10-U ........ 27859.5 Illustrative 1000BASE-LX10 and 1000BASE-BX10 channels and penalties (informative) .. 28059.6 Jitter specifications .................................................................................................................. 28159.7 Optical measurement requirements ......................................................................................... 28159.8 Environmental, safety and labeling specifications .................................................................. 28959.9 Characteristics of the fiber optic cabling ................................................................................. 29059.10Protocol Implementation Conformance Statement (PICS) proforma for Clause 59,

    Physical Medium Dependent (PMD) sublayer and medium, type 1000BASE-LX10 (Long Wavelength) and 1000BASE-BX10 (BiDirectional Long Wavelength) ................................. 294

    60. Physical Medium Dependent (PMD) sublayer and medium, type 1000BASE-PX10 and 1000BASE-PX20 (long wavelength passive optical networks)....................................................... 299

    60.1 Overview.................................................................................................................................. 29960.2 PMD functional specifications................................................................................................. 30260.3 PMD to MDI optical specifications for 1000BASE-PX10-D and 1000BASE-PX10-U......... 30460.4 PMD to MDI optical specifications for 1000BASE-PX20-D and 1000BASE-PX20-U......... 30660.5 Illustrative 1000BASE-PX10 and 1000BASE-PX20 channels and penalties (informative)... 30860.6 Jitter at TP1-4 for 1000BASE-PX10 and 1000BASE-PX20 (informative) ............................ 31060.7 Optical measurement requirements ......................................................................................... 31260.8 Environmental, safety, and labeling ........................................................................................ 31860.9 Characteristics of the fiber optic cabling ................................................................................. 31960.10Protocol Implementation Conformance Statement (PICS) proforma for Clause 60,

    Physical Medium Dependent (PMD) sublayer and medium, type 1000BASE-PX10 and 1000BASE-PX20 (long wavelength passive optical networks) ............................................. 321

    61. Physical Coding Sublayer (PCS), Transmission Convergence (TC) sublayer, and commonspecifications, type 10PASS-TS and type 2BASE-TL.................................................................... 327

    61.1 Overview ................................................................................................................................. 32761.2 PCS functional specifications .................................................................................................. 33661.3 TC sublayer functional specifications...................................................................................... 350

    xii Copyright © 2004 IEEE. All rights reserved.

  • 61.4 Handshaking and PHY control specification for type 2BASE-TL and 10PASS-TS .............. 36861.5 Link segment characteristics.................................................................................................... 37361.6 MDI specification .................................................................................................................... 37461.7 System considerations.............................................................................................................. 37461.8 Environmental specifications................................................................................................... 37461.9 PHY labeling............................................................................................................................ 37461.10Protocol Implementation Conformance Statement (PICS) proforma for Clause 61,

    Physical Coding Sublayer (PCS), Transmission Convergence (TC) sublayer, and common specifications type 10PASS-TS, 2BASE-TL........................................................... 375

    62. Physical Medium Attachment (PMA) and Physical Medium Dependent (PMD), type10PASS-TS...................................................................................................................................... 385

    62.1 Overview ................................................................................................................................. 38562.2 PMA functional specifications................................................................................................. 38662.3 PMD functional specifications................................................................................................. 38862.4 Protocol Implementation Conformance Statement (PICS) proforma for Clause 62,

    Physical Medium Attachment (PMA) and Physical Medium Dependent (PMD), type10PASS-TS.............................................................................................................................. 402

    63. Physical Medium Attachment (PMA) and Physical Medium Dependent (PMD), type2BASE-TL ....................................................................................................................................... 407

    63.1 2BASE-TL Overview .............................................................................................................. 40763.2 2BASE-TL PMA functional specifications ............................................................................. 41063.3 2BASE-TL PMD functional specifications ............................................................................. 41263.4 Protocol Implementation Conformance Statement (PICS) proforma for Clause 63,

    Physical Medium Attachment (PMA) and Physical Medium Dependent (PMD), type2BASE-TL............................................................................................................................... 417

    64. Multi-point MAC Control............................................................................................................... 421

    64.1 Overview.................................................................................................................................. 42164.2 Multi-point MAC Control operation........................................................................................ 42564.3 Multi-Point Control Protocol (MPCP)..................................................................................... 43964.4 Protocol Implementation Conformance Statement (PICS) proforma for Clause 64,

    Multi-point MAC Control ....................................................................................................... 472

    65. Extensions of the Reconciliation Sublayer (RS) and Physical Coding Sublayer (PCS) /Physical Media Attachment (PMA) for 1000BASE-X for Multi-Point Links and ForwardError Correction ............................................................................................................................... 477

    65.1 Extensions of the Reconciliation Sublayer (RS) for Point to Point Emulation ....................... 47765.2 Extensions of the physical coding sublayer for data detection and forward

    error correction ........................................................................................................................ 48165.3 Extensions to PMA for 1000BASE-PX................................................................................... 50065.4 Protocol Implementation Conformance Statement (PICS) proforma for Clause 65,

    Extensions of the Reconciliation Sublayer (RS) and Physical Coding Sublayer (PCS) / Physical Media Attachment (PMA) for 1000BASE-X for Multi-Point Links and Forward Error Correction....................................................................................................................... 502

    Copyright © 2004 IEEE. All rights reserved. xiii

  • 66. Extensions of the 10 Gb/s Reconciliation Sublayer (RS), 100BASE-X PHY, and 1000BASE-X PHY for unidirectional transport .............................................................................................................. 507

    66.1 Modifications to the physical coding sublayer (PCS) and physical mediumattachment (PMA) sublayer, type 100BASE-X ...................................................................... 507

    66.2 Modifications to the physical coding sublayer (PCS) and physical mediumattachment (PMA) sublayer, type 1000BASE-X.................................................................... 509

    66.3 Modifications to the reconciliation sublayer (RS) for 10 Gb/s operation................................ 51066.4 Protocol Implementation Conformance Statement (PICS) proforma for Clause 66,

    Extensions of the 10 Gb/s Reconciliation Sublayer (RS), 100BASE-X PHY, and 1000BASE-X PHY for unidirectional transport...................................................................... 512

    67. System considerations for Ethernet subscriber access networks ..................................................... 515

    67.1 Overview.................................................................................................................................. 51567.2 Discussion and examples of EFM P2MP topologies............................................................... 51667.3 Hybrid Media topologies ......................................................................................................... 51767.4 Topology limitations................................................................................................................ 51767.5 Deployment restrictions for subscriber access copper............................................................. 51767.6 Operations, Administration, and Maintenance ........................................................................ 518

    Annex 4A (normative) Simplified full duplex media access control .......................................................... 519

    Annex 22D (informative) Clause 22 access to Clause 45 MMD registers .................................................. 545

    Annex 58A (informative) Frame based testing............................................................................................ 547

    Annex 61A (informative) EFM copper examples ....................................................................................... 549

    Annex 61B (normative) Handshake codepoints for 2BASE-TL and 10PASS-TS ...................................... 557

    Annex 62A (normative) PMD profiles for 10PASS-TS .............................................................................. 585

    Annex 62B (normative) Performance guidelines for 10PASS-TS PMD profiles........................................ 597

    Annex 62C (informative) 10PASS-TS Examples........................................................................................ 603

    Annex 63A (normative) PMD Profiles for 2BASE-TL............................................................................... 609

    Annex 63B (normative) Performance guidelines for 2BASE-TL PMD profiles ........................................ 613

    Annex 67A (informative) Environmental characteristics for Ethernet subscriber access networks ........... 619

    xiv Copyright © 2004 IEEE. All rights reserved.

  • Copyright © 2004 IEEE. All rights reserved.This is an unapproved IEEE Standards Draft, subject to change i

    List of special symbols

    For the benefit of those who have received this document by electronic means, what follows is a list ofspecial symbols and operators. If any of these symbols or operators fail to print out correctly, the editorshope that this table will at least help you to sort out the meaning of the resulting funny-shaped blobs andstrokes appearing in the body of the document.

    Special symbols and operators

    Printed Character Meaning Frame Vcharacter code Font

    ∗ Boolean AND ALT-042 Symbol

    + Boolean OR, arithmetic addition ALT-043 Symbol^ Boolean XOR ^ Times

    ! Boolean NOT ALT-033 Symbol

    < Less than ALT-060 Symbol

    ≤ Less than or equal to ALT-0163 Symbol

    = Equal to ALT-061 Symbol

    ≠ Not equal to ALT-0185 Symbol

    ≥ Greater than or equal to ALT-0179 Symbol

    > Greater than ALT-062 Symbol

    ⇐ Assignment operator ALT-0220 Symbol

    ∈ Indicates membership ALT-0206 Symbol

    ∉ Indicates nonmembership ALT-0207 Symbol± Plus or minus (a tolerance) ALT-0177 Symbol

    ° Degrees (as in degrees Celsius) ALT-0176 Symbol

    ∑ Summation ALT-0229 Symbol

    — Big dash (em dash) Ctrl-q Shft-q Times

    – Little dash (en dash) Ctrl-q Shft-p Times

    † Dagger ALT-0134 Times

    ‡ Double dagger ALT-0135 Times

    α Lower case alpha a Symbolβ Lower case beta b Symbolε Lower case epsilon e Symbolγ Lower case gamma g Symbol

    Square root ALT-0214 Times

  • 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: Media Access Control Parameters, Physical Layers, and Management Parameters for Subscriber Access Networks

    [These changes are part of IEEE Std 802.3™-2002.]

    EDITORIAL NOTE—This amendment is based on the current edition of IEEE Std 802.3-2002 as amended byIEEE Std 802.3ae™-2002, IEEE Std 802.3af™-2003, IEEE Std 802.3aj™-2003, and IEEE Std 802.3ak™-2004.The editing instructions define how to merge the material contained here into this base document set to form thenew comprehensive standard as created by the addition of IEEE Std 802.3ah™-2004.

    Editing instructions are shown in bold italic. Four editing instructions are used: change, delete, insert, andreplace. Change is used to make small corrections in existing text or tables. The editing instruction specifiesthe location of the change and describes what is being changed either by using strikethrough (to remove oldmaterial) or underscore (to add new material). Delete removes existing material. Insert adds new materialwithout disturbing the existing material. Insertions may require renumbering. If so, renumbering instructionsare given in the editing instruction. Editorial notes will not be carried over into future editions. Replace isused to make large changes in existing text, subclauses, tables, or figures by removing existing material andreplacing it with new material. Editorial notes will not be carried over into future editions because thechanges will be incorporated into the base standard.

    Copyright © 2004 IEEE. All rights reserved. 1

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    1. Introduction

    1.2 Notation

    Insert the following to the end of 1.2.5, Hexadecimal notation:

    Numerical values designated with a 16 subscript indicate a hexadecimal interpretation of the corresponding-number. For example: 0F16 represents an 8-bit hexadecimal value of the decimal number 15.

    1.3 Normative References

    Change existing reference to read as follows:

    ITU-T Recommendation G.652, 2000—Characteristics of a single-mode opitical fibre cable.ITU-TRecommendation G.652, 2003— Characteristics of a single-mode optical fibre and cable.

    ANSI X3.230-1994 (FC-PH), Information Technology—Fibre Channel—Physical and Signaling Interface.ANSI INCITS 230-1994 (R1999), Information Technology—Fibre Channel—Physical and SignalingInterface (FC-PH) (formerly ANSI X3.230-1994).

    Insert the following references in alphabetic order into the reference list in 1.3:

    ANSI/EIA-455-95A-2000, Absolute Optical Power Test for Optical Fibers and Cables.

    ANSI/EIA/TIA-455-127-1991, FOTP-127 — Spectral Characterization of Multimode Laser Diodes.

    ANSI T1.417-2001, Spectrum management for loop transmission systems.

    ANSI T1.424-2004, Interface between networks and customer installations - Very-high Speed DigitalSubscriber Lines (VDSL) Metallic Interface (Trial-Use Standard).

    ETSI TS1 101 270-1 (1999), Transmission and Multiplexing (TM); Access transmission systems on metallicaccess cables; Very high speed Digital Subscriber Line (VDSL); Part 1: Functional requirements.

    ETSI TS 270-2 (2001), Transmission and Multiplexing (TM); Access transmission systems on metallicaccess cables; Very high speed Digital Subscriber Line (VDSL); Part 2: Transceiver specification.

    IEC 61280-2-2 (1998), Fiber optic communication sub-system basic test procedures – Part 2-2: Testprocedures for digital systems – Optical eye pattern, waveform, and extinction ratio.

    IEC 61754-1:1996, Fibre optic interfaces —Part 1: General and guidance.

    ITU-T Recommendation G.991.2 (2001), Amendment 1.

    ITU-T Recommendation G.991.2 (2001), Single-Pair High-Speed Digital Subscriber Line (SHDSL)transceivers.

    ITU-T Recommendation G.993.1 (2003), Amendment 1.

    ITU-T Recommendation G.993.1 (2001), Very high speed digital subscriber line foundation.

    ITU-T Recommendation G.994.1 (2004), Handshake procedures for digital subscriber line (DSL)transceivers.

    ITU-T Recommendation G.975 (2000), Optical fibre submarine cable systems Forward error correction forsubmarine systems.

    2 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    1.4 Definitions

    Change 1.4.10 to the following:

    1.4.10 100BASE-FX: IEEE 802.3 Physical Layer specification for a 100 Mb/s CSMA/CD local area net-work over two optical fibers. (See IEEE 802.3 Clauses 24 and 26.) IEEE 802.3 Physical Layer specificationfor a 100 Mb/s CSMA/CD local area network over two multimode optical fibers. (See IEEE 802.3 Clauses24 and 26.)

    Insert the following definitions alphabetically into 1.4. Renumber the definitions as required. Thesedefinitions will be renumbered in alphabetic order in a future edition of this standard:

    1.4.xxx 100BASE-BX10: IEEE 802.3 Physical Layer specification for a 100 Mb/s point to point link overone single mode fiber. The link includes two different specifications for 100BASE-BX10-D and 100BASE-BX10-U. (See IEEE 802.3 Clauses 58 and 66.)

    1.4.xxx 100BASE-LX10: IEEE 802.3 Physical Layer specification for a 100 Mb/s point to point link overtwo single mode optical fibers. (See IEEE 802.3 Clauses 58 and 66.)

    1.4.xxx 1000BASE-BX10: IEEE 802.3 Physical Layer specification for a 1000 Mb/s point to point link overone single mode optical fiber. (See IEEE 802.3 Clauses 59 and 66.)

    1.4.xxx 1000BASE-LX10: IEEE 802.3 Physical Layer specification for a 1000 Mb/s point to point link overtwo single-mode or multimode optical fibers. (See IEEE 802.3 Clauses 59 and 66.)

    1.4.xxx 1000BASE-PX10: IEEE 802.3 Physical Layer specification for a 1000 Mb/s point to multi-pointlink over one single mode optical fiber, with a reach of up to 10 km. (See IEEE 802.3 Clauses 60, 65, and66.)

    1.4.xxx 1000BASE-PX20: IEEE 802.3 Physical Layer specification for a 1000 Mb/s point to multi-pointlink over one single mode optical fiber, with a reach of up to 20 km. (See IEEE 802.3 Clauses 60, 65, and66.)

    1.4.xxx 10PASS-TS: IEEE 802.3 Physical Layer specification up to 100 Mb/s point to point link over singlecopper wire pair. (See IEEE 802.3 Clauses61 and 62.)

    1.4.xxx 2BASE-TL: IEEE 802.3 Physical Layer specification up to 5.696 Mb/s point to point link oversingle copper wire pair. (See IEEE 802.3 Clauses 61 and 63.)

    1.4.xxx Aggregation group: A collection of PMEs that may be aggregated according to a particularimplementation of the PME aggregation function. (See IEEE 802.3 subclause 61.2.2.)

    1.4.xxx Bandplan: The set of parameters that control the lowest and highest frequencies and power at which10PASS-TS and 2BASE-TL may operate.

    1.4.xxx Coupled Power Ratio (CPR): The ratio (in dB) of the total power coupled into a multimode fiber tothe optical power that can be coupled into a single-mode fiber.

    1.4.xxx Downstream: In an access network, where there is a clear indication in each deployment as to whichend of a link is closer to a subscriber, transmission toward the subscriber end of the link.

    Copyright © 2004 IEEE. All rights reserved. 3

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    1.4.xxx Grant: Within P2MP protocols, a permission to transmit at a specific time, for a specific duration.Grants are issued by the OLT (master) to ONUs (slaves) by means of GATE messages.

    1.4.xxx Logical Link Identifier (LLID): A numeric identifier assigned to a P2MP association between anOLT and ONU established through the Point-to-Point Emulation sublayer. Each P2MP association isassigned a unique LLID. The P2MP association is bound to an ONU DTE, where a MAC would observe aprivate association.

    1.4.xxx OAM Discovery: Process that detects the presence and configuration of the OAM sublayer in theremote DTE.

    1.4.xxx Operations, Administration, and Maintenance (OAM): A group of network support functions thatmonitor and sustain segment operation, activities that are concerned with, but not limited to, failure detec-tion, notification, location, and repairs that are intended to eliminate faults and keep a segment in an opera-tional state and support activities required to provide the services of a subscriber access network to users/subscribers.

    1.4.xxx Optical Line Terminal (OLT): The network-end DTE for an optical access network. The OLT is themaster entity in a P2MP network with regard to the MPCP protocol.

    1.4.xxx Optical Network Unit (ONU): The subscriber-end DTE to an optical access network. An ONU is aslave entity in a P2MP network with regard to the MPCP protocol.

    1.4.xxx P2MP Discovery: Process by which the OLT finds a newly attached and active ONU in the P2MPnetwork, and by which the OLT and ONU exchange registration information. The OLT sends a GATEflagged for discovery.

    1.4.xxx P2MP Discovery window: A time period in a given wavelength band reserved by the OLTexclusively for the discovery process.

    1.4.xxx P2MP Timestamp: The timestamp used to synchronize slaves (e.g., ONUs) with the master (OLT)and for the ranging process.

    1.4.xxx Point to Multi-Point Network (P2MP): A passive optical network providing transport of Ethernetframes (See Clauses 64 and 65).

    1.4.xxx Point-to-point emulation (P2PE): Emulation of private communication between two end-stations(e.g., ONU) in a P2MP. Emulation creates the equivalent of a star topology with the OLT in the nexus, and isrequired for compliance with IEEE 802.1D bridging.

    1.4.xxx Ranging: A procedure by which the propagation delay between a master (e.g., OLT) and slave (e.g.,ONU) is measured. The round trip delay computation is performed by the OLT, using the timestamp inMPCP messages from the ONU.

    1.4.xxx Reflectance: Ratio of reflected to incident power. This is the inverse of return loss.

    1.4.xxx Upstream: In an access network, transmission away from the subscriber end of the link. Applicableto networks where there is a clear indication in each deployment as to which end of a link is closer to asubscriber.

    4 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    1.5 Abbreviations

    Insert the following abbreviations in alphabetic order into the abbreviations list in 1.5:

    10P label to indicate “pertains to 10PASS-TS port-type”10P/2B label to indicate “pertains to 10PASS-TS and 2BASE-TL port-types”2B label to indicate “pertains to 2BASE-TL port-type”2-PAM two level pulse amplitude modulationCO central officeCPE customer premises equipmentCPR coupled power ratioDA destination addressDMT discrete multi-toneDSL digital subscriber lineEFM Ethernet in the first mileFEC forward error correctionFSW frame synchronization wordIB indicator bitsLLID logical link identifierLT line terminationMDIO management data input/outputMPCP multi-point control protocolNT network terminationOAM operations, administration, and maintenanceOAMPDU operations, administration, and maintenance protocol data unitODN optical distribution networkOH overheadOLT optical line terminalONU optical network unitORLT optical return loss toleranceP2MP point to multi-pointP2P point to pointP2PE point-to-point emulationPAF PME aggregation functionPAM pulse amplitude modulationPME physical medium entityPMS-TC physical media specific - transmission convergencePSD power spectral densitySA source addressSHDSL single-pair high-speed digital subscriber lineTC transmission convergenceTCM trellis coded modulationTPS-TC transport protocol specific transmission convergence sublayerUPBO upstream power back-offVDSL very high speed digital subscriber lineVTU VDSL transceiver unitVTU-O VTU at the central office endVTU-R VTU at the remote endxDSL generic term covering the family of all DSL technologies

    Copyright © 2004 IEEE. All rights reserved. 5

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    6 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

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

    22.2.4 Management functions

    Change the third paragraph of this subclause (IEEE Std 802.3af-2003) as follows:

    The MII basic register set consists of two registers referred to as the Control register (Register 0) and theStatus register (Register 1). All PHYs that provide an MII shall incorporate the basic register set. All PHYsthat provide a GMII shall incorporate an extended basic register set consisting of the Control register(Register 0), Status register (Register 1), and Extended Status register (Register 15). The status and controlfunctions defined here are considered basic and fundamental to 100 Mb/s and 1000 Mb/s PHYs. Registers 2through 1214 are part of the extended register set. The format of Registers 4 through 10 are defined for thespecific Auto-Negotiation protocol used (Clause 28 or Clause 37). The format of these registers is selectedby the bit settings of Registers 1 and 15.

    Change Table 22-6 (IEEE Std 802.3af-2003) as follows:

    Table 22–6—MII management register set

    Register address Register name Basic/ExtendedMII GMII

    0 Control B B

    1 Status B B

    2, 3 PHY Identifier E E

    4 Auto-Negotiation Advertisement E E

    5 Auto-Negotiation Link Partner Base Page Ability

    E E

    6 Auto-Negotiation Expansion E E

    7 Auto-Negotiation Next Page Transmit E E

    8 Auto-Negotiation Link Partner Received Next Page

    E E

    9 MASTER-SLAVE Control Register E E

    10 MASTER-SLAVE Status Register E E

    11 PSE Control Register E E

    12 PSE Status Register E E

    13,14 Reserved E E

    13 MMD Access Control Register E E

    14 MMD Access Address Data Register E E

    15 Extended Status Reserved B

    16 through 31 Vendor Specific E E

    Copyright © 2004 IEEE. All rights reserved. 7

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    22.2.4.1 Control register (Register 0)

    Change Table 22-7 as follows:

    Table 22–7—Control register bit definitions

    Bit(s) Name Description R/Wa

    aR/W = Read/Write, SC = Self-Clearing.

    0.15 Reset 1 = PHY reset0 = normal operation

    R/WSC

    0.14 Loopback 1 = enable loopback mode0 = disable loopback mode

    R/W

    0.13 Speed Selection (LSB) 0.6 0.131 1 = Reserved1 0 = 1000 Mb/s0 1 = 100 Mb/s0 0 = 10 Mb/s

    R/W

    0.12 Auto-Negotiation Enable 1 = Eenable Auto-Negotiation Pprocess0 = Ddisable Auto-Negotiation Pprocess

    R/W

    0.11 Power Down 1 = power down0 = normal operationb

    bFor normal operation, both 0.10 and 0.11 must be cleared to zero; see 22.2.4.1.5.

    R/W

    0.10 Isolate 1 = electrically Isolate PHY from MII or GMII0 = normal operationb

    R/W

    0.9 Restart Auto-Negotiation 1 = Rrestart Auto-Negotiation Pprocess0 = normal operation

    R/WSC

    0.8 Duplex Mode 1 = Ffull Dduplex0 = Hhalf Dduplex

    R/W

    0.7 Collision Test 1 = enable COL signal test0 = disable COL signal test

    R/W

    0.6 Speed Selection (MSB) 0.6 0.131 1 = Reserved1 0 = 1000 Mb/s0 1 = 100 Mb/s0 0 = 10 Mb/s

    R/W

    0.5 Unidirectional enable When bit 0.12 is one or bit 0.8 is zero, this bit is ignored. When bit 0.12 is zero and bit 0.8 is one:

    1 = Enable transmit from media independent interface regardless of whether the PHY has determined that a valid link has been established0 = Enable transmit from media independent interface only when the PHY has determined that a valid link has been established

    R/W

    0.5:0 0.4:0

    Reserved Write as 0, ignore on Rread R/W

    8 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    Change 22.2.4.1.11 to read

    22.2.4.1.11 Reserved bits

    Bits 0.5:00.4:0 are reserved for future standardization. They shall be written as zero and shall be ignoredwhen read; however, a PHY shall return the value zero in these bits.

    Insert subclause:

    22.2.4.1.12 Unidirectional enable

    If a PHY reports via bit 1.7 that it lacks the ability to encode and transmit data from the media independentinterface regardless of whether the PHY has determined that a valid link has been established, the PHY shallreturn a value of zero in bit 0.5, and any attempt to write a one to bit 0.5 shall be ignored.

    The ability to encode and transmit data from the media independent interface regardless of whether thePHY has determined that a valid link has been established is controlled by bit 0.5 as well as the status ofAuto-Negotiation Enable bit 0.12 and the Duplex Mode bit 0.8 as this ability can only be supported if Auto-Negotiation is disabled and the PHY is operating in full-duplex mode. If bit 0.5 is set to a logic one, bit0.12 to logic zero and bit 0.8 to logic one, encoding and transmitting data from the media independentinterface shall be enabled regardless of whether the PHY has determined that a valid link has beenestablished. If bit 0.5 is set to a logic zero, bit 0.12 to logic one or bit 0.8 to logic zero, encoding andtransmitting data from the media independent interface shall be dependent on whether the PHY hasdetermined that a valid link has been established. When bit 0.12 is one or bit 0.8 is zero, bit 0.5 shall beignored.

    A management entity shall set bit 0.5 to a logic one only after it has enabled an associated OAM sublayer(see Clause 57) or if this device is a 1000BASE-PX-D PHY. A management entity shall clear bit 0.5 to alogic zero prior to it disabling an associated OAM sublayer when this device is not a 1000BASE-PX-D PHY.To avoid collisions, a management entity should not set bit 0.5 of a 1000BASE-PX-U PHY to a logic one.

    The default value of bit 0.5 is zero, except for 1000BASE-PX-D, where it is one.

    Copyright © 2004 IEEE. All rights reserved. 9

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    22.2.4.2 Status register (Register 1)

    Change the ninth row of Table 22-8:

    Table 22–8—Status register bit definitions

    Bit(s) Name Description R/Wa

    aRO = Read Only, LL = Latching Low, LH = Latching High

    1.15 100BASE-T4 1 = PHY able to perform 100BASE-T40 = PHY not able to perform 100BASE-T4

    RO

    1.14 100BASE-X Full Duplex 1 = PHY able to perform full duplex 100BASE-X0 = PHY not able to perform full duplex 100BASE-X

    RO

    1.13 100BASE-X Half Duplex 1 = PHY able to perform half duplex 100BASE-X0 = PHY not able to perform half duplex 100BASE-X

    RO

    1.12 10 Mb/s Full Duplex 1 = PHY able to operate at 10 Mb/s in full duplex mode0 = PHY not able to operate at 10 Mb/s in full duplex mode

    RO

    1.11 10 Mb/s Half Duplex 1 = PHY able to operate at 10 Mb/s in half duplex mode0 = PHY not able to operate at 10 Mb/s in half duplex mode

    RO

    1.10 100BASE-T2 Full Duplex 1 = PHY able to perform full duplex 100BASE-T20 = PHY not able to perform full duplex 100BASE-T2

    RO

    1.9 100BASE-T2 Half Duplex 1 = PHY able to perform half duplex 100BASE-T20 = PHY not able to perform half duplex 100BASE-T2

    RO

    1.8 Extended Status 1 = Extended status information in Register 150 = No extended status information in Register 15

    RO

    1.7 ReservedUnidirectional ability

    ignore when read1 = PHY able to transmit from media independent interface regardless of whether the PHY has determined that a valid link has been established0 = PHY able to transmit from media independent interface only when the PHY has determined that a valid link has been established

    RO

    1.6 MF Preamble Suppression 1 = PHY will accept management frames with preamble suppressed.0 = PHY will not accept management frames with preamble suppressed.

    RO

    1.5 Auto-Negotiation Complete

    1 = Auto-Negotiation process completed0 = Auto-Negotiation process not completed

    RO

    1.4 Remote Fault 1 = remote fault condition detected0 = no remote fault condition detected

    RO/LH

    1.3 Auto-Negotiation Ability 1 = PHY is able to perform Auto-Negotiation0 = PHY is not able to perform Auto-Negotiation

    RO

    1.2 Link Status 1 = link is up0 = link is down

    RO/LL

    1.1 Jabber Detect 1 = jabber condition detected0 = no jabber condition detected

    RO/LH

    1.0 Extended Capability 1 = extended register capabilities0 = basic register set capabilities only

    RO

    10 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    Replace 22.2.4.2.8 with the following

    22.2.4.2.8 Unidirectional ability

    When read as a logic one, bit 1.7 indicates that the PHY has the ability to encode and transmit data from themedia independent interface regardless of whether the PHY has determined that a valid link has beenestablished. When read as a logic zero, bit 1.7 indicates the PHY is able to transmit data from the mediaindependent interface only when the PHY has determined that a valid link has been established.

    A PHY shall return a value of zero in bit 1.7 if it is not a 100BASE-X PHY using the PCS and PMAspecified in 66.1 or a 1000BASE-X PHY using the PCS and PMA specified in 66.2.

    22.2.4.3 Extended capability registers

    Change the first paragraph of this subclause (IEEE Std 802.3af-2003) as follows:

    In addition to the basic register set defined in 22.2.4.1 and 22.2.4.2, PHYs may provide an extended set ofcapabilities that may be accessed and controlled via the MII management interface. ThirteenEleven registershave been defined within the extended address space for the purpose of providing a PHY-specific identifierto layer management, to provide control and monitoring for the Auto-Negotiation process, and to providecontrol and monitoring of power sourcing equipment, and to provide MDIO Manageable Device (MMD)register access.

    Insert the following new subclauses after subclause 22.2.4.3.10, renumber current subclause 22.2.4.3.11to 22.2.4.3.13. Renumber current tables after the newly inserted tables.

    22.2.4.3.11 MMD access control register (Register 13)

    The assignment of bits in the MMD access control register is shown in Table 22–9. The MMD accesscontrol register is used in conjunction with the MMD access address data register (Register 14) to provideaccess to the MMD address space using the interface and mechanisms defined in 22.2.4.

    Each MMD maintains its own individual address register as described in 45.2.7. The DEVAD field directsany accesses of Register 14 to the appropriate MMD as described in 45.2. If the access of Register 14 is anaddress access (bits 13.15:14 = 00) then it is directed to the address register within the MMD associated withthe value in the DEVAD field (bits 13.4:0). Otherwise, both the DEVAD field and that MMD’s addressregister direct the Register 14 data accesses to the appropriate registers within that MMD.

    Table 22–9—MMD access control register bit definitions

    Bit(s) Name Description R/Wa

    aR/W = Read/Write

    13.15:14 Function 13.15 13.140 0 = address0 1 = data, no post increment1 0 = data, post increment on reads and writes1 1 = data, post increment on writes only

    R/W

    13.13:5 Reserved Write as 0, ignore on read R/W

    13.4:0 DEVAD Device address R/W

    Copyright © 2004 IEEE. All rights reserved. 11

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    The Function field can be set to any of four values:

    a) When set to 00, accesses to Register 14 access the MMD’s individual address register. This addressregister should always be initialized before attempting any accesses to other MMD registers.

    b) When set to 01, accesses to Register 14 access the register within the MMD selected by the value inthe MMD’s address register.

    c) When set to 10, accesses to Register 14 access the register within the MMD selected by the value inthe MMD’s address register. After that access is complete, for both read and write accesses, thevalue in the MMD’s address field is incremented.

    d) When set to 11, accesses to Register 14 access the register within the MMD selected by the value inthe MMD’s address register. After that access is complete, for write accesses only, the value in theMMD’s address field is incremented. For read accesses, the value in the MMD’s address field is notmodified.

    For additional insight into the operation and usage of this register, see Annex 22D.

    22.2.4.3.12 MMD access address data register (Register 14)

    The assignment of bits in the MMD access address data register is shown in Table 22–10. The MMD accessaddress data register is used in conjunction with the MMD access control register (Register 13) to provideaccess to the MMD address space using the interface and mechanisms defined in 22.2.4. Accesses to thisregister are controlled by the value of the fields in Register 13 and the contents of the MMD’s individualaddress field as described in 22.2.4.3.11.

    For additional insight into the operation and usage of this register, see Annex 22D.

    22.7.2.3 Major capabilities/options

    Insert the following major capability/option into 22.7.2.3 after *GM:

    Table 22–10—MMD access address data register bit definitions

    Bit(s) Name Description R/Wa

    aR/W = Read/Write

    14.15:0 Address Data If 13.15:14 = 00, MMD DEVAD’s address register.Otherwise, MMD DEVAD’s data register as indicated by the contents of its address register

    R/W

    Item Feature Subclause Status Support Value/Comment

    *MUNI Implementation of unidirectional PCS 22.2.4 O Yes [ ]No [ ]

    12 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    22.7.3.4 Management functions

    Insert the following PICS items into 22.7.3.4 after MF37, and renumber the following PICS items:

    Item Feature Subclause Status Support Value/Comment

    MF38 PHY without unidirectional ability

    22.2.4.1.12 M Yes [ ]NA [ ]

    PHY returns a value of 0 in 0.5 if 1.7=0

    MF39 PHY without unidirectional ability

    22.2.4.1.12 M Yes [ ]NA [ ]

    PHY always maintains a value of 0 in 0.5 if 1.7=0

    MF40 Unidirectional enable 22.2.4.1.12 MUNI:M Yes [ ]NA [ ]

    By setting 0.12 = 0, 0.8 = 1 and 0.5 = 1

    MF41 Unidirectional disable 22.2.4.1.12 MUNI:M Yes [ ]NA [ ]

    By setting 0.12 = 1, 0.8 = 0 or 0.5 = 0

    MF42 Ignore bit 0.5 22.2.4.1.12 MUNI:M Yes [ ]NA [ ]

    Ignore 0.5 when 0.12 = 1 or0.8 = 0

    MF43 Enable unidirectional mode 22.2.4.1.12 MUNI:M Yes [ ]NA [ ]

    Enable only when OAM sub-layer is enabled or when part of 1000BASE-PX-D PHY

    MF44 Disable unidirectional mode 22.2.4.1.12 MUNI:M Yes [ ]NA [ ]

    Unidirectional mode is dis-abled before disabling OAM sublayer when not part of 1000BASE-PX-D PHY

    MF45 Unidirectional ability 22.2.4.2.8 M Yes [ ]NA [ ]

    Bit 1.7 = 0 for all PHYs except those using 66.1 and 66.2

    Copyright © 2004 IEEE. All rights reserved. 13

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    14 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    30. 10 Mb/s, 100 Mbs, 1000 Mb/s and 10Gb/s Management

    Change the title of this clause as follows:

    30. 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Management

    30.1 Overview

    Change the first paragraph of this subclause as follows (as modified by IEEE Std 802.3ae-2002 andIEEE Std 802.3af-2003):

    This clause provides the Layer Management specification for DTEs, repeaters, and MAUs based on theCSMA/CD access method. The clause is produced from the ISO framework additions to Clause 5, LayerManagement; Clause 19, Repeater Management; and Clause 20, MAU Management. It incorporatesadditions to the objects, attributes, and behaviours to support 100 Mb/s, 1000 Mb/s and 10 Gb/s, full duplexoperation, MAC Control, Link Aggregation, and DTE Power via MDI, and subscriber access networks.

    30.1.1 Scope

    Change the first paragraph of this subclause as follows (as modified by IEEE Std 802.3ae-2002 andIEEE Std 802.3af-2003):

    This clause includes selections from Clauses 5, 19, and 20. It is intended to be an entirely equivalentspecification for the management of 10 Mb/s DTEs, 10 Mb/s baseband repeater units, and 10 Mb/sintegrated MAUs. It incorporates additions to the objects, attributes, and behaviours to support subsequentadditions to this standard.It also includes the additions for management of MAC Control, DTEs andrepeaters at speeds greater than 10 Mb/s, embedded MAUs, PHYs and DTE Power via MDI.Implementations of management for DTEs, repeater units, and embedded MAUs should follow therequirements of this clause (e.g., a 10 Mb/s implementation should incorporate the attributes to indicate thatit is not capable of 100 Mb/s or 1000 Mb/s operation,; half duplex DTE should incorporate the attributes toindicate that it is not capable of full duplex operation, etc.).

    30.1.2 Relationship to objects in IEEE 802.1F

    Change the second paragraph of this subclause as follows (as modified by IEEE Std 802.3af-2003):

    oResourceTypeIDThis object class is mandatory and shall be implemented as defined in IEEE 802.1F. This object is bound to oMAC-Entity, oRepeater, oMidSpan and oMAU as defined by the NAME BINDINGs in 30A.10.1. Note that the binding to oMAU is mandatory only when MII is present. The Entity Relationship Diagrams, Figures 30–3, 30–4, and 30–45, shows these bindings pictorially.

    30.1.4 Management model

    Change the second last paragraph of this subclause as follows (as modified by IEEE Std 802.3ae-2002and IEEE Std 802.3af-2003):

    The above items are defined in 30.3 through 30.10 30.3.7 of this clause in terms of the templaterequirements of ISO/IEC 10165-4: 1991.

    Copyright © 2004 IEEE. All rights reserved. 15

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    30.2.2.1 Text description of managed objects

    Change the following paragraphs of this subclause as follows (as modified by IEEE Std 802.3ae-2002and IEEE Std 802.3af-2003):

    In case of conflict, the formal behaviour definitions in 30.3, 30.4, 30.5, 30.6, and 30.7 take precedence overthe text descriptions in this subclause.

    oAggPortDebugInformationIf oAggregator is implemented, a single instance of oAggPortDebugInformation may be contained within oAggregationPort. This managed object class provides optional additional information that can assist with debugging and fault finding in Systems that support Link Aggregation.

    oAggPortStats If oAggregator is implemented, a single instance of oAggPortStats may be contained within oAggregationPort. This managed object class provides optional additional statistics related to LACP and Marker protocol activity on an instance of an Aggregation Port that is involved in Link Aggregation.

    oAggregationPort If oAggregator is implemented, oAggregationPort is contained within oAggregator. An instance of this managed object class is present for each Aggregation Port that is part of the aggregation represented by the oAggregator instance. This managed object class provides the basic management controls necessary to allow an instance of an Aggregation Port to be managed, for the purposes of Link Aggregation.

    oAggregator If implemented, oAggregator is the top-most managed object class of the DTE portion of the containment tree shown in Figure 30–3. Note that this managed object class may be contained within another superior managed object class. Such containment is expected, but is outside the scope of this International Standard. The oAggregator managed object class provides the management controls necessary to allow an instance of an Aggregator to be managed.

    oAutoNegotiation The managed object of that portion of the containment trees shown in Figure 30–3 and Figure 30–4. The attributes, notifications, and actions defined in this subclause are contained within the MAU managed object.

    oGroup The group managed object class is a view of a collection of repeater ports.

    oMACControlEntity If implemented, and if oOAM is implemented, a single instance of oMACControlEntity is contained within oOAM. Otherwise, if implemented, and if oAggregator is implemented, oMACControlEntity is contained within oAggregator. Otherwise, if implemented, oMACControlEntity becomes the top-most managed object class of the DTE portion of the containment tree shown in Figure 30–3. Note that this managed object class may be contained within another superior managed object class. Such containment is expected, but is outside the scope of this International Standard.

    16 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    oMACControlFunctionEntityIf implemented, oMACControlFunctionEntity is contained within oMACControlEntity. The oMACControlFunctionEntity managed object class provides the management controls necessary to allow an instance of the MAC Control PAUSE function to be managed. Contained within oMACControlEntity. Each function defined and implemented within the MAC Control sublayer has an associated oMACControlFunctionEntity for the purpose of managing that function.

    oMACEntity If oMACControlEntity is implemented, oMACEntity is contained within oMACControlEntity. Otherwise, if oOAM is implemented, oMACEntity is contained within oOAM. Otherwise, if oAggregator is implemented, oMACEntity is contained within oAggregator. Otherwise, oMACEntity becomes the top-most managed object class of the DTE portion of the containment tree shown in Figure 30–3. Note that this managed object class may be contained within another superior managed object class. Such containment is expected, but is outside the scope of this International Standard.

    oMAU The managed object of that portion of the containment trees shown in Figure 30–3 and Figure 30–4. The attributes, notifications, and actions defined in this subclause are contained within the MAU managed object. Neither counter values nor the value of MAUAdminState is required to be preserved across events involving the loss of power.

    oMidSpan The top-most managed object class of the Midspan containment tree shown in Figure 30–54. Note that this managed object class may be contained within another superior managed object class. Such containment is expected, but is outside the scope of this standard.

    oMPCP If implemented, oMPCP is contained within oMACControlEntity. The oMPCP managed object class provides the management controls necessary to allow an instance of the Multi-Point MAC Control function to be managed.

    oOAM If implemented, and if oAggregator is implemented, oOAM is contained within oAggregator. An instance of this managed object class is present for each Aggregation Port that is part of the aggregation represented by the oAggregator instance. Otherwise, if implemented, oOAM becomes the top-most managed object class of the DTE containment tree shown in Figure 30–3. Note that this managed object class may be contained within another superior managed object class. Such containment is expected, but is outside the scope of this International Standard.

    oOMPEmulation If implemented, oOMPEmulation is contained within oMACEntity. The oOMPEmulation managed object class provides the management controls necessary to allow an instance of an OMPEmulation sublayer to be managed.

    oPHYEntity If oOMPEmulation is implemented, oPHYEntity is contained within oOMPEmulation. Otherwise oPHYEntity is cContained within oMACEntity. Many instances of oPHYEntity may coexist within one instance of oMACEntity; however, only one PHY may be active for data transfer to and from the MAC at any one time. oPHYEntity is the managed object that contains the MAU, PAF and PSE managed objects in a DTE.

    Copyright © 2004 IEEE. All rights reserved. 17

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    oPAF The oPAF managed object class provides the management controls necessary to allow an instance of a PME aggregation function (PAF) to be managed. The PAF managed object class also provides a view of a collection of PMEs.

    oPME The oPME managed object class provides the management controls necessary to allow an instance of a PME to be managed. The oPAF managed object contains the PME managed object in a DTE.

    oPSE The managed object of that portion of the containment trees shown in Figure 30–3, Figure 30–4, and Figure 30–54. The attributes and actions defined in this subclause are contained within the oPSE managed object.

    oPSEGroup The PSE Group managed object class is a view of a collection of PSEs.

    oRepeater The top-most managed object class of the repeater portion of the containment tree shown in Figure 30–4Figure30-3. Note that this managed object class may be contained within another superior managed object class. Such containment is expected, but is outside the scope of this standard.

    oRepeaterMonitor A managed object class called out by IEEE Std 802.1F-1993. See 30.1.2, oEWMAMetricMonitor.

    oRepeaterPort The repeater port managed object class provides a view of the functional link between the data transfer service and a single PMA. The attributes associated with repeater port deal with the monitoring of traffic being handled by the repeater from the port and control of the operation of the port. The Port Enable/Disable function as reported by portAdminState is preserved across events involving loss of power. The oRepeaterPort managed object contains the MAU managed object in a repeater set.

    NOTE—Attachment to nonstandard PMAs is outside the scope of this standard.

    oResourceTypeID A managed object class called out by IEEE Std 802.1F-1993. It is used within this clause to identify manufacturer, product, and revision of managed components that implement functions and interfaces defined within IEEE 802.3. The Clause 22 MII or Clause 35 GMII specifies two registers to carry PHY Identifier (22.2.4.3.1), which provides succinct information sufficient to support oResourceTypeID.

    oWIS The managed object of that portion of the containment tree shown in Figure 30–3. The attributes defined in this subclause are contained within the oMAU managed object.

    30.2.3 Containment

    Change the first paragraph of this subclause as follows (as modified by IEEE Std 802.3af-2003):

    A containment relationship is a structuring relationship for managed objects in which the existence of amanaged object is dependent on the existence of a containing managed object. The contained managedobject is said to be the subordinate managed object, and the containing managed object the superiormanaged object. The containment relationship is used for naming managed objects. The local containmentrelationships among object classes are depicted in the entity relationship diagrams, Figure 30–3, throughFigure 30–5 and Figure 30–4. These figures show the names of the object classes and whether a particularcontainment relationship is one-to-one, or one-to-many, or many-to-one. For further requirements on thistopic, see IEEE Std 802.1F-1993. PSE management is only valid in a system that provides management atthe next higher containment level, that is, either a DTE, repeater or Midspan with management.

    18 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    Replace Figure 30–3 with the following:

    Figure 30–3—DTE System entity relationship diagram

    oMACControlEntity30.3.3

    oMACEntity30.3.1

    Denotes one-to-many relationship

    oAggregator30.7.1

    oAggregationPort30.7.2

    oAggPortStats30.7.3

    oAggPortDebugInformation30.7.4

    oOAM30.3.6

    Denotes one-to-one relationship Denotes many-to-one relationship

    oMACControlFunctionEntity30.3.4

    oMPCP30.3.5

    oPHYEntity30.3.2

    oMAU30.5.1

    oAutoNegotiation30.6.1

    oResourceTypeID

    oResourceTypeID

    oWIS30.8.1

    oPSE30.9.1

    Present if MII

    oOMPEmulation30.3.7

    oPAF30.11.1

    oPME30.11.2

    Copyright © 2004 IEEE. All rights reserved. 19

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    Insert new Figure 30–4 as follows. Renumber existing figures as required.

    30.2.5 Capabilities

    Change the first paragraph of this subclause as follows (as modified by IEEE Std 802.3ae-2002 andIEEE Std 802.3af-2003):

    This standard makes use of the concept of packages as defined in ISO/IEC 10165-4: 1992 as a means ofgrouping behaviour, attributes, actions, and notifications within a managed object class definition. Packagesmay either be mandatory, or be conditional, that is to say, present if a given condition is true. Within thisstandard capabilities are defined, each of which corresponds to a set of packages, which are components ofa number of managed object class definitions and which share the same condition for presence.Implementation of the appropriate basic and mandatory packages is the minimum requirement for claimingconformance to IEEE 802.3 Management. Implementation of an entire optional capability is required inorder to claim conformance to that capability. The capabilities and packages for IEEE 802.3 Managementare specified in Tables 30–1 through 30–4 30–5.

    In Tables 30-1a, 30-1b, 30-1c, 30-1d and 30-1e change the DTE and MAU column heading ‘100/1000Mb/s Monitor Capability (Optional)’ to read ‘PHY Error Monitor Capability (Optional)’.

    Figure 30–4—Repeater entity relationship diagram

    Denotes one-to-many relationship

    Denotes one-to-one relationship

    oRepeater30.4.1

    oResourceTypeID oGroup30.4.2

    oRepeaterPort30.4.3

    oMAU30.5.1

    oAutoNegotiation30.6.1

    oPSE30.9.1

    oResourceTypeID

    Present if MII

    20 Copyright © 2004 IEEE. All rights reserved.

  • IEEE CSMA/CD Std 802.3ah-2004

    Insert the following entries to Table 30–1b after ‘aRateControlStatus’ (as modified by IEEE Std802.3ae-2002):

    Change the following entry in Table 30–1c (as modified by IEEE 802.3ae-2002):

    DTE Repeater MAU

    Bas

    ic P

    acka

    ge (

    Man

    dato

    ry)

    Man

    dato

    ry P

    acka

    ge (

    Man

    dato

    ry)

    Rec

    omm

    ende

    d P

    acka

    ge (

    Opt

    iona

    l)O

    ptio

    nal P

    acka

    ge (

    Opt

    iona

    l)A

    rray

    Pac

    kage

    (O

    ptio

    nal)

    Exc

    essi

    ve D

    efer

    ral P

    acka

    ge (

    Opt

    iona

    l)M

    ultip

    le P

    HY

    Pac

    kage

    (O

    ptio

    nal)

    PH

    Y E

    rror

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)B

    asic

    Con

    trol

    Cap

    abili

    ty (

    Man

    dato

    ry)

    Per

    form

    ance

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)A

    ddre

    ss T

    rack

    ing

    Cap

    abili

    ty (

    Opt

    iona

    l)10

    0/10

    00 M

    b/s

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)10

    00 M

    b/s

    Bur

    st M

    onito

    r C

    apab

    ility

    (O

    ptio

    nal)

    Bas

    ic P

    acka

    ge (

    Man

    dato

    ry)

    MA

    U C

    ontr

    ol P

    acka

    ge (

    Opt

    iona

    l)M

    edia

    Los

    s Tr

    acki

    ng P

    acka

    ge (

    Con

    ditio

    nal)

    Bro

    adba

    nd D

    TE

    MA

    U P

    acka

    ge (

    Con

    ditio

    nal)

    MII

    Cap

    abili

    ty (

    Con

    ditio

    nal)

    PH

    Y E

    rror

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)A

    uto-

    Neg

    otia

    tion

    Pac

    kage

    (M

    anda

    tory

    )

    aDeferControlAbility ATTRIBUTE GET X

    aDeferControlStatus ATTRIBUTE GET-SET X

    DTE Repeater MAU

    Bas

    ic P

    acka

    ge (

    Man

    dato

    ry)

    Man

    dato

    ry P

    acka

    ge (

    Man

    dato

    ry)

    Rec

    omm

    ende

    d P

    acka

    ge (

    Opt

    iona

    l)O

    ptio

    nal P

    acka

    ge (

    Opt

    iona

    l)A

    rray

    Pac

    kage

    (O

    ptio

    nal)

    Exc

    essi

    ve D

    efer

    ral P

    acka

    ge (

    Opt

    iona

    l)M

    ultip

    le P

    HY

    Pac

    kage

    (O

    ptio

    nal)

    PH

    Y E

    rror

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)B

    asic

    Con

    trol

    Cap

    abili

    ty (

    Man

    dato

    ry)

    Per

    form

    ance

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)A

    ddre

    ss T

    rack

    ing

    Cap

    abili

    ty (

    Opt

    iona

    l)10

    0/10

    00 M

    b/s

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)10

    00 M

    b/s

    Bur

    st M

    onito

    r C

    apab

    ility

    (O

    ptio

    nal)

    Bas

    ic P

    acka

    ge (

    Man

    dato

    ry)

    MA

    U C

    ontr

    ol P

    acka

    ge (

    Opt

    iona

    l)M

    edia

    Los

    s Tr

    acki

    ng P

    acka

    ge (

    Con

    ditio

    nal)

    Bro

    adba

    nd D

    TE

    MA

    U P

    acka

    ge (

    Con

    ditio

    nal)

    MII

    Cap

    abili

    ty (

    Con

    ditio

    nal)

    PH

    Y E

    rror

    Mon

    itor

    Cap

    abili

    ty (

    Opt

    iona

    l)A

    uto-

    Neg

    otia

    tion

    Pac

    kage

    (M

    anda

    tory

    )

    oMACControlFunctionPAUSEEntity managed object class (instance of oMACControlFunctionEntity) (30.3.4)

    Copyright © 2004 IEEE. All rights reserved. 21

  • IEEE Std 802.3ah-2004 AMENDMENT TO IEEE Std 802.3

    Insert the following new table after Table 30–4:

    Table 30–5—EFM Capabilities

    DTE MAU PME

    Mul

    ti-P

    oint

    Con

    trol

    Pro

    toco

    l Pac

    kage

    (C

    ondi

    tiona

    l)

    Ope

    ratio

    n A

    dmin

    istr

    atio

    n M

    aint

    enan

    ce P

    acka

    ge (

    Con

    ditio

    nal)

    Opt

    ical

    Mul

    tipoi

    nt E

    mul

    atio

    n P

    acka

    ge (

    Con

    ditio

    nal)

    Opt

    ical

    Mul

    tipoi

    nt E

    mul

    atio

    n M

    onito

    r P

    acka

    ge (

    Opt

    iona

    l)

    PC

    S C

    ode

    Err

    or M

    onito

    r P

    acka

    ge (

    Opt

    iona

    l)

    For

    war

    d E

    rror

    Cor

    rect

    ion

    Pac

    kage

    (C

    ondi

    tiona

    l)

    Bas

    ic P

    acka

    ge (

    Man

    dato

    ry)

    PM

    E A

    ggre

    gatio

    n P

    acka

    ge (

    Opt