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/[email protected]/
[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
Wed Dec 3 16:58:13 CET 2008
> Which leaves the problem of "an entity assigning to itself, > and doing a contract with itself" - which can be seen as a > problem with neutrality. We aren't lawyers. Why are you asking us to solve legal problems. Any lawyer will tell you that this is simple. Incorporate an entity separate from the NCC that will organize meetings. It can have the same board of directors as the NCC, or some other arrangement if you wish. This organization can then sign contracts with the RIPE NCC. The RIPE NCC no longer has to worry about RIPE meetings because RIPE now deals with a separate organization to hold the meetings. --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 ]