IPv6 Address Allocation Policies & Procedures

Champika Wijayatunga, APNIC

1st ASEAN IPv6 SummitOct 20-22, 2003 – Kuala Lumpur, Malaysia

Presentation Outline

• APNIC Overview

• APNIC community and the policy development process

• IPv6 allocation and assignment policies

• Statistics

APNIC Overview

What is APNIC?

• Regional Internet Registry (RIR)for the Asia Pacific Region– Regional authority for Internet Resource distribution– IP addresses (IPv4 and IPv6), AS numbers, in-addr.arpa

delegation

• Established 1993 – Operating within ICANN (IANA) structure – Pilot project of APNG in Tokyo, Japan– Relocated to Brisbane, Australia in 1998

What is APNIC?

• Industry self-regulatory body– Non-profit, neutral and independent– Participation by those who need and use IP

addresses– Consensus-based, open and transparent

• Membership-based structure– Open to any interested party– Provides formal structure for cost recovery,

election of representatives etc

APNIC Region

Where are APNIC Members?

HK 13%

IN 12%

PH 6%

SG 5%

JP 5%PK4%

TH4%

Pacific 3%

Other 5%

AU 23%

LK 1%ID 1%

BD 3%TW 3%

MY 4%

NZ 4%

CN 4%

AP 4%

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

What is APNIC’s role?

• Resource distribution & registration services–IPv4, IPv6, ASNs, in-addr.arpa, whois

• Policy development and implementation–Discuss the policies via mailing lists, Open policy meetings,

SIG sessions–Membership reviews and approves policy

• Training and education–Effective IP address management: Asia Pacific Policies and

Procedures

Internet Registry structure

ICANN

ASO

APNIC ARIN RIPE NCCLACNIC

IANA

NIR LIR LIR

LIR ISP ISP

ISP ISP

ISPISP

ISP ISP

ISP ISP

LIR LIR

ISP ISP

What is the APNIC Community? • Open forum in the Asia Pacific

– Open to any interested parties

• Voluntary participation

• Decisions made by consensus

• Public meetings

• Mailing lists– web archived

Definition – “Internet Community”

Global Internet Community

APNIC Internet Community

IETF

ISOC

Individuals

APNIC Members

APAN SANOG / PITA etc

ISP Associations

What does the community do ?

• Develops Internet resource policies– Applicable to the use of IP addresses, ASNs etc.

• Provides input on the direction of APNIC– open and democratic participatory process

• Shares information and experience

• Discusses matters relevant to the Internet

• A voice in regional Internet operations through participation in APNIC activities

APNIC policy development process• Who are involved?

– APNIC Members• ISPs, NIRs, etc.

– Executive Council• 7 members elected by the APNIC members

– APNIC General Secretariat• APNIC’s staff

– Internet Community at large• Interested parties

Principles of policy development

• ‘Bottom up’, consensus based decision making– Community proposes and approves policy– No policies implemented without consensus of

community

• Open and transparent– Anyone can attend– All decisions archived

Principles of policy development

TRANSPARENT‘BOTTOM UP’

• All decisions & policies documented & freely available to anyone

• Anyone can participate

• Internet community proposes & approves policy

OPEN

Consensus based

Participation in policy development

• Why should I bother?– Responsibility as an APNIC member

• To be aware of the current policies for managing address space allocated to you

– Business reasons• Policies affect your business operating environment and

are constantly changing• Ensure your ‘needs’ are met

– Educational• Learn and share experiences• Stay abreast with ‘best practices’ in the Internet

Elements of the process

MemberMeeting

Working Groups

Birds of a Feather

Special InterestGroups

Open Policy Meeting&

Mailing Lists

SIGs: Formal groups which discuss broad areas of policy relevant to the APNIC internet community BOFs: Informal meetings to

exchange ideas eg. CA BOF, Network Abuse BOF, Training Need to hold at least one to form new SIG

WGs: semi formal, volunteer group tasked by a SIG to work on a particular project until completed eg. ‘Broadband’

MM: forum specific to APNIC business eg. fee structure, election of executive council & endorsement of policy decisions

How does it work?

New policy or amendment proposed

Endorsement by MM?

Report of consensus in SIG to MM

Consensus?

Implementation 3 months

Posted to SIG ML for discussion

Face to face discussions in public open forum (SIGs)

YES

YES

NO

NO

How to get your voice heard

• Contribute on the public mailing lists– http://www.apnic.net/community/lists/index.html

• Attend meetings– Or send a representative– Gather input at forums

• Give feedback– Training or seminar events

