[arin-announce] NEW Consultation: Available Methods of Reporting Network Sub-Delegation Information

ARIN info at arin.net
Mon Oct 2 11:19:47 EDT 2017

ARIN was previously requested via the ARIN Consultation and Suggestion 
Process (ACSP) to open a consultation to generate discussion about the 
possibility of sun-setting RWhois support by the ARIN organization. 
ARIN's initial response to the ACSP indicated we would open a 
consultation following the completion of the Registration Data Access 
Protocol (RDAP) specification inside the IETF processes. This work has 
been completed and the RFC has been published. ARIN took the additional 
step of implementing RDAP inside its own directory services offering 
with referral support to the other Regional Internet Registries (RIRs). 
With this work complete, we are following through with the formalized 
request to open a consultation on this topic.


In accordance with ARIN's Number Resource Policy Manual (NRPM), 
Organizations are required to report certain types of customer network 
sub-delegation information (reassignments and reallocations) to ARIN. 
Currently there are two reporting methods available. Both are delineated 
in the NRPM and supported by ARIN's production services. There is also a 
third possible method of reporting sub-delegation information that could 
be made available, but is not yet offered.

Method 1:

SWIP (currently available):  The reporting of sub-delegation information 
using ARIN's database. This can be done either by submitting a SWIP 
template, interfacing with ARIN's RESTful API, or by creating a 
sub-delegation inside ARIN Online using ARIN's SWIP-EZ functionality.


Method 2:

RWhois (currently available):  The reporting of sub-delegation 
information on your own hosted and operated RWhois server with referral 
link information provided in ARIN Whois as part of your own 
organization's Whois records. In order for a user of ARIN's directory 
services to view sub-delegation information hosted by an RWhois server, 
they would have to submit a separate query to that RWhois server, and 
are not referred in an automated fashion.


Method 3:

RDAP:  The five RIRs currently use RDAP for referrals to each other's 
Whois data. Although the specification language of the RDAP could allow 
it to be used as a third method for the reporting of sub-delegation 
information to ARIN, it is not currently offered as an option. In order 
to make this option available, associated registry software would need 
to be created. This possible method would allow users of ARIN's 
directory services to view sub-delegation information available on 
customer hosted RDAP servers in an automated fashion. This RDAP method 
may also be viewed as redundant to RWhois.


Options Going Forward

ARIN expects to continue offering Method 1 (SWIP) into the foreseeable 
future. As previously described, we are acting on a formal suggestion to 
consult with the community about the future of RWhois support, and also 
have potential options with RDAP.

  * Question (general):

         Of the three sub-delegation reporting methods listed (SWIP, 
RWhois, RDAP), which should ARIN support in the future?

  * Question (SWIP/RESTful API specific):

         The existing RESTful API allows users to report (SWIP) one 
sub-delegation at a time to be added to ARIN Whois. Should    ARIN add 
bulk-upload features to the RESTful API?

  * Question (RWhois specific):

          As noted, RWhois servers are not referred to in an automated 
fashion when users query ARIN Whois. Should ARIN automate referrals to 
RWhois servers from ARIN's Whois service?

  * Question (RDAP specific):

         If ARIN was to allow the reporting of network sub-delegation 
information using RDAP, associated enabling software would be required. 
Should ARIN enable this method by creating an RDAP software suite that 
would allow ARIN registrants to run         RDAP service locally?

The feedback you provide during this consultation will help inform 
decisions about software tools and support for the reporting of network 
sub-delegation information to ARIN in the future. Thank you for your 
participation in the ARIN Consultation and Suggestion Process.

Please provide comments toarin-consult at arin.net. You can subscribe to 
this mailing list at:

Discussion onarin-consult at arin.netwill close on 27 October 2017. If you 
have any questions, please contact us atinfo at arin.net.


John Curran
President and CEO
American Registry for Internet Numbers (ARIN)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-announce/attachments/20171002/1c587db2/attachment.html>

More information about the ARIN-announce mailing list