Re: [Bimi] Logo/Trademark conflict

Dave Crocker <dhc@dcrocker.net> Wed, 10 April 2019 19:00 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 5ACC412041E for <bimi@ietfa.amsl.com>; Wed, 10 Apr 2019 12:00:28 -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 (1024-bit key) 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 5Tu2vl-F6pkz for <bimi@ietfa.amsl.com>; Wed, 10 Apr 2019 12:00:27 -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 087611205FF for <bimi@ietf.org>; Wed, 10 Apr 2019 12:00:27 -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 x3AJ2Cla002213 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 10 Apr 2019 12:02:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1554922932; bh=mn3x+exf2TxhEv91MC1CbSg+vjsI0zn5L0NapbpzRXw=; h=Subject:To:Cc:References:Reply-To:From:Date:In-Reply-To:From; b=l1VYtcYx1dw+wr2F9m+EwRCEOxSu59EXz6LV9e0z96KzIdn+w/Romtl7iIr+9s2P8 KR6isvIH48PVN1kvOm6zw2ZL9NAwGCVIHPpc3A5BuduvpBuHsc4CzIymy8iW+cHdG3 3dSw/0uqKtO2ivYQOBVvzCSplNw4+ajrjANWw2HA=
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>
Cc: bimi@ietf.org
References: <54c335ec-d4a7-d842-1d72-af5a5ec8df43@dcrocker.net> <CAOZAAfMVp+jit7raDqP0vnz-AtU6J4igZsJY+0rt5MjZivEE_g@mail.gmail.com> <5f5663ae-149b-59f8-efd7-42864f6643d9@dcrocker.net> <CAOZAAfNyQQ99MT7xKgZT=LJjSF-kxezn-7ZzW1Ac1EFSu-dj1A@mail.gmail.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5b941325-70fe-efbf-2357-3c2f8b668f01@dcrocker.net>
Date: Wed, 10 Apr 2019 12:00:17 -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: <CAOZAAfNyQQ99MT7xKgZT=LJjSF-kxezn-7ZzW1Ac1EFSu-dj1A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/UUW6688Opd53Jk8y8GVOcmqScUw>
Subject: Re: [Bimi] Logo/Trademark conflict
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, 10 Apr 2019 19:00:36 -0000

On 4/10/2019 9:30 AM, Seth Blank wrote:
> We went through these issues in detail at the BoF and discussed our 
> starting point for addressing them, which we agree doesn't cover use 
> cases at scale.

IMO, unless and until there are use cases for this working at scale, the 
effort won't work at scale.  It might not work then, either, but this at 
least is a foundational requirement for serious discussions.


 > What is your suggestion for addressing these issues?

Besides advising that there be serious discussions that start with a 
robust characterization of the problem space for working at scale, I've 
no idea how to 'solve' this.  Given at least 120 years of discussion in 
this space, it's unlikely anyone else does, either.

Problems with such discouraging histories sometimes do get solved.  But 
never by ignoring the challenges they post.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net