> On Apr 27, 2022, at 11:23, John Curran wrote:
>
> Owen -
>
> Yes, apparently RIPE makes the address blocks themselves somehow “magical” in
> nature for perpetuity regardless of who is the address holder - certainly an
> interesting approach when one considers the implications.
>
>
Owen -
Yes, apparently RIPE makes the address blocks themselves somehow “magical” in
nature for perpetuity regardless of who is the address holder - certainly an
interesting approach when one considers the implications.
However, ARIN is the formal successor administrator of its registry with
Interestingly, if your resources were issued by an organization that was not
one of the current 5 RIRs at the time of issuance, RIPE will consider your
resources eligible to be treated as “legacy without contract” when you transfer
to RIPE.
This is, by far, the most liberal and most respectful
Thank you for the clarification. And I eagerly await the policy proposal
changing that language.
I meant to ask this at the Open Mic session this morning, but I had someone
at my door and by the time I got back, the meeting was all over.
WOW, that was quick!
I hope everyone has a safe trip
David,
While every issued resource is allocated the size of IPv6 is determined by the
policy they are requested under as either end user or ISP. So an ISP requesting
IPv6 is still evaluated under NRPM 6.5.2 and an end user is evaluated under
NRPM 6.5.8. It is my understanding that the ARIN AC
In I believe the IANA resource report at ARIN 49, John Sweeting mentioned
that ARIN is now only making allocations. Since the smallest IPv6
allocation in policy is a /40, does that mean that ARIN is no longer
handing out /48s or /44s to organizations that formerly would have
received end-users
On 26 Apr 2022, at 7:45 PM, Martin Hannigan
mailto:hanni...@gmail.com>> wrote:
On Tue, Apr 26, 2022 at 6:20 PM Andrew Dul
mailto:andrew@quark.net>> wrote:
Legacy holders have the option to add records to ARIN’s authenticated irr. It
only requires them to sign an lrsa or rsa. In my
Folks -
It’s important to note that these references shared below are _not_ based on a
common definition of “legacy number resource" –
ARIN considers a legacy number resource to be one that’s held by the original
registrant (or their legal successor, e.g. due to merger) and that was issued
