3. ARIN and the Regional Internet Registry (RIR) System Leslie Nobile Director of Registration Services

4. What is an RIR? An RIR is an organization that manages the allocation and registration of Internet number resources within a particular region of the world. Internet number resources include IP addresses and autonomous system (AS) numbers.

5. Regional Internet Registries

6. 1993 IR function contracted by NSF to NSI; InterNIC formed, DoD oversight ends. APNIC formed.   Registrant 1992 RFC 1366: Regional IRs established; RIPE NCC formed   Registrant 1991 RFC 1261: DoD IR function contract moved to Network Solutions, Inc.   Registrant 1980s Internet Registry (IR) function contracted by DoD to SRI International   Registrant 1980s NSFNET/ARPANET - Jon Postel managed addressing via DoD contract; this was called the Internet Assigned Numbers Authority (IANA)  Registrant Government Oversight Historical Timeline DDN NIC InterNIC

7. Historical Timeline 2005 Regionalization complete; AfriNIC formed   Registrant 2002 Regionalization continues; LACNIC formed   Registrant 1998 ICANN formed by US Gov’t (top level technical coordination)   Registrant 1997 IR regionalization continues; ARIN formed. USG oversight of IR function ends.   Registrant Community Oversight

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. Number ResourcesOrganizationPolicy Development IP address allocation & assignment ASN assignment Directory services WHOIS IRR Reverse DNS Elections Meetings Information dissemination Website Newsletters Roundtables Training Maintain email discussion lists Conduct public policy meetings Publish policy documents RIR Services

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. Who Provisions IP Addresses and ASNs? ICANN IANA Top level technical coordination of the Internet (Names, Numbers, Root Servers) Manage global unallocated IP address pool Allocate number resources to RIRs RIR Manage regional unallocated IP address pool Allocate number resources to ISPs/LIRs Assign number resources to End-users ISP/LIR Manage local IP address pool for use by customers and for infrastructure Allocate number resources to ISPs Assign number resources to End-users

12. Number Resource Provisioning Hierarchy ICANN / IANA (Internet Assigned Numbers Authority) Manage global unallocated IP address pool ISPs End Users ISPs RIRs (AfriNIC, APNIC, ARIN, LACNIC, RIPE NCC) Manage regional unallocated IP address pool Re-AllocateRe-Assign End Users Allocate AssignAllocate

13. "Applying the principles of stewardship, ARIN, a nonprofit corporation, allocates Internet Protocol resources; develops consensus- based policies; and facilitates the advancement of the Internet through information and educational outreach."

14. About ARIN One of five Regional Internet Registries (RIRs) Established December 1997 Provides services related to the technical coordination and management of Internet number resources Services the US, Canada, and 22 economies in the Caribbean Is a non-profit, community-based organization governed by a member-elected executive board

15. ARIN’s Service Region ARIN’s region includesCanada, many Caribbean and North Atlantic islands, and the United States.

16. ARIN’s Core Services Like the other RIRs, ARIN: – Allocates and assigns Internet number resources – Maintains Whois, in-addr.arpa, and other technical services – Facilitates policy development – Provides training, education and outreach – Participates in the global Internet community

17. ARIN on Social Media Facebook – www.facebook.com/TeamARIN Twitter – www.twitter.com/TeamARIN LinkedIn – www.linkedin.com YouTube – www.youtube.com/TeamARIN

18. Q&A

19. David Huberman Technical Specialist Requesting and Managing Internet Number Resources

20. Overview Request and Manage Number Resources – Recently Added ARIN Online Functionality – RESTful Provisioning Recently Implemented Policies Status of IPv4 Future Services

22. Major Changes in Functionality 1)Reverse DNS Zone Management 2)DNSSEC 3)Resource Requests 4)POC Validation 5)View Invoices

23. Reverse DNS All reverse zones managed individually now All zone management takes place inside ARIN Online or via REST calls (no templates!)

24. Reverse DNS in ARIN Online

26. 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.

27. Reverse DNS ARIN issues blocks without any working DNS – Must establish delegations after registration

28. Reverse DNS Authority to manage reverse zones follows SWIP – “Shared Authority” model

