<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"ＭＳ ゴシック";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"ＭＳ Ｐゴシック";
panose-1:2 11 6 0 7 2 5 8 2 4;}
@font-face
{font-family:"\@ＭＳ ゴシック";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"\@ＭＳ Ｐゴシック";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0mm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
h1
{mso-style-priority:9;
mso-style-link:"見出し 1 \(文字\)";
margin:0mm;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Tahoma",sans-serif;
font-weight:normal;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"書式なし \(文字\)";
margin:0mm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"ＭＳ ゴシック";}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
margin:0mm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.1
{mso-style-name:"見出し 1 \(文字\)";
mso-style-priority:9;
mso-style-link:"見出し 1";
font-family:"Tahoma",sans-serif;}
span.a
{mso-style-name:"書式なし \(文字\)";
mso-style-priority:99;
mso-style-link:書式なし;
font-family:"ＭＳ ゴシック";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
/* Page Definitions */
@page WordSection1
{size:612.0pt 792.0pt;
margin:99.25pt 11.0pt 30.0mm 11.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026">
<v:textbox inset="5.85pt,.7pt,5.85pt,.7pt" />
</o:shapedefaults></xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="JA" link="#0563C1" vlink="#954F72" style="text-justify-trim:punctuation">
<div class="WordSection1">
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Hi all, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">> CPE support is the next big frontier in IPv6 deployment.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">That’s why we discussed about the issue with Jordi and other vendors on APNIC 44
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">almost 2 years ago.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><a href="https://conference.apnic.net/44/program/schedule/#/day/6/bof-discussion-with-ipv6-ce-vendors">https://conference.apnic.net/44/program/schedule/#/day/6/bof-discussion-with-ipv6-ce-vendors</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">Following is my presentation at that time.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><a href="https://conference.apnic.net/44/assets/files/APCS549/IPv6-support-at-NEC-CEs.pdf">https://conference.apnic.net/44/assets/files/APCS549/IPv6-support-at-NEC-CEs.pdf</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">After that, we standardized RFC8585.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">So, next step is implemeting
</span><span lang="EN-US">transition technologies and deployment. </span><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">Please let me know if there’s opportunity to use transition technologies
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">we have minimum order quantity though, we may discuss about it.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">Let’s cross the chasm together. :-)
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">Regards,
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">Masanobu
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">========================
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"> NEC Platforms, Ltd.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"> KAWASHIMA Masanobu
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"> kawashimam@vx.jp.nec.com
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black"> https://www.necplatforms.co.jp/en/
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-align:justify;text-justify:inter-ideograph"><span lang="EN-US" style="font-size:10.5pt;font-family:"Tahoma",sans-serif;color:black">========================
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">> -----Original Message-----</span></p>
<p class="MsoPlainText"><span lang="EN-US">> From: NANOG <nanog-bounces@nanog.org> On Behalf Of Lee Howard</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Sent: Friday, August 9, 2019 5:18 AM</span></p>
<p class="MsoPlainText"><span lang="EN-US">> To: nanog@nanog.org</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Subject: Re: MAP-E</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> On 8/2/19 11:39 AM, Jay Hanke wrote:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > Is there a summary presentation someplace laying out the options that</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > are active in the wild with some deployment stats?</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> I can't think of a public presentation off the top of my head that explains how each major transition technology works,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> and the pros and cons of each. There must be one, but it's hard to cover the major options in an hour.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> If you want to know who is using any given transition technology, there's this crowd-sourced list:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> <a href="https://docs.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/edit#gid=0">
<span style="color:windowtext;text-decoration:none">https://docs.google.com/spreadsheets/d/1ksOoWOaRdRyjZnjLSikHf4O5L1OUTNOO_7NK9vcVApc/edit#gid=0</span></a></span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> Very brief summary of options:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> NAT444. Your basic NAT, plus NAT again. You really need to deploy IPv6, too, or all your traffic will go through a</span></p>
<p class="MsoPlainText"><span lang="EN-US">> translator (everything else below assumes native IPv6 is deployed). State information can get expensive. Well understood.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> Dual-stack Lite. CPE sends IPv4 traffic through an IPv6 tunnel</span></p>
<p class="MsoPlainText"><span lang="EN-US">> (softwire) to a pre-configured DS-Lite box, which does NAT44. Works fine, deployed at scale (see sheet above), but</span></p>
<p class="MsoPlainText"><span lang="EN-US">> keeping state on lots of</span></p>
<p class="MsoPlainText"><span lang="EN-US">> NAT44 can get expensive at scale.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> NAT64. IPv6-only to users. DNS resolver given in provisioning information is a DNS64 server. When it does a lookup</span></p>
<p class="MsoPlainText"><span lang="EN-US">> but there's no AAAA, it invents one based on the A record (e.g., 2001:db8:64::<IPv4</span></p>
<p class="MsoPlainText"><span lang="EN-US">> address>). The IPv6 prefix in the invented AAAA is actually a NAT64</span></p>
<p class="MsoPlainText"><span lang="EN-US">> translator. Pro: no CPE support required, well understood. Con: No support for IPv4-only stuff in the prem, breaks</span></p>
<p class="MsoPlainText"><span lang="EN-US">> DNSSEC.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> 464xlat. IPv6-only between CE and NAT64. Any IPv4 traffic the CPE receives, it translates to IPv6 and forwards to</span></p>
<p class="MsoPlainText"><span lang="EN-US">> a destination that's the</span></p>
<p class="MsoPlainText"><span lang="EN-US">> NAT64 server, which translates again. Pro: widely deployed at scale on mobile networks. Con: Very little CPE support</span></p>
<p class="MsoPlainText"><span lang="EN-US">> in home routers.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> MAP-T, MAP-E. IPv6-only between CE and Border Relay (BR). CPE is provisioned with an IPv4 address and a range of ports.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> It does basic NAT44, but only uses the reserved ports. Then it translates to IPv6</span></p>
<p class="MsoPlainText"><span lang="EN-US">> (MAP-T) or encapsulates in IPv6 (MAP-E) and forwards to the configured Border Relay (BR), which changes it to IPv4.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Pro: Stateless, very efficient. Con: Very little CPE support in home routers.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> Jordi is going to tell me there's plenty of support for 464xlat.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> However, you can't go into any old electronics store in North America and buy a home gateway with support for 464xlat</span></p>
<p class="MsoPlainText"><span lang="EN-US">> or MAP. You can't buy them directly from a vendor, unless you're large enough to request a specific firmware build.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Yes, you can get support from OpenWRT, but that's probably not how you want your support team spending their time.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> CPE support is the next big frontier in IPv6 deployment.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> Lee</span></p>
<p class="MsoPlainText"><span lang="EN-US">> </span></p>
<p class="MsoPlainText"><span lang="EN-US">> ></span></p>
<p class="MsoPlainText"><span lang="EN-US">> > On Fri, Aug 2, 2019 at 10:34 AM JORDI PALET MARTINEZ via NANOG</span></p>
<p class="MsoPlainText"><span lang="EN-US">> > <<a href="mailto:nanog@nanog.org"><span style="color:windowtext;text-decoration:none">nanog@nanog.org</span></a>> wrote:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> I understand that, but the inconvenient is the fix allocation of ports per client, and not all the clients use</span></p>
<p class="MsoPlainText"><span lang="EN-US">> the same number of ports. Every option has good and bad things.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> MAP is less efficient in terms of maximizing the
</span><span lang="EN-US" style="font-family:"Courier New"">“</span><span lang="EN-US">use</span><span lang="EN-US" style="font-family:"Courier New"">”</span><span lang="EN-US"> of the existing IPv4 addresses.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> <a href="https://datatracker.ietf.org/doc/draft-lmhp-v6ops-transition-comparis">
<span style="color:windowtext;text-decoration:none">https://datatracker.ietf.org/doc/draft-lmhp-v6ops-transition-comparis</span></a></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> on/</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Regards,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Jordi</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> @jordipalet</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> El 2/8/19 17:25, "NANOG en nombre de Baldur Norddahl" <<a href="mailto:nanog-bounces@nanog.org%20en%20nombre%20de%20baldur.norddahl@gmail.com"><span style="color:windowtext;text-decoration:none">nanog-bounces@nanog.org
en nombre de</span></a></span></p>
<p class="MsoPlainText"><span lang="EN-US"><a href="mailto:nanog-bounces@nanog.org%20en%20nombre%20de%20baldur.norddahl@gmail.com"><span style="color:windowtext;text-decoration:none">> baldur.norddahl@gmail.com</span></a>> escribi</span><span lang="EN-US" style="font-family:"Courier New"">ó</span><span lang="EN-US">:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Hi Jordi</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> My alternative to MAP-E is plain old NAT 444 dual stack. I am trying to avoid the expense and operative nightmare</span></p>
<p class="MsoPlainText"><span lang="EN-US">> of having to run a redundant NAT server setup with thousands of users. MAP is the only alternative that avoids a provider</span></p>
<p class="MsoPlainText"><span lang="EN-US">> run NAT server.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Regards,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Baldur</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> On Fri, Aug 2, 2019 at 3:38 PM JORDI PALET MARTINEZ via NANOG <<a href="mailto:nanog@nanog.org"><span style="color:windowtext;text-decoration:none">nanog@nanog.org</span></a>> wrote:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Ask the vendor to support RFC8585.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Also, you can do it with OpenWRT.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> I think 464XLAT is a better option and both of them are supported by OpenWRT.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> You can also use OpenSource (Jool) for the NAT64.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Regards,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Jordi</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> @jordipalet</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> El 2/8/19 14:20, "NANOG en nombre de Baldur Norddahl" <<a href="mailto:nanog-bounces@nanog.org%20en%20nombre%20de%20baldur.norddahl@gmail.com"><span style="color:windowtext;text-decoration:none">nanog-bounces@nanog.org
en nombre de</span></a></span></p>
<p class="MsoPlainText"><span lang="EN-US"><a href="mailto:nanog-bounces@nanog.org%20en%20nombre%20de%20baldur.norddahl@gmail.com"><span style="color:windowtext;text-decoration:none">> baldur.norddahl@gmail.com</span></a>> escribi</span><span lang="EN-US" style="font-family:"Courier New"">ó</span><span lang="EN-US">:</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Hello</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Are there any known public deployments of MAP-E? What about CPE routers with support?</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> The pricing on IPv4 is now at USD 20/address so I am thinking we are forced to go the CGN route going forward.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> Of all the options, MAP-E appears to be the most elegant. Just add/remove some more headers on a packet and route</span></p>
<p class="MsoPlainText"><span lang="EN-US">> it as normal. No need to invest in anything as our core routers can already do that. No worries about scale.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> BUT - our current CPE has zero support. We are too small that they will make this feature just for us, so I need</span></p>
<p class="MsoPlainText"><span lang="EN-US">> to convince them there is going to be a demand. Alternatively I need to find a different CPE vendor that has MAP-E</span></p>
<p class="MsoPlainText"><span lang="EN-US">> support, but are there any?</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> What is holding MAP-E back? In my view MAP-E could be the end game for IPv4. Customers get full IPv6 and enough</span></p>
<p class="MsoPlainText"><span lang="EN-US">> of IPv4 to be somewhat compatible. The ISP networks are not forced to do a lot of processing such as CGN otherwise</span></p>
<p class="MsoPlainText"><span lang="EN-US">> requires.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> I read some posts from Japan where users are reporting a deployment of MAP-E. Anyone know about that?</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Regards,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Baldur</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> **********************************************</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> IPv4 is over</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Are you ready for the new Internet ?</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> <a href="http://www.theipv6company.com">
<span style="color:windowtext;text-decoration:none">http://www.theipv6company.com</span></a></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> The IPv6 Company</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> This electronic message contains information which may be privileged or confidential. The information is intended</span></p>
<p class="MsoPlainText"><span lang="EN-US">> to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> distribution or use of the contents of this information, even if partially, including attached files, is strictly</span></p>
<p class="MsoPlainText"><span lang="EN-US">> prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> copying, distribution or use of the contents of this information, even if partially, including attached files, is</span></p>
<p class="MsoPlainText"><span lang="EN-US">> strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about</span></p>
<p class="MsoPlainText"><span lang="EN-US">> this communication and delete it.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> **********************************************</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> IPv4 is over</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> Are you ready for the new Internet ?</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> <a href="http://www.theipv6company.com">
<span style="color:windowtext;text-decoration:none">http://www.theipv6company.com</span></a></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> The IPv6 Company</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> >> This electronic message contains information which may be privileged or confidential. The information is intended</span></p>
<p class="MsoPlainText"><span lang="EN-US">> to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> distribution or use of the contents of this information, even if partially, including attached files, is strictly</span></p>
<p class="MsoPlainText"><span lang="EN-US">> prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure,</span></p>
<p class="MsoPlainText"><span lang="EN-US">> copying, distribution or use of the contents of this information, even if partially, including attached files, is</span></p>
<p class="MsoPlainText"><span lang="EN-US">> strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about</span></p>
<p class="MsoPlainText"><span lang="EN-US">> this communication and delete it.</span></p>
<p class="MsoPlainText"><span lang="EN-US">> >></span></p>
<p class="MsoPlainText"><span lang="EN-US">> ></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>