• Next meeting: In conjunction with APRICOT 2004 - Kuala Lumpur, 24-28 Feb 2004– http://www.apnic.net/meetings/

IPv6 Policies & Procedures

IPv6 policy development process

Discussions within APNIC community

(Liaison with other RIRs)

Policy meetings & SIGs, mailing lists etc

By RIRs and community

Consensus of community

Policy is implemented

RegionalPolicy

Variations Membership approval

IPv6 address policies

• Accordance with the Regional Internet Registry IPv6 policy document– http://www.apnic.net/policies.html

• Developed through joint discussions among the APNIC, ARIN and RIPE communities

IPv6 address policies - goals

• Internet is able to function and grow to the maximum extent possible

• Aggregation– Hierarchical distribution– Aggregation of routing information– Limiting no of routing entries advertised into the Internet

• Efficient address usage– Avoid wasteful practices

• Minimise Overhead• Registration of addresses, Uniqueness,

Fairness & consistency

IPv6 address policies - principles

• Address space not to be considered freehold property

• License model of allocation– Allocations are not considered permanent, but

always subject to review and reclamation– Licenses renewed automatically while addresses

in use, consistent with policies

IPv6 address policies - principles

• Routability not guaranteed– No guarantee that any address allocation or

assignment will be globally routable

• Minimum Allocation– To facilitate prefix-based filtering– Minimum allocation size is /32

• Consideration of IPv4 Infrastructure

IPv6 address management hierarchy

IANA

RIR RIR

LIR/ISP

Customer Site Customer Site

Downstream ISPLIR/ISP

IPv6 addressing structure

LIR/32

Subnet /64

Customer Site /48

0 127

32

128 bits

16 16 64

Device /128

IPv6 allocation policy

• Initial allocation size is /32– Allocated to any IPv6 LIR (ISP) planning to

connect 200 End Sites within 2 years– This is the default initial allocation to “new” ISPs

(“slow start” policy)– Provides 16 bits of site address space

• Larger initial allocations can be made if justified according to:– IPv6 network infrastructure plan– Existing IPv4 infrastructure and customer base

IPv6 allocation policy

• LIR to ISP allocation– No specific policy– Optimum utilization of the total address block

allocated to the LIR– All /48 assignments to end sites are required to be

registered either by the LIR or its subordinate ISPs

• HD-Ratio when a subsequent allocation becomes necessary

IPv6 Assignments

• Default assignment /48 for all End Sites– Providing /16 bits of space for subnets

• End Site defined as an end user of an ISP where:– The ISP assigns address space to the end user – The ISP provides Internet transit service to the

end user– The ISP advertises an aggregate prefix route that

contains the end user's assignment – ISP POPs (Points of Presence) are also defined

as End Sites

IPv6 assignments

• /48s assignments per end site– /64 only one subnet – /128 only one device connecting

• Larger assignments - Multiple /48s – Some end sites will need more than one /48– Should be reviewed by RIR/NIR– Second opinion process

• ISP infrastructure – /48 per POP

IPv6 assignments

• IPv6 assignments to End Sites used to determine utilisation of IPv6 address blocks– Intermediate allocation hierarchy not considered– All assignments must be registered– Utilisation determined from registrations

• Intermediate allocation and assignment practices are the responsibility of the LIR.

RIR

LIR

ISPAssignment

Allocation

Allocation

IPv6 registration

• LIR is responsible for all registrations

Assignment

Registration

IPv6 utilisation requirement

• Subsequent allocation may be requested when IPv6 utilisation requirement is met

• Utilisation of IPv6 address space is measured differently from IPv4

IPv6 utilisation requirement

• Under IPv4, address space utililsation measured as simple pecentage:

• IPv4 utilisation requirement is 80%– When 80% of address space has been

assigned or allocated, LIR may receive more– E.g. ISP has assigned 55000 addresses of

/16

availableassignednUtilisatio

%84536,65

000,55 availableassigned

IPv6 utilisation requirement

• Under IPv6 utilisation will be measured according to HD-Ratio (RFC 3194):

• IPv6 utilisation requirement is HD=0.80– Measured according to assignments only

