Re: [arch-d] Comments on draft-iab-protocol-maintenance-03

Ted Hardie <ted.ietf@gmail.com> Fri, 10 May 2019 16:25 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 557C91201E2 for <architecture-discuss@ietfa.amsl.com>; Fri, 10 May 2019 09:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 TTrW9s1p0Jmt for <architecture-discuss@ietfa.amsl.com>; Fri, 10 May 2019 09:25:26 -0700 (PDT)
Received: from mail-it1-x12a.google.com (mail-it1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 26B981201DC for <architecture-discuss@ietf.org>; Fri, 10 May 2019 09:25:26 -0700 (PDT)
Received: by mail-it1-x12a.google.com with SMTP id l7so10154343ite.2 for <architecture-discuss@ietf.org>; Fri, 10 May 2019 09:25:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Lgfxco6XNTn/FcsMnTl/NIWcVhQLH5obq4gC25vqogk=; b=est0So8yMujysuZNORZkQP8NvBKV0XM0w6gC7vXnsVt8OaXDKVr0CbsqOkkt/DIDFo GGhCIJmIJs0cPlnRH1IoBfuvAGpqgfPobfzdWf58Tko06VlWOwuzS/Nas1vU8sjpQkvl f9KAHRZ58n7UDzM/SBIjANDi1IQ/eDIUK7eJVPNKbbH8laru6N64OXAyN9SgwWAIAKqq b89686VoLV8ajHqIfNckIutTSEoR5pUOl1Lg9yyNwo95+DJ+p2eMuMMYi1ktj/hPhLTN xQ48Gi3MB+rnSTgOJervWbM/yyOZaPJDMhf/jMxJaYFBVltiSNvlccMRntB4RB4ITuTe 0mgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Lgfxco6XNTn/FcsMnTl/NIWcVhQLH5obq4gC25vqogk=; b=GLYOm0FKH6XyWZSkyhHuNSCWW+5KnUVQvjZz03EEbN1mr54CPHgzFf/dM4HAtbKQu3 xGRQfZOUTDATMRxX99uSVJpm+k0o7emdXPG1TR6pQhQZAVvddiaI0JUAj+1xGCCBlgtB 9TrYB7F3aW3DA43gX/7tgrPArLm5KTYwtoHjvfzbUZj/Es/nK/yJ4MRh8PEqspjnSUWB sgvN/94B30k5elQE7EPVpFN7OkX6mw1bGrshAm/bizPiYKFTG/hBReEyS2rNfiPJOL1Q GsLzAAUw7gxQSAqUAmfj3qHA+k5oda3E0+AOEbn9jq0tw+CSmN8bmevcxXlICz+aIDTJ eNGA==
X-Gm-Message-State: APjAAAUJlUl1Ae4D/NYo978qJBRsPL4kOyuKt+Dj3C3mwLn2lUEANeAK iJVx2A5G1iYFNsJCTr2rE9JtASHp+uFIpi058xeF0Z1K
X-Google-Smtp-Source: APXvYqziTBR+tM0GiIHIUBvPgJcrTd/SowsLs6vDjVAEc7q/Pc1ApA1ZOcXiE2OjQxkYxWp3h/sn2hFUGdasSp85nZ4=
X-Received: by 2002:a24:910b:: with SMTP id i11mr7885198ite.110.1557505525402; Fri, 10 May 2019 09:25:25 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190508160140.1003a8f0@elandnews.com> <d99f68a8-e200-4548-a2d5-1748341fd601@www.fastmail.com> <6.2.5.6.2.20190509031500.0d470278@elandnews.com> <f82841df-9401-4cc5-b099-f8bbdad5f4c9@www.fastmail.com>
In-Reply-To: <f82841df-9401-4cc5-b099-f8bbdad5f4c9@www.fastmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 10 May 2019 09:24:59 -0700
Message-ID: <CA+9kkMDiTJWpbkQkJV+p0XZmnjeb+RhOO6BwV00-1K6Hm5BmuQ@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: S Moonesamy <sm+ietf@elandsys.com>, architecture-discuss@ietf.org
Content-Type: multipart/alternative; boundary="00000000000093d2e705888b030d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/vK_BLRmlgvsEUSnn8_I6866cpj4>
Subject: Re: [arch-d] Comments on draft-iab-protocol-maintenance-03
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 16:25:28 -0000

On Thu, May 9, 2019 at 5:42 PM Martin Thomson <mt@lowentropy.net> wrote:

>
> > I am not keen on using telemetry (excluding the Mozilla case) as one
> > has to do a PIA.  There was a recent case about telemetry:
> >
> https://www.rijksoverheid.nl/documenten/rapporten/2018/11/07/data-protection-impact-assessment-op-microsoft-office
>
> We might have to disagree on that point.  There are very interesting
> questions about who gets to decide what is OK to collect, and how we manage
> the concerns of those involved.  Steve Bellovin just gave a great talk on
> the failure of "notice and consent" to the IAB that I hope we'll be able to
> get in front of the community; that's clearly not the answer.


It's now up on Steve's website:

https://www.cs.columbia.edu/~smb/talks/iab-privacy.pdf



>   But we're veering well off into the weeds when we get there.
>
> > There was a comment in that submission about interoperability.
>
> Yes, there was.  Several.
>
>