[Diem] Re: Some high-level thoughts on scoping

Serge Droz <serge@drozilla.ch> Mon, 01 July 2024 16:48 UTC

Return-Path: <prvs=09126670d1=serge@drozilla.ch>
X-Original-To: diem@ietfa.amsl.com
Delivered-To: diem@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ACB4C1930B6 for <diem@ietfa.amsl.com>; Mon, 1 Jul 2024 09:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drozilla.ch
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AN73F23-HQfj for <diem@ietfa.amsl.com>; Mon, 1 Jul 2024 09:47:59 -0700 (PDT)
Received: from phoenix.tux4all.net (phoenix.tux4all.net [IPv6:2a01:4f8:171:286f::4]) (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 AF343C180B60 for <diem@ietf.org>; Mon, 1 Jul 2024 09:47:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=drozilla.ch ; s=phoenix; h=In-Reply-To:From:References:To:Subject:MIME-Version:Date: Message-ID:Content-Type:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=TweXfyouiDwTZ/3MUDfXkAvoAyXQPaJDBojOZI1C5F8=; b=vS01TrbXtoekNkty+mHdVgHrZh dfv3KmamrY12naSN7OdmyTFrFfECosxKOFms8ADrSk3uTt/gCe8lVLlmidkqbRVU1vvixoS0k1n2E ncz3r1neAIaAxbPkuVW59nmNIq6MUZjyFOdvOTAjY2wbkRCJ0FRpJ3JKhJnTU16xzN1o=;
Received: from mob-194-230-147-232.cgn.sunrise.net ([194.230.147.232] helo=[192.168.95.150]) by phoenix.tux4all.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from <serge@drozilla.ch>) id 1sOKC4-00000000186-2J5v for diem@ietf.org; Mon, 01 Jul 2024 18:47:57 +0200
Content-Type: multipart/alternative; boundary="------------iflCsDA7dcfa0xYZEgc425z2"
Message-ID: <63695cad-7e54-42f5-850c-cb9a4fac353f@drozilla.ch>
Date: Mon, 01 Jul 2024 18:47:35 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: diem@ietf.org
References: <CABcZeBNxiUuXRykDSZ8rZ64JNKUgO76Ztdd7JwQv-RTqMgyDQg@mail.gmail.com> <A56BB152-A05F-45DE-B434-68339C08DB5A@pch.net> <6acc90a3-d66a-41cb-a33e-ebc4ecf4310d@dennis-jackson.uk>
Content-Language: en-US
From: Serge Droz <serge@drozilla.ch>
In-Reply-To: <6acc90a3-d66a-41cb-a33e-ebc4ecf4310d@dennis-jackson.uk>
Message-ID-Hash: WWWPD5WZUNSCSHAG6G26QHJ56U4ZKAJY
X-Message-ID-Hash: WWWPD5WZUNSCSHAG6G26QHJ56U4ZKAJY
X-MailFrom: prvs=09126670d1=serge@drozilla.ch
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Diem] Re: Some high-level thoughts on scoping
List-Id: Discussion of digital emblems <diem.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/diem/c789MpdZwm_x4mBKip4hcsoi-2U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/diem>
List-Help: <mailto:diem-request@ietf.org?subject=help>
List-Owner: <mailto:diem-owner@ietf.org>
List-Post: <mailto:diem@ietf.org>
List-Subscribe: <mailto:diem-join@ietf.org>
List-Unsubscribe: <mailto:diem-leave@ietf.org>

Hi Dennis


I think what Bill tries to say is, that there are many more emblems than 
the ICRC one.

Ideally you have a standard that allows you produce an Emblem for the 
use case at hand, so you can use the same tech to read an ICRC emblem as 
you can use to read e.g. an emblem designating a nuclera facility or a 
piece of art.

But yes, there are many parties that should be able to read an ICRC 
emblem, or any other one. But we want to avoid a situation where a 
standard is defined that covers only the requirements of one stakeholder.

  So I don´t think there is a contradiction.

Best

Serge


On 01/07/2024 18:40, Dennis Jackson wrote:
>
> Hi Bill,
>
> On 30/06/2024 03:22, Bill Woodcock wrote:
>
>> I would suggest that the IETF is not in the business of crafting 
>> standards to describe individual products built for individual 
>> organizations, but instead is in the business of crafting open 
>> standards that solve issues of interoperability between multiple 
>> stakeholders. The former don’t require standardization, while the 
>> latter can only exist with standardization.
>
> I think this is a fairly serious misunderstanding of the role the 
> emblems play.
>
> The emblems are applied by the appropriate protected parties (inc 
> medical facilities, the ICRC and national societies) on a broad range 
> of software / services / devices. The emblems are consumed by parties 
> to armed conflict on their own software / services / devices.
>
> Although the ICRC has a privileged role to play in stewarding the 
> emblem, the emblem is used by a wide variety of stakeholders in all 
> manners of conflicts and critically is used to convey information 
> between different and possibly hostile stakeholders using very 
> different implementations. It is emphatically something that needs 
> standardization.
>
> Best,
> Dennis
>
>
> _______________________________________________
> Diem mailing list --diem@ietf.org
> To unsubscribe send an email todiem-leave@ietf.org