Re: [Rfcplusplus] Conversation as metaphor
Ted Hardie <ted.ietf@gmail.com> Tue, 10 July 2018 17:14 UTC
Return-Path: <ted.ietf@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 B946213117F for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 10:14:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 T98gZYkbMH7R for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 10:14:21 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 A4E30131169 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 10:14:21 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id 13-v6so44079305ois.1 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 10:14:21 -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=+LolzaTP97ogM/UW+g5vyXnE31BWnI1rq33x8lUKUNo=; b=diG3kftxC7GMJV0B6gTq93e+2Qdiu5tdXZTxoIYuFUw7ZOYR7sul3hmuXsze+vTKAL zZtaf1IR9NQxJuYJhwiYhfEqXMAdf5IEBacsRHZ9YOIlHHKKFGpcse3MGnin4gvzO0uW vIB9cw6ddbM/lO7KGriKpFbIInqstqLkuMQygK6STW354dMOj0pcRD8CAx4s5uAjSHae sfI9GnCwmZ/HsUmTjSh/PZoCAV66FXlyhKFb5czSY3S8BBDYsw5eEl7rsrdknw1Zo5AB IhyBDBoE0JbHePkhE4aQCyU8AKkKcEVuuoQb+hFuYais6mi4CsCfAl1qtgz8f3ygUYTO YjRw==
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=+LolzaTP97ogM/UW+g5vyXnE31BWnI1rq33x8lUKUNo=; b=mxObm2KrcXKoHIQuRgrNz/GubDJyh+uGKgS8nqCuTQQfC0WSLn2ccZmh3KIbigrRrs 8jGTQ9MRrA78CviBpL13vUwOpf+6Oh9H3lUkovcJlUfFxTH3xB3ZELIjqS0G7yomtttF Vp2eBxhy+cIcq6NKQElGyjmc1UoqgBYq1apJnFAVtaNUcI8lb81GqGLcybtH/37Menm9 k+NPTOEk2Zps7AcVHeKwooZTsyKBFfXW2BdjB5irc9kisNvP2C+K3wfSrHcUJfEkcySw Gk913YwoX4Lue4OLIl9JNadHLi+5mytFry9BVcO66XKMBnJliUNB0ATxYm6SSfSkbex3 /Sjg==
X-Gm-Message-State: APt69E1ISN6nFnWEPXMeWzeJ5dszWj3bHP1O8Q5noeblw5W+Tphv3cqB XCegF5iOpuAHZs3eFsPyuVTReY44cZ7AY6E9qhY=
X-Google-Smtp-Source: AAOMgpc7WbgKiEivz9AsaIm9mx8TNBegl7+weVsXddy5zOsFwjFzni3V9hcCS9bL915+2nctdoFjP5FDcStcVPCbEkI=
X-Received: by 2002:aca:190d:: with SMTP id l13-v6mr30365613oii.216.1531242860753; Tue, 10 Jul 2018 10:14:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:66d9:0:0:0:0:0 with HTTP; Tue, 10 Jul 2018 10:13:50 -0700 (PDT)
In-Reply-To: <a9f9fe28-9e87-05b8-6c4b-2f5d8941f4c8@cisco.com>
References: <CA+9kkMBVC82qy0hbUbQKm=OsFPsaJUPndtVaxd782au6Qy0w6Q@mail.gmail.com> <a9f9fe28-9e87-05b8-6c4b-2f5d8941f4c8@cisco.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 10 Jul 2018 10:13:50 -0700
Message-ID: <CA+9kkMAYFbt39srO_g1J3UqC=E=FB8Wf8Z4PYc0bDPfCxbEhMg@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: rfcplusplus@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c7b68c0570a842b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/guGf4shCHHNIBNQ7frgInY5uCC0>
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: Tue, 10 Jul 2018 17:14:25 -0000
On Mon, Jul 9, 2018 at 2:14 PM, Eliot Lear <lear@cisco.com> wrote: > As to voices, one of the perhaps lost aspects of RFCs is that Jon always > encouraged dissenting views on important topics to be published, so long as > they were well reasoned and reasonably well written. Personally I'd like > to see more dissenting views coming out of independent submissions. I know > I have quite a few to share ;-) I offer that only in as much as having a > few dissenting views might make clear that we really do speak with multiple > voices. > I personally don't think the dissenting opinions are fewer now, but fewer of them are expressed in RFCs. The critiques and dissents come, as Eric mentioned, in other series or other forms. Anyway, I won't be in Montreal, so here's my own bottom line: if the IAB > are serious about actually using different labels, ask yourselves what the > plan is to make those new series successful. How will the new series be > promoted? What will you attract readership? And what will the rules of > the road be for the series? If you do not have a plan, then let's not be > under any illusions that the new series will be successful. > > I think you're quite right that making a successful change of this type will take work, and that promoting the output of the different streams will be part of that work. What's been interesting for me is that the thought of how different the audiences are for that promotion. Reaching the folks who need to understand what the IRTF's output is and means is a very different enterprise than reaching those who might need to understand what the Internet Architecture Board has to say. Given the acronym overload there, a portion of that has to be making sure which IAB is talking, an impact that the IAB or ISE would not feel. But I think that actually illustrates the problem folks have brought forward here: if we were promoting these voices, we would do so at least partly to very different audiences. That's may be an important signal. Ted > Eliot > > On 09.07.18 17:24, Ted Hardie wrote: > > In a different thread, Eric made a statement about the RFC Series being in > conversation with other publications: > > The RFC series (and also I-Ds) have an important role to play here, but it >> also exists in conversation with a lot of other publication venues, and I >> think that's healthy. >> > > While I agree with him, I think the metaphor of "conversation" is even > more useful in describing both the current series and the question before > us. From my personal perspective, the primary reason we use "RFC" as a > series identifier is to identify a specific set of technical documents as > part of a common "conversation". The adoption of the term and series by > the IETF was a signal about the conversation their documents were to be > part of; choosing a different document series (like ANSI, ISO, or minting > a new one) would have sent a signal about a different technical community > with whom the IETF was in dialog. > > When the idea of different streams and stream managers gelled, we kept the > same series identifier for all of them. I think, personally, we did that > because we wanted to be clear that all of the documents continued to be > part of a larger conversation about the development of Internet > technologies. > > One way to understand the problem motivating this BoF is also through the > metaphor of conversation: many outside the community simply don't recognize > that there are multiple voices inside that conversation. They see all of > the documents as utterances by a single, somewhat nebulous group. That can > cause problems. Among those named earlier were the academic community's > failure to value the output of the IRTF; vendors or customers not > distinguishing consensus output from proprietary alternatives; and even a > few efforts to get rejected ideas to appear to have been accepted ones. > > The question before us could be cast as: is it more important now to > highlight the different voices that the streams and statuses currently > convey, so that others understand them as disctinct? > > As Eric points out, there are other ways to maintain a conversation among > different groups than to make their output part of a single series. There > are also other ways we could try to make sure that we highlight that > distinction more fully (using STD numbers for all IETF standards documents, > for example, from proposed standard onward). But I think this is the core > of the tension, shorn of discussion of brand or history: how to we get to > the right balance of maintaining the conversation while improving the > understanding that these are individual voices within it? > > My thoughts as individual, > > regards, > > Ted > > > _______________________________________________ > Rfcplusplus mailing listRfcplusplus@ietf.orghttps://www.ietf.org/mailman/listinfo/rfcplusplus > > >
- [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