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/address-policy-wg@ripe.net/
[address-policy-wg] [Ticket#2013100901002562] New Policy Proposal (PI - PA Transfer)
- Previous message (by thread): [address-policy-wg] 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 ]
LeaderTelecom Ltd.
info at leadertelecom.ru
Wed Oct 9 09:24:47 CEST 2013
Dear Adrian,
I think this subject was covered on this list earlier this year in the thread
named; “Guidance Requested: Changing the Status of PI Address Space”. I’m just
not sure what the status is right now?
I not sure too about status, but ready to work in working group if it already
exist.
Could someone update about current status?
--
Alexey Ivanov
09.10.2013 11:19 - Adrian Hardy написал(а):
Hi all,
I think this subject was covered on this list earlier this year in the thread
named; “Guidance Requested: Changing the Status of PI Address Space”. I’m just
not sure what the status is right now? Do we really need to restart the
discussion?
Regards,
Adrian
e-Quest | Adrian Hardy
Technical Consultant
T: +31 492 392626 | Support: +31 492 780780
Schootense Dreef 26 | 5708 HZ | Helmond
KVK:17121883 | BTW:8009998348B01 | [1]http://www.e-quest.nl
Van: address-policy-wg-bounces at ripe.net
[mailto:address-policy-wg-bounces at ripe.net] Namens ksyu at netassist.ua
Verzonden: woensdag 9 oktober 2013 01:35
Aan: address-policy-wg at ripe.net
Onderwerp: [address-policy-wg] New Policy Proposal (PI - PA Transfer)
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
[1] http://www.e-quest.nl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20131009/9b4d61b9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image113dcb.PNG
Type: image/png
Size: 34020 bytes
Desc: not available
URL: </ripe/mail/archives/address-policy-wg/attachments/20131009/9b4d61b9/attachment.png>
- Previous message (by thread): [address-policy-wg] 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 ]