DATE: 8th July, 2001 Erica Williamsen, Bob Noseworthy COMPANY/AFFILIATION: UNH InterOperability Lab

Transcription

1 /0. REVISION REQUEST ==================================== DATE: th July, 00 NAME: Erica Williamsen, Bob Noseworthy COMPANY/AFFILIATION: UNH InterOperability Lab ericaw@iol.unh.edu, ren@iol.unh.edu REQUESTED REVISION: STANDARD: IEEE Std CLAUSE NUMBER:..., Table - and Table - CLAUSE TITLE: Auto-Negotiation expansion register (Register ) and State diagram variable to MII register mapping PROPOSED REVISION TEXT: See attached draft. RATIONALE FOR REVISION: Clause. states, In the case of any ambiguity between stated requirements and the state diagrams, the state diagrams shall take precedence. This is a problem because Register (AN link partner next page ability register) is never used by the state diagrams. The mr_page_rx variable defines that the received Link Code Word is written to mr_lp_adv_ability[:] and Table - State diagram variable to MII register mapping: states that mr_lp_adv_ability[:] maps to MII Register (Auto-Negotiation link partner ability register). Textual definition of Register (...) states, Support for 00BASE-T and 000BASE-T requires support for Next Page and the provision of an Auto-Negotiation Link Partner Next Page Ability register (register )) to store Link Partner Next Pages. This text does not answer the dilemma that the use of register is only for next pages used for 00BASE-T or 000BASE-T PHYs, or that register is used for the receipt of all next pages in all PHYs. This is the rationale behind the proposal to allow all received next pages to be stored in either register or register. This leads to defining a two new MII register bit (.) bits in register (AN expansion register). The first bit (. - Received Next Page Storage Location) is used to indicate which register is used to store received next pages. The second bit (. - Receive Next Page Location Able) is used to indicate if the first new register bit (.) is supported or not. This revision will also solve the problem of when mr_page_rx is indicated during reception of next pages, which register is checked by management. This will also solve the external MII transceiver problem where the user of an implementation does not have prior knowledge of how the implementation works. Other options considered included writing to either register, register, or writing to both register and register. The disadvantages for storing the Link Partner Next Pages in register are that the system management entity needs to store the information overwritten by subsequent Link ISO/IEC 0-/IEEE Std.0. Revision Request. Subject to change.

2 Partner Next Pages and existing vendors that do not store next pages in register would have to implement this feature. The disadvantages for storing the Link Partner Next Pages in register is that existing vendors that do not store next pages in register would have to implement another register. The disadvantages of writing to both register and register are more overhead storing in both registers and the system management entity needs to store the information overwritten by subsequent Link Partner Next Pages in register. This would also affect all existing vendors. Thus, the proposed remedy seems to be the most efficient solution that minimizes the impact on existing networks. IMPACT ON EXISTING NETWORKS: Of PHY manufactures from the past four years, use register for received next page storage and use register for received next page storage (nearly all 000BASE-T PHYs). None. Received Next Pages can still be stored in either register or register. Two new optional bits (. - Received Next Page Storage Location and. - Receive Next Page Location Able) are defined however in existing implementations, and implementation that chooses not to implement them, these two bits will both be set to zero. This will indicate, through the Receive Next Page Location Able bit (.) being zero, that an indication of the register used to store received Next Pages is not provided Please attach supporting material, if any Submit to:- Geoffrey O. Thompson, Chair IEEE 0. gthompso@nortelnetworks.com For official 0. use REV REQ NUMBER: 0 DATE RECEIVED: th July, 00 EDITORIAL/TECHNICAL ACCEPTED/DENIED BALLOT REQ'D YES/NO COMMENTS: 0-Jan-0 Ver: D. Status: B For information about this Revision Request see ISO/IEC 0-/IEEE Std.0. Revision Request. Subject to change.

