<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p> Depending on the Colo... It is generally a fiber for
everyone.</p>
<p> But Bell being Bell (wink wink) I'm sure they made this extra
<beep> and <beep> for no reason at all.<br>
</p>
<pre class="moz-signature" cols="72">-----
Alain Hebert <a class="moz-txt-link-abbreviated" href="mailto:ahebert@pubnix.net">ahebert@pubnix.net</a>
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 <a class="moz-txt-link-freetext" href="http://www.pubnix.net">http://www.pubnix.net</a> Fax: 514-990-9443
</pre>
<div class="moz-cite-prefix">On 09/09/18 11:04, Clayton Zekelman
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1536505483_552546@surgemail.mnsi.net">
<br>
We used to have a GigE transit port terminated on CO connecting
links inside one of their COs long ago. No CPE. They may have
changed their policy since then.
<br>
<br>
At 07:25 PM 08/09/2018, JASON BOTHE via NANOG wrote:
<br>
<br>
<blockquote type="cite">All,
<br>
<br>
Just curious if anyone uses Bell Canada for IP transit in a colo
environment and whether or not you were able to obtain a
traditional cross-connect without having Bell place a managed
CPE device in your cage. I can’t seem to find anyone
intelligent enough to tell my any different other than “it’s
never been done before†and “we need remote testing
capabilities.â€
<br>
<br>
J~
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>