Re: [tsvwg] UDP Options: on forcing the use of UDP CS=0 in connection with FRAG+LITE

"C. M. Heard" <heard@pobox.com> Mon, 01 July 2019 19:16 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 EB1CF120170 for <tsvwg@ietfa.amsl.com>; Mon, 1 Jul 2019 12:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, SPF_HELO_NONE=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 clMtiyA83R4v for <tsvwg@ietfa.amsl.com>; Mon, 1 Jul 2019 12:16:14 -0700 (PDT)
Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CF98120169 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 12:16:14 -0700 (PDT)
Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 04B9814B2D4 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 15:16:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=sasl; bh=xFO/TiEAyBoJSVZcrcQxYSQzn6o=; b=IXUeML /bhnHRIaUU8EgW/CxttO7px4eYBWf6qxzAPXyfLUBb+0FxNL28AVWY9g4yc9Zp+E oUDByIuPo4aVtshahJYGlA6XO5+fUWnyE06d0lWxypKCm+jbA3xQnAFWTdM86tsX T+BJV/NJHdhIrx/7iHmGtCQM4IlbJAw9dKs+U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; q=dns; s=sasl; b=iS35BmT9gGPwOB/hVkCZVUv13ixYNet0 iUZxYaPpvYFdZ+pqDPuA3yRWCYazbpGzdujdtRiMmRISfHRD0DOgpzWQJFH7Qvt1 9dwx/Rhf68wLCSAawGsYFuN538l7ZQ+luDNulCPLuDp95+W/wcGo7EY1pPRRD91G 0xsEqj/als8=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id F098514B2D2 for <tsvwg@ietf.org>; Mon, 1 Jul 2019 15:16:12 -0400 (EDT)
Received: from mail-io1-f50.google.com (unknown [209.85.166.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 7CAA214B2CF for <tsvwg@ietf.org>; Mon, 1 Jul 2019 15:16:12 -0400 (EDT)
Received: by mail-io1-f50.google.com with SMTP id n5so31336033ioc.7 for <tsvwg@ietf.org>; Mon, 01 Jul 2019 12:16:12 -0700 (PDT)
X-Gm-Message-State: APjAAAU8kKz+vnIjN1UeTN6M02GOQHtLxeGQKCoepuKy9VianWWUKHTU zbQNT3yEIXNgROQOkOdjEMYHouguFrG9IQmTKDc=
X-Google-Smtp-Source: APXvYqw6QoBIyl+P8DipiII6mdWbUVathTK/SS6S22XjKKX20F+KY6Nkhxo4Ln9/J2aK4Dc4AZCaBnLvo0x5WXw5bnM=
X-Received: by 2002:a02:c7c9:: with SMTP id s9mr30114272jao.82.1562008572012; Mon, 01 Jul 2019 12:16:12 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VHGtMz3htgfFLRGhjXm=qC7kOXQs+cchtamhh-giBnpLA@mail.gmail.com> <CALx6S35T9ApzMaoSVgHSJPpcpfXsbHHogoBbEjMPj6vH-kxYeA@mail.gmail.com> <CACL_3VE6kr33Vk5si5AxSZNmhqysZZGoy6HK37COUgwbvcRkdA@mail.gmail.com> <24692A9B-4AF1-4E32-A760-7D4908A61262@strayalpha.com>
In-Reply-To: <24692A9B-4AF1-4E32-A760-7D4908A61262@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Mon, 01 Jul 2019 12:16:00 -0700
X-Gmail-Original-Message-ID: <CACL_3VExhAdFCu-kFLLO5DeRYUOFyJztUgJg-vQmnPoecvzeJg@mail.gmail.com>
Message-ID: <CACL_3VExhAdFCu-kFLLO5DeRYUOFyJztUgJg-vQmnPoecvzeJg@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: Tom Herbert <tom@herbertland.com>, TSVWG <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-Pobox-Relay-ID: B084F582-9C34-11E9-A154-46F8B7964D18-06080547!pb-smtp1.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/7LWL7Wv1XSl4zQnosl1Ij9PMUEc>
Subject: Re: [tsvwg] UDP Options: on forcing the use of UDP CS=0 in connection with FRAG+LITE
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: Mon, 01 Jul 2019 19:16:17 -0000

On Sat, Jun 29, 2019 at 7:58 AM Joe Touch wrote:
>
> See sec 8.1, which incorporates rfc 6936:
>
>          As an exception to the default behavior, protocols that use UDP
>          as a tunnel encapsulation may enable zero-checksum mode for a
>          specific port (or set of ports) for sending and/or receiving.
>          Any node implementing zero-checksum mode must follow the
>          requirements specified in "Applicability Statement for the Use
>          of IPv6 UDP Datagrams with Zero Checksums" [RFC6936].
>
> Frag is a kind of such a tunnel because it adds its own reassembly CS.

I'll agree that FRAG+LITE with UDP CS=0 does conform to the requirements
in RFC 6936 Sections 4 and 5 because it includes a reassembly CS.

> But that also means middleboxes should allow relaying these since 6936
> was passed.

Yes. middleboxes are ***supposed*** to do that. But the empirical data
that we have says that in a significant number of cases (affecting 26%-36%
of the paths) they do not.

It's possible that the situation will improve in the future, but given
that it has not improved enough to make UDP CS=0 useable in other than
controlled environments, I don't think it's a good idea to propose its
use when we have an alternative that avoid UDP CS=0 that is no more
complex to implement.

Mike Heard