Re: [IPsec] John Scudder's No Objection on draft-ietf-ipsecme-ikev2-intermediate-09: (with COMMENT)

Valery Smyslov <svan@elvis.ru> Thu, 03 March 2022 07:16 UTC

Return-Path: <svan@elvis.ru>
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 7AF3F3A13EB; Wed, 2 Mar 2022 23:16:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ZwVrrHr6N_1R; Wed, 2 Mar 2022 23:16:33 -0800 (PST)
Received: from dpmail.elvis.ru (dpmail.elvis.ru [93.188.44.211]) (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 23C983A13EA; Wed, 2 Mar 2022 23:16:31 -0800 (PST)
Received: from kmail.elvis.ru ([93.188.44.208]) by dpmail.elvis.ru with esmtp (Exim 4.89) (envelope-from <svan@elvis.ru>) id 1nPfhJ-0002ef-Fh; Thu, 03 Mar 2022 10:16:27 +0300
Received: from mail16.office.elvis.ru ([10.111.1.29] helo=mail.office.elvis.ru) by kmail.elvis.ru with esmtp (Exim 4.92) (envelope-from <svan@elvis.ru>) id 1nPfhJ-0008Lc-8k; Thu, 03 Mar 2022 10:16:25 +0300
Received: from MAIL16.office.elvis.ru (10.111.1.29) by MAIL16.office.elvis.ru (10.111.1.29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Thu, 3 Mar 2022 10:16:25 +0300
Received: from buildpc (10.111.10.33) by MAIL16.office.elvis.ru (10.111.1.29) with Microsoft SMTP Server id 15.1.1779.2 via Frontend Transport; Thu, 3 Mar 2022 10:16:25 +0300
From: Valery Smyslov <svan@elvis.ru>
To: 'John Scudder' <jgs@juniper.net>, 'The IESG' <iesg@ietf.org>
CC: draft-ietf-ipsecme-ikev2-intermediate@ietf.org, ipsecme-chairs@ietf.org, ipsec@ietf.org, ynir.ietf@gmail.com
References: <164626876794.28446.13200170927730672912@ietfa.amsl.com>
In-Reply-To: <164626876794.28446.13200170927730672912@ietfa.amsl.com>
Date: Thu, 03 Mar 2022 10:16:28 +0300
Message-ID: <052701d82ece$99e43480$cdac9d80$@elvis.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLqJHVru0D+KbGLi2Z0nP24Qyl/6qqJSlEw
Content-Language: ru
X-CrossPremisesHeadersFilteredBySendConnector: MAIL16.office.elvis.ru
X-OrganizationHeadersPreserved: MAIL16.office.elvis.ru
X-KLMS-AntiSpam-Interceptor-Info: not scanned
X-KLMS-Rule-ID: 1
X-KLMS-Message-Action: clean
X-KLMS-AntiSpam-Status: not scanned, disabled by settings
X-KLMS-AntiPhishing: Clean, bases: 2022/02/20 23:15:00
X-KLMS-AntiVirus: Kaspersky Security for Linux Mail Server, version 8.0.3.30, bases: 2022/02/20 20:13:00 #18795747
X-KLMS-AntiVirus-Status: Clean, skipped
X-Spam-Scanner: Rspamd work in dpmail.elvis.ru, WHITELIST
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/I_ovnoEE7IDlllbIc_qQbP4CfBs>
Subject: Re: [IPsec] John Scudder's No Objection on draft-ietf-ipsecme-ikev2-intermediate-09: (with COMMENT)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Mar 2022 07:16:36 -0000

Hi John,

> John Scudder has entered the following ballot position for
> draft-ietf-ipsecme-ikev2-intermediate-09: No Objection
> 
> 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/about/groups/iesg/statements/handling-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-intermediate/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for this. I have just a couple minor questions/suggestions.
> 
> 1. Section 3.2, “these exchanges MUST follow each other”. I suppose what is
> meant is, “these exchanges MUST be sequential” (this hardly seems to need to be
> mandated, but OK). Or is something else intended, in which case, what is it?

No, you got the point. If you think “these exchanges MUST be sequential”
is more natural English wording, I'll use it. As a non-native speaker 
I probably don't feel the difference...

> 2. In Section 3.4, there is:
> 
>    not all error notifications may ever appear in the IKE_INTERMEDIATE
>    exchange (for example, errors concerning authentication are generally
>    only applicable to the IKE_AUTH exchange).
> 
> I can’t make sense of what the word “ever” is doing there. It makes sense to me
> if I remove “ever” to make it “not all error notifications may appear”. It’s OK
> if I change “ever” to “even”. But I don’t get it, as written. Am I missing
> something, or would one of my edits be appropriate?

This is again an artefact of me being a non-native speaker.
By using this word I intended to stress that some error notifications
may _never_ appear in the IKE_INTERMEDIATE, but it's OK for me to drop this word.

Thank you!

Regards,
Valery.