IETF Logo Mail Archive

Re: Info about IETF protocol Badge/Logo process?

Jay Daley <exec-director@ietf.org> Wed, 03 January 2024 17:43 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 50EB7C337C86 for <wgchairs@ietfa.amsl.com>; Wed, 3 Jan 2024 09:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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_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 MPN3L0XFnbf2 for <wgchairs@ietfa.amsl.com>; Wed, 3 Jan 2024 09:43:30 -0800 (PST)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 2A8F2C337C65 for <wgchairs@ietf.org>; Wed, 3 Jan 2024 09:43:30 -0800 (PST)
Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-40d3ae326f6so113180275e9.3 for <wgchairs@ietf.org>; Wed, 03 Jan 2024 09:43:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1704303808; x=1704908608; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=NvpcdJ1vxKAwKfCE6Jx8hU4LWdLbH8t56XfGZVA4Go0=; b=wGVIcj9VTDUlYZ+P5kEFSynfgdXybziRgXBeA5OqwhQwUcTPP8yQsIl0nq2HqpbfE3 6q/ruGRIlbdsrxh0q7wUq9AIwxruw5yp5SQQcBAktkimECn6lMw3ad/CZty0ZImL36v0 ID+RUm6b98QTX4xWscWpxTY/y6Cm9R2NttQSBkNsr/9kQ6J/3/3HQAX4zyv1Bfo+1Rar WnGEdnGBz53vlPgWnjPP6wNgghxmSxp6QaBnNzHNpvsZQaDMpzdOrQmGkL7pCvSiOlXB OKJbymFtS2uiIkqZOlbZCPAvFCXZ5HsvPfagspUloe0Xry6qA4mGGFMBUG0+Eai+S9by Ap5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704303808; x=1704908608; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=NvpcdJ1vxKAwKfCE6Jx8hU4LWdLbH8t56XfGZVA4Go0=; b=hY5rezyvfMm/+O3lyCT4tZMloxMtIYFsV5JKwdz/gFj3AguXUc6buNiWXikZsY0UBV dd3pTk0pSGmK0eEuXw/EP0rtNEqxFnVzOsn3llcVztxSUtXNj9y2stH1rOLml0nqEo4E FR5guprJoJqj3+G3Gvn6lRkPh0goZ2yBWEktlgBfhkELPfOHPBqfloI2bkitZSv1HL0s 1GZeBe1twM+K+pye5lPyqxrSopQpj0rIxKWTk3nOFAuao8oWAoiDKOG2cTa5MW+H9chB CjmsMcgE+UzzScXBYOYOQWBbcRrhXUNC//MQuoKAY8wiYtFibKx2mcaBtWv5hYGs625P 8eAg==
X-Gm-Message-State: AOJu0YxqP7R/Xmv445L7cDJYGswH7/nX2b3ONXSeZm1XgdtOWKFhkIye xuX7bdRd3B1FZvvMpcxRn0Ba6fWflNFsz0bn
X-Google-Smtp-Source: AGHT+IEmgV32R+DSdsVjLiQaVuQXQoUI1EnhD3EISYcvmV+K5FZuzxRek0ToTmeCBjzL+FuyqQYsyw==
X-Received: by 2002:a05:600c:4591:b0:40d:5cd2:fecb with SMTP id r17-20020a05600c459100b0040d5cd2fecbmr6101176wmo.24.1704303808410; Wed, 03 Jan 2024 09:43:28 -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 o16-20020a05600c4fd000b0040d2e37c06dsm2945495wmq.20.2024.01.03.09.43.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Jan 2024 09:43:28 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Jay Daley <exec-director@ietf.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Info about IETF protocol Badge/Logo process?
Date: Wed, 03 Jan 2024 17:43:17 +0000
Message-Id: <0BBA5DEC-D147-4EB4-8A08-37104306CCE1@ietf.org>
References: <CAF4+nEEuR3Ns4_WbRykRPrWOrrhjkgfVc5chHLfDwsp0tOQ6SQ@mail.gmail.com>
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, IETF WG Chairs <wgchairs@ietf.org>
In-Reply-To: <CAF4+nEEuR3Ns4_WbRykRPrWOrrhjkgfVc5chHLfDwsp0tOQ6SQ@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: iPhone Mail (21B91)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/1z-8J-PJlx0baD8Tmv4iR4jKNmI>
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:43:32 -0000


> 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

Yes, the Greg I explicitly copied in so that people would know which Greg. 

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