IETF Logo Mail Archive

Re: Info about IETF protocol Badge/Logo process?

Jay Daley <exec-director@ietf.org> Wed, 03 January 2024 17:24 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 56FD6C14F6E9 for <wgchairs@ietfa.amsl.com>; Wed, 3 Jan 2024 09:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=ham 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 ziozW7JS3m4x for <wgchairs@ietfa.amsl.com>; Wed, 3 Jan 2024 09:24:43 -0800 (PST)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 B832FC14F6E0 for <wgchairs@ietf.org>; Wed, 3 Jan 2024 09:24:43 -0800 (PST)
Received: by mail-wm1-x32e.google.com with SMTP id 5b1f17b1804b1-40d894764e7so24982785e9.1 for <wgchairs@ietf.org>; Wed, 03 Jan 2024 09:24:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1704302682; x=1704907482; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=ypbnpNcTB+DEgJrTpXzBWNwui6H2IuyKwUKwLAajN1k=; b=RUcFPf1TwOl7kunWlEsOpsIOMzGIzlaIWYJ8Eg8XxuSEnOGaBsYIdCnaeMGib+z/rY IQKR+PhLp3QHS7cD89i/HuWxfMC9Yx/srEh0SDKLgpABT5DYN9lp8JUtOFOb/uA8XSNm mDq49DVTJJfRZlB2+dr7lyqMwez65ZoMMwHbU59xt2R9EvSv5a3N/5of0QpUgAnnerdB euYKI2LQtv1KztDZqWUZmR63kl9aY5oWesYBxQVCZC251e4w6fNA5hzBtujpfTXvTlCy Ihpi/X/NSYU3n0L6uIYLRcG+WzoZ+KecEDXQNEtigU8zqrIIVD/XWQcyUqZ09zMF2hMD rFXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704302682; x=1704907482; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ypbnpNcTB+DEgJrTpXzBWNwui6H2IuyKwUKwLAajN1k=; b=OaqF2ZwUh1Zwj+zL+DAUx8V7PVm98yOjSduzO2hjM8QufBaeUPfX632OCJB5QEIA6H Xc4gC/EjsVdrwXzqiH0YZ7mE0FUYEjRt9pDYFAL+ymvQVMLjfCLcgGt9eLximuGAtMNR 0a4P2NzeE1vxTRcj1QolAzPYa8w6R/FFCuVJKP16CW5c0Nf/Ul7F1JBJTK5aIg+TnIe3 5sXIr0wstBqGRE0R24zVyGPzIGmFxSfwGUFhJgAEGrxL+TQ27nSXYWA4PNxHPFsT/3AR vx1puJylAotbYD02b4TfJlD/pUQ6WOwCbRQLyiJfuzJ/TDSDYwEOoJ6IHViTgHwXYh8U 820Q==
X-Gm-Message-State: AOJu0YzIWV4Bm5LEXr0RsbxEihMFYm8QXhTFBfRQt89028EwMPijJNky 0zG9Eq8dA/+8TtbatO/OCKVTMx3cP7AirzTL
X-Google-Smtp-Source: AGHT+IEy7Dap/m5IiDL5J+IkCmuvfmWUNwanyFRjWCqRG6+JzeWuQqmNXa5cVWitskjMxIgmtOOAnw==
X-Received: by 2002:a05:600c:3412:b0:40d:379a:93a2 with SMTP id y18-20020a05600c341200b0040d379a93a2mr7913363wmp.237.1704302681729; Wed, 03 Jan 2024 09:24:41 -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 8-20020a05600c024800b0040d87100733sm2892131wmj.39.2024.01.03.09.24.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jan 2024 09:24:40 -0800 (PST)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <9330D113-E64B-438B-B680-09D4893B18C4@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_50AFAEBE-6438-42CF-933E-D0290A8023E1"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
Subject: Re: Info about IETF protocol Badge/Logo process?
Date: Wed, 03 Jan 2024 17:24:29 +0000
In-Reply-To: <87o7e21goi.fsf@fifthhorseman.net>
Cc: IETF WG Chairs <wgchairs@ietf.org>, Greg Wood <ghwood@staff.ietf.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
References: <87o7e21goi.fsf@fifthhorseman.net>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/yCyhd1cmzq8XZ0lSqmLRpfVI77A>
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 17:24:44 -0000

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/
> 
> 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

v2.23.0 | Report a Bug | By Email