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 allocations for 6RD
- Previous message (by thread): [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
marc.neuckens at belgacom.be
marc.neuckens at belgacom.be
Thu Nov 26 23:23:06 CET 2009
I read in the paragraph 4 (IPv6 Policy Principles) of the IPv6 Address Allocation and Assignment Policy : --------------- 4.4. Consideration of IPv4 infrastructure Where an existing IPv4 service provider requests IPv6 space for eventual transition of existing services to IPv6, the number of present IPv4 customers may be used to justify a larger request than would be justified if based solely on the IPv6 infrastructure. ------------- I suppose this justifies the request, no ? I don't see any problem in allocating an ipv6 allocation bigger than /32 for ISP with millions of existing customers. Who knows how many subnets we will assign in 10, 20 years. A /32 is only 2^16 or 16 million /56 subnets or 65536 /48. I prefer this than allocate now a /32, in 2 years extend to a /30 and then to a /27 and then an other /27. (even if the other /32 in the /27 are not allocated to other LIR) It all depends on how future-proof the address plan is. What is used now for 6rd and transition can be reused in the LIR for extra customers / applications in 5 years. Marc Neuckens Belgacom **** DISCLAIMER **** http://www.belgacom.be/maildisclaimer
- Previous message (by thread): [address-policy-wg] IPv6 allocations for 6RD
- Next message (by thread): [address-policy-wg] IPv6 allocations for 6RD
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]