Re: [Rfcplusplus] IRTF stream considerations

"Diego R. Lopez" <diego.r.lopez@telefonica.com> Wed, 11 July 2018 18:25 UTC

Return-Path: <diego.r.lopez@telefonica.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 45A8D130EB5 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telefonicacorp.onmicrosoft.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 WfsBGov7sL_A for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:25:39 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10113.outbound.protection.outlook.com [40.107.1.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D48F130E69 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telefonicacorp.onmicrosoft.com; s=selector1-telefonica-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PV1Gh4J375IEoGJE0UkVUAtnmbHT457sK8RRoJeXQy4=; b=z3nq0NxMykSZnq0W7DyDgkSNiWaPaGtssc6wZJBpBF34ab/D/x7fIC7YhhXGvBeVmFq0pks+kvRCte68/KtJPE61tSxc1mwlhhDfd0ZbJtAo9kkfti9f1DgPHOMOY9vTWYq3vdEH+5Tq1z4nsUo14D/GanP48oVnWHwZGVcjgg0=
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com (52.134.70.148) by DB3PR0602MB3724.eurprd06.prod.outlook.com (52.134.73.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.930.19; Wed, 11 Jul 2018 18:25:35 +0000
Received: from DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::e8a7:c15c:d575:4c71]) by DB3PR0602MB3788.eurprd06.prod.outlook.com ([fe80::e8a7:c15c:d575:4c71%4]) with mapi id 15.20.0930.016; Wed, 11 Jul 2018 18:25:35 +0000
From: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
To: Aaron Falk <aaron.falk@gmail.com>, Allison Mankin <allison.mankin@gmail.com>
CC: "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
Thread-Topic: [Rfcplusplus] IRTF stream considerations
Thread-Index: AQHUGTxLx6gd/Dkh0kSKiNWESO+u8qSKVgOAgAAy6oA=
Date: Wed, 11 Jul 2018 18:25:35 +0000
Message-ID: <D0D37CB1-F06D-4DE5-A0B4-D9374E8BEDC5@telefonica.com>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com>
In-Reply-To: <D837AAE7-E5D0-41C7-8DC9-6EE44F61112E@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.f.0.180701
authentication-results: spf=none (sender IP is ) smtp.mailfrom=diego.r.lopez@telefonica.com;
x-originating-ip: [87.235.190.32]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB3PR0602MB3724; 7:t+zuvAI4M4HpYa+g5RNH1V5Cy9xoQ6YvU93f8AgxmvQZ2FAUZTiFoUwAOkTISzIO0zmt/+iJ4q/jmL+G/3MIy2OEMQ9IShNIMEy6qjOlyd8qgUh+IG5FVim2NvpadOqIjA2WWaFC1phS+BSCnd+1RiA6uuvEETmh2/GTdiw0WbUe4qv49sUadYBoXl87ztjIrXOABR+/F+xcUOvDLcKPfFryxigGMbBS7JKrwrolGxOS7kOK2ZpeTgBe72sV6Hfu
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 92bb7df3-f3d7-4e02-f6b0-08d5e75bb1b8
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:(40392960112811); BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(48565401081)(2017052603328)(7153060)(7193020); SRVR:DB3PR0602MB3724;
x-ms-traffictypediagnostic: DB3PR0602MB3724:
x-microsoft-antispam-prvs: <DB3PR0602MB3724840679575B23E2586FDBDF5A0@DB3PR0602MB3724.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(40392960112811)(223705240517415)(85827821059158)(128460861657000)(21748063052155)(81160342030619)(17755550239193);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3231311)(944501410)(52105095)(3002001)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:DB3PR0602MB3724; BCL:0; PCL:0; RULEID:; SRVR:DB3PR0602MB3724;
x-forefront-prvs: 0730093765
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(39860400002)(376002)(366004)(346002)(252514010)(40134004)(25724002)(189003)(199004)(53754006)(2900100001)(229853002)(7736002)(2906002)(53936002)(8936002)(99286004)(786003)(966005)(58126008)(316002)(33656002)(561944003)(478600001)(66066001)(4326008)(3846002)(36756003)(110136005)(39060400002)(14454004)(25786009)(68736007)(6246003)(606006)(486006)(83716003)(6306002)(54896002)(6512007)(26005)(106356001)(236005)(82746002)(6486002)(6116002)(105586002)(186003)(6436002)(446003)(97736004)(6506007)(8676002)(5250100002)(76176011)(45080400002)(11346002)(102836004)(2616005)(81156014)(53546011)(86362001)(81166006)(256004)(14444005)(5660300001)(476003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB3PR0602MB3724; H:DB3PR0602MB3788.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 22S+4mXREyBXkKckGhXkl1KupJeDJP509EjK7pmpBZFYxKnK2dXiekaRxCxDn3bsuDvftfrcQq23U44Aj1BlwdzEH+6yQD94G9XNmZFXpfe0spg3qey0bZE3NxwGOwYO2fobyzgcrhPFNjapk986rnZFx5CyKzFEq711rz9tjmCW5Qvh/ZqD/qSDy6cdIMfN7ptzcWXD69IZH1eV09pgHVrdT/Ds/8qpp20+8T+Zn3ycdK3PNr9ZvblplEPvnMU92Wx2oGRAGRlV8zdaQ5rXB4Fv2ETFbNae3cacLH47UrcUdyVdEyZhWE55+VGEirWgBjbVvLeawl1E5sxVficHwdiiAU6e0UFjxQP6hmbQVRE=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_D0D37CB1F06D4DE5A0B4D9374E8BEDC5telefonicacom_"
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 92bb7df3-f3d7-4e02-f6b0-08d5e75bb1b8
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jul 2018 18:25:35.1041 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR0602MB3724
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/y43SQ-CUGMdiMGG5s2j8-ygDiJw>
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:46 -0000

Hi,

And, as shepherd of an IRTF document awaiting IEG review, what would be the fate of those in the queue?

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lopez@telefonica.com<mailto:diego.r.lopez@telefonica.com>
Tel:         +34 913 129 041
Mobile:  +34 682 051 091
----------------------------------

On 11/07/2018, 20:23, "Rfcplusplus on behalf of Aaron Falk" <rfcplusplus-bounces@ietf.org<mailto:rfcplusplus-bounces@ietf.org> on behalf of aaron.falk@gmail.com<mailto: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

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição