IETF Logo Mail Archive

Re: [quicwg/base-drafts] address-based access control (#2279)

ianswett <notifications@github.com> Sat, 05 January 2019 02:15 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 145E112F1AB for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 18:15:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level:
X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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, 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 8NUmU4fYAYMH for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 18:15:40 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CBED12D4E9 for <quic-issues@ietf.org>; Fri, 4 Jan 2019 18:15:40 -0800 (PST)
Date: Fri, 04 Jan 2019 18:15:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546654539; bh=03nFX8fMI2l/chDh9lGZjzWRRlW7nYB9DrJVuhrrvWc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SZlXqEyZkk14/Z/+DxZkqkuVKY/04NK7rzvTTcmM9y2P8J+MIPRy9PhVbFTccTo+T weIKLlHutT1bmSnOrZZxfL/mFEqd1Id/0n65+Vf+qnUfbqtq5n+tvw9C5hMfcsXDzU o3oF4gchmg4C2quHlkzjh1kdcW5sDlo/VJjVLsdY=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab632a58369cd0a0967923aa3cbb7f59689fc9f3a192cf000000011847d54b92a169ce178a34b7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2279/451619694@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2279@github.com>
References: <quicwg/base-drafts/issues/2279@github.com>
Subject: Re: [quicwg/base-drafts] address-based access control (#2279)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c30134b6c60b_26ea3f99300d45b82055de"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/XftVZuCH6DvO-nyx0YGdBmM4_1M>
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: Sat, 05 Jan 2019 02:15:42 -0000

Agreed, if you're doing IP based ACLing, disabling connection migration seems wise.

Otherwise, there's nothing the client can do and the server has to set it's own policy.  Applicability seems like a fine place for this.

-- 
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/2279#issuecomment-451619694

v2.23.0 | Report a Bug | By Email