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 20:05:27 CEST 2015
On Fri, Jun 19, 2015 at 06:24:27PM +0200, Thomas Drewermann wrote: >I forgot one tought in my first mail. >To be particular about the policy in my opinion guest networks >provided by PI assigment holders e.g. companies aren't legitimate use >either. >Because addresses are leased to users/devices which don't belong the >company holding the PI assignment. >That addresses could be treated as assignments to third parties as well. ISTR this discussion on this list before ;) I think the consensus was that single devices, temporarily becoming part of the End User's network, do not count as "assignment to third parties". It's a different story for a /64 assigned to a customer's VM infrastructure though - which is perhaps comparable to the Freifunk case... 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 ]