[196101] in North American Network Operators' Group
Which one(s) of SWIP, RWhois, RDAP? (Fwd: [ARIN-consult] NEW
daemon@ATHENA.MIT.EDU (John Curran)
Tue Oct 3 04:37:52 2017
X-Original-To: nanog@nanog.org
From: John Curran <jcurran@arin.net>
To: NANOG list <nanog@nanog.org>
Date: Mon, 2 Oct 2017 16:08:28 +0000
Errors-To: nanog-bounces@nanog.org
NANOGers!
Apologies (as some of you have already seen this) but it has more relev=
ance
to network operations than most IP number policy matters, so out of avo=
idance
of any doubt, I call this to your attention.
ARIN has opened a community consultation on the question of which metho=
ds
for reporting network sub-delegations should be supported by ARIN. If=
you have
views on this matter, please read the attached and take the time to com=
ment on
the arin-consult mailing list (which is the mailing list which ARIN use=
s for discussion
of community suggestions & consultations and is open to the public.)
Thanks!
/John
John Curran
President and CEO
ARIN
Begin forwarded message:
From: ARIN <info@arin.net<mailto:info@arin.net>>
Subject: [ARIN-consult] NEW Consultation: Available Methods of Reporting Ne=
twork Sub-Delegation Information
Date: 2 October 2017 at 8:19:36 AM PDT
To: <arin-consult@arin.net<mailto:arin-consult@arin.net>>
ARIN was previously requested via the ARIN Consultation and Suggestion Proc=
ess (ACSP) to open a consultation to generate discussion about the possibil=
ity of sun-setting RWhois support by the ARIN organization. ARIN's initial =
response to the ACSP indicated we would open a consultation following the c=
ompletion of the Registration Data Access Protocol (RDAP) specification ins=
ide the IETF processes. This work has been completed and the RFC has been p=
ublished. ARIN took the additional step of implementing RDAP inside its own=
directory services offering with referral support to the other Regional In=
ternet Registries (RIRs). With this work complete, we are following through=
with the formalized request to open a consultation on this topic.
https://www.arin.net/participate/acsp/suggestions/2013-22.html
In accordance with ARIN's Number Resource Policy Manual (NRPM), Organizatio=
ns 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 suppor=
ted 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 us=
ing 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 insid=
e ARIN Online using ARIN's SWIP-EZ functionality.
https://www.arin.net/resources/request/reassignments.html
Method 2:
RWhois (currently available): The reporting of sub-delegation information =
on your own hosted and operated RWhois server with referral link informatio=
n 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 inf=
ormation hosted by an RWhois server, they would have to submit a separate q=
uery to that RWhois server, and are not referred in an automated fashion.
https://www.arin.net/resources/request/reassignments_rwhois.html
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 optio=
n available, associated registry software would need to be created. This po=
ssible method would allow users of ARIN's directory services to view sub-de=
legation information available on customer hosted RDAP servers in an automa=
ted fashion. This RDAP method may also be viewed as redundant to RWhois.
https://tools.ietf.org/html/rfc7482
https://www.arin.net/resources/rdap.html
Options Going Forward
ARIN expects to continue offering Method 1 (SWIP) into the foreseeable futu=
re. As previously described, we are acting on a formal suggestion to consul=
t with the community about the future of RWhois support, and also have pote=
ntial 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-dele=
gation 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 fashi=
on 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 inform=
ation using RDAP, associated enabling software would be required. Should AR=
IN enable this method by creating an RDAP software suite that would allow A=
RIN registrants to run RDAP service locally?
The feedback you provide during this consultation will help inform decision=
s about software tools and support for the reporting of network sub-delegat=
ion information to ARIN in the future. Thank you for your participation in =
the ARIN Consultation and Suggestion Process.
Discussion on arin-consult@arin.net<mailto:arin-consult@arin.net> will clos=
e on 27 October 2017. If you have any questions, please contact us at info@=
arin.net<mailto:info@arin.net>.
Regards,
John Curran
President and CEO
American Registry for Internet Numbers (ARIN)
_______________________________________________
ARIN-Consult
You are receiving this message because you are subscribed to the ARIN Consu=
lt Mailing
List (ARIN-consult@arin.net<mailto:ARIN-consult@arin.net>).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN=
Member Services
Help Desk at info@arin.net<mailto:info@arin.net> if you experience any issu=
es.
