|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
I think 802.3cb should not have modified the 1000BASE-X PCS. There are existing 2.5G implementations using the 1000BASE-X PCS speeded up and I think 802.3cb should just have re-used 1000BASE-X and not invented something new.
Existing 1G implementations have two problems with the requirement to implement link fault signaling:
1. Encoding sequence ordered sets
2. Implementing the link fault state machine which generates remote fault on reception of local fault
Because there is no requirement to signal link interruption the link fault state machine is un-necessary for 2.5G data-rates and just adds extra complexity and causes potential inter-operability problems with existing 2.5G implementations.
For 2.5GBASE-X link fault signaling will be there. It lets 802.3cb align with 802.3bz.
Task force decided to keep it in for 802.3cb.
Also 802.3cb is designed to be compatible with 1000BASE-X PCS running 2.5x faster.
This is true even if a 2.5GBASE-X PCS sends out link fault signaling. The 2.5GBASE-X PCS
link fault signaling is designed to look like idles to the 1000ABSE-X PCS.
See Annex 127B in the 802.3cb for further description.
For 5GBASE-R the link fault signaling is already baked in since it adopts the 10GBASE- R PCS.
I have prepared the attached presentation for today’s ad hoc call.
I have also submitted a comment against draft 3.1 to request making link fault signalling optional for 2.5G and 5G data rates.
Reminder for tomorrow.
I’m expecting a discussion of an unresolved negative vote from May in Whistler. The comment is i-56 (see below from http://grouper.ieee.org/groups/802/3/bz/comments/8023bz_D30_approved.pdf).
802.3bz 2.5/5GBASE-T Task Force Arch Ad Hoc Chair
This meeting is back by request. We have some Sponsor Ballot comments to look into before the interim on June 27th. The timeslot has been moved to accommodate some key people.
Agenda information will be provided prior to each meeting.
Please familiarize yourself with the meeting guidelines and patent policy before the meeting.
Meeting guidelines: https://development.standards.ieee.org/myproject/Public/mytools/mob/slideset.pdf
Patent policy: www.ieee802.org/3/patent.html