29. Reverse DNS - Shared Authority Joe’s Bar and Grill has reassigned a /24 to HELLO WORLD. Both can manage the /24 zone.

30. DNSSEC Same interface as reverse DNS DS records generated by user Zone must have nameservers before you can add DS records

31. 1)Paste DS Record 2)Parse DS Record 3)Apply

32. Requesting IP addresses & ASNs Via ARIN Online only Officer attestation for IP requests now done via a signed form (instead of email) Can no longer specify resource POCs or reverse DNS delegation in request

33. Annual POC Validation Annual validation of each POC handle required (NRPM 3.6) If an ARIN Online account is linked to any POC that has been unvalidated for 60+ days, the system forces validation by preventing the account from performing normal actions.

34. View Invoices Can now view paid and open invoices via ARIN Online Goes back 2 years Available to Admin, Tech, and Billing POC

35. Template Changes Resource request templates deprecated Transfers and SWIPs still done with templates API key required to authorize processing – Generated via ARIN Online – https://www.arin.net/features/api_keys.ht ml https://www.arin.net/features/api_keys.ht ml

36. RESTful Interface Programmatic way to interact with ARIN – Intended to be used for automation – Not meant to be used by humans Useful for ISPs that manage a large number of SWIP records Requires an investment of time to achieve those benefits

37. Example – Reassign Detailed Your automated system issues a PUT call to ARIN using the following URL: https://www.arin.net/rest/net/NET-10-129-0-0-1/reassign?apikey=API-1234-5678-9ABC-DEFG The call contains the following data: 4 HW-1 A Reassigned 10.129.0.0 10.129.0.255 24 NET-10-129-0-0-1 HELLOWORLD

38. Example – Reassign Detailed ARIN’s web server returns the following to your automated system: 4 Tue Jan 25 16:17:18 EST 2011 HW-1 NET-10-129-0-0-2 A Reassigned 10.129.0.0 10.129.0.255 24 NET-10-129-0-0-1 netName>HELLOWORLD Reg date and net handle added

39. Other RESTful Notes IPv6 Reassign Simple available only through the RESTful interface Still operating RESTful beta site as a test bed – Must request access

40. Obtaining RESTful Assistance ARIN Online’s ASK ARIN feature arin-tech-discuss mailing list – Make sure to subscribe – Someone on the list will help you ASAP Registration Services Help Desk telephone not a good fit – Debugging these problems requires a detailed look at the method, URL, and payload being used

41. Recently Implemented Policies

42. 3 Month Supply For ISPs Prior to IANA IPv4 exhaustion, experienced ISPs could get a 12 month supply Dropped to 3 month supply immediately upon IANA exhaustion Still computed based on demonstrated utilization rate

43. IPv6 End-user Changes Before: Block size based on HD-Ratio – Complex (used logarithms) After: Block size based solely on number of sites within a network Number of SitesBlock Size Justified 1/48 2-12/44 13-192/40 193-3,072/36 3,073-49,152/32

44. Results of End-user Policy Change Small uptick in large blocks, but majority still /48 Prefix Length% of assignments in the year prior to new policy % of assignments since new policy implemented /32-/350.35%2.14% /36-/391.04%5.00% /40-/436.60%7.14% /44-/4715.97%17.86% /4876.04%67.86%

45. Better IPv6 Allocation for ISPs To be implemented no later than 15 February 2012 Allows ISPs to have uniform subnets – Each “serving site” gets a block large enough to number the largest serving site – Must be nibble-aligned: /48, /44, /40, etc

46. Example An ISP has 37 PoPs – The largest PoP has 1,084 customers – Wants to assign a /48 to each customer /37 smallest block that has 1,084 /48s (2,048) Each of the 37 PoPs gets a /36 (round to nibble) Smallest block that contains 37 /36s is a /30 (64 /36s) ISP A gets a /28 (round to nibble)

47. Standardize IP Reassignment Registration Requirements To be implemented by 30 September 2011 Abuse contact will be required for all ORGs New policies for ISPs with residential customers that dynamically draw IP addresses from pools – must submit SWIP information for each market area – must show 80% assigned with a 50-80% utilization rate across markets IPv6 /64 and larger static reassignments must be visible via SWIP/RWhois

