IETF Logo Mail Archive

Re: [TLS] DTLS 1.3

Nikos Mavrogiannopoulos <nmav@redhat.com> Tue, 05 July 2016 13:49 UTC

Return-Path: <nmavrogi@redhat.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35A6612D550 for <tls@ietfa.amsl.com>; Tue, 5 Jul 2016 06:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.842
X-Spam-Level:
X-Spam-Status: No, score=-6.842 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506] 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 jBvl5UvZBbkM for <tls@ietfa.amsl.com>; Tue, 5 Jul 2016 06:49:49 -0700 (PDT)
Received: from mx3-phx2.redhat.com (mx3-phx2.redhat.com [209.132.183.24]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDDBD12D534 for <tls@ietf.org>; Tue, 5 Jul 2016 06:49:48 -0700 (PDT)
Received: from zmail22.collab.prod.int.phx2.redhat.com (zmail22.collab.prod.int.phx2.redhat.com [10.5.83.26]) by mx3-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id u65DngVc017845; Tue, 5 Jul 2016 09:49:43 -0400
Date: Tue, 05 Jul 2016 09:49:42 -0400
From: Nikos Mavrogiannopoulos <nmav@redhat.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <367617282.2740434.1467726582647.JavaMail.zimbra@redhat.com>
In-Reply-To: <577AD00E.1000103@cs.tcd.ie>
References: <577A38A2.2090209@gmx.net> <17444145.2646138.1467662059329.JavaMail.zimbra@redhat.com> <577AD00E.1000103@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.36.6.111]
X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF47 (Linux)/8.0.6_GA_5922)
Thread-Topic: DTLS 1.3
Thread-Index: hwiR+/ROjGrMljGLLw8CO14IYEcFvw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/vOU84Kx0rhTfo12PJTkHDf3PbzY>
Cc: tls <tls@ietf.org>
Subject: Re: [TLS] DTLS 1.3
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2016 13:49:50 -0000

----- Original Message -----
> On 04/07/16 20:54, Nikos Mavrogiannopoulos wrote:
> > 
> > where id is sent by the server to the client either via an extension, or
> > by simply assuming that the client will copy and keep the ID seen at the
> > server packets (it doesn't really matter that this ID is unprotected as
> > it doesn't contribute nor affect the security in any way).
> 
> Does that id need to be static? If so, then it'd act as an
> additional way to track a user roaming over different IP and
> ports. That'd be a pity. If such an id is useful, maybe there's
> a way to allow it to change as well, in a way predictable for
> the server.

Could be, but I don't have a use case for such a switch nor can think something
obvious, what do you have in mind?

regards,
Nikos

v2.23.0 | Report a Bug | By Email