Re: [hrpc] draft-tenoever-hrpc-political-00.txt

Eliot Lear <lear@cisco.com> Tue, 04 July 2017 13:16 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 B9ACC13207D for <hrpc@ietfa.amsl.com>; Tue, 4 Jul 2017 06:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 pqUTIZ1dy7oA for <hrpc@ietfa.amsl.com>; Tue, 4 Jul 2017 06:16:00 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EB67131891 for <hrpc@irtf.org>; Tue, 4 Jul 2017 06:15:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7964; q=dns/txt; s=iport; t=1499174159; x=1500383759; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=HOK7C+YcQpbpYLyB4xCE5Y8sN9Z9qD1nbdYwAmQ9dAI=; b=JU4fQA8zfRkIwfWEKjrBIGEAHm4TC4xsn6nmdO8loyu44kPWRdm4YAyX CovRUY3f8muLMjfe8mft55dHwvXQ+Cci27ZMUzWYbBc2KojTf3C3nt8a1 oizpUNtm38MoCiIWtCTuT9lCUlT3plLN6bBjjrWdT6JfMkPUWP8qjyqPG s=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AlAQB4lFtZ/xbLJq1cGgEBAQECAQEBAQgBAQEBgy6BDoEQg22KGXORApBUhSyCEQcaAQqFcAKDSBgBAgEBAQEBAQFrKIUZAQEBAwEBIUsbCxgqAgInMAYBDAYCAQGIFgEMAYIHELA9giYpix0BAQEBAQEBAQEBAQEBAQEBAQEBAQEOCgWDJ4UtK4J5gwCEfYJhBZ8GhCmCHY0/iySGepUzHzg/SzEhCBsVSYcXPjaJKgEBAQ
X-IronPort-AV: E=Sophos;i="5.40,307,1496102400"; d="asc'?scan'208,217";a="653020669"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jul 2017 13:15:55 +0000
Received: from [10.61.243.90] ([10.61.243.90]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v64DFsZN023258; Tue, 4 Jul 2017 13:15:54 GMT
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, hrpc@irtf.org
References: <50539136-8c2a-dfb7-7b07-9c242f0cf305@nomountain.net> <b1abffa3-9861-2f5b-e50d-56180732e125@cs.tcd.ie>
From: Eliot Lear <lear@cisco.com>
Message-ID: <2ba43f57-2db0-048d-7dc1-03125e1b34ea@cisco.com>
Date: Tue, 04 Jul 2017 15:15:53 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <b1abffa3-9861-2f5b-e50d-56180732e125@cs.tcd.ie>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="UkmosLV6LtEl9L0Q0kMPRviJE0XnMOTLa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/Yfi7zs5RTLFHa1waF_wX4OlaS9Y>
Subject: Re: [hrpc] draft-tenoever-hrpc-political-00.txt
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "niels@article19.org" <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, 04 Jul 2017 13:16:03 -0000

Hi,

It seems to me that the most interesting assertion in the draft is that
the IETF are not protocol police.  IMHO if the draft answered JUST that
question, it would be worthwhile publishing.  Certainly Gueren,
Dovrolis, et al, would say that it is nearly impossible to change the
waist of the hourglass.  North and south of that point provides a little
more room, but just try changing TLS or HTTP outside of the IETF. 
Nuttin doin.  At the same time, most phone/tablet apps bypass standards
organizations for pretty much any sort of development.  And oh by the
way, in that case, who cares about the protocol or standards development
since the endpoints are often coded by the same entity?  (And when there
is disagreement in that case, the word we seek is schizophrenia).  And
so perhaps the more refined question would be this: when is an SDO the
protocol police?

Eliot

On 7/4/17 1:22 PM, Stephen Farrell wrote:
>
> On 04/07/17 05:12, Melinda Shore wrote:
>> This is a terrific topic and I'm glad to see this draft.
> I agree it's a fun topic. I'm not sure if this'll end up
> as a useful draft or not though, but I figure it's worth
> exploring.
>
> My own quick comments:
>
> - I'm not sure this should try seek to "answer the
>   question whether protocols are political" as I don't
>   believe that's as useful as just fairly describing
>   various positions on the topic. Maybe, after we've
>   gotten the describing bit properly done, we'd be able
>   to seek an answer, but I'm not sure that's worthwhile.
>
> - 3.3 basically reflects what'd be my starting position,
>   but I don't agree that that position "requires that
>   each protocol and use be evaluated" follows from that
>   at all, at least not without a qualifier like "if you
>   care about whether protocol-foo may be political..."
>
> - I think Andrew is right that some definition of how
>   the term politics is used in this draft is needed.
>   Does it encompass internal "politics" amongst IETF
>   participants? Does it encompass company-internal,
>   and intra-company politics? I'm not sure if the
>   authors intended to include those or not.
>
> FWIW, I'd probably review a version of this in detail
> later, if the RG decide to adopt a later revision of
> this draft. As of now, I don't think it's baked enough
> for the RG to decide to do that yet, but discussing it
> seems useful, as the topic has come up a few times.
>
> Cheers,
> S.
>
>
>
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc