throbber
IEEE Std 802.3r-1996 .
`(Supplement to ISO/lEG 8802-3: 1996
`[ANSI/IEEE Std 802.3, 1996 Edition])
`
`Information technology-
`
`Telecommunications and information exchange between systems(cid:173)
`
`local and metropolitan area networks-Specific requirements-
`Supplement to Carrier Sense Multiple Access with
`Collision Detection {CSMAICD) Access Method
`and Physical layer Specifications-Type 1 OBASE5
`Medium Attachment Unit (MAU) Protocol
`Implementation Conformance Statement (PICS)
`Proforma {Subclause 8 .. 8)
`
`Sponsor
`LAN MAN Standards Committee
`of the
`IEEE Computer Society
`
`Approved 29 July 1996
`IEEE Standards Board
`
`SPECIFICATION
`
`FEB 13 1997
`LINDA HALl liBRARY
`
`Abstract: A Protocol Implementation Conformance Statement (PIGS) proforma for Type 1 OBASE5
`Medium Attachment Unit (MAU) (clause 8) is provided. The PIGS proforma is used to evaluate the
`conformance of a particular implementation of the standard.
`Keywords: dynamic conformance testing, medium attachment unit (MAU), PIGS proforma, proto(cid:173)
`col implementation conformance statement (PIGS), static conformance review, Type 10BASE5
`
`The Institute of Electrical and Electronics Engineers, Inc.
`345 East 47th Street, New York, NY 1 0017-2394, USA
`
`Copyright© 1996 by the Institute of Electrical and Electronics Engineers, Inc.
`All rights reserved. Published 1996. Printed in the United States of America.
`
`ISBN 1-55937-760-7
`
`No part of this publication may be reproduced in any form, in an electronic retrieval system or otheiWise, without the prior
`written permission of the publisher.
`
`Page 1
`
` Dell Inc.
` Exhibit 1016
`
`

`
`IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinat(cid:173)
`ing Committees of the IEEE 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 develop-
`ment 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 sub(cid:173)
`jected to review at least every five years for revision or reaffirmation. When a document is more
`than five years old and has not been reaffirmed, it is reasonable to conclude that its contents,
`although still of some value, do not wholly reflect the present state of the art. Users are cautioned to
`check to determine that they have the latest edition of any IEEE Standard.
`
`Comments for revision of IEEE Standards are welcome from any interested party, regardless of
`membership affiliation with IEEE. Suggestions for changes in doc~ments 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 specific applications. When the need for interpretations is brought to the attention of
`IEEE, the Institute will initiate action to prepare appropriate responses. Since IEEE Standards rep(cid:173)
`resent a consensus of all concerned interests, it is important to ensure that any interpretation has
`also received the concYrrence 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 Standards Board
`445 Hoes Lane
`P.O. Box 1331
`Piscataway, NJ 08855-1331
`USA
`
`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 all 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.
`
`Authorization to photocopy portions of any individual standard for internal or personal use is
`granted by the Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate
`fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact
`Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA;
`(508) 750-8400. Permission to photocopy portions of any individual standard for educational class(cid:173)
`room use can also be obtained thfough the Copyright Clearance Center.
`
`Page 2
`
`

