Search RPD Archives
[AfriNIC-rpd] Pushing IPv6
gift at itibots.com
gift at itibots.com
Fri Nov 25 10:08:07 UTC 2011
+ I think IPV6 implementation is a business decision to address continuity
and sustainability issues. Like any tecknological upgrade people catch up
at the diffrent satages for different reasons. The KRA where Afrinic
should not be found wanting is educationxxxx,awareness+++. If the
legislation is done by the regulators then well and good. All we can do is
lobby. How do we evaluate the effectiveness of our lobby and awareness
campains other than through IPV6 uptake, bearing in mind there is always
an incubation period for such processes.
> I agree with Owen, let's not give out v6 just for the sake of it.
> There's a constituency that I think requires urgent attention, government.
> With many governments rolling out e-government services, my thoughts are
> that AfriNIC should come up with programs that target governments, one of
> the biggest (potential) user of IP resources. This program should _mainly
> target policy makers.
> Vincent Ngundi
> Twitter: @VincentNgundi
> On Thu, Nov 24, 2011 at 11:19 PM, Owen DeLong <owen at delong.com> wrote:
>> On Nov 24, 2011, at 8:37 AM, Mark Elkins wrote:
>> > After listening at AfriNIC-15 and what happens in LACNIC - would it
>> > sense to propose a policy that...
>> > Purpose - to promote IPv6
>> > In order for a resource member to get any new IPv4 resource - and they
>> > have no IPv6 resource - they must apply for an IPv6 resource as well.
>> Personally I don't think so. All it does is push people to request
>> which they can then leave on the shelf. We want to drive actual IPv6
>> deployment, not merely address consumption.
>> In fact, I would say that driving address consumption without deployment
>> is a net lose for the community.
>> > If the resource member asks for any new IPv4 resource - and they have
>> > any IPv6 resources older than four months of age - then the resource
>> > member must show that any of their existing IPv6 resources are in use
>> > either visible in the Routing Tables or the IPv6 resource must be
>> > provably in use (reachable via another Member), which would exclude
>> > anything in a testing environment.
>> This takes a step towards pushing deployment, but, in fact, it's pretty
>> easy to anchor a route at one of your edges and not actually deploy
>> anything behind it.
>> I think it's better to work on more meaningful deployment through
>> and encouragement rather than through policy. Policy initiatives tend to
>> drive resistance and people tend to do the bare minimum necessary to
>> work through or around the policy rather than look for ways to go beyond
>> what the policy requires.
>> Better would be to provide hall-of-fame style incentives for people to
>> go as far as they can in IPv6 deployment. Something like the RIPEness
>> program at RIPE NCC.
>> rpd mailing list
>> rpd at afrinic.net
> rpd mailing list
> rpd at afrinic.net
More information about the RPD