<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-tab-span" style="white-space:pre"> </span>External connectivity will be being provided by Bright House cable, in the form of two 1G circuits. <div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>They'll be dropping them off in the MDF as SX on LC connectors. I've confirmed that it'll be separate paths to separate POPs, and that they'll provide full v4 and v6 tables and route v6 natively.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>My contacts at Brighthouse have been:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>"Mallette, Edwin J." <<a href="mailto:edwin.mallette@bhnis.com">edwin.mallette@bhnis.com</a>></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>"Ickovic, Jeremy C." <<a href="mailto:Jeremy.Ickovic@bhnis.com">Jeremy.Ickovic@bhnis.com</a>></div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>From the last exchange with them:</div><div><br></div><div><blockquote type="cite">Jim,<br><br>We have complete electronic diversity. We have active gear at the site<br>but it is not the equipment we will be utilizing to provide service for<br>the IETF and IEEE meetings. The circuits go back to different routers and<br>the POP routers are in different cities - one will be in Orlando the other<br>POP router will be in Tampa.<br><br>The only issues we typically have with providing full tables for v4 and v6<br>tend to be related to the customer routers memory. As you do this<br>regularly I don't foresee any issues there. We plan to offer you a pair<br>of /30 IPv4 networks a pair of /64 IPv6 networks for point-to-point to the<br>two POP routers and then we'll re-advertise your networks.<br><br>Regards,<br><br>Ed</blockquote><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I've not yet gotten back to them on our addressing and AS. That's on my to-do list shortly. I'll have them be ready to accept any of our (new or old) prefixes....</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>As for the external routers, Lenny has again come through. This time it's two MX80s w/5 SX SFPs in each. The MX80s were required for the guestroom stuff (which I'll get into in another mail). The routers are enroute to VeriLAN now with the following shipping info:</div><div><br></div><div>-) > AddressVerilan, Inc, 4120 SE International Way, Suite A103, Milwaukee, OR, <br>-) > 97222, United States<br>-) > Tracking Number 794665483298, 794665483026 (Return: 800023014102, 4113)<br>-) > Carrier NameFedEx Express Saver (3-Day) (<a href="http://www.fedex.com/Tracking">http://www.fedex.com/Tracking</a>)</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>As always, we should really try to remember to send t-shirts back in the boxes ... Lenny had to jump through some hoops for the MXes....</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Jim</div></body></html>