48. IPv6 Subsequent Allocations for Transitional Technologies ISPs with an initial allocation for native IPv6 can request a separate block to be used for IPv4 -> IPv6 transitional technology – 6rd is the most common example, but the policy doesn’t specify a technology /24 maximum allocation – Allows a typical ISP to map a /56 to each of their existing IPv4 addresses in a 6rd deployment

49. Simplified M&A Transfers If resources are no longer justified, ARIN will work with you to get back into compliance If resources are underused, ARIN will work with you on a plan to regain compliance via growth or return

50. Status of IPv4 at ARIN

51. IPv4 Holdings Profile 1.5% of the subscriber Org IDs hold 80% of the non-legacy IPv4 addresses The remaining 98.5% of the Org IDs hold 20% of the non-legacy IPv4 addresses

52. Inventory Report IANA IPv4 free pool now exhausted – ARIN received its last /8 from IANA in mid- February At that time, ARIN had ~5.49 /8 equivalents in its available pool Daily inventory published on ARIN’s website

53. Inventory updated daily @ 8PM ET

54. The Obvious Question How long will ARIN’s IPv4 inventory last? ARIN doesn’t make projections Why not? – Past performance doesn’t always predict the future – Potential game-changing requests – Projections are interpreted as assurances of availability

55. The Reality – We Have No Idea Network operators may: – become more efficient – continue to consume at the same rate – consume at a faster rate IPv4 availability cannot be guaranteed because IPv4 free pool exhaustion cannot be accurately predicted

56. Post-Depletion World While availability of IPv4 addresses cannot be assured, there will be ways network operators may be able to obtain additional IPv4 addresses – Transfers to Specified Recipients – Specified Transfer Listing Service (STLS) – Waiting List for Unmet IPv4 Requests

57. Transfers to Specified Recipients Resources no longer required to be under RSA If resources are not maintained under RSA, verification of title may take some time Attestation from officer required if resources not under LRSA/RSA RSA coverage = smoother transfer

58. STLS Listers: have available IPv4 addresses Needers: looking for more IPv4 addresses Facilitators: available to help listers and needers find each other

59. Waiting List for Unmet IPv4 Requests Policy initiative Starts when ARIN can’t fill a justified request Option to specify smallest acceptable size If no block available between approved and smallest acceptable size, option to go on the waiting list May receive only one allocation every three months

60. Future ARIN Services

61. Future Services RPKI in development – Cryptographically authenticate registration authority Routing registry changes – Better authentication (currently use only mail-from) Increased functionality in ARIN Online

62. Q&A

63. ARIN Value-Added Trust Services Update Mark Kosters Chief Technology Officer

64. Agenda DNSSEC – a brief update RPKI – the major focus – What is it? – What it will look like within ARIN Online?

65. Why are DNSSEC and RPKI Important? Two critical resources – DNS – Routing Hard to tell when resource is compromised Focus of Government funding - DHS

66. What is DNSSEC? DNS responses are not secure – Easy to Spoof – Examples of malicious attacks DNSSEC attaches signatures – Validates responses – Can not Spoof

67. Changes Required to make DNSSEC work Transfer of in-addr.arpa to ICANN Moving Nameservers for in-addr.arpa from the roots to RIR-managed systems Signing in-addr.arpa, ip6.arpa and delegations that ARIN manages Provisioning of DS Records – ARIN Online – RESTful Interface (just deployed on July 23)

68. Traffic from a.in-addr-servers.arpa

69. Demo Movie from https://www.arin.net/knowledge/dnss ec/ https://www.arin.net/knowledge/dnss ec/ 69 of 23

70. RPKI Pilot Available since June 2009 – http://rpki-pilot.arin.net http://rpki-pilot.arin.net – ARIN-branded version of RIPE NCC software 46 organizations participating #2 (behind RIPE) on prefixes/roas

71. What is RPKI? Attaches certificates to network resources – AS Numbers – IP Addresses Allows ISPs to associate the two – Route Origin Authorizations (ROAs) – Follow the allocation chain to the top

72. What is RPKI? Allows routers to validate Origins Start of validated routing Need minimal bootstrap info – Trust Anchors – Lots of focus on Trust Anchors

