<html 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:"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;}
@font-face
{font-family:"Times New Roman \(Cuerpo en alfa";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EstiloCorreo18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EstiloCorreo19
{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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Somehow, I agree with Andrew.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/"><span lang=EN-US style='color:purple'>https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/</span></a><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>is already in the Editor Queue, so it is a matter of a few days or weeks that it will have an RFC number.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/"><span lang=EN-US style='color:purple'>https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/</span></a><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Is now in IETF v6ops Working Group Last Call, since last week. ***Nobody**** said this is good or bad (even if it is a Working Group document and that means that previously the WG adopted it) … same problem as we have here with policy proposals. It may even happen that because nobody goes to the v6ops mailing list to say “it is a good document” or “I’m missing this or that” or “correct this because it is wrong”, the document just dies. Unfortunate, but is the bad thing of “consensus” that not everybody speaks up, even if they may agree with something.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>So, taking the opportunity … if you believe that </span><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/"><span lang=EN-US style='color:purple'>https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/</span></a><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Provides a good guidance for deploying NAT64/464XLAT, please, register at </span><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/"><span lang=EN-US style='color:purple'>https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/</span></a><span lang=EN-US>, and say that you support that document.<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>Here is the relevant email:<o:p></o:p></span></p><p class=MsoNormal><a href="https://mailarchive.ietf.org/arch/msg/v6ops/h-c-v936g56uWcaB3dndFnouPt8"><span lang=EN-US>https://mailarchive.ietf.org/arch/msg/v6ops/h-c-v936g56uWcaB3dndFnouPt8</span></a><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;color:black'><br>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:10.5pt;color:black;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:10.5pt;color:black;mso-fareast-language:EN-US'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 15/4/19 17:40, "Andrew Alston" <<a href="mailto:Andrew.Alston@liquidtelecom.com">Andrew.Alston@liquidtelecom.com</a>> escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>Willy,</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>Heh – at the speed the IETF works – if you wait for formal RFC’s these days – you’ll be waiting a hell of a long time.</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>TACACS – which has been around for 20+ years – is a draft</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>Segment routing – which is being more and more used – is a draft</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>Segment routing BGP extensions – is a draft </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>It’s a long long list of very much production technologies </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>The draft tag – doesn’t mean much these days</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>Andrew</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-fareast-language:EN-US'> </span><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 style='margin-left:35.4pt'><b><span lang=EN-US>From:</span></b><span lang=EN-US> Willy Manga <mangawilly@gmail.com> <br><b>Sent:</b> Sunday, 14 April 2019 23:51<br><b>To:</b> rpd@afrinic.net<br><b>Subject:</b> Re: [rpd] Proposal: Clarification on temporary resource usage</span><o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'>Hi Jordi,<br><br>On 21/12/2018 18:50, JORDI PALET MARTINEZ via RPD wrote:<br>> [...]<br>> You may want to add the following references (the first one will become, hopefully soon, an RFC):<br>> - <a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/">https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/</a><br>> - <a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/">https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/</a><br><br>I'd love to include them but right now they are still in the draft<br>section. It is better to mention documents elected as RFC in the CPM in<br>my humble opinion.<br><br>If they get approval before the end of the discussion on this proposal,<br>they will surely be included.<br><br>-- <br>Willy Manga<br>@ongolaboy<br><a href="https://ongola.blogspot.com/">https://ongola.blogspot.com/</a><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'>_______________________________________________ RPD mailing list RPD@afrinic.net https://lists.afrinic.net/mailman/listinfo/rpd <o:p></o:p></p></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</body></html>