I wonder if a tactic to address this issue is expanding the use of the Router POC. Maybe a Router POC could be created at the resource level or with a Detailed Reassignment instead of a Router POC at the Organization Level, providing a fine-grained mechanism to delegate control of ROA and IRR.
Just a thought. On Mon, Jun 24, 2024 at 8:34 AM Andrew Gallo <[email protected]> wrote: > > If a holder of address resources reassigns or reallocates a portion of > that space, who can create an RPKI ROA? The original holder (parent), > the downstream org that has the delegated portion of the space? > > The three options for reassignment/reallocation are > Simple Reassignment > Detailed Reassignment > Reallocation > (definitions below) > > Based on my reading, Simple Reassignment allows only the 'parent' (or > delegating) org allowed to create ROAs. But what about Detailed? The > downstream org can have POCs and maintain reverse nameserver records. > Can they also generate ROAs or IRR objects? > > What about Reallocation? > > Thank you. > > > > > > > Simple Reassignment > > Use this option if you will manage abuse and network contacts for > > your customer. > > > > Detailed Reassignment > > Use this for a downstream organization that needs to maintain its > > own reverse nameservers and/or separate Point of Contact (POC) > > information. > > > > Reallocation > > Use this for a downstream organization that needs to maintain its > > own reverse nameservers and/or separate Point of Contact (POC) > > information and make reassignments of IP addresses to its own customers. > > > > _______________________________________________ > arin-tech-discuss mailing list > [email protected] > https://lists.arin.net/mailman/listinfo/arin-tech-discuss > -- =============================================== David Farmer Email:[email protected] 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 ===============================================
_______________________________________________ arin-tech-discuss mailing list [email protected] https://lists.arin.net/mailman/listinfo/arin-tech-discuss
