1 / 40

IP address Allocation & and Requests

IP address Allocation & and Requests. AfNOG Workshop, May 2004 Dakar, Senegal. Overview. Definitions: IR, LIR, RIR Registry system requirements Network plan Becoming a LIR Policy mechanism WHOIS database. Disclaimer. This presentation uses materials from the Registries

havyn
Download Presentation

IP address Allocation & and Requests

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. IP address Allocation & and Requests AfNOG Workshop, May 2004 Dakar, Senegal

  2. Overview • Definitions: IR, LIR, RIR • Registry system requirements • Network plan • Becoming a LIR • Policy mechanism • WHOIS database

  3. Disclaimer • This presentation uses materials from the Registries • This is about numbers • not about domain names

  4. Who are involved? /8 IANA / ICANN /8 ARIN RIPE NCC APNIC AfriNIC LACNIC …, /16, …, /20 LIR LIR LIR ISP …, /19, …, /24, …, /29 End User End User End User Internet Registry Goals: AGGREGATION routing! CONSERVATION no stockpiling! REGISTRATION uniqueness / troubleshooting

  5. Definition:Internet Registry (IR) • organisation which allocates, assigns and registers Internet resources (IP addresses, ASNs)

  6. 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

  7. RIR Service Regions AfriNIC LACNIC

  8. 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

  9. 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’)

  10. Definition: Allocation and Assignment RIR LIR Allocates IP addresses Assigns IP addresses or Reassigns LIR Customer

  11. Registry system requirements • Assignment of globally unique (IP) address space • Registration • Conservation of address space • Minimize routing information (aggregation) • Scalable • Fair

  12. 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

  13. 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)

  14. 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

  15. 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!

  16. 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

  17. 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 Implication of becoming an LIR

  18. 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

  19. 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

  20. Process to become LIR Remplir le formulaire 1 <new-lir@ripe.net> 3 billing@ripe.net Signer le RSA Payer les redevances 2 4 Allocation ARIN process AW=0 sub-allocation Assignation

  21. 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

  22. 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

  23. 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

  24. 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!

  25. 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

  26. 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

  27. 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

  28. The whois Database Introduction and Usage

  29. Overview • What is the whois database? • Why use it? • Who uses it? • Database query process • Database update process

  30. What is the whois Database? • Network Management Database • Contains information about • address space • DNS domains • IP routing policies • contact information

  31. Whyuse 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

  32. Whouses 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

  33. Database Objects • Database object types OBJECTPURPOSE person contact persons role contact groups/roles inetnum IPv4 address allocations/assignments inet6num IPv6 address allocations/assignments aut-num autonomous system number as-macro group of autonomous systems domain reverse domains route prefixes being announced mntner (maintainer) database authorisation

  34. Contact Information Example object - ‘person’ Values Attributes • 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 20000429APNIC

  35. Network Information Example object - ‘inetnum’ Attributes Values inetnum:netname: descr: descr: country: admin-c: tech-c: mnt-by: mnt-lower: changed: source: 203.113.0.0 - 203.113.31.255TOTNET-APTelephone Organization of THAILAND(TOT)Telephone and IP Network Service ProviderTH NM18-AP RC80-AP APNIC-HM MAINT-TH-SS163-AP hostmaster@apnic.net 19990922 APNIC

  36. person • role • mntner • inetnum • domain • aut-num • as-macro • route • inet6num • name, nic-hdl, e-mail • name, nic-hdl, e-mail • maintainer name • network number, name • domain name • as number • as-macro name • route value • network number, name Database Query - Search Keys OBJECT TYPE ATTRIBUTES - SEARCH KEYS • * whois supports queries on any of these objects/keys

  37. 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 19990803source: APNIC Database Query - Inetnum % whois 203.127.128.0 - 203.127.159.255 % whois 202.127.128.0/19 % whois SINGNET-SG • Notes • Incomplete addresses padded with “.0” • Address without prefix interpreted as “/32”

  38. Database Query - Inetnum • RIPE extended whois client ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-3.0.tar.gz • Flags used for inetnum queries None 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

  39. Database Query - Inetnum inetnum hierarchy: whois 210.8.0.0/16 0/0 All less specifics (-L) 210/7 210.8/16 Exact match 1st level more Specific (-m) 210.8.30/23 All more specifics (-M)

  40. inetnum: 202.144.0.0 - 202.144.31.255 • netname: SILNET-AP • descr: Satyam Infoway Pvt.Ltd., • ..... • inetnum: 202.144.13.104 - 202.144.13.111 • netname: SOFTCOMNET • descr: SOFTCOM LAN (Internet)IP. • ..... • inetnum: 202.144.1.0 - 202.144.1.255 • descr: SILNET • descr: Satyam Infoway's Chennai LAN • ..... Database Query - Inetnum ‘-M’ will find all assignments in a range in the database % whois -M 202.144.0.0/19

More Related