<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: rtl;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body style="direction: rtl;" bidimailui-charset-is-forced="true"
bidimailui-detected-decoding-type="latin-charset" bgcolor="#ffffff"
text="#000000">
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;">Dears,</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;">Sahara
Net is the 1st ISP in Saudi Arabia and the Gulf region to provide
a dual stacked ISP service on its Core.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;">A
few months back we launched a project to connect selected Business
clients with dual stack. This has succeeded so far but the demand
is a bit lower than expectations.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;">We
are now ready to provide dual stack to end users (residential) but
lack two things:</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;">1.
User demand: Users simply don't see the benefits for this yet!</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;">2.
CPE availability: Still many CPEs that are popular in the region
are not IPv6/dual stack ready!</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;">Regards..<br>
</p>
<div style="direction: ltr;" class="moz-signature">
<hr style="direction: ltr;">
<p style="direction: ltr;"><map name="FPMap12">
<area shape="rect" coords="470,87,601,109"
href="mail:kais@sahara.com" target="_blank" alt="send an
email to kais@sahara.com">
<area shape="rect" coords="99,108,611,147"
href="http://www.sahara.com" target="_blank" alt="Sahara
Net">
<area shape="rect" coords="5,17,75,120"
href="http://www.sahara.com/" target="_blank" alt="Sahara
Net">
<area shape="rect" coords="81,2,96,132"
href="http://www.sahara.com/" target="_blank" alt="Sahara
Net">
</map>
<img src="cid:part1.08030107.08000703@sahara.com.sa"
usemap="#FPMap12" border="0"></p>
<hr style="direction: ltr;">
<table dir="rtl" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="direction: ltr; text-align: justify; font-weight:
bold; color: grey; font-size: 8px;" valign="top"
width="302">إن هذا البريد الإلكتروني المرسل من قبل صحارى
نت يحتوي على محتويات سرية مرسلة إلى جهة/ متلقٍ مقصود. إذا
لم تكن أنت المتلقي المقصود، فإن هذا البريد الإلكتروني قد
وصلك عن طريق الخطأ، لذا فإنه يمنع منعا باتا أي استخدام أو
إعادة إرسال أو نشر أو طباعة أونسخ كل أو جزء من هذا البريد
الإلكتروني بأي شكل من الأشكال. وفي حالة تلقيكم هذا البريد
الإلكتروني عن طريق الخطأ، فإننا نرجو التكرم بالرد على
المرسل وإخطاره بهذا الخطأ، ومن ثم الإسراع بحذف هذا البريد
الإلكتروني من الأجهزة والأنظمة الخاصة بكم. وعلى الرغم من
أن هذا البريد الإلكتروني تم فحصه وتمحيصه بحثا عن
الفيروسات، إلا أن صحارى نت لا تتحمل أي مسؤولية عن أية
فيروسات قد تصيب أجهزتكم وأنظمتكم، بل إن التأكد من حماية
أجهزتكم وأنظمتكم هو محض مسؤوليتكم.</td>
<td style="direction: ltr;" valign="top" width="18">
<p style="direction: ltr;" dir="rtl"><strong><span
xml:lang="AR-SA" lang="AR-SA"> </span></strong></p>
<br>
</td>
<td style="direction: ltr; text-align: justify; font-weight:
bold; color: grey; font-size: 8px;" valign="top"
width="297">This is an email from Sahara Net. Its contents
are confidential to the intended recipient. If you are not
the intended recipient, be advised that you have received
this e-mail in error and that any use, dissemination,
forwarding, printing or copying of this e-mail is strictly
prohibited. It may not be disclosed to or used by anyone
other than its intended recipient, nor may it be copied in
any way. If received in error please email a reply to the
sender, then delete it from your system. Although this
e-mail has been scanned for viruses, Sahara Net cannot
accept any responsibility for viruses and it is your
responsibility to scan any attachments.</td>
</tr>
</tbody>
</table>
<br>
</div>
<p style="margin-bottom: 0cm; margin-top: 0pt; direction: ltr;"><br>
On 6/13/2011 9:57 AM, Ahmed Abu-Abed wrote:<br>
</p>
<blockquote style="direction: ltr;"
cite="mid:1D1603C34D2E4C5F9F5E6EC13F01EE6E@mTOSH" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.7600.16766">
<div><font face="Calibri">Hi Gaurab,</font></div>
<div> </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> </div>
<div><font face="Calibri">Regards,</font></div>
<div><font face="Calibri">-Ahmed</font></div>
<div> </div>
<div style="font: 10pt Tahoma;">
<div><br>
</div>
<div style="background: none repeat scroll 0% 0% rgb(245, 245,
245);">
<div style=""><b>From:</b> <a moz-do-not-send="true"
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 moz-do-not-send="true"
title="ahmed@tamkien.com" href="mailto:ahmed@tamkien.com">Ahmed
Abu-Abed</a> </div>
<div><b>Cc:</b> <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:gaurab@lahai.com">mailto:gaurab@lahai.com</a>><br>
> *Sent:* Saturday, June 11, 2011 8:21 AM<br>
> *To:* <a moz-do-not-send="true"
href="mailto:menog@menog.net">menog@menog.net</a> <<a
moz-do-not-send="true" 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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:ahmed@tamkien.com">mailto:ahmed@tamkien.com</a>><br>
>> *Cc:* <a moz-do-not-send="true"
href="mailto:%27menog@menog">'menog@menog</a> <<a
moz-do-not-send="true" href="mailto:%27menog@menog">mailto:'menog@menog</a>>.
net' <<a moz-do-not-send="true" href="mailto:%27menog@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 moz-do-not-send="true" href="mailto:Menog@menog.net">Menog@menog.net</a>
<<a moz-do-not-send="true" href="mailto:Menog@menog.net">mailto:Menog@menog.net</a>><br>
>> <a moz-do-not-send="true"
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 moz-do-not-send="true" href="mailto:Menog@menog.net">Menog@menog.net</a>
<<a moz-do-not-send="true" href="mailto:Menog@menog.net">mailto:Menog@menog.net</a>><br>
<a moz-do-not-send="true"
href="http://lists.menog.net/mailman/listinfo/menog">http://lists.menog.net/mailman/listinfo/menog</a><br>
<br>
- -- <br>
<br>
<a moz-do-not-send="true" 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 moz-do-not-send="true"
href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a><br>
<br>
iEYEARECAAYFAk3zEUoACgkQSo7fU26F3X2MvQCdF2BPJIrD7OlYKT6WVedhoWcp<br>
MdYAn1lR8LiWzArp0QsOeFddGrDJ/on1<br>
=wRFh<br>
-----END PGP SIGNATURE-----
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Menog mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Menog@menog.net">Menog@menog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.menog.net/mailman/listinfo/menog">http://lists.menog.net/mailman/listinfo/menog</a>
</pre>
</blockquote>
</body>
</html>