`
`Introduction
`
`(This introduction is not part of IEEE Std 802.3r-1996.)
`
`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.)
`
`~
`0:
`:::;,
`(.)
`w
`(/)
`0
`C\i
`0
`co
`
`~
`
`Lu
`c:
`:::>
`1-
`(.)
`w
`1-
`:c
`(.)
`c:
`<
`ell
`~
`w
`~
`w
`e;
`"'
`
`0
`co
`
`1-
`z
`w
`:::E
`w
`C)
`<
`z
`<
`:::E
`C\i
`0
`co
`
`~
`
`802.2 LOGICAL LINK CONTROL
`
`802.1 BRIDGING
`
`DATA
`LINK
`LAYER
`
`802.3
`MEDIUM
`ACCESS
`
`802.4
`MEDIUM
`ACCESS
`
`802.5
`MEDIUM
`ACCESS
`
`802.6
`MEDIUM
`ACCESS
`
`802.9
`MEDIUM
`ACCESS
`
`802.11
`MEDIUM
`ACCESS
`
`802.12
`MEDIUM
`ACCESS
`
`802.12
`802.11
`802.9
`802.6
`802.5
`802.4
`802.3
`PHYSICAL PHYSICAL PHYSICAL PHYSICAL PHYSICAL PHYSICAL 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 Organi(cid:173)
`zation for Standardization/International Electrotechnical Commission (ISOIIEC) Open Systems Intercon(cid:173)
`nection Basic Reference Model (ISOIIEC 7498-1: 1994). The access standards define several types of
`medium access technologies and associated physical media, each appropriate for particular applications or
`system objectives. Other types are under investigation.
`
`The standards defining the technologies noted above are as follows:
`
`• IEEE Std 802
`
`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.
`
`• ANSI/IEEE Std 802.1B
`and 802.1k
`[ISOIIEC 15802-2]
`
`LAN/MAN Management. Defines an Open Systems Interconnection (OSI)
`management-compatible architecture, and services and protocol elements
`for use in a LAN/MAN environment for performing remote management.
`
`• ANSI/IEEE Std 802.1D
`[ISOJIEC 10038]
`
`MAC Bridging. Specifies an architecture and protocol for the interconnec(cid:173)
`tion of IEEE 802 LANs below the MAC service boundary.
`
`• ANSI/IEEE Std 802.1E
`[ISOJIEC 15802-4]
`
`System Load Protocol. Specifies a set of services and protocol for those
`aspects of management concerned with the loading of systems on IEEE
`802LANs.
`
`• ANSI/IEEE Std 802.2
`[ISOJIEC 8802-2]
`
`• ANSI/IEEE Std 802.3
`[ISO/IEC 8802-3]
`
`Logical Link Control
`
`CSMAICD Access Method and Physical Layer Specifications
`
`iii
`
`Page 3
`
`

`
`• ANSI/IEEE Std 802.4
`[ISOIIEC 8802-4]
`
`• ANSI/IEEE Std 802.5
`[ISOIIEC 8802-5]
`
`Token Passing Bus Access Method and Physical Layer Specifications
`
`. Token Ring Access Method and Physical Layer Specifications
`
`• ANSI/IEEE Std 802.6
`[ISOIIEC 8802-6]
`
`Distributed Queue Dual Bus Access Method and Physical Layer
`Specifications
`
`• ANSI/IEEE Std 802.9
`[ISO/IEC DIS 8802-9]
`
`Integrated Services (IS) LAN Inteiface at the Medium Access Control
`(MAC) and Physical (PHY) Layers
`
`• ANSI/IEEE Std 802.10
`
`Interoperable LAN/MAN Security
`
`• ANSI/IEEE Std 802.12
`
`Demand Priority Access Method, Physical Layer and Repeater
`Specifications
`
`In addition to the family of standards, the following is a recommended practice for a common Physical
`Layer technology:
`
`• IEEE Std 802.7
`
`IEEE Recommended Practice for Broadband Local Area Networks
`
`The following additional working groups have authorized standards projects under development:
`
`• IEEE 802.11
`
`• IEEE 802.14
`
`Wireless LAN Medium Access Control (MAC) Sublayer and Physical
`Layer Specifications
`
`Standard Protocol for Cable-TV Based Broadband Communication
`Network
`
`The reader of this standard is urged to become familiar with the complete family of standards.
`
`Conformance test methodology
`
`An additional standards series, identified by the number 1802, has been established to identify the
`conformance test methodology documents for the 802 family of standards. Thus the conformance test
`documents for 802.3 are numbered 1802.3.
`
`IEEE Std 802.3r-1996
`
`At the time this standard was published, the complete IEEE 802.3 standard consisted of the following pub(cid:173)
`lished documents:
`
`• ISOIIEC 8802-3: 1996
`
`Information technology-Telecommunications and information exchange
`between systems-Local and metropolitan area networks-Specific
`requirements-Part 3: Carrier sense multiple access with collision detec(cid:173)
`tion (CSMAICD) access method and physical layer specifications
`
`• IEEE Std 802.3u-1995
`
`Media Access Control (MAC) Parameters, Physical Layer, Medium
`Attachment Units, and Repeater for I 00 Mb/s Operation, Type I OOBASE-T
`
`iv
`
`Page 4
`
`

