IETF Logo Mail Archive

Re: Changes to the way we manage RFPs

Barry Leiba <barryleiba@computer.org> Wed, 26 February 2020 21:58 UTC

Return-Path: <barryleiba.mailing.lists@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 1932A3A08C9; Wed, 26 Feb 2020 13:58:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, 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, URIBL_BLOCKED=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 aTjLmGSSXaW8; Wed, 26 Feb 2020 13:58:20 -0800 (PST)
Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) (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 13FDF3A0902; Wed, 26 Feb 2020 13:58:20 -0800 (PST)
Received: by mail-oi1-f176.google.com with SMTP id a22so1109991oid.13; Wed, 26 Feb 2020 13:58:20 -0800 (PST)
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=v4E7auzoXUSxZyVrsZsiXGsiixZlQrq4k4zMbfYV5BA=; b=cUD315EYT9uoukHHW1Abn0b27GwsO0sKVy96xy3b+xivGiX2xXGe7B1OH/AKX57nvK wDz0kdzFA9wLBzQnNxpHHxldy/moEL+AvREAB91tkj8PMwL/t7KjthTX+i9LH1U/ca1A PEPcQcUZArKmLHLiPHH8pMWkVOFOg2tQUxnlUyrtp6GECLYHgdUajkGX852aeQNsoyjW 3zaGRt4f+59+o3cOCU3GAqCrIdXZ3l5pCKpqX4JE6CedwzpG8LPzESUDIQwVlmT6XY5z rYM27L1iI3WTtdH/z7g69FsJqqO0J5LviGh+fH94Rnb+/hBDRzfNpgkG+BMYxe9u6Epq ATiw==
X-Gm-Message-State: APjAAAU+vZuRJkCqjlb782nbBq7gXHq7LPBbJFbJVS8WTIXFpiXNvs81 wry1Iju6hEHz7MKgYXZ05IgYovqOYxakpgnLPq1CnA==
X-Google-Smtp-Source: APXvYqyksKfJfo8qN1cZKmaktxOmYmoGmSmxqzruMr3Q012WPOAhwuI1V9V3KrahwOxMF5V9CJur3BNxRcdjE7GGd6k=
X-Received: by 2002:a54:440e:: with SMTP id k14mr880297oiw.160.1582754298470; Wed, 26 Feb 2020 13:58:18 -0800 (PST)
MIME-Version: 1.0
References: <52c88899-8f4e-c92e-d147-e5437c903467@gmail.com> <8AB21B37-3B6F-4BCF-BF35-FB57639FDF8C@ietf.org> <13032.1582721936@localhost>
In-Reply-To: <13032.1582721936@localhost>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 26 Feb 2020 13:58:06 -0800
Message-ID: <CAC4RtVDCPPMi_3Y-PDK4pALhCDeWkx5RiR+jOuS2Oj_KkuSz3Q@mail.gmail.com>
Subject: Re: Changes to the way we manage RFPs
To: jay@ietf.org
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/il4wCCTNVYtiZmxZpDocraAqCyg>
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: Wed, 26 Feb 2020 21:58:27 -0000

On Wed, Feb 26, 2020 at 4:59 AM Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
>
> The ietf-lastcall split has been good for ietf-announce volume, but

But here's the thing: That split should have not affected the volume
on ietf-announce *at all*.  It should have reduced volume on
<ietf@ietf.org>, which is a very different thing.  This isn't the
message thread to discuss that further, but I mention it here to lead
into agreement with some other comments:

I believe that having a new "rfp-announce" list is a fine thing *if*
RFC announcements are posted to *both* ietf-announce and rfc-announce.
That should satisfy all the concerns here: those who subscribe to
ietf-announce need to change nothing and will still get RFP
announcements, and those who only want RFC announcements and not the
other stuff can subscribe only to rfp-announce -- it's an individual
choice.

Barry

v2.23.0 | Report a Bug | By Email