1. Tampa, FL 18 February 2016

2. Welcome. Here today from ARIN… Jan Blacka, Senior User Experience Specialist Kevin Blumberg, ARIN Advisory Council John Curran, President and CEO Susan Hamlin, Director of Communications & Member Services Frank Hill, Senior Software Engineer Wendy Leedy, Member Engagement Coordinator Debra Martin, Senior Project Manager Jon Worley, Senior Director Global Registry Services

3. Agenda 10:00 AMWelcome and Getting Started 10:15 AMARIN: Mission, Role and Services; John Curran 10:45 AMSecurity Overlays on Core Internet Protocols – DNSSEC; Frank Hill 11:20 AM Life After IPv4 Depletion; Jon Worley Noon Networking Lunch 1:00 PMARIN Services and Tools; Debra Martin 1:30 PMPolicy Development Process; Kevin Blumberg 2:00 PMSecurity Overlays on Core Internet Protocols – Resource Certification (RPKI); Frank Hill 2:30 PMIPv6 Adoption; Debra Martin and Jon Worley 3:00 PMQ&A / Open Mic Session

4. Let’s Get Started! Self introductions – Name – Organization – I would like to learn more about “___________.”

5. ARIN and the RIR System: Mission, Role and Services John Curran President and CEO

6. What is an RIR? A Regional Internet Registry (RIR) manages the allocation and registration of Internet number resources in a particular region of the world. Number resources include IP addresses and autonomous system (AS) numbers.

7. Regional Internet Registries

8. Not-for-profit Membership Organization Community Regulated Fee for services, not number resources 100% community funded Open Broad-based - Private sector - Public sector - Civil society Community developed policies Member- elected executive board Open and transparent RIR Structure

9. IP Address and Autonomous System Number Provisioning Process

10. The NRO exists to protect the unallocated number resource pool, to promote and protect the bottom-up policy development process, and to act as a focal point for Internet community input into the RIR system. Number Resource Organization

11. ARIN, a nonprofit member-based organization, supports the operation of the Internet through the management of Internet number resources throughout its service region; coordinates the development of policies by the community for the management of Internet Protocol number resources; and advances the Internet through informational outreach.

12. ARIN’s Service Region The ARIN Region includes many Caribbean and North Atlantic islands, Canada, the United States and outlying areas.

13. Who is the ARIN “community”? Anyone with an interest in Internet number resource management in the ARIN region

14. The ARIN Community includes… 5,200+ members 20,000+ customers 79 professional staff 7 member Board of Trustees elected by the membership 15 member Advisory Council elected by the membership 3 person NRO Number Council elected by the ARIN Community

15. Organizational Chart CMSD: 11 employees ENG: 42 employees EXEC: 6 employees FSD: 6 employees HR: 4 employees RSD: 11 employees (includes future director) Total: 80 employees at ARIN (includes future RSD director)

16. ARIN Board of Trustees Paul Andersen, Vice Chair Vinton G. Cerf, Chair John Curran, President and CEO Timothy Denton, Secretary Aaron Hughes Bill Sandiford, Treasurer Bill Woodcock 16

17. ARIN Advisory Council Dan Alexander, Chair Cathy Aronson Kevin Blumberg, Vice Chair Owen DeLong Andrew Dul David Farmer David Huberman Scott Leibrand Tina Morris Milton Mueller Amy Potter Leif Sawyer Robert Seastrom John Springer Chris Tacit 17

18. NRO Number Council 15 member body – 3 representatives from each RIR From ARIN: – Jason Schiller – Louie Lee – John Sweeting Fulfills role of the ICANN Address Supporting Organization Address Council – Global policy and ICANN Board Seats 18

19. 2016 Focus 1.Continued IPv4 to IPv6 Transition Awareness 2.Continued participation in Internet Governance forums 3.Continue to review and enhance ARIN Online, including making significant user interface improvements per user feedback 4.Participate in planning discussions for the transition of the stewardship of IANA to encourage responsible oversight of critical Internet resources 5.Continue to focus on community suggested, customer facing, high impact software development efforts in a timely manner 6.Improve customer service based on feedback and repeat customer satisfaction survey 19

20. ARIN Services and Products ARIN Manages : Number Resources IP address allocations & assignments ASN assignment Transfers Reverse DNS Directory services Whois Routing Information (Internet Routing Registry [IRR]) WhoWas 20

21. ARIN Services and Products ARIN coordinates and administers : Policy Development Community meetings Discussion Publication Elections Information publication and dissemination and public relations Community outreach Education and training 21

22. ARIN Services and Products ARIN develops technologies for managing Internet number resources : ARIN Online DNSSEC Resource Certification (RPKI) Whois-RWS Reg-RWS Community Software Project Repository 22

24. Globalization of IANA Oversight On 14 March 2014, the US Government announced plans to transition oversight of the IANA functions contract to the global multistakeholder community Current IANA functions contract expires 30 September 2016

25. NTIA* Conditions for Transition Proposal 1.Support and enhance the multi-stakeholder model 2.Maintain the security, stability, and resiliency of the “Internet DNS” 3.Meet the needs and expectation of the global customers and partners of the IANA services 4.Maintain the openness of the Internet * National Telecommunications and Information Administration (NTIA) within the U.S. Department of Commerce

26. Steps in the IANA Stewardship Proposal 1. The three “customer groups” of IANA submitted proposals: Number Resources (RIR community) - 15 Jan 2015 https://www.nro.net/wp-content/uploads/ICG-RFP-Number- Resource-Proposal.pdf Domain Names: 25 June 2015https://community.icann.org/x/aJ00Awhttps://community.icann.org/x/aJ00Aw Protocol Parameters : 6 January 2015 http://tools.ietf.org/html/draft-ietf-ianaplan-icg- response-09

