Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)
draft-ietf-jmap-mdn-17
Yes
(Barry Leiba)
No Objection
Erik Kline
Warren Kumari
(Alissa Cooper)
(Alvaro Retana)
(Deborah Brungard)
(Martin Duke)
(Martin Vigoureux)
(Robert Wilton)
Note: This ballot was opened for revision 15 and is now closed.
Erik Kline
No Objection
Murray Kucherawy
No Objection
Comment
(2020-09-29 for -15)
Sent
There are several places in the document where "header" should be changed to "header field". In Section 2.1, I think this could be a bit clearer: OLD: The following already registered SetError would mean: NEW: In this context, the existing SetError values defined in [reference] are interpreted as follows: In Sections 2.1 and 2.2: This is totally a personal nit, and you're free to ignore me, but since I keep tripping on it I'll mention it: In various places, "id" is used as a word rather than an initialism, as in "The id of the account to use." I keep reading this as the English term from psychoanalysis rather than a truncation of "identifier". I'd probably be happier if the full word was used. Also, in the first bullet of Section 2, it's capitalized as "Id"; we should probably be consistent. In Section 3: a) s/guaranty/guarantee/ (multiple instances) b) There's an extension in Section 3.1 starting with "X-" that should probably be revisited given BCP 178.
Roman Danyliw
No Objection
Comment
(2020-10-05 for -15)
Sent
A few minor comments: ** Section 2. Per “This property MUST NOT be null for "MDN/send", but may be null in the response from the "MDN/parse" method”, should a normative MAY be used here instead (or would that conflict with RFC8098) ** Section 2. The guidance to reference RFC8098 for further details is helpful. In addition to the guidance on case sensitivity, I would have also would have benefit from a bit of prose on how to convert the fields names between this document and RFC8098.
Warren Kumari
No Objection
Éric Vyncke
No Objection
Comment
(2020-09-29 for -15)
Sent
Thank you for the work put into this document. It is clear and easy to read. Please find below a couple of non-blocking COMMENT points. I hope that this helps to improve the document, Regards, -éric -- Section 2 -- While I can guess what is meant by "foreign (non-Internet) message", a more formal description would probably be welcome. -- Section 2.1 -- Wondering whether the values in this section are case sensitive? Section 2 clearly specifies that the fields must be lowercase. Is it useful to specify whether case is important in this section?
Barry Leiba Former IESG member
Yes
Yes
(for -15)
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
(for -15)
Not sent
Alvaro Retana Former IESG member
No Objection
No Objection
(for -15)
Not sent
Benjamin Kaduk Former IESG member
(was Discuss)
No Objection
No Objection
(2020-12-31 for -16)
Sent for earlier
Thank you for addressing my Discuss (and Comment) points!
Deborah Brungard Former IESG member
No Objection
No Objection
(for -15)
Not sent
Martin Duke Former IESG member
No Objection
No Objection
(for -15)
Not sent
Martin Vigoureux Former IESG member
No Objection
No Objection
(for -15)
Not sent
Robert Wilton Former IESG member
No Objection
No Objection
(for -15)
Not sent