throbber
fEB 6
`
`LINDA HALL LIBRARY
`
`IEEE Standards for Local and Metropolitan Area Networks:
`
`Supplement to Carrier Sense Multiple Access with
`Collision Detection (CSMA'CD) Access Method and
`Physical Layer Specifications
`
`Type 10BASE-T Medium Attachment Unit (MAU)
`Protocol Implementation Conformance Statement
`(PICS) Proforma (Section 14.10)
`
`Sponsor
`Technical Committee on Computer Communications
`of the
`IEEE Computer Society
`
`Approved September 17, 1992
`IEEE Standards Board
`
`Abstract: This supplement to ISO/IEC 8802-3:1992 [ANSI/IEEE 802.3,1993 Edition] defmes
`conformance requirements for Type lOBASE-T Medium Attachment Unit (MAU) imple(cid:173)
`mentations for local and metropolitan area networks.
`Keywords: carrier sense multiple access with collision detection; Medium Attachment
`Unit (MAU); local area networks; metropolitan area networks
`
`The Institute of Electrical and Electronics Engineers, Inc.
`345 East 47th Street, New York, NY 10017-2394, USA
`Copyright e 1992 by the
`.
`Institute of Electrical and Electronics Engineers, Inc.
`All rights reserved. Published 1992
`Printed in the United States of America
`
`ISBN 1-55937-265-6
`
`Users of this standard may freely reproduce the PICS proforma in this
`section so that it may be used for its intended purpose and may further
`publish the completed PICS.
`
`December31, 1992
`
`SH15727
`
`Page 1
`
` Dell Inc.
` Exhibit 1015
`
`

`
`IEEE Standards documents are developed within the Technical
`Committees .df the IEEE Societies and the Standards Coordinating
`Committees of the IEEE Standards Board. Members of the committees
`serve voluntarily and without compensation. They are not necessar(cid:173)
`ily 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 which have ex(cid:173)
`pressed 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 five years for revision or :reaffir(cid:173)
`mation. When a document is more than five years old, and has not
`been reaffirmed, it is reasonable to con~lude that its contents, al(cid:173)
`though still of some value, do not wholly reflect the present state of the
`art. Users are cautioned to check to determine that they have the latest
`edition of any IEEE Standard.
`Comments for revision of IEEE Standards are welcome from any
`interested party, regardless of membership affiliation with IEEE.
`Suggestions for changes in documents should be in the form of a pro(cid:173)
`posed change of text, together with appropriate supporting comments.
`Interpretations: Occasionally questions may arise_._regarding the
`meaning of portions of standards as they relate to specific applica(cid:173)
`tions. When the need for interpretations is brought to the attention of
`IEEE, the Institute will initiate action to prepare appropriate re(cid:173)
`sponses. Since IEEE Standards represent a consensus of all con(cid:173)
`cerned interests, it is important to ensure that any interpretation has
`also received the concurrence of a balance of interests. For this rea(cid:173)
`son IEEE and the members of its technical committees are not able to
`provide an instant response to interpr,etation :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 Standards Board
`445 Hoes Lane
`P.O. Box 1331
`Piscataway, NJ 08555-1331
`USA
`
`IEEE Standards documents are adopted by the Institute of Electrical
`and Electronics Engineers without regard to whether their adoption
`may involve patents on articles, materials, or processes. Such
`adoption does not assume any liability to any patent owner, nor does it
`assume any obligation whatever to parties adopting the standards
`documents.
`
`Page 2
`
`

`
`Foreword
`
`(This foreword is not a part efiEEE Std 802.31-1992.)
`
`This standard is part of a family of standards for local and metropolitan area networks.
`The relationship between the standard and other members of the family is shown below.
`(The numbers in the figure refer to IEEE standard numbers.)
`
`?=
`a:>
`§~
`~ ..
`~if
`
`w a:
`~
`~
`::r:
`..
`(.)
`!:t
`~
`>
`a: w >
`0
`~
`
`1-
`
`z w
`::li
`~
`::l
`::IE
`~
`
`I
`[
`
`802.2 LOGICAL LINK
`
`802.1 BRIDGING
`
`DATA
`LINK
`LAYER
`
`802.3
`MEDIUM
`ACCESS
`
`802.4
`MEDIUM
`ACCESS
`
`802.5
`MEDIUM
`ACCESS
`
`802.6
`MEDIUM
`ACCESS
`
`802.3
`PHYSICAL
`
`802.4
`PHYSICAL
`
`802.5
`PHYSICAL
`
`802.6
`PHYSICAL
`
`PHYSICAL
`LAYER
`
`"'Formerly IEEE Std 802.1A.
`
`This family of standards deals with the physical and data link layers as defined by the
`International Organization for Standardization (ISO) Open Systems Interconnection Ba(cid:173)
`sic Reference Model (ISO 7498: 1984). The access standards define several types of
`medium access technologies and associated physical media, eadi appropriate for particu(cid:173)
`lar applications or system objectives. Other types are under investigation.
`The standards defining these technologies are as follows:
`
`• IEEE Std 802t:
`
`• IEEE Std 802.1D:
`
`• IEEE Std 802.1E:
`
`Overview and Architecture. This standard
`provides an overview to the family of IEEE 802
`standards. This document forms part of the 802.1
`scope of work.
`MAC Bridging. Specifies an architecture and
`protocol for the interconnection of IEEE 802
`LANs below the MAC service boundary.
`System Load Protocol. Specifies a set of services
`and protocol for those aspects of management
`concerned with the loading of systems on IEEE
`802 LANs.
`Logical Link Control
`• ISO 8802-2 [ANSI/IEEE Std 802.2]:
`• ISO/IEC 8802-3 [ANSI/IEEE Std 802.3]: CSMA/CD Access Methpd and Physical Layer
`Specifications
`• ISO/IEC 8802-4 [ANSI/IEEE Std 802.4]: Token Bus Access Method and Physical Layer
`Specifications
`
`t The 802 Architecture and Ov~rview Specification, originally known as IEEE Std 802.1A, has been renumbered
`as IEEE Std 802. This has been done to accommodate recognition of the base standard in a family of standards.
`References to IEEE Std 802.1A should be considered as references to IEEE Std 802.
`
`Page 3
`
`

`
`• IEEE Std 802.6:
`
`• ISOIIEC 8802-5 [ANSI/IEEE Std 802.5]: Token Ring Access Method and Physical Layer
`Specifications
`Metropolitan Area Network Access Method and
`Physical Layer Specifications
`Interoperable Local Area Network (LAN)
`Security (SILS), Secure Data Exchange
`In addition to the family of standards the following is a recommended practice for a
`common technology:
`
`• IEEE Std 802.10:
`
`• IEEE Std 802.7:
`
`IEEE Recommended Practice for Broadband
`Local Area Networks
`
`The reader of this document is urged to become familiar with the complete family of
`standards.
`
`Conformance Test Methodology
`
`A new standards series, identified by the number 1802, has been established to identify
`the conformance test methodology documents for the 802 family of standards. This makes
`the correspondence between the various 802 standards and their applicable conformance
`test requirements readily apparent. Thus the conformance test documents for 802.3 are
`numbered 1802.3, the conformance test documents for 802.5 will be 1802.5, and so on.
`
`Participants
`
`When the IEEE 802.3 Working Group approved IEEE Std 802.31-1992 (Section 14.10), it
`had the following membership:
`
`Patricia Thaler, Chair
`Mike Armstrong, Type JOBASE-T Task Force Chair and Editor
`Paul Nikolich, Vice Chair
`William Randle, Editorial Coordinator
`
`John Allen
`Keith Amundsen
`Richard Anderson
`Stephen J. Anderson
`Mark Bohrer
`Richard Bowers
`Richard Brand
`Richard S. Brehove
`SuzyBrown
`Thomas T. Butler
`R. R. (Bob) Campbell
`Luigi Canavese
`Ian Crayford
`Peter Cross
`Robert A. Curtis
`John DeCramer
`Tazio DeNicola
`Sanjay Dhawan
`Scott Dredge
`Tom Edsall
`Richard Ely
`Norman Erbacher
`
`Steve Evitts
`Steve Flickinger
`Mel Gable
`Mark Gerhold
`Sudhir Gupta
`Benny Hanigal
`Mogens Hansen
`G. R. Hartley
`W. B. Hatfield
`Carl G. Hayssen
`Chris Heegard
`Clarence J oh
`Richard John
`Donald C. Johnson
`ImreJuhasz
`Dieter Junkers
`Rainer Kaps
`Yongbum Kim
`Steven Koller
`William F. Kous
`David Kurcharczyk
`Hans Lackner
`
`Michael Lebar
`Michael Lee
`Richard Lefkowitz
`Richard M. Lena
`Yoseph Linde
`Terry D. Lockyer
`Sherry J. Lorei
`Andy J. Luque
`Mark Lynn
`Randall Magliozzi
`Charles Marsh
`BretA.Matz
`• Donna McMaster
`Mark Merrill
`Ray Mompoint
`Thinh Nguyenphu
`Mike O'Conner
`Lloyd Oliver
`Kazuyuki Ozawa
`Prasun K. Paul
`Tony Peatfield
`Anthony Peck
`
`Page 4
`
`

`
`David Poisner
`Peter Rautenberg
`Ivan Reede
`Jim Reinstedler
`Andreas Rende!
`Paul Rivett
`Gary Robinson
`Steven Robinson
`Michael Rothenberg
`Dieter W. Schicketanz
`Tom Schmitt
`
`Fredrick Scholl
`Sam Shen
`Nathan Silberman
`Semir Sirazi
`JosephS. Skorupa
`David A. Smith
`Graham Starkins
`Peter Tarrant
`Mark Taylor
`Geoffrey 0. Thompson
`Douglas H. Thomson
`
`Nathan Tobol
`Carlos A. Tomaszewski
`Nader Vijeh
`Bill Wager
`Robert Wataon
`Alan Wetzel
`Joseph AI Wiencko, Jr.
`Izumi Wilson
`Paul Woodruff
`Nobushige Yokota
`Hong Yu
`
`The following persons were on the balloting committee that approved this standard for
`submission to the IEEE Standards Board:
`
`W. B. Adams
`D. Aelmore
`H. S. Alkhatib
`K. Athul
`W. E. Ayen
`S. Bhatia
`A. 0. Bishop, Jr.
`A. L. Bridges
`R. Caasi
`M. U. Caglayan
`A.L.Carrato
`G. Carson
`B. J. Casey
`G. C. Chachis
`G. W. Cichanowski
`M. H. Coden
`K. Collins
`R. A. Conser
`R. Crowder
`L. F. M. De Moraes
`F. Deravi
`A. K. Dhawan
`N. I. Diihopoulos
`M.G. Duncan
`A.M. Dunn
`S.Dutta
`T. Dzik
`P. Eastman
`H. Eklund
`J. E. Emrich
`C. Fan
`J. W. Fendrich
`J. N. Ferguson
`S. Fineberg
`H. C. Folts
`S. J. Forney
`H. A. Freeman
`I. Fromm
`R. Gagliano
`D. G. Gan
`I. Ghansah
`P. Gonia
`A. Grund
`C. Guarnieri
`S. V. Halasz
`J. L. Hammond
`S. Harris
`C. M. Hay
`C. W. L. Hobbs
`L. A. Hollaar
`M. D. Hopwood
`C. Hsieh
`G. L. Hubscher
`
`P. L. Hutton
`R. J. lliff
`R. Jacobsen
`R. Jain
`J. R. Johnson
`R. Juvonen
`R. H. Karpinski
`G. C. Kessler
`M. Kezunovic
`J. Kolind
`V. Konangi
`P. Kornerup
`J. Kramp
`S. B. Kruger
`A. B. Lake
`L. M. Lam
`G. Langdon
`M. Lawler
`L. M. Leach
`J. Y. Lee
`M.E. Lee
`K. F. Li
`F. C. Lim
`P. Lin
`R. S. Little
`W. D. Livingston
`M. Lolli
`J.Loo
`D. C. Loughry
`N.C. Low
`J. F. P. Luhukay
`A.J.Luque
`C. R. Manson
`E. G. Marmol
`R. McBride
`K. C. McDonald
`W. McDonald
`D. B. Mcindoe
`R. H. Miller
`D. S. Millman
`A. N. Mishra
`H. L. W. Moh
`M.A. F. Morganti
`K. Mori
`D. A. J. Morris
`G. Moseley
`H. H. T. Mouftah
`C. E. Neblock
`R. Nelson
`A. A. Nilsson
`D. O'Mahony
`C. Oestereicher
`Y.Oh
`
`T. E. Phillips
`T. L. Phinney
`A. J. Pina
`R. Pirzada
`U. W. Pooch
`H. J. Pottinger
`R. S. Printis
`A. Putnins
`E. J. Reilly
`J. P. Riganati
`G. S. Robinson
`P. T. Robinson
`R. Rosenthal
`D. Rosich
`F. E. Ross
`C. Sagawa
`J. G. Sanz
`A. Sastry
`M. K. Saxena
`N. Schneidewind
`J. R. Schwab
`D. A. Sheppard
`R. M. Simmons
`W. T. Smith
`R. K. Southard
`C. Spurgeon
`M. Stephenson
`C. M. Stillebroer
`F. J. Strauss
`E. Sykas
`D. Sze
`N.P.Ta
`A. N. Tantawy
`S. R. Taylor
`P. Thaler
`G. 0. Thompson
`R. Tripi
`Wei-Tek Tsai
`M. Uchida
`L. D. Umbaugh
`J. T. Vorhies ·
`B. Vornbrock
`C. M. Weaver
`D. F. Weir
`• R. Wenig
`E. J. Whitaker
`M. Willett
`P. A. Willis
`G. B. Wright
`J. A. Wyatt
`J. Yang
`0. Yuen
`W. H. Yundt
`
`Page 5
`
`

`
`When the IEEE Standards Board approved this standard on September 17, 1992, it had the
`following membership:
`
`Marco W. Migliaro, Chair
`
`Donald C. Loughry, Vice Chair
`Andrew G. Salem, Secretary
`
`Dennis Bodson
`Paul L. Borrill
`Clyde Camp
`Donald C. Fleckenstein
`Jay Forster*
`David F. Franklin
`Ramiro Garcia
`Thomas L. Hannan
`
`"'Member Emeritus
`
`Donald N. Heirman
`Ben C. Johnson

`Walter J. Karplus
`Ivor N. Knight
`Joseph Koepfmger•
`Irving Kolodny
`D. N. "Jim• Logothetis
`Lawrence V. McCall
`
`T. Don Michael*
`John L. Rankine
`Wallace S. Read
`Ronald H. Reimer
`Gary S. Robinson
`Martin V. Schneider
`Terrance R. Whittemore
`Donald W. Zipse
`
`Also included are the following nonvoting IEEE Standards Board liaisons:
`
`Satish K. Aggarwal
`James Beall
`Richard B. Engelman
`David E. Soffrin
`Stanley Warshaw
`
`Kristin M. Dittmann
`IEEE Standards Project Editor
`
`Page 6
`
`

`
`ECTION
`
`PAGE
`
`··
`evisions to ISO/IEC 8802-3: 1992 [ANSI/IEEE Std 802.3, 1992 Edition] al)d
`EE Std 802.3i-1990 .................................................................................. 9
`
`14.10 Type 10BASE-T MAU Protocol Implementation Conformance Statement
`(PICS) Proforma ......................................................................... 9
`·· 14.10.1
`Introduction ................................................................... 9
`Identification of Implementation .......................................... 10
`14.10.2
`14.10.3
`Identification of the Protocol ............................................... 11
`14.10.4 PICS Proforma for 10BASE-T .............................................. 11
`
`Page 7
`
`

`
`IEEE Standards for Local and Metropolitan Area Networks:
`
`Supplement to Carrier Sense Multiple Access with
`Collision Detection (CSMNCD) Access Method and
`Physical Layer Specifications
`
`Type 10BASE-T Medium Attachment Unit (MAU)
`Protocol Implementation Conformance Statement
`(PICS) Proforma (Section 14.10)
`
`Revisions to ISO/IEC 8802-3 : 1992 [ANSJ/IEEE Std 802.3, 1992 Edition]
`and IEEE Std 802.3i-1990
`
`(These additions are part of IEEE Std 802.3i-1990.)
`
`The following additions add references for the 10BASE-T PICS proforma to the appro(cid:173)
`priate places in ISO/IEC 8802-3: 1992 [ANSI/IEEE Std 802.3, 1992 Edition]. The additions do
`not alter the specifications for existing systems.
`
`1.3 References
`Add these references to the list of references in 1.3:
`
`[31] ISO 9646-1 : 1991, Information technology-Open Systems Interconnection-Confor(cid:173)
`mance testing methodology and framework-Part 1: General concepts.
`
`[32] ISO 9646-2 : 1991, Information technology-Open Systems Interconnection-Confor(cid:173)
`mance testing methodology and framework-Part 2: Abstract test suite specification.
`NOTE: Upon incorporation into the base standard, all references will be renumbered.
`
`14.10 Type 10BASE-T MAU Protocol Implementation Conformance Statement (PICS)
`Proforma
`14.10.1 Introduction. To evaluate conformance of a particular implementation, it is
`necessary to state which capabilities and options have been implemented for a given OSI
`protocol. Such a statement is called a Protocol Implementation Conformance Statement
`(PICS).
`.
`This PICS proforma defines conformance requirements for Type 10BASE-T MAU im(cid:173)
`plementations. When the supplier completes this proforma, this document becomes the
`PICS for the specified implementation. The PICS is then used to perform a static
`conformance review of the implementation to determine that all mandatory features are
`implemented and that all conditional features are correctly supported dependent on the
`options claimed to be implemented. The PICS is used also as an aid in test-case selection
`and result analysis during. the dynamic conformance testing.
`
`9
`
`Page 8
`
`

`
`IEEE
`Std 802.31-1992
`
`SUPPLEMENT TO 802.3
`
`Separate MAU and link segment implementations are expected; submissions of either
`for testing do not require submission of the other. Furthermore, there is no current inten(cid:173)
`tion to produce an Abstract Test Suite from the section of the PICS proforma that discusses
`the link segment.
`14.10.1.1 Scope. This subsection provides the PICS proforma for Type 10BASE-T MAU
`specifications in accordance with the relevant guidance given in ISO 9646-2 [32).
`14.10.1.2 Reference. Type 10BASE-T MAU requirements referenced in this PICS pro(cid:173)
`forma are found in 14.2 through 14.8 and in 7.3 through 7.6 of this standard. Sections 7.3
`through 7.6 and 14.2 through 14.8 take precedence over 14.10 in case of any conflict.
`The use and the requirements for PICS proforma are defined in ISO 9646-1 [31) and ISO
`9646-2 [32].
`
`14.10.1.3 Definitions. This document uses the following terms defined in ISO 9646-1
`[31]:
`
`PICS proforma
`Protocol Implementation Conformance Statement (PICS)
`static conformance review
`dynamic conformance testing
`14.10.1.4 Conformance. The supplier of a MAU that is claimed to conform to Type
`10BASE-T MAU specifications shall complete a copy of the PICS proforma provided in this
`document and shall provide the information necessary to identify both the supplier and the
`implementation.
`
`14.10.2 Identification of Implementation. The MAU supplier shall complete the relevant
`fields in this section to identify the supplier and the particular MAU.
`
`Date:
`
`Supplierlnfannation
`
`Company Name:
`
`Representative Name:
`
`Address:
`
`Phone:
`
`FAX:
`
`E-mail:
`
`10
`
`Page 9
`
`

`
`CSMA/CD
`
`Implementation Information
`
`Implementation Name:
`
`IEEE
`Std 802.31-1992
`
`Implementation Identifier (including version/release):
`
`14.10.3 Identification of the· Protocol. The supplier will complete this section to identify
`the precise protocol implemented.
`Check Y [ ] if the MAU identified in the previous section implements each of the follow(cid:173)
`ing protocol standards; check N [ ] otherwise and attach an explanation.
`
`Carrier sense multiple access with collision detection (CSMA/CD)
`access method and physical layer specifications ISO/IEC 8802-3 : 1992
`[ANSI/IEEE Std 802.3, 1992 Edition]
`Twisted-Pair Medium Attachment Unit (MAU) and Baseband Medium Y [ ]
`Type lOBASE-T (IEEE Std 802.3i-1990)
`
`Y [
`
`N [ ]
`
`N [ ]
`
`List any other addenda or amendment documents implemented.
`
`14.10.4 PICS Proforma for 10BASE-T
`14.10.4.1 Abbreviations. The following abbreviations are used in the PICS proforma
`tables:
`
`Req • Requirement. This column indicates whether the conformance requirement of a
`particular clause in the standard is mandatory, optional, or conditional.

