<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:tax="http://schemas.microsoft.com/sharepoint/taxonomy/soap/" xmlns:tns="http://schemas.microsoft.com/sharepoint/soap/recordsrepository/" xmlns:spsup="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You would still need to frequency shift TX and RX.  They are travelling opposite directions on the same piece of glass;  as the traffic rate increases the likelihood
 of collisions increases and you’ll start to get errors.  The collision would either cancel the ‘bit’ or act like OBI and get erroneous bits and checksum errors or missing chunks from the constellation.  There are BIDI 100G transceivers for Multi-mode available
 today based on the Foxconn optics, I’d imagine we’ll see BIDI for the O and C bands in the next 18 months.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> NANOG [mailto:nanog-bounces@nanog.org]
<b>On Behalf Of </b>Eric Kuhnke<br>
<b>Sent:</b> Monday, August 13, 2018 3:56 PM<br>
<b>To:</b> ben@6by7.net; nanog@nanog.org list<br>
<b>Subject:</b> Re: optical circulator as a bidirectional one fiber solution<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">For 1 and 10Gbps OOK modulation yes, but not for something like a ITU DWDM grid channelized or tunable coherent optic. In which the (QPSK, 8PSK, 16QAM) signal has a specific THz width and frequency not unlike a radio operating in a very,
 very narrow waveguide.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, Aug 13, 2018 at 1:57 PM Ben Cannon <<a href="mailto:ben@6by7.net">ben@6by7.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Good news about almost all optics, their Rx window is pretty wide. Meaning a 1550nm optic will activate the receiver on a 1560nm optic just fine (and probably anything in the 1500nm band).  Careful use of specialized
 single strand DWDM muxes (<a href="http://FS.com" target="_blank">FS.com</a>) can yield great bidi-like results with increased channel count. <o:p></o:p></p>
<div id="m_-1921249912650797825AppleMailSignature">
<p class="MsoNormal">-Ben<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Aug 13, 2018, at 10:49 AM, Eric Kuhnke <<a href="mailto:eric.kuhnke@gmail.com" target="_blank">eric.kuhnke@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal">Something that is broadly the same as a coherent 100G QPSK single wavelength optical module, but in two different frequencies, and a passive CWDM mux/demux prism at each end might work. The limitation would be availability of optics for
 a modern 100G MSA that are both coherent and Tx/Rx at two different THz frequencies.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Or with some box and vendor equipment in between, such as: <o:p>
</o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="http://cdn.extranet.coriant.com/resources/Application-Notes/AN_Groove_Bidirectional_Fiber_74C0169.pdf?mtime=20180206023321" target="_blank">http://cdn.extranet.coriant.com/resources/Application-Notes/AN_Groove_Bidirectional_Fiber_74C0169.pdf?mtime=20180206023321</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Aug 7, 2018 at 1:00 PM Daniel Corbe <<a href="mailto:dcorbe@hammerfiber.com" target="_blank">dcorbe@hammerfiber.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt">On 8/7/2018 15:46:03, "Baldur Norddahl" <<a href="mailto:baldur.norddahl@gmail.com" target="_blank">baldur.norddahl@gmail.com</a>>
<br>
wrote:<br>
<br>
>Hello<br>
><br>
>There is a lack of bidirectional one fiber (BIDI) options for 40G and <br>
>100G optics. Usually BIDI is implemented using two CWDM wavelengths, <br>
>one for tx and one for rx. However there is also a lack of CWDM and <br>
>DWDM options for 40G and 100G.<br>
><br>
>Would it be possible to use an optical circulator like this one <br>
>(customized to 1310 nm)?<br>
><br>
><a href="https://www.fs.com/de/en/products/33364.html" target="_blank">https://www.fs.com/de/en/products/33364.html</a><br>
><br>
>Combined with a traditional two fiber 1310 nm 10 km 40G QSFP module <br>
>like this: <a href="https://www.fs.com/de/en/products/24422.html" target="_blank">
https://www.fs.com/de/en/products/24422.html</a><br>
><br>
>The link distance would be 5 km.<br>
><br>
>The optical circulator separates tx and rx by the direction the light <br>
>travels in. It would work even though both directions use the same <br>
>wavelength. There will likely be some reflection but hopefully <br>
>attenuated enough that it is regarded as background noise.<br>
><br>
>Has anyone done this? Any reason it would not work?<br>
><br>
>Regards,<br>
><br>
>Baldur<br>
><br>
<br>
The main issue you're going to run into (especially trying to plug <br>
anything into a DWDM shelf) is 40G and 100G transceivers usually emit 4 <br>
lanes of traffic instead of a single lane like 10 and 1G optics do.<br>
<br>
I'd imagine that's why there are so few solutions that don't involve <br>
things like OTN.<o:p></o:p></p>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</body>
</html>