IP Address News

Providing you with a single site about IP Addresses News and Usage

IP Address News - Providing you with a single site about IP Addresses News and Usage

ARIN 40 Public Policy Preview

Next week is the ARIN 40 meeting in San Jose, CA.     Here is my look ahead at the policies being discussed at the meeting.  We will have five draft policies to discuss during the meeting.  This time there are no recommended drafts so no policies will be headed to last-call after this meeting.  If you aren’t going to be there in person check out the remote participation options.

2017-3 Update to NPRM 3.6: Annual Whois POC Validation

Policy Summary: This draft policy make changes to the requirements for managing POC (Point of Contact) records in the ARIN database.

Discussion: This policy is intended increase the accuracy of the WHOIS information by removing records and removing ARIN services if records are not updated.  This policy was discussed at the last meeting in New Orleans.  While this policy so far does not seem to have a lot of support the AC is using this policy draft as a tool to continue the needed discussion around making changes to improve the accuracy of WHOIS records.

2017-4 Remove Reciprocity Requirement for Inter-RIR Transfers

Policy Summary: This draft policy is intended to allow one-way Inter-RIR transfers to the smaller RIRs (AfriNIC & LacNIC).

Discussion: For a while various policies in AfriNIC and LacNIC have proposed one-way policies such that addresses could be transferred into these regions.  There is a feeling amongst those in the LacNIC and AfriNIC communities if they allow 2 way transfers, all their IPv4 addresses will just be lost to other regions with more money.  This policy was intended to allow those smaller RIRs to obtain additional addresses via transfer from the regions which have older legacy space address holdings.

2017-5 Improved IPv6 Registration Requirements

Policy Summary: This draft policy changes the WHOIS reassignment requirements for IPv6.

Discussion: The current policy for IPv6 WHOIS reassignments requires /64 records to be put into the ARIN database.  This does not mirror the current situation with /28’s being required for IPv4.  This policy seeks to make a new threshold of /47 or larger OR any block which will be announced separately.

2017-6 Improve Reciprocity Requirement for Inter-RIR Transfers

Policy Summary: This draft policy is intended to block Inter-RIR transfers to RIRs which do not have reciprocal two-way transfer agreements with their NIRs.

Discussion: Some regions (such as APNIC) have NIRs (National Internet Registries) where organizations within that country go to obtain Internet resources.  It is suggested that some regions do not have reciprocal needs-based transfer policies between the RIR & NIR, and thus one should prohibit transfers to these RIRs since they do not meet the current ARIN requirements of a “RIRs who agree to the transfer and share reciprocal, compatible, needs-based policies.”

2017-8 Amend the Definition of Community Network

Policy Summary: This draft policy changes the definition of a community network in ARIN policy.

Discussion:  The community network policy in the ARIN region has been very rarely used.  Since it has been so rarely used we have discussed if it should just be removed from the policy manual or if it should be updated such that more organizations and networks could qualify.  This new definition attempts to redefine the policy such that additional organizations can qualify for resources under the community networks policy.

APNIC 44 Observations

Earlier this month I was fortunate to travel to Taichung, Taiwan for APNIC 44.  I’d like to share with you a few a few notes from the meeting.

The conference website for those wishing to jump for more details… https://conference.apnic.net/44/


Policy SIG

Prop-116 – Block transfers from last /8 (103/8). APNIC’s last /8 policy gives /22s to new entrants.  Some new entrants are getting blocks and then just selling them.  So this policy blocks transfers and requires organizations to return the unused blocks to APNIC for reallocation under the last /8 policy. This policy reached consensus and is moving to last call. As a result of consensus, the APNIC EC has issued a statement that all transfers are now blocked from 103/8.

Prop-118 – No need in APNIC. This is a policy to mirror the RIPE policy. After discussion it failed to reach consensus and is going back to the mailing-list. There was a question to APNIC secretariat about how many transfers thus far have been blocked for lack of need. The answer was 1. No details were given on why, but people used this fact to say there is not problem that needs to be solved here.

