<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 13, 2017, at 12:22 , Jason Schiller <<a href="mailto:jschiller@google.com" class="">jschiller@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Comments in line.<div class=""><br class=""></div><div class=""><div class=""><br class=""></div><div class="">Question (general): </div><div class=""><br class=""></div><div class=""> Of the three sub-delegation reporting methods listed (SWIP, RWhois, RDAP), which </div><div class=""> should ARIN support in the future?</div><div class=""><br class=""></div><div class="">Answer: ARIN should support all three in the future.<br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Question (SWIP/RESTful API specific): </div><div class=""><br class=""></div><div class=""> The existing RESTful API allows users to report (SWIP) one sub-delegation at a time </div><div class=""> to be added to ARIN Whois. Should ARIN add bulk-upload features to the RESTful API?</div><div class=""><br class=""></div><div class="">Answer: 1. Bulk removal is more important that bulk additions. </div><div class=""> e.g. can you remove all SWIPs for prefixes within <a href="http://1.2.0.0/18" class="">1.2.0.0/18</a>.</div></div></div></div></blockquote><div><br class=""></div><span class="Apple-tab-span" style="white-space:pre"> </span>The concern I have if we support this kind of bulk removal is that we must somehow validate that</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>the removal comes from an entity allowed to remove all of 1.2.0.0/18 and its subordinates. We</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>wouldn’t want, for example, the owner of 1.2.2.0/24 to be able to use their authority there to</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>remove all of their fellow customers of the owner of 1.2.0.0/18. Obviously this is an implementation</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>detail, but it’s an important one.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""> 2. If we offer bulk additions, it should be supported for all update types </div><div class=""> (template, RESTful API)</div></div></div></div></blockquote><div><br class=""></div><span class="Apple-tab-span" style="white-space:pre"> </span>I disagree. As much as Mark likes to point out that I am the leading defender of templates,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I don’t think adding bulk addition to templates really makes much sense.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""> 3. Sure, but I don't think the priority is very high.</div><div class=""><br class=""></div><div class="">Question (RWhois specific): </div><div class=""><br class=""></div><div class=""> As noted, RWhois servers are not referred to in an automated fashion when users query </div><div class=""> ARIN Whois. Should ARIN automate referrals to RWhois servers from ARIN's Whois service?</div><div class=""><br class=""></div><div class="">Answer: Yes. </div><div class=""> This seems to work for my whois client (whois Version 5.1.1. Report bugs to <<a href="mailto:md%2Bwhois@linux.it" class="">md+whois@linux.it</a>> ).</div><div class=""> (example below)</div><div class=""><br class=""></div><div class=""> When somoene does a "SEARCH WhoisRWS" on the ARIN website, it should likewise chase </div><div class=""> the rwhois referral, and display it on the ARIN web site.</div><div class=""><br class=""></div><div class=""> Furthermore, ARIN should keep stats on when these referrals time out, and when they work.</div><div class=""> </div><div class=""> If there is not a requirement for all whois clients to follow the referral, and this can be addressed on </div><div class=""> the server side, then lets address this on the server side. Double especially if this addresses an issue</div><div class=""> where providers publish rwhois data, but make it only accessible to the RIRs.</div><div class=""><br class=""></div><div class=""> Question: How will this interact with a whois client that currently follows the referral? </div></div></div></div></blockquote><div><br class=""></div><span class="Apple-tab-span" style="white-space:pre"> </span>While I agree with the original design being cleaner (the server does not recurse and recursion is left</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>to the client), the simple reality is that for whatever reason(s), most people are using whois clients</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>that don’t support recursion and therefore don’t recurse. Since it is easy and within ARIN’s capability</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>to mitigate the situation by modifying the server and outside of ARIN’s control and much more difficult</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>to get everyone’s client software updated, I think that this is a case where pragmatism should rule over</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>cleanliness and correctness and we should implement recursion in the server.</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>The server should provide notices to the client that recursion is being attempted, the name of the</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>server being recursed, etc. without any delay introduced by response time (or timeout) of the remote</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>server.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Question (RDAP specific): </div><div class=""><br class=""></div><div class=""> If ARIN was to allow the reporting of network sub-delegation information using RDAP, associated </div><div class=""> enabling software would be required. Should ARIN enable this method by creating an RDAP </div><div class=""> software suite that would allow ARIN registrants to run RDAP service locally?</div><div class=""><br class=""></div><div class="">Answer: Yes. It should be fairly easy to just open (part of) the source of your RDAP service.</div><div class=""> People can crib of that, and integrate with their IPAM / radius logs etc. </div><div class=""> Surely someone will voluntarily provide a packed binary, and the source for it.</div><div class=""> If not ARIN should fill this gap. </div></div></div></div></blockquote><div><br class=""></div><span class="Apple-tab-span" style="white-space:pre"> </span>If RDAP is to become an IETF standard, then IIRC, at least two implementations are required. I’m all for</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>ARIN being the ones to develop one of these implementations for the community if that is necessary,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>but I’m not in favor of ARIN unnecessarily reinventing the wheel if someone else has already provided</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>an open-source implementation of RDAP server and/or client, etc.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="">If ARIN supports RDAP referrals, should it sunset rwhois? No.</div><div class="">Is RDAP referrals better than rwhois referrals? I suspect mileage varies by organization.</div></div></div></div></div></blockquote><div><br class=""></div>I also suspect that this depends on perspective (familiarity with RDAP, familiarity with whois/rwhois,</div><div>existing installed base, publisher vs. consumer of data, etc.)</div><div><br class=""></div><div>Owen</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Whois example</div><div class="">===============</div><div class=""><div class="">whois -h <a href="http://whois.arin.net/" class="">whois.arin.net</a> 23.228.169.1</div><div class=""><br class=""></div><div class="">#</div><div class=""># ARIN WHOIS data and services are subject to the Terms of Use</div><div class=""># available at: <a href="https://www.arin.net/whois_tou.html" class="">https://www.arin.net/whois_tou.html</a></div><div class="">#</div><div class=""># If you see inaccuracies in the results, please report at</div><div class=""># <a href="https://www.arin.net/public/whoisinaccuracy/index.xhtml" class="">https://www.arin.net/public/whoisinaccuracy/index.xhtml</a></div><div class="">#</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">#</div><div class=""># The following results may also be obtained via:</div><div class=""># <a href="https://whois.arin.net/rest/nets;q=23.228.169.1?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2" class="">https://whois.arin.net/rest/nets;q=23.228.169.1?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2</a></div><div class="">#</div><div class=""><br class=""></div><div class="">NetRange: 23.228.128.0 - 23.228.191.255</div><div class="">CIDR: <a href="http://23.228.128.0/18" class="">23.228.128.0/18</a></div><div class="">NetName: GOOGLE-FIBER</div><div class="">NetHandle: NET-23-228-128-0-1</div><div class="">Parent: NET23 (NET-23-0-0-0-0)</div><div class="">NetType: Direct Allocation</div><div class="">OriginAS: AS16591</div><div class="">Organization: Google Fiber Inc. (GF)</div><div class="">RegDate: 2013-09-13</div><div class="">Updated: 2014-03-26</div><div class="">Ref: <a href="https://whois.arin.net/rest/net/NET-23-228-128-0-1" class="">https://whois.arin.net/rest/net/NET-23-228-128-0-1</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">OrgName: Google Fiber Inc.</div><div class="">OrgId: GF</div><div class="">Address: 1600 Amphitheatre Parkway</div><div class="">City: Mountain ViewNeither does WHOIS for records stored in the ARIN database (SWIP), so why should ISPs face an increased burden here if you are not also planning to eliminate whois?</div><div class=""><br class=""></div><div class="">StateProv: CA</div><div class="">PostalCode: 94043</div><div class="">Country: US</div><div class="">RegDate: 2010-10-08</div><div class="">Updated: 2017-01-28</div><div class="">Ref: <a href="https://whois.arin.net/rest/org/GF" class="">https://whois.arin.net/rest/org/GF</a></div><div class=""><br class=""></div><div class="">ReferralServer: rwhois://<a href="http://rwhois.googlefiber.net:8987/" class="">rwhois.googlefiber.net:8987</a></div><div class=""><br class=""></div><div class="">OrgAbuseHandle: GFA32-ARIN</div><div class="">OrgAbuseName: Google Fiber Abuse</div><div class="">OrgAbusePhone: +1-650-253-0000 </div><div class="">OrgAbuseEmail: <a href="mailto:abuse@googlefiber.net" class="">abuse@googlefiber.net</a></div><div class="">OrgAbuseRef: <a href="https://whois.arin.net/rest/poc/GFA32-ARIN" class="">https://whois.arin.net/rest/poc/GFA32-ARIN</a></div><div class=""><br class=""></div><div class="">OrgTechHandle: ZG39-ARIN</div><div class="">OrgTechName: Google Inc</div><div class="">OrgTechPhone: +1-650-253-0000 </div><div class="">OrgTechEmail: <a href="mailto:arin-contact@google.com" class="">arin-contact@google.com</a></div><div class="">OrgTechRef: <a href="https://whois.arin.net/rest/poc/ZG39-ARIN" class="">https://whois.arin.net/rest/poc/ZG39-ARIN</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">#</div><div class=""># ARIN WHOIS data and services are subject to the Terms of Use</div><div class=""># available at: <a href="https://www.arin.net/whois_tou.html" class="">https://www.arin.net/whois_tou.html</a></div><div class="">#</div><div class=""># If you see inaccuracies in the results, please report at</div><div class=""># <a href="https://www.arin.net/public/whoisinaccuracy/index.xhtml" class="">https://www.arin.net/public/whoisinaccuracy/index.xhtml</a></div><div class="">#</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Found a referral to <a href="http://rwhois.googlefiber.net:8987/" class="">rwhois.googlefiber.net:8987</a>.</div><div class=""><br class=""></div><div class="">%rwhois V-1.5:000090:00 <a href="http://rwhois.googlefiber.net/" class="">rwhois.googlefiber.net</a></div><div class="">network:ID:NET-GF-V4-23-228-169-0</div><div class="">network:IP-Network:<a href="http://23.228.169.0/29" class="">23.228.169.0/29</a></div><div class="">network:Org-Name:Wasatch Mental Health</div><div class="">network:Street-Address:750 N 200 W</div><div class="">network:Unit-Number:</div><div class="">network:City:Provo</div><div class="">network:State:UT</div><div class="">network:Postal-Code:84601</div><div class="">network:Country-Code:US</div><div class=""><br class=""></div><div class="">%ok</div></div><div class=""><br class=""></div><div class="">===============</div><div class="">end Whois example</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">What problem are we trying to solve?</div><div class="">If it is having </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Oct 12, 2017 at 4:33 PM, Andrew Dul <span dir="ltr" class=""><<a href="mailto:andrew.dul@quark.net" target="_blank" class="">andrew.dul@quark.net</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" class="">
<div class="gmail-m_-6268663168625075603moz-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 class="">
<br class="">
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 class="">
<br class="">
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 class="">
<br class="">
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 class="">
<br class="">
-Rwhois doesn't support encryption or data-integrity during
transport<br class=""></div></div></blockquote><div class=""><br class=""></div><div class=""><div class="">As Owen points out, neither does WHOIS for records stored in the ARIN database (SWIP), </div><div class="">so why should ISPs face an increased burden here if you are not also planning to eliminate whois?</div></div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" class=""><div class="gmail-m_-6268663168625075603moz-cite-prefix">
-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 class=""></div></div></blockquote><div class=""><br class=""></div><div class="">as stated above whois to rwhois automatic referrals needs to work everywhere.</div><div class=""><br class=""></div><div class=""><div class="">whois -h <a href="http://whois.arin.net/" class="">whois.arin.net</a> 23.228.169.1</div><div class=""><br class=""></div><div class="">#</div><div class=""># ARIN WHOIS data and services are subject to the Terms of Use</div><div class=""># available at: <a href="https://www.arin.net/whois_tou.html" class="">https://www.arin.net/whois_tou.html</a></div><div class="">#</div><div class=""># If you see inaccuracies in the results, please report at</div><div class=""># <a href="https://www.arin.net/public/whoisinaccuracy/index.xhtml" class="">https://www.arin.net/public/whoisinaccuracy/index.xhtml</a></div><div class="">#</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">#</div><div class=""># The following results may also be obtained via:</div><div class=""># <a href="https://whois.arin.net/rest/nets;q=23.228.169.1?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2" class="">https://whois.arin.net/rest/nets;q=23.228.169.1?showDetails=true&showARIN=false&showNonArinTopLevelNet=false&ext=netref2</a></div><div class="">#</div><div class=""><br class=""></div><div class="">NetRange: 23.228.128.0 - 23.228.191.255</div><div class="">CIDR: <a href="http://23.228.128.0/18" class="">23.228.128.0/18</a></div><div class="">NetName: GOOGLE-FIBER</div><div class="">NetHandle: NET-23-228-128-0-1</div><div class="">Parent: NET23 (NET-23-0-0-0-0)</div><div class="">NetType: Direct Allocation</div><div class="">OriginAS: AS16591</div><div class="">Organization: Google Fiber Inc. (GF)</div><div class="">RegDate: 2013-09-13</div><div class="">Updated: 2014-03-26</div><div class="">Ref: <a href="https://whois.arin.net/rest/net/NET-23-228-128-0-1" class="">https://whois.arin.net/rest/net/NET-23-228-128-0-1</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">OrgName: Google Fiber Inc.</div><div class="">OrgId: GF</div><div class="">Address: 1600 Amphitheatre Parkway</div><div class="">City: Mountain View</div><div class="">StateProv: CA</div><div class="">PostalCode: 94043</div><div class="">Country: US</div><div class="">RegDate: 2010-10-08</div><div class="">Updated: 2017-01-28</div><div class="">Ref: <a href="https://whois.arin.net/rest/org/GF" class="">https://whois.arin.net/rest/org/GF</a></div><div class=""><br class=""></div><div class="">ReferralServer: rwhois://<a href="http://rwhois.googlefiber.net:8987/" class="">rwhois.googlefiber.net:8987</a></div><div class=""><br class=""></div><div class="">OrgAbuseHandle: GFA32-ARIN</div><div class="">OrgAbuseName: Google Fiber Abuse</div><div class="">OrgAbusePhone: +1-650-253-0000 </div><div class="">OrgAbuseEmail: <a href="mailto:abuse@googlefiber.net" class="">abuse@googlefiber.net</a></div><div class="">OrgAbuseRef: <a href="https://whois.arin.net/rest/poc/GFA32-ARIN" class="">https://whois.arin.net/rest/poc/GFA32-ARIN</a></div><div class=""><br class=""></div><div class="">OrgTechHandle: ZG39-ARIN</div><div class="">OrgTechName: Google Inc</div><div class="">OrgTechPhone: +1-650-253-0000 </div><div class="">OrgTechEmail: <a href="mailto:arin-contact@google.com" class="">arin-contact@google.com</a></div><div class="">OrgTechRef: <a href="https://whois.arin.net/rest/poc/ZG39-ARIN" class="">https://whois.arin.net/rest/poc/ZG39-ARIN</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">#</div><div class=""># ARIN WHOIS data and services are subject to the Terms of Use</div><div class=""># available at: <a href="https://www.arin.net/whois_tou.html" class="">https://www.arin.net/whois_tou.html</a></div><div class="">#</div><div class=""># If you see inaccuracies in the results, please report at</div><div class=""># <a href="https://www.arin.net/public/whoisinaccuracy/index.xhtml" class="">https://www.arin.net/public/whoisinaccuracy/index.xhtml</a></div><div class="">#</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Found a referral to <a href="http://rwhois.googlefiber.net:8987/" class="">rwhois.googlefiber.net:8987</a>.</div><div class=""><br class=""></div><div class="">%rwhois V-1.5:000090:00 <a href="http://rwhois.googlefiber.net/" class="">rwhois.googlefiber.net</a></div><div class="">network:ID:NET-GF-V4-23-228-169-0</div><div class="">network:IP-Network:<a href="http://23.228.169.0/29" class="">23.228.169.0/29</a></div><div class="">network:Org-Name:Wasatch Mental Health</div><div class="">network:Street-Address:750 N 200 W</div><div class="">network:Unit-Number:</div><div class="">network:City:Provo</div><div class="">network:State:UT</div><div class="">network:Postal-Code:84601</div><div class="">network:Country-Code:US</div><div class=""><br class=""></div><div class="">%ok</div></div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" class=""><div class="gmail-m_-6268663168625075603moz-cite-prefix">
-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 class=""></div></div></blockquote><div class=""><br class=""></div><div class="">If this is a problem, then we should get support procedures for all who run an rwhois server, </div><div class="">publish them publicly, and see if that doesn't solve the problem.</div><div class=""><br class=""></div><div class="">If that doesn't solve it, maybe go as far as naming and shaming, or even considering if the organization</div><div class="">is in compliance the ARIN policy if the rwhois data is not generally reachable, and the data in SWIP is</div><div class="">not sufficient for ARIN policy compliance on its own. </div><div class=""><br class=""></div><div class="">John Sweeting, can ARIN staff reach out to the 372 orgs with an unresponsive rwhois server and ask them to fix it and run another test? </div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" class=""><div class="gmail-m_-6268663168625075603moz-cite-prefix">
-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. </div></div></blockquote><div class="">That seems to just work for my whois client. I don't see why it shouldn't work for all whois clients. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" class=""><div class="gmail-m_-6268663168625075603moz-cite-prefix"> <br class="">
-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 class="">
<br class="">
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 class=""></div></div></blockquote><div class=""><br class=""></div><div class="">I do not believe the problem space is any different with running a local RDAP server (at least at my organization).</div><div class="">I suspect it is not good for the community if I update whois data with the frequency I update my rwhois data whether that be RESTful, template, RESTful bulk, or template bulk. </div><div class=""> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF" class=""><div class="gmail-m_-6268663168625075603moz-cite-prefix">
<br class="">
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 class="">
<br class="">
1) Number of orgs which have IPv4 or IPv6 resources and a rwhois
record on their org-id.<br class="">
<br class="">
2) Number of IPv4 and IPv6 blocks with a rwhois server under the
org-id records<br class="">
<br class="">
3) Number of /24 IPv4 equivalents covered by the above records<br class="">
<br class="">
4) Number of /32 IPv6 equivalents covered by the above records<br class="">
<br class="">
5) Total number of unique rwhois servers<br class="">
<br class="">
6) Percent of rwhois servers which are online (complete a tcp
connection<br class="">
accept a string and respond with some text)<br class="">
<br class="">
7) Percent of rwhois server who appear to respond with a valid
record<br class="">
for an address within each allocated block<br class="">
<br class="">
<br class="">
Thanks,<br class="">
Andrew<div class=""><div class="gmail-h5"><br class="">
<br class="">
<br class="">
<br class="">
On 10/2/2017 8:19 AM, ARIN wrote:<br class="">
</div></div></div>
<blockquote type="cite" class=""><div class=""><div class="gmail-h5"><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">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 class="">
<br class="">
<a class="gmail-m_-6268663168625075603moz-txt-link-freetext" href="https://www.arin.net/participate/acsp/suggestions/2013-22.html" target="_blank">https://www.arin.net/<wbr class="">participate/acsp/suggestions/<wbr class="">2013-22.html</a><br class="">
<br class="">
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 class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">Method 1:<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span><br class="">
<br class="">
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="gmail-m_-6268663168625075603Apple-converted-space"> </span><br class="">
<br class="">
<a class="gmail-m_-6268663168625075603moz-txt-link-freetext" href="https://www.arin.net/resources/request/reassignments.html" target="_blank">https://www.arin.net/<wbr class="">resources/request/<wbr class="">reassignments.html</a><br class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">Method 2:<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span><br class="">
<br class="">
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 class="">
<br class="">
<a class="gmail-m_-6268663168625075603moz-txt-link-freetext" href="https://www.arin.net/resources/request/reassignments_rwhois.html" target="_blank">https://www.arin.net/<wbr class="">resources/request/<wbr class="">reassignments_rwhois.html</a> <wbr class=""> <span class="gmail-m_-6268663168625075603Apple-converted-space"> </span><br class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">Method 3:<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span><br class="">
<br class="">
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 class="">
<br class="">
<a class="gmail-m_-6268663168625075603moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc7482" target="_blank">https://tools.ietf.org/html/<wbr class="">rfc7482</a><br class="">
<a class="gmail-m_-6268663168625075603moz-txt-link-freetext" href="https://www.arin.net/resources/rdap.html" target="_blank">https://www.arin.net/<wbr class="">resources/rdap.html</a><br class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">Options Going Forward<br class="">
<br class="">
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 class="">
</p>
<ul style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">
<li class="">Question (general):<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span></li>
</ul><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
Of the three sub-delegation reporting methods listed
(SWIP, RWhois, RDAP), which should ARIN support in the future?<br class="">
</p>
<ul style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">
<li class="">Question (SWIP/RESTful API specific):<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span></li>
</ul><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
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 class="">
</p>
<ul style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">
<li class="">Question (RWhois specific):<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span></li>
</ul><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
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 class="">
</p>
<ul style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">
<li class="">Question (RDAP specific):<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span></li>
</ul><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
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 class="">
<br class="">
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="gmail-m_-6268663168625075603Apple-converted-space"> </span><br class="">
<br class="">
Discussion on<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span><a class="gmail-m_-6268663168625075603moz-txt-link-abbreviated" href="mailto:arin-consult@arin.net" target="_blank">arin-consult@arin.net</a><span class="gmail-m_-6268663168625075603Apple-converted-space"> </span>will close on 27 October
2017. If you have any questions, please contact us at<span class="gmail-m_-6268663168625075603Apple-converted-space"> </span><a class="gmail-m_-6268663168625075603moz-txt-link-abbreviated" href="mailto:info@arin.net" target="_blank">info@arin.net</a>.<br class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">Regards,</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class="">John Curran<br class="">
President and CEO<br class="">
American Registry for Internet Numbers (ARIN)</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
</p><p style="font-family: -webkit-standard; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; background-color: rgb(255, 255, 255);" class=""><br class="">
</p>
<br class="">
<fieldset class="gmail-m_-6268663168625075603mimeAttachmentHeader"></fieldset>
<br class="">
</div></div><pre class="">______________________________<wbr class="">_________________
ARIN-Consult
You are receiving this message because you are subscribed to the ARIN Consult Mailing
List (<a class="gmail-m_-6268663168625075603moz-txt-link-abbreviated" href="mailto:ARIN-consult@arin.net" target="_blank">ARIN-consult@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="gmail-m_-6268663168625075603moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-consult" target="_blank">http://lists.arin.net/mailman/<wbr class="">listinfo/arin-consult</a> Please contact the ARIN Member Services
Help Desk at <a class="gmail-m_-6268663168625075603moz-txt-link-abbreviated" href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.</pre>
</blockquote><p class=""><br class="">
</p>
</div>
<br class="">______________________________<wbr class="">_________________<br class="">
ARIN-Consult<br class="">
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br class="">
List (<a href="mailto:ARIN-consult@arin.net" class="">ARIN-consult@arin.net</a>).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" rel="noreferrer" target="_blank" class="">http://lists.arin.net/mailman/<wbr class="">listinfo/arin-consult</a> Please contact the ARIN Member Services<br class="">
Help Desk at <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.<br class=""></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature"><font color="#555555" face="'courier new', monospace" class=""><div class=""><span style="font-family: arial;" class=""><font color="#555555" face="'courier new', monospace" class="">_______________________________________________________<br class=""></font><div class=""><font face="'courier new', monospace" class="">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank" class="">jschiller@google.com</a>|571-266-0006</font></div><div class=""><font face="'courier new', monospace" class=""><br class=""></font></div></span></div></font></div>
</div></div></div></div>
_______________________________________________<br class="">ARIN-Consult<br class="">You are receiving this message because you are subscribed to the ARIN Consult Mailing<br class="">List (<a href="mailto:ARIN-consult@arin.net" class="">ARIN-consult@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="http://lists.arin.net/mailman/listinfo/arin-consult" class="">http://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br class="">Help Desk at <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.</div></blockquote></div><br class=""></body></html>