Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Dear colleagues, I prepared a presentation (as attached) focusing on the topic of line coding for EPoC, why it is needed and what our options are looking at other existing Ethernet standards. I also included overview of 64b/66b line code with some details so that people can start thinking about this topic. My belief is that we can reuse 64b/66b line coding in EPoC to guarantee good code-word alignment and have to do absolutely nothing to develop a new line code for EPoC. The same approach was taken in 10G-EPON and worked just great ? no development errors were committed, and companies could just reuse their existing implementations from 10GE and other high speed Ethernet PHYs. The decision on the line code is important, since the selection of the line code influences other choices, including the FEC code word size, mapping of individual data vectors into the FEC code word, as well as the following OFDM symbol size. I plan to submit this contribution to the upcoming meeting in Orlando and I would appreciate your feedback and comments ahead of time. Thank you in advance regards Marek Hajduczenia, PhD ZTE Portugal Standard Development and Industry Relations Edifício Amoreiras Plaza, Rua Carlos Alberto da Mota Pinto, nr. 9 - 6 A, 1070-374 Lisbon, Portugal Office: +351 213 700 090 Fax: + 351 213 813 349 Mobile: +351 961 121 851 (Portugal) ________________________________________________________________________ To unsubscribe from the STDS-802-3-EPOC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-EPOC&A=1
Attachment:
hajduczenia_04_0313 R07.pdf
Description: hajduczenia_04_0313 R07.pdf