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] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
- Previous message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
- Next message (by thread): [address-policy-wg] IXP assignments and transfers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrea Cima
andrea at ripe.net
Thu Sep 3 15:17:47 CEST 2015
Hi Nick, On 02/09/2015 16:27, Nick Hilliard wrote: > On 02/09/2015 14:55, Sascha Luck [ml] wrote: >> Does IXP space come out of a separate pool from any other ipv4? > from what I understand, it comes out of a dedicated /16. RIPE NCC will be > able to confirm whether this is a contiguous /16 or not. 185.1.0.0/16 is the /16 reserved for IXP assignments. However, according to the RIPE-649: "/IP space returned by IXPs will be added to the reserved pool maintained for IXP use/" [1]. This means that we will also make new IXP assignments from an IP block different than 185.1.0.0/16, when re-using the "IP space returned by IXPs". [1] https://www.ripe.net/publications/docs/ripe-649#61 I hope this clarifies Andrea Cima RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20150903/6d052beb/attachment.html>
- Previous message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
- Next message (by thread): [address-policy-wg] IXP assignments and transfers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]