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

Hi Elvis,  

 

I've read the proposal and I’m not sure I see what you are trying to solve
here ...  besides the obvious …  

 

Because if you look at the following URL:  

 

https://www.ripe.net/manage-ips-and-asns/resource-transfers-and-mergers/tran
sfers/inter-rir-transfers/inter-rir-ipv4-transfer-statistics 

 

There is a specific section for Inter-RIR transfers .. with a to RIPE and
>From RIPE tab..  

 

And in the To tab, you will see the following (as an example.. )  

 

157.97.0.0/16                   ARIN      A&F Networks B.V.
17/03/2016

147.28.0.0/16                   ARIN      RGnet, LLC
16/03/2016

192.83.230.0/24               ARIN      RGnet, LLC
16/03/2016

198.133.206.0/24             ARIN      RGnet, LLC
16/03/2016

 

And these are all Legacy Prefixes inter-rir transfers done .. and
published.. 

 

So if the RIPE NCC is already registering the prefixes as part of the Inter
RIR transfers .. even before they are marked as a Legacy prefix.. in the
RIPE DB ..  

How will this policy make a difference ?  

 

And the change in the transfer document that the RIPE NCC is currently still
implementing ..  it clearly states the following :  

 

https://www.ripe.net/publications/docs/ripe-682#4-0-transfer-statistics

 

*        4.0 Transfer Statistics

 

*        The RIPE NCC will publish a list of all transfers. This publication
shall occur on a monthly basis or more frequently if the RIPE NCC so
chooses.

*        This list will contain information about approved changes. The
following information will be published:

*        The name of the offering party

*        The resource originally held by the offering party

*        The name(s) of the receiving party or parties

*        Each subdivided prefix (each partial block derived from that
original block) or resource received

*        The date each resource was transferred

*        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)

 

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.  

 

There is a difference between the RIPE DB and the RIPE registry.. if you
want to update the DB, the LRH can do that themselves.. 

But if the LRH wants to update the registry (the RIPE NCC internal system),
they should provide the proper documentation.  And that is already in place
in procedures..  

 

So the actual change that you are asking is :  

 

In the Services to Legacy Resource Holder policy
(https://www.ripe.net/publications/docs/ripe-639)  .. 

 

Have Legacy Holders to agree to sign a document, that the RIPE NCC already
has in the operational procedure.  

 

In which case the name of the policy is incorrect .. as it isn’t about
Inter-RIR legacy updates .. or transfers .. but about the Services to LRH’s
.. 

 

Perhaps we should see first what the RIPE NCC will implement with the
2015-04 … before we go look into additional policy … 

 

Regards,

Erik Bais 

A2B Internet 

 

-----Oorspronkelijk bericht-----
Van: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Namens
Marco Schmidt
Verzonden: dinsdag 25 april 2017 14:40
Aan: address-policy-wg at ripe.net
Onderwerp: [address-policy-wg] 2017-01 New Policy Proposal (Publish
statistics on Intra-RIR Legacy updates)

 

Dear colleagues,

 

A new RIPE Policy proposal, 2017-01, "Publish statistics on Intra-RIR Legacy
updates" is now available for discussion.

 

The goal of this proposal is to require the RIPE NCC to publish all changes
to the holdership of legacy resources in the existing transfer statistics.

 

You can find the full proposal at:

 <https://www.ripe.net/participate/policies/proposals/2017-01>
https://www.ripe.net/participate/policies/proposals/2017-01

 

As per the RIPE Policy Development Process (PDP), the purpose of this four
week Discussion Phase is to discuss the proposal and provide feedback to the
proposer.

 

At the end of the Discussion Phase, the proposer, with the agreement of the
WG Chairs, will decide how to proceed with the proposal.

 

We encourage you to review this proposal and send your comments to <
<mailto:address-policy-wg at ripe.net> address-policy-wg at ripe.net> before 24
May 2017.

 

Regards,

 

Marco Schmidt

Policy Development Officer

RIPE NCC 

 

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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20170502/9ff66ed8/attachment.html>