<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I'm writing to support the sunsetting
of the rwhois protocol as a method for ARIN members to document
reallocation and reassignment records. <br>
<br>
That doesn't mean this year or next year, but I believe we should
set a timeline for deprecating this protocol. Perhaps a date of
2022 would be reasonable. (Yes, some organizations will not do
the work despite the 4 years of time to do it, but a shorter time
frame would also be unacceptable to some)<br>
<br>
I have seen those who have posted on this consultation noting that
"rwhois works and isn't broken so don't fix it." While I will
agree that it is "technically" not broken, I believe that it is
operationally broken. <br>
<br>
These are some of the reasons why I believe we should move on to
something better. Any by better, I mean moving to records stored
in the ARIN database (SWIP) or RDAP.<br>
<br>
-Rwhois doesn't support encryption or data-integrity during
transport<br>
-There is no automatic referral, so when most people query ARIN
whois they don't know there is potentially another more specific
record and even if they are aware, how to do rwhois is not "easy"
for many users. Yes its easy for engineers and some operators,
but there are many users of "whois" data for whom this is a
barrier too high. Could we invest in lots of training for rwhois,
yes, but we will always be behind on this as long as its not a
click away for most users.<br>
-As was noted in the most recent ARIN meeting, law enforcement
agencies use whois data as a source for their investigations and
other work, and having accurate records available on a timely
basis is very important to them. I don't believe that rwhois data
is as accessible and available as data in the ARIN database.<br>
-RDAP was designed with referral in mind from the ground up, so
that you get all the records no matter where they are located with
a single query. <br>
-ARIN (in possible collaboration with other RIRS) should develop
an RDAP package for those who like to host their own, distributed
database. The new package should support bulk retrieval of
records to assist in data collection and analysis. (Also it was
noted in the most recent ARIN meeting that there are differences
today in how the different RIRs are reporting fields/data via
RDAP. It would be good for the RIRs in collaboration with each
other and other organizations that want to run RDAP servers for IP
number resources to work to create a standard met of fields which
are required for IP number resource records, along with other
optional fields for additional data) <br>
<br>
It has been noted casually that there are many rwhois servers
which are down or aren't available. I believe this also
contributes to this data set being operationally unavailable. <br>
<br>
I'd like to ask if ARIN staff can confirm some of these details
with data from the ARIN's database and operational practices.
Specifically if ARIN could provide the following details about how
rwhois is being operated today I believe it would inform the
community in this consultation process.<br>
<br>
1) Number of orgs which have IPv4 or IPv6 resources and a rwhois
record on their org-id.<br>
<br>
2) Number of IPv4 and IPv6 blocks with a rwhois server under the
org-id records<br>
<br>
3) Number of /24 IPv4 equivalents covered by the above records<br>
<br>
4) Number of /32 IPv6 equivalents covered by the above records<br>
<br>
5) Total number of unique rwhois servers<br>
<br>
6) Percent of rwhois servers which are online (complete a tcp
connection<br>
accept a string and respond with some text)<br>
<br>
7) Percent of rwhois server who appear to respond with a valid
record<br>
for an address within each allocated block<br>
<br>
<br>
Thanks,<br>
Andrew<br>
<br>
<br>
<br>
On 10/2/2017 8:19 AM, ARIN wrote:<br>
</div>
<blockquote type="cite"
cite="mid:381c089a-e807-f684-f1a8-0b47e6982846@arin.net">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">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.<br>
<br>
<a class="moz-txt-link-freetext"
href="https://www.arin.net/participate/acsp/suggestions/2013-22.html"
moz-do-not-send="true">https://www.arin.net/participate/acsp/suggestions/2013-22.html</a><br>
<br>
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.<br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Method 1:<span
class="Apple-converted-space"> </span><br>
<br>
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.<span class="Apple-converted-space"> </span><br>
<br>
<a class="moz-txt-link-freetext"
href="https://www.arin.net/resources/request/reassignments.html"
moz-do-not-send="true">https://www.arin.net/resources/request/reassignments.html</a><br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Method 2:<span
class="Apple-converted-space"> </span><br>
<br>
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.<br>
<br>
<a class="moz-txt-link-freetext"
href="https://www.arin.net/resources/request/reassignments_rwhois.html"
moz-do-not-send="true">https://www.arin.net/resources/request/reassignments_rwhois.html</a> <span
class="Apple-converted-space"> </span><br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Method 3:<span
class="Apple-converted-space"> </span><br>
<br>
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.<br>
<br>
<a class="moz-txt-link-freetext"
href="https://tools.ietf.org/html/rfc7482"
moz-do-not-send="true">https://tools.ietf.org/html/rfc7482</a><br>
<a class="moz-txt-link-freetext"
href="https://www.arin.net/resources/rdap.html"
moz-do-not-send="true">https://www.arin.net/resources/rdap.html</a><br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Options Going Forward<br>
<br>
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.<br>
</p>
<ul style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">
<li>Question (general):<span class="Apple-converted-space"> </span></li>
</ul>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
Of the three sub-delegation reporting methods listed
(SWIP, RWhois, RDAP), which should ARIN support in the future?<br>
</p>
<ul style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">
<li>Question (SWIP/RESTful API specific):<span
class="Apple-converted-space"> </span></li>
</ul>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
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?<br>
</p>
<ul style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">
<li>Question (RWhois specific):<span
class="Apple-converted-space"> </span></li>
</ul>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
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?<br>
</p>
<ul style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">
<li>Question (RDAP specific):<span class="Apple-converted-space"> </span></li>
</ul>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
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?<br>
<br>
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.<span
class="Apple-converted-space"> </span><br>
<br>
Discussion on<span class="Apple-converted-space"> </span><a
class="moz-txt-link-abbreviated"
href="mailto:arin-consult@arin.net" moz-do-not-send="true">arin-consult@arin.net</a><span
class="Apple-converted-space"> </span>will close on 27 October
2017. If you have any questions, please contact us at<span
class="Apple-converted-space"> </span><a
class="moz-txt-link-abbreviated" href="mailto:info@arin.net"
moz-do-not-send="true">info@arin.net</a>.<br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">Regards,</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);">John Curran<br>
President and CEO<br>
American Registry for Internet Numbers (ARIN)</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
</p>
<p style="color: rgb(0, 0, 0); font-family: -webkit-standard;
font-style: normal; font-variant-caps: normal; font-weight:
normal; letter-spacing: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255);"><br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ARIN-Consult
You are receiving this message because you are subscribed to the ARIN Consult Mailing
List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-consult@arin.net">ARIN-consult@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-consult">http://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services
Help Desk at <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
<p><br>
</p>
</body>
</html>