APNIC Services Anna Mulingbayan Snr Internet Resource Analyst/ Liaison Officer South East Asia, APNIC APNIC Regional Meeting <29-Nov-2013>

APNIC Services

•  Resource Delegation (Statistics)

•  IPv4 transfer

•  MyAPNIC

•  Helpdesk

•  Community Engagement

•  Whois database (new feature)

•  Training

“Function as the RIR for the Asia Pacific, in the service of the community of Members and others”

“Provide Internet registry services to the highest possible standards of trust, neutrality, and accuracy”

2

IPv4 last /8 delegations

As at 31 October 2013

0

20

40

60

80

100

120

140

160

180

200 A

pr-1

1 M

ay-1

1 Ju

n-11

Ju

l-11

Aug

-11

Sep

-11

Oct

-11

Nov

-11

Dec

-11

Jan-

12

Feb-

12

Mar

-12

Apr

-12

May

-12

Jun-

12

Jul-1

2 A

ug-1

2 S

ep-1

2 O

ct-1

2 N

ov-1

2 D

ec-1

2 Ja

n-13

Fe

b-13

M

ar-1

3 A

pr-1

3 M

ay-1

3 Ju

n-13

Ju

l-13

Aug

-13

Sep

-13

Oct

-13

Date

Del

egat

ions

3

IPv4 last /8 delegation trend

0 1000000 2000000 3000000 4000000 5000000 6000000 7000000 8000000 9000000

10000000 11000000 12000000 13000000 14000000 15000000 16000000 17000000

1/04

/11

1/04

/12

1/04

/13

1/04

/14

1/04

/15

1/04

/16

1/04

/17

1/04

/18

1/04

/19

1/04

/20

1/04

/21

1/04

/22

1/04

/23

1/04

/24

1/04

/25

1/04

/26

1/04

/27

1/04

/28

1/04

/29

1/04

/30

No

of IP

v4 a

ddre

sses

Date

4

IPv6 delegations by year

0

100

200

300

400

500

600

700

2008 2009 2010 2011 2012 2013

Num

ber o

f del

egat

ions

Year

As at 31 October 2013

5

Cumulative ASN delegations

0

1,000

2,000

3,000

4,000

5,000

6,000

7,000

8,000

2008 2009 2010 2011 2012 2013

2-byte 4-byte

As at 31 October 2013 Date

Del

egat

ions

6

IPv4 address transfer services •  Support for intra- and inter-RIR transfers •  Pre-approval service, with opt-in anonymous listing •  Broker listing; five registered so far

www.apnic.net/transfer-brokers •  Mailing list to enable the source and recipients of IPv4 address transfers

and IPv4 brokers to discuss topics relevant to transfers apnic-transfers@apnic.net

•  Public transfer log ftp://ftp.apnic.net/public/transfers/apnic

•  Transfer fees applied –  20% of the transferred block’s annual fee (other holdings not included in the

calculation) –  Payable by the recipient, or by the source if transferred out of the APNIC region

•  Policy proposal prop-104 was implemented on 18 February 2013 –  Demonstrated need changed from 12 month to 24 month requirement

7

Procedure of IPv4 market transfer between APNIC account holders 1.  The Recipient submits a pre-approval request via MyAPNIC and

gets APNIC approval 2.  The Source and the Recipient reach transfer agreement 3.  The Source initiates IPv4 transfer via MyAPNIC and indicates the

recipient account 4.  The Recipient accepts the transfer in MyAPNIC 5.  APNIC Hostmasters approve the transfer and invoice Recipient for

a transfer fee 6.  The Recipient pays the transfer fee 7.  APNIC Hostmasters transfer the resource from the source

account to the recipient account and update APNIC whois records 8.  APNIC Hostmasters transfer the resource from the source account

to the recipient account and update APNIC whois records

8

9  

Inter-RIR transfers

•  Completed transfers: 11 from ARIN to APNIC (Nov 2012 – August 2013)

•  Transfer time (including evaluation): one – two weeks

•  Successfully transferred live network –  ARIN-managed resources transferred into the AP region, to be

managed by APNIC

•  ARIN and APNIC stats overlap one day after the transfer due to the time zone difference

10

Procedure of IPv4 market transfer from ARIN to APNIC account holders 1. The Recipient submits a pre-approval request via MyAPNIC and gets APNIC approval 2. The Source and the Recipient reach transfer agreement 3. The Source contact ARIN to initiate IPv4 transfer and indicates the recipient’s APNIC member account 4. ARIN evaluates the transfer request based on ARIN policy and forwards the transfer request to APNIC after ARIN approval

5. APNIC confirms with the Recipient and invoice Recipient for a transfer fee 6. The Recipient pays the transfer fee to APNIC 7. APNIC delegates the resource to the recipient account and update APNIC whois records 8. APNIC inform ARIN to update ARIN whois records 9. ARIN notify the Source the transfer has been completed

