Re: [Jmap] Working group last call: draft-ietf-jmap-mdn-03

[cketti <[e-mail]>]

          Capability

>
>       1.3. Addition to the capabilities object
>
>
>
>    The capabilities object is returned as part of the standard JMAP
>    Session object; see the JMAP spec.  Servers supporting _this_
>    specification MUST add a property called "urn:ietf:params:jmap:mdn"
>    to the capabilities object.

This could be more explicit and require the value to be an empty object,
like it is for e.g. "urn:ietf:params:jmap:vacationresponse".

But I think the capability should also be added to the
"accountCapabilities" property of all accounts that support "MDN/set". I
assume in most deployment scenarios this will only be the case for
accounts that also have the "urn:ietf:params:jmap:submission" capability.
The availability of "MDN/parse" can then be tied to the capability being
present in "capabilities". The availability of "MDN/set" to the
capability being present in "accountCapabilities" of the specific account.

Text suggestion:

> Capabilities are announced as part of the standard JMAP Session
> resource; see [@!RFC8620], section 2.
>
> Support for the "MDN" data type and the "MDN/parse" method are
> represented by the capability "urn:ietf:params:jmap:mdn" being present
> in the "capabilities" property.
> The capability "urn:ietf:params:jmap:mdn" being present in the
> "accountCapabilities" property of an account represents support for
> creating and sending MDN messages via the "MDN/set" method.
> Servers that include the capability in one or more
> "accountCapabilities" properties MUST also include the property in the
> "capabilities" property.
>
> The value of this "urn:ietf:params:jmap:mdn" property is an empty
> object in both the JMAP session "capabilities" property and an
> account's "accountCapabilities" property.


          MDN/set and Email object modifications

"EmailSubmission/set" can also modify referenced "Email" objects. RFC
8621 requires the method to include an "Email/set" response with the
changes. It seems like a good idea to copy this mechanism for "MDN/set".

Text suggestion (mostly copied from RFC 8621):

> After all items in the "MDN/set" invocation have been processed, a
> single implicit "Email/set" call MUST be made to set the "$MDNSent"
> keyword on "Email" objects referenced by "MDN" objects that have been
> successfully created. The response to this MUST be returned after the
> "MDN/set" response.


          Minor issues

>    o  *forEmailId*: "String" Email Id of the received email this MDN is
>       relative to.

Expanding on the comment from Neil, the type should be "Id|null".


>    The Email/parse method takes the following arguments:
>
>    o  *accountId*: "String" The id of the account to use.

This should be "MDN/parse method" and the type for "accountId" should be
"Id".

Best,
cketti