1 / 84

The Internet Registry System

The Internet Registry System. CEENet Workshop Budapest, August 2000 Vesna Manojlovic BECHA@ripe.net. Overview. RIPE RIPE NCC Internet Governance Global Internet Registry System IP address distribution & registration IPv6 RIPE Database Reverse DNS Delegation.

liluye
Télécharger la présentation

The Internet Registry System

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 System CEENet Workshop Budapest, August 2000 Vesna Manojlovic BECHA@ripe.net

  2. Overview • RIPE • RIPE NCC • Internet Governance • Global Internet Registry System • IP address distribution & registration • IPv6 • RIPE Database • Reverse DNS Delegation

  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. Global Context • World-wide Internet • Technical Development & Standards Body • World-wide Operators Forum • EU Operators USA Operators • Asian Operators IETF IEPG NANOG RIPE APRICOT

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

  10. RIPE Meetings • 3 times a year • ~3.5 day long • 300+ participants • Working group meetings • Plenary • Presentations • Long breaks • Informal chats • Terminal room • IPv4, IPv6 and wireless connectivity

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

  12. RIPE Meeting Attendees in 1999 other Total 857

  13. RIPE Meeting Attendance per Organisational Category 1999

  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 • 62 staff (21 nationalities) • 2,018+ participating Local IR’s • 11,390,000+ countable hosts in the RIPE NCC region • 3,041,650+ objects in the database

  19. > 2 New Members per Day

  20. New LIRs in 2000

  21. RIPE NCC Member Services • Registration Services • IPv4 addresses • IPv6 addresses • AS numbers • Reverse domain name delegation • LIR Training Courses

  22. RIPE NCC PublicServices • Co-ordination • RIPE support • RIPE database maintenance • Routing Registry Maintenance (RR) • Liaison with: • LIRs / RIRs / ICANN / etc … • Information dissemination • Special Projects • Test Traffic • Routing Information Service (RIS) • Routing Registry Consistency (RR)

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

  24. Internet Governance

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

  26. Developments in Internet Governance ICANN PSO ASO DNSO At Large RIPE NCC ARIN APNIC RIPE ARIN mtg. APNIC mtg.

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

  28. Global Internet Registry System

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

  30. Service Regions

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

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

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

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

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

  36. 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 RIPE NCC <new-lir@ripe.net>

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

  38. Obtaining IP AddressesThrough Existing LIR

  39. Providing Information (1) • Overview of organisation • information relevant to the address space request • name and location of the organisation? • organisation activities? • what is the structure? • does it have subsidiaries and where? • how many departments? • for what part of the company are the addresses requested? • Possible additional information • pointer to web site • deployment plan • special technologies • purchase receipts

  40. Providing Information (2) • 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 • topology map • Utilisation and efficiency guidelines • 25% immediately, 50% in one year • operational needs; no reservations • Can address space be conserved by using: • different subnet sizes? • avoiding padding between subnets? • Any address space already in use? • returning and renumbering? (encouraged)

  41. Addressing Plan 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

  42. Totals: 448 170 297 342 Request Overview 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”

  43. Private Address Space • RFC-1918 (Address Allocation for Private Internets) • Suitable for • partial connectivity • limited access to outside services • can use application layer gateways (fire walls, NAT) • Motivation • saves public address space • allows for more flexibility • security

  44. IPv6

  45. Why IPv6? • Next generation protocol • scalability -- 128 bits addresses • security • dynamic hosts numbering • Interoperable with IPv4 • simple and smooth transition • hardware vendors • applications • Testbed for deployment of IPv6 • www.6bone.net

  46. IPv6 Introduction • Current format boundaries |-3|--13-|--13-|-6-|--13-|--16--|------64 bits-----| +--+-----+-----+---+-----+------+------------------+ |FP|-TLA-|-sub-|Res|-NLA-|--SLA-|---Interface ID---| |--|-ID--|-TLA-|---|--ID-|--ID--|------------------| |----public topology ----|-site-|-----Interface----| +--+-----+-----+---+-----+------+------------------+ /23 /29/35 /48 /64 • Classfull; another level of hierarchy • Hexadecimal representation of addresses • IANA allocations • APNIC 2001:0200::/23 (12 subTLAs) • ARIN 2001:0400::/23 ( 4 subTLAs) • RIPE NCC 2001:0600::/23 (19 subTLAs)

  47. IPv6 Allocations • Draft allocation guidelines • provisional & bootstrap criteria • currently under revision by community • ipv6-wg@ripe.net & lir-wg@ripe.net • Initial allocation to LIRs • /35 subTLA • 13 bits of NLA space + 16 bits of SLA space • whole /29 subTLA reserved http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6.html

  48. The RIPE DatabaseIts usage and its usefulness

  49. 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, maintainer

  50. 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 • Strong protection mechanisms not default

More Related