73. What does RPKI Create? It creates a repository – RFC 3779 Certs – ROAs – CRLS – Manifest records – Ghostbusters support

74. Repository View./ba/03a5be-ddf6-4340-a1f9-1ad3f2c39ee6/1: total 40 -rw-r--r-- 1 markk markk 1543 Jun 26 2009 ICcaIRKhGHJ- TgUZv8GRKqkidR4.roa -rw-r--r-- 1 markk markk 1403 Jun 26 2009 cKxLCU94umS- qD4DOOkAK0M2US0.cer -rw-r--r-- 1 markk markk 485 Jun 26 2009 dSmerM6uJGLWMMQTl2esy4xyUAA.crl -rw-r--r-- 1 markk markk 1882 Jun 26 2009 dSmerM6uJGLWMMQTl2esy4xyUAA.mnf -rw-r--r-- 1 markk markk 1542 Jun 26 2009 nB0gDFtWffKk4VWgln- 12pdFtE8.roa

75. Repository Use Pull down these files using “rcynic” 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

76. Possible Flow RPKI web interface -> repository Repository aggregator -> validator Validated entries -> route checking Route checking results -> local routing decisions (based on local policy) 76 of 23

77. Resource Cert Validation AFRINICRIPE NCCAPNICARINLACNIC LIR1ISP2 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 IANA

78. Resource Cert Validation AFRINICRIPE NCCAPNICARINLACNIC LIR1NIR2 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 1. Did the matching private key sign this text? IANA

79. Resource Cert Validation AFRINICRIPE NCCAPNICARINLACNIC LIR1ISP2 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 2. Is this certificate valid? IANA

80. Resource Cert Validation AFRINICRIPE NCCAPNICARINLACNIC LIR1ISP2 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 IANA 3. Is there a valid certificate path from a Trust Anchor to this certificate?

81. Why is RPKI taking awhile? Intense review of liabilities by legal team and Board of Trustees created additional requirements at ARIN XXVI Two new big requirements – Non-repudiation in ROA generation for hosted CAs – Thwart “Evil Mark” (rogue employee) from making changes

82. General Architecture of RPKI Registration Interface ARIN Online Database Persistence RPKI Engine HSM Tight coupling between resource certificate/ROA entities and registration dataset at the database layer. Once certs/ROAs are created, they must be maintained if the registered dependents are changed.

83. Development before ARIN XXVI ARIN Online Database Persistence RPKI Engine HSM With a few finishing touches, ready to go Jan 1, 2011 with Hosted Model, Delegated Model to follow end of Q1. Highly influenced by RIPE NCC entities. RIPE NCC RPKI Engine with a few tweaks. Sun SCA 6000 Everything is Java, JBoss, Hibernate.

84. Changes Underway Since ARIN XXVI ARIN Online Database Persistence RPKI Engine HSM Minor changes. Message driven engine which delegates to the HSM. Custom programming on IBM 4764’s to enable all DER encoding and crypto. In-browser ROA request signing via AJAX. HSM coding is in C as extensions to IBM CCA. Libtasn1 used for DER coding.

85. Example – Creating an ROA

91. Updates within RPKI outside of ARIN The four other RIRs are in production with Hosted CA services Major routing vendor support being tested Announcement of public domain routing code support

92. ARIN Status Hosted CA anticipated by end of October at the earliest We intend to add up/down code required for delegated model after Hosted CA completed

93. Why is this important? Provides more credibility to identify resource holders Helps in the transfer market identify real resource holders Bootstraps routing security

94. Q&A

96. Current Status of IPv4 and IPv6 in the ARIN region Leslie Nobile Director of Registration Services

97. IPv4 Depletion Situation Report Each RIR received its last /8 from IANA on 3 February 2011 The IANA free pool of IPv4 addresses has reached 0% While each RIR currently has IPv4 addresses to allocate, it is impossible to predict when each RIR will run out ARIN publishes an inventory of available IPv4 addresses, updated daily, at www.arin.net

