Re: [hrpc] I-D Action: draft-irtf-hrpc-political-04.txt

Eliot Lear <lear@cisco.com> Tue, 17 September 2019 05:47 UTC

Return-Path: <lear@cisco.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 44B1B120147 for <hrpc@ietfa.amsl.com>; Mon, 16 Sep 2019 22:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 L1VsD7NaDyJs for <hrpc@ietfa.amsl.com>; Mon, 16 Sep 2019 22:47:55 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FADD12007C for <hrpc@irtf.org>; Mon, 16 Sep 2019 22:47:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4727; q=dns/txt; s=iport; t=1568699275; x=1569908875; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=2S2ehpaS7bMkcsWXgu2vAXCBNpEfyrfT8TNgXB1fhw0=; b=BOvQaaugglLJ6tHEPDQI0n1qUC/7x/OnLMzVNB0DZgGqcrUKkz+U/nu0 D+HhP3Fo6a0Z5Jl6yQNjMAujnKnIm72wocleqmb9EFk6SZ+X7zEYn/x1/ awArM5M0E4w5mlXXAVufk+4ijJTHgVQN50xWqJJrxHLgA6PotAMWsLfLi g=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAADocoBd/xbLJq1mGgEBAQEBAgEBAQEHAgEBAQGBUwUBAQEBCwGDVyAShEuIHGCbMIYKgXsCBwEBAQkDAQEvAQGEPwKDFTQJDgIDCQEBBAEBAQIBBQRthTqFSwYjVhALBD4CAleDOwGCCq0ggTKFTIRwEIE0AYFQij+Bf4E4H4JMPoURgj4ygiYElXGWeYIsgi6BE5E/G4I1h0eDfosfo3qDEQIEBgUCFYFSOIFYMxoIGxU7KgGCQj2QSz4DkSYBAQ
X-IronPort-AV: E=Sophos;i="5.64,515,1559520000"; d="asc'?scan'208,217";a="16843169"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 Sep 2019 05:47:53 +0000
Received: from [10.61.225.65] ([10.61.225.65]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x8H5lqkY027530 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 17 Sep 2019 05:47:52 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <5FEE04EF-307F-4A11-9ED4-E9B7394527AC@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_494E62A9-FA3D-490B-AD4F-1E1C52AEAC75"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 17 Sep 2019 07:47:50 +0200
In-Reply-To: <980ffdbd-79fa-96ca-541c-09107b550531@doria.org>
Cc: hrpc@irtf.org
To: avri@doria.org
References: <156862506643.28251.9847319195246702362@ietfa.amsl.com> <2927d15d-30a2-189b-7a68-dfb11f5f5be0@nielstenoever.net> <980ffdbd-79fa-96ca-541c-09107b550531@doria.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-Outbound-SMTP-Client: 10.61.225.65, [10.61.225.65]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Mfd0xCq5XXDbgG3qFgO7Y_DP0oM>
Subject: Re: [hrpc] I-D Action: draft-irtf-hrpc-political-04.txt
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, 17 Sep 2019 05:47:57 -0000

Hi Avri,

I ask for guidance from the chair and from the RG as to what qualifies as ready for publication.  What are the criteria?  What are we aiming for?  Academic quality?

My view?   There are some real problems in the document.  This is not an exhaustive list:

The thesis statement conflicts with the introduction, and conflates protocols and standards.
As both protocols and standards are central to the document, you would think that they would be defined early on, like in the definitions section.
The difference between protocols and standards is not made, nor is equivalence.
There is no statement of import in the form of what real contribution the work is making and why that contribution matters.
The general and the specific are conflated.  Are protocols and standards at issue here or are we talking about IETF protocols and standards?
The lack of examples is really quite frustrating.

There are a great many other problems with the draft, not the least of which is that the author makes unsupported claims, either by reference or proof, one example being the discussion in Section 5 about the WTO.

Are these show stoppers?  Please before we continue, let’s understand our own standard for publication.

Eliot