APNIC Policy Update

1st TWNIC IP Open Policy Meeting

3 December, 2003

Taipei, Taiwan

Internet Registry Allocation and Assignment

Policies

Overview of APNIC policies

• Definitions

• Background

• Objectives

• Environment

• Allocation & Assignment Policies

Policies

Allocation and Assignment

Allocation“A block of address space held by an IR (or

downstream ISP) 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’)

Policies

Sub-Allocation

/22

/8

APNIC Allocation

Allocation and Assignment

/24

/20

Member Allocation

Customer Assignments/25

Policies

/26/27 /26

APNICAllocates

to APNIC Member

APNIC Member

Customer / End User

Assignsto end-user

Allocatesto downstream

Downstream Assigns

to end-user

Portable & non-portable

Portable Assignments– Customer addresses independent from ISP

• Keeps addresses when changing ISP

– Bad for size of routing tables– Bad for QoS: routes may be filtered, flap-

dampened

Non-portable Assignments– Customer uses ISP’s address space

• Must renumber if changing ISP

– Only way to effectively scale the Internet

Policies

Allocation & assignment terms

Policies

• Terms used in ‘status’ field in the APNIC database

• Describes “portability” of the address space

/8

/25Assignment

Assigned Non-Portable

/8

/26

APNIC Allocation

Assigned PortableAssignment

APNIC Allocation

/26Assignment

Assigned Non-Portable

Sub-allocation /22

/20Member AllocationAllocated Portable

Allocated Non-Portable

Aggregation and “portability”

Aggregation

(Non-portable Assignments) (Portable Assignments)

No Aggregation

BGP Announcement (1) BGP Announcements (4)

ISP Allocation

Customer Assignments Customer Assignments

ISP

Policies

Aggregation and “portability”

ISP D ISP C

ISP A ISP B

Internet

ISP D ISP C

ISP A ISP B

Internet

Aggregation

(Non-portable Assignments) (Portable Assignments)

No Aggregation

(4 routes) (21 routes)

Policies

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

Policies

Why do we need policies ?- Global IPv4 Delegations

Other Orgs (pre-RIR)

42%

Unallocated30%

"Special purpose"

14%

RIPE NCC4%

ARIN 6%

APNIC 4%

Policies

Growth of global routing table

last updated 29 Sep 2003

http://bgp.potaroo.net/as1221/bgp-active.html

DeploymentPeriod of CIDR

CIDR made it work for a while

But they cannot berelied on forever

Projected routing table growth without CIDR

ISPs tend tofilterlonger prefixes

Policies

Routing table prefix distribution

0 20000 40000 60000 80000 100000 120000 140000

Nov-01

Dec-01

Jan-02

Feb-02

Mar-02

Apr-02

May-02

Jun-02

Jul-02

Aug-02

Sep-02

Oct-02

Nov-02<16

16

17

18

19

20

21

22

23

24

>24

Last updated 29 Nov 2002

Policies

APNIC policy environment

“IP addresses not freehold property”– Assignments & allocations on license basis

• Addresses cannot be bought or sold• Internet resources are public resources• ‘Ownership’ is contrary to management goals

“Confidentiality & security”– APNIC to observe and protect trust relationship

• Non-disclosure agreement signed by staff

Policies

APNIC allocation policies

• Aggregation of allocation– Provider responsible for aggregation– Customer assignments /sub-allocations 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

Policies

Initial IPv4 allocation criteria

1a.Have used a /22 from upstream provider – Demonstrated efficient previous address usage

OR

1b.Show immediate need for /22• Can include customer projections & infrastructure equipment

2. Detailed plan for use of /21 within a year

3. Renumber to new space within 1 year

– Meet all policy requirements• Applicants may be required to show purchase receipts

Policies

APNIC allocation policies

• Transfer of address space– Not automatically recognised

• Return unused address space to appropriate IR

• Effects of mergers, acquisitions & take-overs– Will require contact with IR (APNIC)

• contact details may change

• new agreement may be required

– May require re-examination of allocations• requirement depends on new network structure

Policies

Address assignment policies

• Assignments based on requirements • Demonstrated through detailed documentation• Assignment should maximise utilisation

– minimise wastage

• Classless assignments• showing use of VLSM

• Size of allocation– Sufficient for up to 12 months requirement

Policies

Small multihoming assignment policy

1a. Applicants currently multihomed OR

1b. Demonstrate a plan to multihome within 1 month

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

Policies

IPv4 assignment policy for IXPs

Criteria– 3 or more peers– Demonstrate “open peering policy”

• APNIC has a reserved block of space from which to make IXP assignments

Policies

IXPs can apply for an assignment of /24 for Transit LAN

Questions?

APNIC Policy Update

16th APNIC Open Policy Meeting

• 19th – 22nd August, Seoul, Korea

• Held in conjunction with Korea Internet Operations Workshop (KIOW)

• Longest banners of any APNIC meeting

APNIC16 – Policy Update

• Consensus points only – Proposals have been circulated for 2 month

‘comment period’ on the ML (until 20th Nov)– Currently awaiting EC approval

• Prop-001-v001: Revised policy development process– Text proposal on ML 1 month before meeting– ‘Comment period’ on ML 2 months after meeting– Final endorsement from EC

• Prop-002-v001: Document revision policy• Prop-008-v001: IANA IPv4 resource request

procedures

Policy Update from APNIC16..

• Prop-005-v001: RIPE-261 follow up– Regional allocations – Larger allocation size from IANA

• Size /8 or /12 needs further discussion

• Prop-006-v001: Historical resource transfers– Allows transfers from ‘historical’ to ‘current’ status– Recipient must be an APNIC member– Address space subject to current policy framework

• Prop-011-v001: Revised IXP assignment policy– Definition amended, restriction on routing lifted– Further discussion required for remainder of

proposal

Policy Update from APNIC16

• Database SIG– Prop-007-v001: Privacy of customer

assignment records– Prop-010-v001: Protecting resource

records in APNIC whois database

• DNS SIG– Prop-007-v001: Revised lame delegation

cleanup

• Informational only– Create a guidelines document to explain

existing IPv6 policy

Come to the Next APNIC Meeting!

with

APRICOT 2004Kuala Lumpur, Malaysia, 18-27 February 2004

2nd round Fellowship application: 11-17 Jan 04

• Participate in policy development• Attend workshops, tutorials & presentations• Exchange knowledge and information with peers• Stay abreast with developments in the Internet• View multicast online• Provide your input in matters important to you

http://www.apnic.net/meetings/

Thanks and Questions?