1 / 38

Policy Development in RIPE & the RIPE NCC

Policy Development in RIPE & the RIPE NCC. Mirjam Kühne RIPE NCC. Overview. RIPE in the global context RIPE NCC in the global context Policy development how can you participate IPv4 & IPv6 Allocation Policies. What is RIPE?. Reseaux IP Européens (1989)

pcoffey
Télécharger la présentation

Policy Development in RIPE & the RIPE NCC

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. Policy Development in RIPE & the RIPE NCC Mirjam Kühne RIPE NCC

  2. Overview • RIPE • in the global context • RIPE NCC • in the global context • Policy development • how can you participate • IPv4 & IPv6 Allocation Policies

  3. What is RIPE? • Reseaux IP Européens (1989) • collaborative organisation of ISPs • open to all interested parties • voluntary participation, no fees • works by consensus • encourages face-to-face discussion • “interest group” for Internet community in ‘Europe’

  4. RIPE Meeting attendees for 1998 Total: 669

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

  6. What is the RIPE NCC? • Co-ordination and support services for ISPs • Not-for-profit association under Dutch law • formal membership, Executive Board , yearly fee • 7 years of history • 1500+ members (mainly ISPs, but open to anyone)

  7. RIPE NCC Membership

  8. Why an NCC ? • Support for RIPE/ISP community • Activities need continuity • Database ... • Neutrality and impartiality important • to ensure fair distribution of resources • neutral ground for ISPs to co-ordinate technical & administrative issues

  9. RIPE NCC Activities • Registration Services • IPv4 & IPv6 address & AS number allocation • Reverse delegation • Co-ordination & Liaison • RIPE database maintenance • Technical Projects • Information Dissemination & Education

  10. Activity Development Process RIPE Working Groups • define requirements, suggest activities RIPE NCC Staff • produces activity plan & budget RIPE NCC Executive Board • submits to membership RIPE NCC Membership • approves and sets fees

  11. Global Policy Development • Developed in open policy meetings • Implemented by Regional Internet Registries • Co-ordinated among RIRs

  12. RIPE NCC in Global Context Ultimate global numbers authority Sets policy and criteria for Regional Registries Regional Registries: Policies and criteria aligned but differences in local implementation IANA/ICANN RIPE NCC ARIN APNIC RIPE ARIN Mtg APRICOT

  13. Policy Development in RIPE • Developed in RIPE LIR-WG • open-open-open • Implemented by RIPE NCC • open; controlled by membership

  14. Policy Development Process • Policy (changes) can be suggested by • Members/Local IRs • RIPE NCC • Public at large • Policy must be • fair to all • ‘good’ for the Internet • consistent with global policies

  15. How Can You Participate • RIPE Working Groups • LIR-WG • Open Mailing Lists • <majordomo@ripe.net> • Public Meetings • next meeting in Amsterdam February 1999 • RIPE NCC membership • AGM http://www.ripe./net/meetings

  16. IPv4 Facts & Information

  17. IPv4 Allocation Policies • RIPE NCC Member • Initial allocation: /19 • Next allocation based on usage rate • Support and Training to ensure fair distribution

  18. IANA Allocations • 192.x.y.z: 1992/1993 • 193/8: Sep. 1993 • 194/8: Sep. 1993 • 195/8: Mar. 1994 • 62/8: Apr. 1995 • 212/8 Jan. 1998 • 213/8: May 1999 • B’s: 1993 (last assigned from in 1996)

  19. Address Space Usage

  20. Address Space Usage APNIC

  21. RIPE NCC Allocations • 1,500 Members • mainly ISPs • also Telcos, Gov., Associations, Academic • Initial allocation: /19 • Next allocation based on usage rate • Support and Training to ensure fair distribution • 85 Countries

  22. Service Regions of the Registries ARIN RIPE NCC APNIC

  23. 1,5 New Members a Day

  24. RIPE NCC Charging Model • 3 Categories • pre-1997: self-determined • now based on allocations and aging 2000 (prelim.) 1999 1998 Small 2400 2650 2450 Medium 3350 3700 3400 Large 4400 4900 4500 Sign-up 2100 2100 2000

  25. LIR Charging Model • RIPE Community agreement • Service charge • no per-address charge • See ‘Charging by Local Internet Registries’ • Authors: RIPE NCC & LIR-WG chair http://www.ripe.net/docs/ripe-152.html

  26. IPv6 Information & Experiences

  27. IPv6 Allocation Policies Peering with 3  subTLAs AND either Plan to provide IPv6 services within 12 months OR  40 SLA customers

  28. IPv6 Allocation Policies(Bootstrap Phase) Peering with 3  ASes AND Plan to provide IPv6 services within 12 months AND either  40 IPv4 customers OR 6bone experience

  29. IPv6 Allocations • Initial Allocation: /35 subTLA • Entire /29 reserved (aggregatable) • APNIC: 3 sub-TLAs allocated • ARIN: 2 subTLAs allocated • RIPE NCC: 6 subTLAs allocated

  30. IANA Allocations • APNIC: 2001:0200::/23 • ARIN: 2001:0400::/23 • RIPE NCC: 2001:0600::/23

  31. Database Object • inet6num: 2001:0600::/23 netname: RIPE-NCC descr: RIPE Network Co-ordination Centre descr: Amsterdam, Netherlands country: NL admin-c: NN44-RIPE tech-c: MK16-RIPE status: ASSIGNED PA mnt-by: LIR-MNT changed: hostmaster@ripe.net 19990820 source: RIPE

  32. TLA/NLA/SLA Relationship • NLA & SLA database registration • Review before next TLA allocation • No additional charges for IPv6 in 1999/2000 • Part of existing charging scheme in 2001 • review by membership

  33. Open Issues • Multihoming • IETF IPng WG • Current solution: multiple SLAs • Renumbering • outside the IP layer

  34. ASO & ICANN

  35. Global Aspects • All addresses are global • Co-ordination among RIRs and IANA • Dependent on topology • one backbone? • Local connection? • IANA does not allocate addresses directly

  36. Interaction with other Technologies • Difference to dynamic dial-up? • addresses don’t move, user moves • Co-operation with Telco Operators and ETSI • started • continue in the future

  37. Pointers & References • RIPE Meetings http://www.ripe.net/meetings/ripe/index.html • IPv4 Allocation Policies http://www.ripe.net/docs/ripe-185.html • IPv6 Allocation Policies http://www.ripe.net/lir/registries/ipv6.html • Presentation http://www.ripe.net/meetings/pres/index.html

  38. QUESTIONS? http://www.ripe.net

More Related