Re: [anti-spam-wg@localhost] Contacts

[Martin Neitzel <]

[Disclaimer:  all this here is not related to spam.  I only list
what the RIPE can/should do in the case of misbehaving ISPs as
last resort, where "misbehaving" means: "not keeping contact
info current", not "having customers violating someone else's APU".]

Chris Jones wrote:
>
> In regard to the lowering of assignment window(s), I do not understand what
> that means.

Most people become LIR because they are ISPs and need to assign address
space to their customers.  As long as you can assign addresses without
external approval, you can do this as quickly as possible.  Re-imposed low
(zilch) assignment windows translates into slowing down your ISP business,
most prominently getting new customers connected much slower than usually.

A strong case against the currently quick service we all get from the
NCC these days, by the way.  Back in 1995/6, when ISPs where Real ISPs
and today's ISPs where mere PoPs and when wait queues were looooong
(weeks), a small window meant a truly major pain.


> My feeling is though, that a suspension of registration (meaning
> the inability of LIR/ISP customers to access the net) is the least penalty
> that RIR's should be given the authority to implement.

"Suspension of the LIR's registration services" doesn't go that far.
It translates into ``no new ISP customers for the LIR'', which is
something  I could tolerate if the complaint is "the LIR itself has
broken contact info".

"Cutting off the LIR/ISP and its customers from the net" is neither the
result of taking away further reservation services; nor would it be
appropriate.  All parties need this net access to fix the problem,
that is:  get the contact info up-to-date.  Most importantly:

An ISP should not be revoked net access because of an customer's error,
and vice versa.

Every LIR binds itself to procedures documented in 
http://www.ripe.net/ripe/docs/new-lir.html
which contains
	2.1. Responsibilities of a Local Internet Registry

and leads to possible sanctions in
From http://www.ripe.net/ripe/docs/ipv4-policies.html :

5.4.5 Closure of an LIR by the RIPE NCC

 The RIPE NCC may decide to close an LIR for any of the following reasons:

     * the LIR stops paying its bills to the RIPE NCC
     * the LIR cannot be contacted by the RIPE NCC for a significant
       period of time
     * If an LIR consistently violates the policies applicable in the RIPE NCC
       service region.

 In the event of an LIR closure, the RIPE NCC will take responsibility
 for all address space held by the LIR.

"Taking over responsiblity" does not mean terminating the associated
end-user assignments and deleting the route objects right away.  To the
contrary, it may give end-users a graceful chance to renumber to a new
ISP when the old one went belly-up.

								Martin

PS:  If the original question was from the der Mouse as in
     neitzel!infbs!unido!mcvax!talcott!mcgill-vision!garfield!mouse,
     it's no wonder that Piet chimed in.  Good to see you still alive and
     kicking!