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

"C. M. Heard" <heard@pobox.com> Tue, 28 February 2017 23:06 UTC

Return-Path: <heard@pobox.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C609B1297CA for <tsvwg@ietfa.amsl.com>; Tue, 28 Feb 2017 15:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level:
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
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 7pJo6cZduPtb for <tsvwg@ietfa.amsl.com>; Tue, 28 Feb 2017 15:06:38 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B35E1297C9 for <tsvwg@ietf.org>; Tue, 28 Feb 2017 15:06:38 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B9AB06958E for <tsvwg@ietf.org>; Tue, 28 Feb 2017 18:06:36 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type; s=sasl; bh=m03IlpgF1+QPtNrqm3QihdtAPZg=; b=pmPozh j+A69eKNBu3AkxtQepLWOLysoVn453GVLVa3J7kDPidJzdGStoqLxxiGRsN/3o9H qdH1YWUOL+5rTmmYVdbTxPcNY75eDIkiCgHIbkc0cnLbiOn8Fzf4cZC7X6Wt/K9v tf3KdRGdIBwbhHbaEkiDGNd0okOpkN+4HkNIw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type; q=dns; s=sasl; b=laTwRtdOb3pG9eW39I8YOpgRU9sFeR+C HqfyaK//SByA19VEITPBrftefbIBinCgfhAjiJzWMQ3J3cgejSRwEmaET2PGHY7p g4p/yMMApoRGGK+9dx7W522VYxma+MGrCyHXoDrWX5GGiAg2stUFlnYUcpzl+xK5 NdBY5bDwaZo=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B18CA6958B for <tsvwg@ietf.org>; Tue, 28 Feb 2017 18:06:36 -0500 (EST)
Received: from mail-qk0-f177.google.com (unknown [209.85.220.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 4033A69585 for <tsvwg@ietf.org>; Tue, 28 Feb 2017 18:06:36 -0500 (EST)
Received: by mail-qk0-f177.google.com with SMTP id s186so43467875qkb.1 for <tsvwg@ietf.org>; Tue, 28 Feb 2017 15:06:36 -0800 (PST)
X-Gm-Message-State: AMke39lqygJ8kuXwAtiuyqyw+TgJv++eiX+AG4wN/rfZ9BNyAVTKoZFrIE5nDu4wudsOLf4Y8Ylk7ZhPYV0vcQ==
X-Received: by 10.200.36.93 with SMTP id d29mr6508708qtd.265.1488323195606; Tue, 28 Feb 2017 15:06:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Tue, 28 Feb 2017 15:06:15 -0800 (PST)
In-Reply-To: <3a4a6b78-8146-de4c-6246-7bd09de44f1c@isi.edu>
References: <CACL_3VFeJs7KzG9Bchh15bfZ3CmaOPWcfisEreNoGYK5CsEJ+g@mail.gmail.com> <3a4a6b78-8146-de4c-6246-7bd09de44f1c@isi.edu>
From: "C. M. Heard" <heard@pobox.com>
Date: Tue, 28 Feb 2017 15:06:15 -0800
X-Gmail-Original-Message-ID: <CACL_3VFkr3mGe-yTbvHrTZcKVCpEv3FeSOyoShUxCK5+9Tdqqg@mail.gmail.com>
Message-ID: <CACL_3VFkr3mGe-yTbvHrTZcKVCpEv3FeSOyoShUxCK5+9Tdqqg@mail.gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset="UTF-8"
X-Pobox-Relay-ID: 8DC14106-FE0A-11E6-AA4C-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/sOMNHMYxMDgEivX3t-dNWzFDqWg>
Cc: Mark Smith <markzzzsmith@gmail.com>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] New Version Notification for draft-touch-tsvwg-udp-options-05.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 23:06:40 -0000

On Tue, Feb 28, 2017 at 12:03 PM, Joe Touch <touch@isi.edu> wrote:
> On 2/28/2017 10:58 AM, C. M. Heard wrote:
>> If the Fragmentation option includes its own post-reassembly checksum,
>> then a Lite option could be inserted immediately following the UDP
>> header in each fragment, without loss of functionality. Implementations
>> that do not support UDP options would see UDP fragments so constructed
>> as empty UDP datagrams and would discard them, removing the danger of
>> accidental misinterpretation.
>
> Is see how that's useful, but it would also appear to mean we might be
> able to use LITE twice - once as this trick to hide fragments (which is
> elegant - thanks!), but also to allow the use of LITE in the final
> result. I'm not sure whether that makes sense yet, though - if you check
> to see that the whole thing is there, there's little point in allowing
> part of the packet to not be checksummed (it already would be).
>
> So maybe LITE couples with FRAG only in the way you mention, and no other?

That is exactly how I would envision it.

Thanks,

Mike Heard