RIPE NCC at CEENET 98

1
RIPE NCCatCEENET 98

• Bratislava, August 30th
• John Crain ltjohn_at_ripe.netgt

2
Overview

• Introduction to RIPE, CENTR the RIPE NCC
• RIPE Database
• Routing Registries

3
Introduction to RIPE, CENTR and the RIPE NCC
4
What is RIPE?

• Reseaux IP Européens (1989)
• RIPE is a collaborative organisation open to all
  European Internet Service Providers
• RIPE is
• service provider forum
• voluntary participation, no fees
• works by consensus
• encourages face-to-face discussion
• acts like an interest group supporting EU
  Internet community
• but has NO legal power

5
How RIPE Works

• RIPE chair ltchair_at_ripe.netgt
• Chair is Rob Blokzijl (Nikhef)
• How does it work?
• Working groups
• Mailing lists
• Meetings

6
RIPE Working Groups

• Local Internet Registries (Local IR)
• Discussion of IP-Number assignment policies
  adhered to by the RIPE NCC.
• RIPE Database (RIPE DB)
• New ideas and old problems in the RIPE DB
• IP version 6 (IPv6)
• Implementation and experiences on the 6bone.
• Internet Exchange Forum (EIX)
• Where are the new exchanges and what are their
  policies.

7
RIPE Working Groups

• Routing
• Route flap damping and the state of the routers.
• Domain Name System (DNS)
• Discussion on new ideas for DNS
• TLD Administrators (TLD)
• Common problems and some politics
• MBONE
• NETNEWS Co-ordination

8
RIPE does not develop Internet Standards.
9
Global Context
World-wide Internet Technical Development
Standards Body World-wide Operators
Forum EU Operators USA
Operators Asian
Operators
IETF
IEPG
NANOG
RIPE
APRICOT
10
RIPE Mailing Lists

• General announcement list
• ripe-list_at_ripe.net
• local-ir_at_ripe.net
• Working group list
• lir-wg_at_ripe.net
• dns-wg_at_ripe.net
• etc.
• For more information
• Send help to ltmajordomo_at_ripe.netgt
• Get on the mailing lists and be informed!!!

11
RIPE Meetings

• About RIPE meetings
• RIPE meets 3 times a year
• 2.5 day meetings
• 250 participants - growing!
• over 100 organisations participate
• working group meetings, plenary
• presentations, hallway chats
• Come to the meeting!
• keep up to date with Internet
• meet others in the business
• pick up information, tips, ideas
• influence directions in EU Internet

12
RIPE Meetings

• Next meeting info
• http//www.ripe.net/meetings/index.html
• Minutes and agendas from past meetings
• ftp//ftp.ripe.net/ripe/minutes/
• ftp//ftp.ripe.net/ripe/agenda/
• Presentations from past meetings
• ftp//ftp.ripe.net/ripe/presentations/
• Next meeting
• RIPE 31
• Edinburgh, United Kingdom, September 23-25, 1998

13
What is CENTR?

• CENTR is a project facilitated by RIPE NCC on
  behalf of participating ccTLDs in the RIPE area.
• Work is currently on the way for establishing
  CENTR as a separate legal entity.
• CENTR Focuses primarily on the ccTLD admins of
  RIPE area but not exclusively.

14
Aims of CENTR

• Communication channel with Internet governing
  bodies.
• Exchange of experiences and views.
• Common policy making and consensus forming.
• Documentation of practices.

15

• Collection of statistics.
• Support of emerging registries.
• Representation of the members.

16
Short History

• CENTR Started in 1997 in the RIPE TLD-wg
• Initial stage is administratively supported by
  the RIPE NCC
• Autumn of 1997 saw the first RIPE CENTR proposal.
• lthttp//www.ripe.net/docs/ripe-177.htmlgt
• March 2 1998 - First CENTR meeting
• lt http//www.ripe.net/centr/meetings/first.htmlgt

17
Achievements

• Future Structure of the Internet
• Published a response to the US Green and White
  Papers
• Liaison with US Government, EC and IANA
• Process for Establishing CENTR as a legal entity
• Task force has been established to set the
  requirements and criteria for hosting CENTR
• An assessment panel will judge proposals
• Project work
• Information gathering
• Technical workshop
• Managerial workshop to take place 21/9/98

18
Statistic

• 36 Participating ccTLDs plus observer status
• given to ccTLDs in other regions.
• lt http//www.ripe.net/centr/participants.htmlgt
• Three plenary meetings held and one task force
  meeting.
• Budget for 1998 120.000 XEU (ECUs)
• Raised from voluntary contributions
• Task force setup to look at a legal structure for
  CENTR.

19
Related organisation

• World Wide Alliance of TLDs
• lthttp//www.canarie.ca/tld/gt
• Council of Asian Pacific ccTLDs
• lthttp//www.apng.org/apcctld/gt
• Latin American and Caribbean ccTLDs
• Now forming, URL as yet unknown.

20
Contacting CENTR

• CENTR Project Project Manager
• Fay Howard
• Email Fay_at_ripe.net
• Website
• http//www.ripe.net/centr/

21
What is the RIPE NCC?

• Network Co-ordination Centre
• The RIPE NCC is a co-ordination and support
  service for European Internet service providers
  (ISPs)
• Why an NCC?
• Too much RIPE work to be done on a voluntary
  basis
