IETF Logo Mail Archive

[Unbearable] [TokenBinding/Internet-Drafts] Reconcile interactions between TBNEGO and TLS 1.3 (#98)

Nick Harper <notifications@github.com> Wed, 29 March 2017 22:24 UTC

Return-Path: <noreply@github.com>
X-Original-To: unbearable@ietfa.amsl.com
Delivered-To: unbearable@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCE8B126C0F for <unbearable@ietfa.amsl.com>; Wed, 29 Mar 2017 15:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.391
X-Spam-Level:
X-Spam-Status: No, score=-8.391 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-2.796, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 9lJ_-8qQN76d for <unbearable@ietfa.amsl.com>; Wed, 29 Mar 2017 15:24:42 -0700 (PDT)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext6.iad.github.net [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EA33126C23 for <unbearable@ietf.org>; Wed, 29 Mar 2017 15:24:42 -0700 (PDT)
Date: Wed, 29 Mar 2017 15:24:41 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1490826281; bh=ZuFREBGibbAhUwj9qKh0dTKVetZuGNmnb0/vBS3X5g4=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=IJ6XX28uneLpU/ndKFz3QuEsNv1hIbefS9IMqj2t5YiWliX+A51x7q0KGMtryz5KI oBelJhCbAPUnQSeQ/74Bgpsa5SiUVCxd3Cp5E0y8wkpM6JJOSR6SfBp5h+/tTJVYwV 4niLzeSrxy5w2aMnA8gLmAHHWPG9h9H8gCkRX3hc=
From: Nick Harper <notifications@github.com>
Reply-To: TokenBinding/Internet-Drafts <reply+011c274f5fe86f74a14b8e6114bf217f570a840f1d9d5de292cf0000000114f3f62992a169ce0cfed544@reply.github.com>
To: TokenBinding/Internet-Drafts <Internet-Drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <TokenBinding/Internet-Drafts/issues/98@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58dc34296365b_52333fb41d59dc2c785f1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nharper
X-GitHub-Recipient: unbearable-ML
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: unbearable@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/Z1epVOKg_GfgvzNUiL1r-DL-a60>
X-Mailman-Approved-At: Thu, 30 Mar 2017 08:45:32 -0700
Subject: [Unbearable] [TokenBinding/Internet-Drafts] Reconcile interactions between TBNEGO and TLS 1.3 (#98)
X-BeenThere: unbearable@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "\"This list is for discussion of proposals for doing better than bearer tokens \(e.g. HTTP cookies, OAuth tokens etc.\) for web applications. The specific goal is chartering a WG focused on preventing security token export and replay attacks.\"" <unbearable.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/unbearable>, <mailto:unbearable-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/unbearable/>
List-Post: <mailto:unbearable@ietf.org>
List-Help: <mailto:unbearable-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/unbearable>, <mailto:unbearable-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2017 22:24:45 -0000

(from https://mailarchive.ietf.org/arch/msg/unbearable/iA18qpvoIlFo9umezrC_Bhjk57M)

TLS 1.3 specifies that "Future extensions MUST define their interaction with 0-RTT."

I see two potential options to reconcile this disagreement:

1) Have TBNEGO specify something like "Token Binding and 0-RTT MUST NOT both be negotiated on the same connection" and let draft-ietf-tokbind-tls13-0rtt update TBNEGO later.
2) Specify in TBNEGO a max TLS version of 1.2, and have draft-ietf-tokbind-tls13-0rtt or another draft specify the behavior of the extension in TLS 1.3 and higher.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/TokenBinding/Internet-Drafts/issues/98

v2.23.0 | Report a Bug | By Email