Administering the Internet' A brief introduction

1
Administering the Internet.A brief introduction

• presented by
• John LeRoy Crain
• RIPE NCC
• john_at_ripe.net
• August 1999

2
Questions always welcome!!
3
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.

4
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
5
Address Supporting Organization

• RIR agreed on a proposal
• Simple model
• MoU between ICANN and RIRs
• Policies set through existing regional processes
• Formation of Address Council
• oversee policy development processes
• select ICANN directors (open process)
• ltaso-discuss_at_ripe.netgt

6
RIPE and the RIPE NCC
7
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

8
Service Regions of the Registries
RIPE NCC
ARIN
APNIC
9
How RIPE Works

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

10
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)
• TLD Administrators (TLD)
• NETNEWS Co-ordination
• Anti-Spam
• Test-Traffic Project
• European Operators Forum (EOF)
• RIPE does NOT develop Internet Standards

11
RIPE Mailing Lists

• General announcement list
• ripe-list_at_ripe.net
• Working group lists
• lir-wg_at_ripe.net
• dns-wg_at_ripe.net
• etc.
• For more information
• Send help to ltmajordomo_at_ripe.netgt
• Join the mailing lists and get informed
• http//www.ripe.net/info/maillists.html

12
RIPE Meetings

• About RIPE meetings
• RIPE meets 3 times a year
• 3.5 day meetings
• 280 participants - growing!
• working group meetings, plenary
• presentations, hallway chats
• Come to the meeting!
• keep up to date with Internet
• meet others in the business
• gather information, tips, ideas
• influence directions in Internet in Europe and
  surrounding areas

13
RIPE Meeting attendees for 1998
14
RIPE Meetings

• More information about RIPE meetings
• http//www.ripe.net/meetings/ripe/
• Contact
• ltmeeting_at_ripe.netgt
• Next meeting
• Amsterdam, 20-24. September 1999.
• May 2000 in Budapest!

15
RIPENetwork Coordination Centre
16
Why a NCC ?

• RIPE participation was increasing
• Too much RIPE work to be done on a voluntary
  basis.Some of these activities needed continuity
• Contact point inside outside Europe
• Neutrality and impartiality were an important
  issue
• Co-ordination and support service for
  EuropeanInternet Service Providers

17
RIPE NCC History

• RIPE NCC birth - April 1992
• legal umbrella TERENA (formerly RARE)
• Contributing LIRs in 1995
• financed by model of contributing Local IRs
• participative decision making via Contributors
  Committee
• In 1998 has become independent from TERENA
• Membership Association under Dutch law
• General Assembly of all contributors
• Executive Committee of elected nominees
• Annual Report
• http//www.ripe.net/annual-report/98ar.html

18
Formal Decision Making

• Consensus Model

RIPE NCC proposes activity plan based on input
from RIPE
RIPE NCC proposes budget to accompany activity
plan
General Assembly of members votes on
both activities and budget at yearly
meeting (ltncc-co_at_ripe.netgt)
19
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
• 56 staff (20 nationalities)
• 1,430 participating Local IRs
• 8,428,408 hosts in the European Internet
• 2,250,957 objects in the database

20
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

21
Some Core RIPE NCC Activities

• Registration services
• DNS management
• RIPE Database maintenance
• Routing Registry maintenance
• Co-ordination

22
Registration Services

• IP assignments allocations
• AS assignments
• Database updates
• Support guidance to Local Internet Registries
• Training - procedures policies

23
Address distribution to RIPE region
24
How do you get IP addresses?

• Go to your Local Internet Registry.
• Your provider is probably one or has connectivity
  through one.
• http//www.ripe.net/lir/registries/europe.html
• If you are a provider and think you may need to
  be an LIR? Come and talk to the NCC
• Email new-lir_at_ripe.net

25
1.5 New LIRs per Day
26
Address Space Usage
131,072
81 24 95 97 98
27
DNS Management

• Goals
• ensure proper operation of nameservers
• 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 IRs with feedback
• secondary namservers for ccTLDs
• Updates
• ltauto-inaddr_at_ripe.netgt
• Contact
• ltinaddr_at_ripe.netgt
• We DO NOT register domain names

