Re: Clarifying Russ's hums
John C Klensin <john-ietf@jck.com> Wed, 06 November 2013 22:47 UTC
Return-Path: <john-ietf@jck.com>
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 885D021F9F9D for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 14:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.595
X-Spam-Level:
X-Spam-Status: No, score=-103.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUACOB+b4hS2 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 14:47:24 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6470521E808A for <ietf@ietf.org>; Wed, 6 Nov 2013 14:47:24 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VeBsh-000Bkp-7q; Wed, 06 Nov 2013 17:47:23 -0500
Date: Wed, 06 Nov 2013 17:47:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Scott Brim <scott.brim@gmail.com>
Subject: Re: Clarifying Russ's hums
Message-ID: <F00D58A3A2CE04C11C33D28E@JCK-EEE10>
In-Reply-To: <527AB909.4040108@gmail.com>
References: <CAPv4CP_UiuDTshnz-vzb7aTQEV-UrdyXiYb70iR72YQSi_3H1w@mail.gmail.com> <527AB909.4040108@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 06 Nov 2013 22:47:29 -0000
--On Thursday, 07 November, 2013 10:47 +1300 Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > It seems to me that all three are perfecly clear as > aspirational goals, and that they all include some room for > interpretation. It's also true that some of them may be in > immediate conflict with other goals (for example, a web proxy > that is blind to the content might be rather bad at content > filtering). But all that will come out in the detailed > analysis of each issue. Guiding principles really have to > skate over many details. Brian, I thought of it less as (even) aspirational goals than as theater and, as such, completely appropriate. As anything closer to a consensus evaluation, it seemed to have many of the properties that draft-resnick-on-consensus warns about: hums at the end of the process that were not clearly motivated except as a way of confirming and announcing consensus, assessment and reporting of loudness as if it were a vote, concentrating on the majority response rather than the issues and reasoning of the minority, and asking sweeping questions that don't seem to lead to anything actionable (I assume that a hum associated with the question "who is in favor of breathing" would yield at least equal results. at least unless everyone who didn't hum was then asked to demonstrate their objections by ceasing to do it). I also assume that, from a policy standpoint, if an IESG decided to reject every specification, especially those that update existing protocols because the result isn't optimal from a security point of view, we've rapidly see either our first recalls or some rather dramatic reforms. I think that, after this morning's discussion, what I'd like to see is the same thing I would have liked to see yesterday, which is that every specification be evaluated in terms of the tradeoffs among all of the considerations that bear on it, including security generally and surveillance-resistance specifically. If the plenary discussion and/or the theatrical qualities of the hums leads us to get more serious and effective about that, it would be, IMO, great. If not, that would be unfortunate, but I hope today's plenary was intended to start and frame a discussion that will continue, not end it. best, john
- Clarifying Russ's hums Scott Brim
- Re: Clarifying Russ's hums Brian E Carpenter
- Re: Clarifying Russ's hums Scott Brim
- Re: Clarifying Russ's hums Roberto Peon
- Re: Clarifying Russ's hums Arturo Servin
- Re: Clarifying Russ's hums Roberto Peon
- Re: Clarifying Russ's hums Phillip Hallam-Baker
- Re: Clarifying Russ's hums Brian E Carpenter
- Re: Clarifying Russ's hums Yoav Nir
- Re: Clarifying Russ's hums John C Klensin
- Re: Clarifying Russ's hums Roberto Peon
- Re: Clarifying Russ's hums Masataka Ohta