IETF Logo Mail Archive

Re: [IPsec] ESP Signally to higher layers

Robert Moskowitz <rgm-sec@htt-consult.com> Mon, 23 May 2022 14:00 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 7A51AC15E41A for <ipsec@ietfa.amsl.com>; Mon, 23 May 2022 07:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.755
X-Spam-Level:
X-Spam-Status: No, score=-3.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 G5lSl-4xqw-M for <ipsec@ietfa.amsl.com>; Mon, 23 May 2022 07:00:44 -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 E1A29C15E419 for <ipsec@ietf.org>; Mon, 23 May 2022 07:00:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id EDB48625FC; Mon, 23 May 2022 09:59:55 -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 HT5CekFJrJGI; Mon, 23 May 2022 09:59:50 -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 0714F6247F; Mon, 23 May 2022 09:59:50 -0400 (EDT)
Message-ID: <33c6f561-4ab4-fb0e-a949-e441cad60557@htt-consult.com>
Date: Mon, 23 May 2022 10:00:33 -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
To: Christian Hopps <chopps@chopps.org>
Cc: IPsecME WG <ipsec@ietf.org>
References: <76129f8a-9287-e19d-ec32-5c743a7afdf2@htt-consult.com> <m24k1jn2nb.fsf@ja.int.chopps.org>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
In-Reply-To: <m24k1jn2nb.fsf@ja.int.chopps.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/Jq4W_REuEccucahvkysoYc22NFI>
Subject: Re: [IPsec] ESP Signally to higher layers
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 14:00:48 -0000

Thanks Chris.

Helps a bit.

On 5/20/22 20:27, Christian Hopps wrote:
>
> Robert Moskowitz <rgm-sec@htt-consult.com> writes:
>
>> This is an item that goes back to the beginning of ESP work:
>>
>> Minimally, how does the higher level 'learn' that it is secure:
>>
>> E2E or TE2TE?
>>
>> Encrypted/Authenticated/CrCed...  ?
>>
>> And as ESP has a seq#, how might it be convied to the higher layer?
>>
>> Case in point:  MAVlink has a 1-byte seq# in its payload.  How might 
>> this be
>> provided by ESP?
>>
>> https://mavlink.io/en/guide/message_signing.html
>>
>> So I have been thinking about this vis-a-vis diet-esp.  What is the
>> mechanism/trigger that can best work across a number of higher layers 
>> to inform
>> of operating environment and values available (seq#)?
>>
>> Is this done anywhere now?
>
> If you're asking for a generic API mechanism in unix, for datagrams it 
> would be recvmsg. Recvmsg uses a msghdr which can include control data 
> (cmsghdr). That is the way that lower layer information associated 
> with packets is passed up to the application.
>
> man recvmsg
> man cmsg
>
> I don't know if any ESP data is currently passed with this method though.
>
> Thanks,
> Chris.
>
>
>
>>
>> Bob
>>
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/ipsec
>
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec

v2.23.0 | Report a Bug | By Email