Re: [Rfcplusplus] IRTF stream considerations

Allison Mankin <allison.mankin@gmail.com> Wed, 11 July 2018 18: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 1791F130E91 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:26:41 -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 eiDEvpr74P9N for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:26:39 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 273EA130E69 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:26:39 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id l123-v6so18935946pfl.13 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:26:39 -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=TmPIDgoKfzBh+RkE1YHFF39d6g95o7UpoovVK4qU8W0=; b=C50frdFL7pyPor7t2YuEm/E5fjafK4yayv7/YZ8QuzEhghmSS5JOmkbRCumxKpCRpS 1SbAVZvvv+E+21hqY+2mq158Cv6/mloc2U3YBN4zCSG8TNFAn1tr2LYcj7IIUxbs9BM5 Qjn/FVVRzNyyxT/8/5Vw8pWhsUcWQHtzBAo2YbYKKw561xy2BWaXoTW/5IZkzgmfUHAR pB4exC5UijCQ+XJgPagoG5dtV7cjlNaqjNEunkzsLnSOTI+a/xxwqEzYwRAitDGyxiyz LhQsfkPqdyVP07GwTU3Hwo9rlo+MM4s65hahvQMSWLBTEiuh1m7/k1OE7lHju5OZQuwh +Xcg==
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=TmPIDgoKfzBh+RkE1YHFF39d6g95o7UpoovVK4qU8W0=; b=NQv8j3oA2OXotqAiBn8dO2wq82v1Ljl6XrBxd4oOtgKmt6nMS7pYNlP8PgIKfV4HBp hThMi2GmCpwMm8Exhbjl/lsIYZ3A1/6W3Hi47kfUX7PJFe3nrkJP6nY+jg7TwnPw5Y+M bBb632ek1vy/IMfsBTpD3TFtgQ4mcRv+iPkQhx4jyzAOItBvQtqhkcBfC1YpPQ5YmX3T CpBMqjpGlP0qJ2lEpRSwpbACmAAp6z5N5OmU7pACAKcOXaHHMz0vVtO/l3IRwIxWERuG kLGiN67aivy+1aWydAVVMCHxMEEIAAqRtKpdOud60bn+l4LNYM+VyEyTQxG95UicOGQs KXSA==
X-Gm-Message-State: APt69E1aEIZJsdyDJkoqd7cJc1My1lrhBnJGIbloX4N7qyYzq+vNObdx aQSBiHujwcE+XYhuSUkM1B9PcmpoJhGPLMQcXU3Qng==
X-Google-Smtp-Source: AAOMgpcnxxi1SvfZQPHBRtk1hhPASkJAdr8m1338JlqRV2XrMUdaYEEU6+39vGdQ+tLZCcU6VGkAyXUh027Rh6WZ3Bs=
X-Received: by 2002:a63:1063:: with SMTP id 35-v6mr26707624pgq.249.1531333598728; Wed, 11 Jul 2018 11:26:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:ac18:0:0:0:0 with HTTP; Wed, 11 Jul 2018 11:26:37 -0700 (PDT)
In-Reply-To: <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Wed, 11 Jul 2018 14:26:37 -0400
Message-ID: <CAP8yD=ubyhMgX7FReNxTiikJ_-hX8hW2vtk7w=tFzXY1P6fR5g@mail.gmail.com>
To: Aaron Falk <aaron.falk@gmail.com>
Cc: "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002f583f0570bd63f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/8X1TmXZ13yhDLfn-nYS5ZydDi6I>
Subject: Re: [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 18:26:42 -0000

Hi, Aaron,

What would be examples of the surprising?

I don’t see an IRTF more academic stream as being in the strict mold of
conferences and journals, if that is the issue.

Allison


On Wednesday, 11 July 2018, Aaron Falk <aaron.falk@gmail.com> wrote:

> Hi Allison-
>
> Can you clarify whether you are proposing to end the IRTF RFC stream when
> this new series is created or supplementing it with another, more
> academically oriented stream? If the former, do you believe all IRTF
> documents can be published either as IETF RFCs or the new type? (I would
> find that surprising.)
>
> --aaron
>
> On 11 Jul 2018, at 13:26, Allison Mankin wrote:
>
> (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
>
> _______________________________________________
> Rfcplusplus mailing list
> Rfcplusplus@ietf.org
> https://www.ietf.org/mailman/listinfo/rfcplusplus
>
>