ACSP Suggestion 2011.12: Add Contract field to WHOIS

Suggestion

Author: Owen DeLong   
Submitted On: 25 March 2011

Description:

ARIN should add to the WHOIS and any other published address directory services the RSA or not status of each delegation.

Ideally, this should be a single “Contract:” field which would contain one of “None”, “LRSA”, or “RSA”.

Timeframe: Immediate

Status: Closed   Updated: 13 June 2011

Tracking Information

ARIN Comment

07 April 2011

Since organizations may have differing views on their organization’s contract information being published (and there is potential interaction with existing non-disclosure agreements), ARIN staff and legal need to do additional research on the implications of this suggestion. ARIN will report back with an appropriate implementation approach, which may result in bringing this suggestion to the community as a consultation or a formal policy proposal.

This suggestion will remain open and given the upcoming meeting and follow-up work thereafter, ARIN will report back on this suggestion by mid-May 2011.

ARIN Comment

31 May 2011

We have performed and initial review, but we require additional time for thorough staff and legal review. Please expect for us to bring closure on this no later than June 15, 2011.

This suggestion remains open.

ARIN Comment

13 June 2011

As you know from my response on PPML, I am supportive of this suggestion. It turns out to be rather challenging in practice, because any signed agreement with ARIN is inherently under non-disclosure from a legal perspective. In addition, ARIN has many non-disclosures executed at the request of organizations which specifically prohibit such information from being published. The effect of both of these conditions is that we would need an explicit waiver before being able to publish the contractual status information in WHOIS.

It would be difficult and quite costly for ARIN to seek an NDA waiver approval from every organization, and it is likely that many organizations not respond positively or not respond at all to such a waiver request. This leaves ARIN unable at present to provide to provide the data in a consistent manner per your suggestion. While ARIN will not be implementing your suggestion, but we will look into whether future changes to the registration services agreement could bring about a similar outcome in the future.

Let me know if you have any further suggestions.

Regards,
/John

John Curran
President and CEO
ARIN