Re: [IPsec] diet-esp - How do you know?
Paul Wouters <paul.wouters@aiven.io> Tue, 24 May 2022 15:13 UTC
Return-Path: <paul.wouters@aiven.io>
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 B5F56C185B3F for <ipsec@ietfa.amsl.com>; Tue, 24 May 2022 08:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=aiven.io
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 QT96xW87zUdg for <ipsec@ietfa.amsl.com>; Tue, 24 May 2022 08:13:49 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 30BB2C185B3A for <ipsec@ietf.org>; Tue, 24 May 2022 08:13:49 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id v8so29427609lfd.8 for <ipsec@ietf.org>; Tue, 24 May 2022 08:13:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aiven.io; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rpHKnWqphg5MhHArw/vZ244+QOHMO7ihHjnBHmQVsqk=; b=FhTsoXqqYCqe5+7ikAlNmw8mLU8T5mcacpI5c3h+7ACKI15Ob3lcO+lrKtXbYpWVlR 6159JLKe5epGlTueOF+Nx4fpNDAMP7DM9Aq6yGrbT1hdNenUmxChzYKIsxp6nwr8FHMZ wpmaFcneTOtsZNH8f2KK3b82crPAqnB5M4XVo=
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=rpHKnWqphg5MhHArw/vZ244+QOHMO7ihHjnBHmQVsqk=; b=pC3nd2dkfsAW9XHb+VvJ64onvhCSHJso/kO3b8j6ry2DSXEWNblsPl0WbkqPrpMVy1 bzRqT/WDFlm25XbgJR/2FfE7rgxNLRYgp4vxXB1zvFBjVZof225h9M7GnLFMy5JhBhHj 18CYRkIjSpepN6Gcijqka5gVnuBooiCbzNzVDHxvdrocmmq0oKtUHEALHzZOf067xBwq pZ7qEl1RSnDLDPp7jlsPF3KDmb17PmVhRZydgBeFPGrcd1XmluY7yET4zKi53aZrehc1 yiVc5euiAHk8do+h4pbB3TC7LFPH3XlfECvBZ/siSyk6as9uekR4lbPGGrcALyX6n+mF aJ1w==
X-Gm-Message-State: AOAM530Q4U1f0LwDcPA8wlVq0KPb5VUYZuEIh1Ql8S5FwJ7lo6YxZBkT Tt0/1K+RsGMURk0OF727qOhW4zmKkstZbWZXOew4+tPhbsKkww==
X-Google-Smtp-Source: ABdhPJwdzwyAE9dsEtBytV4oESs/gJ8o15ZIP1UsSp2OvVxCUpdUiXUEiKNeIQ6p9oE/xK3D2FgT56h1NJQ9ptzv4RE=
X-Received: by 2002:a05:6512:400e:b0:450:e09d:c9a6 with SMTP id br14-20020a056512400e00b00450e09dc9a6mr21101920lfb.243.1653405227130; Tue, 24 May 2022 08:13:47 -0700 (PDT)
MIME-Version: 1.0
References: <245277bb-6d70-dbcd-b99e-badc435b9c4d@htt-consult.com>
In-Reply-To: <245277bb-6d70-dbcd-b99e-badc435b9c4d@htt-consult.com>
From: Paul Wouters <paul.wouters@aiven.io>
Date: Tue, 24 May 2022 11:13:36 -0400
Message-ID: <CAGL5yWa=hjCZD912YJPWM-x_=ChTo=yULk1P5FRfkfB9Db9+Gg@mail.gmail.com>
To: Robert Moskowitz <rgm-sec@htt-consult.com>
Cc: IPsecME WG <ipsec@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003bceff05dfc367ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/csKmBx-vmtg1exheIrVioOFY8e8>
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 15:13:52 -0000
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] diet-esp - How do you know? Robert Moskowitz
- Re: [IPsec] diet-esp - How do you know? Paul Wouters
- Re: [IPsec] diet-esp - How do you know? Scott Fluhrer (sfluhrer)
- Re: [IPsec] diet-esp - How do you know? Robert Moskowitz
- Re: [IPsec] diet-esp - How do you know? Daniel Migault
- Re: [IPsec] diet-esp - How do you know? Robert Moskowitz
- Re: [IPsec] diet-esp - How do you know? Daniel Migault
- Re: [IPsec] diet-esp - How do you know? Daniel Migault
- Re: [IPsec] diet-esp - How do you know? Scott Fluhrer (sfluhrer)
- Re: [IPsec] diet-esp - How do you know? Robert Moskowitz
- Re: [IPsec] diet-esp - How do you know? Daniel Migault
- Re: [IPsec] diet-esp - How do you know? Daniel Migault
- Re: [IPsec] diet-esp - How do you know? Robert Moskowitz
- Re: [IPsec] diet-esp - How do you know? Daniel Migault