Transcript Slide 1

AfriNIC Transition Plan
Ernest Byaruhanga
I-week
Johannesburg
© - AfriNIC 7/17/2015
September 9th 2004
Why a transition plan?

Africa is served by 3 RIRs
There is a need for harmonization
 consistency..


LIRs and stakeholders and
community need to be updated
with the transition’s:
clear milestones
 action plans

7/17/2015
© AfriNIC 2004
2
Transition plan

Transition is organized in 4 (Business and
Technical) Phases:

Phase 0: Preparation (Ended)
Phase 1: Co-evaluation & AfriNIC
Database/Whois setup (Started)
Phase 2: Uniform policy and Evaluation process
Phase 3: Provisional Recognition & Independent
evaluation with Audit by RIRs.
Phase 4: Final approval




7/17/2015
© AfriNIC 2004
3
Phase 0 (Done)

Training and staffing: AfriNIC has hired staff that
have been trained at RIPE NCC in RIR operations

Physical Office setup



Infrastructure & Technical Transition design




7/17/2015
South Africa
Mauritius
Network architecture design
Internet transit Identification
Servers and Network equipments acquisition
Tools and software identification
© AfriNIC 2004
4
Phase 0 cont (Done)

Policies documents
Policies
 Registration Service Agreements
 Supporting documents


Budget and financial plan
Start of Phase 1
7/17/2015
© AfriNIC 2004
5
Phase 1 (1/2)

Joint Request Evaluation:
5
2
1
Mail Robot
RIPE, ARIN,
APNIC
+ Ticketing
System
LIR
3
4
4
AfriNIC
Hostmaster
AfriNIC Ticketing
7/17/2015
© AfriNIC 2004
6
Phase 1 (cont)

Application for recognition (ICANN
ICP2)

AfriNIC database design and setup

AfriNIC WHOIS DB Setup
Choose to use RIPE WHOIS/DB
 Procedure then similar to RIPE

7/17/2015
© AfriNIC 2004
7
Phase 2 (1/2)
7/17/2015

Will start after Application for formal
recognition

New members will be officially informed
about AfriNIC and be asked to sign two
agreements (RIRs and AfriNIC’s one)

AfriNIC will serve as secondary DNS for
196.0.0.0/8 (reserved for Africa by all
RIRs)

Co-evaluation continues

Finalising Billing Systems.
© AfriNIC 2004
8
Phase 2
7/17/2015

Setup web based tools for members

Prepare and document Data transfer from
the different RIRs to AfriNIC system

Prepare and document transfer of 196/8
reverse DNS to AfriNIC.

Test and validation of Data transfer
process

Review of all supporting documents
© AfriNIC 2004
9
Phase 3
7/17/2015

Provisional recognition from
ICANN (expected for Dec’04)

Data transfer agreement between
AfriNIC and ARIN/RIPE
NCC/APNIC.

Full service to community based
on adopted policies
© AfriNIC 2004 10
So …







Phase-0 ended, Phase-1 has begun
Policy documents were adopted
Offices are setup, staff are operational
We have the community support
We have a financial plan
We have a clear transition plan
We have the International community support
Conclusion
We know where we are going, we are on the
way. We are confident that this progress will
bring more people to the wagon … and give
a positive message to the world that AfriNIC
is going to happen!
7/17/2015
© AfriNIC 2004 11
Transition time schedule
2004
Start sending requests to
[email protected]
Start billing transition
24/05/04 - AfriNIC I
-AGM
-Documents approval
Jan
Feb
Mar
26/01/04
RIPE Meeting
-Policies changes
-Project Meeting
Apr
May
Jun
-New Members start
signing double
Agreements
Jul
Aug
Sep
Oct
Nov
Dec
Start acting as Secondary
for 196/8
ICANN meeting
(Kuala Lumpur)
Application for recognition
ARIN regional Meeting
Staff
relocation in
South Africa
Prepare and Office setup
-General terms and conditions
-Policies (V4,v6, ASN, and DB)
-Internal procedure
-Billing
-New LIR
-Requests Form
-Etc..
-Operational budget
7/17/2015
RIPE NCC regional Meeting
Technical preparation for Phase 1
Start using the same procedure for
African Members
o Request forms
o Evaluation procedure
AfriNIC evaluate requests with RIRs
second approvals.
© AfriNIC 2004 12

Questions??
Next: AfriNIC policies compared with those of other RIRs.
7/17/2015
© AfriNIC 2004 13
Policy Comparison between
AfriNIC and other RIRs
(ARIN, APNIC, RIPE NCC,
LACNIC)
7/17/2015
© AfriNIC 2004 14
AfriNIC Policies?



