Title: Re: [GLOBAL-V6] PI space under IPv6Hi Uchenna,
No, I don’t think translation should be used for this. Translation always break things when used for everything, that’s why IETF deprecated NAT-PT.
The main problem of the routing tables is not IPv6 and will not be in a short time. The real issue is already the deaggregation on IPv4. I don’t think having PI in all the regions will change the trend in a significant way, and this has been evident across talks from several people in RIR meetings, IETF, etc.
We need better ways to do routing, and several groups, including IETF are already working on that. Meanwhile, I think all the regions should support IPv6 PI so they aren’t in disadvantage versus ARIN and APNIC service regions (which are the ones now that have IPv6 PI policies).
Regards,
Jordi
De: Uchenna N Ibekwe <uchenna.ibekwe@verizonbusiness.com> Responder a: <global-v6-bounces@lists.apnic.net> Fecha: Tue, 16 Jan 2007 19:29:16 -0500 Para: <global-v6@lists.apnic.net> Asunto: [GLOBAL-V6] PI space under IPv6
All,
There has much discussion on how to implement PI space in IPv6. I would like present an administrative solution to PI space for IPv6.
Please indulge me if this seems simplistic, we could reserve the IP4 space as largely PI.
I will explain;
-Since we already have most of the PI space reserved under IPv4, it would be easier to continue to use the allocated IPv4 space as PI under the translated IPv6 numbering scheme. -Routing tables as a result will be kept within a manageable size. -No renumbering will be required by end-users, enhancing migration from IPv4 to IPv6. -Multi-homed users or entities will not cause delays for ISPs migrating to IPv6.
This is something to think about, just an idea.
**********************************************
The IPv6 Portal: http://www.ipv6tf.org
Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org
This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