`
`• IEEE Std 802.3r-1996
`
`Supplement to Carrier Sense Multiple Access with Collision Detection
`(CSMAICD) Access Method and Physical Layer Specifications-Type
`JOBASES Medium Attachment Unit (MAU) Protocol Implementation Con(cid:173)
`formance Statement (PICS) Proforma (Subclause 8.8)
`
`Information on the current revision state of the standard may be obtained from
`
`Secretary, IEEE Standards Board
`
`P. 0. Box 1331
`
`445 Hoes Lane
`
`Piscataway, NJ 08855-1331
`
`USA
`
`IEEE 802 committee working documents are available from the IEEE and from
`
`IEEE Document Distribution Service
`
`c/o Alpha Graphics
`
`A'ITN: P. Thrush
`
`10201 N. 35th Ave.
`
`Phoenix, AZ 85051
`
`USA
`
`The following is a list of participants in the 802.3 Working Group when this standard was balloted. Voting
`members at the time of publication are marked with an asterisk (*).
`
`Patlicia Thaler, Chair*
`
`Imre Juhasz, Chair, Conformance Task Force
`
`William Randle, Task Force Editor
`
`Karen Amavisca
`Stephen J. Anderson
`Mike Armstrong*
`Mogens Cash Balsby
`Richard Bowers*
`Richard Brand
`Jack Brown
`Kathy de Graaf
`Sanjay Dhawan
`Steve Evitts
`Steve Flickinger
`Chris Heegard
`Wolfgang Heidasch
`Steve Horowitz
`Clarence Joh
`Dieter Junkers
`
`**Current Chair
`
`YongbumKim
`Hans Lacker*
`David Law*
`Michael Lebar
`Michael Lee
`Yoseph L. Linde
`Andy J. Luque*
`Donna McMaster
`Mark Merrill
`Paul Nikolich*
`Lloyd Oliver*
`Prasun K. Paul
`Tony Peatfield*
`Brian Ramelson
`Brian J. Ramsey
`Peter Rautenberg*
`
`Jim Reinstedler
`Gary Robinson*
`Michael Rothenberg
`Dieter W. Schicketanz
`Fredrick Scholl
`Martin Siegmund
`Joseph S. Skorupa
`Dinah Sloan
`David A. Smith
`David Stein
`Steve Storozum
`Geoffrey 0. Thompson**
`Nathan Tobol
`NadarVijeh
`Ikuo Wakayama
`Paul Woodruff
`
`v
`
`Page 5
`
`

`
`The following persons were on the balloting committee:
`
`DonAelmore
`Kithsiri Athulathmu
`James Carlo
`GeorgeS. Carson
`Robert S. Crowder
`Paul Eastman
`John E. Emrich
`Philip H. Enslow
`Harvey A. Freeman
`Robert J. Gagliano
`Julio Gonzalez Sanz
`ClarkM. Hay
`Paul L. Hutton
`Gary C. Kessler
`YongbumKim
`Stephen B. Kruger
`
`Randolph S. Little
`Donald C. Loughry
`William C. McDonald
`David S. Millman
`W. Melody Mob
`Kinji Mori
`David J. Morris
`Charles Oestereicher
`Art Pina
`VikramPunj
`Yang Qianli
`Brian Ramelson
`Eugene J. Reilly
`John P. Riganati
`Gary S. Robinson
`
`Daniel Rosich
`Floyd E. Ross
`Alfred Y. Rozemeijer
`Frederick E. Sauer
`Gregory D. Schumacher
`Saragur M. Srinidhi
`Clay Stocklin
`Peter Sugar
`Efstathiols D. Sykas
`Geoffrey 0. Thompson
`Robert C. Tripi
`Mark-Rene Uchida
`James T. Vorhies
`Raymond Wenig
`Earl J. Whitaker
`OrenYuen
`
`The final conditions for approval of this standard were met on 29 July 1996. This standard was conditionally
`approved by the IEEE Standards Board on 20 June 1996, with the following membership:
`
`Donald C. Loughry, Chair
`
`Richard J, Holleman, Vice Chair
`Andrew G. Salem, Secretary
`
`E. G. "AI" Kiener
`Joseph L. Koepfinger*
`Stephen R. Lambert
`Lawrence V. McCall
`L. Bruce McClung
`Marco W. Migliaro
`Mary Lou Padgett
`John W. Pope
`
`Jose R. Ramos
`Arthur K. Reilly
`Ronald H. Reimer
`Gary S. Robinson
`Ingo Rusch
`JohnS. Ryan
`Chee Kiow Tan
`Leonard L. Tripp
`Howard L. Wolfman
`
`Gilles A. Baril
`Clyde R. Camp
`Joseph A. Cannatelli
`Stephen L. Diamond
`Harold E. Epstein
`Donald C. Fleckenstein
`Jay Forster*
`Donald N. Heirman
`Ben C. Johnson
`
`*Member Emeritus
`
`Also included are the following nonvoting IEEE Standards Board liaisons:
`
`Satish K. Aggarwal
`
`Alan H. Cookson
`
`Chester C. Taylor
`
`Lisa S. Young
`
`IEEE Standards Project Editor
`
`vi
`
`Page 6
`
`

