Re: [Rfcplusplus] IRTF stream considerations

"Aaron Falk" <aaron.falk@gmail.com> Wed, 11 July 2018 18:25 UTC

Return-Path: <aaron.falk@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 215B2130E91 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:25:32 -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 dHsqXYhJguXJ for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:25:30 -0700 (PDT)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::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 B95CE130E69 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:25:29 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id a5-v6so7377560qtp.2 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:25:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:embedded-html; bh=d4gB1srrcBDUCi2/ZHJoSZoyLPIWtvzPGABqLS417aU=; b=mTsF0v9y2uFxoDsi2LbfJ7BcsIudxcCxKhrv5yeUrYVg7nAZ2nprjGa5t1bdo5MWlk 17I+R2dwF+VhoTr14s/9zaAlavtQMlnyfxvo14aJxyuDT1IiBUTe5p0R6aClXd6sDSOQ N5TOLlmREbua+lyygVJb4q9kMdnbAMh3+439krDnKMgUsa9R8yhbI3KXfeY/g8YXX3Dy yYCCNY16mzrp6BcIwjtaMmIxxoYwrMzJ4zPNcOtWHTbSViUOV4XpTOoKsTTGjVt2sp6U Wy1nJeTiUFWrdspHMvAl3MDSml8/ayuZ4ihFwF0nsFk5K7rnbcbbKJewN0Hl7uVGiW3A LKcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding:embedded-html; bh=d4gB1srrcBDUCi2/ZHJoSZoyLPIWtvzPGABqLS417aU=; b=GHwy7L0SkXHG4p0+oIpM6ytdQrlMTIA92jxhJvcv7LtoLjxt43fmqwpSK1UCWveY6z cB09hrVoY/gDwTyqZMOPLW3sxJJdLJ6bu7DdwsTkUsZtl7W/O5Y2NQmxQbM8SLxI5I12 HnzUbXz8/SW27ZXM+GsPiv/9Ah0HsLYo3M85ufbl4fp9jm6yY+GaB3o3jOz120iPICH+ b2iCAHnlw7BdQKt+AWGiZPOHQvM4vZHpYrQ3zbQppNnSDnvQIeDA2uOUbhAFLhoDxGTX i16Kpz+J4h5C9PoLlIM/SMxZrwpBiIdql2UZxSsLWoy5M2nkFMwTB5IJNfWln5PvCd5g KZYw==
X-Gm-Message-State: APt69E26bXcp5PaFJetQAw+3qi6eUJLpL3qJdFl83kyIJPKtvbmpMRzj l7/iqQeh9XfqHG9BlUzhv6c=
X-Google-Smtp-Source: AAOMgpd0k2dSBZT4BveF9o8NARcbxNbAW0TM2XBM/eqwA85I+PI7Q51bo4wzfRz+zJ3Co2639W3B9A==
X-Received: by 2002:ac8:1c28:: with SMTP id a37-v6mr28539169qtk.298.1531333528792; Wed, 11 Jul 2018 11:25:28 -0700 (PDT)
Received: from [172.19.33.154] ([2001:4878:a000:3000:c4e6:6bd4:d487:2f5e]) by smtp.gmail.com with ESMTPSA id l7-v6sm15938084qtc.27.2018.07.11.11.25.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 11:25:27 -0700 (PDT)
From: Aaron Falk <aaron.falk@gmail.com>
To: Allison Mankin <allison.mankin@gmail.com>
Cc: Rfcplusplus@ietf.org
Date: Wed, 11 Jul 2018 14:25:26 -0400
X-Mailer: MailMate (1.11.3r5509)
Message-ID: <E0A1C6A1-73C2-486C-874E-C99E2EA33575@gmail.com>
In-Reply-To: <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_8EA2C93E-B44E-49BD-A33C-89EFE652ED65_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[589, 5041], "plain":[210, 2568], "uuid":"4110A28D-78B5-4ECD-A904-F0B7A7C5D2CC"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/mt3PM5E2aBt6Zpy23ri6ynaiH6w>
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:25:32 -0000

Sorry, I forgot to mention that I think a "open, academically reviewed 
proceedings/journal" is a great thing and will be good for the IRTF and 
the IETF.

--aaron

On 11 Jul 2018, at 14:23, Aaron Falk 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