AW: [db-wg] Adding route objects

Hi!

> > Why there is *-ISP-MNT in your PI, not your one?
> we are the new ISP and our MNT is in the inetnum!

But why not only client's one?

> Beside that, if you have ONE Upstream and get a second one the first needs
> to place a mnt-routes in his route object

Why?


> . If the customer later wants 
> a third upstream, he needs the first TWO to install a mnt-routes.

If the customer wants a third upstream (not just moving from first to second) 
- he need own autonomous system at first. It also solves this problem ;)

I have customers with own PI and my ASN.
First, there WILL be service interruption when such customer moves from one 
ISP to another. Second, correct workflow is:

1. Customer with own PI have OWN mnter, and ONLY it is present in his inetnum: 
object.
2. This mntner have PGP authorization (by the way, it is a must nowdays).
3. Customer makes a route object:

route:        192.168.231.0/24
descr:        Customer route
origin:       AS_FROM_UPSTREAM
mnt-by:       CUSTOMER-MNT
source:       RIPE # Filtered

then signs it with his PGP key and send it to UPSTREAM. Upstream signs it with 
his key (or add passwd: field if he is too lame to make PGP key ;) ) and send 
it to auto-dbm at ripe.net.

Customer id free to change his route, because of there is customer's mntner.

If there is TWO route objects with same net and different AS (and if there is 
two announces from two points with different AS) - it just will not work. 

-- 
WBR,
Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)