Re: [STDS-802-3-EPOC] Line coding for EPoC

[Marek Hajduczenia <marek.hajduczenia@xxxxxx>]

Hi Alan, 

 

Thank you for the feedback 

 

My presentation at this time is focused only on line code, which I believe
to be a critical piece for definition of multiple other pieces of PCS, FEC
and PMA included. 

 

I think we already had some discussions about the topic of the scrambler /
interleaver, and I would not like to step into that discussion thread ? it
seems to be well understood. As for gearbox ? it is excluded from this slide
deck, but we will need some sort of gearbox-like function at the very bottom
of the PCS. Whether this is going to be the gearbox as defined in Clause 49
or not, that will depend largely on the definition of the PMA, which right
now is pretty much up in the air. 

 

Also, attached please find an update to the presentation, addressing changes
and corrections suggested kindly by Pete Anslow. 

 

Marek

 

From: Alan M. Brown [mailto:abrown@xxxxxxxxxx] 
Sent: Thursday, 07 March, 2013 3:59 PM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-3-EPOC] Line coding for EPoC

 

Hi Marek,

Thanks for your preso and recommendation.

Referencing your slide 8, in your opinion, are there additional portions of
Clause 49 64b/66b encoding/decoding that would be not applicable/ reusable
for us?  E.g., you?ve already excluded scrambler and gearbox; what else?

Alan

 

From: Marek Hajduczenia [mailto:marek.hajduczenia@xxxxxx] 
Sent: Thursday, March 07, 2013 5:31 AM
To: STDS-802-3-EPOC@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-3-EPOC] Line coding for EPoC

 

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)

 

 

 

  _____  

<="" p="">

 

  _____  


________________________________________________________________________

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 R08.pdf
Description: hajduczenia_04_0313 R08.pdf