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 TLD Anycast Allocation Policy
- Previous message (by thread): [address-policy-wg] Summary TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Summary TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Roesen
dr at cluenet.de
Tue Apr 5 14:53:13 CEST 2005
On Tue, Apr 05, 2005 at 02:49:24PM +0200, Iljitsch van Beijnum wrote: > >2. /32 vs. /48 V6 prefix - routability aspect > > There are incorrect documents published which suggest that filtering at > /32 is ok. After changing these documents and waiting some time this > should no longer be an issue. Agreed. We're still in early stages. > >3. /32 vs. /48 V6 prefix - address conservation aspect > > >There is no question that a /32 is quite a big block and that this > >sacrifice > >to "ensure" reachability from most network places is worth it. > > There is at least a question here, even if we agree on the answer. > > However, it's not simply whether it's worth it or not, it's a question > of doing the right thing. If we start changing allocation policies to > accommodate laziness on the part of router operators, where does it > end? Agreed too. Sorry for such "agreed!" mails without more content, but when trying to find consensus, also expressed agreement is necessary. :-) Regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0
- Previous message (by thread): [address-policy-wg] Summary TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Summary TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]