http://www.ietf.org/internet-drafts/draft-santesson-tls-ume-04.txt says: This document does not specify how the server stores the user_principal_name, or how exactly it might be used to locate a certificate. For instance, it might be appropriate to do a case- insensitive lookup. It is RECOMMENDED that the server processes the user_principal_name with a stringprep profile [N7] appropriate for the identity in question, such as Nameprep [N8] for the portion domain portion of UPN, SASLprep [N9] for the user portion of the UPN and stringprep appendix B.3 [N7] as mapping table for case folding. Given that the first and second sentence make it clear that the use of StringPrep is not required, I suggest using MAY instead of RECOMMENDED in the third sentence. RECOMMENDED is the same as SHOULD according to RFC 2119, and is a fairly strong recommendation. Its use seem misplaced here. It may be better to avoid RFC 2119 language completely here, because the entire paragraph is merely an example of what you can do. Thanks, Simon The IESG <iesg-secretary@xxxxxxxx> writes: > The IESG has received a request from an individual submitter to consider the > following documents: > > - 'TLS User Mapping Extension' > <draft-santesson-tls-ume-04.txt> as a Proposed Standard > - 'TLS Handshake Message for Supplemental Data' > <draft-santesson-tls-supp-00.txt> as a Proposed Standard > > The previous Last Call on draft-santesson-tls-ume-03.txt has finished. > However, to resolve some comments that were received during the > previous Last Call, the document has been updated and > draft-santesson-tls-supp-00.txt was written. Due to the significant > changes in one area of the document, the IESG is making a second > call for comments. This comment period is shorter since the majority > of the document is unchanged. > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg@xxxxxxxx or ietf@xxxxxxxx mailing lists by 2006-04-11. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-santesson-tls-ume-04.txt > http://www.ietf.org/internet-drafts/draft-santesson-tls-supp-00.txt _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf