| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
I am not sure what the issue is. The bound comes from the definitions of Ton, Treceiver_settling, and Tcdr. I am sure we will have a separate discussion on that. The bound does not come from the MPCPDU field size. In 10G-EPON, SyncTime field was 2 bytes, but the maximum allowed value was 76 TQ (800 ns Treceiver_settling, 400 ns Tcdr, and 16 ns Burst Delimiter).
The only thing that needs to change in Marek’s presentation is that it should not say that the entire range from 0 to 2^16 is allowed. It does say it now.
Thank you, -Glen
From: Duane Remein [mailto:Duane.Remein@xxxxxxxxxx]
The point is not that the OLT has to use both bytes, the point is it legally can and the ONU is duty bound to accommodate that. Without some upper bound that can come to over 2 seconds of delay. Clearly this is excessive. Best Regards Duane
From: Marek Hajduczenia [mailto:mxhajduczenia@xxxxxxxxx]
Duane,
What would be then "reasonable"? It is not like OLT has to use all 2 octets provided for specific values.
Marek
On Wed, Apr 18, 2018 at 11:51 AM, Duane Remein <Duane.Remein@xxxxxxxxxx> wrote:
To unsubscribe from the STDS-802-3-NGEPON list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-NGEPON&A=1 To unsubscribe from the STDS-802-3-NGEPON list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-NGEPON&A=1 |