Re: [tcpm] Separate header checksums and WiFi

Joe Touch <touch@ISI.EDU> Wed, 31 January 2007 15:59 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCHrd-0003Eu-HD; Wed, 31 Jan 2007 10:59:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HCHrc-0003EJ-5E for tcpm@ietf.org; Wed, 31 Jan 2007 10:59:12 -0500
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HCHrZ-0002HD-Lw for tcpm@ietf.org; Wed, 31 Jan 2007 10:59:12 -0500
Received: from [127.0.0.1] ([67.122.65.220]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id l0VFwmQA028273; Wed, 31 Jan 2007 07:58:49 -0800 (PST)
Message-ID: <45C0BCB7.8090301@isi.edu>
Date: Wed, 31 Jan 2007 07:58:47 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Michael Welzl <michael.welzl@uibk.ac.at>
Subject: Re: [tcpm] Separate header checksums and WiFi
References: <1170256423.4805.611.camel@lap10-c703.uibk.ac.at>
In-Reply-To: <1170256423.4805.611.camel@lap10-c703.uibk.ac.at>
X-Enigmail-Version: 0.94.0.0
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: tcpm@ietf.org
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1547907990=="
Errors-To: tcpm-bounces@ietf.org


Michael Welzl wrote:
> Dear all,
> 
> A long time ago, at the San Diego IETF meeting in August 2004,
> I presented an idea called "Corruption Notification Options"
> (a proposal which is some sort of a refined specification of
> the TCP HACK idea) to this group.
> 
> The group's feedback was that this is useless, as errors
> occur in such a clustered fashion that you wouldn't see
> any packets with an intact header but erroneous payload
> (which is the only situation where the scheme would
> yield any benefit). I think that it was Gorry Fairhurst
> who said this.

There was a separate issue - you need to *know* the header is intact.
For TCP, there's no separate header checksum to provide that
information. I.e., this might be possible with UDP-lite, but isn't with
UDP or TCP. This might not affect the SCTP or DCCP variants, depending
on what their checksums cover.

Joe

-- 
----------------------------------------
Joe Touch
Sr. Network Engineer, USAF TSAT Space Segment

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm