<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">That does not need to be long, Abe.
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">There’s no minimal interval between version. I already published 01… And I do not have a special address format beyond what’s in the draft already. It’s only IPv4 and IPv6. No
new address format. Just assigned ranges, and well known IIDs.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">To your point: the addresses in each realm are the full IPv4 that we know and they cannot talk directly between realms. They are indeed isolated. Nodes in different floors can
only communicate through the shaft. Think of a human and a stairwell. The physical space reserved for the stair well at each level is the same. What people do with the rest of the space is their own. All addresses and AS numbers are reusable.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">I do not see you image of a sphere. My image of a sphere is IPv6, that contains all the IPv4 “planes”, the shaft, and all the air in between.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">You design uses the internet as shaft if you like. In that we differ. YADA leaves the internet as is, and allows to build other internets that cannot leak in one another. But
participating nodes can communicate through the shaft.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">If end nodes do not participate, then a stateful Nat is still needed. For most homes that means an upgrade of the stateful NAT in the gateway so the public side has a YATT format,
and DNS snooping to provide a A record inside. Same for PLATs. For most servers, that means an update in the load balancer, and a NAT if there was none, to allow to speak to other realms. Whatever happened in the current IPv4 can still do. Some levels can
be created IPv6 only from the start, providing YATT addresses to those who need to communicate with the other levels.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Keep safe;<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Pascal<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-weight:bold">From:</span></font></b> Abraham Y. Chen <aychen@avinta.com>
<br>
<b><span style="font-weight:bold">Sent:</span></b> vendredi 1 avril 2022 23:45<br>
<b><span style="font-weight:bold">To:</span></b> Pascal Thubert (pthubert) <pthubert@cisco.com>; Vasilenko Eduard <vasilenko.eduard@huawei.com>; Justin Streiner <streinerj@gmail.com><br>
<b><span style="font-weight:bold">Cc:</span></b> NANOG <nanog@nanog.org><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: Let's Focus on Moving Forward Re: V6 still not supported re: 202203261833.AYC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">Hi, Pascal:</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">1) " ... </span></font> for the next version. ... <font size="4"><span style="font-size:13.5pt"> ": I am not sure that I can wait for so long, because I am asking for
the basics. The reason that I asked for an IP packet header example of your proposal is to visualize what do you mean by the model of "realms and shafts in a multi-level building". The presentation in the draft sounds okay, because the floors are physically
isolated from one another. And, even the building is isolated from other buildings. This is pretty much how PBX numbering plan worked.
</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">2) When you extend each floor to use the whole IPv4 address pool, however, you are essential talking about covering the entire surface of the earth. Then, there is no isolated
buildings with isolated floors to deploy your model anymore. There is only one spherical layer of physical earth surface for you to use as a realm, which is the current IPv4 deployment. How could you still have multiple full IPv4 address sets deployed, yet
not seeing their identical twins, triplets, etc.? Are you proposing multiple spherical layers of "realms", one on top of the other?</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">2) When I cited the DotConnectAfrica graphic logo as a visual model for the EzIP deployment over current IPv4, I was pretty specific that each RAN was tethered from the current
Internet core via one IPv4 address. We were very careful about isolating the netblocks in terms of which one does what. In other words, even though the collection of RANs form a parallel cyberspace to the Internet, you may look at each RAN as an isolated balloon
for others. So that each RAN can use up the entire 240/4 netblock. </span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">Please clarify your configuration.</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">Thanks,</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">Abe (2022-04-01 17:44)
</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">On 2022-04-01 10:55, Abraham Y. Chen wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">On 2022-04-01 10:00, Pascal Thubert (pthubert) wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Makes sense, Abe, for the next version.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Note that the intention is NOT any to ANY. A native IPv6 IoT device can only talk to another IPv6 device, where that other device may use a YATT address or any other IPv6 address.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">But it cannot talk to a YADA node. That’s what I mean by baby steps for those who want to.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Keep safe;<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Pascal<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-weight:bold">From:</span></font></b> Abraham Y. Chen
<a href="mailto:aychen@avinta.com"><aychen@avinta.com></a> <br>
<b><span style="font-weight:bold">Sent:</span></b> vendredi 1 avril 2022 15:49<br>
<b><span style="font-weight:bold">To:</span></b> Vasilenko Eduard <a href="mailto:vasilenko.eduard@huawei.com">
<vasilenko.eduard@huawei.com></a>; Pascal Thubert (pthubert) <a href="mailto:pthubert@cisco.com">
<pthubert@cisco.com></a>; Justin Streiner <a href="mailto:streinerj@gmail.com"><streinerj@gmail.com></a><br>
<b><span style="font-weight:bold">Cc:</span></b> NANOG <a href="mailto:nanog@nanog.org">
<nanog@nanog.org></a><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: Let's Focus on Moving Forward Re: V6 still not supported re: 202203261833.AYC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">Hi, Pascal:</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">What I would appreciate is an IP packet header design/definition layout, word-by-word, ideally in bit-map style, of an explicit presentation of all IP addresses involved from
one IoT in one realm to that in the second realm. This will provide a clearer picture of how the real world implementation may look like.</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">Thanks,</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">Abe (2022-04-01 09:48)</span></font><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">On 2022-04-01 08:49, Vasilenko Eduard wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">As I understand: “IPv4 Realms” between “Shaft” should be capable to have a plain IPv4 header (or else why all of these).</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Then Gateway in the Shaft should change headers (from IPv4 to IPv6).</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Who should implement this gateway and why? He should be formally appointed to such an exercise, right?</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Map this 2 level hierarchy to the real world – you may fail with this.</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Ed/</span></font><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-weight:bold">From:</span></font></b> Pascal Thubert (pthubert) [<a href="mailto:pthubert@cisco.com">mailto:pthubert@cisco.com</a>]
<br>
<b><span style="font-weight:bold">Sent:</span></b> Friday, April 1, 2022 3:41 PM<br>
<b><span style="font-weight:bold">To:</span></b> Vasilenko Eduard <a href="mailto:vasilenko.eduard@huawei.com">
<vasilenko.eduard@huawei.com></a>; Justin Streiner <a href="mailto:streinerj@gmail.com">
<streinerj@gmail.com></a>; Abraham Y. Chen <a href="mailto:aychen@avinta.com"><aychen@avinta.com></a><br>
<b><span style="font-weight:bold">Subject:</span></b> RE: Let's Focus on Moving Forward Re: V6 still not supported re: 202203261833.AYC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Hello Eduard:<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Did you just demonstrate that POPs cannot exist? Or that there cannot be a Default Free Zone?<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">I agree with your real world issue that some things will have to be planned between stake holders, and that it will not be easy.
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">But you know what the French say about “impossible”.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Or to paraphrase Sir Arthur, now that we have eliminated all the impossible transition scenarios, whatever remains…<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">There will be YADA prefixes just like there are root DNS. To be managed by different players as you point out. And all routable within the same shaft.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Keep safe;<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Pascal<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-weight:bold">From:</span></font></b> Vasilenko Eduard <<a href="mailto:vasilenko.eduard@huawei.com">vasilenko.eduard@huawei.com</a>>
<br>
<b><span style="font-weight:bold">Sent:</span></b> vendredi 1 avril 2022 14:32<br>
<b><span style="font-weight:bold">To:</span></b> Pascal Thubert (pthubert) <<a href="mailto:pthubert@cisco.com">pthubert@cisco.com</a>>; Justin Streiner <<a href="mailto:streinerj@gmail.com">streinerj@gmail.com</a>>; Abraham Y. Chen <<a href="mailto:aychen@avinta.com">aychen@avinta.com</a>><br>
<b><span style="font-weight:bold">Subject:</span></b> RE: Let's Focus on Moving Forward Re: V6 still not supported re: 202203261833.AYC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Hi Pascal,</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">In general, your idea to create a hierarchy is good.</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">In practice, it would fail because you have created a virtual hierarchy that does not map to any administrative border. Who should implement gateways
for the “Shaft”? Why?</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">If you would appoint Carrier as the Shaft responsible then it is not enough bits for Shaft.</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">If you would appoint Governments as the Shaft responsible then would be a so big scandal that you would regret the proposal.</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Hence, I do not see proper mapping for the hierarchy to make YADA successful.</span></font><o:p></o:p></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;color:#1F497D">Eduard</span></font><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-weight:bold">From:</span></font></b> NANOG [<a href="mailto:nanog-bounces+vasilenko.eduard=huawei.com@nanog.org">mailto:nanog-bounces+vasilenko.eduard=huawei.com@nanog.org</a>]
<b><span style="font-weight:bold">On Behalf Of </span></b>Pascal Thubert (pthubert) via NANOG<br>
<b><span style="font-weight:bold">Sent:</span></b> Friday, April 1, 2022 2:26 PM<br>
<b><span style="font-weight:bold">To:</span></b> Justin Streiner <<a href="mailto:streinerj@gmail.com">streinerj@gmail.com</a>>; Abraham Y. Chen <<a href="mailto:aychen@avinta.com">aychen@avinta.com</a>><br>
<b><span style="font-weight:bold">Cc:</span></b> NANOG <<a href="mailto:nanog@nanog.org">nanog@nanog.org</a>><br>
<b><span style="font-weight:bold">Subject:</span></b> RE: Let's Focus on Moving Forward Re: V6 still not supported re: 202203261833.AYC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">For the sake of it, Justin, I just published
<a href="https://datatracker.ietf.org/doc/draft-thubert-v6ops-yada-yatt/">https://datatracker.ietf.org/doc/draft-thubert-v6ops-yada-yatt/</a>.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">The first section of the draft (YADA) extends IPv4 range in an IPv4-only world. For some people that might be enough and I’m totally fine with that.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Keep safe;<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Pascal<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-weight:bold">From:</span></font></b> NANOG <<a href="mailto:nanog-bounces+pthubert=cisco.com@nanog.org">nanog-bounces+pthubert=cisco.com@nanog.org</a>>
<b><span style="font-weight:bold">On Behalf Of </span></b>Justin Streiner<br>
<b><span style="font-weight:bold">Sent:</span></b> dimanche 27 mars 2022 18:12<br>
<b><span style="font-weight:bold">To:</span></b> Abraham Y. Chen <<a href="mailto:aychen@avinta.com">aychen@avinta.com</a>><br>
<b><span style="font-weight:bold">Cc:</span></b> NANOG <<a href="mailto:nanog@nanog.org">nanog@nanog.org</a>><br>
<b><span style="font-weight:bold">Subject:</span></b> Re: Let's Focus on Moving Forward Re: V6 still not supported re: 202203261833.AYC<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Abe:<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">To your first point about denying that anyone is being stopped from working on IPv4, I'm referring to users being able to communicate via IPv4. I have seen no evidence of that.<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">I'm not familiar with the process of submitting ideas to IETF, so I'll leave that for others who are more knowledgeable on that to speak up if they're so inclined.<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">Thank you<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">jms<o:p></o:p></span></font></p>
</div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt">On Sat, Mar 26, 2022 at 6:43 PM Abraham Y. Chen <<a href="mailto:aychen@avinta.com">aychen@avinta.com</a>> wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font size="4" face="Calibri"><span style="font-size:13.5pt">1) "... no one is stopping anyone from working on IPv4 ... ": After all these discussions, are you still denying this basic issue? For example, there has not been any
straightforward way to introduce IPv4 enhancement ideas to IETF since at least 2015. If you know the way, please make it public. I am sure that many are eager to learn about it. Thanks.</span></font><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
<p><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2">
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
<table class="MsoNormalTable" border="1" cellpadding="0" style="border:none;border-top:solid #D3D4DE 1.0pt">
<tbody>
<tr>
<td width="55" style="width:41.25pt;border:none;padding:9.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0cm;text-decoration:none"><img border="0" width="46" height="29" style="width:.4791in;height:.302in" id="Picture_x0020_1" src="cid:image001.jpg@01D8467E.71158910" alt="Image removed by sender."></span></a><o:p></o:p></span></font></p>
</td>
<td width="470" style="width:352.5pt;border:none;padding:9.0pt .75pt .75pt .75pt">
<p class="MsoNormal" style="line-height:13.5pt"><font size="2" color="#41424e" face="Arial"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#41424E">Virus-free.
<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank">
<font color="#4453ea"><span style="color:#4453EA">www.avast.com</span></font></a>
</span></font><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><font size="2" face="Calibri"><span style="font-size:11.0pt"> <o:p></o:p></span></font></p>
</div>
</div>
</blockquote>
<p><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</blockquote>
<p><font size="2" face="Calibri"><span style="font-size:11.0pt"><o:p> </o:p></span></font></p>
</div>
</div>
</body>
</html>