• Some activities need continuity
• Neutrality and impartiality is important
• Contact point inside outside Europe

22
RIPE NCC History

• Long ago (1989)
• RIPE participation was increasing
• RIPE could not continue co-ordination through
  voluntary effort alone
• RIPE NCC birth - April 1992
• Legal umbrella TERENA (formerly RARE)
• Financial contributions from TERENA members, EARN
  Eunet - thanks!
• Contributing LIRs in 1995
• Financed by model of contributing Local IRs
• Participative decision making via Contributors
  Committee

23
RIPE NCC History Cont.

• Since 1998
• RIPE NCC has become independent from Terena and
  has a new structure.
• There is a General Assembly of all contributors
  and an Executive Committee of elected nominees.
• Theres a document describing the structure
• ripe-161 A New Structure for the RIPE NCC
  De-Facto Organisational Rules

24
Formal Decision Making

• Consensus Model
• RIPE proposes activity plan
• RIPE NCC proposes budget to accompany
• activity plan (ripe-162)
• General Assembly votes on both
• activities and budget at yearly meeting (or
  electronically)
• (ltncc-co_at_terena.nlgt ripe-169)
• Next AGM to be announced soon(Tentative date -
  October 14th)

25
Vital Statistics

• Statistics 1992
• 3 staff members
• No Local IRs
• 182,528 hosts in European Internet
• 7,955 objects in RIPE database (June 92)
• Statistics Now
• 45 staff
• Nationalities 14
• 1000 participating Local IRs
• 6,795,885 hosts in the European Internet
• 750,000 objects in the database

26
RIPE NCC 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
RIPE NCC
ARIN
APNIC
RIPE
NANOG
APRICOT
27
Growth in EU Internet
RIPE DNS Hostcount per Quarter
28
RIPE NCC Activities

• Registration Services
• IP allocations
• IP assignments/approvals
• AS assignments
• DNS management
• 193/194/195/212/62.in-addr.arpa reverse zones
• secondary for ccTLDs
• Local Internet Registry Training Courses
• RIPE database maintenance
• vital information for operations
• address space, domains, routes, autonomous
  systems, person objects

29
IP Registry Evolution

• Early days
• IP registry function all by US NIC
• unstructured address distribution
• Currently
• distributed hierarchical registry system
• topologically significant allocation via IRs
  (ISP based, not geographical)
• Types of registries
• global IANA
• regional APNIC, RIPE NCC ARIN
• local Provider, Enterprise

30
Multi-coloured Paper-chase

• US Government issued documents on their vision of
  Internet structure in the future.
• Control should be given to an Internationally
  recognised not-for-profit organisation.
• Furthest developed proposal is n IANA
• www.iana.org

31
Goals of the IR System

• Conservation
• fair distribution of address space
• prevention of stockpiling of addresses
• Aggregation
• hierarchical distribution of globally unique
  address space
• permits aggregation of routing information
• keeps routing tables small
• Registration
• provision of public registry
• ensures uniqueness of address space
• enables trouble shooting

32
EU Registry Structure

• IANA

EU Regional IR RIPE NCC
ISP Local IR
ISP Local IR
ISP Local IR
ISP Local IR
Enterprise Local IR
ISP Local IR
ISP Local IR
Example country B
Example country A
33
Growth in EU Internet
Number of Local Internet Registries
34
Non EU requests

• Whom to contact?
• historical determination
• Regional IR will always forward request
• ARIN (Registration Services)
• IP AS numbers inaddr requests
  lthostmaster_at_arin.netgt
• Inaddrs (Bs) done by Internic
  lthostmaster_at_internic.netgt
• APNIC
• IP, AS numbers inaddr requests to
  lthostmaster_at_apnic.netgt
• Future other Regional Registries?

35
Scope of RIPE NCC
RIPE NCC
APNIC
ARIN
36
RIPE NCC Activities

• RIPE support
• organisational support for RIPE meetings
• Support to working groups chairs
• Information dissemination
• mailing list discussions
• RIPE document store
• RIPE meetings
• WWW site
• Representation at meetings
• formally reporting to IANA for EU registries
• liaison role at other Internet organisations/meeti
  ngs

37
RIPE NCC Activities

• Routing Registry Maintenance (RR)
• encouraging ASes register policy in DB
• consistency check AS and routing data
• maintaining RR tools
• Co-ordination
• European Internet service providers
• sister organisations - ARIN, APNIC
• Internet Assigned Numbers Authority (IANA)

38
Where do you go for IPv4?
End Users should go to a Local Internet
Registry Http//www.ripe.net/lir/registries/indic
es/
39
Internal Organisation (1)

• Role mailboxes
• Registration Services
• lthostmaster_at_ripe.netgt
• RIPE database
• ltripe-dbm_at_ripe.netgt, ltauto-dbm_at_ripe.netgt
• Reverse delegations
• ltinaddr_at_ripe.netgt, ltauto-inaddr_at_ripe.netgt
• Billing
• ltbilling_at_ripe.netgt

40
Internal Organisation (2)

• Role Mailboxes continued
• New LIR set-up
• ltnew-lir_at_ripe.netgt
• General Questions
• ltncc_at_ripe.netgt
• Local IR Training
• lttraining_at_ripe.netgt
• Website questions suggestions
• ltwebmaster_at_ripe.netgt
• Special mailbox
• RIPE Meeting ltmeeting_at_ripe.netgt

41
Questions