When it 24 did this it listed the existing PHY speeds, thinking new PHYs would be 25 added as they came available. 802.3ch-2020 already failed to add itself. 26 Making this general change will fix the problem that clause 149 27 (2.5G/5G/10GBASE-T1) are not included, as well as smooth the path for 28 IEEE P802.3cy, without impacting existing networks, or closing 29 possibilities for 100BASE-T1L and any possible future 1000BASE-T1L. 30 Additionally, contributions in the Greater than 10 Mb/s long-reach SPE 31 study group have shown that long-reach 1 Gb/s is challenging, leaving 32 greater than 1 Gb/s unlikely - hence 1 Gb/s is a good threshold to pass 33 autonegotiation off to the shorter-reach HSM. 34 35 IMPACT ON EXISTING NETWORKS: None. 36 37 38 +----------------------------------------------------------------------+ 39 |Please attach supporting material, if any | 40 |Submit to:- David Law, Chair IEEE 802.3 | 41 |and copy:- Adam Healey, Vice-Chair IEEE 802.3 | 42 | | 43 |At:- E-Mail: stds-802-3-maint-req@ieee.org | 44 | | 45 | +------- For official 802.3 use -----------+ | 46 | | REV REQ NUMBER: 1394 | | 47 | | DATE RECEIVED: 18 February, 2022 | | 48 | | EDITORIAL/TECHNICAL | | 49 | | ACCEPTED/DENIED | | 50 | | BALLOT REQ'D YES/NO | | 51 | | COMMENTS: | | 52 +-------------+------------------------------------------+-------------+ 53 | For information about this Revision Request see - | 54 |http://www.ieee802.org/3/maint/requests/revision_history.html#REQ1394 | 55 +----------------------------------------------------------------------+ 56