Re: [kitten] John Scudder's No Objection on draft-ietf-kitten-krb-spake-preauth-11: (with COMMENT)

Greg Hudson <ghudson@mit.edu> Thu, 18 January 2024 17:57 UTC

Return-Path: <ghudson@mit.edu>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A67E1C14F68A for <kitten@ietfa.amsl.com>; Thu, 18 Jan 2024 09:57:23 -0800 (PST)
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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 0vv6zBywUFz6 for <kitten@ietfa.amsl.com>; Thu, 18 Jan 2024 09:57:20 -0800 (PST)
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 F1B3CC14F6F2 for <kitten@ietf.org>; Thu, 18 Jan 2024 09:57:19 -0800 (PST)
Received: from [100.64.0.1] (pool-173-76-238-212.bstnma.fios.verizon.net [173.76.238.212]) (authenticated bits=0) (User authenticated as ghudson@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 40IHvB2b024669 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 18 Jan 2024 12:57:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1705600634; bh=34F8PHAaB7KtLFE/6QWHHpbjTR/+al+o5F9jJ+9pOs4=; h=Message-ID:Date:MIME-Version:Subject:From:Content-Type; b=ZpT362XFh5tvZIgWAfiCFjjDSmWety6bd8+Dw0vh5DTL2NqklhCmfp6BbF7ZO3LHv 8oFA9ToN9I/cWFhfS87xThVfszB5a2nvgBLU5uApDenXLkCAJ0SNdbRUznp9xTs5uk IGBnqXGWDCB1kABDuRzfHmrf12MChG40450Ir7HmbrSCofon/dSgpgVRcFLc+TFL97 ACADac/puQiSfpQzrh6E5Ry0nAc1PAgqYGeJGrfw0wSDzVbWzxheB1xUQh2+KjX6F+ XOReu/FN2qQ8qyNsCIYM1xFbKjFU6gymltrnDua+tZxqtEOHYtnVXIR7OAEs5zUS7q rNb3vhVxvuvaA==
Message-ID: <311870f4-e559-44ec-b864-d2e0de4959b6@mit.edu>
Date: Thu, 18 Jan 2024 12:57:11 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: John Scudder <jgs@juniper.net>, The IESG <iesg@ietf.org>
Cc: draft-ietf-kitten-krb-spake-preauth@ietf.org, kitten-chairs@ietf.org, kitten@ietf.org, Nicolas Williams <nico@cryptonector.com>
References: <170550971259.44795.14577927249974933402@ietfa.amsl.com>
From: Greg Hudson <ghudson@mit.edu>
In-Reply-To: <170550971259.44795.14577927249974933402@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/batAdLeCA0PBu5oAGecUAwe0bmg>
Subject: Re: [kitten] John Scudder's No Objection on draft-ietf-kitten-krb-spake-preauth-11: (with COMMENT)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2024 17:57:23 -0000

On 1/17/24 11:41, John Scudder via Datatracker wrote:
> - Section 4.3 ends with the line,
> 
>     KEY_USAGE_SPAKE  65
> 
>    I understand this to be, that you're providing the reader with the
>    IANA-assigned value. But without descriptive words around it, it's just
>    puzzling and lacking in context. I think you could safely delete the line,
>    since its information is included in Section 11 and in general it's
>    desirable, in my experience, to have only a single source of truth for this
>    kind of thing. Or otherwise, maybe you can work the information into the
>    prose more smoothly.

I will delete the line.

> - Although RFC 7322 section 4.8.6 provides shockingly little guidance about how
> to format your references, I still think you should try to do better than

I will copy the additional reference text from RFC 9032, yielding:

    [SPAKE]    Abdalla, M. and D. Pointcheval, "Simple Password-Based
               Encrypted Key Exchange Protocols", Cryptography-CT-RSA
               2005, Lecture Notes in Computer Science, Volume 3376,
               pages 191-208, Springer, DOI 10.1007/978-3-540-30574-3_14,
               February 2005,
               <https://doi.org/10.1007/978-3-540-30574-3_14>.

> - You might want to consider your usage of "man-in-the-middle" in light of
> https://www.ietf.org/about/groups/iesg/statements/on-inclusive-language/.

I will change this usage to "machine-in-the-middle".