Re: [tsvwg] Alternative version of the UDP FRAG option

Tom Herbert <tom@herbertland.com> Tue, 19 March 2019 02:11 UTC

Return-Path: <tom@herbertland.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 B25471277D0 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2019 19:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 TDngusaZZNf3 for <tsvwg@ietfa.amsl.com>; Mon, 18 Mar 2019 19:11:55 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 143F2126C15 for <tsvwg@ietf.org>; Mon, 18 Mar 2019 19:11:55 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id t28so20451952qte.6 for <tsvwg@ietf.org>; Mon, 18 Mar 2019 19:11:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7gsTL9MfzMJeKolYPQTO1oN4/z73h0dt2BtWLZsmqYs=; b=huCY1DbYB98RQjiLYKjfsgYrTxoyesJtkeMAqddiUsDj2//8WzBMpGzw2YIFYDLAqJ elMu9DKUYH+GsqxWxl3REtIUWAZkz3crE7+GPrNjr7PHBmojttDfI1IXFsH+EVAANPi/ mjCn0Z71XEqNqW/Oyzkv+ChtyWbOp/J8Ky3rqeogoiDrKQmbaqJOE5cjFlTc0HbjkW0r lb7hnFl7GiznlERa8qjAYG9t7Kdxq5Jhu7i++LP/ufroPBpKMEHqXrfFuO4P25nBSWFO mBPRCunktHeqAY8dtTw3gnydt0QaGT/bDTpxAqqzYwose+AHGZyRJdLrvvNarthTsukn pc3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7gsTL9MfzMJeKolYPQTO1oN4/z73h0dt2BtWLZsmqYs=; b=b//ZWnyK8cL5mvwtyclm1NsbwVYdhHQsmyB6sS5GUuFppK4g53Ynne/0p/6y4tO4DC hpW/RFUNFhLNKDCMhLWabiJRAuHze05sp+UVvBzGY4hruL7Xv513nUTPJ4xcOt8wMHdL /70eNDo5HW+OW9Pws8B7r9rwdwp22N/sn0LvF6DyFnsPmJs17Pw/sV9hvPqfz/NkBwCo HbMpsvO2jsEZmh8PBtCJcsmGATPxx1s44t4f6iiFIHZ19Z71IxY8ZzH5ZEwf+0G++yCU rJa6tuSUQOESN4S9w8dQgAI56kpIZQ6SdPQe4gym39mACzDhEn1zESak/3YoAN4GZ54Y kRXw==
X-Gm-Message-State: APjAAAU/Iz+3De6+m42zkdo+atUUKxSWROlfcWbOx3UzHXrrfQCF5lhA ud81MOMJ+QLm+1bh3dBK0vQZTrBJKAL7m0BEqYFM2g==
X-Google-Smtp-Source: APXvYqyKWancPKi3T/iTLo7oS+yxs3mqfQ3yqwVT3PcJoRhRopIwbgbzZ0a3BmA/4zzLSap+FqjaQHTMCHJVou8IKhA=
X-Received: by 2002:a0c:ba13:: with SMTP id w19mr24188qvf.179.1552961513573; Mon, 18 Mar 2019 19:11:53 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VE1=0OORUuOKg9GjcdVuhBNTkWhymE7PAs5WYO0ZR0DWQ@mail.gmail.com> <CALx6S37y_AbESyX5PcCSu7NEr-uPVrPXksEeAx5aSNAyqshL6Q@mail.gmail.com> <CACL_3VFJTxM3s-GLOTz9xmkNk1uOQoCmAGApbAf1ZgbH3Opptw@mail.gmail.com> <CALx6S36aWKHFXO=Zx8W-wFqqC5-Oueb3j-b9evm-yKpfguVQuw@mail.gmail.com> <5C8FBBED.7000805@erg.abdn.ac.uk> <CALx6S34FKNJ_6Ep659L3t_Kf4bnEKZ5LTjXo-zWz4PrveU_UVA@mail.gmail.com> <CALx6S37MsCmOOsn0bnHoTwJkN7Khfm03z__W4hhy7c29XuvQHw@mail.gmail.com> <5C8FDEED.8010701@erg.abdn.ac.uk> <CALx6S36fQcRdgvCG3XS78EecFjdb36D22iBzovXcODH_W+BHbg@mail.gmail.com> <5be88c76-d65a-c491-86be-74a52fef7687@strayalpha.com> <CALx6S35h+ANRpqrEyC97JocXUrDw_+b85a8bP7QgjSchMPXF-g@mail.gmail.com> <62f9f885-5dd6-78d4-2d8a-8fab83871529@strayalpha.com>
In-Reply-To: <62f9f885-5dd6-78d4-2d8a-8fab83871529@strayalpha.com>
From: Tom Herbert <tom@herbertland.com>
Date: Mon, 18 Mar 2019 19:11:41 -0700
Message-ID: <CALx6S35bb5YpjR16OfQN+JJw3O3LG=NqkdFEnKdTEd3UoZWo5A@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005de20905846907ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/uQJDpx4-k8hIxEJnHq3HUr41XcU>
Subject: Re: [tsvwg] Alternative version of the UDP FRAG option
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Mar 2019 02:11:57 -0000

On Mon, Mar 18, 2019, 7:00 PM Joe Touch <touch@strayalpha.com> wrote:

>
> On 3/18/2019 6:33 PM, Tom Herbert wrote:
>
>
>
> On Mon, Mar 18, 2019, 5:32 PM Joe Touch <touch@strayalpha.com> wrote:
>
>> I'm trying to catch up with all the proposals and create a summary.
>>
>> That said:
>>
>> 1) the notion of soft state and its impact on the protocol is already
>> mentioned in the draft, as are its limitations
>>
>>
>> Joe,
>
> Is a normative description of UDP option negotiation forthcoming?
>
> We decided on soft state a while ago instead. That's already in the
> current descciption.
>
>
> 2) we definitely need to stick to some design principles. Some are
>> already proposed in the draft, but the discussion of late has strayed
>> far afield of those. In particular, the draft already has a list of
>> rules for when to drop packets based on various option properties.
>>
>
> But other existing standard protocols that have options already use a
> certain set design principles (like skip option bit in HBH and dest
> options). It's not clear to me at least why those aren't being followed.
>
> Because we're starting with "all options can be silently ignored" to
> support consistency with legacy receivers (at least until soft state is
> established) . That's NOT where other protocols start. There are several
> other places where we diverge (trailer, optional core checksum, etc.).
>

Then you can only send options that can be ignored. If the idea is that
soft state somehow allows sending of options that can't be ignored, that's
fine, but we need the normative description of how soft state works to
evaluate if the requirements are can be meant. This has to include edge
condition handling. UDP is stateless, so inferring connection state from a
5-tuple is perilous. For instance, after a NAT state eviction one side sees
an unchanged tuple, and the other side sees a completely new tuple and
might even be a different host thanks to VIP. How does soft state handle
that?

Joe
>