Engineering Update · •Manual/UI tester •Project Management •One project manager and one part-time project manager •CTO Staffing Summary 3. #ARIN44

Mark Kosters, CTO

Engineering Update

#ARIN442

Agenda•Staffing•Recent accomplishments•Statistics•Engineering plans through ARIN 45•A challenge question

#ARIN44

• Operations• Five engineers + manager

• Information Systems and Security • Three engineers + manager

• Development• Ten engineers + manager• User Experience Expert• User Interface Designer

• Software Integration • Six engineers + manager• Manual/UI tester

• Project Management • One project manager and one part-time project manager

• CTO

Staffing Summary

3

#ARIN44

•Main focus areas• Stateless website

• 16 releases since March that required no downtime• New POCs

• Routing• DNS

• Re-networked our provisioning site in Ashburn• Technical Debt

Highlights Since ARIN 42

4

#ARIN44

• ACSPs• ACSP Consultation: Deleting Aged Report Request Tickets• ACSP 2019.3: Add Routing & DNS POCs to ARIN Online• ACSP 2019.11: ROA Search Functionality• ACSP 2013.29: Improve ARIN Online Form Time-Out Behavior

• RDAP improvements• Linking entities in search results• Improvements to single-word query behavior• Returning nameservers in domain queries

• NRO• Identifier Technology Health Indicators (ITHI) Reporting

Highlights Since ARIN 42 (cont.)

5

#ARIN44

ARIN Online Usage157,230 accounts activated since inception through Q3 of 2019

60

5000

10000

15000

20000

25000

2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019

Number of Accounts Activated

#ARIN44

Active Usage of ARIN Online

7

0

10000

20000

30000

40000

50000

60000

70000

0 1 2-5 6-10 11-15 16+

Logins from Inception Through Q3 of 2019

Num

ber o

f Use

rs

Times Logged In

#ARIN44

Provisioning Transactions(cumulative – RESTful + templates)

8

0

1,000,000

2,000,000

3,000,000

4,000,000

5,000,000

6,000,000

7,000,000

8,000,000

9,000,000

ARIN29

ARIN30

ARIN31

ARIN32

ARIN33

ARIN34

ARIN35

ARIN36

ARIN37

ARIN38

ARIN39

ARIN40

ARIN41

ARIN42

ARIN43

ARIN44

408k 596k596k

1.0M 1.3M 1.5M1.7M

2.0M2.2M 2.4M 2.5M

2.8M 3.0M 3.2M 3.4M 3.6M

40k320k

3.5M

4.3M4.7M

5.0M5.6M

6.0M 6.2M6.5M

7.1M7.4M

7.7M8.2M 8.5M

841k

#ARIN44

Resource Public Key Infrastructure (RPKI) Usage

Oct2012

Apr2013

Oct 2013

Apr2014

Oct2014

Apr2015

Oct2015

Apr 2016

Oct2016

Apr2017

Oct 2017

Apr2018

Sep 2018

Apr 2019

Sep 2019

CertifiedOrgs 47 68 108 153 187 220 250 268 292 328 361 434 591 793

ROAs 19 60 106 162 239 308 338 370 414 470 538 604 1013 4519 5454

Covered Resources 30 82 147 258 332 430 482 528 577 640 741 825 1953 5816 7514

Up/Down Delegated 0 0 0 1 2 1 2 2 2 1 1 1 1

9

#ARIN44

Whois/Whois-RWS Queries Per Second

10

0.00

500.00

1000.00

1500.00

2000.00

2500.00

3000.00

3500.00

4000.00

1999

-10

2000

-06

2001

-02

2001

-10

2002

-06

2003

-02

2003

-10

2004

-06

2005

-02

2005

-10

2006

-06

2007

-02

2007

-10

2008

-06

2009

-02

2009

-10

2010

-06

2011

-02

2011

-10

2012

-06

2013

-02

2013

-10

2014

-06

2015

-02

2015

-10

2016

-06

2017

-02

2017

-10

2018

-06

2019

-02

Queries Per Second

Whois-RWSWhois

#ARIN4411

0.00

50.00

100.00

150.00

200.00

250.00

2015

-06

2015

-08

2015

-10

2015

-12

2016

-02

2016

-04

2016

-06

2016

-08

2016

-10

2016

-12

2017

-02

2017

-04

2017

-06

2017

-08

2017

-10

2017

-12

2018

-02

2018

-04

2018

-06

2018

-08

2018

-10

2018

-12

2019

-02

2019

-04

2019

-06

2019

-08

Queries Per Second

IPv4

IPv6

Registry Data Access Protocol (RDAP)

#ARIN44

Whois/Whois-RWS/RDAP Queries over IPv6

12

0.00%

5.00%

10.00%

15.00%

20.00%

25.00%

2009

-01

2009

-06

2009

-11

2010

-04

2010

-09

2011

-02

2011

-07

2011

-12

2012

-05

2012

-10

2013

-03

2013

-08

2014

-01

2014

