Re: [Acme] restification of acme

Anders Rundgren <anders.rundgren.net@gmail.com> Wed, 21 January 2015 08:02 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01D1B1A039B for <acme@ietfa.amsl.com>; Wed, 21 Jan 2015 00:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 uGzCWxAoAVTw for <acme@ietfa.amsl.com>; Wed, 21 Jan 2015 00:02:05 -0800 (PST)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C1E51A039A for <acme@ietf.org>; Wed, 21 Jan 2015 00:02:05 -0800 (PST)
Received: by mail-wi0-f176.google.com with SMTP id em10so13526981wid.3 for <acme@ietf.org>; Wed, 21 Jan 2015 00:02:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=yMho2l2xzvofb8KHSZS5S1N2yoMcAuCvcnS6OluljtI=; b=UpO4UfG/xKlu5KMD1ShexLw/TB2kUY53D1tKozXXD7ZHDY8J122V1LSpbmPOIJekHE qJl+EXIlIA+irxU7e6hRZupOgqQei2TQDGjcRvvZE0YKIf8bGGjLvBgtKIvbQNgzEssJ WyzvJ8R6Rfs4xoIDohVI38XCrPWZTYxdeJZJbZgVbTCbhxeJrXEkNChyoehdOUa9ckvv 0HuKnwn/b4NOx85QIfv0ODmip2Vhip5+kXhAcn4R4CRcz208CnoTGfCC2PIi+8nbvu2z zRHRI6N5lrn2+A13CLUuczXQbk9FqxlE1bFoOtHf063ihx8G7NrlSXPWaYUWkdpnAKJV 4AzQ==
X-Received: by 10.180.231.33 with SMTP id td1mr52893523wic.33.1421827324070; Wed, 21 Jan 2015 00:02:04 -0800 (PST)
Received: from [192.168.1.79] (48.194.130.77.rev.sfr.net. [77.130.194.48]) by mx.google.com with ESMTPSA id da2sm14224507wjb.21.2015.01.21.00.02.03 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Jan 2015 00:02:03 -0800 (PST)
Message-ID: <54BF5CF0.5050106@gmail.com>
Date: Wed, 21 Jan 2015 09:01:52 +0100
From: Anders Rundgren <anders.rundgren.net@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Jacob Hoffman-Andrews <jsha@eff.org>, Phillip Hallam-Baker <phill@hallambaker.com>, Fraser Tweedale <frase@frase.id.au>
References: <20150120080427.GB1238@bacardi.hollandpark.frase.id.au> <CAMm+LwgKLSCSvx1QHL+HLgtc0NK8-HygpgXEF81unbcxWt6Uvw@mail.gmail.com> <54BEB082.3040901@eff.org>
In-Reply-To: <54BEB082.3040901@eff.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/MIgTq2W4v5Ux_EJcD6cBigaTDYs>
Cc: "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] restification of acme
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jan 2015 08:02:07 -0000

I'm not going to comment on the conversion of ACME into a REST-based design, I just find
it amusing/interesting/odd that I in my [sort of] "ACME for mobile devices", SKS/KeyGen2,
came up with essentially the diametrically opposed solution like:

- HTTP POST to the same URL using HTTP 200 as the sole response code
- Uniquely identifiable JSON message classes
- Clear-text JSON signatures
- Key attestations rather than PKCS #10/PoP

Message classes are registered and then automatically instantiated in one place and
after that dispatched to the appropriate handler which also provides the return object.

This is like an extremely scaled-down version of the thing that made people turn to REST,
the bloated and ugly beast known as WS-*.

Anders