Re: [Rfcplusplus] Conversation as metaphor

Ted Hardie <ted.ietf@gmail.com> Tue, 10 July 2018 18:15 UTC

Return-Path: <ted.ietf@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 BEF6C131028 for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 11:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=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 8SXNrNVwcPAu for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 11:15:53 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::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 C91FA130EAA for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 11:15:53 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id r16-v6so44452917oie.3 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 11:15:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=4c2NfTlKpvFh9fqkdOgsuoADV+wScd91uniUS28PvgE=; b=Gd+bvSiKPjHGufpDBqf3Y9WPETNCrPGoPTt5c5St7mRuTLYy84nFbAd0nNY40n6TLx Neu8U1QuSKEuu//dPHT48myM9iSsQ1z7mjMZPeX+1NWZ1Dx8cxAALrMUUZGe/GmvBqSM MqndfjDSyONRJbahL6UKvcjQ9KpeKJoJBWfxYui1k9o9jPtxOlv7UcxqI4IVFNT+Zl0b ZScrcg5ZPOZH76VvcKfdobfbiLgD/xdWdyr6msQDUXPZ0n2AdKD8oLU6AVIZdPQRgKPG p0jiNMtUc0R3inteO79YXl5UAOin4n/K4hhJ3XquuS6TyYiUZ7oOx2uUMepzmbyET0Bq LISA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=4c2NfTlKpvFh9fqkdOgsuoADV+wScd91uniUS28PvgE=; b=bpSuYS93eSuiuLZvymR3oYu1VC61mtui3wCb9j6T9QPgwcpPFehoW9U/z96/+hofDO O9KzMWgob33BUoK/Sqa87teCxcn5ddsErc/uNCuDTumJwrX5nwmwqJRH8rF6+YIscvZv sdgIarLh/nwpq4jlopFV53kYvGjK3z1iNK2jrs3LUkcDJr95lw8FpIAQpHmQ8SEMM3ex tJEXL90n+IWB+EKSpg3Q1pxwvV+6ribXHP9e/p7Cxiv8w0sUL30gtMwI5FjaA1UKNnDd Tt9HbO+5SRZCu64EA1EIQREbKWP92fPRWqShKP/MokHMRFwqixVYji+onlm3CWJhBx72 A3lg==
X-Gm-Message-State: APt69E3BMoMJUwsSu8f5gmAkfksS+/r1vErBSMwtW4cL+OjpC9bED5/y xhvAAR3mUa/h1hbFSkrFi+c6A3yQOYDrEyHPyHU=
X-Google-Smtp-Source: AAOMgpe2b3uC8Hx4XUikuWsdczqydiLQgQtXtsNUyvz3b1XyEu7lIxwXDkRi6TP6h6WN4rJoS1l73eBJUm4tH/MbHvw=
X-Received: by 2002:aca:3c45:: with SMTP id j66-v6mr26702688oia.118.1531246552876; Tue, 10 Jul 2018 11:15:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Tue, 10 Jul 2018 11:15:22 -0700 (PDT)
In-Reply-To: <a4b50286-5c54-e6cf-9087-7171030b7fca@juniper.net>
References: <CA+9kkMBVC82qy0hbUbQKm=OsFPsaJUPndtVaxd782au6Qy0w6Q@mail.gmail.com> <a4b50286-5c54-e6cf-9087-7171030b7fca@juniper.net>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 10 Jul 2018 11:15:22 -0700
Message-ID: <CA+9kkMB7rJ7KHkpMxu5wUzQwva=qZ02-7C71YttQ5upXvjB5oQ@mail.gmail.com>
To: Eric C Rosen <erosen@juniper.net>
Cc: rfcplusplus@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d90b300570a91e24"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/wh3NLoYW7YQQJ8hoExtNQ8PyBoQ>
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 18:15:57 -0000

Howdy,

On Tue, Jul 10, 2018 at 11:06 AM, Eric C Rosen <erosen@juniper.net> wrote:

> On 7/9/2018 11:24 AM, Ted Hardie wrote:
>
>> the academic community's failure to value the output of the IRTF
>>
>
> I don't understand the relevance of this issue to anything being discussed
> here.
>
> If a RG wishes to publish its output in a respected academic journal, I
> don't think there is anything to stop them.
>
> I meant specifically "output as RFCs", sorry that wasn't as clear as it
needed to be.


> Maintaining the current publication process for RG output but changing the
> name from "RFC" to "IRTF-Masterpiece" is not going to make any difference
> in how the academic community values the work.
>
>
That's not what others are saying.  The problem as it has been explained to
me is that tenure committees and similar academic assessments look at the
output of the individual in part by looking at where the output has
appeared.  When it appears in a series which looks to them to be primarily
engineering specifications, it is not valued as highly.  A differently
labeled series which was entirely composed of research output might be
valued differently.

I agree with Eliot's earlier point that this is a "might", and that the
value ascribed to it depends not just on its output but on the work done to
highlight the stream's output.

regards,

Ted