27. Steps in the IANA Stewardship Proposal 2.The IANA Stewardship Transition Coordination Group (ICG) combined the three proposals into a single IANA Stewardship Transition Proposal – Oct. 2015 https://www.ianacg.org/icg-files/documents/IANA-transition-proposal-v9.pdf 3. ICG to send proposal to NTIA via the ICANN Board. Another body, the Cross Community Working Group is working on accountability requirements (implementation, review of work, etc.).

28. IANA Stewardship – Potential Implications Successful transition of IANA Stewardship from the USG to the Internet community would be an important validation of the Internet’s multi-stakeholder governance model Inability to transition could raise concerns about the validity of the multi-stakeholder process and fuel discussion of the perceived need for intergovernmental mechanisms for Internet Governance

29. Get 6 – Websites on IPv6 http://teamarin.net/infographic/ IPv6 Wiki

30. How to Participate in ARIN Attend Public Policy and Members Meetings & Public Policy Consultations – Remote participation available Apply for Meeting Fellowship Discuss policies on Public Policy Mailing List (ppml) Come to outreach events Subscribe to an ARIN mailing list

31. More Ways to Participate Give your opinion on community consultations Submit a suggestion Contribute to the IPv6 wiki Write a guest blog for TeamARIN.net Connect with us on social media Members – Vote in annual elections

32. https://www.arin.net/participate/meetings/fellowship.html

33. Q&A

34. Security Overlays on Core Internet Protocols – DNSSEC Frank Hill Sr Software Engineer

35. Core Internet Protocols Two critical resources that are unsecured – Domain Name Servers – Routing Hard to tell if compromised – From the user point of view – From the ISP/Enterprise

36. DNS

37. How DNS Works Resolver Question: www.arin.net A www.arin.net A ? Caching forwarder (recursive) root-server www.arin.net A ? Ask net server @ X.gtld-servers.net (+ glue) gtld-server www.arin.net A ? Ask arin server @ ns1.arin.net (+ glue) arin-server www.arin.net A ? 192.168.5.10 Add to cache

38. What Is DNSSEC? Why Use It? Standard DNS (forward or reverse) responses are not secure – Easy to spoof – Notable malicious attacks DNSSEC attaches signatures – Validates responses – Can not spoof

39. Reverse DNS at ARIN ARIN issues blocks without any working DNS – Registrant must establish delegations after registration – Then employ DNSSEC if desired Just as susceptible as forward DNS if you do not use DNSSEC

40. Reverse DNS at ARIN Authority to manage reverse zones follows allocations – “Shared Authority” model – Multiple sub-allocation recipient entities may have authority over a particular zone

41. Setting up DNSSEC at ARIN Must have a RSA/LRSA signed – We need to know who you are Create entry method for DS Records – ARIN Online – RESTful interface – Not available via templates Only key holders may create and submit Delegation Signer (DS) records

42. Reverse DNS in ARIN Online First identify the network that you want to put Reverse DNS nameservers on…

43. Reverse DNS in ARIN Online …then enter the Reverse DNS nameservers…

44. DNSSEC in ARIN Online …then apply DS record to apply to the delegation

45. Reverse DNS: Querying ARIN’s Whois Query for the zone directly: whois> 81.147.204.in-addr.arpa Name: 81.147.204.in-addr.arpa. Updated: 2006-05-15 NameServer: AUTHNS2.DNVR.QWEST.NET NameServer: AUTHNS3.STTL.QWEST.NET NameServer: AUTHNS1.MPLS.QWEST.NET Ref: http://whois.arin.net/rest/rdns/81.147.204.in-addr.arpa.

46. DNSSEC in Zone Files ; File written on Mon Feb 24 17:00:53 2014 ; dnssec_signzone version 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 0.74.in-addr.arpa. 86400 IN NS NS3.COVAD.COM. 86400 IN NS NS4.COVAD.COM. 10800 NSEC 1.74.in-addr.arpa. NS RRSIG NSEC 10800 RRSIG NSEC 5 4 10800 20140306210053 ( 20140224210053 57974 74.in-addr.arpa. oNk3GVaCWj2j8+EAr0PncqnZeQjm8h4w51nS D2VUi7YtR9FvYLF/j4KO+8qYZ3TAixb9c05c 8EVIhtY1grXEdOm30zJpZyaoaODpbHt8FdWY vwup9Tq4oVbxVyuSNXriZ2Mq55IIMgDR3nAT BLP5UClxUWkgvS/6poF+W/1H4QY= ) 1.74.in-addr.arpa. 86400 IN NS NS3.COVAD.COM. 86400 IN NS NS4.COVAD.COM. 10800 NSEC 10.74.in-addr.arpa. NS RRSIG NSEC 10800 RRSIG NSEC 5 4 10800 20140306210053 ( 20140224210053 57974 74.in-addr.arpa. DKYGzSDtIypDVcer5e+XuwoDW4auKy6G/OCV VTcfQGk+3iyy2CEKOZuMZXFaaDvXnaxey9R1 mjams519Ghxp2qOnnkOw6iB6mR5cNkYlkL0h lu+IC4Buh6DqM4HbJCZcMXKEtWE0a6dMf+tH sa+5OV7ezX5LCuDvQVp6p0LftAE= )

