Introducing AFRINIC Policy discussion to the newcomers

1. Presented by: Ernest
6/18/19 https://2019.internetsummit.africa 1
Policy Development Update

2. • Internet now a basic right, part & parcel of our work and personal
space.
• At the heart of the internet’s operation are IP addresses (the engine)
• AFRINIC (+ other RIRs) manage the distribution of these IP addresses
to operators, ISPs, end-users in their communities
• Distribution is governed by policies, developed by these communities
in a transparent, all inclusive bottom-up process.
• AFRINIC (+ all RIRs) act as facilitator, implementer.
• All implemented proposals enter the ‘Policy Manual’ (CPM)
• Participation platforms: Such meetings, rpd list.
6/18/19 2
we are here because..
https://2019.internetsummit.africa

3. 6/18/19 3
The PDP
https://2019.internetsummit.africa

4. AFRINIC Policy Development Process – bis
https://www.afrinic.net/policy/proposals/2017-gen-002-d5#proposal
This proposal is a major revision of the current Policy Development
Process. Major highlights include:
• A clearer mechanism for appeals and disputes.
• Introduction of distinct phases in the policy proposal life cycle.
• More transparency around consensus-gauging.
under discussion (1/10)
6/18/19 https://2019.internetsummit.africa 4

5. Abuse Contact Policy Update
https://afrinic.net/policy/2018-gen-001-d2
Updates CPM 8.0 (Abuse Contact Information) with the following key
amendments:
• Introduction of a mandatory “abuse-c” attribute into inetnum,
inet6num and aut-num whois database objects for resources directly
issued by AFRINIC. The value of this attribute is an “abuse-mailbox”,
which must be a valid e-mail address.
• A mechanism is proposed to validate the “abuse-mailbox” and
report/escalate invalid or those that are unresponsive.
6/18/19 5
under discussion (2/10)
https://2019.internetsummit.africa

6. Provisions for Resource Hijacking
https://www.afrinic.net/policy/proposals/provisions-for-resource-
hijacking
The proposal provides a framework for recognizing that IP address
hijacks are a policy violation within the AFRINIC service region. A
method to identify and report hijacks is proposed and a pool of experts
chosen from the community is instituted to investigate each reported
case.
6/18/19 6
under discussion (3/10)
https://2019.internetsummit.africa

7. IPv4 Inter-RIR Legacy Resource Transfers
https://www.afrinic.net/policy/proposals/2019-v4-001-d1#proposal
• Establishes a mechanism to allow transfers of legacy IPv4 space
to/from other regions. The intent is to align AFRINIC with an IPv4
address market that already exists for which AFRICA is not currently
part.
• The author fronted two Inter-RIR proposals with hope to withdraw
one if the other passes through.
6/18/19 7
under discussion (4/10)
https://2019.internetsummit.africa

8. IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)
https://www.afrinic.net/policy/proposals/2019-v4-002-d1
• Allows establishing a mechanism to allow transfers of IPv4 space
to/from other regions. The intent is to align AFRINIC with an IPv4
address market that already exists for which AFRICA is not currently
part.
• The author fronted two Inter-RIR proposals with hope to withdraw
one if the other passes through.
6/18/19 8
under discussion (5/10)
https://2019.internetsummit.africa

9. IPv6 PI Clarification
https://www.afrinic.net/policy/proposals/2019-v6-001-d2#proposal
• Amends original policy proposal “IPv6 PI Update” (AFPUB-2018-V6-004)
currently CPM 6.8.2(v), which requires that IPv6 PI space should be
announced within 12 months of getting it, and should not be
disaggregated.
• This proposal does not make it mandatory to announce the space, since
there is no RFC1918 equivalent for IPv4, and cases like IXP peering LAN
space doesn’t necessarily have to be announced. If announced however,
the condition to disaggregate it is still in place.
6/18/19 9
under discussion (6/10)
https://2019.internetsummit.africa

