Hiya, Sorry for being slow getting this done. My AD review of this is below. Please consider my comments as last call comments. I have requested last call for this one so you should see the announcement of that shortly.
- section 3, first list, bullet 1: what's option (c) there mean? wasn't clear to me. - typo: "an email server certificates" - section 3, 2nd list, bullet 3 - is that MUST NOT really needed? if URIs are not used, might it be better to be silent? (In case someone does figure out a use?) - section 3, 2nd list, bullet 4 - afaik, CN is what is mostly actually used. Shouldn't we recognise that reality with more than a MAY? It's been more than a decade since PKI folks started to want to not use CN and that's just not worked. (Or am I wrong and CAs/MUAs are finally seeing CN not used?) - section 4, bullets 1&2 - do we have any evidence that these MUSTs will be honoured? If not, or if we have eveidence that they will be ignored, then is it really a good idea to include such RFC6919-isms? (A change here would also percolate to sections 3 and 5 I guess.) - I think the answer is "no," but I'll ask anyway:-) Many mail service providers use names like mail.example.com, smtp.example.com, imap.example.com etc. Would it be useful for this document to encourge the use of specific hostname parts for specific functions? (Hostname part is probably the wron term, I mean the smtp, imap, mail parts of those names) Cheers, S. _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
