[ARIN-consult] [E] Re: Consultation on Orphaned Organization (Org) and Point of Contact (POC) Records

Thu Aug 2 11:05:57 EDT 2018

Yes, some of those are very much expected. However, there have been
approximately 1500 transfers in the last year, which is less than 3% of the
abandon organization in the last year. So, something other than transfers
accounts for the vast majority of abandoned organizations.

I suspect reallocations and reassignments, but that is just a guess. If
those reallocations and reassignments were for a year or so and this is
just annual churn, that's fine. However, if these reallocations and
reassignments were short-term, like weeks or months, then maybe we need to
change some policies. Worse yet if the organizations never had resources
associated with them, then something seems broken somewhere. Maybe calling
for even shorter-term garbage collection, like monthly.  But, I wouldn't
recommend going there without a better understanding of what and why this
is happening.

Thanks.

On Thu, Aug 2, 2018 at 8:30 AM, <stephen.r.middleton at verizon.com> wrote:

> Hello David,
>
>
>
> I suspect that we are seeing an uptick in orphaned supporting records
> (Orgs and POCs) relating to the increase in ARIN Fees (account
> consolidations to reduce costs) and the sale of IPv4 addresses where the
> total held assets are transferred.  In both cases we are seeing
> consolidations and centralizations of resources creating more orphans.
>
>
>
> That said, I’m onboard with wanting to know the cause of the orphans.  How
> many of the newly created 63K were direct recourse holders and how many
> were reassignments?  Of the former direct resource holders; how many became
> orphans through a transfer to specified recipient?
>
>
>
> Best Regards,
>
>
>
>
> [image: Verizon] <http://www.verizon.com/>
>
> Stephen R. Middleton, Sr.
> Global IP Address Management
> Public Data Network Engineering
>
> 22001 Loudoun County Parkway
> <https://maps.google.com/?q=22001+Loudoun+County+Parkway&entry=gmail&source=g>;
> F1-2-277
> Ashburn, VA 20147
>
> Office 703.694.6965
> stephen.r.middleton at one.verizon.com
>
> [image: Facebook] <http://www.facebook.com/verizon>  [image: Twitter]
> <http://twitter.com/verizon>  [image: LinkedIn]
> <http://www.linkedin.com/company/verizon>
>
>
>
> *From:* ARIN-consult [mailto:arin-consult-bounces at arin.net] *On Behalf Of
> *David Farmer
> *Sent:* Wednesday, August 01, 2018 6:11 PM
> *To:* ARIN <info at arin.net>
> *Cc:* <arin-consult at arin.net> <arin-consult at arin.net>
> *Subject:* [E] Re: [ARIN-consult] Consultation on Orphaned Organization
> (Org) and Point of Contact (POC) Records
>
>
>
> 63,455 organizations orphaned in the last year seems like a lot to me.
> Were these organizations ever associated with resources? How long ago were
> they created? How long were they associated with resources? How many of
> these organizations were child organizations, from reallocations or
> reassignments? How many created by ARIN making allocations or assignments?
>
>
>
> This cleanup should happen. However, it kind of sounds like something is
> broken somewhere too. If that is the case, that should get fixed too.
>
>
>
> Thanks
>
>
>
> On Wed, Aug 1, 2018 at 1:44 PM, ARIN <info at arin.net> wrote:
>
> In an effort to improve the quality and integrity of the data in the
> ARIN database, we are exploring a number of new and improved processes
> and procedures.  As part of this effort, we are proposing that ARIN
> establish a routine procedure for deleting and archiving orphaned
> Organization (Org) and Point of Contact (POC) records in the ARIN database.
>
> We have defined an "orphaned Organization" as one that has no registered
> number resources. An "orphaned POC" is defined as one that is not
> directly associated with any number resources nor associated with any
> organization that has registered number resources.
>
> There are several compelling reasons to consider deletion of orphaned
> Orgs and POCs.  Long orphaned Orgs and POCS are likely to serve no
> purpose in the registry, they often contain outdated information, and
> their presence may expose personal data in a manner that may be
> inconsistent with ARIN's personal data privacy policy.
> (https://www.arin.net/privacy.html
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.arin.net_privacy.html&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=PNlZCOTcrBXvix6v31kntg680rC2tshHDXM0RcJv5bE&m=LFgJxgMS40VfZPs9tLL-aizJEVY9RPLkdZ9rMm7qbnM&s=Yq3mov8a1IhXpwkYAuduKiER8MwxDyFAllY059ixUW0&e=>
> )
>
> An analysis of the ARIN registry for orphaned records has shown the
> following results:
>
> Total # of registered Orgs in ARIN's database:  926,474
> Total # of Orgs that have been orphaned for 1+ years:  317,730
> Total # of Orgs that have been orphaned for 2+ years:  254,275
>
> Total # of registered POCs in ARIN's database:  919,050
> Total # of POCs that have been orphaned for 1+ years:  351,644
> Total # of POCs that have been orphaned for 2+ years:  291,741
>
> The proposed procedure would result in the deletion and archival of all
> Orgs and POCs that have been orphaned for 2 or more years.   This
> procedure would be run on a quarterly basis initially, with the plan
> being to move to a more frequent basis (such as monthly) once there is
> operational experience.  All orphaned data will be removed from the
> database and archived in perpetuity.  Note that deleted unique Org and
> POC handles will not be re-utilized.
>
> We are seeking community feedback on this proposed modification to
> current ARIN practices with regards to data maintenance.
>
> This consultation will remain open for thirty (30) days, after which the
> staff will re-evaluate our direction based on any community feedback
> received.
> Comments and Feedback
>
> Please provide comments to arin-consult at arin.net. You can subscribe to
> this mailing list at:
> http://lists.arin.net/mailman/listinfo/arin-consult
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.arin.net_mailman_listinfo_arin-2Dconsult&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=PNlZCOTcrBXvix6v31kntg680rC2tshHDXM0RcJv5bE&m=LFgJxgMS40VfZPs9tLL-aizJEVY9RPLkdZ9rMm7qbnM&s=Nw6o8JGrzLKkS4wQZDy4h7JMF0lAjLqbEPMof9FHbdA&e=>
> .
>
> Discussion on arin-consult at arin.net will close on 31 August 2018.
>
> If you have any questions, please contact us at info at arin.net
>
> Regards,
>
> John Curran
> President and CEO
> American Registry for Internet Numbers (ARIN)
>
>
>
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN
> Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-consult
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.arin.net_mailman_listinfo_arin-2Dconsult&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=PNlZCOTcrBXvix6v31kntg680rC2tshHDXM0RcJv5bE&m=LFgJxgMS40VfZPs9tLL-aizJEVY9RPLkdZ9rMm7qbnM&s=WG-vdW-qH3SVAcJTfEE_WAXMYdKYCldH8ZpuWwlA3PE&e=>
> Please contact the ARIN Member Services
> Help Desk at info at arin.net if you experience any issues.
>
>
>
>
>
> --
>
> ===============================================
> David Farmer               Email:farmer at umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE
> <https://maps.google.com/?q=2218+University+Ave+SE&entry=gmail&source=g>
>       Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
>

-- 
===============================================
David Farmer               Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20180802/85950651/attachment.html>