[quicwg/base-drafts] The method of identifying "the same server" (#3155)

Kazuho Oku <notifications@github.com> Mon, 28 October 2019 04:08 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 62B021200D8 for <quic-issues@ietfa.amsl.com>; Sun, 27 Oct 2019 21:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 aZOn5LfLXmzm for <quic-issues@ietfa.amsl.com>; Sun, 27 Oct 2019 21:07:59 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 810BC120044 for <quic-issues@ietf.org>; Sun, 27 Oct 2019 21:07:59 -0700 (PDT)
Date: Sun, 27 Oct 2019 21:07:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1572235678; bh=uhCSsHP0KVTF9DIfGYq7686cEGwwLfsjFInlb+NyBcM=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=yoc7wUSDG8FSHxctsYsKVBI0d5uj/0ooFn4PAIGKC11CRqRs8z9LwHSEq+y3sgsLG sao8s+gULe87WZyU3kDlQ4XyuIFKmKbocU+p7z0N0gWiR7dAQcjkriLteWb35E3lmV wggxz4Ahl+ZLrKLnPaFg9lmPek8+/2fqBZLXha9U=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6L25FLPIW74WPGLPV3YOOB5EVBNHHB5FITQM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3155@github.com>
Subject: [quicwg/base-drafts] The method of identifying "the same server" (#3155)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db6699e90ae9_14283fcc26acd9601091d8"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/lwpXzLz-SS5yuJc1aldFKstUkQw>
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: Mon, 28 Oct 2019 04:08:02 -0000

At the moment, [section 8.1.2 of the transport draft](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#rfc.section.8.1.2) states that a resumption token can be used "_if the client has a token received in a NEW_TOKEN frame on a previous connection to what it believes to be the same server._"

But what does "the same server" actually mean?

Some possible answers include:

* a) the same server IP address
* b) the same server IP address and port
* c) any server name that was presented in the certificate provided in the previous connection (the scope of session tickets; see [RFC 8446; section 4.6.1]( https://tools.ietf.org/html/rfc8446#section-4.6.1))
* d) the same server-name
* e) the same server-name and ALPN (the scope of 0-RTT; see [RFC 8446; section 4.2.10](https://tools.ietf.org/html/rfc8446#section-4.2.10))

I'd presume it to be one of a, b, or c, but I think it'd be better to clarify what "the same server" actually means.

-- 
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/3155