IP address Allocation & and Requests

AfNOG Workshop, May 2004

Dakar, Senegal

• Definitions: IR, LIR, RIR

• Registry system requirements

• Network plan

• Becoming a LIR

• Policy mechanism

• WHOIS database

Overview

Disclaimer

• This presentation uses materials from the Registries

• This is about numbers– not about domain names

RIPE NCCARIN APNIC

LIRLIRLIR

ISP

End User End UserEnd User

/8

…, /16, …, /20

…, /19, …, /24, …, /29

LACNIC

IANA / ICANN/8

Who are involved?

Internet Registry Goals:

AGGREGATION routing!

CONSERVATION no stockpiling!

REGISTRATION uniqueness / troubleshooting

AfriNIC

Definition:Internet Registry (IR)

• organisation which allocates, assigns and registers Internet resources (IP addresses, ASNs)

Definition: Regional Internet Registry (RIR)

• organisation with regional responsibility for management of Internet resources

• allocates address space to LIRs

• address registration services, co-ordination and policy development

• APNIC, ARIN, RIPE-NCC

• AfriNIC, LACNIC in formation

• Must be neutral and consensus-based

RIR Service Regions

AfriNIC

LACNIC

Definition: Local Internet Registry (LIR)

– Gets allocated address space from RIR– assigns address space to its customers– Usually an ISP

• Very small ISPs get IP address space from their upstream provider

Definition: Allocation /Assignment

• Allocation– A block of address space held by an IR for

subsequent allocation or assignment• Not yet used to address any networks

• Assignment– A block of address space used to address an

operational network – May be provided to LIR customers, or used for

an LIR’s infrastructure (‘self-assignment’)

Definition: Allocation and Assignment

RIRRIR

CustomerCustomer

Allocates IP addressesAllocates IP addresses Assigns IP addressesAssigns IP addressesor Reassignsor Reassigns

LIRLIR

LIRLIR

Registry system requirements

• Assignment of globally unique (IP) address space

• Registration

• Conservation of address space

• Minimize routing information (aggregation)

• Scalable

• Fair

Definition: PI and PA

• Provider Independent (Portable)• Customer holds addresses independent from ISP

• Customer keeps addresses when changing ISP

• Bad for size of routing tables

• Bad for QOS: routes may be filtered, flap-dampened

• Provider Aggregatable (Non-portable)• Customer uses ISP’s address space

• Customer must renumber if changing ISP

• Only way to effectively scale the Internet

Do you need to become LIR?

• You are an Organization/ISP that need more than /23 Public IP addresses

• You need your Own IP address (independence from Upstream Provider)

• Your are multihomed and one of your peer doesn’t want to announce a small block from another provider. (Aggregation)

Why so much NAT

• False perception that RIRs will not give an LIR needed/justified space

• Difficulty of a large ISP (cable, DSL, …) to do customer-by-customer need-based allocation

NAT????

• So you have a NATted network• What can you do?• Design actual address space need if the

NATs were not there• Contact your RIR/NIR with these data and a

plan, as justification for a un-NATted portable IP allocation

• Give your customers real addresses!

Ask for how much space?

• Where do you need the space for?

• Guessing on amount of space needed won’t work:– Not getting enough space doesn’t work– Getting too much space leaves unused space

go to waiste

• Need an addressing plan

Implication of becoming an LIR

• Advantages– independent allocation

from RIR

– independent from LIR of upstream provider

• Disadvantages– has overhead

– costs resources

– costs $$$ (CFA, cedis, ...)

– possible need to renumber from upstream LIR block

Addressing Plan

• Identify components of network• Customer services

• ISP internal infrastructure

• Identify phases of deployment• Starting off, 6 months, 12 months

• Identify equipment and topology changes• Need for redundancy

• Need for increased scale

Responsibilities of an LIR

• Be familiar with latest IP policies

• Follow goals of Registry System– conservation– aggregation– registration

• Manage allocations responsibly

• Keep up to date records– internally– WHOIS database

Process to become LIR

Remplir le formulaire

Signer le RSAPayer les

redevances

billing@ripe.net<new-lir@ripe.net>

Allocation

Assignationsub-allocation

1

2

3

4

AW=0ARIN process

Allocation Request

ARIN Form :

http://www.arin.net/library/templates/net-isp.txt

RIPE NCC form:

http://www.ripe.net/ripe/docs/first-allocation.html

Network plan RIPE NCC

subnet: /25 /25 /25 /25 dynamic dial-up POP1

subnet: /25 0 /25 /25 dynamic dial-up POP 2

subnet: /26 /27 /27 /27,/28 office LAN – City 1

subnet: /27 0 /28 /27 web/mail/ftp servers A

subnet: /27 /28 /28 /27 web/mail/ftp servers B

subnet: /28 /28 /28 /28 training room LAN City 1

totals: /24,/25,/28 /25,/26 /24,/26,/28 /24,/25

Minimizing space requirements

• Dynamic addresses for dialups

• Classless assignments• Utilisation and efficiency guidelines

– 25% immediately, 50% in one year– operational needs; no reservations

• RFC1918

• Name-based web hosting

• Unnumbered interfaces

Private Address Space

