Re: And a third [was: A couple of opinion pieces]

Leif Johansson <leifj@mnt.se> Mon, 15 July 2019 18:33 UTC

Return-Path: <leifj@mnt.se>
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 54B04120130 for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2019 11:33:50 -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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.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 ipfWOWLdF7aW for <ietf@ietfa.amsl.com>; Mon, 15 Jul 2019 11:33:47 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::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 5A3F812012B for <ietf@ietf.org>; Mon, 15 Jul 2019 11:33:47 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id i21so17291116ljj.3 for <ietf@ietf.org>; Mon, 15 Jul 2019 11:33:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HCYPe2oMdsBiiPxMDSDYjKmNTpi73oeevg4Tg9op+l0=; b=yYJj5jdBAsH0jiST4ouls/3sKmXNcFCMv7N76+5BdtXNa3julPOLV4RnYo8rEzqLx3 44dPBKpbmm6CzbYf7fJI8+2Or5YgPhqviUUiNM3L/EDEfHzvNF99rX10e1XBm4WTpoX/ G7kuWF542XISvrM0nV53aRtAfbTuLll28HoGFSTAslROVV0K7SMyJJ75CrldkDzu3vue pvO/libDWbQFdUswiE0j11nORp3QGV6A27yXEFy03OYkVB946cbaEMk60IaesroStVpY J2zH3NPG2t+YhtW+msVgtM0t/uRL5qlsJGC80BnXGQ9wuaoef1honFSeod90j794d8ob Ufaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HCYPe2oMdsBiiPxMDSDYjKmNTpi73oeevg4Tg9op+l0=; b=WYqZ0Qg80GRWrOx1R/vCQKVl9f6tVrgUPAzdRohmbhbAjVUodByeVfYIqLyG8Fd0/w 8KaaMYRn6uGulGCpQjsvwXEEhr5z3BrBa7MqI4MTSE4YgSAEHS1wSiJz2rX71hp49QSG JBALYEKg+1KXyNTXd0RTmhfINOs80Zb4VJ7KexiP1vaNElpFgUE36GjcnG+BMe0+P3eX GDgBkoMm7XjhFglU/NQP1JAg9d2AMEqWeT0FoN8H8qfqdRKfjR8G90wRUiACgt+VOtFT 1S24bx0J5L0+m7rj8pPyyNJpGxWMoMJb69OGdOEQdv2Bh+Pj30W7dhy+AP6FdU+Xcld2 guXg==
X-Gm-Message-State: APjAAAUFKWP4/mWbMk/YGrEPmfNQVaSHXtuPIb18sW7LrkiTj8lZS0f8 NyZOf70FZMz97LurZ5pkLYQ9Jgs8
X-Google-Smtp-Source: APXvYqxr/FUOG6nqvuMm2sLELJE5BWTf381sCOsSCZkzoKQ0EEYBJDJcioO92rNXEDoaM1RX/gzYYQ==
X-Received: by 2002:a2e:9198:: with SMTP id f24mr15188742ljg.221.1563215625295; Mon, 15 Jul 2019 11:33:45 -0700 (PDT)
Received: from [10.0.0.192] (h88-129-251-65.cust.a3fiber.se. [88.129.251.65]) by smtp.gmail.com with ESMTPSA id 20sm3257579ljf.21.2019.07.15.11.33.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Jul 2019 11:33:44 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-57B12C2B-7058-4EF5-A6B1-EE0BB9BA9AED"
Mime-Version: 1.0 (1.0)
Subject: Re: And a third [was: A couple of opinion pieces]
From: Leif Johansson <leifj@mnt.se>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <CAL02cgQqcf3L0ea7OTwWYCBaN-b2Q6xSYMGaLmHJrQt1Dm9fTA@mail.gmail.com>
Date: Mon, 15 Jul 2019 20:33:44 +0200
Cc: Christian Huitema <huitema@huitema.net>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <FCCD6C7B-F705-4348-A9F5-314265CE3E4E@mnt.se>
References: <406bd6b2-9c6d-bec8-b953-3e5fdd24451c@gmail.com> <01643f7a-4bab-12ec-0009-f17d6a44b91e@gmail.com> <23ef5f0a-20ed-4a15-0a95-556851938b81@huitema.net> <DA84C3BC-12F4-4FED-B984-1D56028A7D26@mnt.se> <CAL02cgR93ROFZtxxWWnR2sKoBtwDPNwbeD1OHd=u9TicrHanZg@mail.gmail.com> <5E63DB6A-79AE-4C68-AEB1-CFB6DE5DD0C0@mnt.se> <CAL02cgQqcf3L0ea7OTwWYCBaN-b2Q6xSYMGaLmHJrQt1Dm9fTA@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Cklp-jh_HyecdnGg1uYdaCBC8T4>
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: Mon, 15 Jul 2019 18:33:50 -0000


Skickat från min iPhone