`
`Contents
`
`CLAUSE
`
`PAGE
`
`8.8
`
`Protocol Implementation Conformance Statement (PICS) proforma for clause 8, Medium Attachment
`Unit and baseband medium specifications, Type 10BASE5 ............................................................... 1
`
`8.8.1 Overview .............................................................................................................................................. 1
`
`8.8.2 Abbreviations and special symbols ....................................................................................... 2
`8.8.3
`Instructions for completing the PICS proforma .................................................................... 2
`8.8.4
`Identification .......................................................................................................................... 3
`PICS proforma tables for MAD ............................................................................................ 4
`8.8.6
`PICS proforma tables for MAD AUI characteristics .......................................................... 12
`8.8.7
`8.8.8
`PICS proforma tables for 10BASE5 coaxial cable .............................................................. 15
`
`vii
`
`Page 7
`
`

`
`Information technology-
`
`Telecommunications and information exchange between systems(cid:173)
`
`local and metropolitan area networks-Specific requirements-
`
`Supplement to Carrier Sense Multiple Access with
`Collision Detection {CSMAICD) Access Method and
`Physical Layer Specifications-Type 1 OBASE5
`Medium Attachment Unit {MAU) Protocol
`Implementation Conformance Statement {PICS)
`Proforma {Subclause 8.8)
`
`(These additions are part ofiSO/IEC 8802-3: 1996 [ANSI/IEEE Std 802.3, 1996 Edition].)
`
`8.8 Protocol Implementation Conformance Statement (PICS) proforma for clause 8,
`Medium Attachment Unit and baseband medium specifications, Type 10BASE51
`
`8.8.1 Overview
`
`The supplier of a protocol implementation that is claimed to conform to Type 10BASE5 MAU (clause 8)
`specifications shall complete the following PICS proforma.
`
`A completed PICS proforma is the PICS for the implementation in question. The PICS is a statement of
`which capabilities and options of the protocol have been implemented. The PICS can be used for a variety of
`purposes by various parties, including the following:
`
`As a checklist by the protocol implementor, to reduce the risk of failure to conform to the International
`Standard through oversight;
`
`As a detailed indication of the capabilities of the implementation, stated relative to the common basis
`for understanding provided by the standard PICS proforma, by the supplier and acquirer, or potential
`acquirer, of the implementation;
`
`As a basis for intially checking the possibility of interworking with another implementation by the
`user, or potential user, of the implementation (note that, while interworking can never be guaranteed,
`failure to interwork can often be predicted from incompatible PICs);
`
`As the basis for selecting appropriate tests against which to assess the claim for conformance of the
`implementation, by a protocol tester.
`
`1Copyright release for PICS proformas: Users of this standard may freely reproduce the PICS proforma in this subclause so that it may
`be used for its intended purpose and may further publish the completed PICS.
`
`1
`
`Page 8
`
`

`
`SUPPLEMENT TO 802.3
`
`IEEE
`Std 802.3r-1996
`
`8.8.2 Abbreviations and special symbols
`
`8.8.2.1 Status symbols
`
`The following abbreviations are used in the PICS proforma tables:
`
`M
`
`0
`
`mandatory
`
`optional
`
`0. <n> optional, but support of at least one of the group of options labeled by the same numeral <n> is
`required
`
`X
`
`prohibited
`
`<item>: conditional-item symbol, dependent upon the support for <item>
`
`logical negation, applied to a conditional item symbol
`
`8.8.2.2 Abbreviations
`
`Ref
`
`reference section
`
`8.8.3 Instructions for completing the PICS proforma
`
`8.8.3.1 General structure of the PICS proforma
`
`The structure of this PICS proforma is based on the guidelines given in ISO/IEC 9646-2: 1994 and ISO/IEC
`JTC1/SC6 N 7359. The first part of the PICS proforma, Implementation Identification and Protocol
`Summary, is to be completed as indicated with the information necessary to identify fully both the supplier
`and the particular MAU.
`
`The main part of the PICS proforma is a fixed-format questionnaire. Each item is identified by an item
`reference in the first column; the second column contains the question to be asked or the parameter to be
`measured; the third column contains the reference(s) to the material that specifies the item in the main body
`of ISOIIEC 8802-3; the fourth column records the status of the item-whether support is mandatory,
`optional, prohibited, or conditional-and provides space for the answers; the fifth column provides
`additional comments and/or value(s) for measurable parameters. The tables below group related items into
`separate subsubclauses. This satisfies the requirement of ISOIIEC 9646-2 that all PICS proforma clauses be
`individually identified.
`
`A supplier wishing to submit a 10BASE5 MAU for conformance testing against this standard must fill in the
`column headed Support in the PICS proforma tables and submit the resulting PICS with the equipment for
`test. One of the boxes in this column must be checked, with Yes indicating that the implementation is intended
`to meet the particular mandatory or optional requirement, No indicating that the option has not been imple(cid:173)
`mented (or enabled where switchable) or that the requirement is not met, or N/A indicating the item is not
`applicable (for example, an item that is conditional). It should be noted that any instances of No checked
`against a mandatory requirement will result in the implementation failing the static conformance test.
`
`8.8.3.2 Additional information
`
`Any additional information that is needed to ensure that the MAU or the coaxial cable submitted for test is
`configured as a 10BASE5 MAU or coaxial cable should be entered into the PIXIT (Protocol Implementation
`eXtra Information for Testing) d()cument supplied by the conformance testing organization. Relevant infor(cid:173)
`mation on 10BASE5 MAUs includes the following:
`
`2
`
`Page 9
`
`

`
`CSMNCD
`
`IEEE
`Std 802.3r-·t996
`
`Enable/disable mechanisms for SQE Test
`a)
`b) Enable/disable mechanisms for features that allow compatibility with nonstandard implementations
`c) Operational instructions for DTEs or repeaters in cases where the MAU is embedded
`d)
`Environmental conditions
`e)
`Power supply voltage range
`
`The above list is illustrative and is neither mandatory nor exhaustive.
`
`8.8.3.3 Exception information
`
`It may occasionally happen that a supplier will wish to answer an item with mandatory or prohibited status
`(after any conditions have been applied) in a way that conflicts with the indicated requirement. No pre(cid:173)
`printed answer will be found in the Support column for this. Instead, the supplier shall write the missing
`answer into the Support column, together with an X<i> reference to an item of Exception Information, and
`shall provide the appropriate rationale in the Exception item itself.
`
`An implementation for which an Exception item is required in this way does not conform to ISO!IEC
`8802-3: 1996.
`
`8.8.3.4 Conditional items
`
`The PICS proforma contains a number of conditional items. These are items for which both the applicability
`of the item itself, and its status if it applies-mandatory, optional, or prohibited-are dependent upon
`whether or not certain other items are supported.
`
`Individual conditional items are indicated by a conditional symbol of the form "<item>:<s>" in the Status
`column, where "<item>" is the section number and item reference that appears in the first column of the
`table for some other item, and "<s>" is a status symbol, M, 0, O.<n>, or X. The "!" symbol, prefixed to an
`item reference, means logical negation.
`
`If the item referred to by the conditional symbol is marked as supported, the conditional item is applicable,
`and its status is given by "<s>"; the support column is to be completed in the usual way. Otherwise, the con(cid:173)
`ditional item is not relevant and the Not Applicable (N/ A) answer is to be marked.
`
`Each item whose reference is used in a conditional symbol is indicated by an asterisk in the Item column.
`
`8.8.4 Identification
`
`8.8.4.1 Implementation identification
`
`The MAU supplier shall complete the relevant fields in this section to identify the supplier and the particular
`MAU.
`
`Supplier
`
`Contact point for queries about the PICS
`
`Implementation name(s) and version(s)
`
`3
`
`Page 10
`
`

`
`IEEE
`Std 802.3r-1996
`
`8.8.4.2 Protocol summary
`
`SUPPLEMENT TO 802.3
`
`The supplier will complete this section to identify the precise protocol implemented.
`
`Identification of protocol specification
`
`ISO/IEC 8802-3: 1996, Medium Attachment Unit and
`baseband medium specifications, Type 10BASE5
`(clause 8)
`
`Identification of amendments and corrigenda to this
`PICS proforma which have been completed as part of
`this PICS
`
`Have any Exception items been required?
`(The answer Yes means that the implementation does not
`conform to ISO/IEC 8802-3 : 1996)
`
`Yes []No []
`
`Date of Statement
`
`8.8.5 Global statement of conformance
`
`The supplier must indicate below whether or not the implementation implements all the mandatory require(cid:173)
`ments. Answering No to this question indicates nonconformance to the protocol specification. Nonsupported
`mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is
`non-conforming.
`
`This implementation meets all mandatory requirements
`
`Yes []No []
`
`8.8.6 PICS proforma tables for MAU
`
`8.8.6.1 MAU compatibility
`
`Item
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/comment
`
`MAU intended for
`attachment to
`repeater
`
`Monitor Function
`supported
`
`AUI Circuit CO
`supported
`
`SQETest
`supported
`
`9.4.1
`
`0
`
`0
`
`8.8.6.1/2
`:M
`!8.8.6.112
`:0
`
`8.8.6.111
`:X
`!8.8.6.111
`:M
`
`Yes [] No []
`
`Yes[] No []
`
`N/A []
`Yes [] No []
`N/A []
`Yes[] No []
`
`N/A []
`Yes [] No []
`N/A []
`Yes [] No []
`
`Required for
`Monitor function
`
`Function not
`performed for
`MAUs attached to
`repeaters
`
`*1
`
`*2
`
`*3
`
`4
`
`4
`
`Page 11
`
`