`
`Imp • Implementation. This column is filled in for a particular implementation with a
`"Y" or an "N" to indicate claimed conformance.
`
`M • Mandatory. Conformance cannot be met unless the parameter is implemented as spec(cid:173)
`ified.
`
`0 11111 Optional. The parameter may be implemented or not but, if implemented, it must be as
`stated in the standard.
`
`C m Conditional. If~ associated major option is implemented, this parameter must be im(cid:173)
`plemented.
`NOTE: Recommendations in the standard become "Optional" parameters in the context of a PICS proforma.
`
`14.10.4.2 PICS Completion Instructions and Implementation Statement. A supplier
`wishing to submit a 10BASE-T MAU for conformance testing against this standard must.
`fill in the column headed "Imp" in the PICS proforma tables and submit the resulting PICS
`with the equipment for test. This column must be filled in either with a "Y" for yes, indicat(cid:173)
`ing that the implementation is intended to meet the particular mandatory or optional re(cid:173)
`quirement, or "N" for no, indicating that the option has not been implemented (or enabled .
`where switchable) or that the requirement is not met. It should be noted that any instances
`
`11
`
`Page 10
`
`

`
`IEEE
`Std 802.31-1992
`
`SUPPLEMENT TO 802.3
`
`of "N" entered against a mandatory requirement will result in the implementation failing
`the static conformance test. In addition, the supplier must indicate below whether or not the
`implementation implements all the mandatory requirements.
`
`!This implementation implements all mandatory requirements
`
`y [
`
`]
`
`N [ ]
`
`14.10.4.3 Additional Information. Any additional information that is needed to en(cid:173)
`sure that the MAD or link segment submitted for test is configured as a 10BASE-T MAU or
`link segment should be entered into the PIXIT (Protocol Implementation eXtra Informa(cid:173)
`tion for Testing) document supplied by the conformance testing organization. Relevant in(cid:173)
`formation on 10BASE-T MAUs or link segments includes the following:
`
`(1) Enable/disable mechanisms for SQE Test
`(2) Enable/disable mechanisms for features that allow compatibility with nonstandard
`implementations
`(3) Operational instructions for DTEs or repeaters in cases where the MAU is embedded
`(4) Environmental conditions
`(5) Input voltage range for implementations with embedded MADs
`
`The above list is illustrative and is not intended to be either mandatory or exhaustive.
`14.10.4.4 References. ISO 9646-2 [32] requires that all PICS proforma clauses be
`individually identified. Tables have subsection headings and numbered clauses in order
`to meet this requirement.
`
`12
`
`Page 11
`
`

`
`I
`
`1
`2
`3
`4
`5
`6
`7
`
`1
`2
`
`3
`
`4
`
`5
`6
`7
`
`8
`9
`
`1
`2
`
`3
`
`4
`
`5
`6
`
`Function performed by MAU s
`attached to DTEs, not by MAU s
`attached to repeaters
`
`Value/comment
`DO circuit to TD circuit
`DO A positive relative to DO B
`causes TD+ positive relative
`to TD-
`2 bits max
`
`Second and following bits meet
`amplitude and jitter
`specifications
`2 bit times max
`2 bit times max
`Start of idle followed by a
`repeating sequence of silence
`and link test pulse
`16 ms ± 8 ms, ~±50 m V
`Normal start of packet
`requirements apply
`
`Value/comment
`RD circuit to DI circuit
`RD+ positive relative to RD-
`causes DI A positive relative
`toDIB
`5 bits max
`
`Second and following bits meet
`jitter specifications
`2 bit times max
`2 bit times max
`
`CSMA/CD
`
`14.10.4.5 PICS Proforma Tables for MAU
`14.10.4.5.1 MAU Functions
`
`IEEE
`Std 802.31-1992
`
`Req lm):
`
`Value/comment
`...
`
`"
`
`Section
`14.2.1
`
`Parameter
`MAU functions:
`Transmit
`Receive
`Loop back
`Collision Presence
`Jabber
`Link Integrity Test
`SQETest
`
`M
`M
`M
`M
`M
`M
`c
`
`14.10.4.5.2 Transmit Function
`
`Parameter
`Transmit path
`Transmit signal polarity
`
`Section
`14.2.1.1
`14.2.1.1
`
`Req Imp
`M
`M
`
`Start-up bit loss (DO to TD
`circuits)
`Transmit settling time
`
`14.2.1.1
`
`14.2.1.1
`
`Transmit steady-state delay
`Transmit delay variability
`TP_IDL
`
`14.2.1.1
`14.2.1.1
`14.2.1.1
`
`Silence duration
`TP _IDL termination with
`respect to start of packet
`
`14.2.1.1
`14.2.1.1
`
`14.10.4.5.3 Receive Function
`
`M
`
`M
`
`M
`M
`M
`
`M
`M
`
`Parameter
`Receive path
`Receive signal polarity
`
`Section
`14.2.1.2
`14.2.1.2
`
`Req Imp
`M
`M
`
`Start-up bit loss (RD to DI
`circuits)
`'
`Receive settling time
`
`Receive steady-state delay
`Receive delay variability
`
`14.2.1.2
`
`14.2.1.2
`
`14.2.1.2
`14.2.1.2
`
`M
`
`M
`
`M
`M
`
`13
`
`Page 12
`
`

`
`IEEE
`Std 802.31-1992
`
`SUPPLEMENT TO 802.3
`
`14.10A.5.4 Loop back Function
`Parameter
`1 Loopback function require-
`ments when RD = idle and
`DO= active
`2 Loopback bit loss (DO to Dl
`circuits)
`3 Loopback settling time
`
`Section Req Imp Value/comment
`DO signals to DI circuit
`14.2.1.3 M
`
`14.2.1.3 M
`
`5 bits max
`
`4 Loopback steady-state delay
`
`14.2.1.3 M
`
`14.2.1.3 M
`
`Second and following bits meet
`jitter specifications
`1 bit time max
`
`Parameter
`1 Collision Presence function
`requirements
`
`14.10A.5.5 Collision Detect Function
`Section Req Imp Value/comment
`CSO on Cl circuit if DO=active,
`14.2.1.4 M
`RD=active and in Link Test
`Pass state
`9 bit times max
`9 bit times max
`
`14.2.1.4 M
`14.2.1.4 M.
`
`2 Collision indication delay
`3 Collision indicate deassert
`delay
`4 CI circuit with no collision,
`SQE Test, or jabber
`5 DI circuit source switch delay
`from CSO assert
`6 DI circuit source switch delay
`from CSO deassert
`14.10.4.5.6 signal_quality_error Message Test Function. The following are
`conditional based on whether the signal_quality_error Message Test is to be performed
`(14.1 0.4.5.117).
`
`14.2.1.4 M
`
`IDL signal
`
`14.2.1.4 M
`
`9 bit times max
`
`14.2.1.4 M
`
`9 bit times max
`
`'"
`
`Parameter
`1 SQE Test induced TD or DI
`circuit signals
`2 SQE test wait timer range
`3 SQE_test timer range
`4 CI circuit during SQE Test
`5 SQE Test in Link Fail state
`
`14.10A.5.7 Jabber Function
`
`Section Req Imp Value/comment
`c
`14.2.1.5
`No extraneous signals
`permitted
`0.6 to 1.6 J!S
`5 to 15 bit times
`CSO signal
`CSO must not be sent
`
`14.2.1.5
`14.2.1.5
`14.2.1.5
`14.2.1.5
`
`c
`c
`c\
`c
`
`Parameter
`1 Jabber Function
`implementation
`2 Xmit max timer range
`14.2.1.6 M
`3 CI circuit during jabber
`14.2.1.6 M
`4 Unjab timer range
`14.2.1.6 M
`5 MAU Jabber Lockup Protection 14.2.1.6 M
`
`Section Req Imp Value/comment
`Self-interrupt of transmit and
`14.2.1.6 M
`loop back
`20 ms min, 150 ms max
`CSO signal
`0.5± 0.25 s
`Jabber not activated by the long-
`est permitted output specified
`in 9.6.5
`
`14
`
`Page 13
`
`

