Mahesh Jethanandani has entered the following ballot position for draft-ietf-tls-rfc8447bis-13: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8447bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- > D: Indicates that the item is discouraged. This marking could be > used to identify mechanisms that might result in problems if they > are used, such as a weak cryptographic algorithm or a mechanism > that might cause interoperability problems in deployment. When > marking a registry entry as “D”, either the References or the > Comments Column MUST include sufficient information to determine > why the marking has been applied. Implementers and users SHOULD > consult the linked references associated with the item to > determine the conditions under which the item SHOULD NOT or MUST > NOT be used. First of all thanks to Barry Leiba for his ARTART review. I had a follow-up comment to what he brought up and has to do with the last sentence of the above paragraph. The fact that the document says "SHOULD NOT or MUST NOT" and not just "MUST NOT" makes me think there might be conditions under which the item may be used. I would have therefore thought the linked reference might, in addition, describe under what circumstances an item marked D might be used. If there are none, why not just a "MUST NOT"? _______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