-06

2014

-11

2015

-04

2015

-09

2016

-02

2016

-07

2016

-12

2017

-05

2017

-10

2018

-03

2018

-08

2019

-01

2019

-06

Directory Service Queries over IPv6

#ARIN44

Internet Routing Registry (IRR) Maintainers

1,726 1,850 1,951 2,1022,322 2,485 2,692

2,9573,494

0

500

1,000

1,500

2,000

2,500

3,000

3,500

4,000

2011 2012 2013 2014 2015 2016 2017 2018 2019Maintainers

2019 Data through Q3

13

#ARIN44

IRR route / route6 Objects

18,636 19,969 21,204 23,535 27,255 31,464 36,315 39,167 63,867

242527 698 1,072 1,385 1,712 2,145 3,211

8,677

1

10

100

1,000

10,000

100,000

2011 2012 2013 2014 2015 2016 2017 2018 2019

2019 data through Q3 routeroute6

14

#ARIN44

IRR inetnum / inet6num Objects

419 481 531 621 731 906 965 1,066

5,089

1325 38 51 77 137 159 173

345

1

10

100

1,000

10,000

2011 2012 2013 2014 2015 2016 2017 2018 2019

inetnum

inet6num2019 data through Q3

15

#ARIN44

Number of Organizations Number of Objects

7 1,001-19,574

59 100-1,000

6 90-99

9 80-89

12 70-79

19 60-69

22 50-59

654 10-49

798 5-9

1,943 1-4

IRR Object Breakout by Organization

16

#ARIN4417

Factors That Influence Priorities• Legal and regulatory• Ratified policies• ARIN Consultation and Suggestion Process (ACSP)• Board of Trustee initiatives• Operating plan objectives

• Defects, maintenance, and upgrades• Mailing list ad-hoc requests• Environment changes• Customer feedback (via feedback button)• Customer Survey

#ARIN44

• IRR

• Development started work in Q3 2019

• Working on back-end management interface

•Website phase II• Website chat

• Website usability improvements

What We Are Working on Through 2020 Q1

18

#ARIN44

• Technical backlog • Some services hosted on Java 7, JBoss, and CentOS 6• Upgrading bump-in-the-wire DNSSEC signer • Need to roll keys for the various /8s• Set it up to move off of Secure64 if necessary

• RPKI HSM Upgrade – moving to the IBM 4767 from the IBM 4765

• Global Service Load Balancing for ARIN Services• Currently using round-robin DNS

What We Are Working on Through 2020 Q1 (cont.)

19

#ARIN44

• Tackling technical debt and IRR work at the same time• Using Kubernetes to move from monolithic architecture to micro-

services• Tackle things in smaller components

• ARIN Online user interface upgrade was a multi-year effort with our monolithic system

• Tackling things in smaller chunks will end up with a more manageable system by eliminating middleware (i.e., JBoss)

• Utilize current themes in technology• Modernize incrementally

• The end result will be more robust and easier to maintain

What We Are Working on Through 2020 Q1 (cont.)

20

#ARIN44

• Working out differences on• Registration Data Access Protocol (RDAP) implementations• Extended statistics file formats

• Identifier Technology Health Indicators (ITHI)• Working on coordinated reporting between the RIRs

• Resource Public Key Infrastructure (RPKI)• Providing operational feedback on various protocol enhancements within the Internet

Engineering Task Force (IETF)• Examples are:

• RPKI Validation Reconsidered• RPKI Signed Object for Trust Anchor Locators (TALs)• Where to easily find the various TALs

Coordination Work with the Other RIRs

21

#ARIN4422

Challenge Question – What to Do with Duplicate Services?• We have several overlapping services

• Easy to add new services• Hard to retire services• Each service has cost and effort to run• There are many – will just focus on three

• Report access• FTP• HTTP/HTTPS

• Provisioning for reassignments• Templates

• Been around since before 1991• Mail based – very complex

• Reg-RWS• RESTful API

• SWIP-EZ• Web-based input

#ARIN4423

More Duplicate Services•Directory services (e.g., Whois)• Port 43 Whois• RFC 812 – published in 1982

• RWhois• RFC2167 – published in 1997

• Whois-RWS• RESTful interface to Whois data over http/https

• Web-based Whois-RWS• https://whois.arin.net

• RDAP• The IETF sanctioned way for getting directory services data

• Web-based RDAP• https://search.arin.net

#ARIN4424

Consultation on Retirement of Legacy Services• Requires YOUR input on why you rely on legacy services – examples:• Not useful• It’s the way its always been done

• Useful• We need to upgrade our internal interface with ARIN• We are missing key functionality

• Consultations for potential retirement of legacy services planned in 2020 • If a service is to be retired, you will have plenty of time for transition• Important to consider for managing ARIN’s overall technical debt; i.e. cost-

effective maintainability of ARIN’s technical infrastructure

#ARIN44

Thank you.Any Questions?

???

25

Thank you.Any Questions?

#ARIN44

Discussion

26