Re: [Taps] How to handle Protocol stacks that are not equivalent
Max Franke <mfranke@inet.tu-berlin.de> Tue, 23 July 2019 21:56 UTC
Return-Path: <mfranke@inet.tu-berlin.de>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C72E1209B4 for <taps@ietfa.amsl.com>; Tue, 23 Jul 2019 14:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.478
X-Spam-Level:
X-Spam-Status: No, score=0.478 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, MISSING_MIMEOLE=1.899, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 C5_cjDJpQRz8 for <taps@ietfa.amsl.com>; Tue, 23 Jul 2019 14:56:28 -0700 (PDT)
Received: from mail.net.t-labs.tu-berlin.de (mail.net.t-labs.tu-berlin.de [130.149.152.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4FEDC120956 for <taps@ietf.org>; Tue, 23 Jul 2019 14:56:28 -0700 (PDT)
Received: from [172.16.150.129] (unknown [207.115.96.130]) by mail.net.t-labs.tu-berlin.de (Postfix) with ESMTPSA id 7BE7C20805; Tue, 23 Jul 2019 23:56:26 +0200 (CEST)
Date: Tue, 23 Jul 2019 17:56:22 -0400
Message-ID: <f8d01742-e729-4c42-9049-a2110a3a1991@email.android.com>
X-Android-Message-ID: <f8d01742-e729-4c42-9049-a2110a3a1991@email.android.com>
In-Reply-To: <958d4405-a636-7d60-1804-dc6951f2c873@inet.tu-berlin.de>
From: Max Franke <mfranke@inet.tu-berlin.de>
To: Theresa Enghardt <theresa@inet.tu-berlin.de>
Cc: taps@ietf.org
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/rHgGV0lmAUoJUlKxXwIJx5Y8Qqs>
Subject: Re: [Taps] How to handle Protocol stacks that are not equivalent
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2019 21:56:38 -0000
Hi, (trimmed Cc list)
On 23.07.19 16:53, Anna Brunström wrote:
Subject: Re: [Taps] How to handle Protocol stacks that are not equivalent
Yes, that's correct. My interpretation is that being in the candidate set already requires equivalence.
Same here, seems we all agree on this.
Agreed.
However, the equivalence question becomes way more interesting once you're adding security.
TLS 1.2 is not equivalent to TLS 1.3, therefore you can't race them, the Architecture clearly says so and I agree.
As the application probably never asked for any specific version -- What if our TCP stack only supports TLS 1.2 but our QUIC stack offers basically TLS 1.3? We always take the better version and then fall back in case this fails? But wouldn't that be racing?
I think this is also an interesting question for the Implementation draft.
Best,
Theresa
- [Taps] How to handle Protocol stacks that are not… Philipp S. Tiesel
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Gorry Fairhurst
- Re: [Taps] How to handle Protocol stacks that are… Theresa Enghardt
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Joe Touch
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Max Franke
- Re: [Taps] How to handle Protocol stacks that are… Joe Touch
- Re: [Taps] How to handle Protocol stacks that are… Tommy Pauly
- Re: [Taps] How to handle Protocol stacks that are… Anna Brunström
- Re: [Taps] How to handle Protocol stacks that are… Theresa Enghardt
- Re: [Taps] How to handle Protocol stacks that are… Max Franke
- Re: [Taps] How to handle Protocol stacks that are… Philipp S. Tiesel