Return-Path: X-Original-To: quic@ietfa.amsl.com Delivered-To: quic@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 989621201D8 for ; Fri, 7 Jun 2019 10:10:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.508 X-Spam-Level: X-Spam-Status: No, score=-17.508 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 uPiyRnOExj5N for ; Fri, 7 Jun 2019 10:09:59 -0700 (PDT) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 974E5120260 for ; Fri, 7 Jun 2019 10:09:58 -0700 (PDT) Received: by mail-wr1-x432.google.com with SMTP id b17so2871458wrq.11 for ; Fri, 07 Jun 2019 10:09:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yM7wXyy0URebvaxoBw4SIj6jFwqLIOrPNiNzfRSJYhk=; b=NJluh2KgPXLoQY1ICBKF9yi9ccdamqDfqNizF5kcdQvcOhGHtTZmsuBOm8VfVOo4IU O+8lBgRZxw3V/5SxU+qBA5GqGPsCx18+XdcSsePmKsYqVMa63XSrY3n0RxXmECgJMVUy uF9XD0uTX2Gcg98eYR+/LzhTnYkl66Egwr8OuEHk9jUXdjWcj4blXMU0qdNL1uszXlHm UmOQ2Ah+AfBfRMc4FVx6HL6ps4vHgPTl0vERm2iGj/4yYStL071tXJv4xxqb87VeAXpg +/vqSuirRL1GqeIRw6gGYI384MvLPcKVaADdUQoRYfa1nKO2p7n3t/DAr98KKZhopiUk xfAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yM7wXyy0URebvaxoBw4SIj6jFwqLIOrPNiNzfRSJYhk=; b=C/QyjzL6pOrsJ98eyOKQ5xFSlSsPHELY7ea2eBnepmhCHn4UxSn3FxvtdWpPJr75uD ddE/Dg7FAJFxSu9SZBcxca3K1oCnFPoCgSWo1hRgiHnjslKiwzCt+G7QVLDXjjz06mQc XGXxlEBWVBPFbTbEq18jXrDB+ezzJLSG9j3XjGAeY0gJnWPw999KzB82k5BQL1V2Rfcu oSjve8dZ6Iloy7h/M3XsHIAUZ0n15aOy88gYosByirnuoz2haiAICFCWP0Zx4Zm7Zzkw PoIVflmyTTENsedF86xJlJzqTkROjhQLMGNHd7Z0Ccnrdylx9wdxbgCaKELzvmphDo3f CIhA== X-Gm-Message-State: APjAAAVxAjY5ZhVkkeP/8Rx874xsSdKkS6gTwtfKwqxoz0BdkD2WvdsR oUWatsrM38cFaopl3PW1eSRSr9rCcOc5/B6b59jQuQ== X-Google-Smtp-Source: APXvYqzYFFdyRbLfjkFVVT+buBW9qjzlQ5ev3MCxbYXv7hgCCxAWL1dcE1yi0dVVJOoMGr+KffK4HF0gvtG6SdQKXA4= X-Received: by 2002:a5d:4a8d:: with SMTP id o13mr1690947wrq.350.1559927396523; Fri, 07 Jun 2019 10:09:56 -0700 (PDT) MIME-Version: 1.0 References: <39BCBB46-D35D-44F7-9069-A49BD8CA0C98@fb.com> In-Reply-To: <39BCBB46-D35D-44F7-9069-A49BD8CA0C98@fb.com> From: Ryan Hamilton Date: Fri, 7 Jun 2019 10:09:43 -0700 Message-ID: Subject: Re: Cookie crumbling in QPACK? To: Alan Frindell Cc: =?UTF-8?Q?Bence_B=C3=A9ky?= , "quic@ietf.org" Content-Type: multipart/alternative; boundary="00000000000058aabf058abee633" Archived-At: X-BeenThere: quic@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Main mailing list of the IETF QUIC working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jun 2019 17:10:11 -0000 --00000000000058aabf058abee633 Content-Type: text/plain; charset="UTF-8" On Fri, Jun 7, 2019 at 9:13 AM Alan Frindell wrote: > It should be as safe for QPACK as it is for HPACK. Since HTTP/2 went out > of the way to mention it in the draft, I suppose HTTP/3 should also? > Agreed. I think HTTP/3 should either mention it explicitly, or normatively reference 8.1.2.5. --00000000000058aabf058abee633 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Jun 7, 2019 at 9:13 AM = Alan Frindell <afrind@fb.com> wr= ote:

It should be as safe for QPACK as it is for HPACK.= =C2=A0 Since HTTP/2 went out of the way to mention it in the draft, I suppo= se HTTP/3 should also?


Agreed. I think HTTP/3 should either mention it explicitly, or norm= atively reference 8.1.2.5.

--00000000000058aabf058abee633--