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] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Previous message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Roesen
dr at cluenet.de
Thu Mar 24 17:27:42 CET 2005
On Thu, Mar 24, 2005 at 03:44:42PM +0000, Jon Lawrence wrote: > On Thursday 24 March 2005 14:44, Daniel Roesen wrote: > > On Thu, Mar 24, 2005 at 02:55:24PM +0100, Iljitsch van Beijnum wrote: > > > So how exactly do I build a prefix length filter that only applies to > > > allocations and not assignments? > > > > This is why people propose reserving a range for PI assignments, so > > that this range can have different filtering. No rocket science. > > > But Daniel, there's no such thing as v6 PI :) That's what THEY want to make you believe. :-)= > As I read it, they're talking about reserving a block for what would > effectively be micro-allocations no PI. And what's the difference please? Especially since those aren't allocations (you can't assign more-specifics to others) but assignments? Don't play with words. It's IPv6 PI for whoever-is-deemed-special. Regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0
- Previous message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
- Next message (by thread): [address-policy-wg] Policy proposal: #alpha: TLD Anycast Allocation Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]