Re: [Rfcplusplus] IRTF stream considerations
Jari Arkko <jari.arkko@piuha.net> Mon, 16 July 2018 19:26 UTC
Return-Path: <jari.arkko@piuha.net>
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 03DBA1311FE for <rfcplusplus@ietfa.amsl.com>; Mon, 16 Jul 2018 12:26: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] 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 cua_vDQ2FfJz for <rfcplusplus@ietfa.amsl.com>; Mon, 16 Jul 2018 12:26:41 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CDD781311F1 for <Rfcplusplus@ietf.org>; Mon, 16 Jul 2018 12:26:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DDF8A660131; Mon, 16 Jul 2018 22:26:39 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kWLvKpFA5KJt; Mon, 16 Jul 2018 22:26:38 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id E2DC766012A; Mon, 16 Jul 2018 22:26:37 +0300 (EEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <06ac0cc7-85e6-135d-1332-cd2e75d4640f@gmail.com>
Date: Mon, 16 Jul 2018 15:26:36 -0400
Cc: "Rfcplusplus@ietf.org" <Rfcplusplus@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BFE96616-A750-4100-9431-666A7A8964C7@piuha.net>
References: <CAP8yD=vm+jRxdi3ZUncoFZNDYKOQKvFaphT7gxb5o1tDXWmumA@mail.gmail.com> <b69b370c-317b-284f-85d1-1353c67a3043@gmail.com> <8f98deb9-7ed3-3303-356a-e6d3dc5a80c0@nostrum.com> <08e8650b-2f33-943e-ddcb-a6bf6c45b2ce@gmail.com> <c2c450a6-4f14-6325-8c54-6ecee4e0983f@nostrum.com> <22b91a2a-82ff-af78-4b79-c58eb305cec6@gmail.com> <77486708-e38d-03d3-f4d0-0f0b67797542@nostrum.com> <f9dede92-980a-58de-444e-b9934b8e78b3@gmail.com> <3d659e94-8455-f7c4-98a8-405bfda728c6@nostrum.com> <06ac0cc7-85e6-135d-1332-cd2e75d4640f@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Allison Mankin <allison.mankin@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/AMC80fB4UNBbFbQuF8q5wo8o-6E>
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: Mon, 16 Jul 2018 19:26:48 -0000
First, on the primary topic of this thread, I believe thinking what would be the best publication approach for the IRTF would be a welcome activity, to optimise the channel(s) that they best serve the researchers participating in IRTF. Then on some other topics: Brian wrote: > What I mean is > that *if* the IETF decides, by its own process, that the IETF wants > to make a change, *then* the next stage must be a serious effort to > discuss it with the rest of the community. Currently, we don't have a > clear method for that. I agree. But want to note that discussion on rfc-interest list, discussions at BOFs during IETF meetings, the plenary, and the like have traditionally been tools that we use when topics related to the RFC series are being discussed. Obviously, an effort should be made to reach as far as possible when there’s a topic for discussion. And as we know, a BOF or other gathering at an IETF is not the final decision place, no matter what gets discussed we’ll have to continue online for some more. Many people talked about: > controversial changes FWIW, my perception of some of the past discussions is that there was at least some level of controversy. You could perhaps argue whether that was lower or higher level than on current topic, but people seem to care about the RFC series and don’t always have the same opinions. Which is a good thing :-) Jari
- [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