> 15 juli 2019 kl. 20:29 skrev Richard Barnes <rlb@ipv.sx>:
> 
>  
> 
>> On Mon, Jul 15, 2019 at 2:19 PM Leif Johansson <leifj@mnt.se> wrote:
>> 
>> 
>> Skickat från min iPhone
>> 
>>> 15 juli 2019 kl. 20:15 skrev Richard Barnes <rlb@ipv.sx>:
>>> 
>>> 
>>> 
>>>> On Mon, Jul 15, 2019 at 1:37 PM Leif Johansson <leifj@mnt.se> wrote:
>>>> 
>>>> 
>>>> Skickat från min iPhone
>>>> 
>>>> > 15 juli 2019 kl. 18:22 skrev Christian Huitema <huitema@huitema.net>:
>>>> > 
>>>> > Brian,
>>>> > 
>>>> > This is an interesting piece, and I share your assessment of the IAB's
>>>> > situation in the late 90's. But I continue to be very skeptical of your
>>>> > references to a "much wider community".
>>>> > 
>>>> > To assess that, I just did a small exercise of listing all the RFC
>>>> > published in the "independent" stream in 2018. There are 14 such RFC:
>>>> > 8507, 8494, 8493, 8492, 8483, 8479, 8433, 8409, 8374, 8369, 8367, 8351,
>>>> > 8328 and 8324. 8369 is an April's fool RFC. RFC 8367 and 8369 were
>>>> > published on 1 April 2018. I looked at the authors of these RFC, and did
>>>> > a quick check: are these outsiders, part of a "wider community" or are
>>>> > these people who are also contributing to the IETF. The overwhelming
>>>> > response is, "insiders". Pretty much all the authors are or were
>>>> > involved in the IETF, many of them with a prominent track record. There
>>>> > are just 2 exceptions, a single RFC in which only 3 of the 5 authors are
>>>> > well associated with the IETF.
>>>> > 
>>>> > There may well be a wider community of people who could publish
>>>> > independent RFC, or for that matter who could participate in the IETF.
>>>> > But data analysis does not indicate that these people participate in the
>>>> > RFC series.
>>>> > 
>>>> 
>>>> cf my post elsewhere on this list on how digital identitiy development moved away from pkix (and the IETF)
>>>> 
>>>> This seems like a perfect illustration of the streetlight effect (I admit I had to make google find the name for me). 
>>>> 
>>>> We have no knowledge of why other communities choose not to publish in the RFC series because we don’t have data about any other communities. 
>>> 
>>> This seems to presume that it would be desirable for other communities to publish in the RFC series.  (I presume you mean, "other than the IETF/IAB/IRTF community".)  Is that your belief, and if so, could you say why?
>> 
>> No I don’t
>> 
>> A more interesting question is this: what happened to make the openidc (to pick a random example) not even consider making RFCs their publication ”format”.
> 
> Now I'm confused.  If it's not desirable for other communities to publish RFCs, why does this question matter?
> 

Because if we can figure out what we did (if anything) to discourage this then maybe there some useful clue to be had there.

> --Richard
> 
>  
>> 
>>> 
>>> --Richard
>>> 
>>>  
>>>> 
>>>> qed - unless... you go talk to some other SDOs and similar organisations... almost like a liason-function might.
>>>> 
>>>> Cheers Leif
>>>> 
>>>> > -- Christian Huitema
>>>> > 
>>>> > 
>>>> >> On 7/14/2019 9:19 PM, Brian E Carpenter wrote:
>>>> >> Various recent discussions here have made me think that the IETF is
>>>> >> at a point where some fundamentals in the standards process, the
>>>> >> publication process, and its basic organization need to be re-evaluated
>>>> >> and perhaps changed. The goal of course would be to make the IETF more
>>>> >> useful, not change for its own sake.
>>>> >> 
>>>> >> It's above my pay grade to decide whether to start an organized
>>>> >> approach to this, but in addition to the two opinion pieces mentioned
>>>> >> below, please also consider this:
>>>> >> https://www.cs.auckland.ac.nz/~brian/CommentaryIAB.pdf
>>>> >> This is about the institution, not the people. Please read the opening
>>>> >> disclaimer, and of course comments are welcome, as always.
>>>> >> 
>>>> >> Regards
>>>> >>   Brian Carpenter
>>>> >> 
>>>> >>> On 20-Jun-19 16:24, Brian E Carpenter wrote:
>>>> >>> Hi,
>>>> >>> 
>>>> >>> The first document is early input to the 2019-2020 NomCom and to
>>>> >>> all those thinking of volunteering for it, or for any of the
>>>> >>> open leadership positions:
>>>> >>> 
>>>> >>> Some Thoughts on IETF Community Leadership
>>>> >>> https://tools.ietf.org/html/draft-carpenter-community-leaders-01
>>>> >>> 
>>>> >>> The second one is also relevant to NomCom, but also to those who
>>>> >>> will be involved in the process of identifying the future RFC Series
>>>> >>> Editor, and to those who care about the IETF standards process in general:
>>>> >>> 
>>>> >>> Request for Comments
>>>> >>> https://tools.ietf.org/html/draft-carpenter-request-for-comments-01
>>>> >>> 
>>>> >>> Comments are most welcome, but these documents are both personal opinions.
>>>> >>> 
>>>> >>> Regards
>>>> >>>   Brian Carpenter
>>>> >>> 
>>>> > 
>>>>