Re: [Rfcplusplus] IRTF stream considerations

Peter Saint-Andre <stpeter@mozilla.com> Wed, 11 July 2018 19:05 UTC

Return-Path: <stpeter@mozilla.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 E5B0A130F6D for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 12:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 xWUMGNvzz3TB for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 12:05:30 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 CA3E8130F70 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 12:05:29 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id v71-v6so4143401itb.3 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 12:05:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to; bh=Mchysyr9dH1ElixwMr8bDXedwVR2MozA30/0HVDMNCU=; b=bnr57aJoScy1uvJDihIq4EuW57zUTh3hrwZCZXqFeSBLjIxTR9nA7bY0JqtmT4oDF2 K42JohRyyk9pZLJc/bV4+I2g2J7VOAA++mqj+Fa3iqBqwLnlGlusgW1TRD/H/C8DBeFo xZzVpEFtWOyZFrn94v0kjnIc+5ZsMNZdm6aCo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to; bh=Mchysyr9dH1ElixwMr8bDXedwVR2MozA30/0HVDMNCU=; b=rpT1Dapq3uzj75+ynx28HL+W/vfsgeQZCFbog7xLJbe+3bJCBVRubh0LwLlxA1QRyl nQg+7q+pvwHzsWaAqp5VbbHYBk3jfkSwcBZVbQD7pPctwyDhyc0cgtBJTa8XfyRYctAV akuXYaLuI7+C1adzsDHPo3vVQp+3HQMTwT2xFHnBZvOJE74zCfFM2UCA+gw3FsWxipae FH1sPxek8Klw9LJJsY3G3GPDd0qLs9HHrfP8O+enRAfAaHz75d4Qf9gqfoYt8oVNB9k4 jDfgz+xU8JPCrZkN49a8+NLZQEueWKxA3b+/XrLd7LY0TEPbmzznXabOykAWbIY+ubfT EOVA==
X-Gm-Message-State: APt69E1v1MyK5cxpBQo/MYc7wc4xHsINfot3Bkg1m1K1zQa7Lk/vKjRT Vk63NDORAiTO/0o5KT2MZ8RWtw==
X-Google-Smtp-Source: AAOMgpePRq99g3poyIgoeTNTCwos3v5tlhqe+fXKVtkZb01Cy/jz3Onw23IOcYJA06f6JHGPjDtF5g==
X-Received: by 2002:a02:687:: with SMTP id 129-v6mr24787126jav.59.1531335929025; Wed, 11 Jul 2018 12:05:29 -0700 (PDT)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id x17-v6sm7709978iob.6.2018.07.11.12.05.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 12:05:28 -0700 (PDT)
To: Aaron Falk <aaron.falk@gmail.com>, Allison Mankin <allison.mankin@gmail.com>
Cc: Rfcplusplus@ietf.org
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com> <E0A1C6A1-73C2-486C-874E-C99E2EA33575@gmail.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; prefer-encrypt=mutual; keydata= xsFNBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABzSdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT7CwZQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekM7BTQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAcLBfAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <9690a162-b4fa-4857-f890-4fb3856273d5@mozilla.com>
Date: Wed, 11 Jul 2018 13:05:27 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <E0A1C6A1-73C2-486C-874E-C99E2EA33575@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="PdHtOJoZYMn9wg3OxZt79MGWGW4fjRaSz"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/Tt4oDY7DNQND28ojvC5kvGK-Xlk>
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 19:05:33 -0000

+1!

On 7/11/18 12:25 PM, Aaron Falk wrote:
> 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
> 
> 
> 
> _______________________________________________
> Rfcplusplus mailing list
> Rfcplusplus@ietf.org
> https://www.ietf.org/mailman/listinfo/rfcplusplus
>