IETF Logo Mail Archive

Re: Sergeant-at-Armss and New proposal/New SOW comment period

Randy Bush <randy@psg.com> Sun, 01 September 2019 23:37 UTC

Return-Path: <randy@psg.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 103F61200BA for <ietf@ietfa.amsl.com>; Sun, 1 Sep 2019 16:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 4-EK0JgtJHwD for <ietf@ietfa.amsl.com>; Sun, 1 Sep 2019 16:37:12 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED75E120074 for <ietf@ietf.org>; Sun, 1 Sep 2019 16:37:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1i4ZPB-0005KQ-1P; Sun, 01 Sep 2019 23:37:09 +0000
Date: Sun, 01 Sep 2019 16:37:08 -0700
Message-ID: <m21rwzfv17.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Sergeant-at-Armss and New proposal/New SOW comment period
In-Reply-To: <CABcZeBPQu4oZ6pGT8cgAFPTQk4nnQm4S9LzVF46dwBCA+kO7Sw@mail.gmail.com>
References: <061D2F46-71C3-4260-B203-73B07EB59418@encrypted.net> <5B276430-96A9-44EA-929B-B9C2325AFCA5@encrypted.net> <863c6fa8-2735-b2c6-5542-d5d100485a6e@outer-planes.net> <10843FAF-66D2-483D-96AB-2F993803AAC6@cisco.com> <6FA9D85E1B425914CA994AFD@PSB> <dcda8d0b-3e75-53de-560c-cf6942e61efd@nostrum.com> <CABcZeBPQu4oZ6pGT8cgAFPTQk4nnQm4S9LzVF46dwBCA+kO7Sw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oXBFjOh-XFJQKDzsjJuE4ByUpvA>
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: Sun, 01 Sep 2019 23:37:13 -0000

> On the other hand, I, and I suspect others, don't really want to wade
> through the IETF mailing list in order to follow this discussion.

otoh, some of us do not want to subscribe to yet another mailing list
for ietf administrivia.  but yes, it is a trade-off to fork or not to
fork when a sub-subject is hot on some list.

do folk not have delete and delete-thread keys?

randy

v2.23.0 | Report a Bug | By Email