Thanks to bring up this critical SMF fiber ZDW question, I add to chime in, please also count on me in contributing to the proposal for ZDW update.
I contacted several largest fiber vendors global from NA and APAC with supporting data to narrow down the ZDW range for the installment base.
Hi Chris,
Naturally, I am fully supportive of a discussion which brings out a more realistic approach to dealing with fiber specs, especially the ZDW. Please count me in as a supporter.
Jumping on the bandwagon of your planned contribution, I would also like to reiterate that realistic fiber specifications don’t end at the ZDW. Holding on to older PMD/DGD specs
similarly eats away link budget that could be well spent somewhere else. (https://www.ieee802.org/3/df/public/22_10/22_1012/kuschnerov_3df_01b_221012.pdf)
Anyway – looking forward to more industry discussions on these topics. As I learned from Peter, there’s no easy way going about fiber specs…
Best,
Maxim
----
Huawei
Hi Chris,
Thank you for your note below to raise this important industry wide issue.
I agree that proper update SMF fiber ZDW spec. is long overdue and has a great potential to save very significant cost and power for the networking industry.
Please count me as a contributor to the proposal for ZDW update. I also like to encourage our colleagues to contribute to this discussion and update.
Thanks.
Rang-Chen (Ryan) Yu
SiFotonics
Dear P802.3df TF Participants,
During last week’s meeting, Roberto presented actual
SMF Zero Dispersion Wavelength (ZDW) data collected by several manufacturers.
ITU-T G.652 SMF codes, which underlie all 802.3 optical standards, specify ZDW from 1300nm to 1324nm. Looking at the above graph, the astute observer may ask why are we worried
about 1300nm. The puzzlement is well justified. 1300nm ZDW fiber basically doesn’t exist. It is not to be found in any datacenter. Yet all 802.3 standards use the ITU-T ZDW limits. In addition to unnecessarily burdening design, this also potentially significantly
increases testing cost. To properly test, fiber with 1300nm and 1324 ZDW must be used. This requires going to manufacturers and asking for custom fiber which includes custom doping and other non-standard steps, which is not conducive to low cost.
This is rarely, if ever, done for real manufacturing environments. Instead, standard SMF is used. The result is that almost all transceivers in the field are not actually verified
for wavelengths near ZDW, for example CWDM4 L2. As a practical matter, this works out just fine, because the transceivers never encounter the full ZDW range. In other words, IEEE 802.3 pretends to write a serious spec, and industry pretends to test to it.
We have repeatedly tried to make the 802.3 SMF ZDW spec. realistic, for example:
https://www.ieee802.org/3/cu/public/May19/cole_3cu_01a_0519.pdf
In each case, we have been instructed to go back to ITU-T and get the spec changed there. Because of a variety of reasons, some less than admirable, this has never been successful.
A straightforward reason is that DWDM applications, which are of primary interest in ITU-T, are in C-band where the exact value of ZDW doesn’t much matter. If you want to know the full story, please ask Peter Stassar who valiantly attempted numerous times
to get this done.
As Baud rate goes up, this spec. becomes more important and we should base our optical specifications on realistic fiber parameters so that we don’t force manufacturers and users
to wink and nod at each other that deployed optics meet specs.
We will be putting together a presentation to propose that we continue to use ITU-T G.652 SMF specs. but change ZDW for example to 1307nm to 1322nm, exact values TBDs. If you have
interest in contributing please let me know. We are already reaching out to fiber manufacturers.
Thank you
Chris
All,
The unapproved minutes for the October 2022 session have been posted. Please see
https://www.ieee802.org/3/df/public/22_10/index.html [ieee802.org].
My thanks to Kent Lusted for his prompt turning around of minutes.
Please note that there were no additional changes made to the Oct 2022 Session Website.
Regards,
John D’Ambrosia
Chair, IEEE P802.3df Task Force
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1
To unsubscribe from the STDS-802-3-B400G list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G&A=1