Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-17 Thread Martin Hannigan
On Tue, Jul 16, 2019 at 11:29 AM ARIN wrote: [ clip ] The current policy, “3.6. Annual Validation of ARIN’s Public Whois Point > of Contact Data” does not provide sufficient validation of the actual > availablility of the abuse mailbox. > RFC 2142 clearly identifies what mailboxes are used

Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-17 Thread Steve Atkins
> On Jul 17, 2019, at 8:12 AM, JORDI PALET MARTINEZ via ARIN-PPML > wrote: > > Hi Steve, > > The actual POC validation is also sending an email with a link. So, if you > aren’t able to "classify" that and have a human behind, then the validation > fails, so in that sense I don't see the

Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-17 Thread JORDI PALET MARTINEZ via ARIN-PPML
Hi Steve, The actual POC validation is also sending an email with a link. So, if you aren’t able to "classify" that and have a human behind, then the validation fails, so in that sense I don't see the difference. The final goal is that we can be sure that if somebody is sending an abuse

Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-16 Thread Steve Atkins
> On Jul 16, 2019, at 6:05 PM, JORDI PALET MARTINEZ via ARIN-PPML > wrote: > > Hi Scott, > > I guess there is some misunderstanding in that part of the text. May be > “ultimately” is not doing the intended “work”. The idea is “last resort”. > > The idea is not that messages are processed

Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-16 Thread JORDI PALET MARTINEZ via ARIN-PPML
El 16/7/19 19:27, "Scott Leibrand" escribió: Ok, glad to hear the intent regarding automated processing is closer to what I would consider appropriate. How about: "All emails sent to this address must be processed appropriately, ultimately reaching a human processor who evaluates

Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-16 Thread Scott Leibrand
Ok, glad to hear the intent regarding automated processing is closer to what I would consider appropriate. How about: "All emails sent to this address must be processed appropriately, ultimately reaching a human processor who evaluates each message that cannot be appropriately handled by any

Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-16 Thread JORDI PALET MARTINEZ via ARIN-PPML
Hi Scott, I guess there is some misunderstanding in that part of the text. May be “ultimately” is not doing the intended “work”. The idea is “last resort”. The idea is not that messages are processed only by humans. If it can be automatically processed that’s fine and perfect. The goal

Re: [arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-16 Thread Scott Leibrand
Strongly opposed as written. This policy would require that all "abuse reports receive a response" from "a human processor who evaluates each message received", which constitutes an inappropriate interference in the business operations of ISPs, and presents a denial of service vector. There are

[arin-ppml] Revised/Retitled - Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts

2019-07-16 Thread ARIN
The following has been revised and retitled: * Draft Policy ARIN-2019-5: Validation of POCs Referenced as Abuse Contacts Formerly: * Draft Policy ARIN-2019-5: Validation of Abuse-mailbox Revised text is below and can be found at: https://www.arin.net/participate/policy/drafts/2019_5/ You are