`
`CSMAICD
`
`8.8.6.2 Transmit function
`
`IEEE
`Std 802.3r-1996
`
`Item
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/comment
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`Transmit path
`
`8.2.1.1
`
`Transmit signal polarity
`
`8.2.1.1
`
`Start-up bit loss
`(DO to coaxial cable)
`
`8.2.1.1
`
`Transmit settling time
`
`8.2.1.1
`
`Transmit steady-state
`delay
`
`Start-up bit loss
`(DO to coaxial cabl~)
`variability
`
`No extraneous signal
`on the coaxial media
`after DO idle
`
`Start collision presence
`state
`
`Collision presence
`state duration
`
`8.2.1.1
`
`8.2.1.1
`
`8.2.1.1
`
`8.2.1.1
`
`8.2.1.1
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`Yes [] No []
`
`Yes [] No []
`
`DO circuit to coaxial
`cable
`
`DO A positive relative
`to DO B causes more
`positive voltage on the
`coaxial medium
`
`Yes [] No []
`
`2 bits max
`
`Yes [] No []
`
`Second and following
`bits meet amplitude and
`jitter specifications
`
`Yes [] No []
`
`1/2 bit times max
`
`Yes [] No []
`
`2 bits max between
`packets separated by
`::;96BT
`
`Yes [] No []
`
`Yes [] No []
`
`Within 0.6 J.lS to 1.6 J.lS
`after idle
`
`Yes [] No []
`
`5-15 bit times
`
`5
`
`Page 12
`
`

