Hi Ben,

My apologies for missing your email in March:

On 12/03/2020 20:42, Ben Schwartz wrote:
Section 3 says token-part1 "contains at least 64 bit of entropy", but Section 3.1 says token-part1 "MUST be at least 64 octet long after decoding".  Is this difference deliberate?

No, I obviously made a typo when saying octets. I will fix.

Also 64 octets of entropy is a _lot_.  RFC 8555 says "the token is required to contain at least 128 bits of entropy".

The draft seems to be oriented entirely toward use with e-mail clients that have a built-in ACME-S/MIME client.  I'm a bit disappointed that the draft doesn't accommodate users with "naive" email clients very well, e.g. by allowing customized subject lines.

Actually, I was trying to accommodate naive email clients, but it was a fine balance trying to specify minimal requirements.

Can you suggest some specific text to change and then we can discuss whether or not it should be done? My thinking about the Subject header field was that I wanted to have a unique subject (so that ACME email messages are easily findable). I also wanted to allow the token in the subject for APIs that can easily access Subject and not other header fields.

Best Regards,

Alexey

I assume this is deliberate, perhaps because of a desire to use short-TTL S/MIME certificates that would be impractical to provision manually, but the draft doesn't mention a rationale.

On Thu, Mar 12, 2020 at 2:52 PM Salz, Rich <[email protected] <mailto:[email protected]>> wrote:

    This mail begins a one-week working group last call on
    https://datatracker.ietf.org/doc/draft-ietf-acme-email-smime/?include_text=1

    If you have comments or issues, please post here.

    If anyone wants to be a document shepherd, please contact the chairs.

    /r$

    _______________________________________________
    Acme mailing list
    [email protected] <mailto:[email protected]>
    https://www.ietf.org/mailman/listinfo/acme


_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme

Reply via email to