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 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Roesen
dr at cluenet.de
Wed Mar 2 11:29:06 CET 2005
On Wed, Mar 02, 2005 at 10:50:35AM +0100, Iljitsch van Beijnum wrote: > It's important to separate fundamental problems that aren't fixable, or > require unpleasant compromises to be fixed, from the incidental > problems that can be fixed in time and with education. The ones you > list all fall in the latter category, IMO. Doing more-specific multihoming makes ONLY sense when planning to filter them at some point in time. Unfortunately at exactly this point, this scheme fails. This cannot be fixed in time and with education, this is a very fundamental problem of this approach. Regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]