Re: [httpapi] Fwd: New Version Notification for draft-nottingham-link-template-03.txt

Mark Nottingham <mnot@mnot.net> Wed, 01 September 2021 23:24 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8773A1D9C for <httpapi@ietfa.amsl.com>; Wed, 1 Sep 2021 16:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=dL+3xju0; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VpQo6T4Y
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 IG0yYO6etweO for <httpapi@ietfa.amsl.com>; Wed, 1 Sep 2021 16:24:19 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A3B93A1D98 for <httpapi@ietf.org>; Wed, 1 Sep 2021 16:24:19 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id EDB993200A09; Wed, 1 Sep 2021 19:24:17 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 01 Sep 2021 19:24:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=c 6ArXo/0aBsB6viobzw1ZmWxF5zhMQU7S9xpesINgEY=; b=dL+3xju09cMTQbKWg a6+VKuw174Geq7th3cz6RB1lA+wQ96UjfISM1QcFwoC92eJW0XgSKQ89OZtW69/y j6NQvFRR+WrYWZ7sS4JBBZk70RDXr4l/0vU6OLmUeM+q/sg6UO2GIq+5k/Kfqor6 oFS+96WzwIJm3YesRAYGH3cJaGUvgfhoSYCN+bw0/K1TEhXIZ/5yhphD1TPpUVV2 cneOA4dbThUCjP+zj/aFHBBlddFywCSufVVmXYvGNBPs36ysgsMFHLBcH4fLTnPk DGRYQFswegDI12ty0NsfJuWr6bxzQSXkrGvSGu6acl7p45ThMx1rMmkJqXhmMEsE 3jLBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=c6ArXo/0aBsB6viobzw1ZmWxF5zhMQU7S9xpesINg EY=; b=VpQo6T4Y68DUQIjHcDhozgoxX/V6sAk5S0BK+cgK4mtuYNCDTOSE7QpxK F6Rb2iFIhKOymbzH1UNHawxLAJkgY+8BfclfwlnZuWd/ZTwGhCVgFg+Xr/72yMv9 mac3cFqc+3VAQp6Ng6RSLf8LBs0EZvRNkyHFH8L6zd4v7qv3RaTpnpqb7JzgRFrC ZFWwbYqJ7+Q1wbyqn+NEndLwHSFjX5k2UbmIeeS9ntebrhzaBcyzg38gUEIQGyn6 VFPCK2Np2A1ea7Xsbk0qo+M0iduvrAseZHU38V6lelxoocfQxesn4E2KWb3Ofjqg sKAuABrS8FrDAgaWAjgGVpmabCCvg==
X-ME-Sender: <xms:ngswYeov9GcyLX1oxS5ICW_PrS_NEOSYpGoF9B4fgxB-wJjpCpJx0A> <xme:ngswYcq-sgV2sH0SAuYf6QFODW1tzm4Da3-7K5zxuVv89I0AxPck70RzQVqs1sMkK ZIV5i7prhVEP3Fo-A>
X-ME-Received: <xmr:ngswYTMQHQrPThmWxlSKmOKH0juTQX5Vyc2jHqohNbFMdu8FvMBUyYWTJUER2f-tPoe2dgU95rsiZ4eeF5Q-yEBXr6A0EsQNmOx0j5h8gTflpZkxmg1qhh19>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddvgedgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne goufhushhpvggtthffohhmrghinhculdegledmnecujfgurheptggguffhjgffgffkfhfv ofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnh hothesmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpedvfeejtdejffffvdehffei keeiudeuheeugfeuhfegiefgveduffdvudelfeeuheenucffohhmrghinhepghhithhhuh gsrdhiohdpihgvthhfrdhorhhgpdhmnhhothdrnhgvthenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:ngswYd4j1dimXtRMf9ATkdt1g080ZVHmiRpQtNQTK0ZPeAVsKle5Rg> <xmx:ngswYd595aGfiu_E2FOBk2FAKDBCFSNIsVVpx7_48NDlDQ5tAp9Zpg> <xmx:ngswYdinWisPq8NAaPP20AMWECK0xx6ApnrqCzhyAZuX4hFjXCjfow> <xmx:oQswYXkwzzT-U1C3_ICXP5ZPByWHipbJtyRozKIq3NmwvEaJ0_-hAg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 1 Sep 2021 19:24:13 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <acb765f3-eb1c-459d-a480-89bcf53eb56a@www.fastmail.com>
Date: Thu, 02 Sep 2021 09:24:04 +1000
Cc: httpapi@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8ACB36A-C2C2-4DE8-9AD3-6FA547E8964C@mnot.net>
References: <163047452150.9745.15606863469504346040@ietfa.amsl.com> <63DA4A31-930D-444D-9A4D-A639DB4D22E6@mnot.net> <acb765f3-eb1c-459d-a480-89bcf53eb56a@www.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/-rmFohZo_cWQlLeGN89f4JEWwIw>
Subject: Re: [httpapi] Fwd: New Version Notification for draft-nottingham-link-template-03.txt
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2021 23:24:26 -0000

