IETF Logo Mail Archive

Re: [IPsec] Paul Wouters' Yes on draft-ietf-ipsecme-ikev2-auth-announce-09: (with COMMENT)

Paul Wouters <paul@nohats.ca> Thu, 18 April 2024 13:42 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3B3CC14F68D; Thu, 18 Apr 2024 06:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.73
X-Spam-Level:
X-Spam-Status: No, score=-3.73 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_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 SIymiYr6NGBD; Thu, 18 Apr 2024 06:42:50 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (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 C4418C14F61D; Thu, 18 Apr 2024 06:42:49 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4VKzVZ2Wxfz5Bw; Thu, 18 Apr 2024 15:42:46 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1713447766; bh=qEjjtEL3jq02JrFyqRQRvtac/CmR64Ofl9QIbV84WUY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=VU9ixU17yZpV06GE2zsnUj+RYdRj6A70H4ws962PuaGzNWxzcjwlIUqF3/FD4Fr3q E68BwrNKbimo2VirSsN4Kc+MC9+6qSHnfi3WeNEBJ1HxkKO0a8Mdtb/4cS8xo67ZHU hjgoJVqkG0K8NxuCHRettuB1fvn3fkrfSu+ZrcT4=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id zojTrKPQyCft; Thu, 18 Apr 2024 15:42:45 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 18 Apr 2024 15:42:45 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 3A47711CB669; Thu, 18 Apr 2024 09:42:44 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 36D4511CB668; Thu, 18 Apr 2024 09:42:44 -0400 (EDT)
Date: Thu, 18 Apr 2024 09:42:44 -0400
From: Paul Wouters <paul@nohats.ca>
To: Valery Smyslov <svan@elvis.ru>
cc: 'Paul Wouters' <paul.wouters@aiven.io>, 'The IESG' <iesg@ietf.org>, draft-ietf-ipsecme-ikev2-auth-announce@ietf.org, ipsecme-chairs@ietf.org, ipsec@ietf.org, kivinen@iki.fi
In-Reply-To: <002501da9190$980e67d0$c82b3770$@elvis.ru>
Message-ID: <5ba416c1-e4b6-aee6-b5c6-2c57cbd56c58@nohats.ca>
References: <000c01da9167$b202adf0$160809d0$@elvis.ru> <CF1A94F8-CAC8-4906-81BF-58E2BFDF4F8A@nohats.ca> <002501da9190$980e67d0$c82b3770$@elvis.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/_TuJBCy4Y9cW0QRlJx9-j8TeuzM>
Subject: Re: [IPsec] Paul Wouters' Yes on draft-ietf-ipsecme-ikev2-auth-announce-09: (with COMMENT)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2024 13:42:54 -0000

On Thu, 18 Apr 2024, Valery Smyslov wrote:

> OK, then how about (Section 3):
>
> CURRENT:
>   The receiving party may take this
>   information into consideration when selecting an algorithm for its
>   authentication if several alternatives are available.
>
> NEW:
>   The receiving party may take this
>   information into consideration when selecting an algorithm for its
>   authentication (i.e., the algorithm used for calculation of the AUTH
>   payload) if several alternatives are available.
>
> Does this help?

That's great, thanks!

Paul

v2.23.0 | Report a Bug | By Email