IEEE-802.5T-2000.pdf

The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright © 2000 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 10 March 2000. Printed in the United States of America. Print: ISBN 0-7381-1743-9 SH94755 PDF: ISBN 0-7381-1744-7 SS94755 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 Std 802.5t-2000 (Amendment to ANSI/IEEE Std 802.5, 1998 Edition; ANSI/IEEE Std 802.5r, 1998 Edition; and ANSI/IEEE Std 802.5j, 1998 Edition) Information technology Telecommunications and information exchange between systems Local and metropolitan area networks Specifi c requirements Amendment to Part 5: Token Ring Access Method and Physical Layer Specifi cations Sponsor LAN/MAN Standards Committee of the IEEE Computer Society Approved 13 January 2000 IEEE-SA Standards Board Abstract: This supplement specifies the changes required to ANSI/IEEE Std 802.5, 1998 Edition, (Base standard) and ANSI/IEEE 802.5r, 1998 Edition, and ANSI/IEEE Std 802.5j, 1998 Edition, (Amendment 1 standard) to support 100 Mbit/s Dedicated Token Ring (DTR) operation. The Base standard, together with the Amendment 1 standard, specifies shared and dedicated (point-to-point) Token Ring operation at both 4 Mbit/s and 16 Mbit/s using either the TKP Access Protocol or the TXI Access Protocol. This supplement extends Token Ring operation to 100 Mbit/s for the DTR C- Port and Station using the TXI Access Protocol. Extensions to the medium access control (MAC) have been made to accommodate the requirements for high media rates (100 Mbit/s and above). Keywords: data processing interconnection, dedicated token ring, fi ll duplex operation, local area network (LAN), medium access control (MAC), 100 Mbit/s operation, token ring Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=Japan, IHS Not for Resale, 07/30/2008 02:45:14 MDTNo reproduction or networking permitted without license from IHS -,-,- IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Com- mittees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an interest in participating in the development of the standard. Use of an IEEE Standard is wholly voluntary. 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 fi ve years for revision or reaffi rmation. When a document is more than fi ve years old and has not been reaffi rmed, it is rea- sonable to conclude that its contents, although still of some value, do not wholly refl ect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE Standard. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affi liation with IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specifi c 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 all 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. 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-1331 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, Cus- tomer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; (978) 750-8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copy- right Clearance Center. Note: 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. The IEEE shall not be responsible for identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=Japan, IHS Not for Resale, 07/30/2008 02:45:14 MDTNo reproduction or networking permitted without license from IHS -,-,- Copyright © 2000 IEEE. All rights reserved. iii Introduction (This introduction is not part of IEEE Std 802.5t-2000, Information technologyTelecommunications and information exchange between systemsLocal and metropolitan area networksSpecifi c requirementsAmendment to Part 5: Token Ring Access Method and Physical Layer Specifi cations.) This standard is part of a family of standards for local and metropolitan area networks. The relationship between this standard and other members of the family is shown below. (The numbers in the fi gure refer to IEEE standard numbers.) This family of standards deals with the Physical and Data Link layers as defi ned by the International Organiza- tion for Standardization (ISO) Open Systems Interconnection (OSI) Basic Reference Model (ISO/IEC 7498-1:1994). The access standards defi ne seven types of medium access technologies and associated physi- cal media, each appropriate for particular applications or system objectives. Other types are under investigation. The standards defi ning the access technologies are as follows: IEEE Std 802 Overview and Architecture. This standard provides an overview to the family of IEEE 802 Standards. ANSI/IEEE Std 802.1B and 802.1k ISO/IEC 15802-2 LAN/MAN Management. Defi nes an OSI management-compatible architec- ture, and services and protocol elements for use in a LAN/MAN environment for performing remote management. ANSI/IEEE Std 802.1D ISO/IEC 15802-3 Media Access Control (MAC) Bridges. Specifi es an architecture and protocol for the interconnection of IEEE 802 LANs below the MAC service boundary. ANSI/IEEE Std 802.1E ISO/IEC 15802-4 System Load Protocol. Specifi es a set of services and protocol for those aspects of management concerned with the loading of systems on IEEE 802 LANs. IEEE Std 802.1F Common Defi nitions and Procedures for IEEE 802 Management Information ANSI/IEEE Std 802.1G ISO/IEC 15802-5 Remote Media Access Control Bridging . Specifi es extensions for the intercon- nection, using non-LAN communication technologies, of geographically sepa- rated IEEE 802 LANs below the level of the logical link control protocol. * Formerly IEEE Std 802.1A. DATA LINK LAYER PHYSICAL 802.2 LOGICAL LINK CONTROL 802.1 BRIDGING 802.1 MANAGEMENT 802 OVERVIEW 2) Clause 3 as amended by Clause 10 for the DTR C-Port or Station supporting the 4 Mbit/s or 16 Mbit/s media speeds; 3) Clause 3 as amended by Clause 10 and Clause 14 for the DTR C-Port or Station supporting the High Media Rate (HMR) media speeds. b) Support 48-bit addressing and use either a universally administered individual address or a locally administered individual address, as specified in 3.2.4. c) Recognize the first bit of the source address as indication of the presence of the routing information field in the frame format defined in 3.2.5. Note that the ability to generate or respond to frames with source routing information is optional. d) Exhibit external behavior corresponding to the system timing parameters specified as follows: 1) Clause 3 for the Classic station supporting the 4 Mbit/s or 16 Mbit/s media speeds, and using the TKP Access Protocol; 2) Clause 3 as amended by Clause 10 for the DTR C-Port or Station supporting the 4 Mbit/s or 16 Mbit/s media speeds, and using the TKP or TXI Access Protocols; 3) Clause 3 as amended by Clause 10 and Clause 14 for the DTR C-Port or Station supporting the HMR media speeds, and using the TXI Access Protocol. e) Exhibit external behavior corresponding to the Station Policy Flags and Variables specified as follows: 1) Clause 3 for the Classic station supporting the 4 Mbit/s or 16 Mbit/s media speeds, and using the TKP Access Protocol; 2) Clause 3 as amended by Clause 10 for the DTR C-Port or Station supporting the 4 Mbit/s or 16 Mbit/s media speeds, and using the TKP or TXI Access Protocols; 3) Clause 3 as amended by Clause 10 and Clause 14 for the DTR C-Port or Station supporting the HMR media speeds, and using the TXI Access Protocol. f) Implement capabilities corresponding to the Error Counters specified as follows: 1) Clause 3 for the Classic station supporting the 4 Mbit/s or 16 Mbit/s media speeds, and using the TKP Access Protocol; 2) Clause 3 as amended by Clause 10 for the DTR C-Port or Station supporting the 4 Mbit/s or 16 Mbit/s media speeds, and using the TKP or TXI Access Protocols; 3) Clause 3 as amended by Clause 10 and Clause 14 for the DTR C-Port or Station supporting the HMR media speeds and using the TXI Access Protocol. g) Perform the TKP and TXI Access Protocol functions as follows: 1) Classic Token Ring for 4 Mbit/s or 16 Mbit/s using the TKP Access Protocol operation speci- fied by the Station Operation Tables in ANSI/IEEE Std 802.5, 1998 Edition, Clause 4; 2) DTR for 4 Mbit/s or 16 Mbit/s using the TKP Access Protocol operation specified by the Sta- tion and Port Operation Tables in ANSI/IEEE Std 802.5r, 1998 Edition, and ANSI/IEEE Std 802.5j, 1998 Edition, 9.3 through 9.6; 3) DTR for 4 Mbit/s or 16 Mbit/s using the TXI Access Protocol operation specified by the Sta- tion and Port Operation Tables in ANSI/IEEE Std 802.5r, 1998 Edition, and ANSI/IEEE Std 802.5j, 1998 Edition, 9.2 and 9.3; 4) DTR for the HMR using the TXI Access Protocol operation specified by the Station and Port Operation Tables in 9.2 and 9.3 in this document. 1.7 Fibre optic media conformance requirements A 4 Mbit/s, 16 Mbit/s, and 100 Mbit/s media rate implementation, claiming conformance to this part of ANSI/IEEE Std 802.5, 1998 Edition, and operating in Station or Port mode, shall meet all appropriate parameters in Clause 13. Copyright The Institute of Electrical and Electronics Engineers, Inc. Provided by IHS under license with IEEELicensee=IHS Employees/1111111001, User=Japan, IHS Not for Resale, 07/30/2008 02:45:14 MDTNo reproduction or networking permitted without license from IHS -,-,- IEEE Std 802.5t-2000 LOCAL AND METROPOLITAN AREA NETWORKSAMENDMENT TO PART 5: Copyright © 2000 IEEE. All rights reserved. 4 1.8 Local regulation The supplier of a protocol implementation that is claimed to conform to this standard shall meet local safety and environmental regulations. Annex E provides some limited guidance in this area. Replace the title of 2.2 with the following two titles to cover all types of Stations and C-Ports: 2.2 C-Port and Station functional organization and data flow 2.2.1 4 Mbit/s and 16 Mbit/s classic Station functional organization and data flow The remainder of this clause remains unchanged. Add a new title after 2.2.1 to cover the 100 Mbit/s DTR C-Port and Station: 2.2.2 100 Mbit/s C-Port and Station functional organization and data flow Figure 2.2-1 and Figure 2.2-2 illustrate a C-Ports and Stations data flow, indicating which clauses of this standard address the various functions of a token ring C-Port or Station. Figure 2.2-1 is for a Station and C-Port connected using twisted-pair media. Figure 2.2-2 is for a Station and C-Port connected using fibre optic media. a) The PMC/PSC internal service interface (PM_UNITDATA.request; PM_UNITDATA.indication) defines the information exchange between the physical media components (PMC) specified in 9.7 and 9.8 and the physical signaling components (PSC) specified in 9.8. This service interface is de- fined in 9.8. b) The PSC/MAC internal service interface (PS_UNITDATA.indication, PS_UNITDATA.request) defines the information exchange between the PSC specified in 9.8 and the MAC sublayer specified in Clause 9 and Clause 14. Clause 14 defines frame formats and station facilities. Clause 9 also specifies the C-Ports Port Medium Access Control (PMAC) and Stations Station Medium Access Control (SMAC) protocol, which uses the formats and facilities defined in Clause 14 to receive and transmit information. This service interface is defined in 9.8. c) The PMAC/SMAC/PHY internal service interface (PM_STATUS.indication, PS_CONTROL.request, and PS_STATUS.indication) provides the control mechanism for the physical layer (PHY) func- tions by the MAC protocol, and the mechanism for indicating the status of the PHY functions to the MAC protocol. The PM_ STATUS.indication service interface is defined in 9.7. The PS_CONTROL.request and PS_STATUS.indication service interfaces are defined in 9.8. d) The PMAC/SMAC/LLC service interface (MA_UNITDATA.indication, MA_UNITDATA.request) is specified in ISO/IEC 15802-1 and is used as specified in 9.1. It defines the information exchange between the PMAC/SMAC sublayer and the Logical Link Control (LLC) sublayer. e) The PMAC/SMAC/Bridge service interface (M_UNITDATA.indication, M_UNITDATA.request, M_UNITDATA.response) is specified in IEEE Std 802.1d and is used as specified in 9.1. It defines the information exchange between the MAC and the interna