47. DNSSEC in Zone Files 0.121.74.in-addr.arpa. 86400 IN NS DNS1.ACTUSA.NET. 86400 IN NS DNS2.ACTUSA.NET. 86400 IN NS DNS3.ACTUSA.NET. 86400 DS 46693 5 1 ( AEEDA98EE493DFF5F3F33208ECB0FA4186BD 8056 ) 86400 DS 46693 5 2 ( 66E6D421894AFE2AF0B350BD8F4C54D2EBA5 DA72A615FE64BE8EF600C6534CEF ) 86400 RRSIG DS 5 5 86400 20140306210053 ( 20140224210053 57974 74.in-addr.arpa. n+aPxBHuf+sbzQN4LmHzlOi0C/hkaSVO3q1y 6J0KjqNPzYqtxLgZjU+IL9qhtIOocgNQib9l gFRmZ9inf2bER435GMsa/nnjpVVWW/MBRKxf Pcc72w2iOAMu2G0prtVT08ENxtu/pBfnsOZK nhCY8UOBOYLOLE5Whtk3XOuX9+U= ) 10800 NSEC 1.121.74.in-addr.arpa. NS DS RRSIG NSEC 10800 RRSIG NSEC 5 5 10800 20140306210053 ( 20140224210053 57974 74.in-addr.arpa. YvRowkdVDfv+PW42ySNUwW8S8jRyV6EKKRxe …

48. DNSSEC Validating Resolvers www.internetsociety.org/deploy360/dnssec/ www.isc.org/downloads/bind/dnssec/

49. Reverse DNS Management and DNSSEC in ARIN Online Available on ARIN’s website http://www.arin.net/knowledge/dnssec/

50. DNSSEC Statistics ARIN 36 Number of Orgs with DNSSEC123 Total Number of Delegations 583,442 DNSSEC Secured Zones586 Percentage Secured 0.1 %

51. Q&A

52. Life After IPv4 Depletion Jon Worley –Analyst Jon Worley Technical Services Manager

53. Overview IPv4 depletion recap Post-depletion observations Post-depletion IPv4 options – IPv4 Waiting List – IPv4 Transfers – Dedicated IPv4 block to facilitate IPv6 deployment 53

54. IPv4 Address Space in ARIN Free Pool /8s

55. IPv4 Depletion Recap June 2015: IPv4 requests reach peak volume – 414 total requests – A mad rush for the last IPv4 blocks July 1 st, 2015: First unmet IPv4 request – An org qualified for a block size that was no longer available – Within a few weeks, only single /24s remained in the free pool September 24 th, 2015: Full IPv4 depletion – No IPv4 blocks available other than those reserved for specific policies – Significant drop in monthly # of IPv4 requests

56. 2015 IPv4 Requests ------- = waiting list initiated ------- = IPv4 depletion

57. Reserved IPv4 Space /10 reserved to facilitate IPv6 deployment 2 /16s reserved for critical Internet infrastructure – Public exchange points – Core DNS service providers (excluding new gTLDs) – Regional Internet Registries – IANA

58. Post-IPv4 Depletion Observations IPv4 demand remains strong Lots of questions/confusion from customers – Not all aware we’ve reach full IPv4 depletion – Education needed on post-depletion options Keeping registration info current is essential – Increase in # of blocks targeted for hijacking – Blocks with bad org/contact info, especially legacy ones, are the biggest target 58

59. Post-IPv4 Depletion Options IPv4 Waiting List IPv4 Transfer Market Dedicated IPv4 block to facilitate IPv6 deployment Adopt IPv6

60. IPv4 Waiting List Policy enacted first time ARIN did not have a contiguous block of addresses of sufficient size to fulfill a qualified request – Must qualify under current ARIN policy and request to be added to the list – Maximum approved size determined by ARIN – Minimum acceptable size specified by requester – One request per org on the list at a time – Limit of one allocation or assignment every 3 months Waiting List published on ARIN’s web site – Approximately /12 needed to fill all pending requests https://www.arin.net/resources/request/waiting_list.html

61. Requests Added to IPv4 Waiting List ------- = waiting list initiated ------- = IPv4 depletion

62. Sources of IPv4 for the Waiting List Returned to ARIN or revoked for non- payment – In both cases, lengthy review required to confirm space is eligible for reissue Redistributed by IANA per global policy for “post exhaustion IPv4 allocation mechanisms by IANA” » /11 (issued 5/14), /12 (issued 9/14), /13 (issued 3/15), and /14 (issued 9/15) by IANA to each RIR

63. How Long Might You Wait? 297 tickets added since wait list started 27 wait list requests filled – 13 filled with IANA /14 equivalent issued in 9/2015 – 13 filled with blocks previously held for organizations deciding whether to go on the waiting – 1 filled with space that had been revoked 19 filled via 8.3 transfer and removed from list (as required per policy) Demand is far greater than availability 63

64. Transfers of IPv4 Addresses 3 ARIN Transfer Policies Available: – Mergers and Acquisitions (NRPM 8.2) Traditional transfer based on change in business structure, including company reorganizations, supported by legal documentation – Transfers to Specified Recipients (NRPM 8.3) IPv4 market transfer based on financial transaction, supported by justified need (within region) – Inter-RIR transfers to Specified Recipients (NRPM 8.4) IPv4 market transfer based on financial transaction, supported by justified need (outside region)

65. Transfers to Specified Recipients (NRPM 8.3) Allows orgs with unused IPv4 resources to transfer them to orgs in need of IPv4 resources Source – Must be current registrant, no disputes – Not have received addresses from ARIN for 12 months prior Recipient – Must demonstrate need for 24-month supply under current ARIN policy

66. Specified Recipient Transfers ------- = waiting list initiated ------- = IPv4 depletion

67. Inter-RIR Transfers (NRPM 8.4) RIR must have reciprocal, compatible needs-based policies – Currently APNIC and RIPE NCC Transfers from ARIN – Source cannot have received IPv4 from ARIN 12 months prior to transfer – Must be current registrant, no disputes – Recipient meets destination RIR policies Transfers to ARIN – Must demonstrate need for 24-month supply under current ARIN policy

68. Inter-RIR Transfers ------- = waiting list initiated ------- = IPv4 depletion

69. Documentation Required for IPv4 Source Verification current registrant is active and in good standing within the ARIN region – If there was a merger or acquisition, an M&A transfer may be required before you can release your IPv4 addresses Notarized officer acknowledgement Additional items may be needed

70. IPv4 Recipient Documentation – Utilization data for ARIN-issued IPv4 space – Data to support 24 month projected need Historical IPv4 utilization rate New services/markets to be deployed Customer growth projections – Signed officer attestation certifying data is accurate

71. Useful Transfer Information ARIN cannot provide detailed information about your source/recipient partner’s status – Can provide general status (e.g. “we’re waiting on them to provide additional info”) – If you need details on what’s required, ask your source/recipient partner If you’re on the IPv4 waiting list, you’ll be removed if/when you receive IPv4 addresses via transfer

72. IPv4 Transfer Stats Transfers to Specified Recipients (8.3) – 452 prefixes transferred, ranging from /24s to /10 – 23 ASNs Inter-RIR Transfers (8.4) – 201 prefixes transferred, ranging from /24s to /13s 188 ARIN to APNIC 10 ARIN to RIPE NCC 3 APNIC to ARIN https://www.arin.net/knowledge/statistics/transfers. html 72

73. Pre-Approval for Recipients Optional free service to confirm your 24 month projected need for IPv4 addresses – Same documentation requirements as transfers Used to receive IPv4 addresses via specified or Inter-RIR transfers up to the pre-approved amount – Eliminates the need to re-justify need on each transfer – Good for 24 months from the pre-approval date

74. Specified Transfer Listing Service (STLS) Optional fee-based service to facilitate specified recipient and inter-RIR transfers – Sources have IPv4 addresses verified as available – Recipients have a verified need for IPv4 addresses – Facilitators arrange transfers between parties Approved participants can view detailed information for all other participants Public summary available on ARIN’s website – Available block sizes – # of needers and approved block sizes – List of facilitators with contact information

75. Tips for Faster Transfer Processing Ensure all registration information is current – If not, we can help you get it up to date Request pre-approval – Ensures you can bid confidently – Turns transfers into a point-click-ship exercise Provide detailed information to support 24- month need when submitting transfer/pre- approval

76. Reserved IPv4 Block for IPv6 Deployment Requirements Used to facilitate IPv6 deployment (dual stacking, IPv4->IPv6 translation, etc) Need cannot be met from your existing ARIN IPv4 space Have an IPv6 block registered One /24 per organization every six months

77. Help! What Should I Do? Small networks can get a /24 once per six months for IPv6 transition – Cost likely to be lower than the transfer market – Reserved block likely to last several years – Can also have a request on the waiting list Larger networks can get pre-approved for 24 month need and seek IPv4 on the transfer market – Waiting list probably not a realistic option unless you can delay your IPv4 needs indefinitely All networks should begin IPv6 adoption

78. Waiting List vs. Transfer Market Since 7/1/2015

80. LUNCH Take your valuables as the room will not be locked.

81. ARIN Technical Services Debra Martin Senior Project Manager

82. Major Services ARIN Online Mail Directory Services – Whois – Whois-RWS – RDAP DNS IRR RPKI OT&E

83. ARIN Online Web Interface – Creating an account – Linking to existing Points of Contacts (POCs) – Creating/linking to Organizations – Managing Reverse DNS – Managing Resource Requests – Specified Transfer Listing Service – Ask ARIN – Message Center – RPKI – Reporting – Billing and Payments – Voting

84. ARIN Online Usage 104,312 accounts activated since inception through Q3 of 2015 84 Number of Accounts Activated 500010000 15000 20000 * Through Q3 of 2015

85. Active Usage of ARIN Online 85 # of Users Times logged in Logins from inception through Q3 of 2015 One user logged in 1,205,887 times!

86. Linking? Way of managing resources put into place before ARIN Online was unveiled A good set of videos at – https://www.youtube.com/user/teamarin https://www.youtube.com/user/teamarin – Teaches you how to: Create an account via “Manage your Records” video Relationships with POCs “Point of Contact Records” video

87. Ask ARIN and Message Center Ask ARIN A way to ask ARIN staff a question on the web Message Center – Tracks ticketed requests – Ticketed requests are things like resource requests and correspondence, RPKI notifications, reports

88. Reports Associations Report – POCs linked to your ARIN Online account, including roles served by these POCs for any associated Org IDs (Admin, Tech, Abuse, etc.) – Org IDs associated with your ARIN Online account – Network records (NETs) and Autonomous System Number records (ASNs) associated with your linked POCs, directly or via an associated Org ID

89. Reports (Cont) User Reassignment Report – Reassignments associated with your ARIN Online account via associated Org IDs – ”Holes" in all Network records (NETs) associated with your ARIN Online account, where no reassignment or reallocation has been made Whowas – History of a resource Bulk Whois – Directory services information placed in files Reports are ticketed and delivered into your Message Center

90. Billing Can View and pay current and past- due invoices

91. REST Services Provisioning – Reassignment Information – Points of Contacts – Organizations Requesting Reports

92. What is REST? Representational State Transfer As applied to web services – defines a pattern of usage with HTTP to create, read, update, and delete (CRUD) data – “Resources” are addressable in URLs Very popular protocol model – Amazon S3, Yahoo & Google services, …

93. The BIG Advantage of REST Easily understood – Any modern programmer can incorporate it – Can look like web pages Re-uses HTTP in a simple manner – Many, many clients – Other HTTP advantages This is why it is very, very popular with Google, Amazon, Yahoo, Twitter, Facebook, YouTube, Flickr, …

94. What does it look like? Who can use it? Where the data is. What type of data it is. The ID of the data. It is a standard URL. Anyone can use it. Go ahead, put it into your browser.

95. Where can more information on REST be found? RESTful Web Services – O’Reilly Media – Leonard Richardson – Sam Ruby

96. RESTful Services Whois-RWS RDAP RPKI Provisioning Reporting

97. Mail/Templates Before ARIN Online, only way of communicating with ARIN Now only – Reassignment information – Inter-RIR Transfers – Email Questions Lots of Spam

98. Reg-RWS Transactions (cumulative) 98

99. Directory Services Whois – Resource Information as per RFC812 Whois-RWS – RESTful Implementation of Whois RDAP – Resource Information as per RFCs 7480- 7484

100. Whois Queries Per Second 100

101. DNS Provide Reverse DNS delegation management for IPv4 and IPv6 This includes DNSSEC More Detail later

102. IRR Provides coarse routing information for routing filters Processed through templates sent via email Has a whois interface using RPSL (RFC 2622) ARIN will be upgrading this service starting Q3 of 2016 Documented at – https://www.arin.net/resources/routing/

103. OT&E (Operational Test & Evaluation) Lots of people test in production – Is not the best place to test – Things do get stuck – may impact others – Operational Test & Evaluation Goodness of OT&E – Place to test code – Place to test process – All services now under ote.arin.net except email – Need to register to participate – https://www.arin.net/resources/ote.html https://www.arin.net/resources/ote.html

104. RPKI We will talk about this in detail later

105. Feedback Users can notify us of Internet Number Resource Fraud and Whois Inaccuracy Can provide feedback on the application via the feedback button Suggestions through “ARIN Consultation and Suggestion Process” (ACSP)

106. Tools Lots of API’s You can build your own tools Some have shared their tools with others Repository for these tools is at http://projects.arin.net

107. Q&A

108. ARIN’s Policy Development Process Kevin Blumberg Vice Chair, ARIN Advisory Council

109. Overview Basic steps Examples of past policy changes A current proposal How to get involved

110. Policy Development Process (PDP) Steps 1)Proposal – Someone in the community thinks a policy can be improved and documents 2)Draft Policy- Discussion on the list and possibly at meeting(s) - Is there really a problem? Is this a good solution? 3)Recommended Draft Policy - More discussion and presentation at meeting(s). Does community support turning this into policy? 4)Last call 5)Board Review 6)Staff Implementation (NRPM) If you submit a proposal, you can participate further, or let the ARIN process “shepherd” it through the steps

