IETF Logo Mail Archive

Re: [httpapi] [IANA #1273263] expert review for draft-ietf-httpapi-link-template (http-fields)

"Roy T. Fielding" <fielding@gbiv.com> Mon, 05 February 2024 19:54 UTC

Return-Path: <fielding@gbiv.com>
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 0BE61C14F61A for <httpapi@ietfa.amsl.com>; Mon, 5 Feb 2024 11:54:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gbiv.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odFORRkIXZt9 for <httpapi@ietfa.amsl.com>; Mon, 5 Feb 2024 11:54:37 -0800 (PST)
Received: from serval.cherry.relay.mailchannels.net (serval.cherry.relay.mailchannels.net [23.83.223.163]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4E58C14F5E6 for <httpapi@ietf.org>; Mon, 5 Feb 2024 11:54:36 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 437007627A0; Mon, 5 Feb 2024 19:54:36 +0000 (UTC)
Received: from pdx1-sub0-mail-a203.dreamhost.com (unknown [127.0.0.6]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id A7871765380; Mon, 5 Feb 2024 19:54:35 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1707162875; a=rsa-sha256; cv=none; b=+XuZDil3DUvADzAvPe0ZiVh8xqhE2sbvCS8EVzq0Kkj8FVe0KknWXLJOnQWbT11QjnwEHA SeXmU3gwVTYtZ8oq2iTiTQiCUvFF47qGZTG4kVed1W8NXN3+o5bDaBnjV2ol0oeNKfUSjN +8NOtkZh5OPkfE67f+qBeVXCIEB0jdGAe3KYAdXqthIK/s6+PMsd2zq0bgnZqAQMrZG4Pd qHrLOyg/Y4nDdBrSk47+wIe8UwQ0kHlRwkQpDI6mc4r2TSf3WtX+xN1qK8q9JfE0i5yc31 ZTT/n0MXLTr7bUBm5FypPuSjURjKlod0Ub7N2thRFToY7MGlAgcdIWfvw1HzWw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1707162875; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=3+JNIWHh75O6x+fqGA+Rlt3TaYboBboH+R1m3BR1YPg=; b=CFVHYOFTntT3oQEhLrgxpfP8J4+mGFlbofyDRyAK4bpLasEqAVzatqmx53pBnzE24FkucB 1CzgdY41nicoy/9v7SOH3K8n1cy8+Si0+e1kCsg/2LQDmC/C1PQpM9uNSvKnE/qB8KXmbx hMj80ExiENVueCPIFOZ/YDPQivwTlahXStqQrVZQ46z7XJ6S40PHIQ9PaRiSPMvWuXu1I+ MN4STFsQQEdMZGH4uhk4kWhboUeXqzNYzVMGKEWHoDM7AeNBhjHh254tpEKo+NLh11tHo+ EbGqdYD+9qvAQiGEKNj7lFO7eiC+R/EtJ7JfVM9fc0Hb6BuFfuySc1DJdeYFlg==
ARC-Authentication-Results: i=1; rspamd-55b4bfd7cb-lhtzx; auth=pass smtp.auth=dreamhost smtp.mailfrom=fielding@gbiv.com
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|fielding@gbiv.com
X-MailChannels-Auth-Id: dreamhost
X-Daffy-Eight: 0256135326a3d3d0_1707162875935_3431273200
X-MC-Loop-Signature: 1707162875934:1368366083
X-MC-Ingress-Time: 1707162875934
Received: from pdx1-sub0-mail-a203.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.108.147.48 (trex/6.9.2); Mon, 05 Feb 2024 19:54:35 +0000
Received: from smtpclient.apple (ip72-194-73-53.oc.oc.cox.net [72.194.73.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by pdx1-sub0-mail-a203.dreamhost.com (Postfix) with ESMTPSA id 4TTHCH1LRvzLJ; Mon, 5 Feb 2024 11:54:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gbiv.com; s=dreamhost; t=1707162875; bh=ONijwdUGbWEPg0qnX4gS0eESuNeKduErMWCdUxZRhCI=; h=Content-Type:Subject:From:Date:Cc:Content-Transfer-Encoding:To; b=ZythfFxqS/VYku7FiNc+ctTdfBI6RLQcnu+kTHmg9ks/bdBowUJu+dK7psgyXWD3N zX1YKZhSNVdG72/VvGUYJPH/ZQGvF5MpUl1hDLkZeyU1At3jo3+YzFwWluR3fAalqq DC/tPByzjUjGlzYuhvFfo133lf7+98OgVwhxf3F3kulDoO2iST7MqfRVAa4MjOUCY8 7cOYCPHSuDEYrt8vRrawec5I3EVJ6xthfNrpDb5yT8QVWiyf0hmSI9yis3Alk0bGDR XgXczeI8eYYhQbKAGZuapSH+ICyXwoF3SP+M3lncRfaI92P2ilUqt/436DupgkcGhx wz050PPWrr67g==
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <rt-5.0.3-446863-1707161759-1080.1273263-9-0@icann.org>
Date: Mon, 05 Feb 2024 11:54:23 -0800
Cc: httpapi@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <471573B4-812A-444F-9485-E8585B57B1CC@gbiv.com>
References: <RT-Ticket-1273263@icann.org> <rt-5.0.3-160229-1684947950-583.1273263-9-0@icann.org> <rt-5.0.3-160220-1684948461-859.1273263-9-0@icann.org> <8DB17B43-BD93-4BCE-A56B-07E0769051F6@gbiv.com> <rt-5.0.3-167887-1684957333-396.1273263-9-0@icann.org> <rt-5.0.3-446863-1707161759-1080.1273263-9-0@icann.org>
To: drafts-expert-review-comment@iana.org
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/vUn5o1UEPnoIg2Pf-8DmdssApJE>
Subject: Re: [httpapi] [IANA #1273263] expert review for draft-ietf-httpapi-link-template (http-fields)
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 05 Feb 2024 19:54:42 -0000

My prior expert review still applies to this draft (approved).

Unrelated to IANA, I also noticed a typo

   "Structure Field" -> "Structured Fields

and there are several places in the new text where parameter
has been oddly capitalized as "Parameter".

....Roy


> On Feb 5, 2024, at 11:35 AM, Amanda Baber via RT <drafts-expert-review-comment@iana.org> wrote:
> 
> Hi Roy (cc: httpapi WG),
> 
> Does version -03 of this document need another review? You approved -02:
> 
> https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-link-template-03
> 
> thanks,
> 
> Amanda Baber
> IANA Operations Manager
> 
> On Wed May 24 19:42:13 2023, fielding@gbiv.com wrote:
>>> On May 24, 2023, at 10:14 AM, David Dong via RT <drafts-expert-
>>> review-comment@iana.org> wrote:
>>> 
>>> Dear Roy and Mark (cc: httpapi WG)
>>> 
>>> As the designated experts for the Hypertext Transfer Protocol (HTTP)
>>> Field Name registry, can you review the proposed registration in
>>> draft-ietf-httpapi-link-template-02 for us? Please see:
>>> 
>>> https://datatracker.ietf.org/doc/draft-ietf-httpapi-link-template/
>>> 
>>> The due date is June 7th, 2023.
>>> 
>>> As Mark is the author of this draft, we will act on Roy's review.
>>> 
>>> If this is OK, when the IESG approves the document for publication,
>>> we'll make the registration at:
>>> 
>>> https://www.iana.org/assignments/http-fields/
>> 
>> The registration information in section 4 looks good and has the
>> appropriate status,
>> so I believe this to be OK for registration by IANA.
>> 
>> As for HTTP considerations, I expect Link-Template to be potentially
>> useful as
>> a trailer as well, particularly to supply optional links determined by
>> the sender
>> while content is being generated (i.e., after the header section has
>> been sent).
>> However, the spec doesn't even mention trailers. This would be a good
>> time
>> for Mark to review what we wrote in
>> 
>> https://www.rfc-
>> editor.org/rfc/rfc9110.html#considerations.for.new.fields
>> 
>> and be sure that the spec documents those aspects not already covered
>> by the
>> choice of structured syntax. [Use of Link in trailers wasn't mentioned
>> in RFC8288.]
>> 
>> Cheers,
>> 
>> ....Roy
>

v2.23.0 | Report a Bug | By Email