1 / 155

Winnipeg 11 September 2014

Winnipeg 11 September 2014. Welcome. Here today from ARIN…. Paul Andersen , ARIN Board of Trustees – Vice Chair and Treasurer Susan Hamlin, Director, Communications and Member Services Andy Newton, Chief Engineer Leslie Nobile , Director, Registration Services

larissa-vang
Download Presentation

Winnipeg 11 September 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Winnipeg 11 September 2014

  2. Welcome. Here today from ARIN… • Paul Andersen, ARIN Board of Trustees – Vice Chair and Treasurer • Susan Hamlin, Director, Communications and Member Services • Andy Newton, Chief Engineer • Leslie Nobile, Director, Registration Services • John Sweeting, Advisory Council Chair

  3. Local speakers • Ron Dallmeier, R&D Technologies • Jacque Latour, CIRA • Bill Reid, MBIX • Sean Wallberg ,ERTW

  4. Today’s Agenda • Welcome and Getting Started • ARIN: Mission, Role, and Services • Obtaining IP Addresses: IPv4 Inventory, Countdown Plan • Automating Interactions with ARIN using REST • IPv4 Waiting List and Transfers • Using RPKI to Secure Routing • Lunch (12:00 to 1:00) upstairs in West Ballroom

  5. Today’s Agenda – after lunch • Obtaining IPv6 Address Space • Current Number Resource Policy Discussions and How to Participate • IPv6 Tutorial • Break (3:00 – 3:15) • How to Add DNSSEC to your ARIN Records • Manitoba Internet Exchange Update • Q&A and Open Microphone • Beers and Peers

  6. ARIN: Mission, Role and Services Paul Andersen Vice Chair and Treasurer ARIN Board of Trustees

  7. ”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."

  8. ARIN’s Service Region ARIN’s region includes many (20) Caribbean and North Atlantic islands, Canada and the United States and outlying areas.

  9. Regional Internet Registries

  10. Who Provisions IP Addresses & ASNs?

  11. ARIN Structure: • Not-for-profit • Fee for services, not number resources • 100% community funded • Membership organization (private and public sector, civil society) • Member-elected Board of Trustees • Community regulated…Internet number resource policies developed by the Community • Open and transparent

  12. ARIN Support Organization

  13. ARIN Services

  14. Information on Joining in the Internet Governance Discussion https://www.arin.net/participate/governance/participate.html Visit ARIN’s webpage: Ways to Participate in Internet Governance

  15. ARIN Community Input • 14 March 2014 the US government announced desire to transition oversight of the Internet Assigned Numbers Authority (IANA) functions contract from the National Telecommunications and Information Administration (NTIA) to the global multistakeholder community. • Coordination Group formed to facilitate the transition process – input from the Number Resource Organization , Address Supporting Organization, ISOC, IETF, IAB • All RIRs will engage their respective communities • ARIN 34 in Baltimore – on agenda and a likely consultation via email on the issue http://teamarin.net/education/internet-governance/iana-globalization/

  16. Participate in ARIN Contribute your Opinions and Ideas: • Public Policy Mailing List • IPv6 Wiki • Attend Public Policy and Members Meetings, Public Public Policy Consultations– remote participation • Outreach events • Submit a suggestion • Participate in community consultations • Write a guest blog – TeamARIN.net • Members – Vote in annual elections

  17. ARIN Mailing Lists ARIN Consultation - arin-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.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.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. ARIN Mailing Lists ARIN Announce: arin-announce@arin.net ARIN Discussion: arin-discuss@arin.net (members only) 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.net http://www.arin.net/participate/mailing_lists/index.html

  18. ARIN’s IPv4 Inventory, Depletion Projections, and Countdown Plan Leslie Nobile Director, Registration Services

  19. ARIN’s IPv4 Inventory As of 2 Sept 2014, ARIN has 0.76 /8 equivalents of IPv4 addresses remaining IPv4 inventory published on ARIN’s website: www.arin.net Updated daily @ 8PM ET

  20. Prefix Length Breakdown

  21. IPv4 Annual Burn Rate

  22. ARIN’s IPv4 Free Pool

  23. Linear Depletion Projection

  24. “Run On The Bank” Projection

  25. Which Projection is More Likely? • Probably somewhere in the middle, but it only takes one unexpected very large request (e.g. /10) to change things completely • Policy requirement to only fill requests with one block will prevent large ISPS from depleting all of the small blocks

  26. IPv4 Countdown Plan

  27. IPv4 Countdown Plan – Phase 4 • Started at 1 /8 equivalent left • All IPv4 requests team-reviewed and processed on a first in, first out basis • Org has 60 days from approval to complete payment and RSA • IPv4 hold period drops to 2 months

  28. New IPv4 Policy – “Reduce All Minimum Allocation/Assignment Units to /24” • Will be implemented on 17 Sept 2014 • /24 minimum allocation/assignment • No longer a multi-homed requirement

  29. Minimum Requirements for IPv4 - ISPs • ISPs qualify for a /24 by having one /24 reassigned and efficiently used • Allocations > /24 based on demonstrated utilization history and renumbering (if applicable) • Allocation size not based on predicted customer base (see Slow Start policy NRPM 4.2.1.4) • 3 month supply per policy

  30. IPv4 ISP Data Typically Requested • Static: Mapping of static IPs/subnets to customer names and street addresses • Dynamic: List of all dynamic pools with prefix/range assigned, area served (location), peak util % • Internal Infrastructure: Mapping of internal subnets with description and # IPs used

  31. Example

  32. Other IPv4 ISP Data Requested • Typically ask for: • Customer justification data • If necessary, may ask for: • Customer contact information and proof of customer payments • Proof of equipment lease/purchase

  33. Minimum Requirements for IPv4 – End Users • /24 minimum assignment size • Show 25% immediate utilization rate (within 30 days) and 50% projected one-year utilization rate • If requesting additional assignment, must show that each previous assignment is 80% utilized

  34. IPv4 End User Data Requested • Subnet mapping for previous ARIN assignments • Each subnet with description and # IPs currently used • Planned subnet mapping for requested block • Each subnet with description, # IPs used within 30 days, # IPs used within one year

  35. Example

  36. The Bottom Line • ARIN has v4 space today, but can’t guarantee future availability • Plan appropriately to ensure continued growth of your network • Waiting List • Specified Recipient Transfers • IPv6

  37. Automating Your Interactions with ARIN Andy Newton Chief Engineer

  38. Why Automate? • Interact with ARIN faster • Not dependent on ARIN’s systems for user interface issues • Build a customized system using standards-based technologies • Improved accuracy • Integrate multiple services

  39. Why Automate (continued) • We have a rich set of interfaces • Focused on reliability and completeness • Welcome to share your tools with the community at projects.arin.net

  40. REST – Service Summary • ARIN’sRESTful Web Services (RWS) • Whois-RWS • Provides public Whois data via REST • Reg-RWS (or Registration-RWS) • Allows ARIN customers to register and maintain data in a programmatic fashion • Report Request/Retrieval Automation • Permits request and download of various ARIN data (subject to AUP) • RPKI using Reg-RWS

  41. 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, …

  42. 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, …

  43. What does it look like?Who can use it? Where the data is. What type of data it is. The ID of the data. http://whois.arin.net/rest/poc/KOSTE-ARIN It is a standard URL. Anyone can use it. Go ahead, put it into your browser.

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

  45. Whois-RWS • Publicly accessible, just like traditional Whois • Searches and lookups on IP addresses, AS numbers, POCs, Orgs, etc… • Very popular • As of September 2013, constitutes 65% of our query load • For more information: • http://www.arin.net/resources/whoisrws/index.html

  46. Registration RWS (Reg-RWS) • 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

  47. Reg-RWS • Requires an API Key • You generate one in ARIN Online on the “Web Account” page • Permits you to register and manage your data (ORGs, POCs, NETs, ASes) • But only your data • More information • http://www.arin.net/resources/restful-interfaces.html

  48. Anatomy of a RESTful request • Uses a URL (just like you would type into your browser) • Uses a request type, known as a “method”, of GET, PUT, POST or DELETE • Usually requires a payload • Adheres to a published structure • Depends upon the type of data • Depends upon the method • Method, Payload, and XML schema info is found at “RESTful Provisioning Downloads”

  49. Example – Reassign Detailed • Your automated system issues a PUT command to ARIN using the following URL: http://www.arin.net/rest/net/NET-10-129-0-0-1/reassign?apikey=API-1234-5678-9ABC-DEFG <net xmlns="http://www.arin.net/regrws/core/v1" >      <version>4</version>      <comment></comment>      <registrationDate></registrationDate>      <orgHandle>HW-1</orgHandle>      <handle></handle>      <netBlocks>            <netBlock>                  <type>A</type>                  <description>Reassigned</description>                  <startAddress>10.129.0.0</startAddress>                  <endAddress>10.129.0.255</endAddress>                  <cidrLength>24</cidrLength>            </netBlock>      </netBlocks>      <parentNetHandle>NET-10-129-0-0-1</parentNetHandle>      <netName>HELLOWORLD</netName>      <originASes></originASes>      <pocLinks></pocLinks></net> The payload contains the following data:

More Related