The Link-Template HTTP Header Field
draft-ietf-httpapi-link-template-04
Yes
Zaheduzzaman Sarker
No Objection
Erik Kline
Jim Guichard
John Scudder
(Andrew Alston)
No Record
Deb Cooley
Francesca Palombini
Gunter Van de Velde
Mahesh Jethanandani
Orie Steele
Warren Kumari
Note: This ballot was opened for revision 03 and is now closed.
Zaheduzzaman Sarker
Yes
Erik Kline
No Objection
Jim Guichard
No Objection
John Scudder
No Objection
Murray Kucherawy
No Objection
Comment
(2024-02-15 for -03)
Sent
Feedback from incoming ART AD, Orie Steele: I'd prefer to see specific security considerations associated with "Display Strings", based on this MUST: "These Parameter values MUST be Strings, unless they contain non-ASCII characters, in which case they MUST be Display Strings. " ... and the following comment in the normative reference: "It is NOT RECOMMENDED that they be used in situations where a String (Section 3.3.3) or Token (Section 3.3.4) would be adequate, because Unicode has processing considerations (e.g., normalization) and security considerations (e.g., homograph attacks) that make it more difficult to handle correctly."
Paul Wouters
(was Discuss)
No Objection
Comment
(2024-02-15 for -03)
Not sent
I see these were addressed in -03, apologies for not noticing that earlier.
Roman Danyliw
No Objection
Comment
(2024-02-09 for -03)
Not sent
Thank you to Radia Perlman for the SECDIR review.
Éric Vyncke
No Objection
Comment
(2024-02-12 for -03)
Not sent
Nice and clear shepherd write-up for a useful document (even to my non-expert eyes). Minor regret: the companion documents in other WG are not on the same telechat date.
Deb Cooley
No Record
Francesca Palombini
No Record
Gunter Van de Velde
No Record
Mahesh Jethanandani
No Record
Orie Steele
No Record
Warren Kumari
No Record
Andrew Alston Former IESG member
No Objection
No Objection
(for -03)
Not sent
Robert Wilton Former IESG member
No Objection
No Objection
(2024-02-12 for -03)
Sent
Hi Mark, Thanks for this document. I have one minor comment: (1) p 1, sec 1. Introduction This specification defines a HTTP header field [HTTP] for conveying templates for links in the headers of a HTTP message. It is complimentary to the Link header field defined in Section 3 of [WEB-LINKING], which carries links directly. As a minor comment, it wasn't entirely clear to me what these HTTP templates are used for and why it is helpful to carry them in the HTTP headers (as opposed to the body). Hence please consider whether adding a paragraph to the intro, highlighting potential use cases, or perhaps giving an example of what is useful for may be helpful to readers. Regards, Rob