[quicwg/base-drafts] Re-use of PSK (#222)
ekr <notifications@github.com> Wed, 25 January 2017 00:42 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41EB21295E6 for <quic-issues@ietfa.amsl.com>; Tue, 24 Jan 2017 16:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.037
X-Spam-Level:
X-Spam-Status: No, score=-7.037 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-1.156, RP_MATCHES_RCVD=-3.199, SPF_PASS=-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 KwgrHlsm3bLa for <quic-issues@ietfa.amsl.com>; Tue, 24 Jan 2017 16:42:06 -0800 (PST)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BB4C1295DE for <quic-issues@ietf.org>; Tue, 24 Jan 2017 16:42:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=VDPJhq5qTklL/JDlSMLO2uYhAXI=; b=mi64qa7q/15ByVXK AoRRA4NNjC+9J/jFask24auWPhb7V5yXNgnpVtCTbMYZa097rFKkYCT4WEcrqcWI tbhSYDhBB1ghZLd84znFSCFFulf+mMfZu7BurehsHu7WIzbl68cZAAnyaTTFtnwa teHU2scLREFtPJ1ZNIBt3nNZjnk=
Received: by filter0498p1mdw1.sendgrid.net with SMTP id filter0498p1mdw1-28781-5887F455-10 2017-01-25 00:41:57.279707113 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id gobleUjBTpuhuxy78WJ6sA for <quic-issues@ietf.org>; Wed, 25 Jan 2017 00:41:57.281 +0000 (UTC)
Date: Tue, 24 Jan 2017 16:41:57 -0800
From: ekr <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/222@github.com>
Subject: [quicwg/base-drafts] Re-use of PSK (#222)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5887f45531bf9_6a733fb4847b7140142247"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2OlBPjmjnEncNFjm2g7KX/k1v0WXW2vy1G4T EFoe3HqtfnyX/lceNlqzG2mIhCgmHuXZgT449Uj1eFndCPMety3bwOzrNwXf/Ddgj+eLlkww5iUw8s q9fUEH9j0B7RVna/oeZpBjLrUY/yFhR1u7eavohxPegv9+g8flujnWYxPA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/p_edAk6Z7F8uahip2K7h_XV5GW0>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jan 2017 00:42:08 -0000
S 8.3 says: ``` A source address token is opaque and consumed only by the server. Therefore it can be included in the TLS 1.3 pre-shared key identifier for 0-RTT handshakes. Servers that use 0-RTT are advised to provide new pre-shared key identifiers after every handshake to avoid linkability of connections by passive observers. Clients MUST use a new pre-shared key identifier for every connection that they initiate; if no pre-shared key identifier is available, then resumption is not possible. ``` This seem like an unnecessary requirement. Reusing the same PSK ID seems fine here. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/222