IETF Logo Mail Archive

Re: NomCom eligibility & IETF 107

Barry Leiba <barryleiba@computer.org> Tue, 31 March 2020 18:49 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB5F13A26C4 for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 11:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.251
X-Spam-Level:
X-Spam-Status: No, score=0.251 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mwreg1cNF4Ia for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 11:49:52 -0700 (PDT)
Received: from mail-io1-f48.google.com (mail-io1-f48.google.com [209.85.166.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8E7A3A26C3 for <ietf@ietf.org>; Tue, 31 Mar 2020 11:49:51 -0700 (PDT)
Received: by mail-io1-f48.google.com with SMTP id y14so5773474iol.12 for <ietf@ietf.org>; Tue, 31 Mar 2020 11:49:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WcLDu2D/ANLnMeXAOngNHCIon6+jSG8Van61s1pV2Cs=; b=K52AMkoRlLG7jd3mf9o0NXQhSplE8KJWYvbexlfk4k2NsY221Va/aq5zLgCivPzTyK gUVq3fId1N/GfD7QgUiaSaTWqYI+AnLiLXiPXijIWoIRKjwFAa0xXz73gwcD3FloYq8b 5VXBtoNxxi5o79sVJZ3hNptEoWWvy3ehl/AjZnpY6PKGqn/TMYrrM/Kw+5lPMfnccwU1 O/00FYXdVs6N+ZaUfSXMmnrtk/fYLeyxNmxEuuJixD6nWgzCrc2GlvR3VzCG07rTD6UB ozuMftgSXg/CD/9XF1hykQSHmCD5Bm54wf8Fd7h/qEzK6PuEH2/gNs/UrkBviQfukWXl +UJw==
X-Gm-Message-State: ANhLgQ0wJY+3J9CfmCMIywJog3fdXFgCIlSp3aNmTIPm6cjdTdqmaER0 CSQiszZndPa7mZsD14ZOIOcgR4nYg54T3KIpa4h2XOxe
X-Google-Smtp-Source: ADFU+vt3og3ra3H39cATdiyoLncW2BkDtDkE063pNZAFxM1vBY4OmftVtSlXNeyfHORhxOxY2YC6uWLRJ8zWBDIelN8=
X-Received: by 2002:a5d:8952:: with SMTP id b18mr16651673iot.40.1585680590996; Tue, 31 Mar 2020 11:49:50 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.com> <CAC4RtVCzMPGuunYZBCSh90ddY2kKJ_Hqnot0s1jmhNQ7qT0xkg@mail.gmail.com> <89730DD8-0451-4658-A0CD-83A85E2055FE@episteme.net> <0C31D020-46FA-424E-8FFD-64BBE8F952E9@cooperw.in> <1E702B62-9982-48F2-B8D6-F4F80A8DE168@episteme.net> <20200331184236.GT18021@localhost>
In-Reply-To: <20200331184236.GT18021@localhost>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 31 Mar 2020 14:49:40 -0400
Message-ID: <CALaySJ+_+-kf+3nta8LwMiwPmqPmRdOgC7KAnDfeDgx0ThVa-w@mail.gmail.com>
Subject: Re: NomCom eligibility & IETF 107
To: Nico Williams <nico@cryptonector.com>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RZDjMPv9n_BKrhjkB-_769p4X60>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 18:49:53 -0000

> Whereas the IESG just making a decision w/o a Last Call based on a claim
> to authority that is -presumably?!- not subject to appeal... strikes me
> as even more negative an outcome than an inconclusive LC.

To be clear on this point: Any IESG decision is subject to the normal
appeal process.  An appeal could be filed regardless of which way we
handle this (with or without a BCP).

Barry

v2.23.0 | Report a Bug | By Email