<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
We know it is not a matter of crying wolf on false asumptions becasue as it is now we know that the wolf eventually will come, this is really a preemption of the wolf's coming so that we can be prepared for it. <br>There need to be forceful policies that will enhance the integration of v4 and v6 and well as a full migration to v6. We need to engage in intensive research that will provide an environment where the two can co-exist without conflicts, without compatibility, user and security issues.<br><br>We cannot let the coming catch us unprepared because it definitely is coming. <br><br>Regards,<br>Basil Harriott<br><br>"You don't need wings to fly"<br><br><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">From: paul@redbarn.org<br>Date: Wed, 27 Feb 2013 11:23:10 -0800<br>To: msalim@localweb.com; Jawaid.Bazyar@foreThought.net; arin-discuss@arin.net<br>Subject: Re: [arin-discuss] Implementing IPv6<br><br>Its going to be a bit of a mess if folks wait for the sky to fall before planning and executing their v6 migration.<br>
<br>
Also if more folks would get it done then the transition and translation costs for those coming in after v4 is gone will be lower.<br>
<br>
There is and had been every reason to expedite, so, nothing that's happened so far should be thought of as crying wolf.<br>
<br>
Paul<br><br><div class="ecxgmail_quote">"Mike A. Salim" <msalim@localweb.com> wrote:<blockquote class="ecxgmail_quote" style="padding-left:1ex">
<pre style="white-space:pre-wrap;word-wrap:break-word;font-family:monospace">Is IPv4 space "really" running out any time soon? Since "wolf" was cried almost two years ago and the sky didn't fall yet, I do not see an immediate mass rush to IPv6 coming yet.<br><br>As for simple / stupid checklists, these abound.<br><br>I googled for IPv6 checklists and found:<br><br><a href="http://technet.microsoft.com/en-us/library/cc786337%28v=ws.10%29.aspx" target="_blank">http://technet.microsoft.com/en-us/library/cc786337(v=ws.10).aspx</a><br><br><a href="http://www.es.net/services/ipv6-network/ipv6-implementation-checklist" target="_blank">http://www.es.net/services/ipv6-network/ipv6-implementation-checklist</a>/<br><br><a href="http://www.infoworld.com/d/data-explosion/your-handy-ipv6-checklist-232" target="_blank">http://www.infoworld.com/d/data-explosion/your-handy-ipv6-checklist-232</a><br><br>There is probably no "one size fits all" checklist. For example, how much practical attention is
being
paid to IPv6 security at this point? Zero to none as far as I can tell. I am having a hard time finding any commercial or open source IPv6 monitoring tools that will just tell me if my http is alive over IPv6, let alone IPv6 specific security tools.<br><br>Mike<br><br>A. Michael Salim<br>VP and Chief Technology Officer,<br>American Data Technology, Inc.<br>PO Box 12892<br>Research Triangle Park, NC 27709, USA<br>P: (919)544-4101 x101<br>F: (919)544-5345<br>E: msalim@localweb.com<br>W: <a href="http://www.localweb.com" target="_blank">http://www.localweb.com</a><br><br>PRIVACY NOTIFICATION: This e-mail message, including any attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is for the sole use of the intended recipient(s). It may contain confidential and/or legally privileged information. Unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender
by
reply e-mail and destroy all copies of the original message.<br><br>Please don't print this e-mail unless you really need to. <br><br><br>-----Original Message-----<br>From: arin-discuss-bounces@arin.net [mailto:arin-discuss-bounces@arin.net] On Behalf Of Jawaid Bazyar<br>Sent: Wednesday, February 27, 2013 12:03 PM<br>To: arin-discuss@arin.net<br>Subject: Re: [arin-discuss] Implementing IPv6<br><br>What is really needed is simple cookbooks for ISPs and business networks<br>- step by step checklist of everything you need to do to fully enable and support IPv6.<br><br>We have implemented IPv6 and successfully tested it directly. What we don't have is clear methodology around IPv4 to v6 gateways and vice-versa.<br><br>Make it stupid easy to implement and it will get done.<br><br>On 02/27/2013 09:40 AM, Tim St. Pierre wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px solid #729fcf;padding-left:1ex">So how do we make it "The end of the Freakin' IPv4 World" so people <br>will actually do this already.<br><br>I talk to access ISPs about it all the time, and the usual response is <br>"well, we're working on it, but it's years away. It isn't really a <br>priority right now." I think if we set a deadline, like "World Turn <br>off IPv4 day", then we will actually see some traction.<br><br>-Tim<br><br>On 13-02-27 10:52 AM, Adrian Goins wrote:<br><blockquote class="ecxgmail_quote" style="border-left:1px solid #ad7fa8;padding-left:1ex">I was sucked into the Cogent/HE problems during World IPv6 day v1 and <br>v2. It ultimately affected one of my clients deciding to keep IPv6 up <br>for their infrastructure - they saw that split in reachability as bad <br>for their customers, since customers using HE as a tunnel broker <br>would think that the client was the problem, not peering. For most <br>users of the Internet
discussions about peering have no value.<br><br>I agree with the statement about multihoming being the solution. If <br>you can't afford to multihome, see about getting your connectivity <br>from a provider who _is_ multihomed. It puts you a couple hops away <br>from the backbone, but it may be worth it to route around this issue.<br>You might even be able to find someone in your datacenter who can <br>throw a cross-connect to your cage and push you out to L3 or ATT or <br>someone other than Cogent.<br><br>We're up with IPv6 transit from Cogent and L3, using our own /32. I <br>have the opportunity to get transit directly from HE, and I'm <br>considering doing so as well. I think that the whole squabble is bad <br>for the Internet and terrible for IPv6 adoption as a whole, but it's <br>almost worth it for me to pay for the extra handoff to not be drawn <br>into it any more than I have to be.<br><br>What I'm waiting for is IPv6 to the real end
users.
If TWC or Comcast <br>or Vz would reliably roll out IPv6 across their customer networks, it <br>would make life much easier. One of our providers at our EU office <br>was kind enough to enable IPv6 on our wireless link, but when I asked <br>them about giving me a /64 or /48, they were stupefied. It hadn't <br>occurred to them that we actually need to have an IP block in order <br>to make use of it.<br><br>I think we're still a long way off from where we should be for <br>awareness and adoption, and, like most things business humans do, <br>until it's actually the end of the freakin' IPv4 world, no one is <br>going to make a move.<br><br>Adrian Goins<br>agoins@arces.net <mailto:agoins@arces.net><br><br><br><br><br>On Feb 22, 2013, at 3:37 PM, Kerry L. Kriegel <kkriegel@cyberlynk.net <br><mailto:kkriegel@cyberlynk.net>> wrote:<br><br><blockquote class="ecxgmail_quote" style="border-left:1px s\00000d\00000a olid\00000d\00000a#8ae234;padding-left:1ex">We only broadcast our data center /32. Cogent is the only provider <br>we have doing IPv6 at the moment.<br>AT&T says they do it, but getting it implemented across our peering <br>link has been in process for several months.<br>TWTC has the request, and may be online within the week.<br>TWC -- no way.<br>Cogent – online.<br>Level3 – online in about 45 days.<br>Thank you,<br>*Kerry L. Kriegel*<br>Network Operations Engineer<br>Cyberlynk Network, Inc.<br>Office: 414-858-9335<br>Fax: 414-858-9336<br>*From:*Michael Wallace [mailto:michael@birdhosting.com <br><<a href="http://birdhosting.com" target="_blank">http://birdhosting.com</a>>] *Sent:*Friday, February 22, 2013 10:53 AM <br>*To:*Kerry L. Kriegel; arin-discuss@arin.net <br><mailto:arin-discuss@arin.net><br>*Subject:*re: [arin-discuss] Implementing IPv6<br><br>There are plenty of providers out there that do IPv6. We are <br>currently terminating to a
bunch
of them. Abovenet, Level3, HE, etc <br>etc. Are you broadcasting the BGP for these?<br><br>Thanks,<br><br>Michael Wallace<br>Bird Hosting<br><br><hr><br>----<br><br>*From*: "Kerry L. Kriegel" <kkriegel@cyberlynk.net <br><mailto:kkriegel@cyberlynk.net>><br>*Sent*: Friday, February 22, 2013 8:48 AM *To*:arin-discuss@arin.net <br><mailto:arin-discuss@arin.net><br>*Subject*: [arin-discuss] Implementing IPv6<br><br>We received our /32 IPv6 block from ARIN awhile back but before we <br>could do anything with it we needed to do some hardware / IOS <br>upgrades on our backbone. We got enough of that finished last week <br>that we decided to “roll out” IPv6 and see how things looked.<br>After a couple days of trouble shooting why none of the engineers in <br>our data center could reach their Hurricane Electric Tunnel networks <br>at home (and vice versa), I stopped looking at our backbone and <br>started looking a
t
Google.<br>It appears that the squabble started in 2009 between Cogent and HE <br>is still in progress. I was wondering if anyone on this list had any <br>“inside” information about the problem and whether or not there was <br>an end in sight. It seems to me that having a disconnect between two <br>major players is going to hinder IPv6 adaptation.<br>Thank you,<br>*Kerry L. Kriegel*<br>Network Operations Engineer<br>Cyberlynk Network, Inc.<br>Office: 414-858-9335<br>Fax: 414-858-9336<br><hr><br>ARIN-Discuss<br>You are receiving this message because you are subscribed to the <br>ARIN Discussion Mailing List (ARIN-discuss@arin.net <br><mailto:ARIN-discuss@arin.net>).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="http://lists.arin.net/mailman/listinfo/arin-discuss" target="_blank">http://lists.arin.net/mailman/listinfo/arin-discuss</a><br>Please contact info@arin.net if you experience any issues.</blockquote><br><br><br><hr><br>ARIN-Discuss<br>You are receiving this message because you are subscribed to the ARIN <br>Discussion Mailing List (ARIN-discuss@arin.net).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="http://lists.arin.net/mailman/listinfo/arin-discuss" target="_blank">http://lists.arin.net/mailman/listinfo/arin-discuss</a><br>Please contactinfo@arin.net if you experience any issues.</blockquote><br><br>--<br>--<br>Tim St. Pierre<br>System Operator<br>Communicate Freely<br>289 225 1220 x5101<br>tim@communicatefreely.net<br><a href="http://www.communicatefreely.net" target="_blank">www.communicatefreely.net</a><br><br><br><hr><br>ARIN-Discuss<br>You are receiving this message because you are subscribed to the ARIN <br>Discussion Mailing List (ARIN-discuss@arin.net).<br>Unsubscribe or manage your mailing list subscription at:<br><a href="http://lists.arin.net/mailman/listinfo/arin-discuss" target="_blank">http://lists.arin.net/mailman/listinfo/arin-discuss</a><br>Please contact info@arin.net if you experience any issues.</blockquote></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br>_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (ARIN-discuss@arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-discuss
Please contact info@arin.net if you experience any issues.</div> </div></body>
</html>