Re: [Rfcplusplus] Conversation as metaphor
Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 11 July 2018 02:10 UTC
Return-Path: <brian.e.carpenter@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 7018B130DE8 for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 19:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 8W9cGZlq_7Ie for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 19:10:36 -0700 (PDT)
Received: from mail-pl0-x235.google.com (mail-pl0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (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 E032112E039 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 19:10:35 -0700 (PDT)
Received: by mail-pl0-x235.google.com with SMTP id 31-v6so8435455plc.4 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 19:10:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=CfI2fteQRgN5vmGBZWXkFgPHGCPGX3ETdHwn/VZQbb4=; b=F0GCw/Y2v7pxsDT++RH4L0d/90avQex4NLa7s1qLC1lIYXoUXWMC7nAJbUqw6CDnq8 HSg2SRPTTMH+8EkEl1D3b3ogmYmswmRx0k7fzOcf3gqx/yANrOGKnRmqlOeblKvmofSD k78WI/6hPqdIkb47F5eiGuU3S03WR1yZbQ2HxZ01xsmyBZ0TGTindSiXCKZUY1/MtqV9 K1DUED2lhofBmLx7/t9bezPD4IbZcOLr3DY0WT1WMyIMWFO5sfivX6fc+9wX4XwVNTUv 9/NoPtDggBU1zmGxBUX1oA2fW7wwhtyaJVnk23QyTbZIj16GFUQSfhJyGLaAONslqmxA 6drQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CfI2fteQRgN5vmGBZWXkFgPHGCPGX3ETdHwn/VZQbb4=; b=Hde7d6liwp52jwapfduZ5HAEm5IKUtH077cRVsuMGdAP3FakEJvYlZYDcILqq9sSRr EdZx/W/Is7QgKrM85qaiQrwbe8SHbzTHKBNy551YvVwj1Afecq4TH1Nl8gDtCRTAmkDZ PKVzdOzxgdr/iS0JUQB56qLa1ucv06waNiHKavUNeFFjRTtPf1V1oAit8il6vtEHarUO jLZqnBvHpUIVpVimjFYQA7NGwe4tNWgbc1HrUbX0695VOvCbOyXlUSWhqbRwMWDM2yXI W6QlfBKZcOQjgtpiM8L3Cx+cyiMWtTG0zi8IueJYc/kiZPoZXuptsP+0VY8wu09T2+Sb WlwA==
X-Gm-Message-State: APt69E1DuA2uIr5z2tL0tJxN6k4EGjUthk9rFIZCv2b0FxHtckABvmbX IxdPLwUyNJI9Kwb0vR20OVI=
X-Google-Smtp-Source: AAOMgpdLmFCQnNLAFlsblCaPg9ydARL0P8JD5hzby1rYQ1w4wyqMAvk5Loz+UbOiLrQxWQ+OL+iaCQ==
X-Received: by 2002:a17:902:3e3:: with SMTP id d90-v6mr26963051pld.12.1531275035410; Tue, 10 Jul 2018 19:10:35 -0700 (PDT)
Received: from [192.168.178.38] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id p20-v6sm27966871pff.90.2018.07.10.19.10.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jul 2018 19:10:34 -0700 (PDT)
To: Ted Hardie <ted.ietf@gmail.com>, Eric C Rosen <erosen@juniper.net>
Cc: rfcplusplus@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
References: <CA+9kkMBVC82qy0hbUbQKm=OsFPsaJUPndtVaxd782au6Qy0w6Q@mail.gmail.com> <a4b50286-5c54-e6cf-9087-7171030b7fca@juniper.net> <C9EBFF44-DB93-45E4-954D-2AC5E2F47D03@gmail.com> <20180710192810.GQ20282@mx4.yitter.info> <0e127473-902a-2421-6b5d-73f9e7f83286@juniper.net> <CA+9kkMDwOuLOJMzBSowqga-6s0GnO=03PBScOaHRcJT0+QYicw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <3d5402df-5fd6-43b8-f75e-0423253bb07e@gmail.com>
Date: Wed, 11 Jul 2018 14:10:35 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CA+9kkMDwOuLOJMzBSowqga-6s0GnO=03PBScOaHRcJT0+QYicw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/bEbyzRXHQ9iLlj4hH4ZsNmEsH3c>
Subject: Re: [Rfcplusplus] Conversation as metaphor
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 02:10:37 -0000
On 11/07/2018 08:09, Ted Hardie wrote: > On Tue, Jul 10, 2018 at 12:58 PM, Eric C Rosen <erosen@juniper.net> wrote: > >> >> If the IRTF determines that it would prefer a different publication venue, >> I certainly have no problem with that. We shouldn't force researchers to >> publish their work as RFCs. (I didn't think we did so, but ...) If I were >> a researcher, I'd probably want to publish in a reputable academic journal, >> but perhaps my academic experience is a bit dated. >> >> But that's really irrelevant to the main topic of this discussion. What we >> are primarily discussing is whether we should prohibit folks from >> publishing RFCs when they want to do so and find it valuable to do so. >> That's a completely different question. >> >> > I must respectfully disagree that this is an irrelevant question. The > proposed experiment would establish new identifiers for the work of the > IRTF currently published as a stream within the RFC series. That output > might (and I acknowledge again that it is only "might") change the academic > assessment of that output while retaining its other characteristics. I > personally believe this question is thus on topic for a discussion of the > experiment. 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] Conversation as metaphor Ted Hardie
- Re: [Rfcplusplus] Conversation as metaphor Eliot Lear
- Re: [Rfcplusplus] Conversation as metaphor Eric C Rosen
- Re: [Rfcplusplus] Conversation as metaphor Ted Hardie
- Re: [Rfcplusplus] Conversation as metaphor Ted Hardie
- Re: [Rfcplusplus] Conversation as metaphor Bob Hinden
- Re: [Rfcplusplus] Conversation as metaphor Andrew Sullivan
- Re: [Rfcplusplus] Conversation as metaphor Bob Hinden
- Re: [Rfcplusplus] Conversation as metaphor Eric C Rosen
- Re: [Rfcplusplus] Conversation as metaphor Eric Rescorla
- Re: [Rfcplusplus] Conversation as metaphor Ted Hardie
- Re: [Rfcplusplus] Conversation as metaphor Aaron Falk
- Re: [Rfcplusplus] Conversation as metaphor Andrew Sullivan
- Re: [Rfcplusplus] Conversation as metaphor Ted Hardie
- Re: [Rfcplusplus] Conversation as metaphor Aaron Falk
- Re: [Rfcplusplus] Conversation as metaphor Eric C Rosen
- Re: [Rfcplusplus] Conversation as metaphor Aaron Falk
- Re: [Rfcplusplus] Conversation as metaphor Melinda Shore
- Re: [Rfcplusplus] Conversation as metaphor Aaron Falk
- [Rfcplusplus] What would the ISE publish [Was: Co… RFC ISE (Adrian Farrel)
- Re: [Rfcplusplus] Conversation as metaphor Brian E Carpenter
- Re: [Rfcplusplus] Conversation as metaphor Brian E Carpenter
- Re: [Rfcplusplus] Conversation as metaphor Brian E Carpenter
- Re: [Rfcplusplus] Conversation as metaphor Brian E Carpenter
- Re: [Rfcplusplus] Conversation as metaphor Brian Trammell (IETF)
- Re: [Rfcplusplus] Conversation as metaphor Ted Hardie
- Re: [Rfcplusplus] Conversation as metaphor Peter Saint-Andre
- Re: [Rfcplusplus] Conversation as metaphor RFC ISE (Adrian Farrel)
- Re: [Rfcplusplus] Conversation as metaphor Peter Saint-Andre
- Re: [Rfcplusplus] Conversation as metaphor S Moonesamy
- Re: [Rfcplusplus] Conversation as metaphor Peter Saint-Andre
- Re: [Rfcplusplus] Conversation as metaphor Eric Rescorla
- Re: [Rfcplusplus] Conversation as metaphor Eliot Lear
- Re: [Rfcplusplus] Conversation as metaphor S Moonesamy
- Re: [Rfcplusplus] Conversation as metaphor Brian E Carpenter
- Re: [Rfcplusplus] Conversation as metaphor Martin Thomson
- Re: [Rfcplusplus] Conversation as metaphor Joel M. Halpern
- Re: [Rfcplusplus] Conversation as metaphor Martin Thomson
- Re: [Rfcplusplus] Conversation as metaphor Eliot Lear
- Re: [Rfcplusplus] Conversation as metaphor S Moonesamy
- Re: [Rfcplusplus] Conversation as metaphor Aaron Falk