[httpapi] Opsdir telechat review of draft-ietf-httpapi-link-template-03

Dhruv Dhody via Datatracker <noreply@ietf.org> Wed, 14 February 2024 10:26 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dhruv Dhody via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-httpapi-link-template.all@ietf.org, httpapi@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170790641388.60597.15299467404561267997@ietfa.amsl.com>
Reply-To: Dhruv Dhody <dd@dhruvdhody.com>
Date: Wed, 14 Feb 2024 02:26:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/QohBQMhH6HraOQ3Kdi1n4-Hkh4c>
Subject: [httpapi] Opsdir telechat review of draft-ietf-httpapi-link-template-03

Reviewer: Dhruv Dhody
Review result: Ready

Reviewer: Dhruv Dhody
Review Result: Ready

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

This document defines a new HTTP header field, the "Link-Template". I don't
think this new field creates new operational issues.

Just a few suggestions -

- I wish the document had more background information on why this header field
is needed.

- Referencing RFCs - consider using the [RFCXXXX] style, currently, it is a mix
of [STRING] and [RFCXXXX]. BTW
https://www.rfc-editor.org/rfc/rfc7322.html#section-4.8.6.2 says you should use
[RFCXXXX] style.

Thanks!
Dhruv

[httpapi] Opsdir telechat review of draft-ietf-ht… Dhruv Dhody via Datatracker
Re: [httpapi] Opsdir telechat review of draft-iet… Julian Reschke