Re: [arch-d] clusterpation, was Proposed IAB program: Evolvability, Deployability , & Maintainability.

John Levine <johnl@taugh.com> Wed, 22 July 2020 04:00 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A30473A0C1F for <architecture-discuss@ietfa.amsl.com>; Tue, 21 Jul 2020 21:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=eTS9XSLV; dkim=pass (1536-bit key) header.d=taugh.com header.b=K4D34IHv
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 yrqINdnOYH1n for <architecture-discuss@ietfa.amsl.com>; Tue, 21 Jul 2020 21:00:31 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D98483A0C1C for <architecture-discuss@ietf.org>; Tue, 21 Jul 2020 21:00:30 -0700 (PDT)
Received: (qmail 76614 invoked from network); 22 Jul 2020 04:00:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=12b41.5f17b9dd.k2007; bh=j80yaDt5A9xPiFKz3uEIvlTGMdTHYN6PUedmXyYIlj0=; b=eTS9XSLVduY/3Q3VPMm1brGlpF1sB1PlgUHCbScRB0mWdpmZu4SgkiYHzHNHPtla2B5ja6ny53EljzEaT/yhPIJjeBozgeHfJe3qE8cqXdLmc7EPGsSudgMCiya+XF0hU7OzVrqpd18j36DNfMWHBUdeA8El6hJb5Kc8bdHxYwBMENyqPMVLzrBtAJDgY1D+aj9cnGLBBCrIuf7ers4QDMrQ7L5Oxw5GG7Mw/Qph7bg15l9YtqpMdIfY7360TaOM
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=12b41.5f17b9dd.k2007; bh=j80yaDt5A9xPiFKz3uEIvlTGMdTHYN6PUedmXyYIlj0=; b=K4D34IHvkLocEACqAkiHHdeU3RPf+Ue6iu9CuT8SeVJiZmXRuuGc4w+2OmRyqwWDMU6esHGjXD0wkC91amxiarTrD2HuWbZ2TNqol9Ly1CSvFg/AoO/emCO6wJWdm0FM3Udqqd4iKf9+qn2loNevuneAJWV0Xa50XDKhCCg7AqOaRLN8o4i0Ss/CUNRUQjAxyZgL4DsXd0tX0fpZqxDhSwGw2Xt7U1km5Yj72fPhIcbx62pZjplYfdVzosyAmQKD
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 22 Jul 2020 04:00:28 -0000
Received: by ary.qy (Postfix, from userid 501) id 728C81D5EB94; Wed, 22 Jul 2020 00:00:28 -0400 (EDT)
Date: 22 Jul 2020 00:00:28 -0400
Message-Id: <20200722040028.728C81D5EB94@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: architecture-discuss@ietf.org
In-Reply-To: <CAKKJt-fNX16Ap8afcg55DXj3DFb8mGYdB3MxHtLyyMN5a0eFLQ@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/06SSMAucn5K6XIFTRX25KLEz7_Q>
Subject: Re: [arch-d] clusterpation, was Proposed IAB program: Evolvability, Deployability , & Maintainability.
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2020 04:00:34 -0000

In article <CAKKJt-fNX16Ap8afcg55DXj3DFb8mGYdB3MxHtLyyMN5a0eFLQ@mail.gmail.com> you write:
>Because (for reasons I don't understand) I'm involved in AUTH48 processing
>for RTCWeb, I find myself wondering whether the proposed IAB program might
>include considering ways to avoid C-238-style protocol specification
>clusters, whether from the point of view of architectural oversight,
>standards process oversight, or RFC Editor oversight.

I think we all agree that we don't ever want to see another document
cluster as large or as long-lived as C238.

But I would rather not attempt to invent processes to try and guess
how best to prevent hypothetical superclusters. I'd rather that the
RPC and I (or a future RSE) work informally with ADs and WG chairs
when we see a potentially large cluster forming, or worse when a
document is about to link two normal sized clusters into a big one.