Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <563bf7a2.7090...@yahoo.co.uk>, denis wrote: >Hi Ronald > >On 06/11/2015 00:48, Ronald F. Guilmette wrote: >> In message <20151105220739.gw47...@cilantro.c4inet.net>, >> "Sascha Luck [ml]" wrote: >>> Please, Ron, RTFM for *once* before throwing accusations about. >> >> It wasn't an

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <20151106003148.gx47...@cilantro.c4inet.net>, "Sascha Luck [ml]" wrote: >On Thu, Nov 05, 2015 at 03:48:43PM -0800, Ronald F. Guilmette wrote: >> >>Laugh now... while you can. > >Threats again, is it? I call on the chairs to point out to this >individual that n.a.n.a.e tactics are not

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <563bf492.2020...@yahoo.co.uk>, denis wrote: >On 06/11/2015 00:58, Ronald F. Guilmette wrote: >> In message <563bdb1c.4020...@yahoo.co.uk>, >> denis wrote: >>> This really does matter. Even with a valid RIPE ASN they cannot 'steal' >>> RIPE address space. >> >> Really??? >> >> If so

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <563bf1e0.3090...@yahoo.co.uk>, denis wrote: >First of all I apologise if I have mixed up some of your views, some of >Sacha's views and some of my own views. If I have I did so with good >intentions. I was not trying to derail anything, but I disagree that >this is a simple discu

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Sascha Luck [ml]
On Thu, Nov 05, 2015 at 11:41:32PM +0100, denis wrote: When it comes to getting an ASN the AUT-NUM does require reference to a PERSON/ROLE object. But you can pick any PERSON or ROLE object in the database and reference them. Technically there is no cross checking. The 'owner' of those objects

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread denis
Hi Ronald On 06/11/2015 00:48, Ronald F. Guilmette wrote: In message <20151105220739.gw47...@cilantro.c4inet.net>, "Sascha Luck [ml]" wrote: ... All the mntner object does is grant access to change a ripedb object. It says nothing about who operates a resource or what they are doing with

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread denis
Hi Ronald On 06/11/2015 00:58, Ronald F. Guilmette wrote: In message <563bdb1c.4020...@yahoo.co.uk>, denis wrote: On 05/11/2015 21:33, Ronald F. Guilmette wrote: In message <637758753.2826426.1446595528880.javamail.ya...@mail.yahoo.com>, ripede...@yahoo.co.uk wrote: With regards to this spe

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Suresh Ramasubramanian
That might not get as much traction but a cross registry one time cleanup of such route objects should be attempted to be coordinated, I guess? --srs > On 06-Nov-2015, at 1:36 AM, denis wrote: > > I agree a full implementation of cross registry auth with all 4 other RIRs > would be greatb

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Sascha Luck [ml]
On Thu, Nov 05, 2015 at 03:48:43PM -0800, Ronald F. Guilmette wrote: Laugh now... while you can. Threats again, is it? I call on the chairs to point out to this individual that n.a.n.a.e tactics are not welcome on this list. I also end my participation in this discussion here. Given that you

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Suresh Ramasubramanian
+1 here - though for step 3 it might be an idea to check just how many such objects are there and with what frequency they pop up. Some of these funny announcements can be short lived indeed - only lasting a few hours. --srs > On 06-Nov-2015, at 1:29 AM, Bengt Gördén wrote: > > I don't see a

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread denis
HI Ronald On 05/11/2015 23:44, Ronald F. Guilmette wrote: In message <563a6462.7080...@yahoo.co.uk>, denis wrote: You{r} talk about privacy and this whole thread is about making lots of personal data public and how many over engineered processes can be put in place to the detriment of all the

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <563bdb1c.4020...@yahoo.co.uk>, denis wrote: >On 05/11/2015 21:33, Ronald F. Guilmette wrote: >> In message <637758753.2826426.1446595528880.javamail.ya...@mail.yahoo.com>, >> ripede...@yahoo.co.uk wrote: >> >> With regards to this specific incident (and this specific set of what loo

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <20151105220739.gw47...@cilantro.c4inet.net>, "Sascha Luck [ml]" wrote: >On Thu, Nov 05, 2015 at 01:50:37PM -0800, Ronald F. Guilmette wrote: >>It has been well more than just one or two cases, and I suspect >>that you know that. Only one or two GLARING cases per month >>perhaps, bu

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <20151105214840.gu47...@cilantro.c4inet.net>, "Sascha Luck [ml]" wrote: >On Thu, Nov 05, 2015 at 01:31:31PM -0800, Ronald F. Guilmette wrote: >>>1) All resource holders are presumed to be bad actors and all of >>>their data must be kept in a database, their correctness to be >>>stric

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Aftab Siddiqui
Hi Elvis, > > I like the idea. I would have preffered a cross registry/RIR solution but > as you said, it has been many months (I actually raised the issue 2 RIPE > meetings ago - in London) but nothing visible has been done to fix this > problem. > > +1 from me. > I raised similar kind of issue

