Re: [Rfcplusplus] IRTF stream considerations

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 11 July 2018 23:49 UTC

Return-Path: <brian.e.carpenter@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 79E6C130E73 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 16:49:46 -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 F-f4iOwJF2yq for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 16:49:44 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 43819124BE5 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 16:49:44 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id x5-v6so3341674pgp.7 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 16:49:44 -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=BYLoOmmWsh8/ykKU3x3HGsVD+g1m48NXO+dXqIu0oco=; b=n32b9+eOQussfA+8QDsuC5uW7Czu2Jy/vgHQUS+ZAgYk7qDRulSrzqC73Zfn9kEokR WTKvBD6LFNwvIBxuYAIw1Zj4S3lVqZZXlStA+KWmZrmbURGsrqMfcmWbWnLDhmtj0VZr kC3WlBL1UYj3X4DJF3vFk9hjGpYLj82O4Y1c41ISaFUsgKDDEJodKFL2glfPpFCFJF7r BQZq5mGolyLSmEDHAhLum7P/n4HfrVMuh6dru0ZTSNBW59ErfD5ae3Ue9PI/ShZcahiP SBIPSDwW4qkoltXIRu5+IF4l6I4R+JskmDOpRmWELGVBCtLKhXCqWXlAWD2gMXOVRYX0 KGhQ==
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=BYLoOmmWsh8/ykKU3x3HGsVD+g1m48NXO+dXqIu0oco=; b=WuUastcGxTyoEsYrpRKygaPMHinj46Kwx1ejYSKuUu2CAsGHg7CvLbJFQJXCdbOC+B W9xgbMOQvH9OewuUZstPFFQxs4V0X3LPByh5ew0WkM34oKvRjH/FBuZM4cxFHMRJdnqR XODtGq9QicqE3OLQrXIzsvT2K90YHFSIRDz1S+NjWaYpzLmO3GnTPefL9lCnafGfh0Bx KO4F8UA/dWEbYH3NJPQOS5GHccv0ERz1pO4AR0/IyglF7B6ZZtSsRfB2axMi8NdtuhL+ DRxdd3OZJBsidEZ3A4gQZ/ZoKKO6qBhLtarvNY/55r6DfawUrdsWRd5IvY5ea45Wk8sD Eylw==
X-Gm-Message-State: AOUpUlFj2iL8HXIQj5m91wVTTsiKeUAINuQjK3Z+1mW5Lg1ndsUFWSmd yBVTj/iDdHNltSYNCi3rheiTug==
X-Google-Smtp-Source: AAOMgpeoDrwpvU/GQirZLtP8zGeFegpYWN+O656bT7BppjMSofFmEhDk4dtBMa6nlxzo4HH/DqonZQ==
X-Received: by 2002:a63:3f05:: with SMTP id m5-v6mr577423pga.51.1531352983403; Wed, 11 Jul 2018 16:49:43 -0700 (PDT)
Received: from [192.168.178.38] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id t76-v6sm57707755pfe.109.2018.07.11.16.49.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 16:49:42 -0700 (PDT)
To: Allison Mankin <allison.mankin@gmail.com>, "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b69b370c-317b-284f-85d1-1353c67a3043@gmail.com>
Date: Thu, 12 Jul 2018 11:49:46 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/jQHmeaGqN231LNIPfCQwpeUIxds>
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 23:49:47 -0000

Hi Allison,

On 12/07/2018 05: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.

Well, that's good to hear, but nevertheless it is an IETF BOF and that
limits its direct input to IESG decision making (certainly not its
range of topics). What the IRTF decides to do is its own choice, of course.

Personally (IRTF participant hat on) I think this is a very good thing
for the IRTF to discuss, and I look forward to the discussion when
it's brought to the IRTF as a whole. (I'm assuming this is not something
the IRSG believes it can decide on its own.) Others have mentioned
some of the obvious questions about the boundary between this and
the RFC series.

> 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.

Yes. In my mind there's a distinction between IRTF output that is indeed
"just" research, and IRTF output that directly feeds into IETF follow-up.
Of course, where the line lies is a judgment call.
 
> 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).

Since I haven't seen this discussed on IRTF lists, don't you mean that this
is a likely proposal from the IRSG for discussion?

Regards
   Brian
> 
> 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
>