1 / 114

Welcome! APNIC Members Training Course

Welcome! APNIC Members Training Course. Effective IP Address Management Asia Pacific Policies and Procedures 3 September 2002, Kitakyushu, Japan. Introduction. Presenters Miwa Fujii – Training Officer miwa@apnic.net George Kuo – Internet Resource Analyst george@apnic.net

elewa
Download Presentation

Welcome! APNIC Members Training Course

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. Welcome!APNIC Members Training Course Effective IP Address Management Asia Pacific Policies and Procedures 3 September 2002, Kitakyushu, Japan

  2. Introduction • Presenters • Miwa Fujii – Training Officer • miwa@apnic.net • George Kuo – Internet Resource Analyst • george@apnic.net • Arth Paulite – Internet Resource Analyst • arth@apnic.net

  3. Assumptions & Objectives • Assumptions • Are current APNIC member or a prospective member • Have not submitted many requests • Are not familiar or up to date with policies • Are not familiar with procedures • Objectives • Provide overview of current policies • To minimise “pain” of requesting resources • To promote awareness

  4. Session 1(9-10.30) - General Introduction to APNIC(5) What is the role of APNIC? RIR Goals & Principles(12) Short background APNIC Policies(25) All current APNIC policies Policies & Procedures(33) Additional guidelines Session 2(11-12.30) - Operational Requesting resources(42) Overview, forms, tips etc. IP Management(53) Planning your allocation APNIC Database(65) Short intro to the whois DB Reverse DNS(86) Basic concepts Summary(95) Schedule

  5. Introduction to APNIC Asia Pacific Network Information Centre

  6. Intro What is APNIC? • Regional Internet Registry for the Asia Pacific • Regional authority for Internet Resource distribution • IPv4 & IPv6 addresses, ASNs, reverse dns delegation • Industry self-regulatory body • Participation by those who use Internet resources • Consensus-based, open and transparent • Non-profit, neutral and independent • Open membership-based structure

  7. Intro APNIC is not… • Not a network operator • Does not provide networking services • Works closely with APRICOT forum • Not a standards body • Does not develop technical standards • Works within IETF in relevant areas (IPv6 etc) • Not a domain name registry or registrar • Will refer queries to relevant parties

  8. Intro Internet Registry Hierarchy

  9. Intro APNIC Region

  10. Intro APNIC Services & Activities • Resource services & registration • IPv4, IPv6, ASNs, in-addr.arpa, whois • Authoritative registration server: whois • Policy development and implementation • Membership reviews and approves policy • Information dissemination • APNIC meetings • Training courses & seminars

  11. Questions ? • Want to know more about APNIC and the APNIC meetings? • Come to the newcomer’s orientation this afternoon at 18.00.

  12. RIR Goals & Principles Definitions, RIR Goals, Brief History & Policy Development

  13. Policy Background Definitions- Allocation and 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’)

  14. Policy Background /8 APNIC Allocation /20 Member Allocation /24 /26 /25 Allocation and Assignment APNICAllocatesIP addresses APNIC MemberAssignsIP addresses Customer / End User Customer Assignments

  15. Policy Background Portable & Non-portable • 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 • Non-portable • Customer uses ISP’s address space • Customer must renumber if changing ISP • Only way to effectively scale the Internet

  16. Policy Background Classful and Classless • Classful(Obsolete) • Wasteful address architecture • network boundaries are fixed at 8, 16 or 24 bits (class A, B, and C) • Classless(Best Current Practice) • Efficient architecture • network boundaries may occur at any bit (e.g. /12, /16, /19, /24 etc) • CIDR • Classless Inter Domain Routing architecture • Allows aggregation of routes within ISPs infrastructure

  17. Policy Background A (8 bits) Host address (24 bits) B (16 bits) Host (16 bits) C (24 bits) Host (8 bits) Classful Address Architecture 128 networks x 16M hosts Class A (50% of all address space) 0 16K networks x 64K hosts Class B (25%) 10 2M networks x 256 hosts Class C (12,5%) 110 • Classful addressing obsolete: • inefficient • depletion of B space • too many routes from C space

  18. Policy Background Host (13 bits) 19 bits 20 bits Host (12 bits) Host (8 bits) 24 bits 26 bits Host (6 bits) Classless Address Architecture 4M hosts /10 Host address (22 bits) 10 bits 8192 hosts /19 4096 hosts /20 4096 hosts /24 64 hosts /26 • Network boundaries may occur at any bit

  19. Policy Background CIDR Aggregation BGP announcements 202.128.0.0/16 ISP 202.128.0.0/16 Provider Aggregation Provider Aggregation Customer Customer Customer 202.128.1.0/25 202.128.32.0/29 202.128.3.0/26

  20. Policy Background APNIC Policies - Objectives • Conservation • Ensuring efficient use and conservation of resources • Aggregation • Limiting growth of routable prefixes • Registration • Registering the Internet resources in a public db • Uniqueness • Global visibility • Fairness and consistency • Equal consideration irrespective of external factors

  21. Policy Background Why do we need Policies ?- Global IPv4 Delegations

  22. Policy Background But they cannot be relied on forever Projected routing table growth without CIDR Moore’s Law and CIDR made it work for a while DeploymentPeriod of CIDR Why do we need Policies? - Growth of Global Routing Table http://bgp.potaroo.net/as1221/bgp-active.html • (as of 19 July 2002)

  23. Policy Background Routing Table Prefix Distribution

  24. Policy Background APNIC Policy Development • Based on global and regional policies • Global: RFC2050 • Regional: ‘Policies for Address Space Management in the Asia Pacific Region’ • http://www.apnic.net/docs/add-manage-policy.html • Policy development • APNIC and APNIC members • Other RIRs and wider community • Policy implementation • APNIC and APNIC members

  25. APNIC IPv4 Address Policies Allocation & Assignment Policies

  26. Policies APNIC Policy Environment • IP addresses not freehold property • Internet resources are public resources • ‘Ownership’ is contrary to management goals • Need to avoid the mistakes of the past • Assignments & allocations on lease basis • Confidentiality & security • APNIC to observe and protect trust relationship • Non-disclosure agreement signed by staff

  27. Policies APNIC Allocation Policies • Allocations as Non portable address space • Provider responsible for aggregation • Customer assignments must be non-portable • Allocations based on demonstrated need • Detailed documentation required • All address space held to be declared • Address space to be obtained from one source • routing considerations may apply • Stockpiling not permitted

  28. Policies Initial IPv4 Allocation Criteria • Have used a /22 from upstream provider • Demonstrated efficient previous address usage OR • Show immediate need for /22 • Can include customer projections & infrastructure equipment • Provide detailed plan for use of /21 within a year • Renumber to new space within 1 year • Meet all policy requirements • Applicants may be required to show purchase receipts

  29. Policies Address Assignment Policies • Assignments based on requirements • Demonstrated through detailed documentation • Justification through description of usage, and number of hosts initially, in 6 months, and one year • Assignment should maximise utilisation • (minimise wastage) • Classless assignments, showing use of VLSM • Size of allocation • Sufficient for up to 12 months requirement

  30. Policies Small Multihoming Assignment Policy • Applicants currently multihomed OR • Demonstrate a plan to multihome within 1month • Agree to renumber out of previously assigned space • Demonstrate need to use 25% of requested space immediately and 50% within 1 year • Meet all policy requirements or have the assignment revoked

  31. Policies IPv4 Assignment policy for IXPs • /24 assignment for IX point’s Transit LAN • Must agree not to announce the space to the global routing table • IXP must be able to demonstrate “open peering policy” • Have 3 or more peers • APNIC has a reserved block of space from which to make IXP assignments

  32. Questions ?

  33. APNIC Policies & Procedures Policies, Procedures and Best Current Practices

  34. P&P& BCP Virtual web hosting • Name based hosting • ‘Strongly recommended’ • Use ‘infrastructure’ field to describe web servers • IP based hosting • Permitted on technical grounds for SSL, virtual ftp.. • Use ‘infrastructure’ field to describe web servers • Special verification for IP based • If more than /22 used for this purpose • Requestor must send list of URLs of virtual domain and corresponding IP address

  35. P&P& BCP Cable, DSL services • 1:1 contention ratio • Can be either statically or dynamically assigned • Means 1 IP address per customer • Greater than 1:1 contention ratio • Preferred because conserves address space • Choice of addressing is optional for members • dynamic addressing is encouraged • Verification for DSL Services • Equipment details • Ex: BRAS, Number of ports • Purchase requests

  36. P&P& BCP New Cable Service • Bootstrapping criteria for new cable service • Applies to startup providers commencing new cable • Allocation size based on assumption that requestor will assign a /24 to each CMTS in their network • Complete ‘additional info’ with make, model & quantity • Purchase receipts for equipments may be asked • Assignments greater than /30 need to be • Requested through second opinion process • Registered separately in the database

  37. P&P& BCP Cable / DSL • Cable, DSL services • Special verification for 1:1 (permanently on-line) • For anything over a /22 in total, verification through customer list for random head-ends or other alternative • For residential networks • Do not need to register on-site tech-c, however ISPs tech-c can be used

  38. P&P& BCP Renumbering • One-for-one exchange to assist renumbering • needs confirmation from upstream ISP to confirm renumbering will take place • ‘No Questions Asked’ return prefix policy • swap 3 or more discontiguous prefixes (ISP or customers) for single prefix, no charge ftp://ftp.apnic.net/apnic/docs/no-questions-policy • Form for returning addresses ftp://ftp.apnic.net/apnic/docs/address-return-request

  39. P&P& BCP Subsequent Allocations • 80% overall utilisation • Demonstrated conservative assignments • Correct database registrations for customers • Fix inconsistencies before next allocation • Amount depends on “usage” rate • How much, how fast, allocate for up to one year • Contiguous allocation not guaranteed • But every effort made

  40. P&P& BCP Summary • All address space held should be documented • Check other RIR, NIR databases for historical allocations • ‘No reservations’ policy • Reservations may never be claimed • Fragments address space • Customers may need more or less address space than is actually reserved • Aggregation • LIR announces allocation as a single aggregate

  41. Questions ?

  42. Requesting Internet Resources

  43. Req IP Requesting IP addresses- Overview Put together an Addressing Plan <hostmaster@apnic.net> Register allcustomerassignments in db Requestan Allocation Second opinion request 80% utilisation in Allocation ISP Request (APNIC-084) For customer assignments(APNIC-073) whois.apnic.net Request newAllocation APNIC-084

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

  45. Addressing Plan Example 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 mgmt 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 Connectto Internet Deploymentphases subnet size Description subnet mask relativeprefix

  46. Req IP Address Request Forms • Allocation Request • ISP Address Request Form • http://www.apnic.net/services/ipv4/ • Assignment Request (Second opinion) • Second opinion Request Form • http://cgi.apnic.net/apnic-bin/second-opinion-request.pl

  47. Req IP Hostmaster Administrivia • <hostmaster@apnic.net> mailbox • Is filtered to accept requests from members only • Requires member account name • Subject: IP Address Request [CONNECT-AU] • Ticketing system • Every request is assigned a ticket • Ticket # is a confirmation that your request has been well received • New staff at LIR • Require an ‘introduction’ to hostmasters • To ensure confidentiality

  48. Req IP Requesting IP addresses • Create person objects and a company maintainer object before you apply. • Read the “Tips” document at: • http://www.apnic.net/info/faq/isp-request-tips.html • Use correct account name for your request • Always use same ticket # for same request • Please keep # in subject line of email eg. • [APNIC #14122] [CHINANET-CN]

  49. Req IP Requesting IP addresses • Provide a detailed description of your network topology • More information provided = less iteration • Make sure the request has correct format & syntax • http://www.apnic.net/services/help/isp_txt/ • http://ftp.apnic.net/apnic/docs/second-opinion-request • Provide list of all current addresses held • Additional comments field • Topology map, deployment plan etc • Any additional info that supports the request • Plan to adopt best current practice

  50. Req IP Requesting New Allocation- Checklist • Utilisation in allocation is 80% • All customer assignments are registered in the whois database • With accurate and up-to-data information • Sufficient documentation to support address requirement • Membership fee is paid

More Related