[ncc-services-wg] Proposed Implementation Plan for 2012-08, "Publication of Sponsoring LIR for Independent Number Resources"

Dear Wilfried,

If a resource is transferred from a sponsoring LIR to the infrastructure of an LIR the attribute will be removed. This was not clear in the proposal and I’ve now adjusted the text, I’ve removed “.. or to the infrastructure of an LIR” and added separately:

“If a resource is transferred from a sponsoring LIR to the infrastructure of an LIR the attribute will be removed. The attribute will also be removed if an LIR cancels the contract, until a new contract is in place.”

Thanks for pointing this out!

Kind regards,

Johan Åhlén
RIPE NCC
Asst. Manager Database

On 31 Jan 2014, at 18:45, Wilfried Woeber <Woeber at CC.UniVie.ac.at> wrote:

> Hi
> Johan and Team!
> 
> Johan Åhlén wrote:
>> Dear colleagues,
>> 
>> Last week, the RIPE community reached consensus on the policy proposal 2012-08, "Publication of Sponsoring LIR for Independent Number Resources”. The RIPE NCC’s proposed implementation plan of the policy can be found here:
>> https://labs.ripe.net/Members/johan_ahlen/policy-2012-08-proposed-plan-for-implementation
> 
> I think the proposal for implementation as outlined is sound (wearing
> my hat as the manager of an LIR which sponsors some resources for our
> community).
> 
> There's one (minor) loose end maybe, where I don't easily understand the
> background or goal for a First Track item:
> 
> <quote>
> ° A resource is transferred from one sponsoring LIR to another,
>  or to the infrastructure of an LIR
> </quote>
> 
> The transfer case is obvious, but I'm not sure that a resource needs a
> "sponsored-by" label pointing to self? IIRC we already do have assignements
> of resources for an LIR's/ISPs infratructure. So wouldn't we create two
> different flavours of "infrastructure"?
> 
> I may easily miss something, though :-)
> Regards,
> Wilfried
> 
>> You can find the full policy proposal at:
>> https://www.ripe.net/ripe/policies/proposals/2012-08
>> 
>> The corresponding RIPE Document is ripe-603, which is available at:
>> https://www.ripe.net/ripe/docs/ripe-603
>> 
>> If you have any comments or concerns, please let us know. 
>> 
>> Note: this email has been sent to both the RIPE NCC Services WG and the RIPE Database WG mailing lists. We would like to ask you to keep the discussion on the RIPE NCC Services WG mailing list to better facilitate participation. 
>> 
>> Kind regards,
>> 
>> Johan Åhlén
>> Assistant Manager Database
>> RIPE NCC
> 
>