• RFC1918– 10/8, 172.16/12, 192.168/16– saves public address space– allows for more flexibility

• Suitable when– hosts do not require access to other networks– access to outside services through application

layer GW

• Not a solution for address space shortage!

Whom to ask for address space

• Ask LIR of your (upstream) ISP

• Become LIR yourself! When?– you have customers who need addresses– you need more than a /21 in 1 year

Influencing the RIR

• LIRs become member of association controlling RIR– LIR’s control RIR, RIR doesn’t control LIRs

• Policies developed in open forums

• Co-ordinated between RIRs and with IANA

• Based on consensus rather than rules

• Assures fair and open process

Policy Development Process

• Policy (changes) can be suggested by– RIR Members/Local IRs – RIR staff– Public at large

• Policy must be– fair to all– ‘good’ for the Internet– consistent with global policies

The whois Database

Introduction and Usage

Overview

• What is the whois database?

• Why use it?

• Who uses it?

• Database query process

• Database update process

What is the whois Database?

• Network Management Database

• Contains information about– address space– DNS domains– IP routing policies– contact information

Why use the Database?

• Queries– Ascertain custodianship of a resource– Obtain details of technical contacts for a

network– Investigate security incidents– Track source of network abuse or “spam” email

Who uses the Database?

• Queries– Internet Service Providers– Site network managers and engineers– Any Internet user

• Updates– Internet registries (RIRs, LIRs)– Internet Service Providers– Anyone who holds an Internet resource

Database Objects• Database object types

OBJECT PURPOSEperson contact persons role contact groups/rolesinetnum IPv4 address allocations/assignmentsinet6num IPv6 address allocations/assignmentsaut-num autonomous system numberas-macro group of autonomous systemsdomain reverse domainsroute prefixes being announcedmntner (maintainer) database authorisation

Contact InformationExample object - ‘person’

person:

address:

address:

country:phone:

fax-no:

e-mail:

nic-hdl:mnt-by:

changed:source:

Brajesh Jain B 115 SARVODAYA ENCLAVENEW DELHI 110017 TH +91-11-6864138+91-11-6865888bcjain@ndb.vsnl.net.inBJ16-APMAINT-IN-ESTEL-BCJbcjain@ndb.vsnl.net.in 20000429

APNIC

AttributesAttributes ValuesValues

Network Information

Example object - ‘inetnum’

inetnum:netname:descr:descr:country:admin-c:tech-c:mnt-by:mnt-lower:changed:source:

203.113.0.0 - 203.113.31.255 TOTNET-APTelephone Organization of THAILAND(TOT) Telephone and IP Network Service Provider TH

NM18-APRC80-APAPNIC-HMMAINT-TH-SS163-AP

hostmaster@apnic.net 19990922APNIC

AttributesAttributes ValuesValues

Database Query - Search Keys

OBJECT TYPEOBJECT TYPE ATTRIBUTES - SEARCH KEYS ATTRIBUTES - SEARCH KEYS

** whois supports queries on any of these objects/keyswhois supports queries on any of these objects/keys

name, nic-hdl, e-mailname, nic-hdl, e-mailmaintainer namenetwork number, namedomain nameas numberas-macro nameroute valuenetwork number, name

personrolemntnerinetnumdomainaut-numas-macrorouteinet6num

Database Query - Inetnum

• NotesNotes• Incomplete addresses padded with “.0”Incomplete addresses padded with “.0”• Address without prefix interpreted as “/32”Address without prefix interpreted as “/32”

% whois 203.127.128.0 - 203.127.159.255

% whois SINGNET-SG% whois 202.127.128.0/19

inetnum: 203.127.128.0 - 203.127.159.255netname: SINGNET-SG descr: Singapore Telecommunications Ltd descr: 31, Exeter Road, #02-00, Podium Blockdescr: Comcentre, 0923 country: SGadmin-c: CWL3-APtech-c: CWL3-APmnt-by: APNIC-HM changed: hostmaster@apnic.net 19990803 source: APNIC

Database Query - Inetnum

• RIPE extended whois clientftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.0.tar.gz

• Flags used for inetnum queriesNone find exact match

- L find all less specific matches

- m find first level more specific matches

- M find all More specific matches

- r turn off recursive lookups

210.8.30/23210.8.30/23

Database Query - Inetnuminetnum hierarchy: whois 210.8.0.0/16

All less All less specifics (-L)specifics (-L) 210/7210/7

0/00/0

Exact matchExact match 210.8/16210.8/16

All moreAll morespecifics (-M)specifics (-M)

1st level1st levelmoremoreSpecific (-m)Specific (-m)

‘‘-M’ will find all assignments in a range in the database-M’ will find all assignments in a range in the database

inetnum: 202.144.0.0 - 202.144.31.255netname: SILNET-APdescr: Satyam Infoway Pvt.Ltd.,.....inetnum: 202.144.13.104 - 202.144.13.111netname: SOFTCOMNETdescr: SOFTCOM LAN (Internet)IP......inetnum: 202.144.1.0 - 202.144.1.255descr: SILNETdescr: Satyam Infoway's Chennai LAN.....

% whois -M 202.144.0.0/19

Database Query - Inetnum