Now, there's of course a catch - the PDP takes a while to run through (a couple of months at best, some times much longer), and you need *consensus* for a proposed policy change to become policy - so you need to convince the RIPE community that it's of common interest to change this.
Thank you for the information about PDP. I guess the process will take much longer than we expected. Is it probable that an agreement could be reached regarding an assignment of a block of IP-addresses from the yet unallocated ranges? Has this question ever been raised before? For example, we’d like to get address 2.2.2.2 – but if a similar *easy to rmemeber address* is available from a allocatable space, we’ll be satisfied with that too. Should we send a request for a policy change or is it most likely not going to help reach a consensus?
Since we're running out of addresses quickly, even if you succeed in changing the policy, the subnet containing 2.2.2.2 might already be handed out to someone else. So I wouldn't bet the success of my company on the chance of receiving 2.2.2.2 - you might succeed, but you might as well not.
Ok, I see. Is it technically possible to get address 2.2.2.2 when this range 2.*.*.* becomes publicly available for assignment? -- Kind regards, Sergey Gotsulyak Ideco Sales Team 280 Madison Ave, Suite 912 New York, NY 10016 Phone: (800) 715-3502 Email: goz@idecogateway.com Web: www.idecogateway.com