Re: [Bimi] Laches
Dave Crocker <dhc@dcrocker.net> Wed, 03 April 2019 17:13 UTC
Return-Path: <dhc@dcrocker.net>
X-Original-To: bimi@ietfa.amsl.com
Delivered-To: bimi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61A51120135 for <bimi@ietfa.amsl.com>; Wed, 3 Apr 2019 10:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
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 ed6YSo0XsoRX for <bimi@ietfa.amsl.com>; Wed, 3 Apr 2019 10:13:08 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77053120128 for <bimi@ietf.org>; Wed, 3 Apr 2019 10:13:08 -0700 (PDT)
Received: from [192.168.1.85] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id x33HElTp027836 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 3 Apr 2019 10:14:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1554311688; bh=RJMahs/7HpIffw+WZGqvQ0LIR02bgUEt8SprZjhPpfI=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=ZuVYDyo/X/mV1a5L+5IR7i913SNuQG0nFq83P+eUoNrlIHiQpGY45saP0IQFhBVTh mN74ju3teHx5nbZIOWhQuCmmgscebCg/I2bmnujittXcfjJmzwuS+6GS57HFGkk9RU /Ci3nNqQXFSUtYtdwZuUYp6ucq0IYOvrH/zQECv8=
To: Wei Chuang <weihaw=40google.com@dmarc.ietf.org>, Richard Clayton <richard@highwayman.com>
Cc: bimi@ietf.org
References: <309EBD4AD64BE436663E721D@PSB> <CAAFsWK3uhFfeEt34wRJRQen1YVK4uNo=nxJoaGc4m84Y1J+ctQ@mail.gmail.com> <f4544345-bf26-a6fa-8697-e3b9e2ed8a51@dcrocker.net> <CAAFsWK1oQJzCG2HrwJDQVBp+cyaDCwMXpN51bZRcxb0Km9XTXQ@mail.gmail.com> <094f20b3-1c4f-b5e7-76f8-d683a4b3d991@dcrocker.net> <7v+NdwF3b4ocFAeC@highwayman.com> <CAAFsWK13BfC_9z2G1H76kY+97vfNTPcKY5mBm-=60KhurD1Mgw@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
Message-ID: <16adbb53-3f6f-f0f6-4e0d-cc77e3abda3f@dcrocker.net>
Date: Wed, 03 Apr 2019 10:12:56 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CAAFsWK13BfC_9z2G1H76kY+97vfNTPcKY5mBm-=60KhurD1Mgw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/ziFuSL9p950Jp4FdlPMfpcUXd5w>
Subject: Re: [Bimi] Laches
X-BeenThere: bimi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Brand Indicators for Message Identification <bimi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bimi>, <mailto:bimi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bimi/>
List-Post: <mailto:bimi@ietf.org>
List-Help: <mailto:bimi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bimi>, <mailto:bimi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2019 17:13:09 -0000
On 4/3/2019 10:02 AM, Wei Chuang wrote: > (IANAL) To be sure this topic is complex. We have ideas to your point > above but that's still in progress, and we hope to have more to share > soon. Your framing this around "laches" is new to us, and helpful feedback. Wei, Something like Bimi is easy to make work at small scale. And it doesn't need a standards effort. So the question for any Internet-scale standards effort is: What are the critical issues that need to be solved? For Bimi, I believe the challenge of making logo use 'validated' at scale is the primary, critical issue.(*) This was noted at the start of the Bimi effort, two years ago. That there is still no resolution is not surprising, but it adds to the concern about there pursuing Bimi components now, with the hope that this major scaling barrier will somehow get resolved 'soon'. Any effort to pursue Bimi-related standards needs to happen /after/ this long-standing legal, technical, and operational challenge has a viable proposal for solution. d/ (*) There are, of course, other concerns, such as the frankly tenuous premise that Bimi will drive authentication adoption by bulk senders on the also-thin possibility of more recipient logo-impressions. But as technical barriers go, logo 'validation' is easily dominant. -- Dave Crocker Brandenburg InternetWorking bbiw.net
- [Bimi] Today's BoF John C Klensin
- Re: [Bimi] Today's BoF Wei Chuang
- Re: [Bimi] Today's BoF Dave Crocker
- Re: [Bimi] Today's BoF Wei Chuang
- Re: [Bimi] Today's BoF Dave Crocker
- [Bimi] Laches (was: Today's BoF) Richard Clayton
- Re: [Bimi] Today's BoF John C Klensin
- Re: [Bimi] Today's BoF John Levine
- Re: [Bimi] Today's BoF John C Klensin
- Re: [Bimi] Today's BoF Wei Chuang
- Re: [Bimi] Today's BoF Wei Chuang
- Re: [Bimi] Today's BoF Wei Chuang
- Re: [Bimi] Today's BoF Richard Clayton
- Re: [Bimi] Laches (was: Today's BoF) Wei Chuang
- Re: [Bimi] Laches Dave Crocker
- Re: [Bimi] Laches John Levine
- Re: [Bimi] Laches Dave Crocker
- Re: [Bimi] Today's BoF Wei Chuang