This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Abuse-C/IRT
- Previous message (by thread): [db-wg] Abuse-C/IRT
- Next message (by thread): [db-wg] Abuse-C/IRT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Tue May 11 09:52:43 CEST 2004
Hi, On Mon, May 10, 2004 at 02:45:58PM -0400, der Mouse wrote: > >> I do not consider it acceptable for a jurisdiction to allow entities > >> in it to evade the responsibility I believe they have to be > >> accountable for public resource fragments assigned to them. > > The LIR holding the address space *is* visible. > > What good does that do? None of the LIRs do anything of use about > broken contact information as far as I can see; the most I've seen > anyone do is ARIN putting in a little note about "we know this contact > information is broken, but we're going to let this address space go on > being used by someone not even we can contact anyway". (I'm > paraphrasing rather loosely, of course.) Now you seem to confuse LIR and RIR? ARIN is a RIR, and the ISPs holding the address space would be the LIR. I agree that a LIR's contact data should always be up-to-date, and actually enabling people to contact "someone" who can "make things stop". Unfortunately, not even *this* is currently in place - and IMHO that's a much worse problem than "having end-user data in there or not". > > So if one of their customers is doing bad things, you know whom to > > talk to - and if necessary, sends the feds to. > > Actually, no, because the jurisdiction the LIR is in is not necessarily > that of the end user. For example, I, in Canada, have address space > whose LIR is ARIN, in the US. ARIN is the RIR (regional internet registry). The LIR (local internet registry) would be your local ISP. There are also direct RIR->end user address blocks. In those case, it's of course the RIRs job to make sure that the end user data is there - but this is not what's being talked about, as there are no such blocks in IPv6. > Or is this for values of "LIR" that include all entities who reassign > their allocated address space? This is the definition of LIR (at least over here, and since this is a RIPE list, I stick to the RIPE definitions). > > If the LIR is "careless" - well, in that case mandatory end-user > > registrations aren't going to be very useful either. > > Ultimately - if the IANA actually bothered to enforce them - they would > get a sloppy LIR decommissioned, or at least its own assignemnts > revoked, which amounts ot the same thing in practice. (Of course, this Mixing RIR and LIR again. But effectively, I agree, if you go down one level (RIPE -> ISP registry). Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 60210 (58081) SpaceNet AG Mail: netmaster at Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
- Previous message (by thread): [db-wg] Abuse-C/IRT
- Next message (by thread): [db-wg] Abuse-C/IRT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]