Re: [Rfcplusplus] IRTF stream considerations

"Aaron Falk" <aaron.falk@gmail.com> Wed, 11 July 2018 18:23 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 0C5D9130E8A for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:23:26 -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 m4RUo76rdEHB for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:23:23 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (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 4B8A6130E69 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:23:23 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id z8-v6so13392669qto.9 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:23:23 -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=804pjxU8rBKdJATDTcMIxFSFEr7ZPN3W0MRExbB7gXM=; b=jnB9NHxhHLwz2vSV7zl/2ZaOKvMvyx1q+teqArLY/+UBVqVh+7efqueNJMuNQ1Tsy/ FACvOli1pA/O50hstpSS1yRtuMnhD3OFJQ3tsymUyF/+1+o9EKTn6/KhvkFKZKip1/sj KGqIsdAM60VAiUXIph8bYS0O5VfE+yPi+vcY6VmDIBzVf19dwgI/oZv7Gwe9PmzU3Bv4 C6sastfqP4/jW3VSIQBvdOAex3lA4lkZTXlFv/xwDmEQZCPrE2l0rcWpln0hBRSqBVJf XnQozm1O1KRnxcX8h/4UDVUTFSCroLLe4HzmA+grCBvnegNrSbpCFI3LR5JuphGhRvYm IFdg==
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=804pjxU8rBKdJATDTcMIxFSFEr7ZPN3W0MRExbB7gXM=; b=N/34omqbWCO76hoUGahTsCJ/dvTNOw/OHRRtLfOfoUh/lzZfq9RbnUgwq8yUFsRbfM Xcvr/BgRNGL2OXPxvzaecqsXgZerAsOuUAkzQrpp+aPwKdVjM07zl4bDcf9bShsmcph7 uEZe4eSSfoU0Sucu/4CKbNxqAuHO8hPZeY4fvQkMJs9MpI62keH34I0YR5rizEWNv1BZ qcEUOU2GblTeFUZhJSCzgN/oQLJvbXD1Z0UwNlwjHroiCTUWsJYy0YQCJ41WD/OJfLa1 FnsWuBdzk45P9+80KKdK9fipweeC9e28GcUgcdMUJaXqIBaN65/9Ri4O9k2jLLtOQjP5 lHFA==
X-Gm-Message-State: AOUpUlHVLp2rZezVVOTNEOwMWpB8FNHjHJ2dSuOjDDgs89aGRtBF4pyU qXQv2nJCE4XJpdfNEIjh8xg=
X-Google-Smtp-Source: AAOMgpeajhRQqX6Vt5v+3sA54vFnsLQe/esR6cpqPxfHO4BhtQfFma3Ml5EMDHPhHvV2XK0vyJtyRg==
X-Received: by 2002:a0c:ae17:: with SMTP id y23-v6mr441786qvc.157.1531333402398; Wed, 11 Jul 2018 11:23:22 -0700 (PDT)
Received: from [172.19.33.154] ([2001:4878:a000:3000:c4e6:6bd4:d487:2f5e]) by smtp.gmail.com with ESMTPSA id f17-v6sm12284587qtp.1.2018.07.11.11.23.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 11:23:21 -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:23:19 -0400
X-Mailer: MailMate (1.11.3r5509)
Message-ID: <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com>
In-Reply-To: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_4C48F6BB-FD13-4695-9163-D90A10630670_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[777, 3842], "plain":[381, 1973], "uuid":"707A1A90-A169-474A-8168-B46B7F86D1FD"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/1nZ-dLQqclVPKWGFjKUKTjuQPno>
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:23:27 -0000

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