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] Changing the Status of PI Address Space
- Previous message (by thread): [address-policy-wg] New AS Number Blocks allocated to the RIPE NCC
- Next message (by thread): [address-policy-wg] Changing the Status of PI Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Elvis Daniel Velea
elvis at v4escrow.net
Tue Mar 4 01:25:35 CET 2014
Hi everyone, I'd like to restart the discussion that was taking place on the mailing list before the RIPE Meeting in Athens. The discussion happened on the mailing list and in Athens and moved to a discussion on whether we should permit PI transfers through policy -> I understand that Erik Bais is working on a policy proposal that would include PI transfers. However, the discussion on ASSIGNED PI to ALLOCATED PA status change for address space given and used by the LIR has been stopped and I would like to restart it. My opinion is that I don't think a policy is needed for these changes to be performed by the RIPE NCC at the request of the LIR. Changes from ALLOCATED PI to ALLOCATED PA have been done in the past; plus - Tore has also pointed out some precedent where ASSIGNED PIs have been changed to ALLOCATED PAs. By keeping the artificial limit of PI used by LIRs the registry is suffering as any assignments made within that PI block are not properly recorded in the registry/RIPE Database. By looking back at the feedback received from lots of people in the community (and I counted at least 20 people responding to Andrea's e-mail) I have the feeling that this should have been already implemented. Therefore, I'm curious: - should we restart the discussion? - was the minimum limit of the prefix size the only reason why it hasn't yet been implemented? (some were saying any prefix, some were saying min /22) - or was it already implemented and I missed the announcement? Kind regards, Elvis -- <http://v4escrow.net> Elvis Daniel Velea Chief Business Analyst Email: elvis at V4Escrow.net <mailto:elvis at v4escrow.net> US Phone: +1 (702) 475 5914 EU Phone: +3 (161) 458 1914 Recognised IPv4 Broker/Facilitator in: This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received this email in error, please notify the sender immediately and delete the original.Any other use of this email is strictly prohibited. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20140304/334ed077/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: logo.png Type: image/png Size: 5043 bytes Desc: not available URL: </ripe/mail/archives/address-policy-wg/attachments/20140304/334ed077/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: 1.png Type: image/png Size: 11971 bytes Desc: not available URL: </ripe/mail/archives/address-policy-wg/attachments/20140304/334ed077/attachment-0001.png>
- Previous message (by thread): [address-policy-wg] New AS Number Blocks allocated to the RIPE NCC
- Next message (by thread): [address-policy-wg] Changing the Status of PI Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]