[address-policy-wg] Re: [ncc-announce] 2007-01 Implementation: Direct Internet Resource Assignments to End Users from the RIPE NCC

Dear Ahmed,

Thank you for your email. The points that you have raised are not the 
result of this policy change, but are already part of the current policy.

Ahmed Abdulraheem wrote:
> Hello,
> I am still not understanding about some terms in the Policy requirements
> such as:
>
> - End User must specify and establish need for a Provider Independent (PI)
> assignment.
>
>   

All users must justify their need for the Internet number resources they 
request. The RIPE NCC's evaluation of this need is based on the RIPE 
policy document related to the specific kind of number resource in 
question. Please find the Address Policy and Address Management related 
documents online at:
http://www.ripe.net/ripe/docs/index.html

> - End User must provide up-to-date registration information to the LIR;
> some or all data will be published in the RIPE Database.
>
>   

Contact information for all assignments and allocations is published in 
the RIPE Database. The LIR gathers this information from the end-user 
and enters it into the request form and/or the RIPE Database.

> - End User may not sub-assign resources to third parties.
>
>   

An assignment is considered to be the final step in the 
allocation/assignment chain. If an organisation wants to make 
assignments to its customers, that organisation must obtain a (sub-) 
allocation. There can be no assignments registered within other 
assignments, they can only be registered within allocations. Please see 
further details about this at:
http://www.ripe.net/ripe/docs/ripe-441.html

If you have any further questions, please contact me.

Kind regards,

Andrea Cima
RIPE NCC


> I need more explanation about this
>
> Regards,
>
>
> Eng.Ahmad Abdul Rahim
> System Administrator
> S.A Department
> Tel.+965-808888-380
> Qualitynet Co.
>
> -----ncc-announce-admin at ripe.net wrote: -----
>
> To: address-policy-wg at ripe.net, ncc-services-wg at ripe.net,
> ncc-announce at ripe.net
> From: Andrea Cima <andrea at ripe.net>
> Sent by: ncc-announce-admin at ripe.net
> Date: 02/12/2009 07:07PM
> Subject: [ncc-announce] 2007-01 Implementation: Direct Internet Resource
> Assignments to End Users from the RIPE NCC
>
> [Apologies for duplicate emails]
>
> Dear Colleagues,
>
> We are pleased to announce that phase one of policy proposal 2007-01,
> "Direct Internet Resource Assignments to End Users from the RIPE NCC",
> will be implemented on 3 March 2009.
>
> This change will require that an End User have a contractual
> relationship with a sponsoring LIR or the RIPE NCC before the End User
> can receive Internet number resources (Autonomous System (AS) Number,
> Provider Independent (PI) IPv4 and IPv6, Internet Exchange Point (IXP)
> and anycasting assignments) directly from the RIPE NCC.
>
> The full text of policy proposal 2007-01 can be found at:
> http://www.ripe.net/ripe/policies/proposals/2007-01.html
>
> Phase one addresses the implementation of the new policy in relation to
> all new requests for independent numbering resource assignments.
>
> Please note that from 3 March 2009, End Users requesting independent
> numbering resources must sign a contract with a sponsoring LIR or with
> the RIPE NCC in order to receive those resources. Requests for
> independent numbering resources that do not demonstrate such a contract
> will not be processed by the RIPE NCC.
>
> Information on the required content of contracts between End Users and
> sponsoring LIRs is available at:
> http://www.ripe.net/membership/lir-end-user-requirements.html
>
> Phase two of policy proposal 2007-01 will address the contractual
> relationship between End Users who hold previously assigned independent
> numbering resources and the RIPE NCC or a sponsoring LIR. A plan for
> implementation of this phase will be presented at the next meeting of
> the RIPE NCC Services Working Group, which will take place at the RIPE
> 58 Meeting in Amsterdam from 4-8 May 2009.
>
> Kind regards,
>
> Andrea Cima
> RIPE NCC
>
>
>
>
>