Re: [IPsec] IPsecME WG Adoption call for draft-pwouters-ipsecme-multi-sa-performance
Daniel Migault <mglt.ietf@gmail.com> Wed, 23 November 2022 14:32 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 5FEEBC14F735 for <ipsec@ietfa.amsl.com>; Wed, 23 Nov 2022 06:32:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 ZX_7t9JEjAjh for <ipsec@ietfa.amsl.com>; Wed, 23 Nov 2022 06:32:41 -0800 (PST)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (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 02012C14F74E for <ipsec@ietf.org>; Wed, 23 Nov 2022 06:32:40 -0800 (PST)
Received: by mail-oi1-x235.google.com with SMTP id r76so19152103oie.13 for <ipsec@ietf.org>; Wed, 23 Nov 2022 06:32:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iFp1GOUyJ+M7rCPtYzhB5mGL2e0oMnKSrwyoCg8hmKQ=; b=TQuQQTPQMIBStoJtjE7fWRUR4Gw92yWcQz4ow0wQElgYe23pJsLxnZnSbu6rgH/l7G C1NAW2wAhe9FAE5wc/+AX+Fs5Rp10UBa7conLMjQ3oWKf2kLibvQpFzFQ1GhjxBvvXlw 6PO8krWQS1T99XGIG+wNObnjFJvNXP3BasaDNa42wIy0qktAA4wW2sSIQZn+cvQklUy7 5fh7C61yfxlPqA0l95CS13nG8K4IQYu6xDJEtX6PWeEK5J1N6yCxv1zQAX6zXL7gxY6S hFzVK3IfldBw1eTfKVS7cW/RC6rXEvvDYEJH5POcjAkZ8Gmb5lltIqHpDiIYKJIXbjtp /YJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iFp1GOUyJ+M7rCPtYzhB5mGL2e0oMnKSrwyoCg8hmKQ=; b=G3SBNgTZiZs3bm3b3a+Cx/Pg9W+icL5zENaOC+3VYExCE/RjIuf9OnJDSNrclj1TMx 4V6C6Do5ggGwFCNHfhXt75iZRPX4BSpGkvC/xBO/RgAGqLTejL7nbkQ1JlivJv944A89 tYdK3BcFjg0Tm5uhFJVs8G/OA+LMO3GO2Ylq8O8mBXStrO9mfACasgIy+NAWf2w3Is5h glEM6q5nCTTJAF7UclZ2PYGLbs5WrVmksUgkoGlXEXjdqsfTDl7EhJ41zjjhP9T+yU38 AFOHrCtOjzlfgzkwhTfIb7n+QqQgs4IAWrXRLKmZ3lBrYKyeefw/ZDq/KCV8V3DAhQS6 VKnw==
X-Gm-Message-State: ANoB5pmZwdiLvgNu5kLg69H2/vgNwyIFYuIrPMWQmrofNDnp3Z5uSGcc c3WYgMAJRnierhcprMaCGDkqWhDFmmr6+uIvkfY=
X-Google-Smtp-Source: AA0mqf4jlvaKuxFmdY4rLpvRSWm6V6vtjoEIzF6DxiEB8JmOlpu4Vh/TVX6e3mDUCgfUesDuMaNjwuYefVCSQMbB8dM=
X-Received: by 2002:a05:6808:1592:b0:35a:93eb:faf4 with SMTP id t18-20020a056808159200b0035a93ebfaf4mr3982895oiw.185.1669213959671; Wed, 23 Nov 2022 06:32:39 -0800 (PST)
MIME-Version: 1.0
References: <25451.58560.690380.833165@fireball.acr.fi> <0fa86a3b220940f2abdd310ec9b829f2@huawei.com> <CADZyTkk6tuUgTZuivJNkj20tOqJreVu+hRFfuL=3w1wFqikcPQ@mail.gmail.com> <20221123063631.GI424616@gauss3.secunet.de>
In-Reply-To: <20221123063631.GI424616@gauss3.secunet.de>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Wed, 23 Nov 2022 09:32:28 -0500
Message-ID: <CADZyTkkac3r48rk0VmfGHyADZjD6xivGKe27mqyxNU=yY_k8Nw@mail.gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: "Panwei (William)" <william.panwei=40huawei.com@dmarc.ietf.org>, Tero Kivinen <kivinen@iki.fi>, "ipsec@ietf.org" <ipsec@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001ed52605ee2429f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/UwbDsL-EzaaawM40JIU0_URnXVY>
Subject: Re: [IPsec] IPsecME WG Adoption call for draft-pwouters-ipsecme-multi-sa-performance
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 23 Nov 2022 14:32:45 -0000
Hi Steffen, I think I mostly agree with you. Please see inline, Yours, Daniel On Wed, Nov 23, 2022 at 1:36 AM Steffen Klassert < steffen.klassert@secunet.com> wrote: > On Tue, Nov 22, 2022 at 04:58:55PM -0500, Daniel Migault wrote: > > This draft is missing an important part which is the actual negotiation > > of the multiple SAs. A peer willing to set these multiple SAs will have > to > > negotiate them anyway. Some implementations can > > handle parallel CREATE_CHILD_SA others cannot and the negotiation of > > multiple SAs might take a very long time, at least a time that is not > > acceptable to high performance tunnels. Since these child SAs need to be > > created, the one willing to the multiple SAs can simply start and stop > when > > the responder says stop. In terms of IKEv2 the gains are minimal. The > > document may add a mechanism similar to address that: > > https://datatracker.ietf.org/doc/draft-mglt-ipsecme-multiple-child-sa/ > > I'm one of the authors of the above mentioned draft and the draft > we are discussing here. > > Speaking as an author of the above mentioned draft: > > This draft was a first attempt so solve the multi cpu SA case. > The mechanism to install all child SAs once that was used there > was seen as as too complex, given that the number of cpus are > not too high. So it should be possible to either create > separate parallel child SAs, or creating them on demand when > traffic pops up an a certain cpu. > The draft we discuss here takes this into account and > reduces the complexity to a minimum. I agree but in my opinion the draft has some scalability limitation and to be useful needs to be combined with something else - at least this is my understanding. Maybe I am biased as the use case it may address is not the one we have. Do not get me wrong, I think the work has been useful and should be documented. But I think that the alternative that limits the number of SA is very attractive, especially for our hardware implementations with a limited number of SA. > > However, draft-ponchon-ipsecme-anti-replay-subspaces addresses all of > these > > issues nicely and provides a much more scalable solution. It basically > > makes -IMO - both -multiple-child-sa and -multi-sa-performance obsolete. > > I disagree here. The multi-sa-performance draft just adds two IKE > notifications, so no achitectural changes. This is the 'low hanging > fruit', it can be done independent of any changes to ESP. > > The anti-replay-subspaces draft does architectural changes to ESP, > this needs more work. > > I agree that the advantage of the draft is that it is a very ow hanging fruit but on the other hand - at least as I see it - -ponchon-ipsecme-anti-replay-subspaces provides a complete solution to the scalability concern we have. > > My suggestion is that -multi-sa-performance is being moved to > experimental > > and almost shipped as it is so the work being achieved is documented. > This > > has been some interesting work, but today, I would like the group to > spend > > more cycles on draft-ponchon-ipsecme-anti-replay-subspaces that I > consider > > more promising. > > I already proposed to work on a ESP-v4 version, and this draft should > definitely be considered there. But the discussion about ESP-v4 should > be open, and not focused on this particular proposal. > > I agree ESP-v4 should be considered natively, but I would like -ponchon-ipsecme-anti-replay-subspaces to be implemented with the current ESP mostly so we do not wait ESP-v4 to have it. Actually at Ericsson we would like to implement the standard version of -ponchon-ipsecme-anti-replay-subspaces in a reasonable delay -- i.e. next year. To clarify my position I am not opposed to the adoption of the draft. My position is that it gets published as soon as possible as an experiment that paves the way for a more complete solution. In other words, I think we should not have the document being discussed for years in the WG. -- Daniel Migault Ericsson
- [IPsec] IPsecME WG Adoption call for draft-pwoute… Tero Kivinen
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Valery Smyslov
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Pierre Pfister (ppfister)
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Paul Wouters
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Michael Richardson
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Christian Hopps
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Panwei (William)
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Daniel Migault
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Steffen Klassert
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Daniel Migault
- Re: [IPsec] IPsecME WG Adoption call for draft-pw… Paul Wouters