Re: [anti-abuse-wg] AS's with route objects for undelegated space

2015-11-05 Thread Ronald F. Guilmette
In message , Richard Clayton wrote: >I note the wish by some not to adopt a policing role, but it does seem >to me that this is civic hygiene... I await the inevitable... "We are not the civic hygienists!" :-) Regards, rfg P.S. Thanks for your report about those other ASNs. Facinating.

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Piotr Strzyzewski
On Thu, Nov 05, 2015 at 08:56:42PM +0100, Gert Doering wrote: Hi > On Thu, Nov 05, 2015 at 07:40:58PM +, ripede...@yahoo.co.uk wrote: > > STEP 4 > > > > This is a one off cleanup of existing ROUTE objects. For all ROUTE > > objects currently in the RIPE Database that relate to an out of > >

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <563a6462.7080...@yahoo.co.uk>, denis wrote: >You{r} talk about privacy and this whole thread is about making lots of >personal data public and how many over engineered processes can be put >in place to the detriment of all the good folk to trip up a few of the >bad folk. Excuse

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread denis
HI Ronald On 05/11/2015 21:33, Ronald F. Guilmette wrote: In message <637758753.2826426.1446595528880.javamail.ya...@mail.yahoo.com>, ripede...@yahoo.co.uk wrote: With regards to this specific incident (and this specific set of what looks to be 3 inter-related rogue ASNs) I myself don't really

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Sascha Luck [ml]
On Thu, Nov 05, 2015 at 01:50:37PM -0800, Ronald F. Guilmette wrote: It has been well more than just one or two cases, and I suspect that you know that. Only one or two GLARING cases per month perhaps, but over time it has added up. so what? the NCC has 14,000 members (or thereabouts) and ther

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <20151104184211.gm47...@cilantro.c4inet.net>, "Sascha Luck [ml]" wrote: >A few people or companies who act in bad faith do not change this >fact and there is no reason to put the entire membership under >general suspicion and waste its time and fees with elaborate data >collection /

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Sascha Luck [ml]
On Thu, Nov 05, 2015 at 01:31:31PM -0800, Ronald F. Guilmette wrote: In message <20151104143230.gk47...@cilantro.c4inet.net>, I really would like to be there with a video camera the next time you find yourself having to go through airport security. YouTube stardom awaits us. Yeah, but not min

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Sascha Luck [ml]
On Thu, Nov 05, 2015 at 01:31:31PM -0800, Ronald F. Guilmette wrote: 1) All resource holders are presumed to be bad actors and all of their data must be kept in a database, their correctness to be strictly enforced. I am sure that your view is sincerly held, carefully considered, and shared by

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <20151104143230.gk47...@cilantro.c4inet.net>, "Sascha Luck [ml]" wrote: >No. Just NO. I am, frankly, flabbergasted at this mindset: > >1) All resource holders are presumed to be bad actors and all of >their data must be kept in a database, their correctness to be >strictly enforced.

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Sascha Luck [ml]
On Thu, Nov 05, 2015 at 07:40:58PM +, ripede...@yahoo.co.uk wrote: STEP 2 For those ROUTE objects from STEP 1 where the out of region resource does exist, hold the object creation as pending. The mechanism for doing this already exists in the RIPE Database software as it is used for multiple

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Ronald F. Guilmette
In message <637758753.2826426.1446595528880.javamail.ya...@mail.yahoo.com>, ripede...@yahoo.co.uk wrote: >Ronald >"I neither mentioned nor asked about out-of-region objects." >"then proceeded to announce a bunch of self-evidently bogus routes to relat= >ively large swaths of APNIC address space.

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Elvis Daniel Velea
Hi, I like the idea. I would have preffered a cross registry/RIR solution but as you said, it has been many months (I actually raised the issue 2 RIPE meetings ago - in London) but nothing visible has been done to fix this problem. +1 from me. cheers, elvis Excuse the briefness of this mail, it

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread denis
Hi Gert Thanks for the quick response and support. On 05/11/2015 20:56, Gert Doering wrote: Hi, On Thu, Nov 05, 2015 at 07:40:58PM +, ripede...@yahoo.co.uk wrote: So here is my 4 step proposal that I believe could be implemented within a month. If we implemented this you can be sure that

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Bengt Gördén
Den 2015-11-05 kl. 20:40, skrev ripede...@yahoo.co.uk: HI all I am going to have one last go at solving this problem. I challenge anyone/everyone to tell me why this is such a stupid idea, technically impossible to do, won't solve any of the issues partially or fully. Then I can shut up about

