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] Summary of the PI Task Force's recent discussions
- Previous message (by thread): [address-policy-wg] Summary of the PI Task Force's recent discussions
- Next message (by thread): [address-policy-wg] Summary of the PI Task Force's recent discussions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Mon Aug 11 11:43:07 CEST 2003
On Mon, Aug 11, 2003 at 11:36:54AM +0200, Gert Doering <gert at Space.Net> wrote a message of 29 lines which said: > That's an operational problem, not a technical one. Policy is only about operational problems (filtering by operators, for instance, otherwise we would just use a /29 - more than enough for the nameserver and its close friends - and announce it with BGP). > If IANA/ICANN isn't working, give them a good beating, but please > don't break policy to cover for human deficiencies. It is completely unrealistic. Do you really expect the European ccTLD to be able to change Uncle Sam's policies and practices in the next few years? <troll>Change the policy to disallow any new IPv4 allocation and assignment. After all, IPv6 works, technically speaking, so it is "just an operational problem" now, do not create convoluted policies because of IPv4 addresses scarcity.</troll>
- Previous message (by thread): [address-policy-wg] Summary of the PI Task Force's recent discussions
- Next message (by thread): [address-policy-wg] Summary of the PI Task Force's recent discussions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]