IETF Logo Mail Archive

Re: [Rfced-future] Model proposal

Christian Huitema <huitema@huitema.net> Tue, 07 July 2020 17:51 UTC

Return-Path: <huitema@huitema.net>
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 830843A08BD for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 10:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 IwOd7RhZU2GD for <rfced-future@ietfa.amsl.com>; Tue, 7 Jul 2020 10:51:33 -0700 (PDT)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 D8A6E3A0893 for <rfced-future@iab.org>; Tue, 7 Jul 2020 10:51:30 -0700 (PDT)
Received: from xse328.mail2web.com ([66.113.197.74] helo=xse.mail2web.com) by mx37.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jsrkV-0007DW-MB for rfced-future@iab.org; Tue, 07 Jul 2020 19:51:28 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4B1VNS5jGHz3JN6 for <rfced-future@iab.org>; Tue, 7 Jul 2020 10:51:04 -0700 (PDT)
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jsrkG-0006C5-M1 for rfced-future@iab.org; Tue, 07 Jul 2020 10:51:04 -0700
Received: (qmail 22335 invoked from network); 7 Jul 2020 17:51:04 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.46.187]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <rfced-future@iab.org>; 7 Jul 2020 17:51:03 -0000
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Eric Rescorla <ekr@rtfm.com>
Cc: rfced-future@iab.org
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>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Message-ID: <fbb94e7f-1abc-5ca6-af3a-4dfa02e47400@huitema.net>
Date: Tue, 07 Jul 2020 10:51:03 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <7eb9cdfc-c295-8de8-cba5-a5a1ca6ff6f7@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Originating-IP: 66.113.197.74
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.56)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0f6LF1GdvkEexklpcFpSF5apSDasLI4SayDByyq9LIhVF+CGJIg6eL+k Bm4EUfvr3UTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDjRzgyua+oKUgQGcbmeu+KPhY RkpFG1KU35iPF8F1Y4iJ/txGEdgq4bsYdEWhb4PCQVFPFt+4EqMnp4CTDhVg0lKlzDUUdXZXKiJE 9FAeBYpBbCpe79Kozx0nomzoHNuEaZ3WIIa/WG5uTfK4bh5BPg7GrRD93GuKsil0DsNlfaQNjS91 xLLHjz8tOnVewUzjKn6AaXxoL/FjeXc4guU5t5coTPkiAq+E/1gvF2d40ruQVyADaS6UpCBADjTx teudCa15Ytj/yAhGv8ezOASMHW/bWfgucjnNmABpGhD9TTsjQT2BGVI0EbGkW8Q42wJCdCZm6kTr qH+fmxyzQoG+NtezYqxGMqsKjARq8PBC4qjRn0hhkccum+xyb3k4eNalTAas0edmB2q/yBRqnQY9 Wp4oEuFb796V1/nl3YbqwU/VPb6Z51AWQAUvAUQbV3oqEaMjfjmXaBok2IyAEprch60jiD6XqsJZ tjQxlyCdseyB/kQBXu3m1qDxg6B2XQ/iOJ3j+DDpQoTcv7hBwGGVtIFP0gqqcSkAlMX+K43+J9/B H1fP3YU+2XWwKzL04bcfwzQZWnqpeh+UbGCVNeqba5Xked+P+aSZU/EB7YnRWs2LBDMrD7q/cJog wbqzsuokPO51RBbod5rqqd0HqGkzTU7JPy9twDyaj6un7qWOkNcXNDx/g9vPQyv42JOO44KE5sjc sJtVdJ1AVuOcCr3izni0EW+/nh8HB0VCDAq8bK2Jpw5u60x79m7ILuy+hK5E647lNwN4qOsSZg+f YhVZG3Fpf9P2WwOdPRT3EWlMd754CMBw7+ErSKQN7lw8ITGaNmGHCZF9ZXtfSxIkZLsbHZnckpWa LvahyBjmQxBKOzsmHW0N+NPiHPgn+dyxhvT1Z5EPOIlpyGKEA1x50oTQDUtseoetsROuM82YMzIj 8EU=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/zu7VWyIHCGT9uxcN9EnUuCn30M8>
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:51:39 -0000

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.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email