Re: Clarity, evolving documents, living documents, the RSE, IETF Management Styles, and traffic volume on this list.

Eric Rescorla <ekr@rtfm.com> Thu, 04 July 2019 15:39 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79FC512010C for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 08:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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, SPF_HELO_NONE=0.001, SPF_NONE=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=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 Q0D6wOfYmV_I for <ietf@ietfa.amsl.com>; Thu, 4 Jul 2019 08:39:09 -0700 (PDT)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 EEAEC12004A for <ietf@ietf.org>; Thu, 4 Jul 2019 08:39:08 -0700 (PDT)
Received: by mail-lj1-x231.google.com with SMTP id 16so6524149ljv.10 for <ietf@ietf.org>; Thu, 04 Jul 2019 08:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zioAlg3nL5R62rwPIRkBXi+PGBI7zdasc5qmVt5qweE=; b=HjwIICH0xakGp9fPkIwkuU7kgRsPvpL4OjFAA/1Sn52YkWTIWix82ZPhvC7tqI6tYi tpqioD5SY6kTa+dVHfU3j6ML0gNj9RBv94SIvb8zxL4sGKMKB657gmAgwXAtGvbYIRY7 E/YZBmSHwy1cZjk49sFmHaWt4iR2zLkqOHLIdiX9nLyOh5JY9Uo8jPG/vnkqsTeI4RIU XF27TNSfYtVcMJaQcImxWtyd89+LoFkbJ2TcwRLEDrUUzEPd2KQ1wF3kUYpRdAyq4usZ CEJYHZssKz7lDvL207fzA8Vo+9zcXbfyLDgARUOpGzMTgoBrKV35IbRuJaHIOHM0i7vM yA6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zioAlg3nL5R62rwPIRkBXi+PGBI7zdasc5qmVt5qweE=; b=iJTnUyfgnvgmUgeBHs/QQLLYYe1o1PtLrcTj9BBXUsg/xCWju/H/ol2XLdObcU2joM 653N9aA3QOx/rritb/T54Nzs8QzIFqPWLBtvvdCGcsyvOK4kLCqJ/r6sLvEQ93HFGU6K PSzXayg4GE4TSAAel0BU1lB5fm9yY0RZBB381aiw47Tawuxl0FIeiTDXWQlumV9t459m XcCPlqGOPnZgSHLre547RoJxeiCmwDDZ5X1wh1bUPDivOna/3/G6urWRBIDusdvfG+08 zFqtt1KBvjgSGGqPI3XJWZbS6L4zUgXkT8Q1eknf0QM6OslAwUr5oivRrUM72AsHBYtv EK6A==
X-Gm-Message-State: APjAAAX98MsImS9I1P0CEw8hLHzWcx19iuVK9giEmufNY8M0NjPh/oaO j3uzAvOzI6C1Rd/IprHp56O1bQMUO5hPNHqmHMxqtA==
X-Google-Smtp-Source: APXvYqzbVG52UWOsjKuMmJBGa1JtQURvJdoUUXfbgwX8VF1H5/rpjSv6bD7SzNje4/VAmSpb1gFzULim4Ga1RxbrOTc=
X-Received: by 2002:a2e:96d0:: with SMTP id d16mr25376409ljj.14.1562254747207; Thu, 04 Jul 2019 08:39:07 -0700 (PDT)
MIME-Version: 1.0
References: <0856af71-4d84-09d1-834d-12ac7252420c@network-heretics.com> <e8d28a7f-128d-e8d0-17d3-146c6ff5b546@joelhalpern.com> <CAHw9_i+UBs85P+gjcF6BJd1_WD2qFrrYCnXb4rtcG9Hepqm37w@mail.gmail.com> <796c1f6c-cd67-2cd5-9a98-9059a0e516f8@network-heretics.com> <20190704013009.dlifopcbm2umnqo7@mx4.yitter.info> <b18809df-ee98-fb29-b6c4-04ed579e163a@network-heretics.com> <20190704052335.GF3508@localhost> <911a7af5-071a-ce88-527d-70dfe939b256@network-heretics.com> <6317584D-4C9B-46E9-8197-D2A488701868@fugue.com> <20190704140552.GE49950@hanna.meerval.net> <35880DA835A7565D0201CC91@PSB>
In-Reply-To: <35880DA835A7565D0201CC91@PSB>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 04 Jul 2019 08:38:30 -0700
Message-ID: <CABcZeBOzpoJFaZOGzUwgr=Wv=GjB=kUKk5Y3u8tJffb3WVB4cQ@mail.gmail.com>
Subject: Re: Clarity, evolving documents, living documents, the RSE, IETF Management Styles, and traffic volume on this list.
To: John C Klensin <john-ietf@jck.com>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000419af9058cdcc74b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i8jxdiFZBy3ZIc5fVxNoYABrvvo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jul 2019 15:39:13 -0000