Prop-119 – Temporary transfers. This policy was promoted as needed because reallocations or reassignments weren’t “good enough.”  The policy draft required an end date to transfer, then a block would be returned to original organization.  The policy didn’t specify minimum term.  There was an interesting and quite lively discussion on this one. It failed to reach consensus and there was significant opposition. The policy will be returned to the mailing-list.

Prop-120 – Adjust the last /8 policy. The policy sought to combine the two current pools 103/8 & recovered pool (which currently has a wait list) after 103/8 is exhausted. The community wanted to preserve the “new entrant” gets something ideal, so combining the two pools didn’t make sense to many. There was a discussion of then how to combine/prioritize the wait-list. This policy failed to reach consensus and is going back to the mailing-list.

Prop-121 – Simpler Initial Ipv6 allocations. Removes the 200 assignments plan requirement, everyone gets the minimum, unless you want to provide a detailed plan for getting more.  Policy reached consensus, moving to last call.

Prop-122 – Simpler Subsequent Ipv6 allocations. If 121 reaches consensus, then prop-122 subsequent allocations policy should also be adjusted to bring it in line with initial allocation. Policy reached consensus, moving to last call.


I always find it interesting to see how the NIRs work within the RIR structure. While the update reports are sometimes just some quite repetitive stats, I did find the following interesting to note.

CNNIC – reports 93% of Chinese internet users use mobile as their connection method. They are spending significant effort to promote and train people to use RPKI.

KRNIC – KRNIC is undergoing a process to update all of their reallocation records with ISPs within their subregion. Still working on completing DNSsec signing of all their reverse zones.

INNIC – The “national” internet exchange in Indonesia has a peak rate of over 300Gbps and an interesting distributed topology throughout larger islands. INNIC is building their own “myINNIC” portal for members to access their records.

NAT w/ Geoff

Geoff Huston is off promoting NAT as the savior of the Internet now. Not really, but sort of, I certainly disagree with some of his conclusions. As someone who has lost days dealing with nat10 overlap between organizations, and trying to route/nat/encrypt/nat between multiple enterprise networks, the idea that we’d want to continue to add more NAT just sounds crazy to me if we don’t have to. Has NAT solved the issue with extra addresses needed at the edge, yes, and well it works well in the home CPE market. But beyond that, I’m not sure I’d promote NAT as a solution.

APNIC services

APNIC now has an organization object structure within its database. (Also some new contacts features in their portal)

APNIC continues to see fraud with address records, with people creating fake documentation and justification for resource needs. Often seen attempts at quick transfers with these kinds of fraud activities.

APNIC is continuing to look at how they want to be involved in the IP-geo-location issues.  They have a geoloc field in their database objects, but it is seldom used. Many other organizations feel like APNIC records are responsible for their addresses being located “somewhere else.” The conversation seemed to ignore that there are many different large commercial organizations which build geolocation databases (not off of whois information) and those records need to be updated too when a block is moved between organizations.

George Michaelson had a presentation about IRR and RPKI. With the idea to try and start people talking about how routing records should be created/stored in the future.  One interesting note there was that JPNIC now has (or will have soon) expiration dates on all RPSL records such that a regular review cycle is now required for all routing records. This certainly sounds like a good idea, if you assume RPSL is a good idea long term.  I don’t know if this would work well in other regions outside of JPNIC.

ASO review

APNIC will be chartering a working group to gather info from the public for the future structure of the ASO based upon the ITEMs consulting review of the ASO. Aftab Siddiqui and Izumi Okutani will be the co-chairs.

APNIC member meeting

Based on trends so far APNIC expects to transfer less (when measured by total addresses transferred) IPv4 addresses in 2017 compared to 2016 & 2015. A comparable year to 2014. Total number of transfers is projected to be up slightly in 2017 compared to 2016.

APNIC now using the new RDAP whowas specification implementation. https://www.apnic.net/about-apnic/whois_search/whowas/

There was a comment about the “ready to ROA” program and if it was perhaps distracting from other work that was perhaps more important. It seemed like there was some implication that people were just creating ROAs without fully understanding the implications or have any intent to use the RPKI for routing validation. (But perhaps I was reading too much into the comments I heard offline)