3 IEEE P0. Revision request 00 Changes to ANSI/IEEE Std 0.-00, Clause EDITORIAL NOTES - This revision request is based on the current edition of IEEE Std The editing instructions define how to merge the material contained here into this base document. Editing instructions are shown in bold italic. Three editing instructions are used: change, delete, and insert. Change is used to make small corrections in existing text or tables. The editing instruction specifies the location of the change and describes what is being changed either by using strikethrough (to remove old material) or underscore (to add new material). Delete removes existing material. Insert adds new material without disturbing the existing material. Insertions may require renumbering. If so, renumbering instructions are given in the editing instruction. Editorial notes will not be carried over into future editions. Editors Notes: To be removed prior to final publication. Revision History: Draft.00, September, 00 Draft.00, November, 00 Editors Notes: To be removed prior to final publication. Revision History: Draft.0, September, 00 Draft.0, November, 00 Draft., January, 00 Change subclause... as follows: Initial draft. Working Group Ballot draft. Remove spurious copy of Figure -b. Initial draft. Working Group Ballot draft. Remove spurious copy of Figure -b. Working Group Recirculation Ballot draft. Add recommendation to use Register in new implementations.... Auto-Negotiation link partner ability register (Register ) (RO) This register contains the Advertised Ability of the Link Partner s PHY. (See Tables and.) The bit definitions shall be a direct representation of the received Link Code Word (Figure ). Upon successful completion of Auto-Negotiation, status register (Register ) Auto-Negotiation Complete bit (.) shall be set to logic one. If the Next Page function is supported, the Auto-Negotiation link partner ability register may be used to store Link Partner Next Pages and bit (.) in the Auto-Negotiation expansion register (Register ) is set to logic zero, then the Auto-Negotiation link partner ability register may be used to store Link Partner Next Pages. If bit (.) in the Auto-Negotiation expansion register (Register ) is set to logic one, then bit (.) determines where the Link Partner Next Pages are stored. Table Link partner ability register bit definitions (Base Page ) Bit(s) Name Description R/W. Next Page See... RO. Acknowledge See... RO ISO/IEC 0-/IEEE Std.0. Revision Request. Subject to change.

4 Table Link partner ability register bit definitions (Base Page) (continued) Bit(s) Name Description R/W. Remote Fault See... RO.: Technology Ability Field See... RO.:0 Selector Field See... RO Table Link partner ability register bit definitions (Next Page) Bit(s) Name Description R/W. Next Page See... RO. Acknowledge See... RO. Message Page See... RO. Acknowledge See... RO. Toggle See... RO.0:0 Message/Unformatted Code Field The values contained in this register are only guaranteed to be valid once Auto-Negotiation has successfully completed, as indicated by bit. or, if used with Next Page exchange, after the Page Received bit (.) has been set to logic one. NOTE If this register is used to store Link Partner Next Pages, the previous value of this register is assumed to be stored by a management entity that needs the information overwritten by subsequent Link Partner Next Pages. Change subclause... as follows: See Auto-Negotiation expansion register (Register ) (RO) All of the bits in the Auto-Negotiation expansion register are read only; a write to the Auto-Negotiation expansion register shall have no effect. (See Table.) Bits.: are reserved for future Auto-Negotiation expansion. The Receive Next Page Location Able bit (.) shall be set to logic one to indicate that the Link Partner Next Page Storage Location bit (.) is supported. The Receive Next Page Storage Location bit (.) shall be set to logic one to indicate that the link partner's Next Pages are stored in the Auto-Negotiation link partner Next Page ability register (Register ). This bit shall be set to logic zero to indicate that the link partner's Next Pages are stored in the Auto-Negotiation link partner ability register (Register ). It is recommended that all new implementations store the link partner's Next Pages in the Auto-Negotiation link partner Next Page ability register (Register ). NOTE It is highly recommended that the Link Partner Next Page Storage Location bit (.) is supported. If this bit is not supported there is no indication if the Link Partners Next Page is stored in Register or register. RO ISO/IEC 0-/IEEE Std.0. Revision Request. Subject to change.

