[BEHAVE] Response of firewalls and middleboxes to TCP SYN packets that are ECN-Capable?
Sally Floyd <sallyfloyd@mac.com> Thu, 02 August 2007 21:36 UTC
Return-path: <behave-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGiLT-0003uZ-Kw; Thu, 02 Aug 2007 17:36:35 -0400
Received: from behave by megatron.ietf.org with local (Exim 4.43) id 1IGiLS-0003uN-S9 for behave-confirm+ok@megatron.ietf.org; Thu, 02 Aug 2007 17:36:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGiLS-0003uA-Gk for behave@ietf.org; Thu, 02 Aug 2007 17:36:34 -0400
Received: from smtpout.mac.com ([17.250.248.174]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGiLS-0003oB-2s for behave@ietf.org; Thu, 02 Aug 2007 17:36:34 -0400
Received: from mac.com (smtpin04-en2 [10.13.10.149]) by smtpout.mac.com (Xserve/smtpout04/MantshX 4.0) with ESMTP id l72LaXqp013727 for <behave@ietf.org>; Thu, 2 Aug 2007 14:36:33 -0700 (PDT)
Received: from [192.150.186.170] (laptop170.icsi.berkeley.edu [192.150.186.170]) (authenticated bits=0) by mac.com (Xserve/smtpin04/MantshX 4.0) with ESMTP id l72LaWLC020426 for <behave@ietf.org>; Thu, 2 Aug 2007 14:36:32 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v624)
Content-Transfer-Encoding: 7bit
Message-Id: <ef4738efbd5f84e2acd22562f941288a@mac.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
To: behave@ietf.org
From: Sally Floyd <sallyfloyd@mac.com>
Date: Thu, 02 Aug 2007 14:36:32 -0700
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [BEHAVE] Response of firewalls and middleboxes to TCP SYN packets that are ECN-Capable?
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
Errors-To: behave-bounces@ietf.org
In the TCPM working group, my co-authors and I are finishing up a
draft on adding ECN-capability to TCP's SYN/ACK packets
("http://tools.ietf.org/html/draft-ietf-tcpm-ecnsyn").
Dave Thaler gave a report at the March IETF on the problems that
regular TCP data packets can encounter from routers or middleboxes
along the path
("http://www3.ietf.org/proceedings/07mar/slides/tsvarea-3/sld6.htm")
The point of this email is to ask if anyone knows anything about
specific problems that TCP SYN/ACK packets might encounter from the
network if the ECN field in the IP header is marked as ECN-Capable
(ECT) or Congestion Experienced (CE), over and above the problems
that are already known about for TCP data packets. I am sending
this email to this mailing list because it was suggested by someone
at the TCPM working group last week.
Any feedback that anyone might have would be appreciated.
Many thanks,
- Sally
http://www.icir.org/floyd/
_______________________________________________
Behave mailing list
Behave@ietf.org
https://www1.ietf.org/mailman/listinfo/behave
- [BEHAVE] Response of firewalls and middleboxes to… Sally Floyd
- Re: [BEHAVE] Response of firewalls and middleboxe… Rémi Denis-Courmont
- Re: [BEHAVE] Response of firewalls and middleboxe… Sally Floyd