IETF Logo Mail Archive

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

Daniel Migault <mglt.ietf@gmail.com> Tue, 24 May 2022 20:23 UTC

Return-Path: <mglt.ietf@gmail.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 76ED4C20D66F for <ipsec@ietfa.amsl.com>; Tue, 24 May 2022 13:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 wGX3QU3sycV6 for <ipsec@ietfa.amsl.com>; Tue, 24 May 2022 13:23:17 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 ietfa.amsl.com (Postfix) with ESMTPS id D8F17C20D71D for <ipsec@ietf.org>; Tue, 24 May 2022 13:23:17 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id l13so26053204lfp.11 for <ipsec@ietf.org>; Tue, 24 May 2022 13:23:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BqUr0R5jCWBTEVAfCs+BW4DZDaWkFq38quJCYO6XdZ8=; b=WYUkV3y3+qoqiC4zJY936fNkccJHPKbtPLHQ1hHB2TV1knjHoYXyjoHefVaaF0pHfb IkBDnIyBwAW1G298stojSSfsyZ8NzbYQ6ara9I86hxkAQHKDt8vfPawFUSE2hLFQdNT9 tl7GFYY37ASZCIZdgkHbDTYn2ilYYsmWOUuOBGTeET6xPQZVNIBSmdAuegPRbnWHWPzw 5YGKA/vv+yvtoD9LihOSsHsmhjtKk9cAYIj1bD+1lW67Ea6s1KimfHp4bMfGZ/Ui16vx lEl5z4x3Kt8gB5RB2fOcSAiR6K+yyoBYdtOj0cOT/BiRBmlXSSaxkmpVdRTOxCkHkb4U H1Yw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BqUr0R5jCWBTEVAfCs+BW4DZDaWkFq38quJCYO6XdZ8=; b=oZg/K+ZeoSSlgvTtqgYXwbpTWp3YEIQxB/fgwUz6UPwX3NgQx0aVdCuy5oggCXfJPU YqhphEIrzIiflhOz4eEboHuKqRXpzilcBpbnRl+P0hEkah8EO5TfKpwt3Uj+jrLfD/fF T9GeoLATjXt3uVyL+Aa9lUC16Itojfai96cRh1fquL0Kg7cHMy8Pf/zH8mXqT46dLbD0 +xhiVYPLvnsuYJdKurHfK3nnEZlbLkP74EhGWy3JA0J4cWVJVRUag+tTCTnCMAoMT+bw zjodOsU89rFb8o651Os2PGLuoqA+iKt2ktsDPuRiLfDlxBUbvSMVlH+SUAFLY8/zA5M0 lKlA==
X-Gm-Message-State: AOAM531udxSq+f5819jvoox3UYrImDL/mMTi+n7OH4XngjKp8cZNsK1N kaRQgtNpS978/W+KpblHGhPn9W5ooGjQHyv+3Bc=
X-Google-Smtp-Source: ABdhPJzrscdQbv4L80Nqf6jxqbY00LWSkSrK9T44arPexonTTgcXQTiVD+YZ4xYGGnxDDkS6UabKHMngC0+DpvtxFfg=
X-Received: by 2002:a05:6512:55a:b0:478:54e1:efee with SMTP id h26-20020a056512055a00b0047854e1efeemr14770709lfl.448.1653423795580; Tue, 24 May 2022 13:23:15 -0700 (PDT)
MIME-Version: 1.0
References: <245277bb-6d70-dbcd-b99e-badc435b9c4d@htt-consult.com> <CAGL5yWa=hjCZD912YJPWM-x_=ChTo=yULk1P5FRfkfB9Db9+Gg@mail.gmail.com>
In-Reply-To: <CAGL5yWa=hjCZD912YJPWM-x_=ChTo=yULk1P5FRfkfB9Db9+Gg@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Tue, 24 May 2022 16:23:04 -0400
Message-ID: <CADZyTknARDjj=SZmstnBqxo5hJp-NzH09a6cH5Dxj3Zg7VfyAw@mail.gmail.com>
To: Paul Wouters <paul.wouters=40aiven.io@dmarc.ietf.org>
Cc: Robert Moskowitz <rgm-sec@htt-consult.com>, IPsecME WG <ipsec@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ffb91805dfc7b9d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/GVS2EEBhBR0I1YMC-7EhTytXsAc>
Subject: Re: [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: Tue, 24 May 2022 20:23:18 -0000

This is correct. IKEv2 is used both to agree on the use of Diet-ESP as well
as values to be used for the compression/decompression.

Yours,
Daniel

On Tue, May 24, 2022 at 11:14 AM Paul Wouters <paul.wouters=
40aiven.io@dmarc.ietf.org> wrote:

>
> On Sun, May 22, 2022 at 9:20 PM Robert Moskowitz <rgm-sec@htt-consult.com>
> wrote:
>
>> I think there is something else I am missing here.
>>
>> How does the receiving system 'know' that the packet is a diet-esp packet?
>>
>
>
> https://datatracker.ietf.org/doc/html/draft-mglt-ipsecme-ikev2-diet-esp-extension-02
>
> It's negotiated with IKEv2.
>
> I guess the IKE stack has to signal this to the ESP implementation on what
> to expect when
> the policy is installed ?
>
> Paul
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>


-- 
Daniel Migault
Ericsson

v2.23.0 | Report a Bug | By Email