Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates
draft-ietf-acme-email-smime-14

[ section 2 ]

* Use the 8174 text?

[ section 6 ]

* I think it's fair to all-caps RECOMMENDED the use of DNSSEC.

I support Barry's DISCUSS, especially the bit that references DMARC.  

You might mention in Security Considerations that the DKIM and DMARC RFCs discuss their dependence on the DNS as well, and their respective vulnerabilities.

It seems to me that the second paragraph of Security Considerations says approximately the same thing that the (1) bullet does in the same section.

Thank you for the work put behind this document, it could indeed be really useful.

My only comment is support to Barry's point about the intended status of the document.

Regards

-éric

Thanks for discussing things with me and addressing my comments.  Version -12 takes care of all my comments except for the one in Section 2:  Please use the new BCP 14 boilerplate and add a normative reference to RFC 8174.

The changes from version -10 do introduce a few typos and nits, so I'll record them here; please consider fixing them, but there's no need to respond further.

— Section 1 —

   This document aims to support both:

I suggest saying what it does, rather than what it aims to do.  Also (nit), as the two numbered items are each multiple sentences, the intro is better worded thus:

NEW
   This document supports both of the following:
END

   Such MUA can present nice User	
   Interface to the user and automate certificate issuance.

Nits: there are articles missing, “user interface” doesn’t need capitalization, and “user interface to the user” is redundant:

NEW
   Such an MUA can present a nice
   interface to the user and automate certificate issuance.
END

In the second bullet, make it “An MUA”, as we pronounce it “em-yoo-ay”, not “moo-ah”.

— Section 3 —

   The process of issing an S/MIME certificate works as follows.

Typo: make it “issuing”.

— Section 3.1 —

   To aid in debugging (and in for some

Typo: change “in for” to “for”.

— Section 3.2 —
In bullet 7:

       The text/plain body part (whether or not it is
       inside multipart/alternative) MUST contain a block of lines
       starting with the line "-----BEGIN ACME RESPONSE-----", followed
       by one or more line containing the base64url-encoded SHA-256
       digest [FIPS180-4] of the key authorization, calculated from
       concatenated token-part1 (received over email) and token-part2
       (received over HTTPS), as outlined in the 5th bullet in
       Section 3.

You changed this from “3rd bullet” to the new “5th bullet”, but I don’t understand why: it’s still the third bullet that talks about how the content is formed.