IETF Logo Mail Archive

Re: [Add] What to do in this potential working group

Jari Arkko <jari.arkko@piuha.net> Tue, 20 August 2019 20:26 UTC

Return-Path: <jari.arkko@piuha.net>
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 90673120086 for <add@ietfa.amsl.com>; Tue, 20 Aug 2019 13:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 gFAdk4RVbKON for <add@ietfa.amsl.com>; Tue, 20 Aug 2019 13:26:00 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 31A5512001E for <add@ietf.org>; Tue, 20 Aug 2019 13:26:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7C50066026B; Tue, 20 Aug 2019 23:25:58 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96Z2t4W0xAWW; Tue, 20 Aug 2019 23:25:57 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 03522660118; Tue, 20 Aug 2019 23:25:56 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Message-Id: <CC96CEBC-0D1A-4E63-9E3E-AA80CCE9D8CE@piuha.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A06F248-6B71-42C6-BE50-BACB39D28C52"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 20 Aug 2019 23:25:56 +0300
In-Reply-To: <CAMOjQcFGVeHJx4O3dNMa2JSnNpiWPdhaEXxcQv=eJ6ig2C4vng@mail.gmail.com>
Cc: ADD Mailing list <add@ietf.org>
To: Eric Orth <ericorth@google.com>
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net> <CAMOjQcFGVeHJx4O3dNMa2JSnNpiWPdhaEXxcQv=eJ6ig2C4vng@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/7vhy1fA86WJrVlQcl6B_pS6LH3A>
Subject: Re: [Add] What to do in this potential working group
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: Tue, 20 Aug 2019 20:26:03 -0000

> * Recommendation that having devices or apps “call home” for every user action to a centralised global service is bad practice and should be avoided
> I think such a recommendation may need to be further scoped and nuanced.  For many specialized devices/apps, calling into a specific centralized service may be the entire user-obvious purpose of the device/app.

Yes, of course. (But for the record, I was thinking of only in terms of DNS. But even for that there may be cases where a specific centralised service is used by a specific gadget. I’m just reacting on general purpose Internet appliances and browser-type apps doing this.)

Jari

v2.23.0 | Report a Bug | By Email