Re: [Rfcplusplus] Conversation as metaphor

Ted Hardie <ted.ietf@gmail.com> Tue, 10 July 2018 20:09 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 7D101130FCD for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 13:09:53 -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 rmOVWL5lTHEK for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 13:09:51 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 3CA551311AC for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 13:09:50 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id q11-v6so19481722oic.12 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 13:09:50 -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=qP/dGzHvPla1Qrw6iUiFwX2yfgAJZfS26UYc/Ajz+Aw=; b=iWZb1dCJPgH2PMUptPKPqPXWCUoZOhfWxc8iZENIrvMfsoxYxgdBzhHmxULIT03d05 7A8fnVT19ecAgiyhq4thtN3g+dRdkLlS7h5RMiqb19IKlqjC0iaVdazPgdLdmzyfa1ic g+VKeyUF3T+g7Hm5K1VgSD1zRIc/PEpzpKJS46nNpwjxgPYVYHtrEgmt8KVVLBiwXEsr 6zAlwASfeVa5TzLULBx9HWoEVEmkmVpLNuOYnvT6rv99/QHlfsWLHMiCpHSavrG9FZW/ pUMcYo7sMfnmG7hTkh0GKIMLyc80cB/8AfM0o9vAJ9a1AgL8mc5xNweFTznESFGWg36p XQLQ==
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=qP/dGzHvPla1Qrw6iUiFwX2yfgAJZfS26UYc/Ajz+Aw=; b=ezpyIBZjVU1p/fvsh1botnEQ0wz0sBePwIoZ2MYzJFnVm7wcxi6EGHOxBG34VVqWCX qsr9g6Rmvs8N4hadMGaz3fQiwAZohTgU3TL2GSx+vPjjjPHgXFpFf2dPhCXnkjHGQegc DXpY6Xc+HJYvMly/NRzuvOePSHPy7St2UGqiMTv59ubsFBrHQqRhgCmcPhGrCFbOvR7l s8d7Csg/IZGHPCMHLixY0+ibZzVbSlNqh7u0Qen4qK/t5/55neEwF8S99tFizsXRmO+1 ua7gfeLij5YmmJNL1VphrrVLvJE4jh0ffXuEjdO2cKOAmqJa/vXWeTVB23pR+h1oU19p l2/A==
X-Gm-Message-State: APt69E0jZ3biRQLrMadsLnxW9uVsk8Y3SYnR7RSp6zJalX/WmxGxhnJW LYYEGob8foNLbyHC5KZ11aXZMcTNpkXnqqD59+k=
X-Google-Smtp-Source: AAOMgpfdgvL4AJSzYrvtn5sUOmLfK5cQkXrF8qBH+IRYLLRhL14nD1n1r8CZZRqIbQdGgZdXLKXEULvgaKlIYtlLeCQ=
X-Received: by 2002:aca:6287:: with SMTP id w129-v6mr31372171oib.122.1531253389463; Tue, 10 Jul 2018 13:09:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Tue, 10 Jul 2018 13:09:18 -0700 (PDT)
In-Reply-To: <0e127473-902a-2421-6b5d-73f9e7f83286@juniper.net>
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>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 10 Jul 2018 13:09:18 -0700
Message-ID: <CA+9kkMDwOuLOJMzBSowqga-6s0GnO=03PBScOaHRcJT0+QYicw@mail.gmail.com>
To: Eric C Rosen <erosen@juniper.net>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, rfcplusplus@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005714cd0570aab6b4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/adjm0WZvxcpDD2iuMCPW-6ZZ20M>
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:09:54 -0000

On Tue, Jul 10, 2018 at 12:58 PM, Eric C Rosen <erosen@juniper.net> wrote:

>
> If the IRTF determines that it would prefer a different publication venue,
> I 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 ...)  If I were
> a researcher, I'd probably want to publish in a reputable academic journal,
> but perhaps my academic experience is a bit dated.
>
> 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.
>
>
I must respectfully disagree that this is an irrelevant question.  The
proposed experiment would establish new identifiers for the work of the
IRTF currently published as a stream within the RFC series.  That output
might (and I acknowledge again that it is only "might") change the academic
assessment of that output while retaining its other characteristics.  I
personally believe this question is thus on topic for a discussion of the
experiment.

regards,

Ted