`
`IEEE
`Std 802.3r-1996
`
`8.8.6.3 Receive function
`
`SUPPLEMENT TO 802.3
`
`Item
`
`Parameter
`
`Ref~rence
`
`Status
`
`Support
`
`Value/comment
`
`Direct coupling of
`signal from medium to
`the receiver
`
`AC coupling from the
`receiver to AUI
`interface
`
`8.2.1.2
`
`8.2.1.2
`
`Start-up bit loss
`(coaxial cable to Dl)
`
`8.2.1.2
`
`Receive settling time
`
`8.2.1.2
`
`Receive steady-state
`delay
`
`Start-up bit loss
`(coaxial cable to DI)
`variability
`
`8.2.1.2
`
`8.2.1.2
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`Receive signal polarity
`
`8.2.1.2
`
`M
`
`Edge jitter
`
`Receive function while
`transmitting
`
`8.2.1.2
`
`8.2.1.2
`
`M
`
`M
`
`.Yes []No []
`
`Yes []No []
`
`Yes []No []
`
`5 bits max
`
`Yes []No []
`
`Second and following bits meet
`jitter specifications
`
`Yes []No []
`
`1/2 bit times max
`
`Yes []No []
`
`5 bits max between packets
`separated by ::;; 96 BT
`
`Yes []No [] More positive voltage on the
`coaxial cable will convert as DI
`A positive relative to DI Bon
`the DI circuits
`
`Yes []No [] MAU receiver + cable
`introduce ::;; 6 ns
`
`Yes []No []
`
`I
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`6
`
`Page 13
`
`

