[32075] in North American Network Operators' Group
RE: DoS issue, conclusion
daemon@ATHENA.MIT.EDU (Mathew Butler)
Tue Nov 7 18:35:34 2000
Message-ID: <F062E72E4BA2D4119F1700B0D03D205F3988@MAIL>
From: Mathew Butler <mbutler@tonbu.com>
To: 'Christian Nielsen' <cnielsen@nielsen.net>,
Ariel Biener <ariel@fireball.tau.ac.il>
Cc: nanog@merit.edu
Date: Tue, 7 Nov 2000 15:26:24 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C04912.24AE1000"
Errors-To: owner-nanog-outgoing@merit.edu
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C04912.24AE1000
Content-Type: text/plain;
charset="iso-8859-1"
Actually, this brings up an interesting point... what can one reasonably
expect from an upstream provider to be put in the original service contract?
Who has to pay for the time to resolve issues? What kinds of issues are
normally part of the contract, and what kinds aren't?
-Mat Butler
-----Original Message-----
From: Christian Nielsen [mailto:cnielsen@nielsen.net]
Sent: Tuesday, November 07, 2000 3:18 PM
To: Ariel Biener
Cc: nanog@merit.edu
Subject: Re: DoS issue, conclusion
On Tue, 7 Nov 2000, Ariel Biener wrote:
> 3). Major Tier1 providers are either not represented on this list, or
> don't care.
not that... it is just that most ISPs dont have large staff to deal with
these
types of issues. And maybe, if you were being DoSed, and you offered to pay
for their time, they might answer differently.
Christian
------_=_NextPart_001_01C04912.24AE1000
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: DoS issue, conclusion</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Actually, this brings up an interesting point... what =
can one reasonably expect from an upstream provider to be put in the =
original service contract? Who has to pay for the time to resolve =
issues? What kinds of issues are normally part of the contract, =
and what kinds aren't?</FONT></P>
<P><FONT SIZE=3D2>-Mat Butler</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Christian Nielsen [<A =
HREF=3D"mailto:cnielsen@nielsen.net">mailto:cnielsen@nielsen.net</A>]</F=
ONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, November 07, 2000 3:18 PM</FONT>
<BR><FONT SIZE=3D2>To: Ariel Biener</FONT>
<BR><FONT SIZE=3D2>Cc: nanog@merit.edu</FONT>
<BR><FONT SIZE=3D2>Subject: Re: DoS issue, conclusion</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>On Tue, 7 Nov 2000, Ariel Biener wrote:</FONT>
</P>
<P><FONT SIZE=3D2>> 3). Major Tier1 providers are either not =
represented on this list, or</FONT>
<BR><FONT SIZE=3D2>> don't care.</FONT>
</P>
<P><FONT SIZE=3D2>not that... it is just that most ISPs dont have large =
staff to deal with these</FONT>
<BR><FONT SIZE=3D2>types of issues. And maybe, if you were being DoSed, =
and you offered to pay</FONT>
<BR><FONT SIZE=3D2>for their time, they might answer =
differently.</FONT>
</P>
<P><FONT SIZE=3D2>Christian</FONT>
</P>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C04912.24AE1000--
