Re: [address-policy-wg] Idea for aggregating IP addresses

2016-09-22 Thread Arash Naderpour
Soon or late it will end up here to “IPv4 is DEAD, go and develop IPv6”, that’s a regular answer here when you bring up something related to IPv4 J Your idea looks like a disk defragmentation procedure, but first you need to check how many percent it is defragmented and how much free

Re: [address-policy-wg] Idea for aggregating IP addresses

2016-09-22 Thread Peter Hessler
Hi Clarification question. Are you requesting that non-continuous IPv4 blocks be exchanged for the equivalent size in a single continuous IPv4 block that does not match the previously issued IPv4 addresses, or do you want to take continuous IPv4 blocks and combine them? On 2016 Sep 22 (Thu) at

Re: [address-policy-wg] Idea for aggregating IP addresses

2016-09-22 Thread Garry Glendown
Guten Tag, > Hello, > > One of the goals of RIPE is to aggregate IP addresses. I'd like to > suggest the ability for a LIR and End User to exchange number of > blocks of IP ranges for a greater block. > > For example: > LIR/End User has 4 different /22 subnets and LIR/End User can exchange > these

[address-policy-wg] Idea for aggregating IP addresses

2016-09-22 Thread Ping IP
Hello, One of the goals of RIPE is to aggregate IP addresses. I'd like to suggest the ability for a LIR and End User to exchange number of blocks of IP ranges for a greater block. For example: LIR/End User has 4 different /22 subnets and LIR/End User can exchange these subnets for 1 x /20

Re: [address-policy-wg] Idea for aggregating IP addresses

2016-09-22 Thread Mozafary Mohammad
Hello The suggestion help IP broker to made bigger IP block and earn more money. bigger IP block is more expensive than smaller one. :) Also why RIPE NCC should return "Spam dirty" IP range and assign new one to a user? Thanks On 9/22/2016 4:07 PM, Ping IP wrote: Hello, One of the