[address-policy-wg] ripe-587, Temporary Internet Number Assignment Policies

Hi Marcus,

I don't think any RIR is in a position to reserve space for a conference/event with thousands of participants bringing their own multiple devices and allowing public addresses for each one. Even many ISPs will not be able to do that!

With 464XLAT you don't really need that, and the effect "for the participant devices" is the same as having NAT or CGN, with the advantage that they will also get global IPv6 addresses (as many as they want for every device if they deliver /64 per host as per RFC8273).

In section 3.4 (IPv4 Pool Size Considerations) of https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-comparison/ (which has been already submitted to the IESG for publication), you can find a simple calculation that demonstrates that a /22 (IPv4) can server, for example, over 275.000 subscribers (devices in a conference), in the worst case.
 
Saludos,
Jordi
@jordipalet
 
 

El 7/3/22 12:32, "address-policy-wg en nombre de Marcus Stoegbauer" <address-policy-wg-bounces at ripe.net en nombre de marcus at grmpf.org> escribió:

    Apologies for the late reply, I'm just catching up with my mailing lists..

    On 27 Jan 2022, at 16:44, JORDI PALET MARTINEZ via address-policy-wg wrote:

    > I'm not convinced that we should "today", provide IPv4 temporary assignments, neither for conferences or experiments.
    >
    > A conference can perfectly survive today with a single IPv4 public address (or very few of them) from the ISP providing the link (even if running BGP), using 464XLAT, so the participants get dual-stack in the same way they are used to (private IPv4 addresses) and they also have global IPv6 addresses. This can be made with pure open source in a VM (if the provider doesn't have a NAT64, it can be also in the VM, in addition to the CLAT support, both using Jool, or other choices), etc. It is very well proven.

    A conference is not a very well defined term. I agree with your assessment for conferences like RIPE meetings, NOGs and so on.
    However, also events like Chaos Communication Congresses (https://events.ccc.de/congress/2019/wiki/index.php/Main_Page as an example) have the word conference in it. And those are events with >15,000 users, stretching over almost a week, where each participant is bringing multiple devices. Here you won't simply use one or even a handful of public IPv4 addresses for translation, but rather want a public IPv4 address per device. In short: I still see a need, also for shorter temporary assignments for conferences like this.

       Marcus-- 

    To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

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.