On 1 Sep 2021, at 10:39 pm, Martin Thomson <mt@lowentropy.net> wrote:
> 
> Why not use structured fields for this?  As far as I can see, that just means <> becomes "", but the practical benefits seem to outweigh a small cosmetic consistency.

Good q. I think it should definitely be considered. This is currently following the Link syntax because a) it was written before SF, and b) Someone who's familiar with Link is going to wonder why. I doubt (b) is good enough.

It does beg the question of whether there should be a SF variant of Link. See also <https://mnot.github.io/I-D/binary-structured-headers/#links>.


> (Like Julian, var-base seems ... challenging.  I found the description of it hard to follow, but it seemed like the order of resolving against base URIs was unexpected.)

Yeah, that's only half-baked; needs more thought (and as Julian points out, examples).

Cheers,


> On Wed, Sep 1, 2021, at 15:36, Mark Nottingham wrote:
>> Hi all,
>> 
>> I've had this spec on the back burner for a *long* time, because I 
>> wanted to make sure it was actually useful to someone before 
>> progressing it.
>> 
>> I've heard from a few people that it would be useful for them in the 
>> real world, so I'd like the WG to consider adoption.
>> 
>> Any thoughts?
>> 
>> Cheers,
>> 
>> 
>>> Begin forwarded message:
>>> 
>>> *From: *internet-drafts@ietf.org
>>> *Subject: **New Version Notification for draft-nottingham-link-template-03.txt*
>>> *Date: *1 September 2021 at 3:35:21 pm AEST
>>> *To: *"Mark Nottingham" <mnot@mnot.net>
>>> 
>>> 
>>> A new version of I-D, draft-nottingham-link-template-03.txt
>>> has been successfully submitted by Mark Nottingham and posted to the
>>> IETF repository.
>>> 
>>> Name: draft-nottingham-link-template
>>> Revision: 03
>>> Title: The Link-Template HTTP Header Field
>>> Document date: 2021-09-01
>>> Group: Individual Submission
>>> Pages: 5
>>> URL:            https://www.ietf.org/archive/id/draft-nottingham-link-template-03.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-nottingham-link-template/
>>> Html:           https://www.ietf.org/archive/id/draft-nottingham-link-template-03.html
>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-nottingham-link-template
>>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-nottingham-link-template-03
>>> 
>>> Abstract:
>>>  This specification defines the Link-Template HTTP header field,
>>>  providing a means for describing the structure of a link between two
>>>  resources, so that new links can be generated.
>>> 
>>> 
>>> 
>>> 
>>> The IETF Secretariat
>>> 
>>> 
>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
>> 
>> -- 
>> httpapi mailing list
>> httpapi@ietf.org
>> https://www.ietf.org/mailman/listinfo/httpapi
>> 
> 
> -- 
> httpapi mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi

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