This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 PI assignment policy
- Previous message (by thread): [address-policy-wg] IPv6 PI assignment policy
- Next message (by thread): [address-policy-wg] IPv6 PI assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Fri Jun 19 21:59:21 CEST 2015
Hi, > What if the freifunk communities formed an alliance and become a LIR as > a part of the alliance? It would lower the costs of becoming a LIR and > at the same time allow communities to get enough independent IPv6 > addreses that could be assigned to customers. One option is to get 8 freifunk communities together, start one LIR between them, get a /29 from RIPE NCC and then let each community use a /32 from that. I have a personal LIR that 'donated' a /32 to a community in such a way and it works fine. The deaggregation from /29 to /32 is not great, but not something that causes much trouble in the DFZ. Cheers, Sander
- Previous message (by thread): [address-policy-wg] IPv6 PI assignment policy
- Next message (by thread): [address-policy-wg] IPv6 PI assignment policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]