Re: [802.3_ISAAC] [EXTERNAL] Re: [802.3_ISAAC] Question on Baseline Text Proposal for TDD Based 802.3dm PHY
Hi, Ragnar,
Regarding loc_rcvr_status, statements b) and c) are both similarly defined in IEEE 802.3ch. I agree with you that statement c) indicates that frame synchronization is required before loc_rcvr_status = OK. Please also note that pcs_status and scr_status are used in data mode and training mode, respectively. I believe statement c) provides a fairly clear definition for loc_rcvr_status = OK.
As for statement b), the full sentence from the TDD text proposal reads:
“When loc_rcvr_status indicates OK, then the PCS Synchronization process accepts data-units via the PMA_UNITDATA.indication primitive. It attains frame and block synchronization based on the PMA training frames and conveys received blocks to the PCS Receive process when PHY control is in PCS_DATA state.”
In addition to the original sentence from IEEE 802.3ch, we added the clause “when PHY control is in PCS_DATA state” in our proposal for clarity—because block synchronization, in our view, only applies during data mode.
So, the proposal we’re presenting is not introducing anything fundamentally new; it’s consistent with both 802.3bp and 802.3ch.
Finally, since receiver design is implementation-dependent, I won’t comment on your specific state diagram. We believe our PHYC state diagram text proposal is sufficient as currently written.
Thank you!
Wei
________________________________________________________________________
To unsubscribe from the STDS-802-3-ISAAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-ISAAC&A=1