IETF Logo Mail Archive

Re: a brief pondering

Adam Roach <adam@nostrum.com> Mon, 23 March 2020 03:23 UTC

Return-Path: <adam@nostrum.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 2883A3A012A for <ietf@ietfa.amsl.com>; Sun, 22 Mar 2020 20:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.405
X-Spam-Level:
X-Spam-Status: No, score=-1.405 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.274, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 dR0M8hgQ432t for <ietf@ietfa.amsl.com>; Sun, 22 Mar 2020 20:23:40 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 4A1DE3A0433 for <IETF@ietf.org>; Sun, 22 Mar 2020 20:23:40 -0700 (PDT)
Received: from [172.17.121.48] (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 02N3Namo075308 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 22 Mar 2020 22:23:37 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1584933818; bh=chQEtRG8MbmSzZh3wHKbKG4rYqrEVxW9OzmoimA4hmw=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=neOGxsmIisxZuiMhUZ4KJwFu/wQxn/++VrH4XPSkPokuVs4OW63faRsDOxINWWLWU +0tRpohe+ONPxjanoSDtrSAZ/ID0K8ZMphaP7BmD8OS5fU7aviTgQWsBZc3JDdnvf7 Uaki8fEc42anl6eERkmR9JLX0sS4sj7hwlFRpPnQ=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be [172.17.121.48]
Subject: Re: a brief pondering
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Carsten Bormann <cabo@tzi.org>
Cc: ietf <IETF@ietf.org>, Eliot Lear <lear@lear.ch>
References: <fd6b7ee2-cdbe-14a1-0087-ce61282b22f6@lear.ch> <29D0DCA7-1D72-428F-A6DD-05511D90C039@cable.comcast.com> <31A798F0-9DE0-4231-A768-76BA9A1A2180@tzi.org> <26B25A87-5820-462D-8279-8C82EC44EB16@lurchi.franken.de> <2DE1D3E9-EE59-479B-8624-29749E7F02D3@tzi.org> <CAKKJt-c=AAVXdLtFKLHXGOk5m_J-kdnd19nSSQU7b58ub3YfFw@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <6f9c3bec-8e6e-146c-5eec-81b0f6e01b7c@nostrum.com>
Date: Sun, 22 Mar 2020 22:23:31 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <CAKKJt-c=AAVXdLtFKLHXGOk5m_J-kdnd19nSSQU7b58ub3YfFw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-1xH2paKYm-GOQfA0VHYEHFyx5c>
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: Mon, 23 Mar 2020 03:23:56 -0000

On 3/22/2020 4:55 PM, Spencer Dawkins at IETF wrote:
> As much as I enjoyed some getting some TSVWG doc unstuck from C238, 
> someday that cluster needs to finally empty out,


All cluster 238 documents are in the RFC Editor queue. There's no 
conventional way that you could create a normative dependency on any one 
of them to a new document, and that's the only way that a document could 
get added to the cluster.

/a

v2.23.0 | Report a Bug | By Email