Re: [hrpc] draft-irtf-hrpc-political - current determination regarding RG last call.

Eric Rescorla <ekr@rtfm.com> Tue, 15 October 2019 13:21 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F76B1200FB for <hrpc@ietfa.amsl.com>; Tue, 15 Oct 2019 06:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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] 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 0gZnyf-6iwVQ for <hrpc@ietfa.amsl.com>; Tue, 15 Oct 2019 06:21:38 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 359E212004C for <hrpc@irtf.org>; Tue, 15 Oct 2019 06:21:38 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id a22so20256699ljd.0 for <hrpc@irtf.org>; Tue, 15 Oct 2019 06:21:38 -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=Z9iWhDzmJ2/12viiXSiC0GLFXUfkw22LPtV2SNzmIyc=; b=XFFPYTOyfed0wRg4hnvw6bYcoAc15HXFNzVV5ThUpJCyjM7iXsDHjbKPMCs+hlETjK ae87vlQexcxaob5TRKhPJozdEmwpthfPo3jwMGPuOlPdrx6J16dCHY4k4HKfPk/lW2bf yUQzb+l84EfSZiQ20LAaysS2Fhywb1rmczQ22/q17GTL7MQ7gGzWk093nD9q+Y1XBIK1 VQUwtSkAMr1W8dKieNIHefijLrRBLA/RwhC0GFKbbMiX6PL3MhRxCT3KKHu3e2R/HMTM KwcQx8udk7wPU2ivnkyBqrl0j27Hfj7C+3kk+kjIbdh5MrlPcGJla927TtFoV3XgI0Gd ZX/Q==
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=Z9iWhDzmJ2/12viiXSiC0GLFXUfkw22LPtV2SNzmIyc=; b=Ddvqa1gAfQAab9unBcKVvyqYT0Hwew3oPX3KP0XY5e5uvY8MCHRAF9fLU1y6LkM/H7 2X/zxB2o9Zcazf/Umgt3F5q2iwKnnHJYrHJSs0/UMhb8h8RHZpOL1ME2uIAUDp62b0Kk 5IzZUF05ZF8E8zCEbbTsgXdnc4pA/2ebsSt4fp1k6miVdNbGLPDAO+EenZOUjIJEQMi9 Wc+BvtO0cLpWHRvVZsgbzDUkinU3UITaEGQrsP8ZD3mzeNmRVfVpeYgmGS+UVG2qeO0B GSllAGH8Sg8ZJ9FlVTK9Tt3MtordV+DdMbrNNcxgoTKWCGZ6VFiilu3rQE44aQtk7Doh wCGw==
X-Gm-Message-State: APjAAAXKlQROwN92SgTnJUOlMqYEnj0aaY21RUst4c5PDHCNQUtuavq3 +1P2/X0K0i98LrsRGt01hBQ9icpa5IX3VJaxgAN3ZA==
X-Google-Smtp-Source: APXvYqwfUIt9QE7gGs7fC3mx4hblyIOU1pPZNT1n32+HU9f2LpsKVrV7yVUQNnrOwTZJJPSN+HUlKHWj1faPQEO/wsY=
X-Received: by 2002:a05:651c:237:: with SMTP id z23mr16536276ljn.93.1571145696282; Tue, 15 Oct 2019 06:21:36 -0700 (PDT)
MIME-Version: 1.0
References: <53caa46d-7ea5-f73f-1476-83d8d25555ba@doria.org> <2AE7E345-43BE-436C-BED9-3E39A7909B47@cisco.com>
In-Reply-To: <2AE7E345-43BE-436C-BED9-3E39A7909B47@cisco.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 15 Oct 2019 06:20:59 -0700
Message-ID: <CABcZeBONvpKT35BVS5JQTrOFRSOjWStya1MKcOjemB8tc6UeXA@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: avri@doria.org, hrpc@irtf.org
Content-Type: multipart/alternative; boundary="0000000000001e1f640594f2dd77"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/1rH_uGMtC2rJDGJwPnF2LVQxBJE>
Subject: Re: [hrpc] draft-irtf-hrpc-political - current determination regarding RG last call.
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "mail@nielstenoever.net" <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 13:21:43 -0000

I concur partially with Eliot: i don't think this is about sides. I
actually suspect that Niels and I agree to a fair extent about the
political nature of standards development. My concern is not that but
rather whether this document makes interesting/useful claims and whether it
supports them with evidence. At present, it's not clear to me that it does
so, or really even what point it is trying to make.


On Tue, Oct 15, 2019 at 12:13 AM Eliot Lear <lear@cisco.com> wrote:

> Hi Avri,
>
> First, I appreciate the level of effort that Niels is putting into this
> work.  I want to take issue with two points you made:
>
> On 14 Oct 2019, at 16:44, avri@doria.org wrote:
>
> I think the document does a decent job of expressing one side of the
> argument, though there are places in that discussion that are shy on
> references and on arguments that logically show why that view should be
> considered the right argument.
>
>
> To me this was never about “sides”.  To begin with there may be a great
> many sides.
>
> Regardless, once there is a clear and bounded research question,
> reasonable argumentation and references, and a bounded conclusion,
> regardless of whether I agree with the work, I am comfortable with it being
> published.  Some might want to publish opposing argument.  So long as we as
> a group are open to those publications as well, why would it be necessary
> to hold up this work?
>
> Having written an economic and policy paper with people who had opposite
> views[1]*, I don’t recommend the practice.  One gets into all sorts of
> arguments about methodology and reference quality etc with one’s
> co-authors, and for what?  What is the value of such a work over two
> separate works?
>
> Which brings me to my next point:
>
>
> Regarding the discussion of whether we need RG consensus to publish in
> the IRSG stream: as I have said several times, I believe that in
> becoming a RG draft, a private draft becomes subjected to the RG rough
> consensus process.
>
>
> Yes, you have said this.  I do not recall you saying why you would take
> this approach.  Can we please have a discussion as to whether this is the
> best way forward?  What is the value of rough consensus in this case?  Or
> perhaps I should ask that question differently: on what do you seek rough
> consensus: the positions in the document or whether it is simply in good
> enough form to be sent up to the IRSG?  The latter is a whole lot easier to
> get to.
>

Well, "good enough to send to the IRSG" needs to be judged against some
standard. In any case, having the document be an RFC under the IRTF stream
involves a certain amount of endorsement and so I would want there to be
some level of consensus that the we had confidence in the statements in the
document (just as I would want if I were to be on the PC of a conference
which was considering this as a submission).

-Ekr