`
`CSMA/CD
`
`8.8.6.4 Collision function
`
`IEEE
`Std 802.3r-1996
`
`Item
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/commimt
`
`Collision absence
`
`8.2.1.3
`
`M
`
`Yes []No []
`
`IDL signal on the CI circuit, unless
`sending mau_not_available
`
`8.8.6.1/1
`:X
`!8.8.6.1/1
`:M
`
`N/A []
`Yes []No []
`N/A []
`Yes []No []
`
`CSO on CI circuit at BR +25%,
`-15% with a duty cycle not worse
`than 40/60 ratio with <': 2 MAUs
`transmitting
`
`M
`
`Yes []No []
`
`NoCSOon CI
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`Collision Presence
`function require-
`ments
`
`8.2.1.3
`
`No collision
`detection with
`single transmitter
`
`Collision assertion
`after transmission
`of <': 20 bit times
`
`8.2.1.3
`8.2.2.2.4
`
`8.2.1.3
`8.2.2.2.4
`
`Collision assertion
`by transmission
`< 20 bit times
`
`8.2.1.3
`8.2.2.2.4
`
`Collision
`deassertion after
`end of collision
`between second
`MAU
`
`Collision
`deassertion after
`end of collision
`between more than
`twoMAUs
`
`8.8.6.1/1
`:X
`!8.8.6.1/1
`:M
`
`8.8.6.1/1
`:X
`!8.8.6.1/1
`:M
`
`N/A []
`Yes []No []
`N/A []
`Yes []No []
`
`N/A []
`Yes []No []
`N/A []
`Yes []No []
`
`Yes []No []
`
`CSO on CI ::; 17 BT after collision
`
`CSO on CI ::; 29 BT after collision
`
`IDL on CI ::; 17 BT after arrival of
`end of transmission
`
`8.2.1.3
`
`M
`
`8.2.1.3
`
`M·
`
`Yes []No []
`
`IDL on CI ::; 29 BT after arrival of
`end of transmission from all but
`oneMAU
`
`8.8.6.5 Monitor function
`
`Item
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/comment
`
`1
`
`2
`
`3
`
`Signal path
`
`Transmit disable
`delay
`
`MAU function in
`isolated state
`
`8.2.1.4
`
`8.2.1.4
`
`8.2.1.4
`
`8.8.6.1/2
`:M
`
`8.8.6.1/2
`:M
`
`8.8.6.1/2
`:M
`
`N/A
`Yes
`
`[]
`[]No []
`
`N/A
`Yes
`
`N/A
`Yes
`
`[]
`[]No []
`
`[]
`[]No []
`
`From DTE to MAU
`through CO circuit
`
`::;20ms
`
`Receive and
`collision functions
`are normal, XMIT
`disabled
`
`7
`
`Page 14
`
`

`
`IEEE
`Std 802.3r-1996
`
`8.8.6.6 Jabber function
`
`SUPPLEMENT TO 802.3
`
`Item
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/comment
`
`Jabber function
`implementation
`
`8.2.1.5
`
`Frame timer range
`
`8.2.1.5
`
`M
`
`M
`
`CI circuit during
`jabber
`
`8.2.1.5
`8.2.2.2.4
`
`Collision presence
`function activated
`after transmit disable
`
`Unjab timer range
`
`MAU unjab (reset)
`with monitor function
`
`MAU jabber lockup
`protection
`
`8.2.1.5
`
`8.2.1.5
`
`8.2.1.5
`
`9.4.1
`
`8.8.6.1/1
`:X
`!8.8.6.1/1
`:M
`
`M
`
`0
`
`8.8.6.112
`:M
`
`8.8.6.111
`:M
`!8.8.6.111
`:0
`
`Yes
`
`[]No []
`
`Yes. []No []
`
`NIA []
`[]No []
`Yes
`NIA []
`[]No []
`Yes
`
`Yes
`
`[]No []
`
`[]No []
`Yes
`NIA []
`[]No []
`Yes
`NIA []
`[]No []
`Yes
`NIA []
`[]No []
`Yes
`
`Self-interruption of
`the transmitter
`
`20 ms min,
`150ms max
`
`CSO signal
`
`No extraneous signal
`on the coaxial media
`
`0.5 s±50%
`
`Isolate message
`
`Jabber function not
`activated under
`worst case
`conditions in 9.6.5
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`Page 15
`
`

