Re: [Rfcplusplus] Conversation as metaphor

Bob Hinden <bob.hinden@gmail.com> Tue, 10 July 2018 19:51 UTC

Return-Path: <bob.hinden@gmail.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 B31DB13104C for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 12:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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=gmail.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 5IaXlboXSi5U for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 12:51:31 -0700 (PDT)
Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (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 B8F861310CD for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 12:51:31 -0700 (PDT)
Received: by mail-pl0-x22b.google.com with SMTP id 31-v6so8069335plc.4 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 12:51:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=t9uH8LJNMwsQrO0NoMOI9Rp2OT1qFm2QsUOI5mAVW+g=; b=uqBlw4eC/4B9jEXqQn9xyK+61zlhA2wmMks9D4d2ggjpQkLbFAVEJjwb4k+9WDYotv GgrneL1JCiNuhfiD+pWrjNb50YkEKZ+v3wEgXzh8/6lswAqbY/AvvNl4Fac6YLOmIWwF 5g5GH5HIGBtmvOYW5ONmtuOdREjmDZsJLvy2r6JV3HKBlTUKwMocSO+Ou+wRUA4xd0uM IIgywn/bRCaHQrj6vUobDvIVXm2KmyAKv6hJd0LUtBtb67Ftwp6XyvYkicUdUw69hNgM o1ylMiYB493Ewxt8LN+HHTy7XiwOXOyYfozbLMjc8pGYE85XPemAGmK2AfCjTmY+Nr7M wR3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=t9uH8LJNMwsQrO0NoMOI9Rp2OT1qFm2QsUOI5mAVW+g=; b=Gt62+3MdfGlL828IKYKsTsm92H9DDL48KEwDeug4+oEbJAST3RC3mnMA6fubwFpOs4 Vns+uMG5CNnOa6NYBhBUeNkndJuLZbTDxHflIq7Lc4BGIac3Xdi1pqqwup0RFiW6FCdh BbvwR/I5/glGpszf0XdOzjkTbrusTKsnld3fiW/6xsukDNPA7m0ezplKjRVFDt9MUeUO TtwzBN0QHc9ezCk+zOv95/v/irjAJ+n0+nrp71zAT6GJblfbdCI6+PFBKyz4Dx8X3xyl m9X2VlWE7SR7SKz+SVAUiG2tM6DITX3DD0xDrueK5RPps3yhq3mvRHHnxIYaw5KgI1JP +yhg==
X-Gm-Message-State: APt69E230i15rhvfkUM3QkXHbH72ZnGzpQubzR8zA5/MZZqWnkBhUvye mnDP4F6KHL1EAD0X2WiRm2U=
X-Google-Smtp-Source: AAOMgpdLuhcEeVzwVMdLJWAS3s36BR3nvHz5Qu/tFrH9SO9ND05+gBn9jCox2PGwGcNhIojc0SdODg==
X-Received: by 2002:a17:902:7009:: with SMTP id y9-v6mr25776969plk.217.1531252291197; Tue, 10 Jul 2018 12:51:31 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id g23-v6sm24698280pgv.26.2018.07.10.12.51.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jul 2018 12:51:30 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <4354E24C-458D-4A6B-9510-AAB49C230D65@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5E3FF79F-BEA6-4411-A367-BDD9D2E0E79D"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 10 Jul 2018 12:51:27 -0700
In-Reply-To: <20180710192810.GQ20282@mx4.yitter.info>
Cc: Bob Hinden <bob.hinden@gmail.com>, rfcplusplus@ietf.org
To: Andrew Sullivan <ajs@anvilwalrusden.com>
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>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/x_xgtLhIOemWjZzlMaNm23amZ80>
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:51:34 -0000

Andrew,

> On Jul 10, 2018, at 12:28 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> 
> 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.

Fair point.

I think that’s a good summary for the whole topic of the BOF.   We don’t understand the problem (or even agree there is a problem), nor have we done any real research on solutions.

I continue to think a better way to approach these issues, is to hand them to the RFC Editor and let her come back with a recommendation.

Bob