111. Past Policy Changes: IPv6 Policy Circa 2001: Initial IPv6 policy aligned with IPv4 at that time, conservation was important, small amounts issued for short periods, hierarchical distribution from upstreams, and, no end user policy at all 2003-2016 Dozens of proposals to improve IPv6 policy Changes included: Minimum allocation size increased (/35 to /32), larger allocations from IANA, policy for end users, community networks (mesh networks), assignment sizes from ISPs to customers (/56s), larger amounts for ISPs and easier criteria, larger amounts for end users and easier criteria, bit boundary assignments and allocations, etc.

112. Past Policy Changes: Transfers 1997 thru 2007: Policy for Mergers and Acquisitions existed, everything else should go back to ARIN 2007 thru 2016: Many proposals to improve transfers. Changes included: Allow needs-based transfers of unused or underutilized address space between organizations via ARIN, increase supply period from one year to two, allow ASN transfers, allow Inter-RIR transfers, etc. Still seeing proposals to make transfers easier, there are some who are trying to reduce the needs requirement, some want ARIN to simply record the transfers.

113. Policy Currently Under Discussion ARIN-2015-5: Out of Region Use Would allow an organization to receive Internet number resources from ARIN for use out of region as long as the applicant is currently using at least the equivalent of a /22 of IPv4 space, /44 of IPv6, or 1 ASN within the ARIN service region. Earlier Abandoned Proposals ARIN-2014-1: Out of Region Use ARIN-2013-6: Allocation of IPv4 and IPv6 Address Space to Out-of-region Requestors ARIN-2011-13: IPv4 Number Resources for Use Within Region (continued on next slide)