On Thu, Jul 4, 2019 at 8:29 AM John C Klensin <john-ietf@jck.com> wrote:

> Hi.
>
> I don't know if anyone else is having the same problem, but I'm
> having tremendous difficulty following all of the messages in
> this thread, much less the thread about the happenings
> surrounding the RFC Editor function.  That includes the
> side-thread about, e.g., whether one can describe, with facts
> and careful reasoning, an idea or action as stupid without
> insulting the intelligence of whomever was advocating it.  Many,
> many messages.   If only to reduce the odds of re-inventing and
> repeating what has been said before, I'm trying to read
> everything in a thread before I start a response but it means I
> am running hours, sometimes days, behind.
>
> It is especially problematic because I'm also trying to find
> time to get some technical work done that much of the IETF seems
> to think it important as long as _someone else_ puts in the time
> to understand the issues and do the work [1].  I've has it
> suggested to me off list that maybe most of those participating
> actively in the discussions either don't have technical work to
> do or have too much time on their hands.  I'd rather think that
> priorities (and levels of support for IETF work) are different,
> but I do suggest, as Randy Bush has pointed out a couple of
> times, maybe it would be better if people took a deep breath,
> let some of these discussions sink in, and actual get some
> technical work done, including trying to finish I-Ds before
> Monday's posting deadline and then actually reading enough of
> those drafts to make IETF 106 more productive.
>
> Or perhaps, if these topics are really important enough, we
> should call off the IETF 105 agenda and devote the meeting to
> them, without conflicts and one day per topic.   I understand
> the logistical problems with trying to do that in one large room
> but perhaps smaller group parallel sessions and discussions on
> the same subject (with people allocated at random or when rooms
> fill up) and then summaries of conclusions would work even
> better.
>
> In any event, it is probably worth noting and remembering that
> these very long threads on the IETF list get participation from
> a very small fraction of the IETF community.  Whether others
> tune out after looking at one message or a dozen, we aren't
> hearing from them.  Because these topics have effects on the
> entire IETF, how it works, and how it is perceived, real IETF
> consensus --across the entire spectrum of IETF contributors and
> other materially affected parties-- is important if decisions
> are to be made.  It is difficult and perhaps impossible to draw
> inferences about consensus across the IETF when only a handful
> (or two) of people are participating.  It is even closer to
> impossible if those people participating in a way that
> discourages others from getting involved, however unintentional
> (and respectful) the mechanisms that are being used.
>
> A more substantive note or two follow, but I believe the above
> is important and it saddens me that it didn't come from someone
> in "the leadership".
>

It's worth noting that Alissa said something that reads to me as fairly
close to this last Wednesday.

https://mailarchive.ietf.org/arch/msg/ietf/5Q3KQOBY5FQTxh_-abI4M_fepQU

-Ekr

    john
>
> [1] I'm not trying to be cryptic, just to keep the above short.
> The very high-level summary of the topic area might be best
> described as a set of questions.   Do any of you, or your
> organizations, colleagues, or customers, use a language  that
> cannot be written properly in ASCII characters and even
> occasionally want to write it properly while using the Internet?
> (Note that list of languages includes English.)  Would you, or
> your organizations, colleagues, or customers find it helpful to
> be able to use identifiers, user names, or other descriptors or
> mnemonics that are not tied to English?  Do you think it is
> important that everyone have confidence that strings that should
> compare equal do so and that ones that shouldn't, don't?  Do you
> understand that the problems the other questions imply are hard
> and require either significant digging in or suggest that the
> IETF should publicly give up and accept the consequences?   If
> your answer to any of those questions is "yes", why are you not
> digging in personally and why are you allowing the IESG to
> essentially ignore the topics, not answer questions about how to
> progress documents, and to set up mechanisms and then neglect
> them sufficiently to ensure failure?
>
>
>