Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[AFRINIC-rpd] New Policy Proposal: Inter RIR IPv4 Address Transfers (AFPUB-2013-V4-001-DRAFT-01)

Owen DeLong owen at delong.com
Wed Jan 16 06:46:03 UTC 2013


Let me clarify... I'm not just talking about having addresses on interfaces and being able to ping. I'm talking about having IPv6 deployed to the point that if you add a node that cannot get an IPv6 address, it is not a second class citizen, at least within the organization.

Owen


Sent from my iPad

On Jan 15, 2013, at 8:32 PM, Maina Noah <mainanoa at gmail.com> wrote:

> Arturo, Owen and all,
> 
> I guess lets stick to each individual persons experience but IMHO the duration you guys are implying is still way to long and my argument was not based on deploying v6 on only the core but also on every other system that needs a v6 address. You have a point though on the issue of training which ofcourse tends to take time but on deployments it shouldn't be that long.
> 
> Cheers,
> 
> Maina Noah
> 
> 
> On 16 January 2013 03:56, Arturo Servin <aservin at lacnic.net> wrote:
>> Maina,
>> 
>> 	I normally do not post to policy list and less into other RIRs policy-lists, but my comment is technical.
>> 
>> 	Yes, a medium IPv6 deployment may take you more than 6 months. I can tell you by experience not just mine, but from other people to whom I interact. A large one may take you a year.
>> 
>> 	IPv6 deployment is not just configuring a few core routers, as Owen said there is planning, addressing, and training (unless you hire people that already knows this take time, a lot of time. And in the best case, you will have just a few experts but you would need to train technicians, system admins, help-desk, etc.) You also need procedures, testing, purchasing equipment, etc.
>> 
>> 	Believe me, if you think that you can deploy IPv6 in a medium enterprise (50-2500 nodes) or in a small/medium ISP/Datacenter in a month, you are, very, but very positive.
>> 
>> 
>> Cheers,
>> as
>> 
>> On 15 Jan 2013, at 17:42, Owen DeLong wrote:
>> 
>>> 
>>> On Jan 15, 2013, at 11:34 AM, Maina Noah <mainanoa at gmail.com> wrote:
>>> 
>>>> 
>>>> 
>>>> 
>>>> On 15 January 2013 21:58, Owen DeLong <owen at delong.com> wrote:
>>>>> 
>>>>> On Jan 15, 2013, at 10:21 AM, Seun Ojedeji <seun.ojedeji at gmail.com> wrote:
>>>>> 
>>>>>> On Jan 15, 2013 2:58 PM, "Andrew Alston" <alston.networks at gmail.com> wrote:
>>>>>> >
>>>>>> > Hi Maina,
>>>>>> >
>>>>>> >  
>>>>>> >
>>>>>> > I personally believe that the problem is two-fold.  Firstly, the community tends to resist change and the argument always surfaces, why implement something that isn’t going to generate revenue.  The fact is though that many of us have been saying for years and years that IPv6 is not about revenue generation, it’s about revenue retention.  When the day arrives that customers cannot access something elsewhere in the rest of the world because its gone IPv6 only
>>>>>> >
>>>>>> I don't get it Andrew you are making it look like it's either now or never ;-)  will v6 allocation end at this future your are painting here?
>>>>>> and an ISP cannot offer IPv6, at that point, the customer is going to walk and go somewhere that can give him full access to the Net, and the revenue from that customer is gone. 
>>>>>> >
>>>>> 
>>>>> It's not now or never, but if you wait for the customer to demand it, it's too late. Deploying IPv6 is not an instantaneous process. You can't get the request from the customer today and have IPv6 delivered to them in a stable, scalable manner in 30 days. You're looking at a process which could take as little as 6 months on a small dynamic network or as much as 3-5 years in a large-scale organization.
>>>>  
>>>> Owen from my experience deploying IPv6 for one of the ISP in East Africa, i think that is a bit over-exaggerated when you say 6 months. A typical ISP with for instance 10 POP's at minimum could deploy v6 across the core in a month or so ...6 months is way to long even if they didn't plan well it could take at-most 3 moons…We have mailing list like afnog etc where folks can exchange ideas hence make life easier in case one was stuck.
>>> 
>>> Across the core, sure. But what about provisioning systems, address management, monitoring, any internal software, etc.?
>>> 
>>> There's a lot more to deploying IPv6 to customers in a sustainable scalable manner than merely getting addresses on a few core routers.
>>> 
>>>> So guys don't be scared 3-5 Years is way to long unless if that large-scale organization in question has very lazy net-engineers !!!!!
>>> 
>>> How many large-scale organizations have you worked with on IPv6 deployment? I'm talking full deployment, not just the core routers… All the way to the edge and in a sustainable and scalable way. A way that IPv6 is a routine product, not an exception or one-off for a few customers.
>>> 
>>> Also, let's define the term large-scale… We're talking 20,000 employees (enterprise) or more than 1,000,000 customers (ISP).
>>> 
>>> Owen
>>> 
>>> _______________________________________________
>>> rpd mailing list
>>> rpd at afrinic.net
>>> https://lists.afrinic.net/mailman/listinfo.cgi/rpd
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20130115/9396017f/attachment.html>


More information about the RPD mailing list