Re: [Rfced-future] Model proposal
Eric Rescorla <ekr@rtfm.com> Tue, 07 July 2020 17:04 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 CB1703A1164 for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 10:04:41 -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 qRJwTYGCUu_O for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 10:04:39 -0700 (PDT)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (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 8C7A63A1179 for <rfced-future@iab.org>; Tue, 7 Jul 2020 10:04:39 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id h19so50816702ljg.13 for <rfced-future@iab.org>; Tue, 07 Jul 2020 10:04:39 -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=ZwBU+eieycr8f1DgjisxT4+mKSL9CFJU7/kl6Xcjj70=; b=yiA52O81JgFMufyNIC2YbHyggVXBsKH1WrDMGaGc8L0YWKo2eNQ5FHHr67Jor8Xw5r UYiTOGgCkLGqi7WZIc4H8p9wBiA+cK0YCMrQu4HktPpLabYMcoyEXvXhNZK6WJwhZXpA tUJtEzoMBeR4aycq8OsAFS8+/elPNINZQFgsWiEEe13P5zt63opDZtapXTKzqWwlxgZv fW87HeyLaCn8oYjwBuXgHB/nLjOjZzHDrKR3CD0pVVmdxkDabycJIhE5C9bxd86hEHSK Vb+mrqOgp1HmbHO81ROere8K3TlPSixfv2eA0EquMmXTsWhgXTu5VdqA2a4VuJJHFv9H VKaA==
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=ZwBU+eieycr8f1DgjisxT4+mKSL9CFJU7/kl6Xcjj70=; b=GGvZQqKtAlx/I0jWmTE5BWQQWZ0r1HsfhbtoBkvYUm1MNdx34nas83mRBw06K146wG E+jbqvMX5CUNLXPiVJSEdvoVCIwLQyKpoWngcnOwGvCYAB1p96XmITYHstGgdncw5weJ r7oZqZZDTadSYxbuT5pqlwdv5Q7DHZAFYjwDZrwkLZzzXEUFkge4O8vHUYnaA/bYKxDu 3Omn+njIgUN2xEXYAEmRJLNjInnWBYCZtpDtOvjpxi6/THVzxzVVnPA5k8wphYCLuoy0 +FG9KWCx2AyaBjKYF/KFXTfFLWAOlvR9Zol3SC7BZkLJodyN0xivMv7dActRn3v3b/z/ qd8Q==
X-Gm-Message-State: AOAM530rzpoKK8vuqlHvarjA/nBUGopT3ZuISkdJSpiVeLkSAB2mhEYR EiyPUv5fo0blLuozWH0KoDpjAl1QzMZPs5GQqW3RDWQ6/Qx3Sw==
X-Google-Smtp-Source: ABdhPJzTC4h29vNC4Qlzp6RNH7SOoJkoOzWeEtxxBauJiRUJwEVT7E/0slc429ShMwfd8zes4a6a+muKlXs+JMldJHo=
X-Received: by 2002:a2e:3311:: with SMTP id d17mr30874215ljc.13.1594141477625; Tue, 07 Jul 2020 10:04:37 -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>
In-Reply-To: <d1f33279-0656-4caa-81e7-aa665d3a4acb@www.fastmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 07 Jul 2020 10:04:01 -0700
Message-ID: <CABcZeBMdrfjy+kqQ20MS_1fZrNddff+ycwau5VdC5qAFQN2qVA@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: rfced-future@iab.org
Content-Type: multipart/alternative; boundary="0000000000007ef38805a9dcfcf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/H-65Tqmhq1Bvq0AWoGcMpQXHG7M>
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 17:04:43 -0000
On Mon, Jul 6, 2020 at 9:19 PM Martin Thomson <mt@lowentropy.net> wrote: > I do recall several lengthy discussions about the number of authors on a > document, but as these were recurrent and inconclusive, I am of the view > that these are perfect for a working group to strategize on. > I'd like to focus in on this example for a moment, as it also consumed a fair amount of IESG time, and I think it shows some of the complexity here. Authorship conventions vary fairly significantly even within genres. For instance, in computer security alone, I am familiar with at least three primary author ordering rules: - Students first, ranked from most to least contribution, followed by professors (sometimes ranked loosely from least to most supervision/engagement). [a lot of Security] - Students first, but loosely ranked by increasing need to find a job as well as contribution, then professors as above [Systems-influenced Security] - Alphabetical [Crypto] If you go outside computer science into broader paper publishing you will also see the following (among others): - Giant author lists [especitally particle physics [0]] - Detailed taxonomies of what contributors/authors did [medicine [1]] My point here is that authorship policies depend on what values the community in question is trying to promote (recognizing people's contributions, advancing their careers, precisely delimiting what everyone has done, having a single point of contact, etc.). And when we discussed these topics in the IESG, we discussed similar considerations. Thus, while these discussions certainly do benefit from understanding the perspectives of other communities deciding on the right policies is more about community objectives than it is about publishing expertise. Indeed, it seems possible that we might develop different policies for different streams depending on which objectives are most important to those streams. -Ekr [0] https://www.nature.com/news/physics-paper-sets-record-with-more-than-5-000-authors-1.17567 [1] https://www.elsevier.com/authors/journal-authors/policies-and-ethics/credit-author-statement
- [Rfced-future] Model proposal Martin Thomson
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Martin Thomson
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Christian Huitema
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Adam Roach
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Stephen Farrell
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Larry Masinter
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Eric Rescorla
- Re: [Rfced-future] Model proposal Joel M. Halpern
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal S Moonesamy
- Re: [Rfced-future] Model proposal Martin J. Dürst
- Re: [Rfced-future] Model proposal Mirja Kuehlewind
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Russ Housley
- Re: [Rfced-future] Model proposal Scott O. Bradner
- Re: [Rfced-future] Model proposal Scott O. Bradner
- Re: [Rfced-future] Model proposal Russ Housley
- Re: [Rfced-future] Model proposal Eliot Lear
- Re: [Rfced-future] Model proposal Christian Huitema
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Martin Thomson
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Nico Williams
- Re: [Rfced-future] Model proposal Eliot Lear
- Re: [Rfced-future] Model proposal Brian E Carpenter
- Re: [Rfced-future] Model proposal Brian E Carpenter