[address-policy-wg] 2017-01 New Policy Proposal (Publish statistics on Intra-RIR Legacy updates)

Hello Erik,

We would like to provide some clarification regarding your point on publishing transfer statistics for legacy updates.

On 2017-05-02 15:39:39 CET, Erik Bais wrote:
> And I like to put the emphasis on :  
> 
>  
> *        The RIPE NCC will publish a list of all transfers.
> 
> And 
> 
> *        Whether it was a transfer according to this policy or a transfer
> due to changes to an organisation's business structure (such as a merger or
> acquisition)
> 
> This paragraph 4 isn’t a part of the paragraph 3.. (3.0 Inter-RIR Transfers
> )  
 or the limitations in paragraph 2 (2.0 Transfers within the RIPE NCC
> Service Region)  
> 
> And there is also no difference between RIPE PA or Legacy space in that
> section 
  
> 
> So how I read (and wrote) the policy is that the Transfer statistics should
> be published on all transfers.  
> 
> *        A transfer can be a change of resources from company name A to
> company name B .. (via the M&A process)  
> 
> *        Or via the actual Transfer procedure 
  
> 
> *        Or a company name change .. ( company A is now known as company B,
> but same company, same owners etc.  )                     This is the least
> interesting one imho.  
> 
> There is no limitation for legacy resources .. and it doesn’t affect their
> legacy status .. under this policy.  
> 

The current Transfer Policy does not include the publishing of legacy updates within the RIPE NCC service region.

The RIPE Policy, "RIPE NCC Services to Legacy Internet Resource Holders", clearly states that "Any existing or future RIPE policy referring to resources shall not apply to legacy resources unless the policy explicitly includes legacy resources in its scope."
https://www.ripe.net/publications/docs/ripe-639#1-2-scope

Legacy resources are mentioned in the scope of the Transfer Policies for inter-RIR transfers, but not for updates within our service region or transfer statistics.

Of course, another difficulty is that the RIPE NCC is not involved in many of these legacy updates. Therefore, we would not be able to distinguish whether a legacy update relates to a resource transfer, a merger, or a company name change in any statistics that we published.

We hope this is helpful.

Kind regards,
Marco Schmidt
Policy Development Officer
RIPE NCC

Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum