Re: [sig-policy] [Sig-policy] prop-073: Automaticallocation/assignmentof
Hash: SHA1
- From past experiences, I would have to agree with Yamanishi-san.
When you get something that you really didn't ask for or
are not ready for, it tends to be mostly forgotten, unmanaged, lost...etc
Regards,
Seiichi
myamanis at bb.softbank dot co dot jp wrote:
> Dear Andy and All.
>
> I totally agree that there are various barriers for IPv6 deployment including lack of expertise.
> However, the point which I cannot figure out well is whether there is the APNIC application
> barrier to receiving IPv6 address space as described in prop-073 or not.
>
>> In the document there's also a section on the biggest hurdles to IPv6
>> deployment. Availability of IPv6 address space isn't cited there but
>> "Lack of IPv6 expertise" is the second highest hurdle listed. I think
>> it's pretty hard to gain expertise without training and the
>> opportunity to experiment with available IPv6 address space.
>
> Certainly, "lack of IPv6 expertise" is big hurdle for IPv6 deployment and we should make
> more opportunity of training. But, is it actually increased by "automatic IPv6 allocation/assignment"?
>
> Best Rgs,
> Masato Yamanishi
>
> ________________________________
>
> From: sig-policy-bounces at lists dot apnic dot net 代理 Andy Linton
> Sent: 2009/08/09 (日) 8:38
> To: sig-policy
> Subject: Re: [sig-policy] [Sig-policy] prop-073: Automaticallocation/assignmentof IPv6
>
>
>
>
> On 7/08/2009, at 23:21 , <myamanis at bb.softbank dot co dot jp> <myamanis at bb.softbank dot co dot jp
> > wrote:
>
>> Dear Terry and Andy,
>>
>> Sorry for very delayed comment.
>>
>>> As a community, we have done much to promote the adoption of
>>> IPv6. This
>>> policy proposal extends the efforts by removing the APNIC application
>>> barrier to receiving IPv6 address space.
>> At least for me, it is not so clear whether there is such barrier or
>> not.
>
> In May this year the NRO produced a document "NRO Response to TSB
> ‘Questionnaire on IPv6 Address Allocation and Encouraging the
> Deployment of IPv6’"- available at http://nro.org/news/nro-response-to-itu.html
>
> This document has some figures on IPv6 allocation across the globe and
> I've been looking at the figures for our region. One thing that is
> clear to me is that address allocation to economies in South East Asia
> is much higher than in the rest of the region. That's what we'd expect
> - Japan, Korea, Taiwan and China have deployed IPv6 with enthusiasm.
>
> Australia also has plenty of IPv6 address space allocated and New
> Zealand to a lesser degree.
>
> But looking at the tables in the document there are plenty of
> economies that haven't done much or anything about this.
>
> So I think that your view of IPv6 may depend on where you live and work.
>
> In the document there's also a section on the biggest hurdles to IPv6
> deployment. Availability of IPv6 address space isn't cited there but
> "Lack of IPv6 expertise" is the second highest hurdle listed. I think
> it's pretty hard to gain expertise without training and the
> opportunity to experiment with available IPv6 address space.
>
>>> 7. Effect on NIRs
>>> ------------------
>>>
>>> The impact on the NIR would depend if the NIR adopts this proposal
>>> for
>>> their constituency.
>> I think, we need to consider the impact when this policy will be
>> also implemented to NIRs
>> since more IPv6 address will be comsumed.
>> Isn't there any comment or information from NIR people?
>
> Our proposal doesn't try to impose this solution on the NIRs but we
> recognise that it may have some influence on their policies. I'd also
> like to hear from anyone who has a view on this.
>
>
> * sig-policy: APNIC SIG on resource management policy *
> _______________________________________________
> sig-policy mailing list
> sig-policy at lists dot apnic dot net
> http://mailman.apnic.net/mailman/listinfo/sig-policy
>
>
> * sig-policy: APNIC SIG on resource management policy *
> _______________________________________________
> sig-policy mailing list
> sig-policy at lists dot apnic dot net
> http://mailman.apnic.net/mailman/listinfo/sig-policy
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
iD4DBQFKf3ChcrhTYfxyMkIRAsfSAJjy2HDJMSHonlv2UNFB84vxFqphAJ4vUHIU
HzD04Jr2NEt6smX2qGxRgw==
=P/uT
-----END PGP SIGNATURE-----