28
Reverse DNS Quality Report

• 80 of delegating zones good
• Quality improving
• 500 new zones /week
• 45 PRT queries miss at ns.ripe.net
• 52.3 of eligible /24 zones are delegated
• http//www.ripe.net/inaddr/statistics/

29
RIPE DNS Hostcount
30
Additional RIPE NCC Activities

• RIPE support
• organisational support for RIPE meetings
• support to working groups chairs
• Special projects
• Test Traffic project
• CENTR - now at http//www.centr.org
• Coordination
• European Internet Service Providers
• Other organisations - ARIN, APNIC, IANA, ICANN
• Information dissemination
• mailing list discussions
• WWW site http//www.ripe.net
• ftp site ftp//ftp.ripe.net

31
IPv6

• Allocation guidelines published
• Approved by community
• Document and request sent to IANA
• Official address allocation has started
• http//www.ripe.net/registries/ipv6/

32
The RIPE DatabaseIts usage and its usefulness
33
RIPE Database

• Network Management Database
• Data Management
• Local IRs, other ISPs and RIPE NCC
• Software Management
• RIPE NCC with Database Working Group
• Re-implementation in progress

34
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

35
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

36
DB Objects Break 2 Million Mark
37
person Object

• person Mirjam Kuehne
• address RIPE NCC
• address Singel 258
• address NL - 1016 AB Amsterdam
• address Netherlands
• phone [phone]
• fax-no 31 20 535 4445
• e-mail mir_at_ripe.net
• nic-hdl MK16-RIPE
• notify mir_at_ripe.net
• changed mir_at_ripe.net 19950411
• changed mir_at_ripe.net 19970616
• source RIPE

38
role Object

• role RIPE NCC Hostmaster
• address RIPE Network Coordination Centre
• address Singel 258
• address NL - 1016 AB Amsterdam, Netherlands
• phone [phone]
• e-mail hostmaster_at_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_at_ripe.net
• nic-hdl RNH124-RIPE
• changed hostmaster_at_ripe.net 19971002
• source RIPE

39
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_at_ripe.net 19970310
• source RIPE
• / notation possible for inetnum value

40
Querying the Database

• Search keys (Look-up Keys)
• person name, nic-hdl, e-mail
• role name, nic-hdl, e-mail
• maintainer maintainer name
• inetnum network number, network name
• domain domain name
• aut-num AS number
• as-macro AS-macro name
• community community name
• route route value
• Network number and route value are classless
• Network name is a search key, but not unique

41
DB Queries Reach 4.5/sec
(4.5 per sec.)
42
Example query

• whois 193.0.0.0
• inetnum 193.0.0.0 - 193.0.0.255
• netname RIPE-NCC
• admin-c DK58
• tech-c OPS4-RIPE
• route 193.0.0.0/24
• descr RIPE-NCC
• role RIPE NCC Operations
• address Singel 258
• nic-hdl OPS4-RIPE
• person Daniel Karrenberg
• address RIPE Network Coordination Centre (NCC)
• nic-hdl DK58

43
whois -h and -a

• whois -h query a specific host
• whois -h whois.ripe.net
• whois -h whois.arin.net
• whois -a includes the following sources
• RADB
• CANET
• MCI
• ANS
• APNIC
• ARIN
• RIPE

44
whois -t (person)

• person mandatory single
  primary/look-up key
• address mandatory multiple
  
• phone mandatory multiple
  
• fax-no optional multiple
  
• e-mail optional multiple
  look-up key
• nic-hdl mandatory single
  primary/look-up key
• remarks optional multiple
  
• notify optional multiple
  inverse key
• mnt-by optional multiple
  inverse key
• changed mandatory multiple
  
• source mandatory single
• You can also find information about syntax in
  ripe-157 ripe-189 and using the whois -v flag

45
whois -i

• Inverse lookup for special arguments
• Examples
• whois -i tech-c,admin-c,zone-c MK16-RIPE
• whois -i notify mir_at_ripe.net
• whois -i origin AS1234
• whois -i mnt-by AS1234-MNT

