Re: New draft about In-network Computing Solution
Hesham ElBakoury <helbakoury@gmail.com> Thu, 27 April 2023 14:44 UTC
Return-Path: <helbakoury@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 404C1C151701; Thu, 27 Apr 2023 07:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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=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 FOgizFsSHIR3; Thu, 27 Apr 2023 07:44:34 -0700 (PDT)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (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 A6134C14CE22; Thu, 27 Apr 2023 07:44:34 -0700 (PDT)
Received: by mail-pj1-x1035.google.com with SMTP id 98e67ed59e1d1-2472a3bfd23so5893198a91.3; Thu, 27 Apr 2023 07:44:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682606673; x=1685198673; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1HTct3UL9rMol3dGo/OALPp9FLUPCX4WgR8NQjIJKdg=; b=aP01GKVF1m3njhazkJaTkfrfUAoEhBsD6ui7IZZTcBxuXlmXQk6sWG+i4uMc9UKiE9 S5ga5w4gsa16RerNS2n/bg/U2M/kP8vje+mF1hSIeBmJPYggYs574Q6bsuhaGPjXJ7UL IA/pVqGDgH8+WJ0US3gU3oeAaGpCg5TPuV666Nky6rW5XJ0SKkVM3PDsgqrloAf/x/bA lKKsVrmdh9BcIadv4T0DqouVxxA1jVzXTqJYSm7QxG4vkWREE8adJZH5iG8yn96s+1+1 f3vx1XXOSLo0rpKXFrs1Xj8uKfmcGixdkY2DfzX5dCWJ5hDcV4Z0oox/BKopfwIAvBEo kYVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682606673; x=1685198673; 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=1HTct3UL9rMol3dGo/OALPp9FLUPCX4WgR8NQjIJKdg=; b=KQo96nbnq/o9Ojc8g94j8+nh+wLZcaYid8LmG2TiVnIdyKA3xWVuUW9thQnPcbK2vU sDikCF1q/YZq9T/d7850KIClnWcmg2y8kTEBPmv4/PmRf9unIKvcyAvT2yeE8xO5Uq3P 8QL38KW5AWSwiykozF1AHM1+8CsCAEUvnC72/oc5B2k0VMi1vzWdR5wfZdCQ7XTBta99 r2v7aUzw0hst73nqSSdGfCaYgjckw7yYOnjvvTfxqmVSvikmQnJaY+Te76TMLsjgRH/Q kKOJiuMMfcBvGr9Wb4cpnlbQHFSY3vi3T50OTQU233GK16dAoMNBvPL0fx8NiCVmDN4N JdUQ==
X-Gm-Message-State: AC+VfDzC/jhH9Eh/AM1XmAJsEtYouRyOVALTviMgf6GHjfpgUxs3t1xq yIW11QjgdsRlP+nmydvevTTAHLXvvZazZrmUoLo=
X-Google-Smtp-Source: ACHHUZ6m8pq4ZaOgt5SKi5fOnRWA7D7Jjpo8sBVJ4lOf8idOsipW5WcyD42wo9tv+qj2GFWErISci0yK3sNGO6C1XPE=
X-Received: by 2002:a17:90a:eace:b0:23f:e4b7:afb3 with SMTP id ev14-20020a17090aeace00b0023fe4b7afb3mr2057408pjb.9.1682606673372; Thu, 27 Apr 2023 07:44:33 -0700 (PDT)
MIME-Version: 1.0
References: <d2a29216ccd24a95be543d89aca9c3a0@huawei.com>
In-Reply-To: <d2a29216ccd24a95be543d89aca9c3a0@huawei.com>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Thu, 27 Apr 2023 07:44:21 -0700
Message-ID: <CAFvDQ9otFHJyLGHSiSxBm+qQcjfCSAtRGYVEtmiRuaxn5OREcA@mail.gmail.com>
Subject: Re: New draft about In-network Computing Solution
To: Zhe Lou <zhe.lou=40huawei.com@dmarc.ietf.org>
Cc: 姚柯翰 <yaokehan@chinamobile.com>, rtgwg@ietf.org, sfc@ietf.org, Stefano Salsano <stefano.salsano@uniroma2.it>
Content-Type: multipart/alternative; boundary="0000000000001032db05fa52652b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/YmPboInZTavLiwoqPil0U9nAdrs>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2023 14:44:38 -0000
I worked with professor Stefano on Extensible In-band Processing (EIP) which uses a field in the packet to contain data and operations to be performed by the network devices on this data. Data can be provided by the user or collected using in-band telemetry or other means. EIP can be used to support the use cases in your draft and others such as distributed in-band machine learning, semantic routing, detnet, .... etc. More info on EIP including a draft which describes EIP structure is available in this page: https://eip-home.github.io/eip/ Thanks Hesham On Thu, Apr 27, 2023, 6:36 AM Zhe Lou <zhe.lou=40huawei.com@dmarc.ietf.org> wrote: > Dear Kehan, > > > > Many thanks for your comments. I apologize for this late response, as I > took a couple of weeks’ vacation. Please see my comments inline. > > > > Regards > > David > > > > *From:* 姚柯翰 <yaokehan@chinamobile.com> > *Sent:* Wednesday, 12 April 2023 06:16 > *To:* Zhangcuimin <zhangcuimin@huawei.com>; Luigi IANNONE < > luigi.iannone@huawei.com>; zhouyujing (A) <zhouyujing3@huawei.com>; Zhe > Lou <zhe.lou@huawei.com>; yangjinze <yangjinze@huawei.com> > *Cc:* rtgwg@ietf.org; sfc@ietf.org > *Subject:* Re:[sfc] New draft about In-network Computing > Solution(draft-zhou-sfc-sinc) > > > > Dear authors, > > > > It's an interesting idea to consider about routing packets to specific > network nodes for computation offloading. After reading the draft, I have > the following comments: > > > > 1. In-network computing(INC) is closely coupled with applications. > It's about implementing application-specific functions inside commercial > network devices. In section 5, the draft says "In the SINC domain, a host > MUST be SINC-aware. It defines the data operation to be executed.", I agree > with the first sentence, but I think it might not be the case that data > operation should be defined by applications, instead, I think these generic > computing operations should be pre-defined by network and be open to > applications through specific APIs. > > [DL] I think we are talking about 2 things, data calculation/operation > requested by the application, and data operation capabilities offered by > the network node. In the draft, we refer to the former. We do agree that > the later is also important, as we briefly mentioned it in the “control > plane requirements” section. > > To realize successful computation, apart from the definition of computing > operations, other related terms should be defined as well, like data types, > data structures and calculation precision, etc. Since the capabilities of > network devices provided by different vendors varies a lot, only > tranferring computing operations might not be sufficient to perform a > successful computation. If these definition can be done by network and > encapsulated through common APIs which could be open to applications, and > It's more friendly for App developers. > > [DL] The same as above, the application tell the network what it wants and > the network tells the application what it can. > > 2. The control plane requirements in section 8 are a little bit too > general, even though specific control plane design is not in the scope of > this draft. For example, in bullet one, what kind of resources in > switches/routers should be awared? In bullet two, what kind of constraints > should be based on for the selection of proper switches/routers to perform > INC? These requirements should be more clear, and it might influence the > control plane design. > > [DL] These are good points. We are going to update the section according > to the comments from you and Jeff (from the IETF 116 meeting). If you have > suggestions, we may work together on this part. > > 3. The computing operations defined in Appendix A are somewhat > atomic, and it feels like these operations are not enough for > switches/routers to perform successful task offloading. IMHO, as I > mentioned in comment 1, INC primitives should be presented through > encapsulated APIs that network can open to applications. This might be more > realistic. > > [DL] According to the discussion in IETF 116, the appendix A will be > removed. > > > > Welcome more discussions and I'm very happy to contribute if needed. > > > > Best, > > Kehan > > > > > > > > ----邮件原文---- > 发件人:"zhouyujing \\(A\\)" <zhouyujing3=40huawei.com@dmarc.ietf.org> > 收件人:"rtgwg@ietf.org" <rtgwg@ietf.org>,"sfc@ietf.org" <sfc@ietf.org> > 抄 送: Zhe Lou <zhe.lou@huawei.com> > 发送时间:2022-10-28 16:36:57 > 主题: > [sfc] New draft about In-network Computing Solution(draft-zhou-sfc-sinc) > > Hi all, > > We submitted a new draft about In-Network Computing ( > https://datatracker.ietf.org/doc/draft-zhou-sfc-sinc/ > ). In this draft, we want to discuss a mechanism "Signaling In-Network Computing operations" (SINC) to enable in-packet operation signaling for in-network computing for specific scenarios. > > Hope to get your review and comments. > > Many thanks! > > Best, > Yujing Zhou > > -----Original Message----- > From: internet-drafts@ietf.org <internet-drafts@ietf.org> > Sent: 2022年10月24日 9:56 > To: Zhangcuimin <zhangcuimin@huawei.com>; Luigi IANNONE < > luigi.iannone@huawei.com>; zhouyujing (A) <zhouyujing3@huawei.com > >; Zhangcuimin <zhangcuimin@huawei.com>; Zhe Lou <zhe.lou@huawei.com> > Subject: New Version Notification for draft-zhou-sfc-sinc-00.txt > > > > A new version of I-D, draft-zhou-sfc-sinc-00.txt has been successfully submitted by Yujing Zhou and posted to the IETF repository. > > Name: draft-zhou-sfc-sinc > Revision: 00 > Title: Signaling In-Network Computing operations (SINC) > Document date: 2022-10-23 > Group: Individual Submission > Pages: 19 > URL: https://www.ietf.org/archive/id/draft-zhou-sfc-sinc-00.txt > Status: https://datatracker.ietf.org/doc/draft-zhou-sfc-sinc/ > Html: > https://www.ietf.org/archive/id/draft-zhou-sfc-sinc-00.html > Htmlized: https://datatracker.ietf.org/doc/html/draft-zhou-sfc-sinc > > > Abstract: > This memo introduces "Signaling In-Network Computing operations" > (SINC), a mechanism to enable in-packet operation signaling for in- > network computing for specific scenarios like NetReduce, > NetDistributedLock, NetSequencer, etc. In particular, this solution > allows to flexibly communicate computation parameters to be used in > conjunction with the packets' payload, to signal to in-network SINC- > enabled devices the computing operations to be performed. > > > > > > The IETF Secretariat > > > > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg > > Subject: > [sfc] New draft about In-network Computing Solution(draft-zhou-sfc-sinc) > > Hi all, > > We submitted a new draft about In-Network Computing ( > https://datatracker.ietf.org/doc/draft-zhou-sfc-sinc/ > ). In this draft, we want to discuss a mechanism "Signaling In-Network Computing operations" (SINC) to enable in-packet operation signaling for in-network computing for specific scenarios. > > Hope to get your review and comments. > > Many thanks! > > Best, > Yujing Zhou > > -----Original Message----- > From: internet-drafts@ietf.org <internet-drafts@ietf.org> > Sent: 2022年10月24日 9:56 > To: Zhangcuimin <zhangcuimin@huawei.com>; Luigi IANNONE < > luigi.iannone@huawei.com>; zhouyujing (A) <zhouyujing3@huawei.com > >; Zhangcuimin <zhangcuimin@huawei.com>; Zhe Lou <zhe.lou@huawei.com> > Subject: New Version Notification for draft-zhou-sfc-sinc-00.txt > > > > A new version of I-D, draft-zhou-sfc-sinc-00.txt has been successfully submitted by Yujing Zhou and posted to the IETF repository. > > Name: draft-zhou-sfc-sinc > Revision: 00 > Title: Signaling In-Network Computing operations (SINC) > Document date: 2022-10-23 > Group: Individual Submission > Pages: 19 > URL: https://www.ietf.org/archive/id/draft-zhou-sfc-sinc-00.txt > Status: https://datatracker.ietf.org/doc/draft-zhou-sfc-sinc/ > Html: > https://www.ietf.org/archive/id/draft-zhou-sfc-sinc-00.html > Htmlized: https://datatracker.ietf.org/doc/html/draft-zhou-sfc-sinc > > > Abstract: > This memo introduces "Signaling In-Network Computing operations" > (SINC), a mechanism to enable in-packet operation signaling for in- > network computing for specific scenarios like NetReduce, > NetDistributedLock, NetSequencer, etc. In particular, this solution > allows to flexibly communicate computation parameters to be used in > conjunction with the packets' payload, to signal to in-network SINC- > enabled devices the computing operations to be performed. > > > > > > The IETF Secretariat > > > > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg >
- RE: New draft about In-network Computing Solution Zhe Lou
- Re: New draft about In-network Computing Solution Hesham ElBakoury