<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; ">FYI ... Here's the guy with clue that called me...<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Jim</div><div><br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica'; font-size:medium;">"Brabble, Kerry D." <<a href="mailto:Kerry.Brabble@mybrighthouse.com">Kerry.Brabble@mybrighthouse.com</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>RE: URGENT: Brighthouse issues with IETF</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">March 7, 2013 10:26:57 AM EST<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family:'Helvetica'; font-size:medium;">"<a href="mailto:jim@daedelus.com">jim@daedelus.com</a>" <<a href="mailto:jim@daedelus.com">jim@daedelus.com</a>><br></span></div><br><div>Jim,<br><br> As we discussed on the phone, the v6 issue should be resolved. I have verified that your prefix (2001:df8::/32) is now being properly exported at our border routers. I have also verified that both Level3 and TWC are accepting the route from us.<br><br>I will dig into the v4 issues and get back to you shortly. My contact info is below if you need anything.<br><br>-Kerry<br><br><br>Kerry Brabble<br>Principle Network Engineer<br>Brighthouse Networks<br>Sustaining Engineering<br><a href="mailto:Kerry.Brabble@mybrighthouse.com">Kerry.Brabble@mybrighthouse.com</a><br>Office: 407-215-8114<br>Cell: 813-230-9054<br><br><br><br><br><br>On 3/7/13 6:51 AM, "Jim Martin" <jim@daedelus.com> wrote:<br><br><blockquote type="cite">Ed,<br> Thanks very much! The three main contacts on our side would be:<br><br> Jim Martin jim@daedelus.com +1 408 799-2788<br> Warren Kumari warren@kumari.net +1 571 969-4367<br> Collin Doyle cdoyle@verilan.com +1 503 810-2129<br><br> - Jim<br><br>On Mar 7, 2013, at 9:45 AM, "Mallette, Edwin J."<br><edwin.mallette@bhnis.com> wrote:<br><br><blockquote type="cite">Jim,<br><br>We've got our senior folks working on this. Let me see if I can get<br>them to loop you in directly.<br><br>Ed<br><br>On 3/7/13 6:41 AM, "Jim Martin" <jim@daedelus.com> wrote:<br><br><blockquote type="cite">Ed,<br> We're still stuck in a hold on this. How is the escalation going?<br><br> - Jim<br><br>On Mar 6, 2013, at 8:39 PM, Jim Martin <jim@daedelus.com> wrote:<br><br><blockquote type="cite">Thanks very much. We are really in a spot here, and we'd be happy<br>to work this evening or first thing in the morning. Don't be shy<br>about using my or Warren's cell.<br><br>-Jim<br><br>Sent from my iPhone<br><br>On Mar 6, 2013, at 8:22 PM, "Mallette, Edwin J."<br><Edwin.Mallette@bhnis.com> wrote:<br><br><blockquote type="cite">Jim,<br><br>My apologies, I'm escalating internally to get some additional<br>help here.<br><br>Regards<br><br>Ed<br><br>On 3/6/13 5:17 PM, "Jim Martin" <jim@daedelus.com> wrote:<br><br><blockquote type="cite">Ed and Jeremy,<br> We've had a really rough day with runaround at Brighthouse today.<br>The<br>links physically came up yesterday, however we've now been<br>fighting for<br>24 hours with reachability issues with v4 and a total lack of v6.<br>We've<br>been getting full routes, and have been advertising all the IETF<br>routes, but none of the v6 routes are being propagated and the v4<br>is going out through some subset of peers. The end result is a<br>nearly unusable network.<br><br> We've been advised that this is based around an internal<br>policy of "validating" our routes, and as it stands we won't have<br>real reachability until after 5pm tomorrow.<br><br> Note also that we've been working with Jelani Jenkins, who has<br>done his best to help, but keeps running into roadblocks.<br><br> This is putting the delivery of the IETF network in jeopardy,<br>and seems almost entirely to be an administrative snafu. Could<br>you please step in and help get this resolved? If you need any<br>details to help, please contact me at +1 408 799-2788 at any time<br>of day. If I'm not available, Warren Kumari is available to work<br>on this as well at +1 571 969-4367.<br><br> Thanks for your help!<br><br> - Jim<br><br>On Jan 15, 2013, at 2:56 PM, Jim Martin <jim@daedelus.com> wrote:<br><br><blockquote type="cite"> Great! Forgive my being so pedantic, but these are often areas<br>where we have issues.<br><br> I'll get all my addressing and AS information to you shortly.<br><br> Thanks!<br><br> - Jim<br><br>On Jan 15, 2013, at 11:51 AM, "Mallette, Edwin J."<br><edwin.mallette@bhnis.com> wrote:<br><br><blockquote type="cite">Jim,<br><br>We have complete electronic diversity. We have active gear at<br>the site but it is not the equipment we will be utilizing to<br>provide service for the IETF and IEEE meetings. The circuits<br>go back to different routers and the POP routers are in<br>different cities - one will be in Orlando the other POP router<br>will be in Tampa.<br><br>The only issues we typically have with providing full tables<br>for<br>v4<br>and v6<br>tend to be related to the customer routers memory. As you do<br>this regularly I don't foresee any issues there. We plan to<br>offer you a pair of /30 IPv4 networks a pair of /64 IPv6<br>networks for point-to-point to the two POP routers and then<br>we'll re-advertise your networks.<br><br>Regards,<br><br>Ed<br><br>On 1/15/13 2:45 PM, "Jim Martin" <jim@daedelus.com> wrote:<br><br><blockquote type="cite">Ed,<br> Yes, 1G is fine. Usually delivered on SX if you've got active<br>gear at the site. Can you confirm that the two circuits will<br>be physically and logically diverse? We just need to make<br>sure they're going back to different routers at different<br>sites, and that there's no common equipment and minimal<br>commonality of path (though the last leg into the hotel is<br>likely going to be common).<br><br> Any issue with providing full tables for both v4 and native<br>(not-tunneled) v6?<br><br> If there are any details I can get from you when I'm onsite<br>later this week, I'm happy to do so!<br><br> Thanks!<br><br> - Jim<br><br>On Jan 15, 2013, at 11:23 AM, "Mallette, Edwin J."<br><edwin.mallette@bhnis.com> wrote:<br><br><blockquote type="cite">Jim,<br><br>We can support either. We were informed early on that we<br>might need to be ready to go higher than 1G, but if 1G is<br>sufficient we can readily support that.<br><br>I don't know that we need anything additional from you to<br>make ready on our side. We'll need to share the logical<br>details (such as what<br>IPv4/IPv6<br>point-to-point networks we're providing) AS number, peering<br>router addresses etc, but for the order processing to get the<br>UNIs delivered we should be fine though Jeremy can correct<br>me if I'm wrong here.<br>What<br>interfaces media do you prefer ? TX, SX, LX ?<br><br>Ed<br><br>On 1/15/13 12:50 PM, "Jim Martin" <jim@daedelus.com> wrote:<br><br><blockquote type="cite">Ed and Jeremy,<br>Nice to meet you both, and thanks in advance for your help<br>on these circuits. The install deadline on the circuits is<br>March 1st.<br>We'll<br>have<br>staff onsite starting the 5th, with the network going<br>"production"<br>on<br>the<br>9th, and staying in production until the 24th. While 10G is<br>cool, it would require us to acquire some different<br>equipment for our border routers. We'll do that though if<br>it's important to you. Our general use case is 5 minute<br>peaks in the 350-500M range, with very rare spikes to 700M.<br>Usually, 2 x 1G is more than enough. The part that's<br>important though are that the circuits are as divergent as<br>possible (both physically and topologically)and that we can<br>get full IPv4 and<br>IPv6<br>BGP<br>feeds.<br><br>As for my site visit, what info do you need for the Z end to<br>get your order in?<br><br>Thanks!<br><br>- Jim<br><br>On Jan 15, 2013, at 7:31 AM, "Mallette, Edwin J."<br><edwin.mallette@bhnis.com> wrote:<br><br><blockquote type="cite">Jim,<br><br>Nice meeting you. I've CC-ed Jeremy who is in charge of<br>the service delivery to the site. We are preparing to<br>offer either a pair of 1G or 10G UNIs. What is your<br>timeframe for the circuit activation (I.e.<br>When<br>will you have equipment in place so we can ensure our<br>timeframes line<br>up?)<br><br>Regards,<br><br>Ed<br><br>On 1/14/13 3:58 PM, "Jim Martin" <jim@daedelus.com> wrote:<br><br><blockquote type="cite">Jason,<br>Thanks! I'll work with Ed to make this happen...<br><br>Ed,<br>Nice to meet you, I'm Jim Martin with the IETF NOC. As I<br>understand it, BrightHouse is providing two divergent 1G<br>links to the meeting, delivering both IPv4 and IPv6<br>transit. We have our own AS and address space, and will<br>be providing our own CPE (a pair of Juniper routers).<br>Also, I'm heading to the Caribe Royal for a site visit<br>later this week.<br>I'd like to work with you on the exact details of the<br>circuits, and any site specific information you might<br>need me to collect.<br><br>Looking forward to working with you!<br><br>- Jim<br><br>On Jan 14, 2013, at 12:15 PM, "Livingood, Jason"<br><Jason_Livingood@cable.comcast.com> wrote:<br><br><blockquote type="cite">The contact is Ed Mallette <Edwin.Mallette@bhnis.com><br><br><br>On 1/14/13 3:04 PM, "Ray Pelletier" <rpelletier@isoc.org><br>wrote:<br><br><blockquote type="cite">All;<br><br>Do you have a POC with BrightHouse for Jim with regard<br>to the circuits?<br><br>Ray<br></blockquote></blockquote></blockquote><br><br>________________________________<br><br>CONFIDENTIALITY NOTICE: This e-mail may contain information<br>that is privileged, confidential or otherwise protected<br>from disclosure. If you are not the intended recipient of<br>this e-mail, please notify the sender immediately by<br>return e-mail, purge it and do not disseminate or copy it.<br></blockquote></blockquote><br><br>________________________________<br><br>CONFIDENTIALITY NOTICE: This e-mail may contain information<br>that is privileged, confidential or otherwise protected from<br>disclosure.<br>If<br>you<br>are not the intended recipient of this e-mail, please notify<br>the sender immediately by return e-mail, purge it and do not<br>disseminate or copy it.<br></blockquote></blockquote><br><br>________________________________<br><br>CONFIDENTIALITY NOTICE: This e-mail may contain information<br>that is privileged, confidential or otherwise protected from<br>disclosure.<br>If<br>you<br>are not the intended recipient of this e-mail, please notify<br>the sender immediately by return e-mail, purge it and do not<br>disseminate or copy it.<br></blockquote></blockquote></blockquote><br><br>________________________________<br><br>CONFIDENTIALITY NOTICE: This e-mail may contain information that<br>is privileged, confidential or otherwise protected from<br>disclosure. If you are not the intended recipient of this e-mail,<br>please notify the sender immediately by return e-mail, purge it<br>and do not disseminate or copy it.<br></blockquote></blockquote><br></blockquote><br><br>________________________________<br><br>CONFIDENTIALITY NOTICE: This e-mail may contain information that is<br>privileged, confidential or otherwise protected from disclosure. If<br>you are not the intended recipient of this e-mail, please notify the<br>sender immediately by return e-mail, purge it and do not disseminate or copy it.<br></blockquote><br></blockquote><br><br>________________________________<br><br>CONFIDENTIALITY NOTICE: This e-mail may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient of this e-mail, please notify the sender immediately by return e-mail, purge it and do not disseminate or copy it.<br></div></blockquote></div><br></div></body></html>