Re: [Tsvwg] F-RTO - open issues?

Neil Spring <nspring@cs.washington.edu> Wed, 09 October 2002 20:20 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03137 for <tsvwg-archive@odin.ietf.org>; Wed, 9 Oct 2002 16:20:37 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99KMJg15645 for tsvwg-archive@odin.ietf.org; Wed, 9 Oct 2002 16:22:19 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KM3v15634; Wed, 9 Oct 2002 16:22:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KLXv15580 for <tsvwg@optimus.ietf.org>; Wed, 9 Oct 2002 16:21:33 -0400
Received: from evil.cs.washington.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03089 for <tsvwg@ietf.org>; Wed, 9 Oct 2002 16:19:20 -0400 (EDT)
Received: from nspring by evil.cs.washington.edu with local (Exim 3.35 #1 (Debian)) id 17zNKg-00014K-00 for <tsvwg@ietf.org>; Wed, 09 Oct 2002 13:21:26 -0700
Date: Wed, 09 Oct 2002 13:21:26 -0700
From: Neil Spring <nspring@cs.washington.edu>
To: tsvwg@ietf.org
Subject: Re: [Tsvwg] F-RTO - open issues?
Message-ID: <20021009202119.GA4075@cs.washington.edu>
References: <200210081457.RAA17480@mgw.research.nokia.com> <01b001c26f9c$ee9fb320$6b24b183@gurtoannb1> <200210091522.SAA21341@mgw.research.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <200210091522.SAA21341@mgw.research.nokia.com>
User-Agent: Mutt/1.3.28i
Sender: tsvwg-admin@ietf.org
Errors-To: tsvwg-admin@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>

On Wed, Oct 09, 2002 at 06:22:03PM +0300, Pasi Sarolahti wrote:
>> 3. Have you thought about protection against malicious TCP receivers?

> A receiver that sends malicious acks? I think any TCP sender is in
> problems in that case. 

Not all TCP senders have problems with malicious receivers,
only those that trust all acks.

 http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-tcp-nonce-03.txt

is an allocation of a bit in the TCP header to allow the
receiver to prove it has received only un-ECN-marked
original (not re-) transmissions.

That internet draft, whose status I've forgotten though I
thought it was on the path toward submission to the IESG as
a Proposed Standard, was a result of some simple analysis
in:

 http://www.cs.ucsd.edu/~savage/papers/ICNP01.pdf

Although the ICNP paper describes the ECN case specifically,
its predecessor:

 http://www.cs.ucsd.edu/~savage/papers/CCR99.pdf

describes a set of attacks a malicious receiver could employ
to subvert the sender's congestion control policy.  Not all
of these attacks work against robust senders.

enjoy,
-neil
_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg