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

2015-11-02 Thread Aftab Siddiqui
> >Yes it is easy.. but not scalable, exception rate would be very high.. > > Forgive me, but this opinion is based on what, exactly? > > And what exactly are we talking about when we say "exception"? > I could be wrong in this assumption. So lets ask RIPE NCC (secretariat) how many bounce email t

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

2015-11-02 Thread Jeffrey Race
On Tue, 3 Nov 2015 02:42:33 +, Sascha Luck [ml] wrote: >Exactly *what* purpose would a phone call or fax (why not TELEX >if we're doing retro tech?) serve? Precisely to establish that the registrant humanly responds to messages at its published addresses. The registrar would have to employ

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

2015-11-02 Thread Jeffrey Race
On Tue, 03 Nov 2015 02:31:26 +, Aftab Siddiqui wrote: >Yes it is easy.. but not scalable, exception rate would be >very high.. multiply that with 7000+ (members) It's not a problem for the registrar!!No human effort is required at all so the registrar incurs no costs except setting the

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

2015-11-02 Thread Ronald F. Guilmette
In message Aftab Siddiqui wrote: >Yes it is easy.. but not scalable, exception rate would be very high.. Forgive me, but this opinion is based on what, exactly? And what exactly are we talking about when we say "exception"? Are we talking about contact phone numbers that don't work anymore b

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

2015-11-02 Thread Suresh Ramasubramanian
It hasn't worked worth being able to trust any LIR fed data so far over the past few years that we've had iterations of this discussion on this wg I will let Ron continue repeating himself and you can continue to advocate for "we are not the Internet police" --srs > On 03-Nov-2015, at 8:12 AM,

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

2015-11-02 Thread Ronald F. Guilmette
Jeffrey Race wrote: >This is easy stuff. I agree that it isn't at all hard, thank you for supporting the point I was attempting to make, anmd complement you for the clever addition of the "continuously working" requirement, and the idea of automated, time-randomized spot checking. Ingeneous

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

2015-11-02 Thread Sascha Luck [ml]
On Tue, Nov 03, 2015 at 08:06:56AM +0530, Suresh Ramasubramanian wrote: It needn't be done except as an additional verification step for new asns and suspect ones Sigh. Having an ASN assigned involves exchange of signed contracts between sponsoring LIR and end-user. These, as well as company re

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

2015-11-02 Thread Suresh Ramasubramanian
It needn't be done except as an additional verification step for new asns and suspect ones --srs > On 03-Nov-2015, at 8:01 AM, Aftab Siddiqui wrote: > > Yes it is easy.. but not scalable, exception rate would be very high.. > multiply that with 7000+ (members)

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

2015-11-02 Thread Aftab Siddiqui
Hi Jeffrey, On Tue, 3 Nov 2015 at 13:21 Jeffrey Race wrote: > This is trivially and virtually costlessly done in an automated way, > taking about a day of a good programmer's time. Thereafter > zero/minimal maintenance except for 'exception' followups. > > One informs registrants that CONTI

[anti-abuse-wg] Verifiability (was: WHOIS (AS204224))

2015-11-02 Thread Jeffrey Race
This is trivially and virtually costlessly done in an automated way, taking about a day of a good programmer's time. Thereafter zero/minimal maintenance except for 'exception' followups. One informs registrants that CONTINUOUSLY working contact modes (e-mail, fax, phone, postal, say at least