`
`CSMA/CD
`
`8.8.6.7 MAU to coaxial cable interface
`
`IEEE
`Std 802.3r-1996
`
`Item
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/comment
`
`I
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`Input impedance
`
`8.3.1.1
`
`Total capacitive load
`
`8.3.1.1
`
`Bias current
`
`8.3.1.2
`
`Transmit offset
`current
`
`Transmitac
`component
`
`8.3.1.3
`
`8.3.1.3
`
`Transmitter sink cur-
`rent during collision
`
`8.3.1.3
`
`Rise and fall time at
`10 Mb/s
`
`8.3.1.3
`
`Rise and fall time
`match
`
`8.3.1.3
`
`Harmonic content at
`BR
`
`8.3.1.3
`
`8.3.1.4
`
`8.3.1.4
`
`8.3.1.5
`
`8.3.1.5
`
`Transmit signal
`polarity
`
`Transmit signal
`edge jitter
`
`Receive collision
`detection threshold
`
`Receive collision
`detection threshold,
`large impulse
`response
`
`No negative edge
`transmission
`
`8.3.1.4
`
`M
`
`Yes []No []
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`M
`
`Yes []No []
`
`R:?: IOOkQ
`
`Yes []No []
`
`C~4pF
`
`Yes []No []
`
`max +2 ~J.A
`min-25 ~J.A
`
`Yes []No []
`
`-37 rnA to -45 rnA
`
`Yes []No []
`
`+28 rnA to offset value
`
`Yes []No []
`
`No more than -25 ~J.A at -7 V
`no more than ±250 !J.A at -10 V
`
`Yes []No []
`
`25 ± 5 ns (10-90%)
`
`Yes []No []
`
`within 2 ns at 10 Mb/s
`
`Yes []No [ l
`
`2nd and 3rd harmonics :?: 20 dB
`below fundamental, 4th and 5th
`harmonics :?: 30 dB below
`fundamental, 6th and 7th
`harmonics <:: 40 dB below
`fundamental, all higher harmon-
`ics <:: 50 dB below fundamental
`
`Yes []No []
`
`No inversion of signal from
`PLS to coaxial cable
`
`Yes []No []
`
`MAU introduce no more than
`2 ns of edge jitter
`
`Yes []No []
`
`-1.448 V to -1.59 V
`
`Yes []No []
`
`-1293 mY*
`[1 + impulse response] if filter
`impulse response is larger than
`nominal
`
`After cessation of CD output
`stream on DO or before first
`edge of next frame on DO
`
`9
`
`Page 16
`
`

`
`IEEE
`Std 802.3r-1996
`
`8.8.6.8 MAU electrical characteristics
`
`Item
`1
`
`Parameter
`
`Reference
`
`Status
`
`Isolation impedance between
`MDI and AUI cable (each con-
`ductor, including shields)
`
`8.3.2.1
`
`M
`
`Breakdown voltage
`
`Current drawn from AUI
`sources
`
`Operation over VP voltage
`range
`
`Low VP circuit behavior
`
`MAU current labeling
`
`8.3.2.1
`
`8.3.2.2
`
`8.3.2.2
`
`8.3.2.2
`
`8.3.2.2
`
`M
`
`M
`
`M
`
`M
`
`M
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`Support
`Yes []No []
`
`Yes []No []
`
`Yes []No []
`
`Yes []No []
`
`Yes []No []
`Yes []No []
`
`SUPPLEMENT TO 802.3
`
`Value/comment
`> 250 kQ at 60Hz,
`< 15 Q for 3 MHz to
`30MHz
`;;:: 1.5 kV ac, rms
`::;o.5A
`
`11.28-15.75 V, any
`permissible AUI cable
`
`No disruption of media
`
`Current consumption
`shall be labeled
`externally
`MTBF ;;:: 1 million
`hours of continuous
`operation
`
`Reliability
`
`8.3.2.3
`
`M
`
`Yes []No []
`
`8.8.6.9 MAU-DTE requirements
`
`Item
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/comment
`
`1
`
`2
`
`AUI electrical characteristics
`
`8.3.3
`
`AUI mechanical connection
`
`8.3.4
`
`M
`
`M
`
`Yes []No []
`
`Yes []No []
`
`As specified in clause
`7; refer to 8.8.7.1-5
`
`As specified in clause
`7; refer to 8.8.7.6
`
`10
`
`Page 17
`
`

`
`CSMA/CD
`
`8.8.6.10 MAU to coaxial cable connection
`
`IEEE
`Std 802.3r-1996
`
`Item
`
`1
`
`Parameter
`
`Reference
`
`Status
`
`Support
`
`Value/comment
`
`Standard N-type
`connector
`
`8.5
`
`0.1
`
`Yes
`
`[]No []
`
`*2
`
`Coaxial tap connector
`
`8.5.3
`
`0.1
`
`3
`
`4
`
`5
`
`6
`
`7
`
`Capacitance
`
`8.5.3.1
`
`Contact resistance
`
`8.5.3.1
`
`Voltage rating
`
`8.5.3.1
`
`De leakage resistance
`between braid and
`external conductors
`
`8.5.3.1
`
`Probe current rating
`
`8.5.3.1
`
`8.8.6.10/2
`:M
`
`8.8.6.10/2
`:M
`
`8.8.6.10/2
`:M
`
`8.8.6.10/2
`:M
`
`Yes
`
`N/A
`Yes
`
`[ J No [ J
`[ l
`[ J No []
`
`N/A
`Yes
`
`[]
`[ J No []
`
`N/A
`Yes
`
`N/A
`Yes
`
`[ l
`[ J No []
`
`[ l
`[ J No []
`
`N/A
`Yes
`
`0.1 A per contact (probe
`and shield)
`
`50 Q, according to IEC
`169-16: 1982andAmd.
`No. I (1996)
`
`2 pf nominal at 10 MHz
`
`:o; 50 mn for shield and
`center conductor
`
`600 V de or ac rms max
`
`>lGQ
`
`8.8.6.10/2
`:M
`
`8.8.6.10/2
`:M
`
`8.8.6.10/2
`.:M
`
`8.8.6.1012
`

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