IETF Logo Mail Archive

Re: FW: ID Tracker State Update Notice: <draft-ietf-curdle-cms-chacha20-poly1305-04.txt>

Paul Wouters <paul@nohats.ca> Fri, 16 December 2016 15:57 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65C5712A0DE for <wgchairs@ietfa.amsl.com>; Fri, 16 Dec 2016 07:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.896
X-Spam-Level:
X-Spam-Status: No, score=-4.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-2.896] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 kpMZkEwUPOVi for <wgchairs@ietfa.amsl.com>; Fri, 16 Dec 2016 07:57:27 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9FAB12A004 for <wgchairs@ietf.org>; Fri, 16 Dec 2016 07:52:40 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3tgFFL5CGvzCyQ; Fri, 16 Dec 2016 16:52:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1481903558; bh=1ikvO/gWzVzZtTXgw3lYdTWT7X5cRBIhGbWgeyGl1M0=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=BE5KmXko3OhtFQs0WnnFu0xhyzhuic8yWv8J0fpXcNa/VKWUM994HOANqgFRLhtyT rDchAvA/5qFP7Qs4YRd3YaK70yF4FBB0+wFpgKYwL7madpvfmPKnnmhfPyA6iibk1V q5R6x8wsLTcUgf2l3pKj2+Y+FgkJgtQLpT6fauis=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Xw6Vh8TQS2e5; Fri, 16 Dec 2016 16:52:37 +0100 (CET)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 16 Dec 2016 16:52:37 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 2A0F936AD; Fri, 16 Dec 2016 10:52:36 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca 2A0F936AD
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 0E4264167421; Fri, 16 Dec 2016 10:52:35 -0500 (EST)
Date: Fri, 16 Dec 2016 10:52:35 -0500
From: Paul Wouters <paul@nohats.ca>
To: "Salz, Rich" <rsalz@akamai.com>
Subject: Re: FW: ID Tracker State Update Notice: <draft-ietf-curdle-cms-chacha20-poly1305-04.txt>
In-Reply-To: <ec1c0951c06b42b780ad7601a27f1291@usma1ex-dag1mb1.msg.corp.akamai.com>
Message-ID: <alpine.LRH.2.20.1612161051320.8918@bofh.nohats.ca>
References: <148190265393.14776.6655493196739795393.idtracker@ietfa.amsl.com> <ec1c0951c06b42b780ad7601a27f1291@usma1ex-dag1mb1.msg.corp.akamai.com>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/a6ePRSLA7FJ_tRDD46mb1hHcUhs>
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2016 15:57:29 -0000

On Fri, 16 Dec 2016, Salz, Rich wrote:

> Is it just me, or would others find "Changed state from ... to ..." easier to follow?

I've said the same in the past. It's just inhuman and error prone for
the reader. Even if it is easier for whatever code that spits it out.

Paul

v2.23.0 | Report a Bug | By Email