Re: [anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread Gert Doering
Hi, On Thu, Nov 05, 2015 at 07:40:58PM +, ripede...@yahoo.co.uk wrote: > So here is my 4 step proposal that I believe could be implemented within a > month. If we implemented this you can be sure that all ROUTE objects in the > RIPE Database were created with the knowledge and approval of th

[anti-abuse-wg] Solving the issue of rogue ROUTE objects in the RIPE Database

2015-11-05 Thread ripedenis
HI all I am going to have one last go at solving this problem. I challenge anyone/everyone to tell me why this is such a stupid idea, technically impossible to do, won't solve any of the issues partially or fully. Then I can shut up about it and go away. If you can't condemn the idea then suppo

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Piotr Strzyzewski
On Mon, Nov 02, 2015 at 07:06:09PM -0800, Ronald F. Guilmette wrote: > I've been to Europe only one time, in 2010. I had to buy a cell phone > there to communicate, and when I did I was entirely surprised to learn > that one cannot do so without presenting some form of identification, > passport,

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Piotr Strzyzewski
On Mon, Nov 02, 2015 at 12:29:18PM -0800, Ronald F. Guilmette wrote: > Should we worry also that the penguins in Antartica won't be able to > obtain RIPE number resources because they also don't have working > phones? Although your argumentation most times violates the eristic rules I would like j

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Piotr Strzyzewski
On Wed, Nov 04, 2015 at 03:41:39PM -0800, Ronald F. Guilmette wrote: > If a formal proposal was put forward to the entire RIPE membership > which proposed that all mailing addresses and phone numbers be > completely removed from the WHOIS data base, would you personally > vote "yea" or "nay" on tha

Re: [anti-abuse-wg] AS's with route objects for undelegated space

2015-11-05 Thread denis
Hi Richard On 05/11/2015 17:40, Richard Clayton wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have read recent discussion here about AS204224 with interest... ... what seems to have escaped notice is rather temporary nature of the dubious route objects inserted into the RIPE database

[anti-abuse-wg] AS's with route objects for undelegated space

2015-11-05 Thread Richard Clayton
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have read recent discussion here about AS204224 with interest... ... what seems to have escaped notice is rather temporary nature of the dubious route objects inserted into the RIPE database by AS204224. At the time of writing there are no such obj

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Brian Nisbet
Ronald, On 04/11/2015 20:49, Ronald F. Guilmette wrote: Brian, My apologies for not responding yesterday. I've been working on what I think is a REALLY important project... one that even relates to some of what's been discussed here... and I just got totally caught up in that yesterday (and pr

Re: [anti-abuse-wg] WHOIS (AS204224)

2015-11-05 Thread Brian Nisbet
On 04/11/2015 23:09, Ronald F. Guilmette wrote: In message , Suresh Ramasubramanian wrote: Right now, most other lists that I see this thread start up on, there are a few people who defend RIPE NCC - and a lot of people who dump on it for this kind of thing. I like to think that I am neithe