IETF Logo Mail Archive

Re: Info about IETF protocol Badge/Logo process?

Jay Daley <exec-director@ietf.org> Wed, 03 January 2024 18:45 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB59C14F6B6 for <wgchairs@ietfa.amsl.com>; Wed, 3 Jan 2024 10:45:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.013
X-Spam-Level:
X-Spam-Status: No, score=-1.013 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
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 tNOpFZGmPKuo for <wgchairs@ietfa.amsl.com>; Wed, 3 Jan 2024 10:45:41 -0800 (PST)
Received: from mail-vk1-xa35.google.com (mail-vk1-xa35.google.com [IPv6:2607:f8b0:4864:20::a35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E82C9C14F6A2 for <wgchairs@ietf.org>; Wed, 3 Jan 2024 10:45:41 -0800 (PST)
Received: by mail-vk1-xa35.google.com with SMTP id 71dfb90a1353d-4b743ca0597so1123914e0c.1 for <wgchairs@ietf.org>; Wed, 03 Jan 2024 10:45:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1704307540; x=1704912340; darn=ietf.org; h=to:cc:date:message-id:subject:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=9rJ0+vnM3/d3960k3xcH+c56Waiu3HsTcemtxxPQFX4=; b=aK7LqyHvRs7xcyuLZft7OAM/vpeXIwexbbrG4aMhps16WTIvFtVaSli4euEJv+KU2C dfmzCel3l6GW2yoN78u8zJviEjIxZ7MsQ2ElkfZuCS5wzyLrdITNBelqeUUlA5ChcwGc dvcpTVW1FkDLNwmKgR00B25/J9We6d4BerYgF47MyexTZBQ9HwKgx03BNIB3IDo5idA8 cPw6kTMY8FK8JczYVbSa86ulUEVD09zP42Lo0z8eLsRP+vrnRBdKjgodgimuwM17G4xB EZF1raj8v8st7mc4ne+4wU5bO7YiPhf+Q2QFx0S28Gia9tFSumxgc0JaGCX3etn3Xw+O J/HQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704307540; x=1704912340; h=to:cc:date:message-id:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=9rJ0+vnM3/d3960k3xcH+c56Waiu3HsTcemtxxPQFX4=; b=uKk44SIfni9Oklpy+pVVUezckt8DFcJQ01LGAu5TWDCdMCmjeCPmTWDk5KT8ikLami +38uLjRt0slw2hcTNsCVaL1h0RamdbGW5nwXwqqHFpJP9BhzkTpZ3bA0rBjpT7jX0/CH okBWslD+9WsSd55b4GTd9h2U2UoT1lGEGGh6PKd4ENbrSoHir+/cUYjAg20hOHKgvg0Z V67bXliC91ISA1WDfDDsOq3SzqGiv477bUQ+ydEXTxIu/ec0wT//PyI6pvCQDqP9azn8 x0jiVo3PaA4v9/iVFksqLOpsnPjpRwQYw7akn+CSqIuBQc8JtH0x9Hlqtxco6OxJXdq6 Le9g==
X-Gm-Message-State: AOJu0YzPbfqBIgmBZsU6+G6JlGbyLq9QdcGTVSbjJ0kP9z33zPcqj9Jo /fR/5aEejylSkidBVs85QgozsLGuztbqTtTfuI3QjNXoD7Eq7H1s
X-Google-Smtp-Source: AGHT+IG1+EK7SSAssKnvVF7imrgjRC7oeOEk8tQvUvI3mnEdiTiS+C1K5C5X70QDDLRL51Km0l0/Rw==
X-Received: by 2002:a05:6122:3129:b0:4b6:b917:13a9 with SMTP id cg41-20020a056122312900b004b6b91713a9mr8016925vkb.6.1704307540565; Wed, 03 Jan 2024 10:45:40 -0800 (PST)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id l21-20020ac5c355000000b004b767f9068dsm510370vkk.36.2024.01.03.10.45.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Jan 2024 10:45:40 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-AE86E3FA-D500-4353-AF23-A782F70005C2"
Content-Transfer-Encoding: 7bit
From: Jay Daley <exec-director@ietf.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Info about IETF protocol Badge/Logo process?
Message-Id: <6CB99451-B4D5-467D-85CE-CCA4B83F8A0A@ietf.org>
Date: Wed, 03 Jan 2024 18:45:27 +0000
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, IETF WG Chairs <wgchairs@ietf.org>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: iPhone Mail (21B91)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/k1H9CFOnCtapRAJSF89iRtz5TTA>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jan 2024 18:45:44 -0000

My apologies Donald. 

I did explicitly add him and the message in my sent folder includes him but his address was removed by mailman, most likely due to an ‘avoid dups’ flag. 

Jay

-- 
Jay Daley 
IETF Executive Director

On 3 Jan 2024, at 18:25, Donald Eastlake <d3e3e3@gmail.com> wrote:


Hi Jay,

On Wed, Jan 3, 2024 at 12:43 PM Jay Daley <exec-director@ietf.org> wrote:
> > On 3 Jan 2024, at 17:34, Donald Eastlake <d3e3e3@gmail.com> wrote:
> >
> > Do you mean Greg Wood? There are lots of Greg's in the IETF.
> > https://datatracker.ietf.org/person/Greg%20Wood" rel="nofollow">https://datatracker.ietf.org/person/Greg%20Wood
>
> Yes, the Greg I explicitly copied in so that people would know which Greg.

No, I see no evidence that you "explicitly copied in" Greg Wood although, of course, I would not have seen it if you blind copied him. I did look at the main headers on your message and, in gmail, they looked like the following:

from:Jay Daley <exec-director@ietf.org>
to:Daniel Kahn Gillmor <dkg@fifthhorseman.net>
cc:IETF WG Chairs <wgchairs@ietf.org>
date:Jan 3, 2024, 12:24 PM
subject:Re: Info about IETF protocol Badge/Logo process?
mailed-by:http://ietf.org" rel="nofollow">ietf.org
signed-by:http://ietf.org" rel="nofollow">ietf.org
security: Standard encryption (TLS)

Only after failing to find any hint in these headers as to what "Greg" you were talking about did I send my follow up message.

In case there was something obscure going on, I just used the "Show original" feature in gmail and the result is attached. I see no sign that you explicitly copied Greg.

Even if you had, it would have been good practice to use his full name and be less cryptic.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

> Jay
>
> > Thanks,
> > Donald
> > ===============================
> > Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> > 2386 Panoramic Circle, Apopka, FL 32703 USA
> > d3e3e3@gmail.com
> >
> >> On Wed, Jan 3, 2024 at 12:24 PM Jay Daley <exec-director@ietf.org> wrote:
> >>
> >> Hi Daniel
> >>
> >> The process is that you talk to Greg and he manages it all.  Provided we have the budget and there are no objections, we generally just commission one.
> >>
> >> Jay
> >>
> >> On 3 Jan 2024, at 17:15, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> >>
> >> I recently became of the repository of "Protocol Badges" linked to from
> >> here:
> >>
> >> https://www.ietf.org/badges/" rel="nofollow">https://www.ietf.org/badges/
> >>
> >> It looks like the following protocols have "design-y" logos:
> >>
> >> QUIC, ACME, MLS, MASQUE, NTS, TLS 1.3, HTTP, HTTP/3, L4S, PRIVACYPASS
> >>
> >> Is there a process for how these badges are created and held by the IETF
> >> trust?  I'd be happy with a pointer to documentation or mailing list
> >> discussion or anything like that if it already exists.
> >>
> >> If you were involved with any of these proocol badges, and you would
> >> rather talk about it off-list, feel free to reply to me privately as
> >> well.
> >>
> >> Thanks,
> >>
> >>       --dkg
> >>
> >>
> >> --
> >> Jay Daley
> >> IETF Executive Director
> >> exec-director@ietf.org
<jdmsg.txt>

v2.23.0 | Report a Bug | By Email