<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Is not for the peering (it is not needed even for IXPs, we can use IPv6-only), is for the NAT64.<div><br id="lineBreakAtBeginningOfMessage"><div>
<div>Saludos,<br>Jordi<br><br>@jordipalet<br><br></div>
</div>
<div><br><blockquote type="cite"><div>El 15 oct 2025, a las 0:59, Owen DeLong <owen@delong.com> escribió:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Oct 14, 2025, at 04:38, Noah <noah@neo.co.tz> wrote:</div><br class="Apple-interchange-newline"><div><div dir="auto"><div dir="auto"><br></div><div data-smartmail="gmail_signature" dir="auto"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b><br></b></div></div></div></div></div><br><div class="gmail_quote gmail_quote_container" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, 14 Oct 2025, 1:46 pm jordi.palet--- via RPD, <<a href="mailto:rpd@afrinic.net">rpd@afrinic.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-break:after-white-space"><br><div>In both cases you need “some” IPv4 addresses, and because you can’t route less than /24, most of the time, you will use a /24. </div></div></blockquote></div><div dir="auto"><br></div><div dir="auto">This is a very important point. At bare minimum, that is the block folks want to see in the DFZ.</div></div></div></blockquote><div><br></div>Fine, let’s reserve a single /24 for each of the governments that doesn’t currently have one and move on. Keeping a /12 is insane.</div><div><br></div><div><blockquote type="cite"><div><div dir="auto"><div class="gmail_quote gmail_quote_container" dir="auto"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-break:after-white-space"><div>If you have multiple PoPs for your BGP upstreams, then you may need multiple /24s.</div></div></blockquote></div><div dir="auto"><br></div><div dir="auto">That is why we settled for /22 in the softlanding policy.</div></div></div></blockquote><div><br></div>THere’s no need for IPv4 to interface with BGP upstreams… IPv4 routing across IPv6 BGP sessions works perfectly well and is not difficult to configure on Juniper, Cisco, FRR, Arista. Other platforms are likely similarly easy to configure, I just haven’t played with them for this purpose. </div><div><br></div><div>IPv4 Link Local peering is also a perfectly viable solution.</div><div><br></div><div>Owen</div><div><br></div><br></div></div></blockquote></div><br></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>