Re: [Rfcplusplus] Conversation as metaphor

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 10 July 2018 20:45 UTC

Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: rfcplusplus@ietfa.amsl.com
Delivered-To: rfcplusplus@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 488041310DC for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 13:45:20 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=aB/ziKsl; dkim=pass (1024-bit key) header.d=yitter.info header.b=JpL7a3Pa
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 2KiVSqLfOqvS for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 13:45:18 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29E05130E35 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 13:45:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id DDF27BEBEB for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 20:45:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1531255515; bh=udRVV9pSFNBiYs8rVQTFUwhpL1aQsrVPymckxLnqCoc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=aB/ziKsl6phK15tQRPKQWiLvsPf2nylXJR9zvdRU+joyi2UJq4waEQcxAsRlENa0O yYYKFFfB0WTBrqKTbpt2pG56OpUeWefhrUUBZc/f1SXCpGL8j2MS+cjVeHH3sCBWOB LGLri6ZJ7Y1VPkP4mzYmNxPKxDxXdG2H6ntQfhj8=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LAaWOtqLNre4 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 20:45:14 +0000 (UTC)
Date: Tue, 10 Jul 2018 16:45:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1531255514; bh=udRVV9pSFNBiYs8rVQTFUwhpL1aQsrVPymckxLnqCoc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=JpL7a3PaQkRSaQpfegSsBc/DbUGCizFN3PWqPbqqsKIKJylsc6WZuiSlDrs6XyHBr DnC4O5bUKWOQly4GHFBN/39Fwcyfw/ChUDs8lLkyT5TsXGfbE6gQdioy4yk8+clspN JaryslAMNoEY7SFnOSaVr0AAgaUX0gQ0bSaaT5eA=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: rfcplusplus@ietf.org
Message-ID: <20180710204512.GT20282@mx4.yitter.info>
References: <CA+9kkMBVC82qy0hbUbQKm=OsFPsaJUPndtVaxd782au6Qy0w6Q@mail.gmail.com> <a4b50286-5c54-e6cf-9087-7171030b7fca@juniper.net> <C9EBFF44-DB93-45E4-954D-2AC5E2F47D03@gmail.com> <20180710192810.GQ20282@mx4.yitter.info> <0e127473-902a-2421-6b5d-73f9e7f83286@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0e127473-902a-2421-6b5d-73f9e7f83286@juniper.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/CmIFSXHx-N7j_sA-fVjU9cm4Db8>
Subject: Re: [Rfcplusplus] Conversation as metaphor
X-BeenThere: rfcplusplus@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: For discussion of the RFC++ BoF proposal and related ideas <rfcplusplus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfcplusplus/>
List-Post: <mailto:rfcplusplus@ietf.org>
List-Help: <mailto:rfcplusplus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 20:45:21 -0000

On Tue, Jul 10, 2018 at 03:58:47PM -0400, Eric C Rosen wrote:

> certainly have no problem with that.  We shouldn't force researchers to
> publish their work as RFCs.  (I didn't think we did so, but ...)

Indeed.

> But that's really irrelevant to the main topic of this discussion. What we
> are primarily discussing is whether we should prohibit folks from publishing
> RFCs when they want to do so and find it valuable to do so.  That's a
> completely different question.

It's a distinct question, but (as Ted argued) I think it's still
on-topic.

But I think your way of describing this issue has a certain merit,
because you are in effect asserting that there is no benefit to the
Internet community in having a gateway function to the RFC series.
One proposed such gateway is IETF consensus, and the argument for that
is that some significant population of people seem to believe already
that the IETF is who is responsible for RFCs (see the remark I posted
yesterday about Googling this).  So, the argument goes, we should
align what we claim with the way things are on the Internet, just as
we might do in the case of our own protocols.

Others seem to be arguing that the RFC series should in fact welcome
anything on any topic, and as long as they can find someone willing to
let them in, there's no reason they shouldn't be in the RFC series too
(i.e. we shouldn't prohibit people "from publishing RFCs when they
want to do so and find it valuable to do so").  It is an interesting
question whether, if I wanted to publish an RFC about Wittgenstein's
remarks on colour, whether the ISE would consider it.  We do have the
April 1st ones, after all.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com