Re: [secdir] [Uta] [Last-Call] Secdir telechat review of draft-ietf-uta-rfc7525bis-09

Benjamin Kaduk <kaduk@mit.edu> Thu, 14 July 2022 05:01 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA49C14CF12; Wed, 13 Jul 2022 22:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mit.edu
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5K-vu_Ts6Mjb; Wed, 13 Jul 2022 22:01:13 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 92B20C14F75F; Wed, 13 Jul 2022 22:01:11 -0700 (PDT)
Received: from kduck.mit.edu (c-73-169-244-254.hsd1.wa.comcast.net [73.169.244.254]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 26E50s8s025880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Jul 2022 01:01:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1657774864; bh=QxEpQrQFmt3kqSxfvhDKjwmRcYoi2vwFTyNwA+G38EU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=fnj2Vlcg06Mfb844Bn79YQPIsH1xrnoT6o09ixKCtmcvZRGpjwTCJW+WTxzm8J8G9 J0Kil7QBoSjZ5/vCCX90GBlpSfvtVSXQE+QaKcIKg4nJU04NZ3I/f5AEBBS6KlnZ3P mk0/iTkFcH1wmvTiSlZBWzKTGQw2sQHe7PqzBPEBhwUacAwKj3411AZxIR3n4HB3AG 87SY0mSbkD5DFUzBMSvg4pFap271QlFSAvdJR64vT0/WIyuZlupCeOAEL8gmIX0plp Jqbs4UlmPsPCBM7XzBx9lP2964rT8ho3H0I6D9k90rdGHcyqFyYhRnS7Ge4FA7DaWl xj6+MkwTvzlIA==
Date: Wed, 13 Jul 2022 22:00:53 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: Rob Sayre <sayrer@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>, "draft-ietf-uta-rfc7525bis.all@ietf.org" <draft-ietf-uta-rfc7525bis.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "uta@ietf.org" <uta@ietf.org>
Message-ID: <20220714050053.GT26442@kduck.mit.edu>
References: <165766858084.5251.12485129434316295805@ietfa.amsl.com> <b24e2934-200f-4f80-5261-aa2a977da39b@stpeter.im> <CAChr6Syq+uOTJsvqWuSustq_HdTaXCtDepyCuRWx+jGoEB06Fw@mail.gmail.com> <CAChr6SzkAmbjGK4XOwPkSwssLoG4NW1yG-6b2aFdFr43yF2zwQ@mail.gmail.com> <SY4PR01MB625186377F07976EFEF775F7EE889@SY4PR01MB6251.ausprd01.prod.outlook.com> <CAChr6Sy2GmkGQfz93+EhfDGEVZuwvkE9NOMwn6XVr5qag_aVBQ@mail.gmail.com> <SY4PR01MB6251FE9DFBD849A9296D31AEEE889@SY4PR01MB6251.ausprd01.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <SY4PR01MB6251FE9DFBD849A9296D31AEEE889@SY4PR01MB6251.ausprd01.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/OYV6W4EH52laYdLf0iMs1J4so0k>
Subject: Re: [secdir] [Uta] [Last-Call] Secdir telechat review of draft-ietf-uta-rfc7525bis-09
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jul 2022 05:01:13 -0000

Hi Peter,

On Thu, Jul 14, 2022 at 03:34:03AM +0000, Peter Gutmann wrote:
> Rob Sayre <sayrer@gmail.com> writes:
> 
> >I don't understand your rationale here, though.
> 
> If you've got existing systems with implemented, tested, and in-production TLS
> 1.2 stacks then the motivation to do a completely new TLS stack that does more
> or less the same thing as the old one but requires twice the code space (since
> it'll have to run alongside the old stack) and, usually, a truck roll to
> upgrade each system using it, is minimal if not zero.
> 
> Thus there are many systems that will probably stay with 1.2 more or less
> forever.

For what it's worth, this makes sense to me, and I don't know of any clear
technical reasons to say that doing this is a bad idea.

On the other hand, I can't even tell whether when Rob says "Just publish
it. It’s fine" if he's talking about raft-ietf-uta-rfc7525bis-09 as-is or
some hypothetical "MUST NOT use TLS 1.2" statement or something else.

-Ben