Re: Info about IETF protocol Badge/Logo process?

David Schinazi <dschinazi.ietf@gmail.com> Fri, 05 January 2024 17:47 UTC

Return-Path: <dschinazi.ietf@gmail.com>
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 9F0B2C14F6A5 for <wgchairs@ietfa.amsl.com>; Fri, 5 Jan 2024 09:47:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.104
X-Spam-Level:
X-Spam-Status: No, score=-1.104 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 JKW9HZkqClwN for <wgchairs@ietfa.amsl.com>; Fri, 5 Jan 2024 09:47:12 -0800 (PST)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 88578C14F600 for <wgchairs@ietf.org>; Fri, 5 Jan 2024 09:47:12 -0800 (PST)
Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-40d5336986cso20245075e9.1 for <wgchairs@ietf.org>; Fri, 05 Jan 2024 09:47:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704476830; x=1705081630; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=DpdmmwFdNuSuKYYX9UWGUJYJVoKhzUUItwQVkmvrJgE=; b=kjGNiH26cuCO5gj85btSbZA2HSSKRrbtZXl7U7Rlqtvn6MoSXCW+vPJnFjGYW7pFuU RVm7JCu+FkMkElQRPTfmjtMdWgzzbt8UczzeOKClVaINxdyl/3haMLNmeQqeb2Xt1izM pMIHc+hhhJrwkTsrQt7tPzLKQWFEboyfkjnIYCFSNS2sZO0W/h6gTo/aCUj9d2i4h6us TVuMeDwqnnJ9N7MlvAWYKvZc0BrZSxW9zlcg77pMaT26oLqY2Bk1skkhv9Xd4+K2k0P0 7WiUf8VPPOxCWtz+5GrvPm1439ZX+ucaJjgwkgzW8Zv3AwJfvEfrBrls/DxaSPybXZ/I Sg3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704476830; x=1705081630; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DpdmmwFdNuSuKYYX9UWGUJYJVoKhzUUItwQVkmvrJgE=; b=OFOxLrsUD2Xco/OC4pGU39uOrkYwOSfi6pfy+q/AnaXFvehNhNbsKgbcnRfFspXfkl N56Ho6oBaJ/iYPq0pbT/2UxSB3sHQx1DXNjtV1pIKLl0IE66vOd4yXvyfxw2m3Mwgzbk +E6XsNqztx23x3IvqI7hbHTPnOqlvXjOrJzjzBGlV+Ukci0CCmNCxIRpZeshWllldXLk jwKCoP7Jv2ktK39INRIOu4H+4jEWo4Yj4Tam8TwSF8gceE+2AnGtHSsPhNGctcaUvwDD WG5UOu7haGx4zrpMPoMtLdinOp6opXVabMgAMrMISI543FOPU1QYaIMQ4XxJx+8EFeGk Y51A==
X-Gm-Message-State: AOJu0Yz2M33PmXP05jP5iCEP7ZjYcwV9geO2Sj11+FyXCMtfGYLiCgDK 7kTl4DP9nSMGDycUI+LS6XKFJpOR8A15Spz6A0eqKoagb+yqOg==
X-Google-Smtp-Source: AGHT+IFEo5F4A+GHPFW9rZJjQB3Is67bnNehFcg5QUL8DymkLylkxDVS8YIBL6C1dBPg/YSibjRP9tdo79x8Rc9bltM=
X-Received: by 2002:a05:600c:8516:b0:40c:55a7:770f with SMTP id gw22-20020a05600c851600b0040c55a7770fmr1278464wmb.159.1704476829734; Fri, 05 Jan 2024 09:47:09 -0800 (PST)
MIME-Version: 1.0
References: <87o7e21goi.fsf@fifthhorseman.net> <9330D113-E64B-438B-B680-09D4893B18C4@ietf.org> <CAF4+nEEuR3Ns4_WbRykRPrWOrrhjkgfVc5chHLfDwsp0tOQ6SQ@mail.gmail.com> <55D82889-6449-4A00-AF3A-D98D394F109A@staff.ietf.org> <7C81A1E7-32F9-44C6-A1E2-A35721CC3DEB@apple.com>
In-Reply-To: <7C81A1E7-32F9-44C6-A1E2-A35721CC3DEB@apple.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Fri, 05 Jan 2024 18:46:58 +0100
Message-ID: <CAPDSy+4Zquk7rC9hbeQE1bvTTQjsX93T-gEZ-Jm1+TRtEonfVg@mail.gmail.com>
Subject: Re: Info about IETF protocol Badge/Logo process?
To: Eric Kinnear <ekinnear@apple.com>
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, IETF WG Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f6dc32060e366f21"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/Rs7vsbvDLKLEYb8K0t1hnvLI-GM>
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: Fri, 05 Jan 2024 17:47:14 -0000

+1000 to Eric, the designers were amazing both in how nice it was to work
with them and in the quality of the final logo

10/10 would MASQUE again

David, logo enthusiast

On Wed, Jan 3, 2024 at 7:35 PM Eric Kinnear <ekinnear=
40apple.com@dmarc.ietf.org> wrote:

> As a side note, we (the MASQUE chairs at the time) worked with Greg and
> external designers to get the MASQUE logo in that list made and it was a
> great experience. Very smooth process, really looked at what we were
> thinking/how the working group and protocol worked, and came up with a
> thoughtful and excellent outcome. Would highly recommend.
>
> Thanks,
> Eric
>
>
> > On Jan 3, 2024, at 9:36 AM, Greg Wood <ghwood@staff.ietf.org> wrote:
> >
> > Hello!
> >
> > Yes, I’m the one to talk with about protocol badges.
> >
> > I think I did a presentation about this process at a previous WG chairs
> forum, but I’m happy to put some more detail at chairs.ietf.org so
> there’s a standing resource.
> >
> > In the meantime, let me know if I can provide more inf.
> >
> > Thanks,
> >
> > -Greg
> >
> >> On Jan 3, 2024, at 12: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
> >>
> >> 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
> >>
> >
>
>