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: #gamma IPv6 Initial Allocation Criteria
- Previous message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 Initial Allocation Criteria
- Next message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 Initial Allocation Criteria
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Tue Apr 5 14:28:43 CEST 2005
On 4-apr-05, at 14:44, Gert Doering wrote: >> I guess that it may make sense to define a time frame here... i mean, >> an organization planning to provide IPv6 connectivity in 20 years >> would >> qualify here? > Yes. But how much harm can it do? This organization would eat up > about > 1/4294967296 of the address space, and pay a yearly fee to RIPE to > be permitted to keep it. Sounds like a fair deal to me. So where do I send the bill for the fee to take up space in my routing table? No deal. > If the address space is allocated and doesn't even end up in the > routing > tables, even better. That's what's site local ng is for.
- Previous message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 Initial Allocation Criteria
- Next message (by thread): [address-policy-wg] Policy proposal: #gamma IPv6 Initial Allocation Criteria
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]