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 assignment for the RIPE meetingnetwork
- Previous message (by thread): [address-policy-wg] IPv6 assignment for the RIPE meetingnetwork
- Next message (by thread): [address-policy-wg] IPv6 assignment for the RIPE meetingnetwork
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
michael.dillon at bt.com
michael.dillon at bt.com
Tue Dec 2 21:33:27 CET 2008
> I can only second Niels here. While organizing conferences > and events with network infrastructure myself, I can tell > that it is a hassle to re-arrange temporary PI every time... > so I do see the incentive. But why should the NCC be a > special case and no one else? I agree that it would be fairer to change the policy so that any conference organizer can apply for a PI IPv6 address block. They fill the role of a network operator for the attendees of a conference and this should be sufficient justification. IPv6 address space is NOT in short supply and we should not treat it as a scarce resource at this time. --Michael Dillon
- Previous message (by thread): [address-policy-wg] IPv6 assignment for the RIPE meetingnetwork
- Next message (by thread): [address-policy-wg] IPv6 assignment for the RIPE meetingnetwork
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]