[TLS] Kathleen Moriarty's Yes on draft-ietf-tls-rfc4492bis-15: (with COMMENT)
Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com> Tue, 14 March 2017 20:40 UTC
Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: tls@ietf.org
Delivered-To: tls@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 42BD4129B08; Tue, 14 Mar 2017 13:40:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-tls-rfc4492bis@ietf.org, Sean Turner <sean@sn3rd.com>, tls-chairs@ietf.org, sean@sn3rd.com, tls@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148952402426.24274.4020884632180640309.idtracker@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 13:40:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/uDAEom5uwnVMJejHcvV8QF4QTrM>
Subject: [TLS] Kathleen Moriarty's Yes on draft-ietf-tls-rfc4492bis-15: (with COMMENT)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Mar 2017 20:40:24 -0000
Kathleen Moriarty has entered the following ballot position for draft-ietf-tls-rfc4492bis-15: Yes 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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-tls-rfc4492bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for your work on this draft. I just have one question: In section 5.10, I see the following text: The default hash function is SHA-1 [FIPS.180-2], and sha_size (see Section 5.4 and Section 5.8) is 20. However, an alternative hash function, such as one of the new SHA hash functions specified in FIPS 180-2 [FIPS.180-2], SHOULD be used instead. Why are you setting the default to SHA-1 and then recommending that something else should be used? Why not just start with a different SHA hash function as the default or at least for TLS 1.2? I do see the prior text about TLS 1.0 and 1.1 using MD5 and SHA-1, but most have recommended to go right to TLS 1.2 with the SSLv3 deprecation. As such, I'm not clear on why the SHA-1 default.
- [TLS] Kathleen Moriarty's Yes on draft-ietf-tls-r… Kathleen Moriarty
- Re: [TLS] Kathleen Moriarty's Yes on draft-ietf-t… Yoav Nir
- Re: [TLS] Kathleen Moriarty's Yes on draft-ietf-t… Martin Thomson
- Re: [TLS] Kathleen Moriarty's Yes on draft-ietf-t… Yoav Nir
- Re: [TLS] Kathleen Moriarty's Yes on draft-ietf-t… Martin Thomson
- Re: [TLS] Kathleen Moriarty's Yes on draft-ietf-t… kathleen.moriarty.ietf
- Re: [TLS] Kathleen Moriarty's Yes on draft-ietf-t… Sean Turner
- Re: [TLS] Kathleen Moriarty's Yes on draft-ietf-t… Yoav Nir