1 / 69

The Internet Registry System How to run a Local IR

The Internet Registry System How to run a Local IR. NATO Workshop Tartu June 2000 John Crain. Overview. RIPE RIPE NCC Internet Registry System Running a Local Internet Registry IP address distribution & registration Reverse Delegation RIPE database. Questions always welcome!.

velma
Télécharger la présentation

The Internet Registry System How to run a Local IR

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. The Internet Registry SystemHow to run a Local IR NATO Workshop Tartu June 2000 John Crain

  2. Overview • RIPE • RIPE NCC • Internet Registry System • Running a Local Internet Registry • IP address distribution & registration • Reverse Delegation • RIPE database

  3. Questions always welcome!

  4. Reseaux IP Européens

  5. What is RIPE? • Reseaux IP Européens (1989) • forum for network engineers to discuss technical issues • RIPE is • service provider forum • open for everybody • voluntary participation, no fees • works by consensus • encourages face-to-face discussion • acts like an “interest group” supporting Internet community • but has NO legal power

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

  7. Join RIPE Working Groups • Local Internet Registries (LIR) • RIPE Database (DB) • IP version 6 (IPv6) • European Internet Exchange Forum (EIX) • Routing / MBONE • Domain Name System (DNS) • NETNEWS Co-ordination • Anti-Spam • Test-Traffic Project • European Operators Forum (EOF) RIPE does NOT develop Internet Standards

  8. Subscribe to RIPE Mailing Lists • General announcement list • <ripe-list@ripe.net> • Working group lists • <lir-wg@ripe.net> • <dns-wg@ripe.net> • etc. • For more information • Send “help” to <majordomo@ripe.net> • Join the mailing lists and get informed http://www.ripe.net/info/maillists.html

  9. RIPE Meetings • 3 times a year • ~3.5 day long • 300+ participants • Working group meetings • Plenary • Presentations • Long breaks • Informal chats

  10. 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 RIPE NCC service region and beyond • Next meeting RIPE 37 • Amsterdam, 12-15. September 2000 • <meeting@ripe.net>

  11. RIPE Meeting Attendees in 1999 other Total 857

  12. RIPE Meeting Attendance per Organisational Category 1999

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

  14. RIPENetwork Coordination Centre

  15. What is the RIPE NCC? • Not-for-profit association under Dutch law • 8 years of history • 2000+ members (mainly ISPs, but open to anyone) • Co-ordination and support services for ISPs

  16. Why a NCC ? • RIPE participation was increasing • Too much RIPE work done on a voluntary basis • Activities require continuity & co-ordination • Neutrality and impartiality is important • Contact point inside & outside RIPE region

  17. RIPE NCC History • April 1992: Birth of the RIPE NCC • TERENA legal umbrella • September 1992: RIR Function • 1995: Contributing Local IRs • 1998: Independent Organisation • not-for-profit association under Dutch law • General Assembly of all members • Executive Board of elected nominees http://www.ripe.net/annual-report/99ar.html

  18. 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 • 60 staff (21 nationalities) • 2,000+ participating Local IR’s • 11,000,000+ hosts in the “European” Internet • 5,000,000+ objects in the database

  19. RIPE NCC Membership

  20. New LIRs per Region 1999 Europe : 551 (Including Turkey, Georgia and Kyrgyz Republic) Middle-East: 31 (including Israel and Iran) Africa: 8

  21. New LIRs in 2000

  22. RIPE NCC Activities (1) Member Services • Registration Services • IPv4 addresses • IPv6 addresses • AS numbers • Reverse domain name delegation • LIR Training Courses

  23. RIPE NCC Activities (2) Public Services • Co-ordination • RIPE support • RIPE database maintenance • Routing Registry Maintenance (RR) • Liaison with: • LIRs / RIRs / ICANN / etc … • Information dissemination • New Projects • Test Traffic • Routing Information Service (RIS) • Routing Registry Consistency (RR)

  24. Formal Decision Making “Consensus” Model RIPE proposes activity plan RIPE NCC proposes budget to accompany activity plan General Assembly votes on both activities and budget at yearly meeting

  25. Global Internet Registry System

  26. Authority in the Net?? • The Internet Corporation for Assigned Names and Numbers (ICANN) is the non-profit corporation that was formed to assume responsibility for the IP address space allocation, protocol parameter assignment, domain name system management, and root server system management functions now performed under U.S. Government contract by IANA and other entities.

  27. ICANN Structure of ICANN The Internet Corporation for Assigned Names and Numbers 3 Supporting Organizations Protocols DNS Addresses IETF, ITU, WWWC, ETSI www.dnso.org APNIC ARIN RIPE NCC http://www.icann.org

  28. Address Supporting Organization • RIR agreed on a proposal • “Simple model” • MoU between ICANN and RIRs • Policies set through existing regional processes • Address Council established • oversee policy development processes • select ICANN directors (open process) http://www.aso.icann.org

  29. RIR Service Regions ARIN RIPE NCC APNIC

  30. Goals of the Internet Registry System • Fair distribution of address space • Conservation • prevention of stockpiling of addresses • Aggregation • hierarchical distribution of globally unique address space • permits aggregation of routing information • Registration • provision of public registry • ensures uniqueness and enables troubleshooting

  31. Global Authority LIR /20 + RIPE NCC Members /32 + End Users Anybody with a network/host Address Distribution RIR /8

  32. Running a Local Internet Registry

  33. How to get IP addresses? • Go to your Local Internet Registry. • Your provider is probably one or is connected to one http://www.ripe.net/lir/registries/europe.html • If you are a provider and think you may need to be an LIR? Contact NCC <new-lir@ripe.net>

  34. Becoming a LIR • Complete application form (ripe-160) • Provide Reg-ID & contact persons • <new-lir@ripe.net> • Read relevant RIPE documents • Sign service agreement (ripe-191) • agreed to follow policies and procedures • Pay sign-up & yearly fee • <billing@ripe.net>

  35. Address Space Usage 98% 97% 96,5% 40,1% 97% 60%

  36. IPv6 • Draft allocation guidelines • currently under revision by community • Address allocation started • 17 sub-TLAs allocated by RIPE NCC http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6.html

  37. DNS Activities

  38. RIPE NCC Hostcount per Quarter

  39. DNS Management • Goals • ensure proper operation of name servers • minimise “pollution” of DNS • Services • manage reverse delegations of networks in 193/8, 194/8, 195/8, 212/8, 213/8 and 62/8 in-addr.arpa domain • support local IR’s with feedback • secondary name servers for ccTLDs • RIPE NCC DOES NOT register domain names

  40. Why Do You Need Reverse Delegation ? • All host-IP mappings in the DNS (A record) should have a corresponding IP-host mapping (PTR record) • Failure to have this will likely • block users from various services (ftp, mail) • make troubleshooting more difficult • produce more useless network traffic in general

  41. Request Reverse Delegation • Send domain object to <auto-inaddr@ripe.net> • an automatic mailbox • Tool will • check if zone is correctly setup • check assignment validity • (try to) enter object to RIPE DB • Questions, Comments to <inaddr@ripe.net>

  42. Reverse DNS Quality Report • 80% of delegating zones good • Quality improving • ~500 new zones /week • 52.3% of eligible /24 zones are delegated http://www.ripe.net/inaddr/statistics

  43. The RIPE DatabaseIts usage and its usefulness

  44. RIPE Database • Network Management Database • Data Management • Local IR’s, other ISPs and RIPE NCC • Software Management • RIPE NCC with Database Working Group • Re-implementation in progress

  45. RIPE Database • RIPE whois server whois.ripe.net • RIPE whois client ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-2.2.1.tar.gz • Glimpse full text search http://www.ripe.net/db/index.html • Database documentation http://www.ripe.net/docs/ripe-157.html http://www.ripe.net/docs/ripe-189.html

  46. Some Database Objects • person: contact persons • role: contact groups/roles • inetnum: address assignments & networks • mntner: authorisation of objects • domain: forward and reverse domains • route: announced routes • aut-num: autonomous system • as-macro: group of autonomous systems • community: group of routes • inet6num: experimental object for IPv6 addresses

  47. Almost 5 Million Objects 4,885,891 Rate: 300, 000 p.m.

  48. ‘person’ Object • person: Mirjam Kuehne • address: RIPE NCC • address: Singel 258 • address: NL - 1016 AB Amsterdam • address: Netherlands • phone: +31 20 535 4444 • fax-no: +31 20 535 4445 • e-mail: mir@ripe.net • nic-hdl: MK16-RIPE • notify: mir@ripe.net • changed: mir@ripe.net 19950411 • changed: mir@ripe.net 19970616 • source: RIPE

  49. ‘role’ Object • role: RIPE NCC Hostmaster • address: RIPE Network Coordination Centre • address: Singel 258 • address: NL - 1016 AB Amsterdam, Netherlands • phone: +31 20 535 4444 • e-mail: hostmaster@ripe.net • trouble: Work days 0900-1800 CET: phone XXX • trouble: Outside Business Hours: phone YYY • admin-c: JLC2-RIPE • tech-c: MK16-RIPE • notify: hostmaster@ripe.net • nic-hdl: RNH124-RIPE • changed: hostmaster@ripe.net 19971002 • source: RIPE

  50. Network Object • inetnum: 193.0.0.0 - 193.0.0.255 • netname: RIPE-NCC • descr: RIPE Network Co-ordination Centre • descr: Amsterdam, Netherlands • country: NL • admin-c: JLC2-RIPE • tech-c: MK16-RIPE • status: ASSIGNED PA • mnt-by: RIPE-NCC-MNT • changed: GeertJan.deGroot@ripe.net 19970310 • source: RIPE • “/” notation possible for inetnum value

More Related