IETF Logo Mail Archive

[IPsec] diet-esp - How do you know?

Robert Moskowitz <rgm-sec@htt-consult.com> Mon, 23 May 2022 01:20 UTC

Return-Path: <rgm-sec@htt-consult.com>
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 542B2C074AD5 for <ipsec@ietfa.amsl.com>; Sun, 22 May 2022 18:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 oJp-Kq2b59T6 for <ipsec@ietfa.amsl.com>; Sun, 22 May 2022 18:20:07 -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 621B5C074AD2 for <ipsec@ietf.org>; Sun, 22 May 2022 18:20:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 5322B62776 for <ipsec@ietf.org>; Sun, 22 May 2022 21:19:20 -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 ZBMTJqK1C4Ud for <ipsec@ietf.org>; Sun, 22 May 2022 21:19:18 -0400 (EDT)
Received: from [192.168.160.11] (unknown [192.168.160.11]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 853226247F for <ipsec@ietf.org>; Sun, 22 May 2022 21:19:17 -0400 (EDT)
Message-ID: <245277bb-6d70-dbcd-b99e-badc435b9c4d@htt-consult.com>
Date: Sun, 22 May 2022 21:19:59 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Content-Language: en-US
From: Robert Moskowitz <rgm-sec@htt-consult.com>
To: IPsecME WG <ipsec@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/2c3v-yF5k9lda8IEhxk_RPp9cg4>
Subject: [IPsec] diet-esp - How do you know?
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.34
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: Mon, 23 May 2022 01:20:08 -0000

I think there is something else I am missing here.

How does the receiving system 'know' that the packet is a diet-esp packet?

Protocol ID is ESP.  That is all we have.  Right after the IPv6 or IPv4 
header comes the ESP header, but is it a regular ESP header with a 
4-byte SPI or is it a dist-esp header with some other SPI size?

How is this done?

Is the source IP the 'key' that it is a diet-esp, and look at all the 
SAs associated with that source IP and hopefully find one that maps to 
at least the 1st byte or full 4 bytes?

What is the logic trigger?

And if it is the source IP, how might gateways and such mess things up.

Or am I back to needing a SCHC protocol ID to put in the Next Header 
field rather than ESP?

Confused here...

Bob

v2.23.0 | Report a Bug | By Email