There’s multiple ways to make this work - 

E.g.  a new RIR for the “region” - simple enough - form an RIR per ICP-2 (or the new RIR Governance doc), get organized, and then apply for recognition.

Or just make use of an existing RIR and apply under their existing policies for ISPs/LIRs as necessary to get the space needed.

Either of these work -  as the Internet Number Registry System is more than a table of entries; it’s a mechanism for the community come together, interact and self-govern operation of an actual system - and either approach provides clarity of who the community is, and how applicable policies are established and updated.  Either approach allow for the operators to interact with the rest of the community - fairly important for making sure services RDAP and RPKI work across the entire registry.

The approach that lacks clarity is what Tony seems to propose - there’s would be a new region with a distinct set of policies and set of operators but they not have an RIR governance model (ala ICP-2/RIR Governance doc) or any interaction with this community….  They’d be run by an existing RIR as if they were a distinct RIR, but minus the community and the governance model. 

/John

John Curran
President and CEO
American Registry for Internet Numbers


On Feb 20, 2026, at 4:28 AM, Seun Ojedeji <seun.ojedeji@gmail.com> wrote:


Well this would be straight forward approach, but I do think respective RIRs may need a review of their "out of region" definition. 

Regards

----
Sent from my mobile
kindly excuse typos

On Fri, 20 Feb 2026, 3:16 am John Curran, <jcurran@arin.net> wrote:
Gert -
   Yes, the “IPv4” qualifier was unnecessary and likely not relevant; instead read that as -

“So general purpose Internet number resource address blocks are issued to RIRs accordingly global number resource policy, and then there’s some “regional" policy regarding from the block to the individual ISPs/LIPs.”

I.e, the question remains as to why a distinct RIR region is necessary here, rather than (as Randy said) just having the involved operators go to any RIR and obtain an appropriately sized IPv6 allocation.

/John

> On Feb 20, 2026, at 3:36 AM, Gert Doering <gert@space.net> wrote:
> Hi,
>
> On Thu, Feb 19, 2026 at 10:26:18PM +0000, John Curran wrote:
>> So general purpose IPv4 address blocks are issued to RIRs [..]
>
> why would anyone want to build this with IPv4?
>
> Gert Doering
>        -- NetMaster
> --
> have you enabled IPv6 on something today...?
>
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard,
>                                           Karin Schuler, Sebastian Cler
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: Dr. Frank Thiäner
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
> -----
> To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
> As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
> More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
> <signature.asc>
-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
-----
To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/