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#2013100901000742] 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 ]
Tomasz Śląski GMAIL
tomasz.slaski at gmail.com
Wed Oct 9 08:22:55 CEST 2013
W dniu 2013-10-09 01:34, ksyu at netassist.ua pisze: > 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 Full support to convert PI to PA. Many people use PI breaking policy, because they have no other way. Conversion PI to PA solves many problems. Regards Tomasz
- Previous message (by thread): [address-policy-wg] [Ticket#2013100901000742] 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 ]