Re: [Rfced-future] Model proposal

Eric Rescorla <ekr@rtfm.com> Tue, 07 July 2020 18:03 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C96BD3A07F8 for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 11:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 GEQ5q6bZYKYj for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 11:03:02 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 2EB8E3A07F2 for <rfced-future@iab.org>; Tue, 7 Jul 2020 11:03:02 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id 9so50969611ljv.5 for <rfced-future@iab.org>; Tue, 07 Jul 2020 11:03:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2FedjV4TzN4Ia2tYxRUNm+4QWtvKL/UcxB9XcXfBhwo=; b=ZaO9eWVoyl14UrTp/HbTow+mhYEMUmKarrlfQ0Y7YunofiU5IL3BIA3qQqbzjkAkzV X3afv5NU+Y00fJ63VFqWYJykRt0yrVS6E5cyx1PaofY6/r8LaywqV83d1T/YJ+ChMWlu bPlh40HgkjJ/IIVkkBSQ+ZPnrzdnTRHwv2yuLZY/B9sQMFzYfwtpqhtLzEOGNp9VM0fn OaeqRQJNpphKZMSybNpapUca8eCK6FWNGdmt4SwcvUzugTofENuH+BEOeAzlwgnjvpja NAiLyCVnPgvN69zWaZCFHNAMsEfZFP1ZNjmoqjvUXrUQKdUaGDIh/bIeyOT4t/JK6mX8 agYQ==
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=2FedjV4TzN4Ia2tYxRUNm+4QWtvKL/UcxB9XcXfBhwo=; b=kV5urCmyM6YbJHOGI2SNJrmh0R/LPOZj+MzfvKekjLEyboc/Ouh9DyObavGKBdHik+ GpxAmbvKwO/6ZLOOXVJsDFUMRYUFzSH2KYObaK46FZpAZ0cYa0Zhh1xuz3512dy8oZjS WV4DnXXDOLD9sr5Wfca9JNrF3uqtfwhDgCiE85lpUVjuU9wLZ50jSFg4784diDmdCdUn yCZXYXtU38AcG6dJgsKnR1jieGrF9w8lMavnyFwuKZ6eYEx8NwgsLfxC05t02RjwDpi0 jkmjBP8S9QzOggcmYQA6ntiM/rsNnmAIlhqLs5GaIjEMmTbSXzD0DBHqjfr7meQQA9r1 BJug==
X-Gm-Message-State: AOAM532gV9HKbm3JA4/XmBnjV1FHmqfbxyTIo8p6qwLvLR/lnxeiCqHt 865lvObnTMiRmePTarL/D1+jIxIaN7quOC8lC5XmpyO35kw=
X-Google-Smtp-Source: ABdhPJywjc1CYhbHQnQmXGB/XsH2KD+qxTA6St6mHgZwDkLfzEzF4iuka+dpurd/qxh9ELIQSkiQe1gzswTwAfQ1akM=
X-Received: by 2002:a2e:3311:: with SMTP id d17mr30991940ljc.13.1594144980289; Tue, 07 Jul 2020 11:03:00 -0700 (PDT)
MIME-Version: 1.0
References: <d4d1cd2d-6df2-4cb4-b63a-f9bba45b48c0@www.fastmail.com> <51b72823-f2a2-29bd-bd88-f63e13522387@gmail.com> <d1f33279-0656-4caa-81e7-aa665d3a4acb@www.fastmail.com> <CABcZeBMdrfjy+kqQ20MS_1fZrNddff+ycwau5VdC5qAFQN2qVA@mail.gmail.com> <7eb9cdfc-c295-8de8-cba5-a5a1ca6ff6f7@joelhalpern.com> <fbb94e7f-1abc-5ca6-af3a-4dfa02e47400@huitema.net>
In-Reply-To: <fbb94e7f-1abc-5ca6-af3a-4dfa02e47400@huitema.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 07 Jul 2020 11:02:24 -0700
Message-ID: <CABcZeBPGbFSR99ecHRWBQOGwDJQrq9g=5DxBwRoBv7i0sh=geA@mail.gmail.com>
To: Christian Huitema <huitema@huitema.net>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, rfced-future@iab.org
Content-Type: multipart/alternative; boundary="00000000000045594c05a9ddcdd1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/_q5Wi3AhS0zj0GtHPH01TAVK5o4>
Subject: Re: [Rfced-future] Model proposal
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2020 18:03:04 -0000

On Tue, Jul 7, 2020 at 10:51 AM Christian Huitema <huitema@huitema.net>
wrote:

> On 7/7/2020 10:27 AM, Joel M. Halpern wrote:
>
> > I understand that other communities handle authorship differently, and
> > that we may (collectively) decide to handle it differently for the RFC
> > series than we currently do.
> >
> > However, if we few it as a single series (which we currently do, with
> > subdivisions) we have taken the few that I think is appropriate that
> > we want a single approach to general appearence, etc.  As such, having
> > drastically different authorship policies for different sub-sets of
> > RFCs would seem a drastic change.
>
>
> I think Joel has a point here. Yes, the IETF is only one of several
> streams, but the RFC series is in practice one of the "brands" of the
> IETF. Having widely different practices in different streams would
> weaken that brand, and contribute to a lesser impact of IETF standards.
> I would advocate some caution there.
>

Well, I'm not advocating recklessness...

In any case, it seems like the most plausible change would be different
overall author limits, in which case the primary thing that would be needed
out of the RFC Series itself would be to not have large numbers of authors
look silly, and then some streams could choose to have lower author limits.
This isn't an especially hard formatting problem: you don't put line breaks
between the authors names and when there are a lot of duplicate
affiliations you use symbolic markers next to the authors.

-Ekr