Re: [Marnew] endpoint consent

Dirk Kutscher <Dirk.Kutscher@neclab.eu> Thu, 24 September 2015 11:44 UTC

Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: marnew@ietfa.amsl.com
Delivered-To: marnew@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4D331A903F for <marnew@ietfa.amsl.com>; Thu, 24 Sep 2015 04:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level:
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 1tmFXX_bsA3g for <marnew@ietfa.amsl.com>; Thu, 24 Sep 2015 04:44:06 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A037A1A907F for <marnew@iab.org>; Thu, 24 Sep 2015 04:44:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 1695310A9A1; Thu, 24 Sep 2015 13:44:05 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b24iHbjx61VY; Thu, 24 Sep 2015 13:44:05 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id F08B310A99E; Thu, 24 Sep 2015 13:43:58 +0200 (CEST)
Received: from HYDRA.office.hd ([169.254.4.236]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.03.0210.002; Thu, 24 Sep 2015 13:43:58 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: Jari Arkko <jari.arkko@piuha.net>, Aaron Falk <aaron.falk@gmail.com>
Thread-Topic: [Marnew] endpoint consent
Thread-Index: AQHQ9iulfdeS+psrpkeCAR2sFvwjJJ5K/WIAgACRGlA=
Date: Thu, 24 Sep 2015 11:43:58 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F52499A0987C9@Hydra.office.hd>
References: <1991284A-864D-45C0-A016-A64C8FA5F029@gmail.com> <09EC7D4E-0245-4019-9D20-F95CF2362845@piuha.net>
In-Reply-To: <09EC7D4E-0245-4019-9D20-F95CF2362845@piuha.net>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.7.0.205]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/marnew/IGxRs4NGg-n5tQ11XGfrYIAmqQo>
Cc: "marnew@iab.org" <marnew@iab.org>
Subject: Re: [Marnew] endpoint consent
X-BeenThere: marnew@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Managing Radio Networks in an Encrypted World <marnew.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/marnew>, <mailto:marnew-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/marnew/>
List-Post: <mailto:marnew@iab.org>
List-Help: <mailto:marnew-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/marnew>, <mailto:marnew-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2015 11:44:08 -0000

Fully agree.

Fine-grained control, being difficult to use correctly by endpoints, seems to boil down to in-network traffic classification.

IMO, a simpler model, with the right incentives for endpoint adaptability, is more likely to see successful deployment.

Regarding the trust discussion, I'd first like to see a list of necessary functions that need to be trusted. If it's just coarse-grained traffic management and perhaps caching, there is not that much explicit consent and trust needed.

Best regards,
DIrk


-----Original Message-----
From: Marnew [mailto:marnew-bounces@iab.org] On Behalf Of Jari Arkko
Sent: Donnerstag, 24. September 2015 06:58
To: Aaron Falk
Cc: marnew@iab.org
Subject: Re: [Marnew] endpoint consent

One challenge is of course that it is already difficult for the users (or even us experts) to understand all the exact things that are going on, so providing a useful control for the users even on bandwidth may not be easy.
Let alone more complex settings.

The other issue is that we should be careful about setting the ambition level.
Fine-grained quality of service treatment has not been successful in the Internet. What's the right ambition level, being able to specify detailed bandwidth consumption rules? Or the ability to differentiate interactive from the non-interactive within one user? The more coarse grained you make this, the more likely it is that it can be used by applications and understood by users.

Jari