John Crain. NATO Workshop, June The Internet Registry System How to run a Local IR NATO Workshop Tartu June 2000 John Crain
John Crain. NATO Workshop, June RIPE RIPE NCC Internet Registry System Running a Local Internet Registry –IP address distribution & registration –Reverse Delegation –RIPE database Overview
John Crain. NATO Workshop, June Questions always welcome!
John Crain. NATO Workshop, June Reseaux IP Européens
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June How RIPE Works RIPE chair –Chair: Rob Blokzijl (Nikhef) How does it work? –Working groups –Mailing lists –Meetings
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June Subscribe to RIPE Mailing Lists General announcement list – Working group lists – –etc. For more information –Send “help” to Join the mailing lists and get informed
John Crain. NATO Workshop, June RIPE Meetings 3 times a year ~3.5 day long 300+ participants Working group meetings Plenary Presentations Long breaks Informal chats
John Crain. NATO Workshop, June 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, September 2000 –
John Crain. NATO Workshop, June RIPE Meeting Attendees in 1999 Total 857 other
John Crain. NATO Workshop, June RIPE Meeting Attendance per Organisational Category 1999
John Crain. NATO Workshop, June Global Context World-wide Internet Technical Development & Standards Body World-wide Operators Forum EU Operators USA Operators Asian Operators IETF IEPG RIPE APRICOT NANOG
John Crain. NATO Workshop, June RIPE Network Coordination Centre
John Crain. NATO Workshop, June What is the RIPE NCC? Not-for-profit association under Dutch law 8 years of history members (mainly ISPs, but open to anyone) Co-ordination and support services for ISPs
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June RIPE NCC Membership
John Crain. NATO Workshop, June New LIRs per Region 1999 Africa: 8 Europe : 551 (Including Turkey, Georgia and Kyrgyz Republic) Middle-East: 31 (including Israel and Iran)
John Crain. NATO Workshop, June New LIRs in 2000
John Crain. NATO Workshop, June RIPE NCC Activities (1) Registration Services –IPv4 addresses –IPv6 addresses –AS numbers –Reverse domain name delegation – LIR Training Courses Member Services
John Crain. NATO Workshop, June RIPE NCC Activities (2) 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) Public Services
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June Global Internet Registry System
John Crain. NATO Workshop, June 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.
John Crain. NATO Workshop, June ICANN Structure of ICANN The Internet Corporation for Assigned Names and Numbers ProtocolsDNSAddresses IETF, ITU, WWWC, ETSI ARIN RIPE NCC 3 Supporting Organizations
John Crain. NATO Workshop, June 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)
John Crain. NATO Workshop, June RIR Service Regions RIPE NCCARIN APNIC
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June Address Distribution Global Authority RIR /8 LIR /20 +RIPE NCC Members End Users /32 + Anybody with a network/host
John Crain. NATO Workshop, June Running a Local Internet Registry
John Crain. NATO Workshop, June How to get IP addresses? Go to your Local Internet Registry. –Your provider is probably one or is connected to one If you are a provider and think you may need to be an LIR? Contact NCC
John Crain. NATO Workshop, June Becoming a LIR Complete application form (ripe-160) 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 –
John Crain. NATO Workshop, June Address Space Usage 98% 97% 96,5% 40,1% 97% 60%
John Crain. NATO Workshop, June IPv6 Draft allocation guidelines –currently under revision by community Address allocation started –17 sub-TLAs allocated by RIPE NCC
John Crain. NATO Workshop, June DNS Activities
John Crain. NATO Workshop, June RIPE NCC Hostcount per Quarter
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June Request Reverse Delegation Send domain object to –an automatic mailbox Tool will –check if zone is correctly setup –check assignment validity –(try to) enter object to RIPE DB Questions, Comments to
John Crain. NATO Workshop, June Reverse DNS Quality Report 80% of delegating zones good Quality improving ~500 new zones /week 52.3% of eligible /24 zones are delegated
John Crain. NATO Workshop, June The RIPE Database Its usage and its usefulness
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June RIPE Database RIPE whois server whois.ripe.net RIPE whois client ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase tar.gz Glimpse full text search Database documentation
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June Almost 5 Million Objects 4,885,891 Rate: 300, 000 p.m.
John Crain. NATO Workshop, June ‘person’ Object person:Mirjam Kuehne address: RIPE NCC address: Singel 258 address: NL AB Amsterdam address: Netherlands phone: fax-no: nic-hdl:MK16-RIPE changed: changed: source:RIPE
John Crain. NATO Workshop, June ‘role’ Object role:RIPE NCC Hostmaster address:RIPE Network Coordination Centre address: Singel 258 address: NL AB Amsterdam, Netherlands phone: trouble:Work days CET: phone XXX trouble:Outside Business Hours: phone YYY admin-c: JLC2-RIPE tech-c:MK16-RIPE nic-hdl:RNH124-RIPE source:RIPE
John Crain. NATO Workshop, June Network Object inetnum: 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 source:RIPE “/” notation possible for inetnum value
John Crain. NATO Workshop, June Querying the Database Search keys (Look-up Keys) –personname, nic-hdl, –rolename, nic-hdl, –maintainermaintainer name –inetnumnetwork number, network name –domaindomain name –aut-numAS number –as-macroAS-macro name –communitycommunity name –routeroute value Network number and route value are classless Network name is a search key, but not unique
John Crain. NATO Workshop, June Queries Reach 7/sec Average 7/sec
John Crain. NATO Workshop, June Example query whois inetnum: netname:RIPE-NCC admin-c:DK58 tech-c:OPS4-RIPE route: /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
John Crain. NATO Workshop, June 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
John Crain. NATO Workshop, June whois -t (person) person: [mandatory] [single] [primary/look-up key] address: [mandatory] [multiple] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] [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] [ ]
John Crain. NATO Workshop, June whois -i Inverse lookup for special arguments Examples: –whois -i tech-c,admin-c,zone-c MK16-RIPE –whois -i notify –whois -i origin AS1234 –whois -i mnt-by AS1234-MNT
John Crain. NATO Workshop, June Example Query 0/0 193/ /16 All more specifics (-M) All less specifics (-L) Exact / 1st less specific (default) 1st level more specific (-m) Example query : /16
John Crain. NATO Workshop, June RIPE whois Flags iinverse 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..)
John Crain. NATO Workshop, June 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 don’t forget whois help (how to query the database)
John Crain. NATO Workshop, June DB Update Procedure Changing an object –add the changed line to the new version of object value: address and date –keep the same primary key *do not forget authentication (password, PGP key) Deleting an object –add delete line to the exact copy of current object –value: address, reason and date –submit to
John Crain. NATO Workshop, June DB Update Procedure Unique Keys (Primary Keys) –personname + nic-hdl –rolename + nic-hdl –maintainermaintainer name –inetnumnetwork number –domaindomain name –aut-numAS number –as-macroAS-macro name –communitycommunity name –routeroute value + origin Uniquely identifies object Updating an existing object will overwrite the old entry hence need unique key
John Crain. NATO Workshop, June Interface –automatic mailbox –send all updates to this mailbox –can use HELP in subject line –send questions and comments to this mailbox Test Database –test-whois.ripe.net –
John Crain. NATO Workshop, June 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 to –please include object and error reports
John Crain. NATO Workshop, June 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: fax-no: changed: source: RIPE WARNING: date in "changed" (980828) changed to *ERROR*: mandatory field "nic-hdl" missing
John Crain. NATO Workshop, June Deleting an Object Add delete attribute to copy of current object person:Mirjam Kuehne address:RIPE NCC address: Singel 258 address: NL AB Amsterdam address: Netherlands phone: fax-no: nic-hdl:MK16-RIPE source:RIPE late for training Submit to database
John Crain. NATO Workshop, June Nic-hdl’s (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
John Crain. NATO Workshop, June Questions?
John Crain. NATO Workshop, June Organizations AFRINICAfrican Network Information Centre APNICAsian Pacific Network Information Centre ARINAmerican Registry for Internet Numbers CEENetCentral and Eastern European Networking Association CENTRCouncil of European National Top level domain Registries CIXCommercial Internet Exchange ETSIEuropean Telecommunications Standards Institute EuroISPAEuropean Internet Service Providers Association IANAInternet Assigned Numbers Authority
John Crain. NATO Workshop, June Organizations ICANNInternet Corporation for Assigned Numbers and Names IETFInternet Engineering Task Force ITUInternational Telecommunications Union NANOG North American Network Operators Group RIPEReseaux IP European Network RIPE NCCRIPE Network Coordination Centre W3CWorld Wide Web Consortium