IETF Logo Mail Archive

[IPsec] Re: Comments on draft-pwouters-ipsecme-delete-info

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 30 July 2024 18:40 UTC

Return-Path: <mcr+ietf@sandelman.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 A9CBDC151531 for <ipsec@ietfa.amsl.com>; Tue, 30 Jul 2024 11:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_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 (2048-bit key) header.d=sandelman.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 EJku-aZ72G-t for <ipsec@ietfa.amsl.com>; Tue, 30 Jul 2024 11:40:10 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63ECAC15152D for <ipsec@ietf.org>; Tue, 30 Jul 2024 11:40:10 -0700 (PDT)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.a=rsa-sha256 header.s=dyas header.b=gclxdpjl; dkim-atps=neutral
Received: from dyas.sandelman.ca (unknown [142.169.16.22]) by relay.sandelman.ca (Postfix) with ESMTPS id 89D4C1F483; Tue, 30 Jul 2024 18:38:57 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 6C91EA1DA8; Tue, 30 Jul 2024 11:39:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1722364766; bh=IOuzuC0tD2gWgvak3YP/IQyjQ6UdTChFpfy/eK6M1e4=; h=From:To:Subject:In-reply-to:References:Date:From; b=gclxdpjlii/fSBnC+VUgr1TsHclu9+5kH5uo6ZSqBjzw18f8OfzIXQgn39anCG3WD Y1ILwEq3PA+pULtQ9xe4Agnj65u9F50823NDxuYEQrGZOlQpgjkcZNzPwxdmciLwoS cucZE91R82k2zpiQLJ30XhUaAdW/HprtZyN3PPGkI2wmGY4oNmGyUV+W/KYLz+QEdz csyZzvDpxr83ha5ODYo1zHA/e39GN1S3WQx36IeopXKvXFPVEGjWs/J8I33DPKn4ot EPcV68yWctG1UoAUUx2Um2cTUa4K1SZ40b++rPItuO6StIukkbJJZVwOFUhC/Vy2WS LJTUe0wpvgWQA==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 6934AA13E8; Tue, 30 Jul 2024 11:39:26 -0700 (PDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Valery Smyslov <smyslov.ietf@gmail.com>, ipsec@ietf.org
In-reply-to: <020701dae1b9$b6741070$235c3150$@gmail.com>
References: <020701dae1b9$b6741070$235c3150$@gmail.com>
Comments: In-reply-to "Valery Smyslov" <smyslov.ietf@gmail.com> message dated "Mon, 29 Jul 2024 16:17:49 +0300."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 30 Jul 2024 11:39:26 -0700
Message-ID: <337427.1722364766@dyas>
Message-ID-Hash: SBKAPDJWGTGAAJC7423DIEAQO2S4RHWT
X-Message-ID-Hash: SBKAPDJWGTGAAJC7423DIEAQO2S4RHWT
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipsec.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPsec] Re: Comments on draft-pwouters-ipsecme-delete-info
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/sdl_eLJ3dQVAAwYkepn8-4O9dN0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Owner: <mailto:ipsec-owner@ietf.org>
List-Post: <mailto:ipsec@ietf.org>
List-Subscribe: <mailto:ipsec-join@ietf.org>
List-Unsubscribe: <mailto:ipsec-leave@ietf.org>

Valery Smyslov <smyslov.ietf@gmail.com> wrote:
    > 2. The list of reasons looks to me both incomplete and excessive at the same
    > time.

If we are going to rely on the enum alone, then it needs to cover all sorts
of cases that might be specific to some implementations, while other
implementations would have a more general code.

So I expect it to be "excessive", but it being incomplete is certainly a
problem.

OTH, an enum that is more generic with text in UTF-8[well: precis!], that
expounds upon the problem is also very useful.  I am not concerned about
attacks in this way.

I'm more concerned that a VPN gets turned off, and the traffic goes in the
clear because nobody can debug it.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.27.6 | Report a Bug | By Email | System Status