Re: [Hipsec] Diet ESP and HIP

Robert Moskowitz <rgm@htt-consult.com> Mon, 21 August 2023 18:48 UTC

Return-Path: <rgm@htt-consult.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43237C15C509 for <hipsec@ietfa.amsl.com>; Mon, 21 Aug 2023 11:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.091, 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
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 QWLjpSIMdaX5 for <hipsec@ietfa.amsl.com>; Mon, 21 Aug 2023 11:48:27 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 82A0CC151548 for <hipsec@ietf.org>; Mon, 21 Aug 2023 11:48:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 567956250B; Mon, 21 Aug 2023 14:47:47 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id N4VSD7xBRUYQ; Mon, 21 Aug 2023 14:47:43 -0400 (EDT)
Received: from [192.168.160.29] (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 8D394623C1; Mon, 21 Aug 2023 14:47:39 -0400 (EDT)
Message-ID: <c19f45aa-6484-d192-da75-d87ea31a5b1b@htt-consult.com>
Date: Mon, 21 Aug 2023 14:48:16 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0
Content-Language: en-US
To: Stu Card <stu.card@axenterprize.com>, HIP <hipsec@ietf.org>
References: <ba2415e1-52f4-cce1-c545-ffdf03edf546@htt-consult.com> <MN2PR13MB4207FBF066371578375AA295F816A@MN2PR13MB4207.namprd13.prod.outlook.com>
From: Robert Moskowitz <rgm@htt-consult.com>
In-Reply-To: <MN2PR13MB4207FBF066371578375AA295F816A@MN2PR13MB4207.namprd13.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/PCEWMSlIrfEPmvBnPw20cmbPJfQ>
Subject: Re: [Hipsec] Diet ESP and HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Aug 2023 18:48:31 -0000

The question is more about taking advantage of diet-esp in HIP.

If so, then look at how IKE is handling it, work out how to do it in HIP 
and propose the methodology.  Then we write the draft.

Probably Independent stream, with the case that HIP is following 
developments in ESP to use over constrained links.


On 8/13/23 16:32, Stu Card wrote:
> Although I have long been intrigues by IKE and MobIKE, what I don't know about them would fill volumes.
>
> Any of you better-informed folk willing to essay this?
>
> -----Original Message-----
> From: Hipsec <hipsec-bounces@ietf.org> On Behalf Of Robert Moskowitz
> Sent: Thursday, July 27, 2023 2:30 PM
> To: HIP <hipsec@ietf.org>
> Subject: [Hipsec] Diet ESP and HIP
>
> Please note that in ipsecme there is work to apply SCHC to EXP:
>
> https://datatracker.ietf.org/doc/draft-mglt-ipsecme-diet-esp/
>
> This is a 32 byte savings.
>
> The additional interesting thing impacting HIP is that addition to IKEv2 to negotiate Diet-ESP:
>
> https://datatracker.ietf.org/doc/draft-mglt-ipsecme-ikev2-diet-esp-extension/
>
> Anyone interested in taking on defining the HIP payload to perform an equivalent operation?
>
> I am swamped with other items, and would love it if someone else steps up to the plate.
>
> Bob
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec