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

Julian Reschke <julian.reschke@gmx.de> Mon, 29 August 2016 16:36 UTC

Return-Path: <julian.reschke@gmx.de>
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 C16E012B00B for <apps-discuss@ietfa.amsl.com>; Mon, 29 Aug 2016 09:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham 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 f8ifcN8yLoB9 for <apps-discuss@ietfa.amsl.com>; Mon, 29 Aug 2016 09:36:12 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D44C612B005 for <apps-discuss@ietf.org>; Mon, 29 Aug 2016 09:36:11 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.78.105]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LdKs1-1bEONx1Nx3-00iTJ3; Mon, 29 Aug 2016 18:35:24 +0200
To: Erik Wilde <erik.wilde@dret.net>, IETF Apps Discuss <apps-discuss@ietf.org>
References: <410cba92-83fa-8e4c-73ff-ac97ea5f8d32@gmx.de> <b6275d6d-e9ab-8b39-a6f3-3ff8d543c41f@dret.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <865f01b1-9c3e-e767-f3f0-ece2fe4f0087@gmx.de>
Date: Mon, 29 Aug 2016 18:35:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <b6275d6d-e9ab-8b39-a6f3-3ff8d543c41f@dret.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Nntq4bxI4wIg4cAY18pMRhPo5rwYTnG4LoqRnl6Vfr0gXlauD/G diiAq7DYHWEbjdGDeL19L7wfMDL06xjKTCH3OMKgZq4xIxrHOaWawiVruONcKSxlfQYvsHY pYiMj2izcMkmLvtNPsXP/O594+MfGTfh3LyQlwC273HCc1+SJ2vOvcKmMt0WJn/faOWuJps aaTQsJNEsSiFXc0lySTXw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:b3LV0dlFe/g=:aBdVD/0DKXxSIZZX3OAOMi r8/84Vw15pmiCVXsQ75nyzxiT7lU+C7Zq3kLSMzMxEBxZzR5d7yEJXDYPc7J3OVfr1Y2KMFaT rxyxE6fSHlLfSWCyvKFNAd+Is4HdvHgPKc/SxmTiLQcskXuo8lMV0X8siU2XFlYxGSiuUs9Kf HBcANZQIZMpb57OfJ9uzLLnAbeKRvbCow0BRnshp0c/CgFdND7W37WEcddhgvgCB+eVrGf6uL LvIHtrmAj5QAfcQicQ2Pm+KmK5cmb4G8q1ZxFdiaTdF4/4c0yMz8y57gMiVpjh4hZGS1u6tg7 7S/Rh6qGGEGH0ZjjgyGsXU+HEZE2GTnP8QitRNAmXW84+OHe09+ZgJHcJi5KnFnQWI35I2m6g I2+Xx7OZ2QTUXeKWacXON+CkvJPVbHnE7twRINuBL/J/quOpsnYwyWFm71MeS6f2FNG7eeJHK n4p4n/lCON8vnLeQgKd94v6g0WR36KtkI1Ih6MH/+CqBaOMtkel9RK4jUwaJ392g+ULYeC9LF 5MP+QONwUzlyhzQSOVDkBCVKyscl6GtDazWOn5B0zZ0dIu1lIspBPvESWZd+Ue7BmzszU3cwh SybTSjjkPcxDXI9uWqNuahSSJ1lji0TQ+JUJ/wAiDW65CwCYHluQD32DufcdWma3F/SO8Bhpk WSNLQMnVZ4TbQurr0SoTTWdjD8cd3RMP4zPPNzN9cs2Ldgi5OmR3YhiPy7k1nP6yvd+ikRZIu 1+U/+ZXLELOSKXrM7vSxdQswBafcW/R/XDKqm6C1wyZ5Ol7+RIIzKaI059NYPLHvjB4OIwTYN OaKJfhA
Archived-At: <https://mailarchive.ietf.org/arch/msg/apps-discuss/pWbunntQpNM7toZ9S8JgkSVO8ac>
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: Mon, 29 Aug 2016 16:36:14 -0000

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