10. SL Update
https://afrinic.net/policy/proposals/2018-v4-001
• Proposes an update to CPM 5.4.7.2 which removes the Board’s power
to replenish the (exhaustion) pool with any IPv4 space available at the
time (such as the /12 reserve in 5.4.7.1). The proposal also stipulates
that the same /12, if still unused by the time phase 2 space is
exhausted, be automatically
6/18/19 10
under discussion (7/10)
https://2019.internetsummit.africa

11. Multihoming not required for ASN
https://www.afrinic.net/policy/proposals/2019-asn-001-d2
Modifies CPM 7.4 by removing 7.4.2, a clause requiring requestors of ASNs
to be multihomed (or demonstrate plan thereof). Instead, the proposal sets
the following criteria:
• A unique routing policy or
• Interconnection with one or more other ASNs which requires a globally
unique ASN.
• An organization will also be eligible if it can demonstrate that it will meet
any of the above criteria upon receiving an ASN (or within the following six
months).
6/18/19 11
under discussion (8/10)
https://2019.internetsummit.africa

12. Internet Number Resources Review by AFRINIC
https://www.afrinic.net/policy/proposals/2016-gen-001-d8
The proposal introduces a mechanism for AFRINIC to conduct reviews
(or audits) for IPv4 number resources issued to members, and
recommends reclamation of resources that are found to be in breach
or not in compliance.
6/18/19 12
under discussion (9/10)
https://2019.internetsummit.africa

13. Clarification on temporary resource usage
https://afrinic.net/policy/2018-gen-004-d1#proposal
• Introduces restrictions to the size of IPv4 space requests for temporary use
(such as conferences and meetings) – capped at /22 maximum.
• Encourages the use of IPv6 on the premise that it is now mature enough to
be deployed for this kind of use whereby the requesting entity preferably
uses IPv6-only on their networks while deploying IPv4 at the edge of the
network using an IPv6 transition mechanism.
• Amends the title of CPM 9.0 to “Temporary Resource Assignments”
(deleted the “allocations” wording) to reflect that these are PI assignments.
6/18/19 13
under discussion (10/10)
https://2019.internetsummit.africa

14. Clarification on IPv6 Sub-Assignments
https://www.afrinic.net/policy/2018-v6-002-d3
• Adds a requirement to CPM 6.8 stipulating that IPv6 PI space cannot
be issued to third parties, and must only be used in the network
infrastructure of the member issued the space.
• Status: Implementation imminent - Pending confirmation of internal
documentation and procedure update.
6/18/19 14
under implementation (1/2)
https://2019.internetsummit.africa

15. IPv6 PI Update
https://www.afrinic.net/policy/2018-v6-004-d1#proposal
On pause - the new proposal “IPv6 PI Clarification” removes the
mandatory requirement to announce the space, and makes this
optional. Waiting for decision on this proposal before proceeding with
automation work below:
• PI space to be announced within 12 months of receiving it, else it
should be returned to pool
• PI space must be announced as single aggregate.
6/18/19 15
under implementation (2/2)
https://2019.internetsummit.africa

16. Lame Delegations in the AFRINIC Reverse DNS
Proposed: 15.03.2017
Last Call: 01.12.2017
Ratified: 21.03.2018
Implemented: August 2018
CPM Article: 10.7
The requirement to delete non-compliant nserver attributes and/or
objects whose referenced nserver values are lame is still not yet
implemented, as the issue of false positives is still under investigation.
6/18/19 16
recently implemented
https://2019.internetsummit.africa

17. Participate, make your voice heard
- Subscribe to rpd@afrinic.net
- Attend the bi-annual public policy meetings (in-person, remotely)
- Propose policy that you deem relevant to address your (and
community’s) needs.
- Speak up and be part of the action during face to face and mailing list
discussions.
6/18/19 17
Be part..
https://2019.internetsummit.africa

18. 6/18/19 https://2019.internetsummit.africa 18
Thank you
=========
Questions?