I oppose this policy.

I just acquired a new downstreamer customer that asked me to provide ip transit and space while he is investing in infrastructure.
Once he will be ready he will setup its own LIR and get his /22 (if in time to..)
He is moving to me from another provider 'cause the old provider said him he will never sell the assigned space to him.
I said I will never sell him the space too, but I can sub-allocate part of my space now and so he can use it to grow his network ipv4/ipv6.
I said him that when he will be ready with his own LIR i can give him the space he is annoucing/using if he simply is able to give me back same amount of space once obtained/bought it in the future. That is the agreement and the whole setup is already described in RIPE database and we are just waiting to get connected to start IP transit.

Am I doing something wrong? 2016-03 wants to forbid this perfect legitimate business?
Plase explain why I should go to my customer tomorrow and say that what we are doing will not be possibile?
You know what? I'll lose the contract. My LIR will be unappetible to him even if only reading today the apwg.
So I should let him go to another LIR maybe.

Please I want to underline what this customer is paying to his old provider and tomorrow to me is only the transit.
The old provider is providing him the space for free and I am doing the same with only more the agreement to give him the space once he will have an LIR.

I don't want to be divantaged so I oppose this policy.

kind regards
Riccardo

Il 19/10/2016 10:05, Marco Schmidt ha scritto:

Dear colleagues,

The draft documents for version 3.0 of the policy proposal 2016-03, "Locking Down the Final /8 Policy" have now been published, along with an impact analysis conducted by the RIPE NCC.

The goal of this proposal is to ban transfers of allocations made under the final /8 policy. Also the proposal specifies what resources must be added to the RIPE NCC IPv4 available pool.

Some of the differences from version 2.0 include:

-    Clarification that changes to holdership of address space as a result of company mergers or acquisitions are not affected by proposed transfer restriction
-    Legacy space handed over to the RIPE NCC will be added to the IPv4 available pool

You can find the full proposal and the impact analysis at:
https://www.ripe.net/participate/policies/proposals/2016-03

And the draft documents at:
https://www.ripe.net/participate/policies/proposals/2016-03/draft

We want to draw your attention to two changes, which we hope it will make your proposal evaluation easier.

-    Policy proposals now contain a diff tool that allows easy comparison of different proposal versions – simply click on the “View Changes” symbol right beside the list of proposal versions.
-    The RIPE NCC impact analysis only mentions areas where  the proposal is actually expected to have an impact. For example, if the analysis makes no comment about financial or legal impact, it means that no such impact is expected.

We encourage you to read the draft document and send any comments to <address-policy-wg@ripe.net> before 17 November 2016.

Regards,

Marco Schmidt
Policy Development Officer
RIPE NCC

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

Ing. Riccardo Gori
e-mail: rgori@wirem.net
Mobile:  +39 339 8925947
Mobile:  +34 602 009 437
Profile: https://it.linkedin.com/in/riccardo-gori-74201943

WIREM Fiber Revolution
Net-IT s.r.l.
Via Cesare Montanari, 2
47521 Cesena (FC)
Tel +39 0547 1955485
Fax +39 0547 1950285

--------------------------------------------------------------------
	CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons 
above and may contain confidential information. If you have received 
the message in error, be informed that any use of the content hereof 
is prohibited. Please return it immediately to the sender and delete 
the message. Should you have any questions, please contact us by re-
plying to info@wirem.net
        Thank you
WIREM - Net-IT s.r.l.Via Cesare Montanari, 2 - 47521 Cesena (FC)
--------------------------------------------------------------------