[address-policy-wg] Maximum size for current IPv4 allocations

Dear Ronald,

On 15/08/2022 12:45, Ronald F. Guilmette wrote:
> In message <19f8c8b6-0590-8903-0e9e-ec6638d1f442 at ripe.net>,
> Marco Schmidt <mschmidt at ripe.net> wrote:
>
>> As Elvis clarified, the examples you listed are the results of resource
>> transfers.
>>
>> The “netname:” attribute of an INETNUM object in the RIPE Database
>> indicates whether an IPv4 allocation was received directly from the RIPE
>> NCC or via a transfer.
> Please elaborate.   How does it do that exactly?  For example, what does
> this value tell us about how the block was received?
>
>     CH-AS5398-20191016
The last part of the netname is the date when the resource was allocated 
by the RIPE NCC, in this example 16 October 2019.
>
>> It includes the date on which that range was
>> provided by the RIPE NCC, also for smaller ranges that are part of a
>> previously bigger range. If the date in the “netname:” and the date on
>> which the object was created differ, you can deduce that the range
>> concerned was not allocated directly by the RIPE NCC.
> In other words you are saying that 193.222.104.0/23 wasw purchased, correct?

If the dates differ, this only indicates that a change of the resource 
holder took place, either for this range directly or another part of a 
previously larger address block. Such change can be a policy transfer, a 
company merger or a network acquisition. The RIPE NCC is not involved in 
the financial details of such update.

Kind regards,
Marco Schmidt
RIPE NCC


>
>> I hope this helps answer your question.
> It may, once I understand clearly everything you just said.
>
>
> Regards,
> rfg
>