Re: [quicwg/base-drafts] Subsequent Initial Packets with Token Field (#1649)

Kazuho Oku <notifications@github.com> Mon, 13 August 2018 03:36 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 31D34130E66 for <quic-issues@ietfa.amsl.com>; Sun, 12 Aug 2018 20:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 ws9pAPCgBi08 for <quic-issues@ietfa.amsl.com>; Sun, 12 Aug 2018 20:36:33 -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 572C3130E65 for <quic-issues@ietf.org>; Sun, 12 Aug 2018 20:36:33 -0700 (PDT)
Date: Sun, 12 Aug 2018 20:36:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1534131392; bh=hRKSJBpQFDrhdKlI0ZmRymFLi1yMDT9zDpRN6aiiuZ0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y6LoqbLmVf8FamEgfJguSz+m3ZddQYQzItkolr03pc12aO94gJhihwgoLFKz8EIMN UgPa1AwrgOWK1JNvsBUFoFELDTuAw9gYXeQVywA5S2ft3KtSoqm7Aa11wUIjxw2WKH ksMEw3Jbm4shot4EiqRi6aPjGeUnKKCmcOn9v3os=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab94253426c3a0e3114afcef8627d1d4104ae7f0d092cf000000011788bec092a169ce14d6881b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1649/412400638@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1649@github.com>
References: <quicwg/base-drafts/issues/1649@github.com>
Subject: Re: [quicwg/base-drafts] Subsequent Initial Packets with Token Field (#1649)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b70fcc0402f6_68cf3fb0e52d45bc304878"; 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/v39R3ZyHxDx1yDieH_A7ix6m27A>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 13 Aug 2018 03:36:35 -0000

FWIW, my assumption has been that the token field will be empty for the subsequent Initial packets. 

IIRC, we have thought that it is possible to split Initial into two packet types (i.e. client's first flight and other obfuscated ones) even though we decided not to. The reason such split has been considered possible is because we have assumed that the token is only required for the client's first flight.

My understanding is that DDoS mitigation devices are required to remember the 5-tuple (or the CIDs) that are permitted to flow though, so that other types of packets (i.e., 0-rtt, handshake, 1-rtt) can be exchanged. Then, I do not see a reason why we need to include tokens in subsequent Initial packets.

-- 
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/1649#issuecomment-412400638