[Rfcplusplus] IRTF stream considerations

Allison Mankin <allison.mankin@gmail.com> Wed, 11 July 2018 17:26 UTC

Return-Path: <allison.mankin@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 97D61130DF2 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 10:26:18 -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, HTML_MESSAGE=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 cRJeJcai1Pec for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 10:26:17 -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 073A6130E40 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 10:26:14 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id l9-v6so7215693pff.9 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 10:26:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Sw/veljJCPRDmSrRaIhKjsgpVTParyWkmcS/4VvI3dE=; b=V8/DqI7U0EFo/o0KBrHaCT1F2vugF137cprtZtIOK5wCseiJulhDs3j8YNUtHW6w/S MJ1NHXUmP2oF83lYsuI1p2lRSnyFV9fYn2DWY2LZIqZMFUUOZHicMbasSYpgZXNMcdJ/ 83OePr3Qt0ngcofibrbwqcsRZc6IQpqo9tIi02FGkkyZEynlcJbGP07jdVxdccww9PTb IKXPrF9iKlmGHuYJvhMnSUTvYs9YiWbib0pbmFA0evdithsUb+yHKUiXohfmYD+vfwXN CYHLZDgpWOBLHnJPLLstvKfoHncezVQGG4+d3uAbt1yIDEE+NV85jNlkJ6M/x5YdonOL 5ZYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Sw/veljJCPRDmSrRaIhKjsgpVTParyWkmcS/4VvI3dE=; b=cKNImzxdMb4H98hV6v+Kzh+gSv4ZxKeQj+VMhIhn3WTMqFvH52EZOHpsLsCWll/nAA 7+uGgzannxaLameG9Qt3w29yaeaqCrygF1EVfpgDZvCvwv9lx7Hoj5Xz17hqZXXNAJNh SYm7LS0yv6hm/ekM6a9y5+5FHVkBKWu8r5ZaMJUk+RCl2MWTeo4ffxKL3kjiiOxkb3DK 7nQLdqJPdVwrT5whXyJZICY78GrT5M9UsKtwF7cXPDv33jQARTSep3HfCg7QHkTIHyde wjxQYnGIQQ7EqjxuwKuim5viqlL4wYUdBaak2eEeP615RdoHWJl9ue6HY6mi9IFDgNoa ydOQ==
X-Gm-Message-State: APt69E2r6JgMC201o8rryxJyvMrIywW2iLCtuH8wY3e7aZeXv4cIPXrT U5Zzex7XrCwbyjvvq7aASl/T0vnZ9YXdziW4VdQ=
X-Google-Smtp-Source: AAOMgpef0/WehxYr1ZASwaUR/772EmtJjxwfZ4rgi7LQTsMQ0lTFoL2F3wi1DvnG6K6TnsrvjZ7/e+nb1SaJ1ogL4/0=
X-Received: by 2002:a62:5984:: with SMTP id k4-v6mr30685900pfj.116.1531329973289; Wed, 11 Jul 2018 10:26:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:ac18:0:0:0:0 with HTTP; Wed, 11 Jul 2018 10:26:12 -0700 (PDT)
From: Allison Mankin <allison.mankin@gmail.com>
Date: Wed, 11 Jul 2018 13:26:12 -0400
Message-ID: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com>
To: "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001788750570bc8b08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/vEAbeTWrduIQfpwToQ2to61JxHY>
Subject: [Rfcplusplus] IRTF stream considerations
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: Wed, 11 Jul 2018 17:26:19 -0000

(IRTF Chair hat on)
One of my goals as IRTF Chair is precisely to create a new, non-RFC stream
for the IRTF. So, IRTF is very much an interested party in this BOF.

The most common response I get during outreach into academia is that RFCs
aren’t a good medium for most academics. This is despite researchers’ wish
eventually to have ideas deployed. We’ve been exploring what work product
will best serve the research community, and . this does include
distinguishing the work from the RFCs. I like Brian Trammell’s discussion
in the “conversation” thread very much, btw; he has expressed how academics
and pseudo-academics contribute very well.

I notice there has been little call for data about IRTF and RFCs. I think
it’s because RFC does mostly signify a production brand. I’d encourage the
other streams to examine what makes them production-ready.

We in IRTF do have some work close to production, for example, CFRG crypto
recommendations. I would want to talk with IESG about appropriate AD
sponsorship when that would be the best context for a draft.

Other work we would like to place into an IRTF stream with a new brand. I
expect us to start developing an open, academically reviewed
proceedings/journal soon, to best serve our researcher contributions. It
will focus on applied research and running code, similar to ANRW.

In summary, IRTF is ready to start our part of an rfcplusplus experiment.
We are a part of the IETF community and indeed a part of this BOF (this
responds to Brian Carpenter’s comment quoted below).

Allison

——————-

Brian Carpenter wrote:

Ted,

It would be on topic if there was a proposal inside the IRTF to change the
publication venue for IRTF output. But this is an IETF BOF so all we can do
is discuss how IETF stream documents are published.

I know this is an inconvenient truth for some people, but there it is.

   Brian