Re: [Perc] Roman Danyliw's No Objection on draft-ietf-perc-dtls-tunnel-09: (with COMMENT)

"Paul E. Jones" <paulej@packetizer.com> Thu, 05 August 2021 22:05 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEDF03A0C7E; Thu, 5 Aug 2021 15:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJOWPRanpHAO; Thu, 5 Aug 2021 15:04:57 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [IPv6:2600:1f18:24d6:2e01:e842:9b2b:72a2:d2c6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 387BF3A0C57; Thu, 5 Aug 2021 15:04:57 -0700 (PDT)
Received: from authuser (localhost [127.0.0.1])
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1628201087; bh=vk3bjR8/V4MCyd/s5l3rxHIuyZfyODws0Y/ABRtgahQ=; h=From:To:Subject:Cc:Date:In-Reply-To:References:Reply-To; b=hUJN7A0q3qu61En4evp36/dwgDddDGiEz+bYn/DWYK/zP9012w88GcSnh10ltIyDL UXKXGO+HghQIfB6Wba7guqJVhkv2TZm0cYa5j293CZjYyNDEjFZnfPF7hPNT8I3hVg cOz5YyR4+zal0zFXn7XPCiMVaOZRY/EQEiAODgj0=
From: "Paul E. Jones" <paulej@packetizer.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: draft-ietf-perc-dtls-tunnel@ietf.org, perc-chairs@ietf.org, perc@ietf.org, suhasietf@gmail.com, suhasietf@gmail.com
Date: Thu, 05 Aug 2021 22:04:41 +0000
Message-Id: <em1355a9d1-73d6-4860-ab07-7118cc26c60e@sydney>
In-Reply-To: <162508387766.24113.5015964775533185016@ietfa.amsl.com>
References: <162508387766.24113.5015964775533185016@ietfa.amsl.com>
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
User-Agent: eM_Client/8.2.1473.0
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/fgsjTP-wUZCWvCBAQVpJLNOBzYo>
Subject: Re: [Perc] Roman Danyliw's No Objection on draft-ietf-perc-dtls-tunnel-09: (with COMMENT)
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Aug 2021 22:05:02 -0000

Roman,

>Thank you to Shawn Emery for the SECDIR review, and to Russ Housley for the
>security related feedback in the GENART review.
>
>** Section 5.4.
>    The Key Distributor MUST match the certificate fingerprint and
>    "external_session_id" received from endpoint's "ClientHello" message
>    with the values received from the SDP transmitted by the endpoint.
>
>Consider adding a reference to RFC8122 to point to the guidance on the SDP
>fingerprint attribute.

Will add.


>** On the topic of relying on the RFC8122 defined hashes, Section 5 allows for
>the possibility of SHA-1 which is now past its prime.  The text there already
>says “Implementations compliant with this specification MUST NOT use the MD2
>and MD5 hash functions to calculate fingerprints or to verify received
>fingerprints that have been calculated using them.”  Likewise, Section 5.1 also
>notes the requirement of at least one of the hashes being SHA-256.  Consider
>saying sometime along the lines of “Implementations using this tunneling
>approach SHOULD NOT use SHA-1 hash functions to calculate or verify
>fingerprints …”

While you're correct that SHA-1 is aging, I would prefer that this 
document not overrule RFC 8122.   Maybe we should update 8122? The 
reality is, though, SHA-1 is still used.  It's also still widely used in 
SRTP deployments.

Paul