98. IPv4 Churn ARIN does get back IPv4 addresses through returns, revocations, and reclamations – Return = voluntary – Revoke = for cause (usually nonpayment) – Reclaimed = fraud or business dissolution From 1/1/2005 to 3/31/2011, ARIN got ~585 /16 equivalents back

99. **Feb 3, 2011- IANA depletion

103. IPv4 vs IPv6 Subscribers 3,711 IPv4 ISP subscribers today – 2,478 (67%) do not have an IPv6 allocation. *as of Aug 1, 2011

104. IPv4 & IPv6 - The Bottom Line IPv4 is depleting quickly; IPv6 must be adopted for continued Internet growth IPv6 is not backwards compatible with IPv4; for the foreseeable future, the Internet must run both IP versions (IPv4 & IPv6) at the same time Deployment is already underway: Today, there are organizations attempting to reach your mail, web, and application servers via IPv6…

105. Who Are the Players in the Transition to IPv6? Broadband Access Providers Internet Service Providers Internet Content Providers Enterprise Customers Equipment Vendors Government Organizations

106. IPv6 Adoption Needs IPv6 address space IPv6 connectivity (native or tunneled) Operating systems, software, and network management tool upgrades Router, firewall, and other hardware upgrades IT staff and customer service training

107. Resources – Community Use Slide Deck – IPv6 Wiki www.getipv6.info www.getipv6.info – Information Page at www.arin.net/knowledge/v4-v6.html www.arin.net/knowledge/v4-v6.html – Outreach Microsite: www.TeamARIN.net www.TeamARIN.net – Social Media at ARIN www.arin.net/social.html www.arin.net/social.html – ARIN Board Resolution – Letter to CEOs

108. Q&A

109. ARIN’s Policy Development Process

110. Policy Development Process (PDP) Flowchart Proposal Template Archive Movie https://www.arin.net/policy/pdp.html

111. Policy Development Principles Open – Developed in open forum Public Policy Mailing List Public Policy Meetings – Anyone can participate Transparent – All aspects documented and available on website Policy process, meetings, and policies Bottom-up – Policies developed by the community – Staff implements, but does not make policy

112. Who Plays a Role in the Policy Process? Community – Submit proposals – Participate in discussions and petitions Advisory Council (elected volunteers) – Facilitate the policy process – Develop policy that is “clear, technically sound and useful” – Determine consensus based on community input

113. Roles… ARIN Board of Trustees (elected volunteers) – Provide corporate fiduciary oversight – Ensure the policy process has been followed – Ratify policies ARIN Staff – Provide feedback to community Staff and legal assessments for all proposals Policy experience reports – Implement ratified policies

114. Basic Steps 1.Community member submits a proposal 2.Community discusses the proposal on the “List” 3.AC creates a draft policy or abandons the proposal 4.Community discusses the draft policy on the “List” and at the meeting 5.AC conducts its consensus review 6.Community performs last call 7.Board adopts 8.Staff implements

115. Petitions Anyone dissatisfied with a decision by the AC can petition in order to keep a proposal moving forward – Occurs between proposal and draft policy stage – 5 day petition period – Needs 10 different people from 10 different organizations to publicly support the petition *8 petitions to date

116. Number Resource Policy Manual NRPM is ARIN’s policy document – Version 2011.3 (27 July 2011) – This is the 23rd version Contains Change Logs Available as PDF Index https://www.arin.net/policy/nrpm.html

117. Policies in the NRPM IPv4 Address Space IPv6 Address Space Autonomous System Numbers (ASNs) Directory Services (WHOIS) Reverse DNS (in-addr) Transfers Experimental Assignments Resource Review Policy

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

119. Current Policy Discussions Draft Policies and Proposals: Changes to Number Policy

120. Current Draft Policies and Proposals 4 Active Draft Policies 9 Policy Proposals

121. Draft Policies ARIN-2011-1: Globally Coordinated Transfer Policy – Would allow transfers to/from the ARIN region The two RIRs must have compatible transfer policy Need required (transfers are needs-based) ARIN-2011-5: Shared Transition Space for IPv4 Address Extension – Creates an IPv4 /10 to be shared (eg. draft- shirasaki-nat444-03 ) – Under Board review. Board asked ARIN to work with the IETF/IAB.

