Re: [hrpc] draft-irtf-hrpc-political - current determination regarding RG last call.
farzaneh badii <farzaneh.badii@gmail.com> Tue, 15 October 2019 03:59 UTC
Return-Path: <farzaneh.badii@gmail.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 31D9712009E for <hrpc@ietfa.amsl.com>; Mon, 14 Oct 2019 20:59:52 -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_HELO_NONE=0.001, 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 2uohYSCShM2K for <hrpc@ietfa.amsl.com>; Mon, 14 Oct 2019 20:59:50 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 33A0F120077 for <hrpc@irtf.org>; Mon, 14 Oct 2019 20:59:50 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id m15so28660436qtq.2 for <hrpc@irtf.org>; Mon, 14 Oct 2019 20:59:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aANg5tyyG97fONreb3h8HzCOQLMghXdR4AZnozlGvuA=; b=ILcw9DhZWBGQ6GoHBNmxAAuwBKGHlT0YgGV95/myGZHcTW1l/2UKyBSRUialSkswz8 mnS5vW6qiPUhQo+ZklXPdg+Jc5sRCiqfTJAZaR6DK0fETXGzTCDnwtJ1fzgp0e0cbn+0 jkxJ92tmNJL3TpDqmARjErfhVYwN1iatHRuTpWlza16Z/DqEvKhFBlv/USlS3VD9CRCM B31rxrldSUNk3d8HGhzDL002Fy9n9v3zgJ5rJ8ft7GLMAYkN3PiBO5li/+CTpxM729bw D5G/JgPTW+V4x1XNg121EpwlMUs7Pd3aNUGLFGyattcFihvE4GWZJMwH3Iraj6pAJZER f4Kw==
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=aANg5tyyG97fONreb3h8HzCOQLMghXdR4AZnozlGvuA=; b=D0d8yCvAwP3R6ijZTQsmgVRaVTx6IrDFBXzbGbe+PkPiLUtWOyGR+Njwnh9f13vTWE NQiXLxmt5REy6BHqzj/EOqVjGXyiWCz2GDOv2Rmv42lTH/G82iw15eDDwmy0TsSRyjED yylUcdnqZhUR1Gc9UEP2oycxVPtexo7q7pcxFzRBQztUdAfRHMkIbAEuXKDlghBGqpFa jHrrLeI18TW5KvPgLT/uFr9vEPv5qb+mqtKnUs51JcQckUniF8oz18Z+541Q4ZVRsgpa 9JPyNzfC8pbN9IoK5hGVSia+lGqpfrsmn4ANbHvgO7E0uAE1TJbUf7L/7XnZxM02G7/3 4UgA==
X-Gm-Message-State: APjAAAXxg6g7N/y3DnxuKXlcx0kEqFwKnj8EiN88porivprq4Lr8KxIQ gqDoIS1rYI6EBisFNhAyCB1mYZ3gHkRuXDaVogASaIMB
X-Google-Smtp-Source: APXvYqwPq0etYfzBJ/9Coe0Qrq6leMZHk3pKWR06Tr88RbtniHZv6jWgQgmRu+wiUZYiujs3degs66Th7JRVKg2hUgs=
X-Received: by 2002:ac8:3823:: with SMTP id q32mr35787987qtb.20.1571111987875; Mon, 14 Oct 2019 20:59:47 -0700 (PDT)
MIME-Version: 1.0
References: <53caa46d-7ea5-f73f-1476-83d8d25555ba@doria.org>
In-Reply-To: <53caa46d-7ea5-f73f-1476-83d8d25555ba@doria.org>
From: farzaneh badii <farzaneh.badii@gmail.com>
Date: Mon, 14 Oct 2019 23:59:19 -0400
Message-ID: <CAN1qJvAw836M0j=cUEcYrATDjqJWJdcaKyJFmrRiNEpB5D53Tw@mail.gmail.com>
To: "avri@acm.org" <avri@doria.org>
Cc: hrpc@irtf.org
Content-Type: multipart/alternative; boundary="000000000000f093920594eb033d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/_DCxznj3kg5hyHoOh6tfn8zmPRA>
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 03:59:52 -0000
I think Avri has accurately captured the discussion. Having a couple of co-editors would be good. Best Farzaneh On Mon, Oct 14, 2019 at 10:45 AM <avri@doria.org> wrote: > Hi, > > Now that the conversation has paused, I believe it is time to say > something about the draft and its readiness for RG last call. In order > not to bury the lead, my conclusion is that at this time is that it is > not yet ready. I will explain > > First I want to say that I think this is an important piece of work and > one that needs to be done right. I think the most value can be achieved > by having a document that does justice to the various sides of this > important question, and one that points the way to have further > discussions about the implications of the question in a balanced, > informed and considered manner. > > 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. Nonetheless the basics of that argument > are well established. What I think is missing is an equivalent basis for > opposing views. I think the various detailed discussions of disagreement > support that view. Opposing views, while in some cases mentioned and > even described briefly, are not given the same depth of analysis that is > given to the predominant view. > > In terms of the HRPC RG's view on the document, the group of respondents > was split. There are several who think the document is ready to go. > There are also as many who think it is not. In my opinion, we have not > yet reached rough consensus for publication. > > I appreciate the speed with which Niels put out versions with the > specific fixes he believed necessary to satisfy the arguments, but feel > they sometimes missed the point about the document not being a balanced > discussion of the issues. I also think we saw that those with a > different point of view did not agree with the updated presentation. > > 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. It is not that all the issues in the doc need to > have rough consensus agreement, but the document itself needs to be > something the RG supports publishing in the IRSG track. This is the same > process we followed with RFC8280. It is not as if the IRSG RFC track is > the only opportunity people have to publish their ideas or their > advocacy. I believe the IRSG RFC track serves as a way for a RGs to > publish documents that are supported by the RG's research and > discussions. This is something I try to make clear to people when they > request that a private draft become a RG draft, I ask whether people > wanted the draft to become subject to RG rough consensus because that is > a criterion I use in moving the document forward. > > As I said above, I think this is an important piece of work and think > that this RG should be able to produce a well researched and broad > document on this subject; one which has often been an elephant in the > room in technical discussions. At this point, I think it is only part > way there. > > My current thought is that I would like to see work on this draft > continue. I think it might be good to find an additional editor or two > to work alongside Niels on taking the next steps on the doc. I am > interested in hearing from volunteers for this task. I would also like > to devote some time in Singapore to a discussion of what content is > needed to complete the draft and to develop a plan for its completion. > The discussion brought up many issues. I am still working on trying to > abstract a brief view of the issues that people brought up and plan on > presenting that as part of the discussion. There were also a few > suggestions of what the document still needed, which I would like to > explore in open discussion. > > I appreciate the amount of thought and effort people put into responding > to my call for feedback. I also appreciate the amount of Niels' work > that has gone into the draft to date. > > thanks > > avri > > > > _______________________________________________ > hrpc mailing list > hrpc@irtf.org > https://www.irtf.org/mailman/listinfo/hrpc >
- [hrpc] draft-irtf-hrpc-political - current determ… avri
- Re: [hrpc] draft-irtf-hrpc-political - current de… Niels ten Oever
- Re: [hrpc] draft-irtf-hrpc-political - current de… Melinda Shore
- Re: [hrpc] draft-irtf-hrpc-political - current de… farzaneh badii
- Re: [hrpc] draft-irtf-hrpc-political - current de… Eliot Lear
- Re: [hrpc] draft-irtf-hrpc-political - current de… Eric Rescorla
- Re: [hrpc] draft-irtf-hrpc-political - current de… Ted Lemon
- Re: [hrpc] draft-irtf-hrpc-political - current de… Eliot Lear
- Re: [hrpc] draft-irtf-hrpc-political - current de… avri
- Re: [hrpc] draft-irtf-hrpc-political - current de… Eric Rescorla