5 Table Expansion register bit definition s Bit(s) Name Description R/W Default.: Reserved Write as zero, ignore on read. Receive Next Page Location Able. Received Next Page Storage Location = Received Next Page storage location is determined specified by bit (.) 0 = Received Next Page storage location is not determined specified by bit (.) = Link Partner Next Pages are stored in Register 0 = Link Partner Next Pages are stored in Register. Parallel Detection Fault = A fault has been detected via the Parallel Detection function. 0 = A fault has not been detected via the Parallel Detection function.. Link Partner Next Page Able = Link Partner is Next Page able 0 = Link Partner is not Next Page able. Next Page Able = Local Device is Next Page able 0 = Local Device is not Next Page able. Page Received = A New Page has been received 0 = A New Page has not been received.0 Link Partner Auto-Negotiation Able = Link Partner is Auto-Negotiation able 0 = Link Partner is not Auto-Negotiation able RO The Parallel Detection Fault bit (.) shall be set to logic one to indicate that zero or more than one of the NLP Receive Link Integrity Test function, 00BASE-TX, or 00BASE-T PMAs have indicated link_status=ready when the autoneg_wait_timer expires. The Parallel Detection Fault bit shall be reset to logic zero on a read of the Auto-Negotiation expansion register (Register ). The Link Partner Next Page Able bit (.) shall be set to logic one to indicate that the Link Partner supports the Next Page function. This bit shall be reset to logic zero to indicate that the Link Partner does not support the Next Page function. The Next Page Able bit (.) shall be set to logic one to indicate that the Local Device supports the Next Page function. The Next Page Able bit (.) shall be set to logic zero if the Next Page function is not supported. The Page Received bit (.) shall be set to logic one to indicate that a new Link Code Word has been received and stored in the Auto-Negotiation link partner ability register. The Page Received bit shall be reset to logic zero on a read of the Auto-Negotiation expansion register (Register ). The Link Partner Auto-Negotiation Able bit (.0) shall be set to logic one to indicate that the Link Partner is able to participate in the Auto-Negotiation function. This bit shall be reset to logic zero if the Link Partner is not Auto-Negotiation able. RO/ LH 0 RO/ LH ISO/IEC 0-/IEEE Std.0. Revision Request. Subject to change.

6 Change subclause... as follows:... State diagram variable to MII register mapping The state diagrams of Figures to generate and accept variables of the form mr_x, where x is an individual signal name. These variables comprise a management interface that may be connected to the MII management function or other equivalent function. Table describes how the MII registers map to the management function interface signals. Table State diagram variable to MII register mapping State diagram variable mr_adv_ability[:] mr_autoneg_complete mr_autoneg_enable mr_lp_adv_ability[:] mr_lp_autoneg_able mr_lp_np_able mr_main_reset mr_next_page_loaded mr_np_able mr_np_tx[:] mr_page_rx mr_parallel_detection_fault mr_restart_negotiation set if Auto-Negotiation is available. Auto-Negotiation expansion MII register.:0 Auto-Negotiation advertisement register. Auto-Negotiation Complete 0. Auto-Negotiation Enable For Base Page:.:0 Auto-Negotiation link partner ability register For Next Page(s): If.= and.= then.:0 Auto-Negotiation link partner Next Page ability register If.= and.= 0 then.:0 Auto-Negotiation link partner ability register If.=0 then.:0 or.:0 is Auto-Negotiation link partner Next Page ability register.0 Link Partner Auto-Negotiation Able. Link Partner Next Page Able 0. Reset Set on write to Auto-Negotiation Next Page Transmit register; cleared by Arbitration state diagram. Next Page Able.:0 Auto-Negotiation Next Page Transmit Register. Page Received. Parallel Detection Fault 0. Auto-Negotiation Restart. Auto-Negotiation Ability Auto-Negotiation is designed in a way that allows it to be easily expanded as new technologies are developed. When a new technology is developed, the following things must be done to allow Auto-Negotiation to support it: a) The appropriate Selector Field value to contain the new technology must be selected and allocated ISO/IEC 0-/IEEE Std.0. Revision Request. Subject to change.

7 b) A Technology bit must be allocated for the new technology within the chosen Selector Field value. c) The new technology s relative priority within the technologies supported within a Selector Field value must be established. Code space allocations are enumerated in Annex A, Annex B, and Annex C. Additions and insertions to the annexes are allowed. No changes to existing bits already defined are allowed ISO/IEC 0-/IEEE Std.0. Revision Request. Subject to change.