RE: Routing wars pending?
- Date: Wed, 15 Nov 95 14:11:41 IST
On Wed, 15 Nov 1995 11:00:04 MET you said:
> With regard to the rest of your message - here is what we do, both as a
> Service Provider Registry and a as backbone provider which has to deal
> with routing:
>
> We strictly refuse requests to assign address space for further
> sub-assignement. Adresses are *directly* assigned to the eventual user.
> If a service provider wants to act as a Local-IR, then the proper way
> of doing it is to get in touch with the RIPE-NCC and establish a
> registry of it's own.
Is that the general consensus in other countries?
>
> Just to make sure that everybody understands the rules, we explicitely
> point out that the assignement is only valid for the purpose of
> connecting (directly or through an intermediate step) to our backbone.
> We explicitely reserve the right to reclaim the address space if these
> conditions are not (or no longer) met. I know that RLR are slightly
> different, of course.
We have had problems with this also.
>
> With regard to routing, the answer is both collaboration by all
> service providers (which is working rather well, I think) *and*
> filtering based on the route objects in the RIPE database (which
> appears to gain popularity). If somebody tries to play games, and most
> of the backbones would have filters, then there is a good chance that
> the hickup is confined to a small part of the Internet - which
> eventually makes the "highjacked" addresses more or less useless.
Yes Europe is very organized - but what do you do about the USA?
>
> And the multiple database issue should be sorted out anyway, because
> the problem of inconsistency *is* there, even without malicious intent
> on any side.
>
> Wilfried.
> --------------------------------------------------------------------------
> Wilfried Woeber : e-mail: Woeber@localhost
> Computer Center - ACOnet :
> Vienna University : Tel: +43 1 4065822 355
> Universitaetsstrasse 7 : Fax: +43 1 4065822 170
> A-1010 Vienna, Austria, Europe : NIC: WW144
> --------------------------------------------------------------------------
Hank
|