IETF Logo Mail Archive

Re: New Version Notification for draft-bonaventure-quic-atsss-overview-00.txt

Lars Eggert <lars@eggert.org> Wed, 03 June 2020 06:48 UTC

Return-Path: <lars@eggert.org>
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 5B4CB3A0C1B for <quic@ietfa.amsl.com>; Tue, 2 Jun 2020 23:48:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 7CGkFt-YeuKe for <quic@ietfa.amsl.com>; Tue, 2 Jun 2020 23:48:56 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 5556C3A0C3C for <quic@ietf.org>; Tue, 2 Jun 2020 23:48:56 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:2546:2eeb:f496:7429] (unknown [IPv6:2a00:ac00:0:35:2546:2eeb:f496:7429]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 4018361CFF0; Wed, 3 Jun 2020 09:48:46 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1591166926; bh=Ae2SO3OliSPLq9xcfpe0sFGgs1HSEuz4vcI0znGWpYY=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=e/i2tLmZvO2Dev0kCXFYDOLPTnfypHMZZkVLGeOv7OytlkvuBx9YE0zLHkTc8S2NM V1l0i1/p3IB6xSMgg3t1rdcZssOiAx8qKpfyVT2varwQVE4QDy0qQotB4vTTXLd2mD iitDxlDAf+5joDaggMYA6pptCXNW4gnR3o98siGc=
From: Lars Eggert <lars@eggert.org>
Message-Id: <9F66D3B3-DBD6-44CE-80EA-0F46F3D1DB9A@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_201694B0-2654-4D5A-A319-ABBF7E0D353B"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: New Version Notification for draft-bonaventure-quic-atsss-overview-00.txt
Date: Wed, 03 Jun 2020 09:48:45 +0300
In-Reply-To: <e74e1342-4f54-679b-00f3-a2e2dc24c9d0@uclouvain.be>
Cc: Christian Huitema <huitema@huitema.net>, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>, Matt Joras <matt.joras@gmail.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
To: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
References: <159084638843.27466.7915766554130545967@ietfa.amsl.com> <CAKKJt-eHQtgjc-zuO7vrGZ1Q2c7=3hetOb0FyqnEmbTDu1Uwuw@mail.gmail.com> <CADdTf+iBRLu20OH-WTEmo=e7WZ8Ce5QVP+_LWO09u6LxjCPe2g@mail.gmail.com> <D2BBDD3C-89F7-43BF-B5C3-1EC5E8C69EBE@ericsson.com> <72be8104-e738-136f-d05c-285fc49533dc@huitema.net> <e74e1342-4f54-679b-00f3-a2e2dc24c9d0@uclouvain.be>
X-MailScanner-ID: 4018361CFF0.A70D7
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/oAAv_dHrGGEngbbIYAKxZDBd_7E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2020 06:48:57 -0000

Hi,

(hat off)

On 2020-6-3, at 9:41, Olivier Bonaventure <olivier.bonaventure@uclouvain.be> wrote:
> As an enduser, I have a contractual relationship with my network provider and this contract can include strong privacy protections. Using the ATSSS service of a provider that I trust and needs to obey to specific laws could be better from a privacy viewpoint.

so that's certainly debatable.

Apart from the privacy aspect though, tunneling all traffic through an operator proxy that would otherwise not be in the path certainly can have performance and management aspects. It's probably going to add delay due to route stretch and possibly queueing, and can limit throughput due to processing overheads or overload.

Lars

v2.23.0 | Report a Bug | By Email