Re: [Coin] New Version Notification for draft-kutscher-coinrg-dir-00.txt

"Dirk Kutscher" <ietf@dkutscher.net> Mon, 04 November 2019 20:57 UTC

Return-Path: <ietf@dkutscher.net>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC391200F1 for <coin@ietfa.amsl.com>; Mon, 4 Nov 2019 12:57:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id horWhYg_iv6B for <coin@ietfa.amsl.com>; Mon, 4 Nov 2019 12:57:43 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C32F12080A for <coin@irtf.org>; Mon, 4 Nov 2019 12:57:42 -0800 (PST)
Received: from [192.168.1.69] ([77.21.26.148]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.183]) with ESMTPSA (Nemesis) id 1My3Ef-1hjOBr2Q6J-00zZoE; Mon, 04 Nov 2019 21:57:28 +0100
From: "Dirk Kutscher" <ietf@dkutscher.net>
To: philip.eardley@bt.com
Cc: coin@irtf.org
Date: Mon, 04 Nov 2019 21:57:27 +0100
X-Mailer: MailMate (1.13r5655)
Message-ID: <9165BA65-3C22-4CD3-88F2-FC6DBB1F9047@dkutscher.net>
In-Reply-To: <LNXP123MB2587A19F746F7C7D7E2B66DCEB7F0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <156261491289.1109.5401492860957076575.idtracker@ietfa.amsl.com> <9917EB2E-0D0B-4F91-B667-9A1046769AC5@dkutscher.net> <LNXP123MB2587A19F746F7C7D7E2B66DCEB7F0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:Rucb3XKOfUggn70el6hyGgzJwh7al6yHErYsHPCUWOGlRGqXEm1 aWQqK+7YG/7AHb0B3CDgqCvwSE+RhQQmpNr4EjTcyqRx/5Z4gnmzxbMKnuQcX1WawTrGJfR dl2MpFi3BYcAG03n64u6Z5NnFQn6WRZP1B48kEnwkVFsR4YmO02mW2JiHCLSmpxSOQN/qDc nmrLAzjIuv0Xk1E5VP2Wg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:s6pHNdtzLt4=:1UxsI29iSUWlvxJgg5Se5r bjJfxLSx9fXYRWQqCnosHKYO4kCVIYha5P5GbbRMkDIivyLaJHRkwaEA5X7vsOQ9GGXm4jj06 IxZvPxnsnTTG37Lj5xccjnlp+NJNGxLFPX1Iji08dS/b2Tbm7OpznmXjOVUSogsCfRX/hhL1j 8Dw+qyT5oAO2XwHxq4xd3XvAgl+yLsiWaiVN+3HxX6k4Avt9GW9ZiGk8rLaM4KJJETvhQKPsy +bqts7s1Jm/rY1yoPBg5Vw5RqfX3XgaBQCwXoH8+X4Yr9d+q28sW9HfIRTagOysbZOlE4Ur5G Xv8N6A+rMes7oTTK1A81BFvGPZMkQ7S+S64jtGKzbKjIWEO0V97nhzd4PQ9efoMDxIotlMplZ cfmgZ+/Ct2/PD0Yjf/L+E3aUPTQeDi1e5HEA7jRZw00MZmrcV5a27u4FSU1PqNT0BUK9IF4vz N3xtFjDt/7c0c/7krYdqna/4LAwf2hu75vCHzkqpyb25y53O9VC4UoSe71XRa6jF46l+bl5Kp os2DAm4mlPzQhuYr8PkAuttdlOLrq5uoWAHAk0A6SMJFvZSF0A58I14f/aZf+FshTGrmBOf/T 4Ku63Sn8jGBOuscERVNn7FFttVyEQzt7YbU1VOuWmE79llCPpWgOknk7YgtO+miiXNSRQQsSE pKh7EJrUurvGT1YmTY8UQaVLoWdOegvxKHMWgYnuN54w/F1UwgCg4s6erVmp0MnE4uqjQvxCW DjZe1ibht3K4Gzx9qxpcu3UwWc9M29TvOanLPOnYntDNwCVGAlho3L9bUloQz+aTJA0MVAx2c gUHIYex+rwplc9oMtXpVnmbj8AexoyahD8So7ZKByi4+ElPvZZ81KbyDMOl8TvNo88kDksGS2 pX3hp/PKImQ5zpXKTdRquxiA0Z/2V6r2CNW0EPgzE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/R9ybynhvBZYE4yY3EnpanTYTDe4>
Subject: Re: [Coin] New Version Notification for draft-kutscher-coinrg-dir-00.txt
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2019 20:57:51 -0000

Thanks, Phil,

That was just in time.

We have just submitted an update that reflects some of your points (see 
other message).

