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

"Martin Thomson" <mt@lowentropy.net> Fri, 10 May 2019 00:42 UTC

Return-Path: <mt@lowentropy.net>
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 564851200DF for <architecture-discuss@ietfa.amsl.com>; Thu, 9 May 2019 17:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=lowentropy.net header.b=QH8Sgcr9; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=N/8R4Bkd
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 lBrBo-u4HmNL for <architecture-discuss@ietfa.amsl.com>; Thu, 9 May 2019 17:42:17 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DD8B1200C4 for <architecture-discuss@ietf.org>; Thu, 9 May 2019 17:42:17 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 558C5452; Thu, 9 May 2019 20:42:16 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Thu, 09 May 2019 20:42:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=rUk7r1sxMFcTA/Ray/A5trNL8hQDbeu u2ebw2oXobtY=; b=QH8Sgcr9BNcLIAOswQ3hKB4SZxlin+/T/7FPI+pJ6vjWWdS KdcpGSkLOOYRv5S6EcKazXhtNTI4DpAFfRliQoOHknN9IAehaOk7NRcI5sRzFtv6 0WH5LLCzkqHJcNmE0ASBqI2b4STh9x7SeBk9+xFC+uhFyHcU3ahwozxaDif92I6Y zsvYHagJ4IEaUE6PkHVBqNfU4Ovt9YRo5qkYnntaXaYOCb7KHCCafOXUwZ16C3aD LdMN/IH05FazSH/+9sRjQCaXkDF5YZ+wccxWlGmYKw+/y8c7+lMKsVu1p/vP7Z79 Vh97SNkdHmVh94r/g9k/Pqtzp8d3PrKupkwfNjw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=rUk7r1 sxMFcTA/Ray/A5trNL8hQDbeuu2ebw2oXobtY=; b=N/8R4Bkd63hQoJFTeiWreH gK17fAttU4UwpqWxEW3NA0ZQl759vpKJ1PAdFQ55B73+1BJLsrsA5t2GO6AK9mUk LHzpDlKx6qmcLQfnrBUt6PqtPFWWel4LfYQtH3bQaaqPyIdtNaBjPER501lsUh9E kS3CV/tqIuOrfB9Fc1//VbbDacL0JJuHjVC9ytKeqUd1EhqKfNwtekrX2tQBtr39 jr4Md5gSg5EE420HoyAWPFm1aoDNjV6qXZtKjAKayF3ED7OgpLyZuf7QXinK4Au+ V3vEg4PKNEnHertTAXqx0gpFxR0vuASkNLYoeMlGRCavSUcm25HY9yls249JVVuQ ==
X-ME-Sender: <xms:58jUXLCvFjwumy0oL_ay99DNsrQLkSpSl13xjSLoOknveXAWqLsm8A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkeeigddugeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucffohhmrghinheprhhijhhkshhovhgvrhhhvghiug drnhhlpdhivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohif vghnthhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:58jUXK0adMCnIYOLc2hH0kxIj57dIJWDwet0uiF_qL1ZrPMllD6Myg> <xmx:58jUXFUUYE37ghRytomC0D-Vk3HUwCbsiVY0jDvnQsHSC_109XBy1Q> <xmx:58jUXIxWZrZ9orrsrM1wBrhx02yVX0sIodm3EJUHr1XHTJMe2yA4xA> <xmx:58jUXMEf7gXsC62hmvckgXG1F32nvwhMwOwWmd2rM5DMp4eMI7RREA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 79C157C54E; Thu, 9 May 2019 20:42:15 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-449-gfb3fc5a-fmstable-20190430v1
Mime-Version: 1.0
Message-Id: <f82841df-9401-4cc5-b099-f8bbdad5f4c9@www.fastmail.com>
In-Reply-To: <6.2.5.6.2.20190509031500.0d470278@elandnews.com>
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>
Date: Thu, 09 May 2019 20:42:17 -0400
From: Martin Thomson <mt@lowentropy.net>
To: S Moonesamy <sm+ietf@elandsys.com>, architecture-discuss@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/LBrgn9D1iWlnyDFwGKnQ8_H1S6c>
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 00:42:19 -0000

On Thu, May 9, 2019, at 21:09, S Moonesamy wrote:
> I'll illustrate the point as follows: we are talking with each other 
> as we both know where to have the discussion and with whom.  That is 
> not obvious to a person who has not participated in the development 
> of a protocol.  In essence, the document would have to stand on its 
> own if we are interested in document clarity.  There is a thread 
> about an erratum: 
> https://mailarchive.ietf.org/arch/msg/yam/MtuLDdVBbG4U2Schf-xDEwsXAt0 
> which might illustrate that point.

Yeah, that's a good example.  Everyone agrees that the spec is sub-optimal, but we have an overwhelming agreement that fixing it isn't what happens next.

But the conversation happened, and that's not so bad.
 
> 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.  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.