IETF Logo Mail Archive

Re: [quicwg/base-drafts] Do Initial secrets change after Retry packet? (#2823)

Mike Bishop <notifications@github.com> Tue, 25 June 2019 18:13 UTC

Return-Path: <noreply@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 D16F2120B3F for <quic-issues@ietfa.amsl.com>; Tue, 25 Jun 2019 11:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 ZFBltLopfomc for <quic-issues@ietfa.amsl.com>; Tue, 25 Jun 2019 11:13:14 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 128F8120233 for <quic-issues@ietf.org>; Tue, 25 Jun 2019 11:13:14 -0700 (PDT)
Date: Tue, 25 Jun 2019 11:13:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1561486393; bh=LzqlqHR9DrUeiWHKQb2AXcaw/vQ+1oYp7eHm35hnwwo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zXCurwF5cnMSVwt/7avLL8gzb4qettVH+r6za/o07uLauhbSORVoSY8V5JFUxSLOC Dxh6ZouROz9fNccH3WjxcPS7WxAEr7ErMUm5jK91nDY9fAfYkc1G6LulFPkxmBrGwG UsmMVIZf5fkWNO+2imSC1hW8rX/3+OvViHVu0whQ=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK54KZJU4R6CGSGN7PF3D6LLTEVBNHHBWWQD7M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2823/505560244@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2823@github.com>
References: <quicwg/base-drafts/issues/2823@github.com>
Subject: Re: [quicwg/base-drafts] Do Initial secrets change after Retry packet? (#2823)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d12643916443_556d3fe57aacd95c2497dd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/KuHUbVEQgRC9K4MzxegkycPC_Og>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Jun 2019 18:13:16 -0000

This is already stated in a different section.  In [17.2.5](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#packet-retry), it says:

> A client sets the Destination Connection ID field of this Initial packet to the value from the Source Connection ID in the Retry packet. **Changing Destination Connection ID also results in a change to the keys used to protect the Initial packet.** It also sets the Token field to the token provided in the Retry. The client MUST NOT change the Source Connection ID because the server could include the connection ID as part of its token validation logic (see Section 8.1.3).

-- 
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/2823#issuecomment-505560244

v2.23.0 | Report a Bug | By Email