AW: [db-wg] Adding route objects

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


>
> > inetnum:        192.168.230.0 - 192.168.231.255
> > netname:        DUMMY-NET
> > descr:          Customer GmbH
> > country:        DE
> > org:            ORG-AAAAA-RIPE
> > admin-c:        AA1
> > tech-c:         AA1
> > status:         ASSIGNED PI
> > mnt-by:         RIPE-NCC-HM-PI-MNT
> > mnt-by:         CUSTOMER-MNT       <- customer (owner of net)
> > mnt-by:         NEW-ISP-MNT        <- we
> > mnt-lower:      RIPE-NCC-HM-PI-MNT
> > mnt-routes:     OLD-ISP1-MNT       <- OLD ISP1
> > mnt-routes:     OLD-ISP2-MNT       <- OLD ISP2
> > mnt-routes:     NEW-ISP-MNT        <- we
> > mnt-domains:    OLD-ISP1-MNT
> > mnt-domains:    OLD-ISP2-MNT
> > mnt-domains:    NEW-ISP-MNT
> > source:         RIPE # Filtered
>

Beside that, if you have ONE Upstream and get a second one the first needs
to place a mnt-routes in his route object. If the customer later wants
a third upstream, he needs the first TWO to install a mnt-routes.

A lot of large player in the market have no workflow for doing this. They
are
able to create a route object for themselves but not alter it so that
another
isp can create a route object for his as. "Able" means they are allowed by
they internal policy/workflow to send the right mail to the ripe db address.
They consider this as an exception from their normal policy how to handle
a customer:-)


The last action took around 6 weeks and lots of emails to explain what we /
the
customer needs. This is really a nightmare. It worked only because the
person
at the tier1 isp has altered his route-object while we phoned, we sent the
create route object to ripe and afterwards he deleted again the mnt-routes
so
nobody saw a change.

Winfried