10. APNIC notify the Recipient the transfer has been completed

12  

IPv4 market transfers

0

2

4

6

8

10

12

14 N

ov-1

0 D

ec-1

0 Ja

n-11

Fe

b-11

M

ar-1

1 A

pr-1

1 M

ay-1

1 Ju

n-11

Ju

l-11

Aug

-11

Sep

-11

Oct

-11

Nov

-11

Dec

-11

Jan-

12

Feb-

12

Mar

-12

Apr

-12

May

-12

Jun-

12

Jul-1

2 A

ug-1

2 S

ep-1

2 O

ct-1

2 N

ov-1

2 D

ec-1

2 Ja

n-13

Fe

b-13

M

ar-1

3 A

pr-1

3 M

ay-1

3 Ju

n-13

Ju

l-13

Aug

-13

Sep

-13

Oct

-13

13

Date

Num

ber o

f tra

nsfe

rs

As at 31 October 2013

IPv4 market transfer by economy

From To

As at 30 September 2013

Num

ber o

f tra

nsfe

rs

Economy

14

0

5

10

15

20

25

30

35

40

45

50 A

U

MY

NZ

SG

C

N

HK

S

G

AP

HK

IN

M

Y P

H

SG

ID

S

G

IN

JP

MN

N

Z H

K

MY

MN

N

Z S

G

PH

JP

S

G

TH

PH

S

G

BD

K

H

AP

AU

C

N

HK

IN

JP

P

H

SG

AU CN FJ HK ID IN JP MN MY NZ PH SG TH TW BD KH ARIN

What is MyAPNIC?

•  A secure services website that enables Members to manage Internet resources and account interactions with APNIC online

•  Uses 128-bit SSL

•  https://myapnic.net

How it Works

Firewall

Finance system

Membership & resource

system

Whois master

Member ID Person

Authority

MyAPNIC server

Member’s staff

APNIC internal system APNIC public servers

Server

Client https://myapnic.net

Access to MyAPNIC

•  MyAPNIC access is available to all authorized contacts of APNIC accounts by registering your username and password

•  Corporate Contacts can register and get instant access

www.apnic.net/corporate_contacts

•  Other contacts need their registration approved by their Corporate Contact

MyAPNIC Digital Certificate

Required for:

•  Online voting

•  Resource certification

•  Approve other contacts’ certificate request

One Click IPv6

APNIC Helpdesk

What is local community engagement? •  Extension of APNIC’s external liaison and outreach

•  Support of local Internet community events

•  Continuing to build rapport and support for APNIC Members

•  Promote APNIC’s missions and services to the wider Internet community

21

Some observations

•  Those who interact with APNIC regularly by emails or who are unable to attend APNIC Conferences are able to meet APNIC staff

•  This allows APNIC Members and the wider Internet community to provide direct feedback on APNIC services for continual improvement

•  Those who know very little of APNIC’s missions and services are better informed

•  Participants use the occasion to exchange information and share common issues they are facing

•  This is also a great opportunity to discuss ideas face-to-face, or problems that are difficult to communicate by emails

22

Membership growth

As at 31 October 2013

0

500

1000

1500

2000

2500

3000

3500

4000

1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013

XL VL L M S VS AS

Date

Mem

bers

23

What activities are involved?

•  Speaking at local Internet events

•  Holding APNIC training events or workshops

•  Holding APNIC Members gathering –  APNIC updates

•  Providing Hostmaster consultations

24

Events in 2013

•  Traceroute 2013 (The biggest Internet party) – Indonesia

•  Member gathering and CTO Forum BD – Bangladesh

•  IPv6 event by ASTI – Philippines

•  CommunicAsia 2013 – Singapore

•  SANOG 22 – India

•  Member gathering and HKNOG inauguration – Hong Kong

•  Annual Cyber security week – Sri Lanka

•  MYNOG – Malaysia

25

Member gatherings

26

Social Media

27

Conferences

•  APRICOT 2014: Bangkok, Thailand –  18 to 28 February 2014 (includes APNIC 37)

https://2014.apricot.net

•  APNIC 38 2014: Nouméa, New Caledonia –  8 to 19 September 2014

•  APRICOT 2015: Fukuoka, Japan –  24 February to 6 March 2015 (includes APNIC 39 and APAN 39)

28

Whois New Attributes

•  Hints to content providers about the users of a network resource

•  ‘geoloc’ attribute is where the resources are used –  Example: geoloc: -27.473136 153.01412!

•  ‘language’ attribute is expected languages of users –  Example: language: zh

•  Available on the ‘inetnum’ and ‘inet6num’ objects now

Whois database

30

Engaging in Training

New Training Website

Questions?