1 / 172

Welcome to the IP Tutorial

Welcome to the IP Tutorial. 26 January 2001 RIPE Network Co-ordination Centre <training@ripe.net> http://www.ripe.net/ripe/meetings/archive/ripe-37/presentations/lir-tutorial/. Schedule. Requesting Address Space Introduction to RIPE NCC Global Registry System

rasul
Download Presentation

Welcome to the IP Tutorial

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. Welcome to theIP Tutorial 26 January 2001 RIPE Network Co-ordination Centre <training@ripe.net> http://www.ripe.net/ripe/meetings/archive/ripe-37/presentations/lir-tutorial/

  2. Schedule • Requesting Address Space • Introduction to RIPE NCC • Global Registry System • Initial Administrivia of Becoming LIR • First Request • Completing the request form • Communication with hostmasters • Customer’s Request • Elementary evaluation • RIPE Database • Evaluation of specific assignment cases • Large request • PI request • Renumbering • Assignment Window • New allocation • IPv6

  3. Introduction to RIPE NCC

  4. What is the RIPE NCC? • Network Co-ordination Centre • The RIPE NCC is a “co-ordination” and support service for its members and RIPE community • One of 3 Regional Internet Registries (RIR) • Why a NCC ? Actions agreed in RIPE community needed • continuity and professionalism • neutrality and impartiality

  5. RIPE NCC History • Birth - April 1992 • TERENA legal umbrella • BecameRIR in September 1992 • Contributing LIRs in 1995 • In 1998 independent • A new structure (ripe-161) • not-for-profit association • General Assembly of all members • Executive Committee of elected nominees

  6. Formal Decision Making “Consensus” Model RIPE proposes activity plan RIPE NCC proposes budget to accompany activity plan (ripe-213) General Assembly votes on both activities and budget at yearly meeting

  7. Vital Statistics • Statistics 1992 • 3 staff members • No Local IR’s • 182,528 hosts in European Internet • 7,955 objects in RIPE database (June ‘92) • Statistics Now • 67 staff (22 nationalities) • 2,526+ participating Local IR’s • 12,088,135+ countable hosts in the RIPE NCC region • 3,537,049+ objects in the database

  8. RIPE NCC Member Services • Registration Services • IPv4 addresses • IPv6 addresses • AS numbers • LIR Training Courses • <hostmaster@ripe.net> • Reverse domain name delegation • NOT registering domain names • Test Traffic Measurements

  9. RIPE NCC Public Services • RIPE whois database maintenance • Routing Registry Maintenance (RR) • Co-ordination • RIPE support • Liaison with: • LIRs / RIRs / ICANN / etc … • Information dissemination • Maintenance of tools • http://www.ripe.net/ripencc/mem-services/tools/index.html

  10. RIPE Database (1) • Public Network Management Database • Information about objects IP address space inetnum, inet6num reverse domains domain routing policies route, aut-num contact details person, role, mntner • Server whois.ripe.net • UNIX command line queries • http://www.ripe.net/ripencc/pub-services/db/

  11. RIPE Database (2) • Software Management • server and client • NOT relational • RIPE NCC • Database Working Group (RIPE community) • Data Management • LIRs • other users • RIPE NCC • Information content not responsibility of RIPE NCC • Protection mechanisms not default, but strongly encouraged

  12. RIPE Database v 3.0 • New language (RFC-2622) Routing Policy Specification Language • allows for more refined policy details • will eventually replace ripe-181 • transition to RPSL will be smooth • RPSL mirror of RIPE DB • rpsl.ripe.net • Test re-implementation server • queries: reimp.ripe.net at port 4343 • updates: <auto-rip@ripe.net>

  13. Summary: RIPE & RIPE NCC Two separate organisations, closely interdependent • RIPE • open forum for discussing policies • RIPE NCC • legitimate, not-for-profit association • formal membership • neutral and impartial

  14. Questions?

  15. Terminology • Internet Registry System

  16. Terminology • Allocation • address space given to registries which is held by them to assign to customers • Assignment • address space given to end-users for use in operational networks /20 allocation = 4096 addresses assignment assignment

  17. 24 110 256 192.0.0.0 - 223.255.255.255 Classful Notation network host 8 0 16,777,216 Class A 0.0.0.0 - 127.255.255.255 16 10 65,536 Class B 128.0.0.0 - 191.255.255.255 Class C • Obsolete because of • depletion of B space • too many routes from C space • Solution • Classless Inter Domain Routing • hierarchical address space allocation

  18. Classless Notation Addresses Prefix Classful Net Mask ... ... ... ... /29 8 255.255.255.248 16 /28 255.255.255.240 32 /27 255.255.255.224 64 /26 255.255.255.192 128 /25 255.255.255.128 256 /24 1 C 255.255.255.0 ... ... ... ... 4096 /20 16 C’s 255.255.240.0 8192 /19 32 C’s 255.255.224 16384 /18 64 C’s 255.255.192 32768 /17 128 C’s 255.255.128 65536 /16 1 B 255.255.0.0 ... ... ... ...

  19. Goals of the Internet Registry System • Aggregation • Conservation • Registration • uniqueness

  20. Local IR Regional Registry Structure IANA / ICANN ARIN RIPE NCC APNIC Local IR / ISP Enterprise Local IR ISP ISP / End user End user

  21. Service Regions

  22. Initial Administrivia of Becoming LIR

  23. Becoming LIR • Completed application form (ripe-212) • Provided Reg-ID & contact persons • <new-lir@ripe.net> • Read relevant RIPE documents • Signed contract (ripe-191) • agreed to follow policies and procedures • Paid the sign-up & yearly fee • <billing@ripe.net>

  24. Contact Persons • Stored in RIPE NCC internal file for each registry • confidential • Only registered contact persons can • send requests to hostmasters • change contact information • Use ‘role’ object • for multiple admin-c and tech-c • Always sign your e-mail messages • PGP optional (soon) • Members’ mailing lists • <local-ir@ripe.net> (lst-localir) • <ncc-co@ripe.net> (lst-contrib)

  25. Registry Identification (RegID) • Distinguishes between contributing registries and individuals • Format • <country code> . <registry name> • Include with every message • Suggestion - modify mail header • X-NCC-RegID: nl.bluelight

  26. New Registry’s First Request • Completing the request form • Communication with the hostmaster

  27. Sample First Request • Example: Blue Light Internet • LIR wants a block of IP addresses • e.g. for own network / infrastructure • do not include needs of customers yet Steps: • Complete request form ripe-141 • Send request to <hostmaster@ripe.net> • RIPE NCC evaluate and approve request With the first assignment RIPE NCC allocates /20 to the LIR

  28. Request Formripe-141 I. General Information Overview of Organisation Contact Information Current Address Space Usage II. The Request Request Overview Addressing Plan III. Database Information IV. Optional Information

  29. Completing the Request Form (starting from Addressing Plan)Gathering Information • Design of the network • how many physical segments it will consist of • what is each segment going to be used for • including equipment used • how many hosts are in each segment • expectations of growth

  30. #[ Addressing Plan Template ]# dynamic dial-up Amsterdam web/mail/ftp servers Amsterdam customers’ servers Amsterdam training room LAN Amsterdam Amsterdam office LAN (*1) dynamic dial-up Utrecht web/mail/ftp servers Utrecht Inet cafe Utrecht training room LAN Utrecht 0.0.0.0 0.0.0.128 0.0.0.160 0.0.0.176 0.0.0.192 0.0.1.0 0.0.1.128 0.0.1.160 0.0.1.176 255.255.255.128 255.255.255.224 255.255.255.240 255.255.255.240 255.255.255.192 255.255.255.128 255.255.255.224 255.255.255.240 255.255.255.240 128 32 16 16 64 128 32 16 16 448 Relative Subnet Mask Size Imm 1yr 2yr Description Prefix 100 10 8 14 24 0 0 14 0 100 12 10 14 35 100 12 14 0 100 16 13 14 50 100 25 14 10 170 297 342 Totals (*1) Office LAN = workstations, router, 2 printers and 1 fileserver

  31. Totals: 448 170 297 342 #[ Request Overview Template ]# request-size: 448 addresses-immediate: 170 addresses-year-1: 297 addresses-year-2: 342 subnets-immediate: 6 subnets-year-1: 8 subnets-year-2: 9 inet-connect: YES, already connected to “UpstreamISP” country-net: NL  private-considered: Yes request-refused: NO  PI-requested: NO  address-space-returned: 195.20.42.0/25, to UpstreamISP, “in 3 months”

  32. #[ Current Address Space Usage Template ]# Prefix Subnet Mask Size Imm 1yr 2yr Description 195.20.42.0 255.255.255.192 64 16 30 50 Dynamic dial-up A’dam 195.20.42.64 255.255.255.224 32 10 22 29 Amsterdam office LAN 195.20.42.96 255.255.255.240 16 4 6 8 Utrecht office LAN 195.20.42.112 255.255.255.240 16 6 10 13 Mail servers 128 36 68 100 Totals Actual addresses

  33. #[Person template]# Jan Jansen Blue Light Internet Oudezijds Achterburgwal 13 Amsterdam The Netherlands jan@bluelight.nl +31-20-555 5555 AUTO-1 BLUELIGHT-MNT jan@bluelight.nl 19990906 RIPE person: address: address: address: address: e-mail: phone: nic-hdl: mnt-by: changed: source: * *

  34. * * #[Network template]# inetnum: netname: descr: descr: country: admin-c: tech-c: status: mnt-by: changed: source: x.x.x.x/23 BLUELIGHT-1 Company infrastructure in both locations NL AB231-RIPE AUTO-1 ASSIGNED PA BLUELIGHT-MNT jan@bluelight.nl 19990906 RIPE

  35. Communication with <hostmaster@ripe.net>

  36. Ticketing System • Unique ticket number • facilitates retrieval / archiving • NCC#YYYYMMXXXX • e.g. NCC#2001053280 • Check status of ticket on the web • http://www.ripe.net/cgi-bin/rttquery • open ncc • open reg • closed • age of your ticket and oldest ticket in queue

  37. Hostmaster-robot • Checks request form • Reg-ID, contact persons • syntax • policy problems • Acknowledgement & diagnostics • LONGACK • Error message • correct & re-send the request • use the same ticket number • NOAUTO • No errors: hostmaster wait-queue • “ongoings” directly to hostmasters

  38. Frequently Asked Questions • List of answers • http://www.ripe.net/ripencc/faq/index.html • Short tips and tricks • http://www.ripe.net/ripencc/tips/tips.html • Ask hostmaster • <lir-help@ripe.net> • include your Reg-ID • Supporting Notes for the European IP Address Space Request Form (ripe-142)

  39. Request Approved • With the first ASSIGNMENT approved LIR automatically gets an ALLOCATION • /20 (4096 addresses) • RIPE NCC hostmaster enters allocation and assignment objects into the RIPE database at this time • /24 & /25 & /26 (448) instead of /23 (512) • Whole allocated range can be announced immediately • Every request has to be sent for approval to RIPE NCC • addresses for LIRs own infrastructure • all customers’ request

  40. Questions?

  41. Customer’s Request Evaluation Basic Database Issues

  42. Assignment Process Gathering information Completing ripe-141 Customer no Documentation completed? yes RIPE NCC evaluation no Documentation completed? approval notify customer update local records update RIPE database  Assignment

  43. Gathering Information • One request form per customer • Ask the same questions RIPE NCC asks LIR • enough information to complete ripe-141 • Add comments • Example: Goody 2 Shoes

  44. Before Submitting the Request • Web form • filling in the requests • syntax check • http://www.ripe.net/cgi-bin/web141/web141.pl.cgi • ftp://ftp.ripe.net/tools/web141.pl.cgi • Complete documentation reduces need for iteration • All the data communicated with RIPE NCC is kept strictly confidential • Documentation for RIPE NCC has to be in English

  45. Evaluation -- General Information • #[Overview of organisation template]# • information relevant to the address space request • Name and location of the company? • What are the company activities? • What is the structure? • Does it have subsidiaries and where? • For what part of the company are the addresses requested? • #[Requester Template]# • LIR contact for RIPE NCC • #[User Template]# • customer’s contact for LIR

  46. Evaluation -- Addressing Plan • Do totals in “Addressing Plan” match numbers in “Request Overview”? • Are all subnets classless? • are the subnet masks real? • Utilisation and efficiency guidelines: 25% immediately, 50% in one year • Can address space be conserved by using • different subnet sizes? • avoiding padding between subnets?

  47. Evaluation -- Network Template • inetnum value (look-up key, unique) • specifies the size of assignment • actual range is not necessary • Relevant netname (look-up key, not unique) • descriptive; uppercase letters, numbers & “-” • RIPE NCC’s only reference to LIR’s assignment • Contact persons • can be multiple • reference nic-hdls (may be a role object) • admin-c • responsible for the network, able to make decisions • tech-c • technical setup of the network

  48. Assignment for customer’s network Assignment for LIR’s network Internal Administration • Wait for the approval from <hostmaster@ripe.net>prior to assignment and registration • Decide on the range of addresses within your address space • classless assignment on bit boundary • Update local records for later refference • archive original documents with assignment

  49. Assignments to (Small) ISPs • LIR cannotallocate address space to an ISP • If the customer of LIR is an ISP, distinguish • ISP’s infrastructure • ISP’s customers • Separate assignments need to be • requested • evaluated / approved • registered in the RIPE Database • Avoid overlapping assignments • i.e. “big” assignment/object for ISP & all its customers, plus for separate customers

  50. Creating Database Objects

More Related