[ARIN-Suggestions] New ACSP Suggestions

ARIN info at arin.net
Fri Jan 14 15:00:40 EST 2022


Three new suggestions were recently submitted to ARIN’s Consultation and Suggestion Process (ACSP). Two are in review and pending response, and the third has been closed as out of scope.

 

ACSP Suggestion 2022.1: Change Nomenclature Regarding Points of Contact

 

https://www.arin.net/participate/community/acsp/suggestions/2022/2021-01/

Description: Contact information objects (“POCs”) should not be referred to as “POCs” because that could also mean “person of color”, effectively perpetuating racism to Blacks. Please rename “POC” to something else. 

Value to Community: Makes ARIN community more inclusive 

Timeframe: Not specified 

Response Pending

 
ACSP Suggestion 2022.2: Operational Support for Ghostbusters RPKI records per RFC 6493
https://www.arin.net/participate/community/acsp/suggestions/2022/2021-02/

 

Description: Please support creation, maintenance, and publication of Ghostbusters RPKI records per RFC 6493 

Value to Community: Would allow for contacting relevant parties to debug operational RPKI issues. 

Timeframe: Not specified 

Response Pending

 
ACSP Suggestion 2022.3: Contact Information on Domains
https://www.arin.net/participate/community/acsp/suggestions/2022/2021-03/
 Description: Re-evaluate the process and consequences of failing to respond, validate or update WHOIS contact information on domains 

Value to Community:

Currently, if an email is missed and contact information isn’t validated or updated the domain name is locked. In certain cases, where all email accounts required to validate and resolve the issues are of the domain in question. Registrars force users to engage in a lengthy process that can take up to 72 hours. This is untenable as financial harm is brought upon business over an assumption that a domain, that was once already purchased, and validated as owned by a real person is no longer the case, purely on the passage of time.

It’s far to easy to miss or mischaracterize these emails by office staff. The concept that somehow a domain, owned by a business with no changes required to it’s contact information somehow is invalidated by default is ridiculous.

At the very least, registrars should have the flexibility to enable the domain on a temporary basis to enable the exact DNS records that were working before the hold to allow communications to email accounts configured under that domain and required to resolve any issues.

Timeframe: Not specified 

Response:

Thank you for your suggestion, numbered 2022.3 on confirmed receipt, asking that ARIN re-evaluate the process and consequence of failing to update or validate Whois contact information. Your suggestion specifies this as an issue related to management of domain names, and because that data is not part of ARIN’s Whois this is not an issue under our control. This is a matter for the domain registry based on the details you provided.

We are closing this suggestion as Out of Scope.

 

 

Regards,

 

American Registry for Internet Numbers (ARIN)

 

 

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-suggestions/attachments/20220114/47074f9d/attachment.htm>


More information about the arin-suggestions mailing list