`
`CSMA/CD
`
`14.10.4.5.8 Link Integrity Test Function
`
`IEEE
`Std 802.31-1992
`
`Parameter
`1 Link loss timer
`Signals during detected
`failure:
`2 TD circuit
`3 DI circuit
`4 CI circuit
`
`M
`M
`M
`
`Section Req
`14.2.1.7 M
`14.2.1.7
`
`Imp
`
`Value/comment
`50 ms min, 150 ms max
`
`TP_IDL
`IDL
`IDL (except when jabber
`condition is also present)
`RD = active or consecutive link
`test pulses = 2 min, 10 max
`2to7ms
`25to150ms
`
`Ignore
`
`Reset link test pulse counter
`
`Disable
`Disable
`Disable
`Disable
`Disahl~
`Deferred until RD = idle and
`DO= idle
`Link Test Fail Reset
`Link test pulse not detected as
`data
`
`Imp
`
`Value/comment
`Meets requirements of Fig 14-3
`
`5 Link Test Fail state exit
`conditions
`6 Link test min timer range
`7 Link test max timer range
`Pulses outside acceptance
`window:
`8 Early while in Link Test Pass
`state
`9 Early or late while not in Link
`Test Pass state
`Link fail effect on MAU
`functions:
`10 Transmit
`11 Receive
`12 Loop back
`13 Collision Presence
`14 SQETest
`15 Link Test Fail Extend state
`exit condition
`16 Power-on state
`17 Pulse/data discrimination
`
`14.2.1.7 M
`
`14.2.1.7 M
`14.2.1.7 M
`14.2.1.7
`
`M
`
`M
`
`14.2.1.7
`
`M
`M
`M
`M
`M
`14.2.1.7 M
`
`14.2.1.7
`0
`14.2.1.7 M
`
`14.10.4.5.9 MAU State Diagram Requirements
`
`Parameter
`1 Transmit, Receive, Loopback,
`and Collision Presence
`Functions state diagram
`2 signal_quality _error Message 14.2.3
`Test Function state diagram
`
`Section Req
`14.2.3
`M
`
`3 Jabber Function J>tate diagram 14.2.3
`4 Link Integrity Test Function
`14.2.3
`state diagram
`
`,.
`
`15
`
`c
`
`M
`M
`
`Meets requirements of Fig 14-4.
`Conditional on whether or not
`the function is to be performed
`(14.1 0.4.5.117)
`Meets requirements of Fig 14-5
`Meets requirements of Fig 14-6
`
`Page 14
`
`

`
`IEEE
`Std 802.31-1992
`
`SUPPLEMENT TO 802.3
`
`14.10.4.5.10 AUI Requirements
`
`Parameter
`1 AUI implementation
`
`Section
`14.3
`
`Req Imp
`0
`
`2 AUI messages
`
`14.2.2
`
`M
`
`14.10.4.5.11 Isolation Requirements
`
`Value/comment
`If implemented refer to
`14.10.4.6
`Comply to 7 .2.1
`
`. Parameter
`1 Isolation, MDI leads to DTE
`Physical Layer circuits
`2 Resistance after breakdown
`test
`
`Section
`14.3.1.1
`
`Req Imp
`M
`
`14.3.1.1
`
`M
`
`Value/comment
`Any one of three tests listed in
`14.3.1.1
`2!: 2 Mil at 500 Vdc
`
`14.10.4.5.12 Transmitter Specification
`
`14.3.1.2.1
`
`Section
`Parameter
`1 Peak differential output voltage 14.3.1.2.1
`on TD circuit
`2 Harmonic content, all ones
`signal
`3 Output waveform, with scaling 14.3.1.2.1
`ofvoltage template
`4 Start of TP _IDL waveform, with 14.3.1.2.1
`each specified load, with and
`without twisted-pair model
`5 Link test pulse waveform, with 14.3.1.2.1
`each specified load, with and
`without twisted-pair model
`6 TD circuit differential o'iitput
`impedance
`Transmitter added timing
`jitter:
`7 Into 100 n through twisted-pair
`model
`8 Into 100 0
`9 Common-mode to differential-
`mode conversion
`10 TD circuit common-mode
`output voltage
`11 TD circuit common-mode
`rejection, 15 V peak 10.1 MHz
`sinusoid
`12 TD circuit fault. tolerance
`
`Req Imp
`M
`
`Value/comment
`2.2 to 2.8 v
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`M
`
`M
`
`M
`
`M
`
`M
`M
`
`M
`
`All harmonics 2!: 27 dB below
`fundamental
`Within Fig 14-9 template
`
`Within Fig 14-10 template,
`overshoot :::; +50 m V after
`excursion below -50 m V
`Within Fig 14-12 template,
`overshOot s +50 m V after
`excursion below -50 m V
`Reflection 2!: 15 dB below inci-
`dent, any simplex link segment
`
`±3.5 ns max
`
`±8 ns max
`2!: 29 -17 log10(f/1 0) dB,
`f=1-20 MHz, fin MHz
`<50 mV peak
`
`S 100 mV differential and
`S 1 nsjitter
`
`No damage from a short
`circuit
`300mAmax
`1000 V min, applied per
`Fig 14-15
`No extraneous signals on the
`TD circuit
`
`14.3.1.2.2
`
`14.3.1.2.3
`
`14.3.1.2.4
`
`14.3.1.2.5
`
`14.3.1.2.6
`
`14.3.1.2.7
`
`13 TD circuit short-circuit current 14.3.1.2.7
`14 TD circuit common-mode
`14.3.1.2. 7
`voltage withstand
`15 Power cycle behaVIor
`
`14.3.2.3
`
`16
`
`Page 15
`
`

`
`CSMA/CD
`
`14.10.4.5.13 Receiver Specification
`
`IEEE
`Std 802.31-1992
`
`Section
`14.3.1.3.1
`14.3.1.3.1
`14.3.1.3.1
`14.3.1.3.2
`
`Req Imp
`M
`M
`M
`M
`
`Value/comment
`Figs 14-16, 14-17, template
`At least ±13.5 ns
`:s; ±1.5 ns, RD to DI circuits
`Fig 14-12 template
`
`14.3.1.3.2
`
`Parameter
`1 RD circuit signal acceptance
`2 Received signal jitter accept
`3 Receiver added jitter
`4 RD circuit link test pulse
`acceptance
`RD circuit differential noise
`rejection:
`5 Signal (1)
`6 Signal (2)
`7 Signal (3)
`
`10 RD circuit common-mode
`rejection
`RD circuit fault tolerance:
`11 Short circuit
`12 Common-mode voltage
`
`8 Idle detection, RD circuit
`9 RD circuit differential input
`impedance
`
`14.3.1.3.3
`14.3.1.3.4
`
`M
`M
`M
`
`M
`M
`
`:s; 300 mVpeak
`s 6.2 V peak-to-peak, :s; 2 MHz
`Single cycle :s; 6.2 V, either
`phase, 2-15 MHz
`Within 2.3 bit times
`Reflected signal;;:: 15 dB below
`incident, any simplex link
`segment
`25 V peak-to-peak square wave
`to add :s; 2.5 ns jitter
`
`14.3.1.3.5
`
`M.
`
`14.3.1.3.6
`
`M
`M
`
`Indefinite short circuit
`1000 V impulse, applied per
`Fig 14-19
`
`14.10.4.5.14 MDI Requirements
`
`Section
`14.5.1
`14.5.1
`
`Parameter
`1 MDI connector
`MDI connector contact
`assignment:
`2 1
`3 2
`4 3
`5 6
`6 Crossover function
`implemented
`7 Crossover function indication 14.5.2
`
`14.5.2
`
`MDI-X connector contact
`assignment:
`8 1
`9 2
`10 3
`11 6
`
`'
`
`14.5.2
`
`~
`
`~ 17
`
`Req Imp
`M
`
`Valueltomment
`ISO 8877 [16] jack
`
`M
`M
`M
`M
`0
`c
`
`c
`c
`c
`c
`
`TD+
`TD-
`RD+
`RD-
`Remote MAU from DTE
`(recommended)
`X symbol on MDI connector.
`Conditional on crossover func-
`tion implementation. Refer to
`response to 14.10.4.5.14/6
`
`RD+
`RD-
`TD+
`TD-
`Conditional on crossover func-
`tion implementation. Refer to
`response to 14.10.4.5.14/6.
`
`Page 16
`
`

`
`IEEE
`Std 802.31-1992
`
`SUPPLEMENT TO 802.3
`
`14.10.4.5.15 Safety Requirements
`
`Parameter
`1 Safety grounding path
`
`Section
`14.7.2.2
`
`2 MAU labeling
`
`14.8
`
`Req Imp Value/comment
`c
`Must be via PG circuit. Condi-
`tional on AUI implementation.
`Refer to response for
`14.10.4.5.10/1 or PIXIT
`Data rate, current, any
`applicable safety warnings
`(recommended)
`Conforms to IEC 380, 435, or 950
`Creates no safety hazard
`
`0
`
`3 General safety
`4 Application of telephony
`voltages
`
`M
`14.7.1
`14.7.2.4 M
`
`'1
`
`I
`
`18
`
`Page 17
`
`

`
`CSMA/CD
`
`JEEE
`Std 802.31-1992
`
`14.10.4.6 PICS Proforma Tables for MAU AUI Characteristics. The whole of14.10.4.6
`is conditional on the AUI being implemented and accessible for testing. Refer to response
`for clause 14.10.4.5.1011 or PIXIT.
`14.10.4.6.1 Signal Characteristics
`
`Section Req Im Value/comment
`Parameter
`c
`1 Signaling rate (stated on label) 7.3.2
`10 Mb/s
`c
`2 CSO signal frequenc (on CI)
`10MHz±15%
`7.3.1.2
`c
`cycle
`3 CSO signal du
`60:40 worst case
`7.3.1.2
`14.10.4.6.2 DI and CI Driver Characteristics
`
`Parameter
`Differential output voltage:
`1 Loaded
`2 Idle state
`3 Start of idle
`4 Current into test load while idle 7.4.1.1
`5 Requirements after idle
`7.4.1.2
`6 Common-mode output voltage,
`7.4.1.3
`AC
`7 Differential output voltage,
`open circuit
`8 Common-mode output voltage,
`DC
`9 Fault tolerance
`10 Fault current
`
`7.4.1.5
`
`7.4.1.6
`7.4.1.6
`
`7.4.1.4
`
`Fig 7-11
`::> 40 m V into test load
`Fig 7-12
`4 rnA max after 80 BT
`First bit to Fig 7-11
`::> 40 mV peak. Fig 7-13
`
`13 Vpeak max
`::;; 5.5 v. Fig 7-13
`
`Fig 7-14
`::> 150 mA, any Fig 7-14 state
`
`Section Req Imp Value/comment
`7.4.1.1
`c
`c
`c
`c
`c
`c
`c
`c
`c
`c
`
`14.10.4.6.3 DO Receiver Characteristics
`
`Parameter
`1 Unsquelched threshold
`2 Squelch
`
`3 High-to-idle transition on
`DO circuit
`4 Differential input impedance
`atlOMHz
`
`Section Req Imp Value/comment
`c
`7.4.2.1
`160 m V max differential
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket