Re: [Coin] COIN activities update

[Marie-Jose Montpetit <[e-mail]>]

Since I was involved in some discussion with Xavier let me chime below.



Marie-José Montpetit, Ph.D.
[e-mail]



On October 28, 2020 at 10:58:36 PM, Xavier de Foy ([e-mail])
wrote:

Hi Laurent,

  Thank you for bringing up those questions.

On Wed, Oct 28, 2020 at 4:02 AM Ciavaglia, Laurent (Nokia -
FR/Paris-Saclay) <[e-mail]> wrote:

Hi Xavier, all,
>
>
>
> Apologies if my comments are out of scope as I'm not so up-to-date with
> the status of COIN technical work / terminology.
>
>
>
> I think the examples you gave makes sense and could be useful to clarify
> of how various operations/flows could work.
>

The original discussion related to what’s “mobile" in the mobile data
discovery and how does it relate to COIN. And since there is currently some
work on Computing in the Network as it relates to 5G the discussion evolved
from there I suppose hence the nomenclature used below.


>
>
> Two comments:
>
>    1. What strikes me when reading the text is the reference to "COIN
>    node" and "COIN network". Are these really necessary/useful terms
>
>

To give some context, a discussion on whether discovery is within the scope
of COIN was started in IETF 108 and never resolved. This email was an
attempt to move this forward. The scenarios were my interpretation of how
(data/resource/service) discovery would be used in the context of COIN.

I actually think that we could think of a COIN-enabled node that could be
discovered (mobile or not) but I agree that a "COIN network” is frankly
just a network unless we consider only those nodes that are associated with
computing capabilities and that a COIN network is established post
discovery with the goal of orchestration or capabilities sharing. Xavier:
is this what you had in mind?




> I mean, I could map the examples you describe (partially or fully) to
> different existing technologies/operations. I find that adding the "COIN
> stuff" may shift the focus away from the genuine technical problem to solve
> by giving a false impression that the "COIN xyz" are sketching a different
> case. Reading your examples without the COIN-related terms, the sentences
> are still very valid. So, I guess the technical problem/solution to address
> is situated at another level, i.e. what is not working as you expect it or
> what would like to enable (in a COIN-like framework) that would be (solved)
> differently. I think this should be the core/focus of the examples.
>
>
>

The distributed and local/edge nature of COIN nodes may be a specificity of
those scenarios (in conjunction with other factors like compute/storage
nature of resources, mobile/battery powered nodes in some cases, etc.) So
it's possible that centralized mechanisms are less efficient in this
context, for example. However this view is based on my current
understanding of COIN in charter and "direction" draft, so it may be off or
incomplete.

Can you expand? We are thinking of revisiting at least the Milestones and
that could be a valid input.




>
>    1. COIN being a RG, I would advise to carefully position the below
>    examples wrt. state of the art, and outline what/where the proposal is
>    proposing new (research) things. Again, on the examples, most, if not all
>    of the pieces/functions could be mapped to existing technologies/protocols.
>    Can we pinpoint more specifically the technical propositions of COIN in
>    these contexts?
>
>
  Agreed, these examples were adapted (for most of them) from what is
present in the existing drafts, they did not go into the technical
propositions (especially since I was not involved in the data discovery
drafts). Distributed discovery of a COIN network by mobile nodes could be
of interest (as opposed to centralized mechanisms for edge computing
service discovery for example). Also, I think the data discovery overview
draft points towards multiple specific technical propositions.

I think distributed discovery by any device may be needed as to ne recreate
bottlenecks that COIN was trying to help :) The question remains: how is
research going to help the discovery (and I would say orchestration) of
distributed computing capabilities (and associated storage for example)
across the core-edge. And feed into the use case drafts.

I saw there is a new version of the original discovery draft. How about the
others?


mjm (with a chair hat on and off)




> Please don't take my comments negatively, I'm just trying to get to the
> core of the issues here; and I think COIN has good potential to deliver
> compelling research.
>
>
>

  Not at all, thanks again for the comments.


> Best regards,
>
> Laurent
>
>
>
> *From:* Coin <[e-mail]> *On Behalf Of *Xavier de Foy
> *Sent:* Monday, October 26, 2020 20:05
> *To:* Marie-Jose Montpetit <[e-mail]>
> *Cc:* [e-mail]; [e-mail]
> *Subject:* Re: [Coin] COIN activities update
>
>
>
> Hi Marie-José, all,
>
>   On Wed, Sep 2, 2020 at 9:09 AM Marie-Jose Montpetit <
> [e-mail]> wrote:
> > And of course there is the discovery draft has also been going though a
> number of revisions
> https://datatracker.ietf.org/doc/draft-mcbride-edge-data-discovery-overview/
> :
> > which raised the discussion topic of “in-network” vs. “on-network” and
> we suppose the reach of computing in the network, a great discussion topic
> to prepare for our next meetings and milestone updates. There are now 3
> discovery draft and we welcome a discussion on maybe consolidating them.
>
>   Thanks for initiating the discussion. In the hope of contributing to it,
> here is a set of simplified discovery scenarios (at least as a starting
> point, please feel free to update it). I think drafts [1][2] cover
> scenarios (a) and (b), and [3] covers (d). A goal is to frame the discovery
> scenarios in the context of COIN.
>
>   The scenarios involve a "COIN network" (which, based my understanding of
> the charter, would be made of distributed/decentralized "COIN nodes"
> providing a computing service integrated with network/transport layers),
> and endpoints (non-COIN nodes, e.g. COIN network users or external data
> sources).
>
>   a. A COIN node discovers a data source (COIN node or endpoint), for the
> purpose of influencing COIN network operation (e.g. code placement, request
> routing, input for computation). Data discovery information may be further
> disseminated between COIN nodes. In a related scenario a COIN node
> discovers an external network function (e.g. SFC node), for the purpose of
> using the service, influencing request routing, and placing the code that
> uses the service.
>
>   b. A COIN node discovers computing/storage resources, for the purpose of
> creating/instantiating new COIN nodes.
>
>   c. A COIN node discovers another COIN node (that belongs to a different
> domain), for the purpose of interfacing 2 different COIN networks.
>
>   d. An endpoint or COIN node (which can be multihomed) discovers a COIN
> network entry point, for the purpose of connecting to it (e.g., as a user,
> or to join a COIN network). As a variant for wireless devices, mobile
> endpoints may need to determine which AP to attach to, in order to access a
> COIN network entry point.
>
>   To come back to the consolidation discussion, would the RG community be
> willing to work on a document covering all or some scenarios listed here?
>
>   Best Regards,
>
> Xavier.
>
> [1] draft-mcbride-edge-data-discovery-overview
> [2] draft-mcbride-data-discovery-problem-statement
> [3] draft-defoy-coinrg-mobile-discovery
>