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 ]
Sascha Luck [ml]
apwg at c4inet.net
Sun Jun 21 19:58:34 CEST 2015
On Fri, Jun 19, 2015 at 09:52:10PM +0200, Ond?ej Caletka wrote: >I don't think it's a good idea. There is a reason why the usage of PI >addresses is restricted. I think your proposal would lead to a situation >where everybody uses PI addresses just-in-case even if they don't really >need them, thus flodding the global routing table. You might as well get used to the idea. If seen as a loose federation of independent "network clouds" (as I understand the Freifunk idea, correct me if I'm wrong), this offers a first glimpse into how things will be if and when the "Internet of Things" becomes something more than vapourware. We might as well start thinking about how to solve the coming resource management issues. For the Freifunk people here, could you provide some detail on how this is solved for IPv4 at the moment? rgds, Sascha Luck
- 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 ]