Re: [Rfcplusplus] Conversation as metaphor

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 10 July 2018 19:28 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 701CC130E51 for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 12:28:47 -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=USgfhT1S; dkim=pass (1024-bit key) header.d=yitter.info header.b=czIczwuo
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 06DTcXmC82Tc for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 12:28:44 -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 B4CCA130E17 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 12:28:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 08E7BBEBEB for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 19:28:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1531250894; bh=p/oqoZRrOlIpjOJlyhey49ot8kvLfD8YWhU3ZWLBB88=; h=Date:From:To:Subject:References:In-Reply-To:From; b=USgfhT1Se4xQ/LM3KW6tSGJfFeRy6jCMULLfGxdivmEPS9o7Tc2TCLAo519uWoA55 8S6gB8evO4G72WnyNAvS843szl7xjtUPeArgAZVJuHS4YTjvYePgGYWRkW+wVIPV1l cZZp7Poz0HZ+dXv5Z+BkzhicYtiRtjLh3QY2ZXn4=
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 IE7defSpWNsc for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 19:28:12 +0000 (UTC)
Date: Tue, 10 Jul 2018 15:28:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1531250892; bh=p/oqoZRrOlIpjOJlyhey49ot8kvLfD8YWhU3ZWLBB88=; h=Date:From:To:Subject:References:In-Reply-To:From; b=czIczwuo927shfv9mwXcyrOg3rD3BLZuotxc8HzYlO9G7MEJFYd/jeOdYRACcMur2 zD1F9ITKdYiSDkwZBdqFsowF5Dx4exNKJo5tW4n0WNOJL0H3WjOKgYFw/2wm6ZvySA qBhfOaw2mPYDIeiWTfShdwisMX6abWxoMnGxdKjY=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: rfcplusplus@ietf.org
Message-ID: <20180710192810.GQ20282@mx4.yitter.info>
References: <CA+9kkMBVC82qy0hbUbQKm=OsFPsaJUPndtVaxd782au6Qy0w6Q@mail.gmail.com> <a4b50286-5c54-e6cf-9087-7171030b7fca@juniper.net> <C9EBFF44-DB93-45E4-954D-2AC5E2F47D03@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C9EBFF44-DB93-45E4-954D-2AC5E2F47D03@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/vOzvg2Q8QU3rFX_xg7TzRJbVdaE>
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 19:28:48 -0000

On Tue, Jul 10, 2018 at 12:19:58PM -0700, Bob Hinden wrote:
> Worse, I suspect it will make it harder.

Of course, as people have pointed out in other threads, we actually
just have no real data about this and our gut feelings about what
might happen are not a good guide.

> The RFC Series is well known, the “IRTF-Masterpice” series will be
> new and not trusted.
 
One thing we _do_ have some data about is the low regard in which the
RFC series is held in many academic contexts, because it is not
considered a peer reviewed publication and because it is often
considered a series for technical standards rather than for academic
research.  That is data that has been provided by various IRTF
participants over several years, and with few exceptions I'm unaware
of that having changed in any large degree recently.

A different series with a different publication standard might have an
easier time of getting acceptance for this role than an established
one that "everyone knows" isn't a peer-reviewed publication.
Certainly in the mists of time when I was still an aspiring academic,
it was easier to establish a new journal's reputation than it was to
rectify the reputation of a journal that was widely regarded as having
passed its peak.  Rather than speculating, however, I'd be inclined to
do some research on journal ranking in the past decade among computer
science people.  This is again something that I doubt can be done
without some investment.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com