[ARIN-Suggestions] Three Suggestions Closed: 2009.21, 2013.4 & 2014.27

Tue Jun 23 15:30:36 EDT 2015

ARIN has issued its final responses to ACSP Suggestions 2009.21, 2013.4, 
and 2014.27. The suggestions and response text are provided below. These 
suggestions are now closed and are available at:

https://www.arin.net/participate/acsp/suggestions/2009-21.html
https://www.arin.net/participate/acsp/suggestions/2013-4.html
https://www.arin.net/participate/acsp/suggestions/2014-27.html

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)

****
Suggestion: 2009.21: COMMON RIR WHOIS SYNTAX*

This suggestion appeared in an email message on NANOG. I think that ARIN 
should consider it and formally reply to Bill Manning.
from bmanning at vacation.karoshi.com
to    Randy Bush <randy at psg.com>
cc nanog at nanog.org
date    Wed, Nov 25, 2009 at 10:32 AM
subject    Re: Who doesn't have AS 1712?
On Wed, Nov 25, 2009 at 06:36:13PM +0900, Randy Bush wrote:
 > > Perhaps the RIRs could get together and agree on a common whois
 > > syntax so that when I check one RIR with one syntax - it would work
 > > on others as well? This issue has been around for over 7 years and
 > > I can't understand why the RIRs can't find common ground for the 
sake of the end users?
 >
 > s/7/15/ it was already feeling like brickmarks on my forhead at the
 > first s'holm ietf in '95
 >
 > randy
there are solutions, rwhois, iris, etc. some require changed behaviours
from the actors, (why RIPE decided unilaterally to change the flags/syntax
of whois escapes me at the mo), and some do not.
basically we are stuck w/ things like whois, swip, ad-nausea, due to
simple intertia.
and here is a saving grace... IPv6.
once, abt 8/9 years ago, I was talking w/ Richard Jimmerson about the
wonderful opportunity the RIRs had to build a scalable, extensable resource
tracking system that could be easily deployed by the RIR clients and 
seamlessly
integrated into a heirarchy of resource management segments.
the rational was/is that the RIRs are handing out functionally the entire
IPv4 address pool to any and all comers. Thats the size of a /32, presuming
one buys into the /64 chastity belt the IETF has wrapped around the 
lower 64
bits.
How is a lowly ISP expected to track/manage address assignments over such a
huge space w/o decent toolage?
so we can let our collective interia drag us down into increasing chaos or
we can use this one time chance to pull our collective bacon out of the 
fire.
After SIDR - I think development and deployment of this type of thing would
be a worthwhile use of my RIR fees.
YMMV of course.
--bill

*Response:*

/11 December 2009/
There have been many attempts to unify directory services over the 
years; from SWIP, whois++, and more recently IRIS and Joint Whois. 
Currently, we are engaged in an ARIN-initiated effort called Whois-RWS 
(http://whoisrws-demo.arin.net). At the most recent ARIN meeting in 
Dearborn MI, we demonstrated this code and are waiting for input from 
the community. We have a mailing list setup for community feedback on 
this effort. To participate, join the mailing list at 
http://lists.arin.net/mailman/listinfo/arin-whoisrws.
One these improvements are fully in production, ARIN will begin to 
explore common syntax methods with the other RIRs. This will not occur 
immediately but is in ARIN's roadmap for improved services to the community.

/20 July 2011/
Michael,
ARIN is an active participant in the IETF WEIRDS effort, and plans to 
attend upcoming IETF meetings regarding syntax among the RIRs. This 
suggestion will remain open until resolved.

/22 June 2015/
Thank you for your suggestion, numbered 2009.21 upon confirmed receipt. 
As you know, this suggestion was taken up by the WEIRDS Working Group at 
the IETF and has required extensive coordination among the RIRS. The new 
standard, Registration Data Access Protocol (RDAP), was adopted in March 
of 2015.
ARIN completed its deployment of RDAP on 20 June 2015, and you can find 
details about this service at: https://www.arin.net/resources/rdap.html
RDAP has been deployed by APNIC and LACNIC and anticipates deployment by 
the other RIRs and domain name registries over time. This suggestion is 
now completed and closed.
Thank you for participating in the ARIN Consultation and Suggestion Process.

****
**Suggestion: ***** *2013.4: CHANGE WHOIS OUTPUT FOR CERTAIN /8 RECORD*S

I would like ARIN to consider and act on this request so suppress the 
RIR /8 output when a more specific DA or DS exists, and instead, display 
the DA or DS.
This is specify for 154/8 however I feel it should cover any space ARIN 
has in it's registry.
This request is intended to allow the referrals for the specific space 
to be returned.
Please see ARIN-20130219.211 for additional information behind this request.

*Response:*

/22 March 2013/
Thank you for your suggestion. This behavior started when Whois-RWS 
rolled out in March 2011. The issue exists only with ERX space (where 
another RIR is authoritative for the /8). We don't show /8's in ARIN 
space if the query hits a DA or DS record. It does break RWhois 
referrals, but as far as we know, that is all that it breaks. So ARIN 
essentially has 2 choices here:
Continue to show the majority RIR when someone looks up an IP address 
outside of the ARIN region Or
Stop showing the ERX /8 record, which fixes the rwhois referral problem. 
But keep in mind, if we remove the /8 for the minority /8s, we won't be 
telling folks which RIR has the block they're looking for.
We believe that it would be prudent to put this suggestion, with 
potential solutions, out to the community as a consultation in order to 
get additional feedback on this issue. Please be sure to add your 
opinion to the consultation.

/03 June 2013/
The ARIN community consultation on a proposed change to Whois output for 
certain /8 records is now closed. Based on feedback received and 
internal staff deliberation, ARIN's directory services (Whois and 
Whois-RWS) will be modified to publish only the DA or DS record for an 
allocation made in a /8 where another RIR manages that particular /8. If 
there is no corresponding DA or DS record in ARIN's service for that /8, 
ARIN will publish the /8 of the authoritative RIR and the referral to 
that particular RIR's directory service.
This suggestion will be added to the list of outstanding projects 
awaiting prioritization found at:
https://www.arin.net/features/#tbd
This suggestion will remain open.

