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/[email protected]/
[address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael.Dillon at radianz.com
Michael.Dillon at radianz.com
Tue Jun 22 11:06:41 CEST 2004
> Besides, there is no benefit to this rule as far as I can see. IPv6 space is > not a scarce resource. IPv4 is, yet is is easy enough to get. It should not be any more difficult to get an IPv6 allocation than it is to get an IPv4 allocation. Therefore, any ISP/LIR who already has an IPv4 allocation should be able to get their first IPv6 /32 simply by asking for it. In fact, you could argue that the RIRs should just allocate an IPv6 block to every ISP/LIR right now and send them out in the next email. --Michael Dillon
- Previous message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
- Next message (by thread): [address-policy-wg] IPv6 Policy Clarification - Initial allocation criteria "d)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]