(intermediate allocations are ignored)– E.g. ISP has assigned 10000 sites from /32

)log()log(

availableassigned

HDnUtilisatio

83.0)536,65log(

)000,10log()log()log( available

assigned

v6 prefix Total site addresses

Utilisationrequirement

Util%

42 64 28 43.5%36 4096 776 18.9%35 8192 1351 16.5%32 65536 7132 10.9%29 524288 37641 7.2%24 16777216 602249 3.6%16 4294967296 50859008 1.2%

8 1099511627776 4294967296 0.4%3 35184372088832 68719476736 0.2%

v6 prefix Total site addresses

Utilisation requirement

Util%

42 64 28 43.5%36 4096 776 18.9%35 8192 1351 16.5%32 65536 7132 10.9%29 524288 37641 7.2%24 16777216 602249 3.6%16 4294967296 50859008 1.2%

8 1099511627776 4294967296 0.4%3 35184372088832 68719476736 0.2%

IPv6 utilisation requirement

• HD Ratio utilisation requirement of 0.80

RFC3194 “The Host-Density Ratio for Address Assignment Efficiency”

Subsequent allocation

• Subsequent allocation can be made when HD = 0.80 is reached

• Other address management policies should also be met– Correct registrations– Correct assignment practices etc

Subsequent allocation

• Subsequent allocation size is at least doubled

• Where possible, the allocation will be made from an adjacent address block– Resulting IPv6 Prefix is 1 bit shorter

• Should be sufficient for 2 years requirement

Other conditions

• Existing /35 Allocations

– A number of /35s have been assigned under interim IPv6 policy

– Holders of /35s immediately eligible to request /32

Portable IPv6 assignments

• For IXPs– Demonstrate ‘open peering policy’– 3 or more peers – Portable assignment size: /48

• All other needs should be met through normal processes

• Critical Infrastructure– Root DNS, ccTLD, IANA, RIRs/NIRs, but not IXPs– Assignment size is /32

IPv6 address allocation procedures

• IPv6 Allocations to RIRs from IANA

– APNIC • 2001:0200::/23• 2001:0C00::/23• 2001:0E00::/23

– ARIN • 2001:0400::/23

– LACNIC• 2001:1200::/23

– RIPE NCC • 2001:0600::/23• 2001:0800::/23• 2001:0A00::/23

• IPv6 FAQ– http://www.apnic.net/faq/IPv6-FAQ.html

IPv6 address request form

• IPv6 Address Request form– http://www.apnic.net/apnic-bin/ipv6-subtla-request.

pl

• Use by organisations requesting IPv6 allocations that they will use for addressing their own infrastructure and making assignments to customers

IPv6 address request form

• Information Required– Contact details– Structure of the organisation

• In terms of how the IP addresses will be utilised

– Peering relationships• Does the member have exterior routing protocol peering

relationships

– IPv6 service plan– Planned addressing structure– ISPs infrastructure – Customer assignments (IPv4 Customers)

Statistics

IPv4 allocations - global

Other Orgs (pre-RIR)

42%

Unallocated30%

"Special purpose"

14%

RIPE NCC4%

ARIN 6%APNIC 4%

IPv4 growth in Asia Pacific

Last Update 26 Sep 2003

0

16

32

48

64

80

96

112

128

144

160

176

Jan-96 Jan-97 Jan-98 Jan-99 Jan-00 Jan-01 Jan-02 Jan-03 Oct-03

Mil

lio

ns

OtherTWTHSGPKPHNZMYKRJPINIDHKCNAUAP

IPv6 Allocations - Global

LACNIC8

ARIN71

RIPE-NCC237

APNIC113

APNIC ARIN RIPE-NCC LACNIC

IPv6 Allocations - Global

Single Allocation16%

JP26%

US14%

DE8%

FI3%

SE3%

FR2%

IT2%

NL2%

AT1%

IE1%

KR8%

UK5%

MX4%

EU3%

AU2%

IPv6 allocations in APIPv6

Last updated Oct 2003

JP 58

ID2

PH1

KR 17

SG 4HK 2

IN1MY

3

PG1

TH3

AU 5

CN 5

TW 11

IPv6 Allocations in AP - by year

7

15

26

45

20

113

0

20

40

60

80

100

120

1999 2000 2001 2002 2003 Total

Last updated Oct 2003

IPv6 Allocations Globally - by time

0

50

100

150

200

250

300

350

400

450

500

Jul-99 Jan-00 Jul-00 Jan-01 Jul-01 Jan-02 Jul-02 Jan-03 Jul-03

LACNIC

RIPE-NCC

ARIN

APNIC

Last updated Oct 2003

References

• IPv6 Resource Guide• http://www.apnic.net/services/ipv6_guide.html

• IPv6 Policy Document• http://www.apnic.net/policies.html

• IPv6 Address request form• http://ftp.apnic.net/apnic/docs/ipv6-alloc-request

FAQ• http://www.apnic.net/info/faq/IPv6-FAQ.html

IPv6

Thank You

Champika Wijayatunga

champika@apnic.net