Re: [apps-discuss] draft-ietf-weirds-bootstrap-00 and our lawn -- feedback?

Nico Williams <nico@cryptonector.com> Mon, 17 February 2014 04:39 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC1A1A0340 for <apps-discuss@ietfa.amsl.com>; Sun, 16 Feb 2014 20:39:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 UT-s2hAD0MtH for <apps-discuss@ietfa.amsl.com>; Sun, 16 Feb 2014 20:39:03 -0800 (PST)
Received: from homiemail-a27.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7021A033C for <apps-discuss@ietf.org>; Sun, 16 Feb 2014 20:39:03 -0800 (PST)
Received: from homiemail-a27.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a27.g.dreamhost.com (Postfix) with ESMTP id E454959805F for <apps-discuss@ietf.org>; Sun, 16 Feb 2014 20:39:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=crJ4zaLbDPmNpVIjTmxX +kif/wg=; b=LVn4Z61caSCiIx5QhbZ/5m2ubh8NZKg55BQp8PRJdKNsAtBYDuhE QO1//gyU8ZyckOJtO5CtzD/5qyXqlTzIx/G0gI3sCNMP/Z/KRWZe7m2qhHsHp6Uj OChxVOMfUIPNDmhM1xZoqD8Y2D8QE2C+2QDqKR7k2Q01BO19szWrSb4=
Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a27.g.dreamhost.com (Postfix) with ESMTPSA id 8D22A598058 for <apps-discuss@ietf.org>; Sun, 16 Feb 2014 20:39:00 -0800 (PST)
Received: by mail-we0-f169.google.com with SMTP id t61so10386295wes.14 for <apps-discuss@ietf.org>; Sun, 16 Feb 2014 20:38:58 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0K1Hxw+wrudXve5GvGheNKBpU0t751LTsTDczjyxgHQ=; b=l+22dUdV315vgu3AwJsUuPjlqKxy+22S9oCfFNL3aVf68EN55rDCLYMOgRc3sxxdbt mfmkOiNzdieUOaOrRnsJnxQzGP1e8ZM27PimeYkSVUE/3bLUvRV6QgNoW/ySbo+YB8U9 I+cSmAW/GdJ7dbd+wHnLY2Bi9s/AYClu6IK8MpdVMGfYbJt8NrVY6qybCg2s9LcxxWid C3bItNJAYSi/y/E5r+aSHvLMG3ONDE3Ugc8iepA5piI1ZRz2gAgv539mYzCBX3HiD8dD 8E6wJx1FQiW2+Jh2/bcK9XM2ylpkeMo5jI+MxQ8ZoCR5/p9hCrZXVE71k39XM1XxYHWi ijug==
MIME-Version: 1.0
X-Received: by 10.180.98.35 with SMTP id ef3mr11162718wib.39.1392611938947; Sun, 16 Feb 2014 20:38:58 -0800 (PST)
Received: by 10.217.108.132 with HTTP; Sun, 16 Feb 2014 20:38:58 -0800 (PST)
In-Reply-To: <CAKioOqsrRc6FztKtLtTShYP7gPi5TN5OvO710vAqZc0ni68cXA@mail.gmail.com>
References: <CAKioOqsrRc6FztKtLtTShYP7gPi5TN5OvO710vAqZc0ni68cXA@mail.gmail.com>
Date: Sun, 16 Feb 2014 22:38:58 -0600
Message-ID: <CAK3OfOhuKQ0YeBhO7nBQ_LHhgDcjPyHFGHj9pwut2ywWJ1JUBQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: darrel@tavis.ca
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/AaVHRkP4TZaXPLyxMuKTpkQoIQs
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] draft-ietf-weirds-bootstrap-00 and our lawn -- feedback?
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 04:39:05 -0000

On Sun, Feb 16, 2014 at 10:09 AM, Darrel Miller <darrel.miller@gmail.com> wrote:
> Your client is a three line shell script because someone took the time
> to write programs like wget that implement a standard protocol.  It
> would surprise me if someone hasn't already written a URI template
> processing utility that you can call from your script.  Your 3 lines
> would likely end up being 4 lines. Pseudocode would look something
> like,

It'd probably still be three loc because where RDAP says to find base
URIs now one would find templates, and then it's just a matter of
passing the named parameters' values to wget in the one command.
Granted, wget (and curl) lacks template support, but it shouldn't be
hard to fix that (or to implement a command-line template expander).

Having just met and read RFC6570, I must say, it seems like the right way to go.

Here's a list of open source URI template implementations:

https://code.google.com/p/uri-templates/wiki/Implementations

Nico
--