Re: [Rfcplusplus] Conversation as metaphor

Melinda Shore <melinda.shore@gmail.com> Tue, 10 July 2018 21:49 UTC

Return-Path: <melinda.shore@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 C572D1310FD for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 14:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 g352qyp7Y4tF for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 14:49:21 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 D9DC9130E90 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 14:49:21 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id c21-v6so12351093pfn.8 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 14:49:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=FB/faFE1YaVpBE9qVmD7N09jHfW+Ng+3pEuN7Y6yghA=; b=RGBumY4wXedvsSTyFsYZiSqPgrXRA76jJ3ZApcM5EIB+oE4ZrptFyprKxaMQ1IAbi1 UfM9bSYrbdxCBr56C5CEsj48z2ruKQVVorPapt3/dA/K9Ad2thcMb/8YuRb//nthdFRY kE6Ntq/cXKSarmgzn4Ooz83kf2YUBuPW+K8hn8uquLRQstE2eTdKfHiwkSe95sAbD+IE OaHJJgaJdsIvIH3g0oGImtBcUE+Piqk3+uL62xB4cDtPI6uLEgugkjp3GMxtLczVS299 d3WNtHAXTv+ebN4DRG1UBNXwvl0T6iE3LdYqNSsIWLSTX7JqYOgVgXEA1b3/0She767H 4Dsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FB/faFE1YaVpBE9qVmD7N09jHfW+Ng+3pEuN7Y6yghA=; b=Q7TPaFWCFsYK3pxGw4CG6R0dDqrHRneyp5kaQFzxwSDBqmDtt/L9tyZ1cdugDATTiB Gma+Wi6nedzx8Hazr5Ik9QLKz6UT0K5Pg+gm4AvRSGHkMfFLSwBpK5RsPTAWQqxSKUMq BQPSQ7rZq3eLX2J52ab1AGUdZb+nuupqFoKPFRWISVYHGxqSigHQFSHaw0owJoAkFiGf 0HNEdq1eNXYPcrgzPofsV763OV87UgmI0nQq3bISJlFeYXPMXr5dzz+udmlWTiLm0wX+ OrY9DhH7hfaFqR0TNCwegcF8HcInPTBp/79j+G+RjdOmNdL/tG0AnwSxhHTeeppdo9Lr pBfw==
X-Gm-Message-State: APt69E2BQafXNS/QtNaDFvDTmjqxIYffHue0Yz4nagK9z1rqbyJR3z+z MB8nZn1ZYCwGY2yQVkxgLfRYFA==
X-Google-Smtp-Source: AAOMgpcCgKl/q/aTWCe+YudM2T3XmIBYdYrRxxcvWkY9WYcp+EsOSMbL8sJlwpirPdW/E1xHuz0LsQ==
X-Received: by 2002:a63:1126:: with SMTP id g38-v6mr22417725pgl.122.1531259361157; Tue, 10 Jul 2018 14:49:21 -0700 (PDT)
Received: from aspen.local (209-193-22-151-radius.dynamic.acsalaska.net. [209.193.22.151]) by smtp.gmail.com with ESMTPSA id b12-v6sm2631003pfe.148.2018.07.10.14.49.19 for <rfcplusplus@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jul 2018 14:49:20 -0700 (PDT)
To: rfcplusplus@ietf.org
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> <CA+9kkMDwOuLOJMzBSowqga-6s0GnO=03PBScOaHRcJT0+QYicw@mail.gmail.com> <1F7626CA-FB10-402A-BCF3-EA89526AC63C@gmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <06a2ec62-8c83-cc0f-9b28-c285f7b77602@gmail.com>
Date: Tue, 10 Jul 2018 13:49:18 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <1F7626CA-FB10-402A-BCF3-EA89526AC63C@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/aiO3nwsomWwuUJvd2RT0CSCWsuA>
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 21:49:24 -0000

On 7/10/18 12:23 PM, Aaron Falk wrote:
> As the IRTF chair when this stream was formalized I should point out
> that an important reason for RGs to publish RFCs is the same reason that
> they are RGs in the first place: to have their work be adjacent,
> influence, and possibly migrate to the IETF. Of course, that is not the
> only reason we have RGs but it is a good reason to have non-standards
> track output in similar format & repositories as the IETF.

It's also probably worth mentioning that academics produce output
other than research papers, and we've got at least one instance of
a researcher who's got a protocol spec they'd like to see published
as an RFC through the IRTF.  It's already been submitted as a draft
and that draft has led to the start of several independent
implementations, and may be used as foundational technology for
other work.  There's at least some value to academics in having
an I-related publication stream available, independent of whether
or not an RFC carries the same stature as peer-reviewed publication.

Melinda