IETF Logo Mail Archive

[apps-discuss] URI templates in Link header fields

Julian Reschke <julian.reschke@gmx.de> Mon, 29 August 2016 08:42 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 C537712D137 for <apps-discuss@ietfa.amsl.com>; Mon, 29 Aug 2016 01:42:10 -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 H1_GqT_FEceL for <apps-discuss@ietfa.amsl.com>; Mon, 29 Aug 2016 01:42:09 -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 0A92812D133 for <apps-discuss@ietf.org>; Mon, 29 Aug 2016 01:42:08 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.78.105]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MV1wf-1bcnck1jqv-00YNVB; Mon, 29 Aug 2016 10:42:03 +0200
To: IETF Apps Discuss <apps-discuss@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <410cba92-83fa-8e4c-73ff-ac97ea5f8d32@gmx.de>
Date: Mon, 29 Aug 2016 10:42:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:7ez3IwWTd/Qib7TBB1pXlXefIo11bFkmuDG3+TPVr0uDNoo17i5 wEAaoGvuGYNWXNENzVEZdHe7Syp8ffnWQxv7wryoCec47YnQgmPaMhWd5FeaaxYzntGAIH2 3vkvHcEXlrys907md2pxMzbj9jmLkl/UUCfwQCsHuSjrODxVFKDSKbVEXZluAD8kskNEGx6 ujgYywN0mylokiaKF1Q6Q==
X-UI-Out-Filterresults: notjunk:1;V01:K0:HsL62M5dIvE=:TVH7WK/DkjhQmKPVwAy7CT yZOmKbaGSzdAL6wyNTGiR34XdFEFRgDgd4BOwkSaxi1OflszpBADMa5VUcMfnfn/rjV5AD2A/ zcDHkLBPz7O98IgVIOhUC/cbUCpasPi5ArFOh4X17JZdjd0UiOK01B4uT3CnKqfLehQxzfyp3 4Kh2kgBquvrk2PTOznyZ7B3lU6Xm+MjY9B474xRPXhwdIX5jpFgmluRfrxvFFXlSHQZbFmgQA Hzi81wPJ0wQbkQMESWUIVvASIeu15X4C05Bb1bdIl5TwRI9hHtFCkpJJnCMAUzyhMN736EmPK jyBXkyEfRxtFo0iLAxLne4VM1kd9SyHSzIoD75DrGUOpbxGqQUmE7qPT1AQSztDXKzKLqO3B7 2QWxNlhsRYSIh4VJKabkPkQiVqAVn9r3sD0v8M1ggbEisPKJuPMt27CbgZUZ+tfryJVtUZBfh 92/nHTiA9OuL0kjzcVzoOF4CsEtqLGoikRsBsjUo3hy7fsyaKUtVbP27URZthOqvCGWQl3gN2 h0OD5Mq/qlfaVFIu/qSGWLW1do24W5JkWuZVQnMMxinoDjeuhNMX44i4A5lasAZs6K1zscpDr 5XgBjYoC4YUDFi6m3XlAOnpRdYbGunH4NJr/DkHzarmZOdg5EcXlwqMgtkaY+vVHZd6n/fdmR dgzySimGpaGoI2v4CmfWQdbA0cLruZjGHBrVvs6tjtTZ7HhfRi1s0j/wnsEW61+n4aYZnYJpm MBMgZ3FPF11kNp7iEaUhHNCsAh8H7gTg9gUJ2swqIgReuPl9Owo2ZuYepFC96njnFZYP0zbdt lMvPQVzGiiA0cvya6JOF4rHdht53Sn5Ui4TzfPHNl3uP27+LfdRI3V7a+gyRh0BsfbysudX0L ZYSaoyGcwhjb42kLhF45/+bBZKqgxileYZxBk0NEe8O2zwipPozpzmGjt+hJ68stdZhkaq+eo 2vwBHvoBTDk2awA9EQN7dS3+vHYA31L8xCJ3WBr7wa8biwokBVt1X
Archived-At: <https://mailarchive.ietf.org/arch/msg/apps-discuss/ra3ZKg2nouh1RA87IJxSKjI6thU>
Subject: [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 08:42:11 -0000

Hi there.

RFC 5988, defining the HTTP Link header field, predates RFC 6570, 
defining URI templates.

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.

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).

Best regards, Julian

v2.23.0 | Report a Bug | By Email