[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] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Bais
ebais at a2b-internet.com
Thu Sep 3 14:58:54 CEST 2015
>From what I see, it looks like it is in the following range .. cat delegated-ripencc-extended-latest | grep '|185.1.' | grep '|256|' resulting in the following info : http://pastebin.com/3SHQsKxi Missing 'only' the following result : ripencc|PL|ipv4|185.1.10.0|512|20130403|assigned ripencc||ipv4|185.1.39.0|256||reserved It would be my wild guess that we are talking about the 185.1.x.y range :) Erik Bais -----Oorspronkelijk bericht----- Van: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Namens Nick Hilliard Verzonden: woensdag 2 september 2015 16:27 Aan: Sascha Luck [ml] <apwg at c4inet.net> CC: address-policy-wg at ripe.net Onderwerp: Re: [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies) 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. Nick
- Previous message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
- Next message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]