IETF Logo Mail Archive

Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)

Christian Huitema <notifications@github.com> Wed, 26 June 2019 03:20 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 C61B212060E for <quic-issues@ietfa.amsl.com>; Tue, 25 Jun 2019 20:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.383
X-Spam-Level:
X-Spam-Status: No, score=-6.383 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] 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 iLNBDJEuN2Rh for <quic-issues@ietfa.amsl.com>; Tue, 25 Jun 2019 20:20:09 -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 CF3E412002F for <quic-issues@ietf.org>; Tue, 25 Jun 2019 20:20:08 -0700 (PDT)
Date: Tue, 25 Jun 2019 20:20:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1561519207; bh=OtJw2KJRE4UDbtzHcGRCtrelfSSsOCUlfXX7JHJxmP0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Vjwx7Lb2VgVwnUwy1ytvAoc7rR2jx6U/MNax73UdCIMlVhPpcnJHlKHyv+/IimFQV d3oj2E2M7B/hX0j6i969rFLj1EjohF26YikI28DHZjBuohUlZwXfUWfhhJh78CIOE8 dz/DxbWOgeJEtLJqD/Wx6Bqno01bb4rgO3IGyJQ8=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6K7F6A2232C7HERNV3EALOPEVBNHHBW5BWIY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2844/505701424@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2844@github.com>
References: <quicwg/base-drafts/issues/2844@github.com>
Subject: Re: [quicwg/base-drafts] Client connection IDs are broken (#2844)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d12e46732329_7f43fd3de2cd96c2495e2"; 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/XyejX5Wcu__7D8qUzqvpU2hFfRY>
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: Wed, 26 Jun 2019 03:20:11 -0000

@DavidSchinazi Got it, OK. Server should not assume that client connections would always come from different 5 tuples, because in the case of proxies they will not. For example, two clients coming through the same proxy will appear to come from the same IP and port.

This is not a problem for clients, because clients can decide whether or not to send several outgoing connections through the same port.

-- 
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/2844#issuecomment-505701424

v2.23.0 | Report a Bug | By Email