46
Example Query
0/0
All less specifics (-L)
193/8
Exact / 1st less specific (default)
193.1/16
1st level more specific (-m)
All more specifics (-M)
Example query 193.1.0.0/16
47
RIPE whois Flags

• i inverse lookup for specified attributes
• L find all Less specific matches
• m find first level more specific matches
• M find all More specific matches
• r turn off recursive lookups
• T type only look for objects of type (inetnum,
  route, etc..)

48
More RIPE whois Flags

• a search all databases
• h hostname search alternate server
• s search databases with source source
• t show template for object of type type
• v verbose information for object of type type
• and dont forget whois help
• (how to query the database)

49
DB Update Procedure

• Unique Keys (Primary Keys)
• person name nic-hdl
• role name nic-hdl
• maintainer maintainer name
• inetnum network number
• domain domain name
• aut-num AS number
• as-macro AS-macro name
• community community name
• route route value origin
• Uniquely identifies object
• Updating an existing object will overwrite the
  old entry hence need unique key

50
E-mail Interface

• ltauto-dbm_at_ripe.netgt
• automatic mailbox
• send all updates to this mailbox
• can use HELP in subject line
• ltripe-dbm_at_ripe.netgt
• send questions and comments to this mailbox
• Test Database
• test-whois.ripe.net
• lttest-dbm_at_ripe.netgt

51
Syntax Checking

• Successful update
• Warnings
• object corrected and accepted
• notification of action taken in acknowledgement
• Errors
• object NOT corrected and NOT accepted
• diagnostics in acknowledgement
• if not understandable send e-mail to
• ltripe-dbm_at_ripe.netgt
• please include object and error reports

52
Example Error Message

• Update FAILED person Mirjam Kuehne
• person Mirjam Kuehne
• address RIPE NCC
• address Singel 258, NL-1016 AB, Amsterdam
• address The Netherlands
• phone [phone]
• fax-no 31 20 535 4445
• e-mail mir_at_ripe.net
• changed mir_at_ripe.net 19980828
• source RIPE
• WARNING date in "changed" (980828) changed to
  19980828
• ERROR mandatory field "nic-hdl" missing

53
Deleting an Object

• Add delete attribute to copy of current object
• person Mirjam Kuehne
• address RIPE NCC
• address Singel 258
• address NL - 1016 AB Amsterdam
• address Netherlands
• phone [phone]
• fax-no 31 20 535 4445
• e-mail mir_at_ripe.net
• nic-hdl MK16-RIPE
• changed mir_at_ripe.net 19980911
• source RIPE
• delete training_at_ripe.net late for training
• Submit to database

54
Nic-hdls (Example)

• person John F. Doe
• nic-hdl AUTO-1JFD
• person Anne Smith
• nic-hdl AUTO-2
• inetnum
• admin-c AUTO-1JFD
• tech-c AUTO-2

JFD304-RIPE
AS519-RIPE
JFD304-RIPE
AS519-RIPE
55
Questions and Answers
56
Organizations
AFRINIC African Network Information
Centre http//www.afrinic.org APNIC Asian
Pacific Network Information Centre http//www.ap
nic.net ARIN American Registry for Internet
Numbers http//www.arin.net CEENet Central
and Eastern European Networking
Association http//www.ceenet.org CENTR Council
of European National Top level domain
Registries http//www.centr.org CIX Commercial
Internet Exchange http//www.cix.org ETSI Europ
ean Telecommunications Standards
Institute http//www.etsi.org EuroISPA European
Internet Service Providers Association http//ww
w.euroispa.org IANA Internet Assigned Numbers
Authority http//www.iana.org
57
Organizations
ICANN Internet Corporation for Assigned Numbers
and Names http//www.icann.net IETF Internet
Engineering Task Force http//www.ietf.org ITU
International Telecommunications
Union http//www.itu.int NANOG North American
Network Operators Group http//www.nanog.org RIP
E Reseaux IP European Network http//www.ripe.
net RIPE NCC RIPE Network Coordination
Centre http//www.ripe.net W3C World Wide Web
Consortium http//www.w3.org