114. 2015-5 continued ARIN-2015-5 presented at ARIN 36 in Oct 2015 AC found draft to be fair, technically sound and supported and promoted to recommended state (late Oct 2015) Presented as Recommended Draft Policy at NANOG 66 Next steps – Last call or present again at ARIN 37? – After Last Call could be: Review of last call comments Board Review Implementation by Staff

115. How Can You Get Involved? Two ways to learn and be heard 1.Public Policy Mailing List 2.Public Policy Consultations/Meetings ARIN meetings (April and October) ARIN Public Policy Consultations at NANOG (twice a year, usually February and June) Remote participation supported

116. Takeaways 1)ARIN doesn't make up number policy, you do. 2)Well documented policy development process includes assistance from ARIN AC and staff throughout the process. 3)Stay informed. Join the policy list and/or attend meetings (in person or remotely).

117. Q&A

118. References Policy Development Process (PDP) http://www.arin.net/policy/pdp.html http://www.arin.net/policy/pdp.html Draft Policies and Proposals http://www.arin.net/policy/proposals/index.html http://www.arin.net/policy/proposals/index.html Number Resource Policy Manual (NRPM) http://www.arin.net/policy/nrpm.html http://www.arin.net/policy/nrpm.html

119. PDP Goals 1)"open, transparent, and inclusive manner that allows anyone to participate in the process.“ 2)"clear, technically sound and useful policies“ 3)“policies, not processes, fees, or services”

