1 / 53

Address Space Application Guidelines - AfNOG Workshop May 2002

Comprehensive overview and definitions of Internet Registry, Local Internet Registry, and Regional Internet Registry services. Learn about allocation and assignment of IP address space, registry system requirements, network plan, and becoming a Local Internet Registry. Disclaimer: Materials used are from Registries, not for domain names. Presenter is not affiliated with Registries. Text in English.

paniz
Download Presentation

Address Space Application Guidelines - AfNOG Workshop May 2002

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. So, you want to apply for address space (or your customers are asking you) AfNOG Workshop, May 2002 Lome, Togo

  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 • I used to for for one of the Regional Registries • I am not speaking on behalf of the Registries! • This is about numbers • not about domain names

  4. IANA RIR /8 LIR (ISP/Enterprise)  /20 ISP / End Users  /32 Who are involved? (ARIN, APNIC, RIPE)

  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 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. Conservation • A few years ago, consensus was that IPv4 address space would run out in the near future • Classless assignments causes this problem to be a medium-term problem now • Conservative address policies help • NAT and other tricks help too • but are not (and should not be) mandatory • you will get the address space you need, you may not get the address space you want

  13. Aggregation • Growth of global routing table faster than Moore’s law • Very serious concern for the growth of the Internet • Currently addressed through aggregation • of multiple customers of the same ISP • of different pieces of the same organisation

  14. But they cannot be relied on forever Projected routing table growth without CIDR CIDR made it work for a while DeploymentPeriod of CIDR Growth of Global Routing Table http://www.telstra.net/ops/bgptable.html

  15. Aggregation and LIRs • LIRs obtain block of allocated address space from RIRs and assign from this block • Different assignments by same LIR can be part of the same routing prefix • ‘Natural’ aggregation of multiple customers • Assignments of ISP LIRs typically match allocated block received from RIR

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

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

  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. Interconnected resilience UpstreamISP Customer services 10 hosts Internal DNS,Web Mail servers 5 hosts Virtual web (name based) Dialup services 16 modems ISP Infrastructure 15 hosts NOC operations Network Plan ’ • Starting off Leased line services 5-8 customers

  20. one loopback interface per assigned router /32 ‘ip unnumbered’ to upstream ISP 5-8 leased line customers UpstreamISP ‘ip unnumbered’ to customers 10 hosts 5 hosts WAN point to point /30 16 dialup modems 15 hosts Network Plan

  21. -numbers of host addresses (interfaces) network-plan: network-plan: network-plan: 16 5 128 • analogue dialup modems, vendor ‘x’ • LAN -web hosting (Name-based hosting) • 5-8 leased line customers (/28) 15 10 4 2 network-plan: network-plan: network-plan: network-plan: • LAN -NOC and Ops management • LAN -mail,DNS, web servers internal • loopback router interfaces • router WAN ports (x 5 lines) Addressing Plan Initial addressing plan

  22. increased number of leased line customers 30 leased linecustomers UpstreamISP 16 hosts- Servers 11 hosts name-based replaced original modem 60 dialupmodems (2PRI) 60 dialupmodems (2PRI) 25 hosts- NOC added new router and LAN for redundancy 8 hosts- 2ndary Servers Network Plan • 6 months later • scale increased • redundancy increasednumberof hosts on all LANs added new dial up equipment

  23. -increases in hosts (interfaces) Changed description network-plan: network-plan: network-plan: 16/ 5/ 128/ 15/ 10/ 4/ 2/ • 2 PRI dialup modems, vendor ‘y’ • LAN -web hosting (Name-based hosting) • 30 leased line customers (pool) 60 11 512 25 16 6 2 network-plan: network-plan: network-plan: network-plan: • LAN -NOC and Ops management • LAN -mail,DNS, web servers internal • loopback router interfaces • router WAN ports (x 8 lines) 0/ 0/ network-plan: network-plan: • 2 PRI dialup modems • LAN-secondary servers 60 8 New hardware Addressing Plan Network plan at 6 months

  24. redundancy of WAN connections now numbered links for BGP4 UpstreamISP A 60 leased linecustomersip unnumbered UpstreamISP B 35 host 11 hosts 240 dialupmodems (8PRI) 240 dialupmodems (8PRI) 40 hosts 8 hosts Network Plan • 12 months total • site redundancy • greater complexity • efficiency added new customer router two pieces of essential equipment

  25. -increases in hosts (interfaces) • -one year total network-plan: network-plan: network-plan: network-plan: 16/60/ 0/60/ 5/11/ 128/512/ 15/25/ 10/16/ 0/8/ 2/2/ 4/6 240 240 11 1020 40 35 8 2 12 • 8 PRI dialup modems, vendor x • 8 PRI dialup modems, vendor y • LAN -web hosting (Name-based hosting) 60 leased line customers (pool) network-plan: network-plan: network-plan: network-plan: network-plan: • LAN -NOC and Ops management • LAN -mail,DNS, web servers internal • LAN-secondary servers • router WAN ports (x 8 lines) • loopback router interfaces Addressing Plan Network plan at 12 months

  26. Can now determine subnet sizes network-plan: network-plan: network-plan: network-plan: 256 256 16 1024 64 64 8 4 16 16/60/240 0/60/240 5/11/11 128/512/1020 15/25/40 10/16/35 0/8/8 2/2/2 4/6/12 • 8 PRI dialup modems, vendor x • 8 PRI dialup modems, vendor y • LAN -web hosting (Name-based hosting) • 60 leased line customers (pool) network-plan: network-plan: network-plan: network-plan: network-plan: • LAN -NOC and Ops management • LAN -mail,DNS, web servers internal • LAN-secondary servers • router WAN ports (x 8 lines) • loopback router interfaces Addressing Plan

  27. Addressing Plan • Addressing plan for network-plan • re-ordered large to small according to relative subnet size • determination of relative subnet addresses network-plan: 0.0.0.0 1024 128/512/1020 60 leased line customers (pool) network-plan: 0.0.4.0 256 16/60/240 8 PRI dial up modems, vendor x network-plan: 0.0.5.0 256 0/60/240 8 PRI dial up modems, vendor y network-plan: 0.0.6.0 64 10/16/35 LAN -mail,DNS, web internal network-plan: 0.0.6.64 64 15/25/40 LAN -NOC and Ops management network-plan: 0.0.6.128 16 5/11/11 LAN -web hosting (Name-based hosting) network-plan: 0.0.6.144 160/8/8 LAN -secondary servers network-plan: 0.0.6.160 16 4/6/12 loopback router interfaces network-plan: 0.0.6.176 4 2/2/2 router WAN ports (x8) • cumulative total 0.0.6.208

  28. Addressing Plan • Addressing plan for network-plan • determination of subnet masks network-plan: 0.0.0.0 255.255.252.0 1024 128/512/1020 60 leased line customers network-plan: 0.0.4.0 255.255.255.0 256 16/60/240 8 PRI dial up modems, vendor x network-plan: 0.0.5.0 255.255.255.0 256 0/60/240 8 PRI dial up modems, vendor y network-plan: 0.0.6.0 255.255.255.192 64 10/16/35 LAN -mail,DNS, web internal network-plan: 0.0.6.64 255.255.255.192 64 15/25/40 LAN -NOC & Ops management network-plan: 0.0.6.128 255.255.255.240 16 5/11/11 LAN -web hosting (Name-based) network-plan: 0.0.6.144 255.255.255.240 160/8/8 LAN -secondary servers network-plan: 0.0.6.160 255.255.255.240 16 4/6/12 loopback router interfaces network-plan: 0.0.6.176 255.255.255.252 4 2/2/2 router WAN ports (x 8 )

  29. Addressing Plan • Addressing plan for network-plan • connect to the Internet (full-time, part-time)? network-plan: 0.0.0.0 255.255.252.0 YES 1024 128/512/1020 60 leased customers network-plan: 0.0.4.0 255.255.255.0 PART 256 16/60/240 8 PRI dial up modems.. network-plan: 0.0.5.0 255.255.255.0 PART 256 0/60/240 8 PRI dial up modems.. network-plan: 0.0.6.0 255.255.255.192 YES 64 10/16/35 LAN -mail,DNS, web internal network-plan: 0.0.6.64 255.255.255.192 YES 64 15/25/40 LAN -NOC & Ops management network-plan: 0.0.6.128 255.255.255.240 YES 16 5/11/11 LAN -web hosting (Name-based) network-plan: 0.0.6.144 255.255.255.240 YES 16 0/8/8 LAN -secondary servers network-plan: 0.0.6.160 255.255.255.240 YES 16 4/6/12 loopback router interfaces network-plan: 0.0.6.176 255.255.255.252 YES 4 2/2/2 router WAN ports (x 8 )

  30. Addressing Plan • Addressing plan complete • total planned for customer assignments /22 • total planned for ISP infrastructure /24 + /23 network-plan: 0.0.0.0 255.255.252.0 YES 1024 128/512/1020 60 leased line customers network-plan: 0.0.4.0 255.255.255.0 PART 256 16/60/240 8 PRI dial up modems.. network-plan: 0.0.5.0 255.255.255.0 PART 256 0/60/240 8 PRI dial up modems.. network-plan: 0.0.6.0 255.255.255.192 YES64 10/16/35 LAN -mail,DNS, web internal network-plan: 0.0.6.64 255.255.255.192 YES64 15/25/40 LAN -NOC & Ops management network-plan: 0.0.6.128 255.255.255.240 YES16 5/11/11 LAN -web hosting (Name-based) network-plan: 0.0.6.144 255.255.255.240 YES 16 0/8/8 LAN -secondary servers network-plan: 0.0.6.160 255.255.255.240 YES 16 4/6/12 loopback router interfaces network-plan: 0.0.6.176 255.255.255.252 YES 4 2/2/2 router WAN ports (x 8 lines ) • detailed,efficient and accurate

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

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

  33. Web Hosting • Name based hosting • single IP address assigned to physical server that hosts several virtual hosts • IP based hosting • single unique IP address assigned to each virtual host

  34. Name Based Hosting • Conserves Address Space • Requires • support of “Host:” header in HTTP requests • HTTP1.1 compliant browsers • Technical Exceptions • SSL certificates • work ongoing at IETF to support name based hosting • Virtual ftp domains with anonymous login

  35. IP Unnumbered • R1 and R2 form a "virtual router" • The serial link has no ip address • All packets arriving at S0 of either router immediately go to its E0 • All packets generated at E0 go onto serial link • Conserves addresses but makes management harder

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

  37. 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 Becoming an LIR?

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

  39. Influencing the RIR • LIRs become member of association controlling LIR • 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

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

  41. The whois Database Introduction and Usage

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

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

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

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

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

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

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

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

  50. 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”

More Related