Re: [Rfcplusplus] IRTF stream considerations

Eric Rescorla <ekr@rtfm.com> Wed, 11 July 2018 19:00 UTC

Return-Path: <ekr@rtfm.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 9E4AD130FB4 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 12:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 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, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 57t8UOT2-Rof for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 12:00:08 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 74552130FC7 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 12:00:08 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id q129-v6so6759180ywg.8 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 12:00:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QRbsysfkyzTfmbTD+Yqx+NCYmD3IY0DBAV0wasU7maQ=; b=lWn1JhRkqk8CvUTsrQsZmxRXxuhrbYpAUT+VFIC2GepNg1vfZWamoHu7Uy/X1UDIun v1sueXHuIsrHgfhUz2vyeEf9ctCvcg+0rtGSwA4AojJPozQtJyr4/VeMYQwwSJV40JoL RFt496cyH5ryv6k608Q1A4q5GZbVVE+uqe9WcuIcLmpXkLaIf+pQR2m0agWJ2a9ZfWK1 GlOzefY6xV6MA1B/HQPPz4pcZWI6BYVhOfvCpihdBXe+7Uh39cE7jaoGyngqQA5Uodta 16iskWin2HrAJOAHhWQfzM7KyE4uMQiNtjyfGxNjoPy3Sg4PbYr05bF98sBH2V8tOvLt LzUA==
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=QRbsysfkyzTfmbTD+Yqx+NCYmD3IY0DBAV0wasU7maQ=; b=qzItSJwoBXE+0TW8v9I1NYYgf5mNaNp+1TrJh04cwusYW2DoQUl1q+8lkx5nOImQax mq84u+YY+oA1YYuCQdEa4n42+Udu/+yENLJ/P2cGFwR1AYThHfN8k0F2XhWJukCxge6e ONk+9QyzmxvmfgA00ugXW71KQintlowdhqd2Fj1/dlYsRLxRrYvpwS3vGaHT77lBDeMA 1OqeklYt6Eqbks/ZmCqAIAnbiyQ+QzyGD822Oq+xqUuHNVvwi5vzERjaDpdP+R+NqK07 DCPglfOU5kCnyh8+wB3FeKJuGcZ2bM2tV9xej3Vn5U3nX01fpLdYY9IT0HZfjtC5LP53 minA==
X-Gm-Message-State: APt69E0N7KfzdgQljk9JAUhmeWaw+BOoxQRX3NjiVURBz0bmtNExeBXk A4mIjIwv3vptEoV5oLRToVloXCitp/mFiwgl8KBvcw==
X-Google-Smtp-Source: AAOMgpcHBJdA4eXd9RoLGk89RV4bnTcFr18B4ewCBwrHNi9Uo76acsBsAxgWiPImqd0J108FCxrYMu/bhP4wgHC+9gI=
X-Received: by 2002:a81:b642:: with SMTP id h2-v6mr15100790ywk.102.1531335607741; Wed, 11 Jul 2018 12:00:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a81:6b83:0:0:0:0:0 with HTTP; Wed, 11 Jul 2018 11:59:27 -0700 (PDT)
In-Reply-To: <5F79ECCE7999F4FD4FFC00A3@PSB>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <5F79ECCE7999F4FD4FFC00A3@PSB>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 11 Jul 2018 11:59:27 -0700
Message-ID: <CABcZeBPSJO4cWZZGS6+NskWFJPMSVs97-GX8k6iFJamgEgeNnA@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Allison Mankin <allison.mankin@gmail.com>, Rfcplusplus@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ee84460570bdda7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/heq1M2A_vikIvxs1Zw5cbIK-5Xo>
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:00:15 -0000

On Wed, Jul 11, 2018 at 11:28 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Wednesday, July 11, 2018 13:26 -0400 Allison Mankin
> <allison.mankin@gmail.com> wrote:
>
> >...
> > 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.
>
> Allison,
>
> Three questions:
>
> How are ANRW papers published now?  From a quick search, it
> looks as if at least one or two of the proceedings volumes were
> published by ACM via their usual methods and using their
> distribution methods.  Is that generally true?
>

Without taking a position on ANRW, ISOC already runs ISOC NDSS, so
presumably cloning that wouldn't be particularly difficult.

-Ekr