[Eligibility-discuss] New ELEGY working group -- startup

Barry Leiba <barryleiba@computer.org> Fri, 26 August 2022 18:30 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD0C0C14F74E for <eligibility-discuss@ietfa.amsl.com>; Fri, 26 Aug 2022 11:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.406
X-Spam-Level:
X-Spam-Status: No, score=-1.406 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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
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 RN3JJf03l0tu for <eligibility-discuss@ietfa.amsl.com>; Fri, 26 Aug 2022 11:30:29 -0700 (PDT)
Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) (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 6CDFEC14F742 for <eligibility-discuss@ietf.org>; Fri, 26 Aug 2022 11:30:29 -0700 (PDT)
Received: by mail-ej1-f54.google.com with SMTP id lx1so4656445ejb.12 for <eligibility-discuss@ietf.org>; Fri, 26 Aug 2022 11:30:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc; bh=2Bo9kjd73aZVUZ9lNxsJFgM57DwI/I7+xU/MSahprvw=; b=NDqGpAuLpJnu7DGTYxLJjzWuQJgeM+5f0YQROt7VXVwLBOZIAsLbHHIrD5biYXKHl4 jX1N9VNkxgUcjR54aDLFQgMHzrx/SwrILWPD2yotALDYLRq+nTPNdEem48zU+AzkISy0 5+7LnFTtfVKa5DtL+TQNndyVDUEdrkfZgVZ7gkc/pTsnC04kIzFwXpdu3FB1tGZMlc6T QRqUmCfrBkhAjTgDUkvKUMt0ARwQt3pe1ensS9oMCnllzj7K+s5D8h5vhX3wV2wByTnP sXLqasu6GX4QgBRpxITqq3Rx0dSmBi7aLKe/TKI6mRufZFzobGuNMQQK4Sdq18mve4rZ BzHQ==
X-Gm-Message-State: ACgBeo3+TLvD4xuQhDAML+PabgJkwcU5cgSEjmxoz7TR3Wd1phOUyFfl +qBxZnHcPaGt8jtvuCa88dX5HFAJ2B9dfCIGxsflXnPMRvo=
X-Google-Smtp-Source: AA6agR4kmg/xDY2ZfD3jG1OSygShpL3cuZJgl8cF3O3QqZesfFsB2nBFuLoUvHx0vW4MkKFswUN2HOPa7NU7exfg+eE=
X-Received: by 2002:a17:906:5a64:b0:741:3586:92f with SMTP id my36-20020a1709065a6400b007413586092fmr1858046ejc.721.1661538627320; Fri, 26 Aug 2022 11:30:27 -0700 (PDT)
MIME-Version: 1.0
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 26 Aug 2022 14:30:15 -0400
Message-ID: <CALaySJ+uvZME0bWQnB9tSvABxkjgsTG8xpfLT1g62bBL3QeG6w@mail.gmail.com>
To: eligibility-discuss@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/_AolC1-eOoLAEBQTlBQK0EuHY50>
Subject: [Eligibility-discuss] New ELEGY working group -- startup
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF eligibility procedures <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2022 18:30:33 -0000

Hi, all.

As the ELEGY working group charter:
https://datatracker.ietf.org/wg/elegy/about/
...was approved by the IESG yesterday and the Secretariat magic seems
to be done, let's hit the ether running and get started.

Michael Richardson and I (Barry Leiba) are your co-chairs, and we've
just had a planning call.

The first order of business is setting a starting point for
discussion.  For that we have the draft draft-duke-elegy-rfc8989bis:
https://datatracker.ietf.org/doc/draft-duke-elegy-rfc8989bis/

We propose that draft as a reasonable starting point, keeping in mind
that every detail in it remains up for discussion and change until we
have working group rough consensus on the details.

So this is a call for the working group to adopt
draft-duke-elegy-rfc8989bis as draft-ietf-elegy-rfc8989bis.  If you
object to or have any comments on the adoption, please post them here
by Friday, 9 Sept.

This is also a call for comments on whether Martin Duke should have a
co-editor who is not on the IESG.  If that matters to you, please
comment on that point.  If you think it doesn't matter, you may also
comment to that effect.

This also also opens general comments on the issue at hand, which is
updating RFC 8713 Section 4.14 to set NomCom eligibility criteria.
Please use the content of draft-duke-elegy-rfc8989bis for now and get
the discussion started: let's not wait until the call for adoption is
formally over, and let's get the discussion started without delay.

Please respond in this thread about the adoption and editor question.
Please start another thread to discuss the eligibility criteria themselves.

Barry, as chair