Kirsty, Thank you for your thorough review. Quickly replying to a couple of your points and I will reply in more details in a separate email. > On 22 Sep 2021, at 18:00, Kirsty Paine via Datatracker <noreply@xxxxxxxx> wrote: [snip] > > Section 4: > • > The "string" values that are allowed for smimeStatus and smimeErrors do not > explicitly mention the allowable charsets (standard ART area guidance). In IETF > protocols, UTF-8 is preferred - see RFC 2277 (BCP 18), Sections 3.1 and 3.2. > Please reference this and make it explicit what characters are allowed. • > Similarly, this draft has protocol elements that contain human-readable text, > so you need to specify language tags for those fields, or justify why language > tagging is not needed. There is text that alludes to this in smimeErrors, > saying "in the language specified in the Content-Language header field, if any" > – but there's no language stipulation for others, e.g. smimeStatus where it > says "Servers MAY return other values not defined below." smimeStatus use tokens, not free form human readable text, so use of language tags is not appropriate for it. But I will check if this can be clarified. [snip] > Section 6 > • I'm not sure why > 10 minutes specifically is recommended – it seems to be landed there without > rationale and without conveying why it's not longer/shorter. It seemed like a reasonable default and making it configurable seemed like overkill (and a way to introduce unnecessary complexity into the protocol). To be honest the proposed default hasn’t been discussed in the WG, so if you have an alternative proposal, it would be great to hear. Best Regards, Alexey -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
