[Hipsec] Need to amend rfc7402 to match IPSECME BEET work
Robert Moskowitz <rgm@htt-consult.com> Thu, 24 July 2025 13:55 UTC
Return-Path: <rgm@htt-consult.com>
X-Original-To: hipsec@mail2.ietf.org
Delivered-To: hipsec@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id EC7ED4A5FA84 for <hipsec@mail2.ietf.org>; Thu, 24 Jul 2025 06:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=htt-consult.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTORuiZ9lama for <hipsec@mail2.ietf.org>; Thu, 24 Jul 2025 06:55:58 -0700 (PDT)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [23.123.122.149]) (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 mail2.ietf.org (Postfix) with ESMTPS id 5BD8A4A5FA21 for <hipsec@ietf.org>; Thu, 24 Jul 2025 06:55:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=htt-consult.com; s=mail; t=1753365355; bh=MvsZQwvAnGAzBfnyiqFxBKmR5w00wv8hK7ufZXNrTY0=; h=Date:To:From:Subject:From; b=FMvztBTljf9IKiL3ozEfE9dfGGiQ/F2mtX8Uk0S9rGaP8kASYzn4DwSsbGB5hNWLw pekCJyvjl0pvVB8y3knB1gGMf+pSps6iBkAzGCrFAtGEmHWn8gGusW3FQBsi5fNRFB 1Z8RtOxaWc1mfMYabL4/9VnJzoqqErd6WT3XqN5GfYxtd75D9Drr/DPFCRQlvmh75x Aumiwovm1dJH5Rab7tnUKdh5SJZZlSQQYCXB5241p6VOUeileL0u9An0Nn8FER3EAP PVZyYdcsiVJX2JLS9ezCgMxUwJYhkC3BBtT5tQXhEFdTCuwptXWRv3wUqcRlTsbqdn PqfGetxT7QMSQ==
Received: from authenticated-user (klovia.htt-consult.com [23.123.122.149]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by klovia.htt-consult.com (Postfix) with ESMTPSA id A61244A032C for <hipsec@ietf.org>; Thu, 24 Jul 2025 09:55:55 -0400 (EDT)
Message-ID: <0d1c88d1-fa32-45f6-a4c3-c81c86be415f@htt-consult.com>
Date: Thu, 24 Jul 2025 09:55:54 -0400
MIME-Version: 1.0
Content-Language: en-US
To: HIP <hipsec@ietf.org>
From: Robert Moskowitz <rgm@htt-consult.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: EIY5FB4Q63JZMUCF46OGNSOBEXU7QW5S
X-Message-ID-Hash: EIY5FB4Q63JZMUCF46OGNSOBEXU7QW5S
X-MailFrom: rgm@htt-consult.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-hipsec.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Hipsec] Need to amend rfc7402 to match IPSECME BEET work
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/EultJkAf4JcnMJHqkvxU1mY7FPk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Owner: <mailto:hipsec-owner@ietf.org>
List-Post: <mailto:hipsec@ietf.org>
List-Subscribe: <mailto:hipsec-join@ietf.org>
List-Unsubscribe: <mailto:hipsec-leave@ietf.org>
to all HIPsters: IPSECME is adding BEET mode directly into IKEv2: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-ikev2-beet-mode/ I have been asked to update 7402 Appendix B to align it to this BEET process. Perhaps fully pulling out App B and point a 7402-bis to this future RFC. Further study needed. I am looking for anyone interested in pitching in. This has actually been on my todo list for a year. :( Also per discussions last night during the IETF plenary, I want to contact Petri Jokela and Jan Melen to see their interest and inclusion as continuing as authors for this bis version. Given this SHOULD only be a BEET alignment with IKEv2 work, I planned on leaving them as authors for 7402-bis unless they ask otherwise. Also I need an xml for 7402 (5202-bis) and can't find one. Anyone have one? Bob
- [Hipsec] Need to amend rfc7402 to match IPSECME B… Robert Moskowitz