[ncc-services-wg] 2012-07's direct engagement option

On Tue, Apr 22, 2014 at 04:09:45PM +0200, Janos Zsako wrote:


>The RIPE NCC may not de-register the legacy resources unless asked to do
>so by the resource holder. Moreover, if the contract (with the member,
>the sponsoring LIR or DAU) is terminated, the resource is simply flagged
>"No contract".

AIUI, if a resource holder extends the SSA to cover legacy resources,
there is a risk that if the NCC is unhappy with the LIR wrt *these*
resources, the LIR could be sanctioned and lose their *other* resources.
That is pretty effective control in my understanding.
This logic also now makes it clear why Option 2.4 is needed, an existing
LIR may mitigate this risk by having their legacy resources covered by a
separate, more individual, contract.
Interesting in this context is also the statement that under option 2.3,

"the RIPE NCC will not allow the Legacy Resource Holder to become the
sponsoring LIR for its own Legacy Internet Resources."


rgds,
Sascha Luck

PS: I hold no legacy resources so I don't really have a pig in this
race.