hknog1.1 presentation
TRANSCRIPT
Agenda
4
• APNIC Policy Updates
• Recent policy implementation
• Policy discussion in 2015
• Transfer Policies and Procedures
• Transfer policies
• Transfer procedures (IPv4 and ASN transfer between members)
• Transfer services
Why is Policy Development
Important?
7
• Fair and consistent distribution of Internet number
resources
• Anyone can participate in how Internet number resources
are managed
– How much Internet number resources you can get
– How IP addresses are transferred
Policy Implementations in 2014
8
prop-107: AS number transfer proposal16 April
7 May
27 May
prop-109: Allocate 1.0.0.0/24 and 1.1.1.0/24
to APNIC Labs as Research Prefixes
prop-105: Distribution of returned IPv4
address blocks (Modification of prop-088)
Prop-105: Distribution of returned
IPv4 address block
9
• What does it mean?
– Members are eligible to receive an additional /22 IPv4 (non 103/8)
block from APNIC
• Where does this /22 block come from?
– IPv4 blocks returned by RIR to IANA
• Spirit of this policy?
– To help Members with their organization needs and move forward
to IPv6 address
HK Members who received additional
/22 under prop 105
10
197
377
HK members who have receivedadditional /22 (non103/8) underprop105
HK members who have notreceived additional /22(non103/8) under prop105
Total HK Members: 574
Proposal discussed at APNIC 39
11
Abandoned
• prop-112 - On demand expansion of IPv6 address allocation size in
legacy IPv6 space
• More information on APNIC Policy Development:
– https://www.apnic.net/policy
- Returned to the mailing list for further discussion
• prop-115 - Registration of detailed assignment information in whois
DB
• prop-114 - Modification in the ASN eligibility criteria
• prop-113 - Modification in the IPv4 eligibility criteria
Prop-112: On demand expansion of IPv6
address allocation size in legacy IPv6 space
12
• Legacy IPv6 space delegated before the first APNIC IPv6
address policy implemented
• Initially a /35, upgraded to /32
• When legacy IPv6 space is delegated, a /29 is reserved
• Author is proposing that members are entitled to the
remaining /29 without demonstrating the needs
• Community did not want to remove demonstrated need for
a small subset
• Author has abandoned the proposal
Prop-113: Modification in the IPv4
eligibility criteria
13
• To remove the multi-home requirement in order apply for
IPv4 assignment
• Helpful for ISPs that are not multi-homed and does not
meet the requirement for /22 allocation
• Consequence? Would finish the final /8 much more
quicker. E.g. ARIN and LACNIC
• Returned to the mailing list for further discussion
Prop-114: Modification in the ASN
eligibility criteria
14
• Eases the requirement for multi-homing
• Operators should be allowed to build their network like
how they want it to be
• Argument: Network operators could use a private ASN for
this purpose and there is no strong technical reason for
this requirement
• Returned to the mailing list for further discussion
Prop-115: Registration of detailed
assignment information in Whois DB
15
• Adding more specific assignment data (port range
information) into the APNIC Whois Database.
• To enable more specific filtering of harmful traffic
• Made available only to operators for security reason.
– Flexibility of APNIC Whois handling this information?
• Did not reach consensus, and returned to the mailing list
for further discussion
More on Policy
16
• Single policy document
– To make it easier for users to consult the policy documentation,
APNIC Secretariat has recently merged seven different policy
documents in a single policy manual.
– www.apnic.net/policy/resources
• Policy Champions program
– A campaign to encourage NOGs to participate in the Policy
Development Process
Live Demo of Confer Tool
18
• HKNOG 2015 is a successful event?- Strongly agree
• Agree
• Neutral
• Disagree
• Strongly disagree
• To test:
• Browse to www.confer.apnic.net
• Register email address, password, display name and start voting!
Transfer Policies
20
• IPv4 and ASN Transfer
• Transfer due to merger/ acquisition
• Transfer of historical internet resources
IPv4 and ASN Transfer
(prop50 + prop107)
21
• Transfer of IPv4 and AS Numbers between
– APNIC members (✓)
– APNIC and NIR (✓)
– APNIC and RIR (✓)
• Spirit of this policy:
– Allow members to transfer unused IPv4 and ASN to members who
still need them
Transfer of IPv4 and AS Numbers
between APNIC Members
22
• Most common transfer request from HK Members
• How to initiate such transfer request?
– Source account to initiate transfer and recipient account to accept
transfer via MyAPNIC
– Recipient account to justify the needs of the resources that will be
transferred
• Is there any transfer fees involved?
– www.apnic.net/fees
Transfer of IPv4 and AS Numbers
between APNIC and NIR
23
• What does it mean?
– Transfer from NIR member to APNIC member or vice versa
• Source account to initiate transfer request
• IR of source account to contact IR of recipient account
• Who will be evaluating the request?
– IR of the recipient account to evaluate transfer request
• How long the whole process will take?
– Depends on how long correspondence is between the recipient and
IR
Transfer of IPv4 and AS Numbers
between APNIC and RIR
24
• Similar to transfer between NIR and RIR
• Transfer from RIR Member to APNIC Member, or vice
versa
• Source account to initiate transfer request
• IR of the recipient account to evaluate transfer request
• More information on: www.apnic.net/transfer
Total number of IPv4 transfer
over the years
25
0
50
100
150
200
250
300
350
400
2011 2012 2013 2014 2015
Total
HK
How many IPv4 transfers involved in
final /8 (103/8)
26
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
2011 2012 2013 2014 Total
non-103/8
103/8
(Not including the
recycle pool)
Transfer Policies
27
• IPv4 and ASN Transfer
• Transfer due to merger/ acquisition
• Transfer of historical internet resources
Transfer due to merger/ acquisition
28
• Due to organization restructure/ acquisition of one
organization by another
• What documentation are required?
– e.g. sales/ transfer agreement issue by local authorities
• Transfer Condition: recipient account needs to become an
APNIC Member
• No transfer fees are involved
• Next renewal fee is calculated based on total resource
holding
Transfer Policies
29
• IPv4 and ASN Transfer
• Transfer due to merger/ acquisition
• Transfer of historical internet resources
Transfer of historical Internet resources
30
• What are historical resources?
– Resources delegated before APNIC was established, or had management
authority over the ranges in question
• If you are managing historical resources, you will have the
option to transfer them
• Once transferred, the renewal fee of the resources will be
calculated based on the normal membership renewal fee
• www.apnic.net/services/manage-resources/historical
Issue Date:
Revision:
Transfer Services
• IPv4 pre-approval
• IPv4 transfer listing service
• APNIC registered IPv4 brokers
IPv4 Transfer Pre-approval
36
• To allow recipient account to demonstrate the need for the
IPv4 block that will be transferred in advance
• Assure recipient account of a certain amount of IPv4
addresses
• Recipient account to complete the “Transfer pre-approval”
form via MyAPNIC
• For more information, please visit:
– http://www.apnic.net/pre-approval
IPv4 Transfer listing service
38
• List Members who have received pre-approval from
APNIC, and have given APNIC permission to make their
needs on a public website
• To help source account make contact with recipient
account that requires more IPv4 address
• For more information, please visit:
– http://www.apnic.net/pre-approval-listing
APNIC Transfers Mailing List
40
• Facilitate discussion on topics related to IPv4 transfer
• Share availability of unused IPv4 address
• Discuss your requirement of IPv4 address
• To subscribe to the mailing list, please go to:
– www.apnic.net/mailing-lists