/26 September 2013/
As part of the ARIN 32 ACSP Consultation: Open Suggestion Review and 
Project Prioritization Survey, we're providing feedback and estimates on 
the predicted work involved. For this suggestion, the following is noted:
Estimated staff effort to implement: 2.5 person months, plus 
communications efforts.
For information about the consultation and how to participate in the 
survey, please see the 26 September 2013 announcement.

/22 June 2015/
Thank you for your suggestion, numbered 2013.4 upon confirmed receipt. 
Your suggestion has been completed and is now closed.
As of ARIN's software deployment on 20 June 2015, ARIN's directory 
services (Whois and Whois-RWS) will be modified to publish only the DA 
or DS record for an allocation made in a /8 where another RIR manages 
that particular /8. If there is no corresponding DA or DS record in 
ARIN's service for that /8, ARIN will publish the /8 of the 
authoritative RIR and the referral to that particular RIR's directory 
service.
Thank you for your participation in the ARIN Suggestion and Consultation 
Process.

****
**Suggestion: ***** *2014.27: DAILY REPORT OF ARIN-ISSUED AS NUMBERS*

At the moment IPv4 and IPv6 prefix assignments and removals are listed 
daily on the ARIN issued list. New AS number assignments are not 
currently listed anywhere at the moment.
It would be nice to have the ASNs which were assigned in a day also on 
either ARIN issued, or another list for ASN assignments if its decided 
that ASNs would not be appropriate on the ARIN-issued list.
Value to Community: The value to the community by listing the daily 
assigned ASNs, would be to those who closely monitor the validity of 
routes, via as-path, for impossible combinations. There are currently 
services for IPv4/IPv6 like the cymru bogons feed,
http://www.team-cymru.org/Services/Bogons/

*Response:*

/22 October 2014/
Thank you for submitting your suggestion, numbered 2014.27, on the topic 
of adding daily reporting of the AS numbers issued by ARIN.
ARIN currently publishes a daily report of the IPv4 and IPv6 resources 
issued for that day. You have suggested either ARIN add the AS number 
information to the existing report, or to have a similar report specific 
to AS numbers published daily. We understand your suggestion and agree 
this public information is something that ARIN can report on a daily 
basis. We anticipate this suggestion will be prioritized for action and 
implemented within the first half of 2015. ARIN will keep this 
suggestion open until it is completed.
/
//22 June 2015/
Thank you for submitting your suggestion, numbered 2014.27, on the topic 
of adding daily reporting of the AS numbers issued by ARIN.
ARIN has implemented this functionality, and AS number information is 
now incorporated into the daily ARIN-issued report. We issued an 
announcement about this impending change on 19 May, 2015 noting that
ASNs will be added to the existing report in the following format:
Remove AS<number>-AS<number>
Remove AS<number>
Add AS<number>
Add AS<number>-AS<number>
Where <number> is either a 2- or 4-byte ASN.
This suggestion is now closed and marked as completed.
Thank you for your participation in the ARIN Suggestion and Consultation 
process.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-suggestions/attachments/20150623/1efc9957/attachment.html>