Re: [Tsvwg] Separate header checksums and WiFi
Randall Stewart <randall@lakerest.net> Sat, 17 February 2007 11:04 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HINN7-0003bs-Rw; Sat, 17 Feb 2007 06:04:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HINN5-0003bn-SY for tsvwg@ietf.org; Sat, 17 Feb 2007 06:04:51 -0500
Received: from adsl-070-155-160-098.sip.cae.bellsouth.net ([70.155.160.98] helo=lakerest.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HINN4-0000rs-GI for tsvwg@ietf.org; Sat, 17 Feb 2007 06:04:51 -0500
Received: from [127.0.0.1] (localhost [127.0.0.1]) by lakerest.net (8.13.6/8.13.6) with ESMTP id l1HB4gia097799; Sat, 17 Feb 2007 06:04:45 -0500 (EST) (envelope-from randall@lakerest.net)
DKIM-Signature: a=rsa-sha1; c=simple/simple; d=lakerest.net; s=lakerest; t=1171710285; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC: Subject:References:In-Reply-To:Content-Type: Content-Transfer-Encoding; b=Zqrt2egqmG/st95ddEg5n4cVHpxdZI5H5cQmx4 7g5AfdLXjUm/rkMeI5mtxDWcnlWr24xNJEqA6tR3bPVbzt6g==
Message-ID: <45D6E12D.1020402@lakerest.net>
Date: Sat, 17 Feb 2007 06:04:13 -0500
From: Randall Stewart <randall@lakerest.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061029 FreeBSD/i386 SeaMonkey/1.0.6
MIME-Version: 1.0
To: Michael Welzl <michael.welzl@uibk.ac.at>
Subject: Re: [Tsvwg] Separate header checksums and WiFi
References: <1170256466.4805.614.camel@lap10-c703.uibk.ac.at>
In-Reply-To: <1170256466.4805.614.camel@lap10-c703.uibk.ac.at>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: tsvwg-bounces@ietf.org
Michael Welzl wrote: > > I'm sending this note to TCPM, TSVWG and DCCP because there > are similar mechanisms there (DCCP: the Data Checksum option; SCTP: > http://www.ietf.org/internet-drafts/draft-stewart-sctp-pktdrprep-06.txt > although I just noticed that this is apparently not a WG item... > still, it's SCTP related). > > Michael: One comment on the above... the pktdrp document deals not with checksums getting to or not getting to transport.. It is designed to interact with a cisco product that runs over satellite networks. Where the router learns that some packet was dropped and what it sends back to the SCTP sender is the whole intact packet that it could not get through the satellite link. aka SCTP --->- R1 ///// satelink //// R2 --->- SCTP It is R1 that has a copy of the packet, and realizes it had a corruption over the link between R1 <-> R2. and R1 then sends back the notification. If R2 sent back the notification then we would see a similar thing as in your testing... R -- Randall Stewart 803-345-0369 <or> 815-342-5222(cell)
- [Tsvwg] Separate header checksums and WiFi Michael Welzl
- Re: [Tsvwg] Separate header checksums and WiFi Randall Stewart