This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] New Policy Proposal (PI - PA Transfer)
- Previous message (by thread): [address-policy-wg] [Ticket#2013100901002562] New Policy Proposal (PI - PA Transfer)
- Next message (by thread): [address-policy-wg] New Policy Proposal (PI - PA Transfer)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrea Cima
andrea at ripe.net
Thu Oct 10 12:57:35 CEST 2013
Dear colleagues, Following the increasing number of requests from LIRs that want to convert their PI assignments into PA allocations, we proposed the following options at RIPE 66: 1) Allow LIRs to change the status of their PI assignments into PA allocations (if equal or larger than the minimum allocation size) 2) Do not allow LIRs to change the status of their PI assignments into PA allocations After RIPE 66, the discussion was continued on the Address Policy Working Group Mailing List. There seemed to be a lot of support for allowing LIRs to change the status of their resources, but people also wanted the minimum allocation size to be disregarded. This would allow for PA allocations smaller than the minimum allocation size. It is our understanding that this last point would require a policy change. We will be addressing this as part of our "Feedback From RIPE NCC Registration Services" presentation at RIPE 67. Based on the feedback we receive from here, we will work with the Working Group Chairs on a way forward. Kind regards, Andrea Cima RIPE NCC On 10/9/13 1:34 AM, ksyu at netassist.ua wrote: > Hello everybody > > I would like to draw attention of the public to the next moment . > According to the RIPE policy, a PI network should be used only as it > was assigned. However, the time comes, the amount of clients > increases, the number of services is growing up, and v4 addresses are > not assigned any more. > What should provider do in this case? The network was assigned for the > particular service and can't be used for other services? Just returned > back . But no one in their right mind will do this ) . > It may be a topical solution for this situation - to return the > opportunity to transfer PI blocks into the PA? > This will give the opportunity to breathe more freely, not to violate > the rules of RIPE policy . > I suggest to discuse the question of transference of PI blocks to PA, > and invite all caring to speak on the matter. > > > Best regards, Kseniya Sokol -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20131010/2250badf/attachment.html>
- Previous message (by thread): [address-policy-wg] [Ticket#2013100901002562] New Policy Proposal (PI - PA Transfer)
- Next message (by thread): [address-policy-wg] New Policy Proposal (PI - PA Transfer)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]