Presentation by Vivek NIgam at SANOG 32 on 9 August, 2018

1. 1
Maintaining your APNIC Routing
Registry (RR) data
SANOG 32, Dhaka
9 August 2018
vivek@apnic.net

2. APNIC database and the Internet Routing
Registry (IRR)
• APNIC Whois Database
⁃ Two databases in one
• Public network management database
⁃ Whois information about networks and contacts (IP addresses, ASNs
and so forth)
• Routing Registry (RR)
⁃ Contains routing information (routes, filters, peers and so forth)
⁃ APNIC RR is part of the global IRR

3. APNIC RR NRTM agreements
APNIC RR
RADB JPIRR NTT
CNNIC AFRINIC IDNIC

4. Out-of-region route objects in RIPE IRR
• Need for operators to have route objects for out-of-region
prefixes
• No workable solution for cross-registry authorization
• Routes created using a well-known maintainer with public
password
• Authorization by prefix custodians was unverified

5. Changing views in the RIPE community
• Good reasons for creating this service initially
• Increase in out-of-region prefix hijacks with false route
objects
• Support for this service has faded in recent times
• RIPE DB working group declared consensus on stopping
this service

6. Does this change affect you?
• No new route objects for out-of-region prefixes in RIPE RR
• “source:” attribute of existing objects will be modified to
“RIPE-NONAUTH”
• Further community consultation before deleting these
objects

7. 22 21
1239
89
50
258
116
266 266
211
163
2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018
Out-of-region routes using APNIC prefixes

8. Number of APNIC Members affected
1 1 1 1 1 2
4 4 4 5 5
7
10
12 13
20 20 21 22
34
40
45
54
57
CX IO NC NP TL MM AF MN VN PH TW KR NZ BD ID JP MY SG AP AU HK IN CN PK

9. 9
WHAT SHOULD YOU DO IF YOU
ARE AFFECTED?

10. Your addresses, your ASN
• Objects created in APNIC Whois Database using normal
mechanisms
⁃ Use MyAPNIC or auto-dbm@apnic.net

11. Your addresses, somebody else’s ASN?
• ASN belongs to another APNIC Member?
⁃ Email notification sent to Member contacts
• ASN delegated by other RIR?
⁃ Email notification sent to whois contacts of ASN
• Unallocated ASN?
⁃ Email notification to APNIC Helpdesk for follow up

12. Route objects in APNIC RR
37828
61567
39328
27198
16433
3876
7402
601 1110 1020
2720 1160
2013 2014 2015 2016 2017 2018
Create Delete

13. Import your routes from whois & BGP

14. Creating new routes

15. Maintaining your routes

16. 16
QUESTIONS?