Re: [Spud] [tsvwg] New Version Notification for draft-touch-tsvwg-udp-options-01.txt

Joe Touch <touch@isi.edu> Mon, 02 November 2015 15:29 UTC

Return-Path: <touch@isi.edu>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FDD01B4843; Mon, 2 Nov 2015 07:29:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4p5Kz1ZJ47k; Mon, 2 Nov 2015 07:29:34 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1EBE1B483E; Mon, 2 Nov 2015 07:29:34 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-225-10.socal.res.rr.com [172.250.225.10]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id tA2FSMWX020213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 2 Nov 2015 07:28:24 -0800 (PST)
To: Tom Herbert <tom@herbertland.com>, Bob Briscoe <ietf@bobbriscoe.net>
References: <CACL_3VF5i7FvMR53R8JwRQAW--QJz3a+T9c_Pnwqt9D-baAJ-w@mail.gmail.com> <5636FD40.4030101@bobbriscoe.net> <CALx6S36vY+E-JN7eU5hwur-W2KzYfavhYSyPbcAwZec1pA0b6w@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <56378116.2050709@isi.edu>
Date: Mon, 2 Nov 2015 07:28:22 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <CALx6S36vY+E-JN7eU5hwur-W2KzYfavhYSyPbcAwZec1pA0b6w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: tA2FSMWX020213
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/FIA4xc-ApPUvvRXpLixhhquvnTw>
Cc: spud <spud@ietf.org>, tsvwg <tsvwg@ietf.org>, touch@isi.edu
Subject: Re: [Spud] [tsvwg] New Version Notification for draft-touch-tsvwg-udp-options-01.txt
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2015 15:29:35 -0000


On 11/1/2015 10:43 PM, Tom Herbert wrote:
> On Mon, Nov 2, 2015 at 3:05 PM, Bob Briscoe <ietf@bobbriscoe.net> wrote:
>> Joe,
>>
>> Before starting measurements, I would recommend searching the Web for the
>> manuals of middleboxes that might block such packets.
>>
> Please look at NIC offloads also. I am pretty certain that the most
> common flavor of checksum offload will break in this proposal since
> devices use the value in the UDP length field as the length of the
> payload to compute the checksum over. 

That is the intended behavior.

> UDP Fragmentation Offload would
> similarly be broken, although we can probably live without that (but
> we can't live without checksum offload!).

We need to live without broken offloads because offloads are part of the
protocol stack. They can't simply jump in and try to help without being
very careful about corner cases like this.

E.g., we've already seen an offload that merges TCP packets with
different options, which ought to be clearly inappropriate.

Joe