Re: [AKO Warning - Message fails DKIM verification] Re: Requesting comments on draft-cheney-safe-02.txt

John Levine <johnl@taugh.com> Thu, 13 August 2009 00:40 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n7D0ePsM046465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Aug 2009 17:40:25 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n7D0eP8n046464; Wed, 12 Aug 2009 17:40:25 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n7D0eJ6h046457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-smtp@imc.org>; Wed, 12 Aug 2009 17:40:23 -0700 (MST) (envelope-from prvs=0469f01fa9=johnl@iecc.com)
Received: (qmail 36952 invoked from network); 13 Aug 2009 00:40:18 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 13 Aug 2009 00:40:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; olt=johnl@user.iecc.com; bh=NeA1txxsQ/MU9m8KxzjLAwW4MSyl+mLbDeQxDTQVjsY=; b=qgjqKiAyEsnaaF3qhqJYNA8OM60x2ZHOHNGLuiDwsmsJydxhk1Bp99qQ82/fdUPQ+rl8Xlb3MnQxfKJMANJvDui7J6Fbv/gZrrxpcgM8dxcykqzqB1lQL/PnVuAZkOu7E4aedscP2KAz+qXVmAx8LkuE3QDk6H+BXUR1hXqbCiY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; bh=NeA1txxsQ/MU9m8KxzjLAwW4MSyl+mLbDeQxDTQVjsY=; b=SumOn9Wbgq2V2ZetiOnqJByjZWf1XYAwiENtWS5uz/8Iz2h8SrZ6THaNDDlzjGddiZCfohK+gANdxzsNjcxD7nVbEDW8Qt7yu06b61AUz2fvj1Xs3D+wrytkkTWVrVUGZgeH3UvnFpZlL8jWOCNIVLzMWqd3hBTrHCCtnBE2ZQA=
Date: Thu, 13 Aug 2009 00:40:17 -0000
Message-ID: <20090813004017.27021.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@imc.org
Subject: Re: [AKO Warning - Message fails DKIM verification] Re: Requesting comments on draft-cheney-safe-02.txt
In-Reply-To: <f742d5fd23095.4a838353@us.army.mil>
Organization:
Cc: austin.cheney@us.army.mil
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

>> What they're saying (and I agree) is that the solution you've come up
>> with is unlikely to gain much attention -- or implementation.

>Specifically, why?  How is that a technology concern for a standards
>body?

Standards development is very labor intensive, and most of the people
who do IETF standards are volunteers working in our spare time.  We
don't have enough volunteer time to update the standards already in
global use, much less to invent new ones, and it just isn't a sensible
use of limited resources to work on stuff that's not likely to be
used.

You will also find that proposals that have working implementations,
at least as prototypes, get a lot more respect than purely paper
designs.  (We have an unlimited supply of those, see for example the
endless e-postage proposals in the ASRG and elsewhere.)  If you think
your plan is workable, get some people to implement it and see how
it works.

R's,
John

PS: If this seems to give an unfair advantage to people with software
development skills, I think that's deliberate.