Re: [tsvwg] Regarding DTLS and UDP options

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 17 April 2017 09:00 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 D1D86129B10 for <tsvwg@ietfa.amsl.com>; Mon, 17 Apr 2017 02:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level:
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 PETxiAVfOTdz for <tsvwg@ietfa.amsl.com>; Mon, 17 Apr 2017 02:00:13 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 21C09129AF4 for <tsvwg@ietf.org>; Mon, 17 Apr 2017 02:00:12 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 769381B0174B; Mon, 17 Apr 2017 11:55:30 +0100 (BST)
Message-ID: <58F48403.8080302@erg.abdn.ac.uk>
Date: Mon, 17 Apr 2017 09:59:47 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
CC: tsvwg <tsvwg@ietf.org>
References: <CACL_3VFeJs7KzG9Bchh15bfZ3CmaOPWcfisEreNoGYK5CsEJ+g@mail.gmail.com> <3a4a6b78-8146-de4c-6246-7bd09de44f1c@isi.edu> <CACL_3VFkr3mGe-yTbvHrTZcKVCpEv3FeSOyoShUxCK5+9Tdqqg@mail.gmail.com> <c79fe3d0-8567-ea7d-72fc-bd33732df60e@isi.edu> <CACL_3VHmoCSo23OWqQFq7upw749CqMK7iazXrBKZARzwbzY5mw@mail.gmail.com> <f97f08d4-0070-437a-e22a-8782497c76eb@isi.edu> <4e36af95-84c3-bc7e-b18a-614f8bfab662@isi.edu>
In-Reply-To: <4e36af95-84c3-bc7e-b18a-614f8bfab662@isi.edu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/f3nRTCzdEVltNr7axs9w5RObs70>
Subject: Re: [tsvwg] Regarding DTLS and UDP options
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
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, 17 Apr 2017 09:00:16 -0000

Thanks Joe,

That seems to be exactly the question the WG asked to explore. I agree 
your next update should add a small susbsection on how DTLS should be 
handled.

Gorry

On 15/04/2017, 00:56, Joe Touch wrote:
> Hi, all,
>
> Christian Huitema a question about the interaction between DTLS and UDP
> options during my remote presentation at IETF 98.
>
> I took a closer look and consulted with Eric Rescorla (DTLS author). He
> and I agreed as follows:
> - DTLS would currently not cover UDP options; DTLS protects only the UDP
> payload
> - the situation is analogous to TCP options, which are not covered by TLS
> I.e., both TLS and DTLS are transport *payload* security only, despite
> their names.
>
> Christian noted that this may be a reason QUIC prefers UDP (to avoid the
> need to protection transport options), however QUIC does not (and
> cannot) deprecate UDP payloads that are smaller than the IP payload.
> That would require a change to RFC 768.
>
> I'll add a clarification on this point to the next rev of the UDP
> options document.
>
> Joe