Skip to main content

IETF Last Call Review of draft-ietf-grow-nrtm-v4-08
review-ietf-grow-nrtm-v4-08-httpdir-lc-reschke-2026-02-27-00

Request Review of draft-ietf-grow-nrtm-v4
Requested revision No specific revision (document currently at 11)
Type IETF Last Call Review
Team HTTP Directorate (httpdir)
Deadline 2026-03-04
Requested 2026-02-19
Requested by Mohamed Boucadair
Authors Sasha Romijn , Job Snijders , Edward Shryane , Stavros Konstantaras
I-D last updated 2026-06-02 (Latest revision 2026-04-17)
Completed reviews Genart IETF Last Call review of -08 by Paul Kyzivat (diff)
Secdir IETF Last Call review of -08 by Watson Ladd (diff)
Httpdir IETF Last Call review of -08 by Julian Reschke (diff)
Opsdir IETF Last Call review of -08 by Menachem Dodge (diff)
Rtgdir IETF Last Call review of -08 by Daniele Ceccarelli (diff)
Artart IETF Last Call review of -08 by Claudio Allocchio (diff)
Assignment Reviewer Julian Reschke
State Completed
Request IETF Last Call review on draft-ietf-grow-nrtm-v4 by HTTP Directorate Assigned
Posted at https://datatracker.ietf.org/wg/grow/about/
Reviewed revision 08 (document currently at 11)
Result Ready w/nits
Completed 2026-02-27
review-ietf-grow-nrtm-v4-08-httpdir-lc-reschke-2026-02-27-00
Note that I’ve been reading this purely from an HTTP point of view.

The only thing related to HTTP is that data is exchanged over HTTP, so it’s not
really HTTP-based.

With regard to terminology, it could be cleaned up to distinguish between the
actual HTTP protocol and the requirement (?) to use only HTTPS.

One other thing I noticed is the requirement to exchange JSON in UTF-8:

"All files MUST use UTF-8 encoding [STD63] and MAY be compressed with GZIP
[RFC1952]."

Being UTF-8 encoded is already required by
https://www.greenbytes.de/tech/webdav/rfc8259.html#rfc.section.8.1

So I’d avoid making this a BCP 14 requirement (just mentioning it, of course,
is fine).