Of course, there is more to be discussed — let’s do that on the list 
and in Singapore.

Thanks,
Dirk





On 4 Nov 2019, at 18:44, philip.eardley@bt.com wrote:

> Dirk, Teemu, Jörg,
>
> I've now got to reading your draft. Thanks - I agree with most of it 
> and think it's useful.
>
> Somewhere in Section 3 - perhaps you could explain the differences 
> from MEC & slicing (I think I know what they are, but may be a 
> question some readers ask themselves)
>
> In S3 / 3.3, I thought it could be clearer where you stop talking 
> about existing systems (which << might intuitively be characterized as 
> "computing in the network">>) and start talking about COIN.
>
> S3.4 - I agree, as you hint, that we should be interested in moving 
> beyond lambda functions to sets of (micro-) functions that are chained 
> /meshed, functions that instantiate other functions etc
>
> << The underlying architectural question is whether the goal is to 
> enable the network to perform computations on the data passing through 
> it, or whether the goal is to enable distributed computational 
> processes to be built in the network.>>
> Am I allowed to say I want both?!
>
> Re heterogenous platforms. I hope COIN will allow different platforms 
> (physical & virtualisation technologies) to be integrated in the COIN.
>
> S4 - I agree that the joint resource optimisation problem (across 
> compute & networking resources) is an interesting research problem and 
> (I believe) could give great gains.
>
> S4.2 - strictly stateless vs stateful. I don’t think we should 
> assume only strictly stateless functions.
> << keep state over a series of function invocations>> I think we will 
> have a series of micro-functions, which I think implies some state. 
> I'm undecided about whether we should aim to keep state over a series 
> of invocations of the same function (but probably, Yes)
>
> S4.5 another security aspect of this could be how to be sure the 
> function does what it claims it will do.
>
> S4.6 - I like the idea of re-starting a function as a way of handling 
> failure (or at least as a possible method). Need to avoid significant 
> virtualisation (& networking) overheads from enforcing extreme quality 
> of service when many users may not need it.
>
> It might be good to illustrate some of the points further through an 
> example? - perhaps based round the one in your ICN-19 paper (analysis 
> of coughing to see which passengers are ill)
>
> Thanks!
> Best wishes,
> phil
>
> -----Original Message-----
> From: Coin <coin-bounces@irtf.org> On Behalf Of Dirk Kutscher
> Sent: 08 July 2019 20:47
> To: coin@irtf.org
> Subject: [Coin] Fwd: New Version Notification for 
> draft-kutscher-coinrg-dir-00.txt
>
> Hello,
>
> We have written up some ideas on COIN Research Directions -- hope you 
> find that useful.
>
> Naturally, we’d be interested in feedback — either on the list or 
> at the meeting in Montreal.
>
> Best regards,
>
> Dirk, Teemu, Jörg
>
>
> Forwarded message:
>
>> From: internet-drafts@ietf.org
>> To: Joerg Ott <jo@in.tum.de>de>, Teemu Karkkainen <kaerkkae@in.tum.de>de>,
>> Teemu Kaerkkaeinen <kaerkkae@in.tum.de>de>, Dirk Kutscher
>> <ietf@dkutscher.net>
>> Subject: New Version Notification for 
>> draft-kutscher-coinrg-dir-00.txt
>> Date: Mon, 08 Jul 2019 12:41:52 -0700
>>
>> A new version of I-D, draft-kutscher-coinrg-dir-00.txt has been
>> successfully submitted by Dirk Kutscher and posted to the IETF
>> repository.
>>
>> Name:		draft-kutscher-coinrg-dir
>> Revision:	00
>> Title:		Directions for Computing in the Network
>> Document date:	2019-07-08
>> Group:		Individual Submission
>> Pages:		17
>> URL:
>> https://www.ietf.org/internet-drafts/draft-kutscher-coinrg-dir-00.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-kutscher-coinrg-dir/
>> Htmlized:
>> https://tools.ietf.org/html/draft-kutscher-coinrg-dir-00
>> Htmlized:
>> https://datatracker.ietf.org/doc/html/draft-kutscher-coinrg-dir
>>
>>
>> Abstract:
>>    In-network computing can be conceived in many different ways - 
>> from
>>    active networking, data plane programmability, running virtualized
>>    functions, service chaining, to distributed computing.
>>
>>    This memo proposes a particular direction for Computing in the
>>    Networking (COIN) research and lists suggested research 
>> challenges.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission until the htmlized version and diff are available at
>> tools.ietf.org.
>>
>> The IETF Secretariat
>
> --
> Coin mailing list
> Coin@irtf.org
> https://www.irtf.org/mailman/listinfo/coin