Re: [apps-discuss] URI templates in Link header fields

Mark Nottingham <mnot@mnot.net> Tue, 30 August 2016 17:08 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3501C12D608 for <apps-discuss@ietfa.amsl.com>; Tue, 30 Aug 2016 10:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.553
X-Spam-Level:
X-Spam-Status: No, score=-1.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=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 9o6CAfEI16O6 for <apps-discuss@ietfa.amsl.com>; Tue, 30 Aug 2016 10:08:26 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (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 BEBB712B039 for <apps-discuss@ietf.org>; Tue, 30 Aug 2016 10:08:26 -0700 (PDT)
Received: from [10.0.3.253] (unknown [209.49.225.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 827A122E257; Tue, 30 Aug 2016 13:08:07 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <865f01b1-9c3e-e767-f3f0-ece2fe4f0087@gmx.de>
Date: Tue, 30 Aug 2016 09:41:21 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <64FC8E9D-03A2-496D-B382-612364F86C99@mnot.net>
References: <410cba92-83fa-8e4c-73ff-ac97ea5f8d32@gmx.de> <b6275d6d-e9ab-8b39-a6f3-3ff8d543c41f@dret.net> <865f01b1-9c3e-e767-f3f0-ece2fe4f0087@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/apps-discuss/PyMhI-qyQpb3Sd0o5JMiNvNdeTU>
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] URI templates in Link header fields
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 30 Aug 2016 17:08:29 -0000

See also:
  https://www.ietf.org/archive/id/draft-nottingham-link-template-01.txt


> On 30 Aug 2016, at 2:35 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 2016-08-29 17:30, Erik Wilde wrote:
>> hello julian
>> 
>> On 2016-08-29 01:42, Julian Reschke wrote:
>>> In the meantime, I heard of a few cases where people were trying to use
>>> templates in Link header fields (an obvious thing to do), and came up
>>> with hacks to do so with the existing Link header field.
>>> I'm tempted to work on a small spec that defines an experimental new
>>> header field, similar to Link but allowing templates.
>> 
>> @mnot has been working on collecting ideas for an update to RFC 5988 for
>> a while now. maybe that's one more motivation to go forward with this?
>> i'd certainly be willing to put in some time to get it off the ground.
>> 
>> https://github.com/mnot/I-D/issues?q=is%3Aissue+is%3Aopen+label%3Arfc5988bis
> 
> Yep, I'm aware of that...
> 
>>> Is anybody aware of existing code trying to use templates in Link header
>>> fields? If so, please report over here (or in doubt send private email).
>> 
>> this is not really code, but people want to use URI templates and there
>> have been some efforts to provide a context that makes that more easy:
>> 
>> - @mnot's https://tools.ietf.org/html/draft-nottingham-link-hint
>> 
>> - my own https://tools.ietf.org/html/draft-wilde-link-desc
>> 
>> - part of the JSON home model:
>> https://tools.ietf.org/html/draft-nottingham-json-home#section-3.1
>> 
>> if i recall correctly all of these have slightly different use cases and
>> models, but (unsurprisingly) also a lot of overlap. it would be great to
>> consolidate all of this so that tooling and implementations can rely on
>> a robust spec.
> 
> Agreed.
> 
> Thanks for the feedback, Julian
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

--
Mark Nottingham   https://www.mnot.net/