120. Security Overlays on Core Internet Protocols – RPKI Frank Hill Sr Software Engineer

121. Core Internet Protocols Two critical resources that are unsecured – Domain Name Servers – Routing Hard to tell if compromised – From the user point of view – From the ISP/Enterprise

122. Routing

123. Routing Architecture The Internet uses a two level routing hierarchy: – Interior Routing Protocols, used by each network to determine how to reach all destinations that line within the network – Interior Routing protocols maintain the current topology of the network

124. Routing Architecture The Internet uses a two level routing hierarchy: – Exterior Routing Protocol, used to link each component network together into a single whole – Exterior protocols assume that each network is fully interconnected internally

125. Exterior Routing: BGP BGP is a large set of bilateral (1:1) routing sessions – A tells B all the destinations (prefixes) that A is capable of reaching – B tells A all the destinations that B is capable of reaching A A B B 10.0.0.0/24 10.1.0.0/16 10.2.0.0/18 192.2.200.0/24

126. What is RPKI? R esource P ublic K ey I nfrastructure Attaches digital certificates to network resources – AS Numbers – IP Addresses Allows ISPs to associate the two – Route Origin Authorizations (ROAs) – Can follow the address allocation chain to the top

127. What does RPKI accomplish? Allows routers or other processes to validate route origins Simplifies validation authority information – Trust Anchor Locator Distributes trusted information – Through repositories

128. Hierarchy of Resource Certificates

129. Route Origin Attestations 128.177.46.0/20 AS53659 128.177.0.0/16 AS17025 192.78.12.0/24 AS2000

130. Current Practices 128.177.0.0/16 AS17025 192.78.12.0/24 AS2000 128.177.46.0/20 AS53659

131. What does RPKI Create? It creates a repository – RFC 3779 (RPKI) Certificates – ROAs – CRLs – Manifest records

132. Relationships Parent Key Parent Cert Parent Manifest Signs Points to (has URI for) Certificate Key

133. AFRINICRIPE NCCAPNICARINLACNIC LIR1 ISP2 ISP ISP4ISP Issued Certificates Resource Allocation Hierarchy Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 ICANN Resource Cert Validation

134. AFRINICRIPE NCCAPNIC ARIN LACNIC LIR1 ISP2 ISP ISP4 ISP Resource Allocation Hierarchy Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 1. Did the matching private key sign this text? ICANN Issued Certificates Resource Cert Validation

135. AFRINICRIPE NCCAPNIC ARIN LACNIC LIR1 ISP2 ISP Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 ISP ISP4 2. Is this certificate valid? ISP Issued Certificates Resource Allocation Hierarchy ICANN Resource Cert Validation

136. AFRINICRIPE NCCAPNIC ARIN LACNIC LIR1 ISP2 ISP Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 Route Origination Authority “ISP4 permits AS65000 to originate a route for the prefix 192.2.200.0/24” Attachment: Signed, ISP4 ISP ISP4 ISP Issued Certificates Resource Allocation Hierarchy ICANN 3. Is there a valid certificate path from a Trust Anchor to this certificate? Resource Cert Validation

137. Repository View./ba/03a5be-ddf6-4340-a1f9-1ad3f2c39ee6/1: total 40 -rw-r--r-- 1 143 143 1543 Jun 26 2009 ICcaIRKhGHJ-TgUZv8GRKqkidR4.roa -rw-r--r-- 1 143 143 1403 Jun 26 2009 cKxLCU94umS-qD4DOOkAK0M2US0.cer -rw-r--r-- 1 143 143 485 Jun 26 2009 dSmerM6uJGLWMMQTl2esy4xyUAA.crl -rw-r--r-- 1 143 143 1882 Jun 26 2009 dSmerM6uJGLWMMQTl2esy4xyUAA.mnf -rw-r--r-- 1 143 143 1542 Jun 26 2009 nB0gDFtWffKk4VWgln-12pdFtE8.roa A Repository Directory containing an RFC3779 Certificate, two ROAs, a CRL, and a manifest

138. Repository Use Pull down these files using a manifest- validating mechanism Validate the ROAs contained in the repository Communicate with the router marking routes “valid”, “invalid”, “unknown” Up to ISP to use local policy on how to route

139. Possible Data Flow for Operations RPKI Web interface -> Repository Repository aggregator -> Validator Validated entries -> Route Checking Route checking results -> local routing decisions (based on local policy)

140. How you can use ARIN’s RPKI System? Hosted – create ROAs through ARIN Online – create ROAs using ARIN’s RESTful service Delegated using Up/Down Protocol

141. HostedRPKI - ARIN Online Pros – Easy to pick up and use – ARIN managed Cons – No current support for downstream customers to manage their own space – Tedious through the UI if you have a large network – We hold your private key

142. HostedRPKI - RESTful Interace Pros – Programmatic interface for large networks – ARIN managed Cons – No current support for downstream customers to manage their own space – We hold your private key

143. Delegated RPKI with Up/Down Pros – You safeguard your own private key – Follows the IETF up/down protocol Cons – Extremely hard to setup – Need to operate your own RPKI environment

144. Hosted RPKI in ARIN Online

148. SAMPLE-ORG

149. Hosted RPKI in ARIN Online SAMPLE-ORG

