Re: [Rfcplusplus] IRTF stream considerations

Allison Mankin <allison.mankin@gmail.com> Wed, 11 July 2018 18:09 UTC

Return-Path: <allison.mankin@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 61020130E8A for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:09:16 -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 bs4Xa3nbCCHF for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:09:14 -0700 (PDT)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 D151C130DF2 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:09:14 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id y8-v6so18914521pfm.10 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:09:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wM9+hDoPYwJXeSwUtM7+6+ryXqAm7nUOMqyJxUn6NCU=; b=RE5KQKK35e4x4Uis9wYHC7svD+CY1G/xmLJZ/a2TfxFKKr98wd5AVImygC9Yp1y0sG TCbkvrYGVPJ5stA7ATwCl9Ewt5CudWA+zIWmQtiYH6mIB7lr8T3eCqDYHIsYhlEac7E3 kuH9Qq5SnayO5WRLc0un4lB2ApQD+Zf7GFnlbUP8zdj/zjrDRnVKFAFcebqMeObInMWI fRJTYzIr43JGtXhohn9pzEVJq9ERDQTR7MeXQnwSjC9mQOxcssAx+KBPN5i0Zz1y97wG Sx5mwk2KeKNTkDcUmb7khrGX67FMoTA5MtTrAXQ4/AJNA1sxJP2U7Enz4u9TBE8izmyy Y99w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wM9+hDoPYwJXeSwUtM7+6+ryXqAm7nUOMqyJxUn6NCU=; b=kk35SbySm7waDC60DWi7gE876ykJ6GLVqfVs1vVRDXrvQOmBxLy2BTNPLanfw0/cvc f2JPLo4vdJww/X9OQm/D85asIvvjMlMBQUVCunoA1E/GG2Y/+6uZJvAHP2yiFOSofWXY 9oe3JxLYeaMMPwpjt9bXwM2Gmz7oj+AbKPHLIs0CFf6rGrITFpTmVAwd++4uOwNKRnz7 MhY72td6mrpBcosbB5dW14IrX5tZARpbDW95Ith3JhRQ2aBqij9DNLBGMfwOUesFAuZp si/VeYXPATzpK2rML2jmgnOcvg9WOirNGicRYSw82vcwZIFvyLnwYB7bJQ7D9kJfnbf9 Xr+g==
X-Gm-Message-State: APt69E0pv09FNl1cyO4+WEuJ1SJOQhQyRxa6pB84d2+DZ36kzFv93HfO b5Uzh0/vbZ3oZuYSG1T3/uwTT39nFDkHfqXLKsM=
X-Google-Smtp-Source: AAOMgpe7/9ghAdEikVTHbeSRt3a9MEe5sWBg3ZzMLc/4bB/VygtEDyaS12w3XFxczzABZw67Voo2u+GCJQtEKXjRLS0=
X-Received: by 2002:a62:5984:: with SMTP id k4-v6mr30832004pfj.116.1531332554415; Wed, 11 Jul 2018 11:09:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:ac18:0:0:0:0 with HTTP; Wed, 11 Jul 2018 11:09:13 -0700 (PDT)
In-Reply-To: <844ec8ff-26b9-4314-d71c-b75a00f3610f@cisco.com>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <844ec8ff-26b9-4314-d71c-b75a00f3610f@cisco.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Wed, 11 Jul 2018 14:09:13 -0400
Message-ID: <CAP8yD=vaz8KctOq-Hw7j8iND4OPuxiOyhbuqOuwAybnqLtkr+A@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f061690570bd247e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/_AP8-hAQEHhdeLPh_kBC-r1sfw4>
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:09:17 -0000

Hi Eliot, I see HRPC as a New Thing (though it need not be so forever). It
mingles social/political science research with protocol research.

There’s another angle on how we handled the HRPC research considerations
document, as well, which is that IRTF can have more varied consenses.
RG/IRSG consensus can be different in scope from the IETF-wide scope of
IETF LC/IESG Evaluation.

On Wednesday, 11 July 2018, Eliot Lear <lear@cisco.com> wrote:

> Hi Allison and thanks.  I'd like to test you on one point:
>
> On 11.07.18 19:26, Allison Mankin wrote:
>
> 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.
>
>
> What would have been your preferred handling of the human rights
> considerations work?  Is that closer to a CFRG recommendation or a new
> Thing?  Please keep in mind that many of us were comfortable with that
> document going out through the IRTF as it was, precisely because it WASN'T
> an IETF document.
>
> Eliot
>