RE: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-15 Thread Michel Py
Hi John, > John Curran wrote : > Even so, we at ARIN are in the midst of a Board-directed review of the RPKI > legal framework to see if any improvements can be made > > – I will provide further updates

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread Ronald F. Guilmette
In message , John Curran wrote: >Alas, it’s not those who fail to properly configure RPKI that are likely to be >litigating, but rather their impacted customers and those customers' business >partners who all were unable to communicate due to no fault of their own. > >Such a matter will not be

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread Anne P. Mitchell, Esq.
> There's obviously a disconnect where people aren't worried about indemnifying > Spamhaus for using their block list, but are worried about indemnifying ARIN > for > using the TAL. That would be because there is a rather substantial difference between publishing an IP address for which you

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread Valdis Klētnieks
On Wed, 14 Aug 2019 16:07:49 -, John Curran said: > > But I suspect a lot of companies are reading it as: "If a spammer sues you > > for using > > a block list that prevents them from spamming your customers, you can't end > > up > > owing money to the block list maintainers. But if you

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread Rubens Kuhl
On Wed, Aug 14, 2019 at 1:09 PM John Curran wrote: > On 14 Aug 2019, at 11:15 AM, Valdis Klētnieks > wrote: > > > > On Wed, 14 Aug 2019 02:42:09 -, John Curran said: > > > >> You might want want to ask them why they are now a problem when they > weren’t > >> before (Also worth noting that

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread John Curran
On 14 Aug 2019, at 11:15 AM, Valdis Klētnieks wrote: > > On Wed, 14 Aug 2019 02:42:09 -, John Curran said: > >> You might want want to ask them why they are now a problem when they weren’t >> before (Also worth noting that many of these ISP's own contracts with their >> customers have

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread Valdis Klētnieks
On Wed, 14 Aug 2019 02:42:09 -, John Curran said: > You might want want to ask them why they are now a problem when they weren’t > before (Also worth noting that many of these ISP's own contracts with their > customers have rather similar indemnification clauses.) Actually, it's probably

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread John Curran
On 14 Aug 2019, at 1:21 AM, Ronald F. Guilmette mailto:r...@tristatelogic.com>> wrote: In message <06570278-e1ad-4bb0-a9fc-11a77bed7...@arin.net>, John Curran mailto:jcur...@arin.net>> wrote: Even so, we at ARIN are in the midst of a

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread John Curran
On 14 Aug 2019, at 2:26 AM, Matthew Petach wrote: > ... > Now, at the risk of bringing down the ire > of the community on my head...ARIN could > consider tying the elements together, at > least for ARIN members. Add the RPKI terms > into the RSA document. You need IP number > resources,

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread John Curran
On 14 Aug 2019, at 1:01 AM, William Herrin wrote: > ... > > I would observe that continued use at that point has been held > > to indicate agreement on your part [ref: Register.com, Inc. v. Verio, Inc., > > 356 F.3d 393 (2d Cir. 2004)] > > In which Verio admitted to the court that they knew

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-14 Thread Matthew Petach
On Tue, Aug 13, 2019 at 5:44 PM John Curran wrote: > On 13 Aug 2019, at 9:28 PM, Ronald F. Guilmette > wrote: > > ... > The last time I looked, RPKI adoption was sitting at around a grand total > of 15% worldwide. Ah yes, here it is... > > https://rpki-monitor.antd.nist.gov/ > > I've asked

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-13 Thread Ronald F. Guilmette
In message <06570278-e1ad-4bb0-a9fc-11a77bed7...@arin.net>, John Curran wrote: >Even so, we at ARIN are in the midst of a Board-directed review of the RPKI >legal framework to see if any improvements can be made

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-13 Thread William Herrin
On Tue, Aug 13, 2019 at 8:25 PM John Curran wrote: > On 13 Aug 2019, at 11:03 PM, William Herrin wrote: > I signed no legal agreement either to register my legacy addresses or to do a whois lookup to check someone else's addresses. Just sayin’. > > If you instead used a command line interface

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-13 Thread John Curran
On 13 Aug 2019, at 11:03 PM, William Herrin mailto:b...@herrin.us>> wrote: On Tue, Aug 13, 2019 at 7:42 PM John Curran mailto:jcur...@arin.net>> wrote: On 13 Aug 2019, at 9:28 PM, Ronald F. Guilmette mailto:r...@tristatelogic.com>> wrote: The last time I looked, RPKI adoption was sitting at

Re: RPKI adoption (was: Re: Corporate Identity Theft: Azuki, LLC -- AS13389, 216.179.128.0/17)

2019-08-13 Thread William Herrin
On Tue, Aug 13, 2019 at 7:42 PM John Curran wrote: > On 13 Aug 2019, at 9:28 PM, Ronald F. Guilmette > wrote: > > The last time I looked, RPKI adoption was sitting at around a grand total > of 15% worldwide. Ah yes, here it is... > > https://rpki-monitor.antd.nist.gov/ > > I've asked many