150. Hosted RPKI in ARIN Online

151. Your ROA request is automatically processed and the ROA is placed in ARIN’s repository, accompanied by its certificate and a manifest. Users of the repository can now validate the ROA using RPKI validators.

152. Delegated with Up/Down

155. You have to do all the ROA creation Need to setup a CA Have a highly available repository Create a CPS

156. RPKI Statistics ARIN XXX ARIN XXXI ARIN XXXII ARIN33ARIN34ARIN 35ARIN 36 RPAs Signed 2772130162208289358 Certified Orgs 4768108153187220 ROAs 1960106162239308338 Covered Resources 3082147258332430482 Up/Down Delegated 00012

157. Q&A

158. Moving to IPv6 Deb Martin, Senior Project Manager Jon Worley, Technical Services Manager

159. The Amazing Success of the Internet 2.92 billion users! 4.5 online hours per day per user! 5.5% of GDP for G-20 countries Time Just about anything about the Internet 159

160. The Original IPv6 Plan - 1995 IPv6 Deployment Time IPv6 Transition – Dual Stack IPv4 Pool Size Size of the Internet 160

161. The Revised IPv6 Plan - 2005 IPv6 Deployment 2004 IPv6 Transition – Dual Stack IPv4 Pool Size Size of the Internet 2006200820102012 Date 161

162. Oops! We were meant to have completed the transition to IPv6 BEFORE we completely exhausted the supply channels of IPv4 addresses! 162

163. Today’s Plan IPv6 Deployment IPv4 Pool Size Size of the Internet IPv6 Transition Today Time ? 0.8 % 163

164. Transition... The downside of an end-to-end architecture: – There is no backwards compatibility across protocol families – A V6-only host cannot communicate with a V4-only host We have been forced to undertake a Dual Stack transition: – Provision the entire network with both IPv4 AND IPv6 – In Dual Stack, hosts configure the hosts’ applications to prefer IPv6 to IPv4 – When the traffic volumes of IPv4 dwindle to insignificant levels, then it’s possible to shut down support for IPv4 164

165. Dual Stack Transition... We did not appreciate the operational problems with this dual stack plan while it was just a paper exercise: The combination of an end host preference for IPv6 and a disconnected set of IPv6 “islands” created operational problems – Protocol “failover” from IPv6 to IPv4 takes between 19 and 108 seconds (depending on the operating system configuration) – This is unacceptably slow Attempting to “bridge” the islands with IPv6-in-IPv4 tunnels created a new collection of IPv6 path MTU Discovery operational problems – There are too many deployed network paths containing firewall filters that block all forms of ICMP, including ICMP6 Packet Too Big Attempts to use end-host IPv6 tunneling also presents operational problems – Widespread use of protocol 41 (IP-in-IP) firewall filters – Path MTU problems 165

166. Dual Stack Transition Signal to the ISPs: – Deploy IPv6 and expose your users to operational problems with IPv6 connectivity Or – Delay IPv6 deployment and wait for these operational issues to be solved by someone else So we wait... 166166166

167. And while we wait... The Internet continues its growth. And without an abundant supply of IPv4 addresses to support this level of growth, the industry is increasingly reliant on NATs: – Edge NATs are now the de facto choice for residential broadband services at the CPE – ISP NATs are now the de facto choice for 3G and 4G mobile IP services 167

168. What is ARIN Hearing from the Community About IPv6? Movement to IPv6 is slow, but progress being made – ISPs slowly rolling out IPv6 – Steady increase in IPv6 traffic – Increase in IPv6 requests Still high demand for IPv4 – Many ISPs purchasing CGN boxes – More turning to the IPv4 market Rent by month Purchasing space outright (costs will increase) 168

169. Why is there little immediate need for IPv6? Some of the claims are either not true or taken over by events – IPv6 gives you better security – IPv6 gives you better routing Some positive things – IPv6 allows for end-to-end networking to occur again – IPv6 has more address bits – It is cheaper per address 169

170. 2003: Sprint T1 via Sprint Linux Router with Sangoma T1 Card OpenBSD firewall Linux-based WWW, DNS, FTP servers Segregated network, no dual stack (security concerns) A lot of PMTU issues A lot of routing issues Service did improve over the years 170

171. 2008: NTT / TiNet IPv6 1000 Mbit/s to NTT / TiNet Cisco ASR 1000 Router Brocade Load Balancers - IPv6 support was Beta DNS, Whois, IRR, more later Dual stack 171

172. Past Meeting Networks IPv6 enabled since 2005 Tunnels to ARIN, others Test bed for transition technology NAT-PT (Cisco, OSS) CGN / NAT-lite IVI Training opportunity For staff & members 172

173. ARIN’s Current Challenges for Networking Dual-Stacked Internally – Challenges over time with our VPN (OpenVPN) One interface works with v6 One does not Middleware Boxes – Claims do not support reality (“we support IPv6”) Yes, but… – No 1-1 feature set – Limits ARIN’s ability to support new services like https support for Whois-RWS 173

174. However, there is some good news… 174

175. US IPv6 Deployment > 25% of US customers connected to Google via IPv6 - up from 10% one year ago today & growing rapidly 175

176. The State of IPv6 Over 10% of the world uses facebook over IPv6 Over 10% 2015 1% 6/6/2012 176176176

177. Why Move to IPv6 Now? IPv4 depletion has occurred – Cost of IPv4 will only increase Lots more addresses and more! – IPv6 performs better than IPv4 – IPv6 is simpler operationally; not difficult to deploy More efficient network management - allows for end-to-end networking to occur again Designed with security in mind IPv6 is your platform for innovation 177

