[rpd] New Proposal: Pv6 PI Clarification

Tue May 7 18:06:56 UTC 2019

> On Apr 11, 2019, at 5:10 AM, JORDI PALET MARTINEZ via RPD <rpd at afrinic.net> wrote:
> 
> Hi Jako,
> 
> I understand that it is easy to believe that ULA is equivalent to RFC1918, but is not.
> 
> Furthermore, with IPv4 private addresses, you can use a standard protocol called NAT, which is an evil. We want to avoid repeating IPv4 mistakes, right?
> 
> In IPv6 you don't have a STANDARD protocol for an equivalent functionality as NAT.
> 
> If you use ULA for a network that you believe is disconnected for "ever" from Internet, and tomorrow you need to connect it, you need to renumber. There is no need for that, because in IPv6 we don't have a scarcity problem (and will not have in several hundred years - so most probably we will replace the protocol with something else, but not because address exhaustion), so it doesn't make sense to be so restrictive.

While I support the use of GUA and think ULA is a useless waste of a /8, I will point out that you do not need to renumber.

You need to add GUA addresses to those hosts that need to communicate with the internet. While that may sound nit picky, it’s a vastly different scope of work in many such situations, adding GUA to hosts that need to communicate being significantly easier than a full fledged renumbering exercise.

Owen

> 
> Regards,
> Jordi
> 
> 
> 
> El 11/4/19 13:49, "Jaco Kroon" <jaco at uls.co.za <mailto:jaco at uls.co.za>> escribió:
> 
>    Hi,
> 
>    Use of ULA compared to RFC1918 addresses?
> 
>    Not objecting.  Making IPv6 more freely available might just help with 
>    uptake, which we really need.
> 
>    Kind Regards,
>    Jaco
> 
> 
>    On 2019/04/11 13:13, JORDI PALET MARTINEZ via RPD wrote:
>> Hi all,
>> 
>> I think the problem statement is very clear and the solution as well, but as usual, I'm happy to clarify and work out if anyone find any issues.
>> 
>> Thanks!
>> 
>> Regards,
>> Jordi
>> 
>> 
>> 
>> El 11/4/19 13:03, "Ernest Byaruhanga" <ernest at afrinic.net> escribió:
>> 
>>     A new proposal has been received as follows:
>> 
>>     IPv6 PI Clarification:
>>     https://afrinic.net/policy/2019-v6-d1#proposal
>> 
>>     It removes conditions around the need to announce IPv6 PI space within 12 months of getting it, as required in CPM6.8.2
>> 
>> 
>>     *Plain text version below* :
>> 
>> 
>>     1.0 Summary of the problem being addressed by this proposal
>> 
>>     By means of policy proposal “IPv6 PI Update” (AFPUB-2018-V6-004), the IPv6 Provider Independent (PI) space policy that provides IPv6 space for end-sites was revised/updated.
>>     This revision however overlooked a sentence in the previous section 6.8.2.v, which read:
>>     “The 'end-site' must show a plan to use and announce the IPv6 provider independent address space within twelve (12) months. After that period, if not announced, the assigned IPv6 PI address space should be reclaimed and returned to the free pool by AFRINIC”.
>>     This text was retained under 6.8.2.iv.
>>     Of course, this doesn’t make sense because there are several possible cases, which are in the scope of this policy, that will not announce their IPv6 PI address space, such as:
>>     IXP’s LAN peering space.
>>     In IPv6 there is no private address space equivalent to the IPv4 one as per RFC1918, so if an organization needs IPv6 space for numbering a network or a set of them, even if those aren’t connected today to the Internet, the RIR should be able to provide that space.
>> 
>>     2.0 Summary of how this proposal addresses the problem
>> 
>>     Simple rewording of the text to allow those cases that don’t need to announce their IPv6 PI space.
>> 
>>     3.0 Proposal
>> 
>>     .....................................
>>     Proposed (New) CPM content:
>> 
>>     6.8.2 Assignment Criteria
>>     Assignment target - End-sites which provide services for a single administrative organisations' network, regardless of their size.
>>     Assignment criteria:
>>     i. The end-site must not be an LIR
>>     ii. The end-site must become an AFRINIC End User Member and pay the normal AFRINIC fee for its membership category
>>     iii. The end-site must justify the need for the IPv6 PI address space.
>>     iv. The end-site must show a plan to use the IPv6 provider independent address space within twelve (12) months.
>>     v. The IPv6 provider independent address space, if announced by the end-site should not be disaggregated.
>>     .....................................
>> 
>>     Current CPM content (to be replaced by the proposed text above)
>> 
>>     6.8.2 Assignment Criteria
>>     Assignment target - End-sites which provide Public Internet services for a single administrative organisations' network, regardless of their size.
>>     Assignment criteria:
>>     i. The end-site must not be an LIR
>>     ii. The end-site must become an AFRINIC End User Member and pay the normal AFRINIC fee for its membership category
>>     iii. The end-site must justify the need for the IPv6 PI address space.
>>     iv. The end-site must show a plan to use the IPv6 provider independent address space within twelve (12) months. After that period, if not announced, the assigned IPv6 PI address space should be reclaimed and returned to the free pool by AFRINIC.
>>     v. The IPv6 provider independent address space to be announced by the end-site should not be disaggregated.
>>     .....................................
>> 
>> 
>>     4. References
>> 
>>     Other RIRs have already accommodated this requirement in their policies:
>>     - APNIC: 10.1.4. Provider Independent IPv6 assignment
>>     https://www.apnic.net/community/policy/resources#Part%203:%20IPv6%20Policy
>>     - ARIN: 6.5.8.1. Initial Assignment Criteria
>>     https://www.arin.net/participate/policy/nrpm/#6-5-8-direct-assignments-from-arin-to-end-user-organizations
>>     - LACNIC: 4.5.4.2 Direct assignment of portable IPv6 addresses to End sites not having portable IPv4 addresses previously assigned by LACNIC
>>     https://www.lacnic.net/684/2/lacnic/4-ipv6-address-allocation-and-assignment-policies
>>     - RIPE: IPv6 Provider Independent (PI) Assignments
>>     https://www.ripe.net/publications/docs/ripe-707#IPv6_PI_Assignments
>> 
>> 
>>     --
>> 
>>     (Sent on co-chairs behalf)
>> 
>> 
>> 
>> 
>> 
>> 
>> **********************************************
>> IPv4 is over
>> Are you ready for the new Internet ?
>> http://www.theipv6company.com
>> The IPv6 Company
>> 
>> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
>> 
>> 
>> 
>> 
>> _______________________________________________
>> RPD mailing list
>> RPD at afrinic.net
>> https://lists.afrinic.net/mailman/listinfo/rpd
> 
> 
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com <http://www.theipv6company.com/>
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> 
> 
> 
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net <mailto:RPD at afrinic.net>
> https://lists.afrinic.net/mailman/listinfo/rpd <https://lists.afrinic.net/mailman/listinfo/rpd>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20190507/9cc896fd/attachment-0001.html>