Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802.3_NGMMF] contribution is posted for Thursday's ad hoc by Jonathan Ingham and Carlo Marriotti

All,

 

I understand I should have said “non-standard” FEC instead of “proprietary” FEC, since all I know is that the FEC/PCS used is not one defined by the IEEE 802.3 for these deployed 100G-BiDi solutions the presenter has prompted us to be concerned about.

 

Jeff

 

 

Juniper Internal

From: Jeffery Maki <00000d5963b8071f-dmarc-request@xxxxxxxxxxxxxxxxx>
Sent: Thursday, April 4, 2019 8:52 AM
To: STDS-802-3-NGMMF@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_NGMMF] contribution is posted for Thursday's ad hoc by Jonathan Ingham and Carlo Marriotti

 

All,

 

100G-BiDi uses proprietary FEC so there is no interop any way. When modules are made that support interoperable FEC the optical specs can be changed too. In this way, we can optimize for the future instead of provisioning for a problem best solved by bookending these early modules in their deployments, which are single operator anyway.

 

Jeff

 

 

From: Robert Lingle <linglerobertjr@xxxxxxxxx>
Sent: Wednesday, April 3, 2019 7:51 PM
To: STDS-802-3-NGMMF@xxxxxxxxxxxxxxxxx
Subject: [802.3_NGMMF] contribution is posted for Thursday's ad hoc by Jonathan Ingham and Carlo Marriotti

 

To unsubscribe from the STDS-802-3-NGMMF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-NGMMF&A=1

 

Juniper Internal

To unsubscribe from the STDS-802-3-NGMMF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-NGMMF&A=1

To unsubscribe from the STDS-802-3-NGMMF list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-NGMMF&A=1