FW: LIR Registration

I sent the mail below to ncc at ripe.net and didnt get an answer up to 
now,
so I'm wondering if anyone in this list may help or could give us some
notes.

tia
>>>>>>>>>>>>>>>>>>>>>>>>


Dear Ladies and Gentlemen,

we plan to become LIR in the very near future and have some questions
concerning registration and status issues.

Currently we deploy VPN-connections over WANs and the internet for
customers, including centralized internet-gateway and hosting 
services.

As we grow, the needs of our customers grow exponentially, forcing us
to provide redundant internet-access at our internet-gateway and 
hosting
location here in Berlin.
For this need, we plan to connect to (in the first step) two upstream
providers and get an fully internet-routable addressblock.

As you state in Ripe-Document 142 the use of PI-address-space in an AS
would be suitable for this, but as you say in the same document you
do not guarentee the ability to route this address-space in the whole
internet. But exactly this guarantee is what we need to provide our 
customers
the service-level-agreements they expect.

So we can't only use this PI-address-space but instead become LIR and 
get
our own allocated address space in an order of magnitude that is
routed in the internet.

Our question is now, what is the real difference between enterprise 
LIR
and small provider LIR? We do not plan to assign customers 
address-space
besides RFC1819 nets for LAN-2-LAN connections through VPNs but only
assign addresses for hosting, housing and VPN-Connections through the
internet.

The second question is, if we would get *at all* an addressblock
/19 if we cant show up a plan that we will use an certain amount of 
this
address in e.g. 48 months which will be true in our current 
considerations.



Sincerely,


Christian Tramnitz