Re: [quicwg/base-drafts] Pad path validation in both directions (#4241)
Christian Huitema <notifications@github.com> Tue, 20 October 2020 19:31 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 4DAF53A1371 for <quic-issues@ietfa.amsl.com>; Tue, 20 Oct 2020 12:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 KngxCIcBxCju for <quic-issues@ietfa.amsl.com>; Tue, 20 Oct 2020 12:31:46 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 515EA3A13A3 for <quic-issues@ietf.org>; Tue, 20 Oct 2020 12:31:45 -0700 (PDT)
Received: from github.com (hubbernetes-node-f674994.ac4-iad.github.net [10.52.122.35]) by smtp.github.com (Postfix) with ESMTPA id 9D826600E8B for <quic-issues@ietf.org>; Tue, 20 Oct 2020 12:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1603222304; bh=lQAIezhzuxS/Be84MriWop5CRV8Y6AAbgLB/OCpkqMo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rLJ6MahyVnT8Vw+evloupDo3mF9JOD6zj36hguA2LsdTZHWIJVdpQ4Hu8oQ4f3FdT hA626TqZ8G0hQKN7iMy5dSY+aG+qEeVvC1OzVDnv4ppOF47h5QJ6o+BFHoU0ccqICz JgW8QGMiDZHoC9GBuH9xiNPGCm6Dwyo5kEvpM4xo=
Date: Tue, 20 Oct 2020 12:31:44 -0700
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZAKE3BYQLNUZQG4E55TMOCBEVBNHHCWKQC3Q@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4241/c713089937@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4241@github.com>
References: <quicwg/base-drafts/pull/4241@github.com>
Subject: Re: [quicwg/base-drafts] Pad path validation in both directions (#4241)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f8f3b2099ae3_3b19b48919e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/H3n-Qwfzl9w_QWaxj_aIu6fHpPM>
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, 20 Oct 2020 19:31:53 -0000
@janaiyengar By symmetry, I mean the assumption that the pair of source and destination addresses and ports used by the server is exactly the symmetric of the pair used by the client. This is not a completely natural assumption in QUIC, because peers are able to process packets received from any address and port, as long as the crypto works out. -- 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/pull/4241#issuecomment-713089937
- [quicwg/base-drafts] Pad path validation in both … Martin Thomson
- Re: [quicwg/base-drafts] Pad path validation in b… ianswett
- Re: [quicwg/base-drafts] Pad path validation in b… Martin Thomson
- Re: [quicwg/base-drafts] Pad path validation in b… Martin Thomson
- Re: [quicwg/base-drafts] Pad path validation in b… Martin Thomson
- Re: [quicwg/base-drafts] Pad path validation in b… ianswett
- Re: [quicwg/base-drafts] Pad path validation in b… Jana Iyengar
- Re: [quicwg/base-drafts] Pad path validation in b… ianswett
- Re: [quicwg/base-drafts] Pad path validation in b… Martin Thomson
- Re: [quicwg/base-drafts] Pad path validation in b… Martin Thomson
- Re: [quicwg/base-drafts] Pad path validation in b… Kazuho Oku
- Re: [quicwg/base-drafts] Pad path validation in b… Jana Iyengar
- Re: [quicwg/base-drafts] Pad path validation in b… Martin Thomson
- Re: [quicwg/base-drafts] Pad path validation in b… Magnus Westerlund
- Re: [quicwg/base-drafts] Pad path validation in b… ianswett
- Re: [quicwg/base-drafts] Pad path validation in b… mirjak
- Re: [quicwg/base-drafts] Pad path validation in b… Christian Huitema
- Re: [quicwg/base-drafts] Pad path validation in b… Jana Iyengar
- Re: [quicwg/base-drafts] Pad path validation in b… ianswett
- Re: [quicwg/base-drafts] Pad path validation in b… Jana Iyengar
- Re: [quicwg/base-drafts] Pad path validation in b… Christian Huitema
- Re: [quicwg/base-drafts] Pad path validation in b… Jana Iyengar
- Re: [quicwg/base-drafts] Pad path validation in b… Jana Iyengar
- Re: [quicwg/base-drafts] Pad path validation in b… Jana Iyengar