IETF Logo Mail Archive

Re: [IPsec] Fwd: New Version Notification for draft-colitti-ipsecme-esp-ping-01.txt

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 28 March 2024 00:24 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 9F7B2C151710 for <ipsec@ietfa.amsl.com>; Wed, 27 Mar 2024 17:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, 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 Bhg5L2jzbf47 for <ipsec@ietfa.amsl.com>; Wed, 27 Mar 2024 17:24:44 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D10BAC15152D for <ipsec@ietf.org>; Wed, 27 Mar 2024 17:24:43 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [111.65.71.87]) by relay.sandelman.ca (Postfix) with ESMTPS id 94FB7201C6; Thu, 28 Mar 2024 00:24:40 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="Uwiohk50"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 7B46BA191D; Thu, 28 Mar 2024 11:13:30 +1100 (AEDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1711584810; bh=X3vyNFYINpExAsIz7CPI73zZiskGqWL+d748BF+GQ0g=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=Uwiohk50hYBJvLTDnkzMqmkFvGYalXaLBtwxyOkL+nXQye/LL6M2qmY1NHqr96zey Ru8DAo3Z2UWGuDwbBAUPN+2nKecGxC6PDFr+K11Ao8mJ8LAfjwN9mhA5DsqIrO7K62 FtEZ7y+bmQwI45ZYFKZcqgJpagkP4MEIR1U9FkeLLA/AN+hqjlxvkMEPJPqdafT272 ysyZ/IloMkBesXLdVyjLKIoBZXsamO8iOcArESTw7L6bjgGW7O/2hc9NpWEGw2jb+q 8QKA2B69PawSs+z+RBEn4tk0cEJ6PHF+gvJkafWSw0KYk7pQd26A2JqeqmM42R9p5r QTReK8FtyY92Q==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 78B4EA191C; Thu, 28 Mar 2024 11:13:30 +1100 (AEDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Paul Wouters <paul@nohats.ca>
cc: "Panwei (William)" <william.panwei=40huawei.com@dmarc.ietf.org>, "ipsec@ietf.org" <ipsec@ietf.org>
In-reply-to: <343238de-93c9-ed85-2c9d-2d783e3a38ca@nohats.ca>
References: <170922023791.21652.13338059706655424526@ietfa.amsl.com> <CAFU7BAQuNkHDRidjQqGbXySKJ1FCRKuAksDa0BHsvfGeG45k6g@mail.gmail.com> <4b44a218c77a49edbaecd3b524dbaac7@huawei.com> <476994.1711501928@dyas> <3f7b0380650a40e6b9cec4afb7f6d034@huawei.com> <497306.1711523247@dyas> <57bd1510e66b45c7af60513fbba3051c@huawei.com> <343238de-93c9-ed85-2c9d-2d783e3a38ca@nohats.ca>
Comments: In-reply-to Paul Wouters <paul@nohats.ca> message dated "Wed, 27 Mar 2024 08:27:36 -0400."
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: Thu, 28 Mar 2024 11:13:30 +1100
Message-ID: <536308.1711584810@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/hxgGVU9e6EsNqYdDg15QSNnHriI>
Subject: Re: [IPsec] Fwd: New Version Notification for draft-colitti-ipsecme-esp-ping-01.txt
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, 28 Mar 2024 00:24:48 -0000

Paul Wouters <paul@nohats.ca> wrote:
    >> If you want to do the traceroute to determine how far ESP actually
    >> gets, you need to make sure every node supports the ESPping.

    > I think people meant to extend traceroute to use an ESP packet instead
    > of an ICMP or UDP packet. The machines in the middle do not need any
    > special support because any packet that hits TTL=0 should solicite
    > an ICMP response.

That's right, and we yeah, we can do that immediately.
Perhaps obviously: The responding server needs to implement this protocol in
order to get a reply though.

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

v2.23.0 | Report a Bug | By Email