IETF Logo Mail Archive

Re: [Rfced-future] Community input

Adrian Farrel <adrian@olddog.co.uk> Fri, 27 November 2020 20:23 UTC

Return-Path: <adrian@olddog.co.uk>
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 CEEF43A0AF9 for <rfced-future@ietfa.amsl.com>; Fri, 27 Nov 2020 12:23:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level:
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 mcQONSCC4VYx for <rfced-future@ietfa.amsl.com>; Fri, 27 Nov 2020 12:23:51 -0800 (PST)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 167593A0E67 for <rfced-future@iab.org>; Fri, 27 Nov 2020 12:23:50 -0800 (PST)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 0ARKNkaL002951; Fri, 27 Nov 2020 20:23:46 GMT
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 394AB2203C; Fri, 27 Nov 2020 20:23:46 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs3.iomartmail.com (Postfix) with ESMTPS id 2380E22032; Fri, 27 Nov 2020 20:23:46 +0000 (GMT)
Received: from LAPTOPK7AS653V ([195.166.134.111]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 0ARKNWD2031402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 27 Nov 2020 20:23:44 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, 'Eliot Lear' <lear=40cisco.com@dmarc.ietf.org>, 'Carsten Bormann' <cabo@tzi.org>
Cc: rfced-future@iab.org
References: <9D0D4CBA-677A-410F-95F3-5C452970B842@tzi.org> <88B51C37-9DD1-42B1-AE71-26B279A8CB1E@cisco.com> <468c74fe-1bdf-08e8-99a3-b8c6376d811b@gmail.com>
In-Reply-To: <468c74fe-1bdf-08e8-99a3-b8c6376d811b@gmail.com>
Date: Fri, 27 Nov 2020 20:23:30 -0000
Organization: Old Dog Consulting
Message-ID: <052d01d6c4fb$3405f790$9c11e6b0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLHBe6V49ZmeBVY+0/71IElyp1ewgHEwq5SActiqcen32i/EA==
Content-Language: en-gb
X-Originating-IP: 195.166.134.111
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25816.002
X-TM-AS-Result: No--5.774-10.0-31-10
X-imss-scan-details: No--5.774-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25816.002
X-TMASE-Result: 10--5.774200-10.000000
X-TMASE-MatchedRID: QfHZjzml1E/xIbpQ8BhdbLIGMNfiwa5N4GUI7stBirpLjXXGQy6nlCj5 3aEB5qDLrniTHHylWEx1jYNX3WIaFLZi82whfl/XMiMrbc70PffFdEMoTK7bMSNBWGZQkFR8pur QOvjX+YQjWb4w1a6vZN6Uoj2d4Up/1NhATl9WiiE5y1daw17SpW0TAJ1EuNBm5CL5Q9KAbJby0O MMa4h0v6G2av8NTWSXzzU2+MLrDVQdTvK9m3LsxiqRJ4M9q7OvwEM6ofA+CGObKItl61J/ySKve Q4wmYdM3UZhrlpuBAXQLWxBF9DMQcRB0bsfrpPIfiAqrjYtFiSDjjMaPWkhLv9dbobfp+QQssho i2h1WXdFPNqv4nkQUH7cGd19dSFd
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/-nXRAE98ApK9k517lkajLZSg1NI>
Subject: Re: [Rfced-future] Community input
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: Fri, 27 Nov 2020 20:23:53 -0000

We have a draft for every occasion...

>> We talked about hypotheticals at the last meeting.  Here are two to
>> bracket this discussion:
>> 
>>   * A change people would generally like (everyone who submits an RFC
>>     to the queue gets an ice cream)
>
> Knowing our community, we would soon get 98 messages about the
> preferred flavour of ice cream, followed by another 98 about the preferred
> spelling of "flavour". But isn't that the price we have collectively decided to
> pay for technical decisions, rather than voting? Why should it be different
> for editorial strategy?

I should point you at https://www.ietf.org/archive/id/draft-farrel-problem-protocol-icrm-00.txt

Adrian

v2.23.0 | Report a Bug | By Email