1 / 161

Welcome to the Local Internet Registry Course

Welcome to the Local Internet Registry Course. Course Background. Why LIRs need training? to be informed to be kept up-to-date need support Financial Resources “start-up” fee course, including lunch, is “free” Get to know each other personally In areas outside Europe. RIPE and RIPE NCC.

koen
Download Presentation

Welcome to the Local Internet Registry Course

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 theLocal Internet Registry Course

  2. Course Background • Why LIRs need training? • to be informed • to be kept up-to-date • need support • Financial Resources • “start-up” fee • course, including lunch, is “free” • Get to know each other personally • In areas outside Europe

  3. RIPE and RIPE NCC

  4. Introduction to RIPE

  5. What is RIPE? • Reseaux IP Européens (1989) • “RIPE is a collaborative organisation open to all European Internet Service Providers” • RIPE is • open forum • voluntary participation • works by consensus • NO legal power • does NOT develop Internet Standards

  6. Global Context • World-wide Internet • Technical Development & Standards Body • World-wide Operators Forum IETF IEPG NANOG RIPE APRICOT

  7. How RIPE Works • RIPE chair <chair@ripe.net> • Chair is: Rob Blokzijl (Nikhef) • How does it work? • Working groups • Mailing lists • Meetings

  8. Join RIPE Working Groups • Local Internet Registries (LIR) • RIPE Database (DB) • … • Working group • chair • charter • agenda • action points • mailing list

  9. Subscribe to RIPE Mailing Lists • Working group lists • lir-wg@ripe.net • dns-wg@ripe.net • etc. • General announcement list • ripe-list@ripe.net • Open but moderated for spam • Archived • <majordomo@ripe.net>

  10. RIPE Meetings • 3 times a year • 3.5 day meetings • ~ 280 participants - growing! • Working group meetings • Plenary • Presentations • Hallway chats

  11. Come to RIPE Meetings • Keep up to date with Internet developments • Meet others in the business • Gather information, tips, ideas • Influence directions in Internet administration • in Europe and surrounding areas • Next meeting  RIPE 35 • Amsterdam, 20-24. February 2000 • <meeting@ripe.net>

  12. Introduction to RIPE NCC

  13. What is the RIPE NCC? • Network Co-ordination Centre • The RIPE NCC is a “co-ordination” and support service mainly for Internet service providers in RIPE area • Why a NCC ?

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

  15. Formal Decision Making “Consensus” Model RIPE proposes activity plan RIPE NCC proposes budget to accompany activity plan (ripe-197) General Assembly votes on both activities and budget at yearly meeting (<ncc-co@ripe.net>)

  16. 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 • 57 staff (20 nationalities) • 1,486+ participating Local IR’s • 9,148,276+ hosts in the “European” Internet • 2,619,263+ objects in the database

  17. ISP Local IR Regional Registry Structure IANA ARIN RIPE NCC APNIC ISP Local IR Enterprise Local IR

  18. Service Regions

  19. Developments in Internet Administration IANA / ICANN PSO ASO DNSO RIPE NCC ARIN APNIC

  20. RIPE NCC Activities

  21. Registration Services • IP assignments & allocations • AS # assignments • 2nd opinions on requests • Database updates • Support & guidance • New LIR start-up • Training - procedures & policies • Contact • <hostmaster@ripe.net>

  22. Goals of the Internet Registry System • Fair distribution of address space • Conservation • Aggregation • Registration

  23. Reverse DNS Management • Goals • ensure proper operation of nameservers • minimise “pollution” of DNS • Services • manage reverse delegations • support Local IR’s with feedback • secondary namservers for ccTLDs • We DO NOT register domain names

  24. RIPE Database • Network Management Database • Information about objects IP address space inetnum domain names domain routing policies route, aut-num contact details person, role • Is NOTrelational database • re-implementation in progress

  25. RIPE Database • Data Management • LIRs • other ISPs • RIPE NCC • Software Management • RIPE NCC • Database Working Group (RIPE community)

  26. Routing Registry (RR) • Goals of the RR • consistency and stability of routing • enable development of tools to use information • Local IR responsibilities • register policy information in RR • maintain RR information • Regional IR responsibilities • consistency checking of data • maintenance of RR support tools

  27. Additional Activities • RIPE support • Special projects • Test Traffic • Co-ordination • European Internet Service Providers • sister organisations - InterNIC / ARIN, APNIC; IANA • Information dissemination

  28. Questions?

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

  30. Setting Up a NewLocal Internet Registry

  31. Steps for Becoming LIR • Filling in application form • Providing Reg-ID & contact persons • <new-lir@ripe.net> • Reading RIPE documents • Signing a contract • Paying the sign-up & yearly fee • <billing@ripe.net>

  32. Contact Persons • Stored in RIPE NCC internal file for each registry • Only registered contact persons can • send requests to hostmasters • change contact information • Use ‘role’ object • Members’ mailing lists • <local-ir@ripe.net> • <ncc-co@ripe.net>

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

  34. New Registry’s First Request

  35. Terminology • Allocation • address space given to registries which is held by them to assign to customers • Assignment • address space given to end-users who then use it in operational networks /19 allocation = 8192 addresses assignment

  36. Sample First Request • As a LIR you want a block of IP addresses • e.g. for your own network / infrastructure • don’t include needs of your customers yet • Request form is ripe-141 Steps: • Complete the request form • Send it to <hostmaster@ripe.net> • We will evaluate it and approve it

  37. Completing the Request Form (starting from Addressing Plan)Gathering Information • Design of network • which segments it consists of • what is each segment going to be used for • including equipment used • how many hosts are in each segment • expectations of growth in next 2 years

  38. #[ Addressing Plan Template ]# 0.0.0.0 0.0.0.128 0.0.1.0 0.0.1.32 0.0.1.64 0.0.1.128 0.0.1.192 0.0.1.208 0.0.1.224 0.0.1.240 0.0.1.248 100 100 100 0 100 100 10 12 20 0 12 25 24 35 50 0 30 40 14 14 14 8 10 13 14 14 14 2 4 6 0 0 6 dial-up Amsterdam dial-up Utrecht web/mail/ftp servers Amsterdam web/mail/ftp servers Utrecht Amsterdam office LAN (*1) Utrecht office LAN (*2) training room LAN Amsterdam e-commerce servers Inet cafe Amsterdam web design dept. LAN A’dam training room LAN 255.255.255.128 255.255.255.128 255.255.255.224 255.255.255.224 255.255.255.192 255.255.255.192 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.248 255.255.255.248 128 128 32 32 64 64 16 16 16 8 8 Relative Subnet Mask Size Imm 1yr 2yr Description Prefix 512 172 331 388 Totals (*1) Office LAN = workstations, router, 2 printers and 1 fileserver

  39. Totals: 512, 172, 331, 388 #[ Request Overview Template]# request-size: 512 addresses-immediate: 172 addresses-year-1: 331 addresses-year-2: 388 subnets-immediate: 7 subnets-year-1: 10 subnets-year-2: 11 inet-connect: YES, already connected to “an ISP” country-net: NL private-considered: Yes request-refused: NO PI-requested: NO address-space-returned: 195.20.45/25 to “old ISP” within “3 months time”

  40. Requester & User #[Requester Template]# name: Jan Jansen organisation: Blue Light Internet BV country: NL phone: +31-20-555 5555 fax-no: +31-20-555 5556 e-mail: jan@bluelight.nl • #[User Template]# • syntax demands two set of data

  41. #[Overview of Organisation Template]# • Name of the company? • What are the company activities? • Where is it located? • What is the structure? • Does it have subsidiaries and where? • Where is the HQ? • For what part of the company are the addresses requested?

  42. #[Current Address Space Usage Template]# Relative 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 range

  43. #[Person template]# Jan Jansen Blue Light Internet Oudezijds Achterburgwal 13 Amsterdam jan@bluelight.nl +31-20-555 5555 JAJA1-RIPE jan@bluelight.nl 19980808 RIPE person: address: address: address: e-mail: phone: nic-hdl: changed: source:

  44. #[Network template]# x.x.x.x./23 bluelight-1 Blue Light Internet Amsterdam NL JAJA1-RIPE JAJA1-RIPE ASSIGNED PA jan@bluelight.nl 19990909 RIPE inetnum: netname: descr: descr: country: admin-c tech-c status: changed: source:

  45. Additional Information • Include all other details • web page • topology map • specific hardware • (*1) Office LAN = workstations, router, 2 printers and 1 fileserver • Summary • send completed request to <hostmaster@ripe.net>

  46. Communication With Hostmaster

  47. Ticketing System • Unique ticket number • facilitates retrieval / archiving • NCC#YYYYMMXXXX • NCC#1999073280 • Check status of ticket on the web

  48. Hostmaster-robot • Checks request form • syntax, missing sections • policy problems • Acknowledgement & diagnostics • LONGACK • Error message • correct & re-send the request • use same ticket number

  49. Request Approved • With the first ASSIGNMENT you were requesting you will automatically get an ALLOCATION • /19 (8192 addresses) • Hostmaster enters allocation and assignment objects into the database for you at this moment • You can announce your allocated range to the Internet

  50. Questions?

More Related