178. Your IPv6 Checklist Get your IPv6 address space Set up IPv6 connectivity (native or tunneled) Configure your operating systems, software, and network management tools Upgrade your router, firewall, and other hardware Get your IT staff training Enable IPv6 on your website 178

179. Talk to Your ISP About IPv6 Services You want access to the entire Internet! – ISPs must connect customers via IPv4 only, IPv4-IPv6, and IPv6 only – They must plan for IPv4-IPv6 transition services Many transition technologies available Research options and make architectural decisions 179

180. Dual-stack Your Network – IPv6 not backwards compatible with IPv4 – Both will run simultaneously for years 180

181. Make Your Servers Reachable Over IPv6 – Mail, Web, Applications – Operating systems, software, and network management tools 181

182. Audit Your Equipment and Software – Are your devices and applications IPv6 ready? 182

183. Encourage Vendors to Support IPv6 – If not already, when will IPv6 support be part of their product cycle? 183

184. Get IPv6 Training for Staff – Free resources available 184

185. Enable IPv6 on Your Website 185

186. Steps To Get Your Website IPv6- Enabled TeamARIN.net/get6 186

187. IPv6 over time ARIN IPv6 Allocations and Assignments 187

188. 2015 IPv6 Requests 188 ------- = waiting list initiated ------- = IPv4 depletion

189. ARIN ISP Members with IPv4 and IPv6 5,268 total members as of 31 January 2016 189

190. Global IPv6 Status Percentage of Members with IPv6 190

191. Requesting IPv6 - ISPs Have a previous v4 allocation from ARIN or predecessor registry OR Intend to multi-home OR Provide a technical justification which details at least 50 assignments made within 5 years 191

192. Data ARIN Will Typically Ask For - ISPs If requesting more than a /32, a spreadsheet/text file with – # of serving sites (PoPs, datacenters) – # of customers served by largest serving site – Block size to be assigned to each customer (/48 typical) 192

193. Requesting IPv6 – End Users Have a v4 direct assignment from ARIN or predecessor registry OR Intend to multi-home OR Show how you will use 2000 IPv6 addresses or 200 IPv6 subnets within a year OR Technical justification as to why provider- assigned IPs are unsuitable 193

194. Data ARIN Will Typically Ask For – End users If requesting more than a /48, a spreadsheet/text file with – List of sites in your network Site = distinct geographic location Street address for each – Campus may count as multiple sites Technical justification showing how they’re configured like geographically separate sites 194 37

195. 2015 Best Practices Forum (BPF) on IPv6 Adoption “Creating an Enabling Environment for IPv6 Adoption” Part of the Internet Governance Forum (IGF), a multi-stakeholder forum for policy dialogue on issues of Internet governance Project designed to document high level best practices for IPv6 adoption – Best practice examples collected via: Public survey running mid-July thru mid–November (results available on the IGF website) Mailing list discussion E-mail correspondence 38

196. Final IPv6 BPF Document Provides an overview of various capacity building programs that are available Highlights numerous examples and best practices that can help businesses and governments with their IPv6 deployment projects Large section of the document is dedicated to role and function of IPv6 task forces http://www.intgovforum.org/cms/documents/best-practice- forums/creating-an-enabling-environment-for-the-development-of- local-content/581-igf2015-bpfipv6-finalpdf/file196

197. Operational Guidance www.NANOG.org/archives/ http://nabcop.org/index.php/Main_Page 197 http://www.internetsociety.org/deploy360/ http://www.intgovforum.org/cms/best-practice-forums/2015-bpf-outs Internet Governance Forum – Enabling Environment for IPv6 Adoption

198. Learn More IPv6 Info Center www.arin.net/knowledge/ipv6_info_center.html www.GetIPv6.info www.TeamARIN.net 41

199. Q&A / Open Mic Session

200. Take Aways Apply for IPv6 addresses and get started. Subscribe to an ARIN mailing list Participate in ARIN 37 – in person or remotely Apply for a future meeting fellowship Think about implementing DNSSEC/Resource Certification Member organizations please update your Voting Contact – linked to an ARIN Web User account Reach out though various channels with questions or suggestions

201. ARIN Mailing Lists ARIN Consultation - arin-consult@arin.netarin-consult@arin.net Open to the general public. Used in conjunction with the ARIN Consultation and Suggestion Process (ACSP) to gather comments, this list is only open when there is a call for comments ARIN Issued - arin-issued@arin.netarin-issued@arin.net Read-only list open to the general public. Used by ARIN staff to provide a daily report of IPv4 and IPv6 addresses returned and IPv4 and IPv6 addresses issued directly by ARIN or address blocks returned to ARIN's free pool. ARIN Technical Discussions - arin-tech-discuss@arin.netarin-tech-discuss@arin.net Open to the general public. Provided for those interested in providing technical feedback to ARIN on experiences in the use or evaluation of current ARIN services and features in development. http://www.arin.net/participate/mailing_lists/index.html ARIN Announce: arin-announce@arin.net ARIN Discussion: arin-discuss@arin.net (members only)arin-discuss@arin.net ARIN Public Policy: arin-ppml@arin.net ARIN Consultation: arin-consult@arin.net ARIN Issued: arin-issued@arin.net ARIN Technical Discussions: arin-tech-discuss@arin.net Suggestions: arin-suggestions@arin.netarin-suggestions@arin.net

202. ARIN on Social Media www.TeamARIN.net www.facebook.com/TeamARIN @TeamARIN www.gplus.to/TeamARIN www.linkedin.com/company/ARIN www.youtube.com/TeamARIN

203. https://www.arin.net/participate/meetings/fellowship.html