Re: [Rfcplusplus] IRTF stream considerations
John C Klensin <john-ietf@jck.com> Wed, 11 July 2018 18:28 UTC
Return-Path: <john-ietf@jck.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 D104E130F58 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 GxiT9lccHWi6 for <rfcplusplus@ietfa.amsl.com>; Wed, 11 Jul 2018 11:28:43 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B10B9130EF9 for <Rfcplusplus@ietf.org>; Wed, 11 Jul 2018 11:28:42 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1fdJqz-0008oO-CM; Wed, 11 Jul 2018 14:28:41 -0400
Date: Wed, 11 Jul 2018 14:28:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Allison Mankin <allison.mankin@gmail.com>
cc: Rfcplusplus@ietf.org
Message-ID: <5F79ECCE7999F4FD4FFC00A3@PSB>
In-Reply-To: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/z5tu8_mDtKmQQdI26hmoE5cw_IA>
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:28:49 -0000
--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? Is the IRTF's plan to continue using the RFC Editor function for editing, archiving, and distribution or do you anticipate going off in some completely different direction? Have you done an analysis of the challenges associated with setting up a new academic journal, independent of known publishers of such things, and getting them accepted and into libraries, etc. Things have changed (and, from what I understand, gotten harder) but I was involved with trying to set one up via the UN some years ago and, after a lot of advice from key institutions and a lot of frustration, determined that we needed to "sell" the journal to an existing major academic journal publisher. I don't know if the same situation would exist with IRTF publications, but it seems to me that the question is worth asking. best, john
- [Rfcplusplus] IRTF stream considerations Allison Mankin
- Re: [Rfcplusplus] IRTF stream considerations Eliot Lear
- Re: [Rfcplusplus] IRTF stream considerations Allison Mankin
- Re: [Rfcplusplus] IRTF stream considerations Aaron Falk
- Re: [Rfcplusplus] IRTF stream considerations Aaron Falk
- Re: [Rfcplusplus] IRTF stream considerations Diego R. Lopez
- Re: [Rfcplusplus] IRTF stream considerations Allison Mankin
- Re: [Rfcplusplus] IRTF stream considerations Allison Mankin
- Re: [Rfcplusplus] IRTF stream considerations John C Klensin
- Re: [Rfcplusplus] IRTF stream considerations Aaron Falk
- Re: [Rfcplusplus] IRTF stream considerations Eric Rescorla
- Re: [Rfcplusplus] IRTF stream considerations Peter Saint-Andre
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Adam Roach
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Adam Roach
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Adam Roach
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Adam Roach
- Re: [Rfcplusplus] IRTF stream considerations Ted Hardie
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Ted Hardie
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Ted Hardie
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Ted Hardie
- Re: [Rfcplusplus] IRTF stream considerations (rea… John C Klensin
- Re: [Rfcplusplus] IRTF stream considerations Brian E Carpenter
- Re: [Rfcplusplus] IRTF stream considerations Jari Arkko