<div dir="ltr">Hi Bevan,<div><br></div><div>I am not sure that I can speak for any consumer of wave services at present, but based on past experience as a scrappy operator:</div><div><br></div><div>1) I want to demarc as close to the source as possible - as an operator it gives me more visibility of faults, the opportunity to strategically do something with the contingency plan, and as a hustler it gives me the opportunity to resell a fractional service in another datacentre</div><div><br></div><div>2) Always get delivery to the MMR if that's an option, otherwise if you can get a better deal on cross-connects than I can then please deliver it to my rack</div><div><br></div><div>3) Typically the cheaper non-redundant option represents better value for money, as I can use the savings to buy more bandwidth from a diverse provider</div><div><br></div><div>4) Call me old fashioned, but I prefer the troubleshooting layers of having expensive services land on a Layer 2 device that is separate to my router. This has the added benefit of letting me upgrade the Layer 3 device later with a remote config cutover rather than with a laptop on the floor of a cold datacentre, and then play router chess with the replaced hardware at my leisure.</div><div><br></div><div>My experience as a telco employee is exactly the opposite of these choices - choose the gold plated options to minimise having to train an ops or field team to handle a fault because there are already too many circuits and faults and the after hours team will just punt it to the day team anyway.</div><div><br></div><div>John</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 19 Nov 2024 at 18:37, Bevan Slattery <<a href="mailto:bevan@slattery.net.au">bevan@slattery.net.au</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div class="msg-4177077287730458147">
<div lang="EN-AU" style="overflow-wrap: break-word;">
<div class="m_-4177077287730458147WordSection1">
<p class="MsoNormal"><span>Sorry one clarification (based upon answer already received!)<u></u><u></u></span></p>
<p class="MsoNormal"><span><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Q: What would you be typically be connecting this service to? Router or Optical?<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">My intention here is that from a client perspective what are you likely to plug into at your end and was based on us delivering from our optical platform. My apologies.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">[background]<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The reason for this is because a number of 400G optical platforms aren’t yet supporting 400G ER/ZR because the cards aren’t quite able for the power (and or heat) of a QSFP-DD 400G ER/ZR optic in the transponder card. I know most 400G
routers can handle this (>120km), but surprisingly Infinera and Ciena each today have limitations supporting this on some of their optical platforms. I was basically looking for if you (the client) are terminating this on a router, then if I can solve the
400G to 40km optical (EoOTN) at my end then most clients plugging this into a router can handle it. But if you were intending taking this as an optical/ODU into an optical box then there we could have some issues with needing to check the client end support
(being limited at present). I’m basically hoping to see lots of “intending on plugging it into my router”
<span style="font-family:"Apple Color Emoji"">😊</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
<a href="https://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">https://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></blockquote></div>