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] Use of the Reserved IP Pool
- Previous message (by thread): [address-policy-wg] Use of the Reserved IP Pool
- Next message (by thread): [address-policy-wg] Use of the Reserved IP Pool
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Wed Jul 2 11:35:44 CEST 2014
On 2 Jul 2014, at 10:10, Dpto. Datos Television Costa Blanca <datos at tvt-datos.es> wrote: > I know opening the door to this could make IPv6 deploy slower, but if one of the requirements to get another /22 (or other prefix) is to have 5 stars plus other ones to ensure the deploy and use of IPv6 it may help on IPv6 deployment. I am not sure what problem you are trying to solve. Or how changing address policy will solve that problem. You say half your customers don't have IPv6-enabled CPE. This does not seem to me to be a justification for ripping up the current address policy to burn through the remaining dregs of IPv4 and leave absolutely nothing for any newcomers in 5, 10 or 20 years from now. To be quite blunt, ISPs these days really must be shipping dual-stack CPE AND have the supporting IPv6 infrastructure in place: working v6 transport/routing; provisioning; DNS; addressing/subnetting plans; etc, etc.
- Previous message (by thread): [address-policy-wg] Use of the Reserved IP Pool
- Next message (by thread): [address-policy-wg] Use of the Reserved IP Pool
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]