Your IP address could not be determined at this time.

ACSP Suggestion 2013.15: Availability of ARIN Online Messages to All POCs of an Org ID

Suggestion

Author:
Janine Moses
Submitted On:
23 May 2013

As the POC and company exec, I would appreciate the ability to at least "view" correspondence between other company employees with access and ARIN. ARIN has asked for company specific information that the employee may/may not have, however I cannot access the request in order to respond to ARIN and the request is 'sitting' unanswered.

Timeframe: Immediate

Status:
Open
Updated:
26 September 2013

Tracking Information

ARIN Comment

17 June 2013

Thanks for your suggestion, numbered 2013.15 upon confirmation, proposing the ability to allow all Points of Contact view ARIN/employee correspondence for a given organization. We have previously received similar recommendations verbally as well as through the suggestions process, see Suggestion 2013.13: Availability of ticket information to all POCs of an Org ID. While you did not indicate, I presume that you are suggesting similar functionality within ARIN Online. If this is not the case, please let me know.

Given the interest in having the ARIN Online security model modified to allow such capability, we will evaluate the effort and schedule it appropriately with other priorities. Once scheduled, we will add it to ARIN's Planned Functionality webpage (https://www.arin.net/features/) and inform you of its assigned priority. In the interim, please let us know directly at hostmaster@arin.net if a request/ticket becomes 'stranded' and we will work with you to resolve the 'view' correspondence issue.

This suggestion will remain open until implemented.

ARIN Comment

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:

ARIN's Engineering Department needs to know what type of ticket type requests this work needs to address. There are several corner cases and we want to make sure we satisfy the most used use case. Estimated staff effort to implement for ALL tickets: 12+ person months, plus communication efforts. (This would also include implementation of 2013.13: Availability of Ticket Information to All POCs of an Org ID)

For information about the consultation and how to participate in the survey, please see the 26 September 2013 announcement.