[98097] in North American Network Operators' Group
Re: DNS Hijacking by Cox
daemon@ATHENA.MIT.EDU (Brandon Galbraith)
Tue Jul 24 19:36:05 2007
Date: Tue, 24 Jul 2007 17:43:30 -0500
From: "Brandon Galbraith" <brandon.galbraith@gmail.com>
To: "Chris L. Morrow" <christopher.morrow@verizonbusiness.com>
Cc: "Mattias Ahnberg" <mattias@ahnberg.pp.se>, NANOG <nanog@merit.edu>
In-Reply-To: <Pine.GSO.4.58.0707242128120.1179@marvin.argfrp.us.uu.net>
Errors-To: owner-nanog@merit.edu
------=_Part_177483_26051782.1185317010098
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 7/24/07, Chris L. Morrow <christopher.morrow@verizonbusiness.com> wrote:
>
>
>
>
> On Tue, 24 Jul 2007, Mattias Ahnberg wrote:
>
> > But it certainly would not hurt if there was a good way to report
> > drones to ISPs and actually get some attention to the problem. A
> > bunch of small streams quickly build up to a larger river in the
> > end, I guess.
>
> I'd point at the IETF/INCH-WG work for a standard abuse@ reporting
> process/format... If you send hundreds or thousands of reports to an ISP
> abusedesk (or ISPs' abusedesks) a standard machine parsable format is a
> key ingredient.
>
> I think that atleast one ISP would love to see standards formatted reports
> about it's users (abuse@uu.net), provided that the appropriate information
> was included.
>
I think at that point, machine-readable formats should be passed up for some
sort of abuse API interchange, where all involved parties can pull status
information in real-time. You also have the benefit of automated systems
having the ability to integrate into the system.
------=_Part_177483_26051782.1185317010098
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><div><span class="gmail_quote">On 7/24/07, <b class="gmail_sendername">Chris L. Morrow</b> <<a href="mailto:christopher.morrow@verizonbusiness.com">christopher.morrow@verizonbusiness.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><br>On Tue, 24 Jul 2007, Mattias Ahnberg wrote:<br><br>> But it certainly would not hurt if there was a good way to report<br>> drones to ISPs and actually get some attention to the problem. A<br>> bunch of small streams quickly build up to a larger river in the
<br>> end, I guess.<br><br>I'd point at the IETF/INCH-WG work for a standard abuse@ reporting<br>process/format... If you send hundreds or thousands of reports to an ISP<br>abusedesk (or ISPs' abusedesks) a standard machine parsable format is a
<br>key ingredient.<br><br>I think that atleast one ISP would love to see standards formatted reports<br>about it's users (<a href="mailto:abuse@uu.net">abuse@uu.net</a>), provided that the appropriate information<br>
was included.<br></blockquote></div><br>I think at that point, machine-readable formats should be passed up for some sort of abuse API interchange, where all involved parties can pull status information in real-time. You also have the benefit of automated systems having the ability to integrate into the system.
<br>
------=_Part_177483_26051782.1185317010098--