7/17/2015
AfriNIC policies were developed by
the AfriNIC Policy WG
Were presented to the community
in the AFNOG-V /AfriNIC-1
meeting in Dakar (May 2004)
Were passed by the community
and ratified by the AfriNIC Board of
Directors!
© AfriNIC 2004 15
Policy Comparison
RIPE NCC
ARIN
APNIC
LACNIC
AfriNIC
Service
Region:
Europe,
North
Equatorial
Afria
USA,
Canada,
South
Equatorial
Africa
Asia, Indian
Ocean
Islands
South
America,
Carribean
Africa, Indian
Ocean
Islands
Official
Language(s):
English
English
English
English,
Spanish,
Portuguese
English,
French
7/17/2015
© AfriNIC 2004 16
IPv4 and IPv6:
RIPE NCC
ARIN
APNIC
LACNIC
AfriNIC
/20, /22
(Africa)
Same
Variable,
/22 (Africa)
/20
/22
/24
/20
N/A
Variable
/19
/23
/20
/24
/22
/30
Variable
/24
/20
/30
/19
/24
/21
/30
Variable
/32
/32
/32
/32
/32
IPv4:
Min. Alocation:
SubAllocations:
Min:
Max:
Assignments:
Min:
Max:
IPv6
7/17/2015
© AfriNIC 2004 17
Eligibility Criteria
RIPE NCC
ARIN
APNIC
LACNIC
IPv4:
show current
usage of IP
addresses from
upstream.
plan to
renumber into
new allocation
within 3 months

demonstrate
existing efficient
utilisation of a /22
must renumber
previous
assignments in 3
months

- be an LIR
- plan to assign 200
/48s in 2 yrs
(same)

IPv6:
AfriNIC
demonstrate
existing efficient
utilisation of a /20
show how the /20
will be used within 3
months


show current use
of /23 from
upstream,
plan to use a /22 in
one year
must renumber into
new allocation in 1
year
Demonstrate
efficient use of
a /22
(multihomed)
and /21 (not
multihomed)
(same)
-be an LIR
-offer IPv6
services to orgs
in service region
for 2 yrs
-be an LIR
-plan to make
/48 assignments
to end-users in
1 year.
7/17/2015
© AfriNIC 2004 18
AS Numbers and Reverse Delegation:
RIPE NCC
ARIN
APNIC
LACNIC
AfriNIC
Reverse
Delegation:
IPv4:
-in-addr.arpa
-LIRs only
Same
Same
Same
Same
IPv6:
Ip6.arpa (was
ip6.int)
Same
Same
Same
Same
(same)
(same)
(same)
AS Numbers
- network must be
multihomed
-network must
mention ASNs of 2
(same)
peers.
7/17/2015
© AfriNIC 2004 19
RIRs Policy Comparison Table.
Service Region:
Official Languages:
IPv4 policies:
 Minimum Allocation:
 Requirements :
 Sub-Allocations :
- minimum size:
- maximum size:
 Assignments:
- minimum size:
- maximum size:
 Assignment Window
Policy:

Additional
Allocation:
IPv6 Policies:
 Initial min. allocation:
 Eligibility Criteria:
 Min Assignment LIR
AS Numbers:
 Eligibility Criteria:
Reverse Delegation:

IPv4:

IPv6:
RIPE NCC
ARIN
LACNIC
APNIC
AfriNIC
Europe, North-Equatorial Africa
USA, Canada, South-Equatorial
Africa
South/Latin-America and
Caribbean.
Asia and Indian Ocean Islands.
Africa and Indian Ocean Islands.
English
English
English, Spanish, Portuguese
English
English, French
/20, /22 (Africa)
 demonstrate existing
efficient utilisation of a /22
 need to renumber previous
assignments in 3 months


/20, /22 (Africa)
demonstrate existing
efficient utilisation of a /20
show how the /20 will be
used within 3 months

/20
demonstrate efficient use of
a/22 (multihomed) and /21
(not multihomed)
Variable, /22 (Africa)
- show current use of /23 from
upstream,
- plan to use a /22 in one year
- must renumber in one year.
/22
-show current usage of IP
addresses from upstream.
-plan to renumber into new
allocation within 3 months
/24
/20
N/A
/23
/20
Variable – Depends on Need
/19
/24
/22
/30
Depends on LIRs assignment
window (see below)
/24
/20
/24
/21
/30
/19
/30
Depends on LIR’s sub-allocation
window.
N/A
N/A
-Only given after 80% of
existing allocation is reached
-Same as RIPE NCC
- Same
/32
- be an LIR
- plan to assign 200 /48s in 2 yrs
- /48 (unless network is v. large)
/32
- IPs assigned by LIR without
approval from RIPE NCC.
- LIR cannot assign IPs > AW
to any end-user in a calendar
year.
- same as RIPE NCC
/32
-be an LIR
-offer IPv6 services to orgs in
region for 24 months.
- Same as RIPE NCC
-Variable.
N/A
-Same as RIPE
NCC/ARIN/LACNIC
/32
-same as RIPE NCC
/32
-be an LIR
-plan to make /48 assignments to
end-users in 1 year.
- network must be multihomed
- network must supply ASN’s of
At least 2 peers.
- same-
- same
-same
-same
- In-addr.arpa
- Only requests from LIR are
accepted
- same-
-same
-same
-same
- ip6.arpa (was ip6.int)
- same -
-same
-same
-same
End
Questions or Comments
7/17/2015
© AfriNIC 2004 21