122. Draft Policies (cont.) ARIN-2011-7: Compliance Requirement – Ensures that ISPs maintain accurate reassignment information Enforcement via stopping reverse DNS services and possibly revocation ARIN-2011-8: Combined M&A and Specified Transfers – Clarifies that organizations can perform both types of transfers at roughly the same time

123. Proposals ARIN-prop-137 Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA – Instructs IANA to accept returned address space and reissue that space to the RIRs (a 1/5 th portion to each RIR every 6 months)

124. Proposals (cont. 1) ARIN-prop-144 Remove Single Aggregate Requirement from Specified Transfer – Removes “aggregate” language from the transfer policy (opposite of prop-153) ARIN-prop-146 Clarify Justified Need for Transfers – Extends the 12-month supply period for address space to all specified transfers ARIN-prop-147 Set Transfer Need to 24 months – Lengthens the supply period for specified transfers to 24 months

125. Proposals (cont. 2) ARIN-prop-149 Improved Transparency for Directed Transfers – Requires ARIN to publish a list of prefixes transferred via the policy for transfers to specified recipients ARIN-prop-151 Limiting Needs Requirements for IPv4 Transfers – Removes the needs-based evaluation from transfers to specified recipients

126. Proposals (cont. 3) ARIN-prop-152 RSA Modification Limits – “This policy serves to provide guidelines and set limits on the extent to which an RSA can be modified to meet the needs of a transfer.” ARIN-prop-153 Correct Erroneous Syntax in NRPM 8.3 – Changes the transfer policy so that only a single aggregate could be transferred (opposite of prop 144)

127. Proposals (cont. 4) ARIN-prop-155 IPv4 Number Resources for Use Within Region – “ IPv4 addresses are issued solely for use in networks within the ARIN region.” – Applies to new requests after it’s implemented

128. How Can You Get Involved? There are two methods to voice your opinion: – Public Policy Mailing List – Public Policy Meeting (in person or remote)

129. ARIN Meetings Two meetings a year Check the ARIN Public Policy Meeting site 4- 6 weeks prior to meeting – Proposals/Draft Policies on Agenda – Discussion Guide (summaries and text) – Attend in Person/ Remote Participation AC meeting last day – Watch list for AC’s decisions – Last Calls – For or against?

130. Public Policy Mailing List (PPML) Open to anyone Easy to subscribe to Contains: ideas, proposals, draft policies, last calls, announcements of adoption and implementation, and petitions Archives available RSS feed available https://www.arin.net/participate/mailing_lists/index.html

131. References Draft Policies & Proposals – https://www.arin.net/policy/proposals/index.html https://www.arin.net/policy/proposals/index.html ARIN Public Policy Mailing List – https://www.arin.net/participate/mailing_lists/index.html https://www.arin.net/participate/mailing_lists/index.html

132. Q&A

133. The Importance of Participating in the ARIN Community

134. Learn More and Get Involved Your participation Important, critical, needed, appreciated… Get Involved in ARIN Public Policy Mailing List ARIN Suggestion and Consultation Process Member Elections Public Policy and Member’s Meetings http://www.arin.net/participate/

135. 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. https://www.arin.net/participate/mailing_lists/index.html ARIN Announce - arin-announce@arin.net ARIN Discussion – 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

136. ARIN Consultation and Suggestion Process Open for business September 2006 As of 31 March 2011 – 14 community consultations all closed https://www.arin.net/participate/acsp/acsp_consultations.html – 127 suggestions 16 remain open https://www.arin.net/participate/acsp/acsp_suggestions.html

137. Board of Trustees Advisory Council NRO Number Council General Member Eligibility Date ( 2011 Elections) : 01 January Board, AC, and NRO Number Council Call for Nominations: 25 July-24 August Deadline to Establish Voter Eligibility: 27 September Board, AC, and NRO NC Final Candidates Announced: 30 September Elections held: 12 – 22 October Three year terms begin: 01 January

138. Next ARIN Meetings Remote participation Policy discussions Tutorials Social event Adjacent to NANOG https://www.arin.net/participate/meetings Apply for the ARIN XXVIII – Philadelphia fellowship by 26 August 2011

139. Q&A