IETF Logo Mail Archive

Re: [Add] Proposed charter and BoF request for IETF 106

"Ralf Weber" <dns@fl1ger.de> Wed, 09 October 2019 15:57 UTC

Return-Path: <dns@fl1ger.de>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1FF3120121 for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 08:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 6OSRHgGabMWW for <add@ietfa.amsl.com>; Wed, 9 Oct 2019 08:57:27 -0700 (PDT)
Received: from smtp.guxx.net (smtp.guxx.net [IPv6:2a01:4f8:a0:322c::25:42]) by ietfa.amsl.com (Postfix) with ESMTP id 4E838120145 for <add@ietf.org>; Wed, 9 Oct 2019 08:57:22 -0700 (PDT)
Received: by nyx.guxx.net (Postfix, from userid 107) id BFE1B5F42AF9; Wed, 9 Oct 2019 17:57:20 +0200 (CEST)
Received: from [192.168.2.190] (p4FC210FD.dip0.t-ipconnect.de [79.194.16.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by nyx.guxx.net (Postfix) with ESMTPSA id 0DC4B5F40E4B; Wed, 9 Oct 2019 17:57:19 +0200 (CEST)
From: Ralf Weber <dns@fl1ger.de>
To: Eric Rescorla <ekr@rtfm.com>
Cc: chris.box@bt.com, ADD Mailing list <add@ietf.org>
Date: Wed, 09 Oct 2019 17:57:18 +0200
X-Mailer: MailMate (1.13r5655)
Message-ID: <1D2F035B-A34D-42E8-BBED-8DB962B04BE1@fl1ger.de>
In-Reply-To: <CABcZeBOnn7WOG3nz1XMP0jGux2gaYGgQskLoFzAvHift+teRtw@mail.gmail.com>
References: <CALaySJLxXVuHQNfTnaeKZ_R9xtBYWfbta+A1bWcE-ZQZwd3VZg@mail.gmail.com> <CABcZeBMkAFZW9mWjw92v+OR0Fa8ed+P80yc78eY07hCpsCNY6Q@mail.gmail.com> <LO2P123MB2256A416C25822B08BCCF9409B950@LO2P123MB2256.GBRP123.PROD.OUTLOOK.COM> <CABcZeBOnn7WOG3nz1XMP0jGux2gaYGgQskLoFzAvHift+teRtw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/1WY3xyeTuvQpwX-JYZ_IsyuNdF8>
Subject: Re: [Add] Proposed charter and BoF request for IETF 106
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Oct 2019 15:57:29 -0000

Moin!


On 9 Oct 2019, at 15:51, Eric Rescorla wrote:

> On Wed, Oct 9, 2019 at 6:36 AM <chris.box@bt.com> wrote:
>> Please point me to an operator that is arguing for the continuing of
>> NXDOMAIN monetisation.
>
>
> Arguing or not, it continues to happen, at least on T-mobile.
I assume you mean T-Mobile US as it is not happening for me at T-Mobile
in Germany.

But that aside Browsers are still monetising sending search results to
a search provider they choose when I enter something in the Omnibox that
most browsers today have. How is that different from ISP monetisation?

Now I don’t like both and wish we would not have these Omniboxes, but
instead an URL and search box with a possibility to choose a search
provider before my search and associated personal identifiable cookie
goes there.

So long
-Ralf

v2.23.0 | Report a Bug | By Email