<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16766"></HEAD>
<BODY style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px"
id=MailContainerBody leftMargin=0 topMargin=0 CanvasTabStop="true"
name="Compose message area">
<DIV><FONT face=Calibri>Hi Gaurab,</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>I know that many regional ISPs started the effort
towards dual-stacking their core, and a few have reached this target, but I
am yet to see an advertised IPv6 access service to residential users.
</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>Regards,</FONT></DIV>
<DIV><FONT face=Calibri>-Ahmed</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV style="FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=gaurab@lahai.com
href="mailto:gaurab@lahai.com">Gaurab Raj Upadhaya</A> </DIV>
<DIV><B>Sent:</B> Saturday, June 11, 2011 9:55 AM</DIV>
<DIV><B>To:</B> <A title=ahmed@tamkien.com href="mailto:ahmed@tamkien.com">Ahmed
Abu-Abed</A> </DIV>
<DIV><B>Cc:</B> <A title=menog@menog.net
href="mailto:menog@menog.net">menog@menog.net</A> </DIV>
<DIV><B>Subject:</B> Re: [menog] Rapid IPv6 deployment for World IPv6
Day</DIV></DIV></DIV>
<DIV><BR></DIV>-----BEGIN PGP SIGNED MESSAGE-----<BR>Hash: SHA1<BR><BR>Hi
Ahmed,<BR><BR>Well, to end-users (either residential or business users).
Not at an<BR>ISP-ISP level.<BR><BR>- -gaurab<BR><BR><BR>On 6/11/11 7:27 AM,
Ahmed Abu-Abed wrote:<BR>> Hi Gaurab,<BR>> <BR>> By v6 to
end-users, do you mean residential users ?<BR>> <BR>>
Regards,<BR>> -Ahmed<BR>> <BR>> <BR>> <BR>> *From:*
Gaurab Raj Upadhaya <<A
href="mailto:gaurab@lahai.com">mailto:gaurab@lahai.com</A>><BR>> *Sent:*
Saturday, June 11, 2011 8:21 AM<BR>> *To:* <A
href="mailto:menog@menog.net">menog@menog.net</A> <<A
href="mailto:menog@menog.net">mailto:menog@menog.net</A>><BR>> *Subject:*
Re: [menog] Rapid IPv6 deployment for World IPv6 Day<BR>> <BR>> Hi Ahmed,
others,<BR>> <BR>> Do we have any ISPs/ Carriers in the ME region that
provide v6 to<BR>> end-users (either as Tunnels, or native ).<BR>>
<BR>> thanks<BR>> -gaurab<BR>> <BR>> <BR>> On 6/9/11 1:41 PM,
Ahmed Abu-Abed wrote:<BR>>> My comments below with a minor correction in
the 1st comment.<BR>> <BR>>> -Ahmed<BR>> <BR>> <BR>>>
*From:* Brian Candler <<A
href="mailto:B.Candler@pobox.com">mailto:B.Candler@pobox.com</A>><BR>>>
*Sent:* Thursday, June 09, 2011 12:54 PM<BR>>> *To:* Ahmed Abu-Abed <<A
href="mailto:ahmed@tamkien.com">mailto:ahmed@tamkien.com</A>><BR>>>
*Cc:* <A href="mailto:'menog@menog">'menog@menog</A> <<A
href="mailto:'menog@menog">mailto:'menog@menog</A>>. net' <<A
href="mailto:'menog@menog">mailto:'menog@menog</A>. net'><BR>>>
*Subject:* Re: [menog] Rapid IPv6 deployment for World IPv6 Day<BR>>
<BR>>> On Thu, Jun 09, 2011 at 10:51:26AM +0300, Ahmed Abu-Abed
wrote:<BR>>>> >> Until the whole internet AND
web content AND networks AND<BR>>>> applications move
to IPv6 ONLY then there will be a need for<BR>>
tunneling.<BR>>>> Dual-stacking is needed but it
doesn't solve the IPv4 depletion issue,<BR>> <BR>>> But client-side
tunnelling relies on having an IPv4 address too, so it<BR>>> doesn't solve
depletion.<BR>>> />> It may not solve depletion but tunneling
accelerates IPv6<BR>>> adoption, while "carrier grade" tunnels present a
more stable approach<BR>>> than multi-level NATs. Future networks will
likely be IPv6-only except<BR>>> for the dual-stack hosts that tunnel
IPv4-in-IPv6 , a reverse of today's<BR>>> tunnels. Refer to the DS-Lite
standards among others, and this approach<BR>>> is part of the 3GPP/LTE
standards for mobile networks migration to IPv6./<BR>>> //<BR>>>
Estimates I've seen so far from IPv6 day suggest that although traffic
was<BR>>> up, V6 accounted for between 0.02% and 0.3% of total
traffic. Of<BR>> that, 90%<BR>>> was tunnelled (i.e. only 10%
native). So basically: (1) there is no<BR>>> signficiant IPv6
Internet today, and (2) if you want to join what<BR>> there is,<BR>>>
you do indeed probably have to tunnel.<BR>>> />> Tunnels solve the
chicken and egg problem, it allows IPv6 content to<BR>>> be accessible
until IPv6 gains a wider installed base which may take<BR>>> years. During
the same time the burden of running IPv4 with no public<BR>>> addresses
will grow. Both RIPE NCC and ARIN have publicly endorsed<BR>>> tunneling
to speed up IPv6 deployment./<BR>> <BR>>> That doesn't mean that
installing a tunnel client is a good idea for<BR>> anyone<BR>>> except
network specialists who know what they're doing.<BR>>> />> Protocols
that automate the setup of carrier grade tunnels, such as<BR>>> TSP, make
installing tunnels a plug and play affair. Refer to my<BR>>> original
email and try it to see for yourself. For zero user<BR>>> intervention
needs, there are CPE IPv6 Adapters that plug in an ethernet<BR>>> port on
an IPv4 home router and automatically setup IPv6-in-IPv4 tunnels<BR>>>
(see the ARIN Wiki on IPv6 CPEs). All these are carrier grade
solutions<BR>>> and have been deployed by tier-1 carriers./<BR>>
<BR>>> If random end-users start installing this stuff without
understanding it,<BR>>> then (a) they are probably opening up security
holes into their<BR>> network, and<BR>>> (b) they may impede a later
smooth rollout of native v6.<BR>>> />> Whether users dual-stack or
tunnel to IPv6 the security requirements<BR>>> are mostly the same.
Waiting for end-to-end dual-stack to be deployed<BR>>> all the way to the
home CPE to complete is a multi year project. And I<BR>>> don't see
IPv6-in-IPv4 tunnels impeding rollout of native IPv6 if the<BR>>> tunnels
clients AND servers are fully under control of the ISP and part<BR>>> of
their network. The rule here is for ISPs to avoid using Teredo, 6to4<BR>>>
and ISATAP tunnels which, unfortunately, are everywhere./<BR>> <BR>>
<BR>> <BR>> <BR>>>
_______________________________________________<BR>>> Menog mailing
list<BR>>> <A href="mailto:Menog@menog.net">Menog@menog.net</A> <<A
href="mailto:Menog@menog.net">mailto:Menog@menog.net</A>><BR>>> <A
href="http://lists.menog.net/mailman/listinfo/menog">http://lists.menog.net/mailman/listinfo/menog</A><BR>>
<BR>> <BR>_______________________________________________<BR>Menog mailing
list<BR><A href="mailto:Menog@menog.net">Menog@menog.net</A> <<A
href="mailto:Menog@menog.net">mailto:Menog@menog.net</A>><BR><A
href="http://lists.menog.net/mailman/listinfo/menog">http://lists.menog.net/mailman/listinfo/menog</A><BR><BR>-
-- <BR><BR><A
href="http://www.gaurab.org.np/">http://www.gaurab.org.np/</A><BR><BR><BR>-----BEGIN
PGP SIGNATURE-----<BR>Version: GnuPG/MacGPG2 v2.0.16 (Darwin)<BR>Comment: Using
GnuPG with Mozilla - <A
href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A><BR><BR>iEYEARECAAYFAk3zEUoACgkQSo7fU26F3X2MvQCdF2BPJIrD7OlYKT6WVedhoWcp<BR>MdYAn1lR8LiWzArp0QsOeFddGrDJ/on1<BR>=wRFh<BR>-----END
PGP SIGNATURE-----</BODY></HTML>