Re: [Coin] Academic contributions in COIN

"Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia.com> Wed, 09 October 2019 07:29 UTC

Return-Path: <laurent.ciavaglia@nokia.com>
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 4BBB612008D; Wed, 9 Oct 2019 00:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 ngwmTrTbEMa6; Wed, 9 Oct 2019 00:28:59 -0700 (PDT)
Received: from FRA01-MR2-obe.outbound.protection.outlook.com (mail-eopbgr90139.outbound.protection.outlook.com [40.107.9.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AC47120074; Wed, 9 Oct 2019 00:28:58 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Yp+iOzEWhUuINnox01XhXUCzsQEOoVWJ2ufccpttd6qXMmAmB7IEeFpvw7BYZ1mGpcEp7hYcv2Xc2S2YC3b1+ZkTEOvFsHfqOK6ZJOLOXjFKJ6IeKFnvS60nwiXLCviETlS2MZCuTU2V2YEfLum8ra0cc+HGwjN3pSXS3Bi/AguGjSBX/0LJreQOnW3nablCQ1U1qJzLoPO10wD71sGcpvSHBgdj6wO/Q7jftRwk2PLYZ2IVbd3Eg410JsC5w7ueaa7ikCoDsIQmkrXPZNG8DH+BvdTrItNevMnbvOmVvV91tS/DtMHAhi3+WxNSp/aP8JfrK/Tm3zxP0NLr3mDxdA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=29HPIpnxEyWaQijPGfb9bCbcjH8kgl9NOmHafAyjGic=; b=he87dYJa1WYnW7Y353s4z2OmCp2n3v+HA41FC+70UqLCOhaxP/Jla6VHQ/i3keSyQP2BTWRCkUk/aO7Xre5YnZq83hUGCknT5iFAYFFD3F/BC36qChvVv6EloAJigvbzIx9gkBkwHKBsGhkdh0elUQoRj2m584Ay6Ug25ecaCkNV2bGGzBHS5SNahrJvwox7BQSodG/QGUxahmi6D3xEuB98572j17wP5EM17QO78Uilxw6GIztbOi7qt0qU83K3LMLZ1Xr438w9XBIL4QU6e166xHQVZZ9lSqMXzDb83AWrtCVWuqoSPwqKNJbfZpIQzvn4sTY4FWqk6J8briK0kQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=29HPIpnxEyWaQijPGfb9bCbcjH8kgl9NOmHafAyjGic=; b=hIQ3Vr/TTwSQxc6ftg1Ztto7tWfMNqvios9PadtJVxsCZVMCnSx0qYvZPwmUd62oH+MpeCRX2v/WAHdtiiHSsPCr8LwLklAzdkKLWaC43lwwRrtbuTG+vHHTm8kUOXj/XbYjfGG1r1Yjnxcwlgr5BPbS2tSjHLgywq0qvZexxU4=
Received: from PR1PR07MB4891.eurprd07.prod.outlook.com (20.177.208.146) by PR1PR07MB4939.eurprd07.prod.outlook.com (20.177.208.90) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.13; Wed, 9 Oct 2019 07:28:55 +0000
Received: from PR1PR07MB4891.eurprd07.prod.outlook.com ([fe80::9d2d:b0:f626:5b53]) by PR1PR07MB4891.eurprd07.prod.outlook.com ([fe80::9d2d:b0:f626:5b53%7]) with mapi id 15.20.2347.016; Wed, 9 Oct 2019 07:28:55 +0000
From: "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" <laurent.ciavaglia@nokia.com>
To: Marie-Jose Montpetit <marie@mjmontpetit.com>, Noa Zilberman <noa.zilberman@cl.cam.ac.uk>
CC: "coinrg-chairs@irtf.org" <coinrg-chairs@irtf.org>, "coin@irtf.org" <coin@irtf.org>, "nmrg-chairs@irtf.org" <nmrg-chairs@irtf.org>
Thread-Topic: [Coin] Academic contributions in COIN
Thread-Index: AQHVffC+4RAd5CU96kyJcQGcB1e/MqdREYFmgADT++A=
Date: Wed, 09 Oct 2019 07:28:55 +0000
Message-ID: <PR1PR07MB48916841A5B577F0AA38D881F3950@PR1PR07MB4891.eurprd07.prod.outlook.com>
References: <CAPjWiCTXJdkNWAMLhgv2Pb70gxX5=J0oXH8kyw4EfC4NF-B+PA@mail.gmail.com> <CAJi8f4EF-pEzkWkpQSsOESF84kzVH-U82JrSZJ2BcOPK3TDv0A@mail.gmail.com> <CAJi8f4EF-pEzkWkpQSsOESF84kzVH-U82JrSZJ2BcOPK3TDv0A@mail.gmail.com> <CAPjWiCSLw3Af8tzFxjv9rkMmJ4QfmK84Y6XhoxLiGxDxbE3U8w@mail.gmail.com>
In-Reply-To: <CAPjWiCSLw3Af8tzFxjv9rkMmJ4QfmK84Y6XhoxLiGxDxbE3U8w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=laurent.ciavaglia@nokia.com;
x-originating-ip: [88.121.21.187]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6a836c81-e209-42d7-ba8a-08d74c8a57a2
x-ms-office365-filtering-ht: Tenant
x-ms-traffictypediagnostic: PR1PR07MB4939:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <PR1PR07MB4939DAA0193AB8A3078441CCF3950@PR1PR07MB4939.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 018577E36E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(376002)(366004)(136003)(39860400002)(199004)(189003)(446003)(26005)(5660300002)(186003)(86362001)(2906002)(9686003)(76176011)(6436002)(7696005)(8936002)(7736002)(74316002)(102836004)(9326002)(11346002)(476003)(25786009)(53546011)(6506007)(4326008)(486006)(81156014)(52536014)(110136005)(54906003)(8676002)(14454004)(316002)(76116006)(81166006)(66066001)(6246003)(606006)(14444005)(6116002)(256004)(3846002)(790700001)(6306002)(54896002)(71190400001)(478600001)(99286004)(229853002)(33656002)(66946007)(64756008)(66446008)(66476007)(66556008)(236005)(71200400001)(55016002)(966005); DIR:OUT; SFP:1102; SCL:1; SRVR:PR1PR07MB4939; H:PR1PR07MB4891.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: zd2khPx4zsY04aBeQZPOLjbxKBuPT2ZFupwKm3MogCtZPTaKSfAfos4VJOf7E21XCJ/nemMoVMGwlovliZXZ1mkxJ+szzjNpC1EzavCTwLRTHyRsI27nT6mbiOmN3vnxIbw4grrg7nYn+1US7EL3Tis5BDp9UF2Ou3YU1JjkfM1MsFecgzKEOwNkk9QCrZLvrdq3uE/lX7qHQvUDEo2Qp/ZeILJTRNbcUwjEZXabEh9o8nCxBF8Z4LIQJ/COqDLb7bFc0gWEHYMeueAlJP/5abtjDXQlF15im/90osKEzrfG4nLSOVzLsNtAeNSgriGPzUCIgcn4yWUvQ4CXHgELH+2/sKLyL+Vcb69s996eXRL/TWUpfBfOgwKSTYMsP2xtn6pAxzS/BxZbi8nPQFx/zwbIdfJleZnPHnYogjMDywMlhTPJWEiAeNgltumqNPVFpnj7s36RepAKxCDgwEDFKg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_PR1PR07MB48916841A5B577F0AA38D881F3950PR1PR07MB4891eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6a836c81-e209-42d7-ba8a-08d74c8a57a2
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2019 07:28:55.3775 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: xKchBKVT3IUKWmANaGSS99HyupN989E3cVdvQSe1me2NHgH4qqWRziXIhXxACUcZ0iMmKwkB3XfahRK9o12e7cIGU9oS+1Z7EzqgvXlMAhM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR1PR07MB4939
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/2bDlhBm9Anmpoe5W4gAqqKpypUk>
Subject: Re: [Coin] Academic contributions in COIN
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: Wed, 09 Oct 2019 07:29:03 -0000

Hi,

In NMRG, we're facing similar challenges wrt. involvement of academics.
Here are few of the things we have done / are trying to do:

- Co-locate interim meetings at universities/research centers (or local/regional hubs) with active teams in the domain and try to attract close-by teams to participate.
- Bring the RG where the research/academic community meets and provide tutorials, interim meetings there. This is useful also to bring the knowledge of what the RG is, how it works and sometimes the activity of the RG is more focused/advanced on some areas and helps to teach/increase the level of awareness of the community.
- Publish position paper(s) and survey paper(s) on the topic by active members of the RG. This is usually well handled by a mix of industry/academic teams and link the published papers as results/outcome of the RG. This is usually more straightforward and timely than going through the RFC publication cycle (even with efficient processing, by the time of RFC publication, the content may be obsolete / not so relevant anymore).
- Balance theoretical and practical aspects of the research.
- If relevant, create dedicated workshops (co-located with conference on the topic), special issues in journals/magazines.
- Liaise with research projects (EU has regular calls and projects). Such consortia are usually good sources of inputs/resources and are eager to contribute to (pre-)standardization activities.
- We have used virtual meetings as a means to ease participation and involvement. Remote participation at IETF meetings (active or passive) is also useful.

I think you are aware of it, but at most IETF meetings, academics and locals could get access to "discounted" rates.

I also welcome other proposals and feedback, because this is, I think, a common challenge for the IRTF RGs.

At another level, having another "official" and recognized output channel from the IRTF (i.e. not only RFCs) would be much useful. I remember there have been discussions on an IRTF Journal ("ANRJ" 😉). I would much support this project.

HTH, best regards, Laurent.

From: Coin <coin-bounces@irtf.org> On Behalf Of Marie-Jose Montpetit
Sent: Tuesday, October 8, 2019 20:32
To: Noa Zilberman <noa.zilberman@cl.cam.ac.uk>
Cc: coinrg-chairs@irtf.org; coin@irtf.org
Subject: Re: [Coin] Academic contributions in COIN

Some comments below.

Marie-José Montpetit, Ph.D.
Research Affiliate, MIT Media Laboratory
mariejose@mjmontpetit.com<mailto:mariejose@mjmontpetit.com>
mariejo@mit.edu<mailto:mariejo@mit.edu>


On October 8, 2019 at 2:01:33 PM, Noa Zilberman (noa.zilberman@cl.cam.ac.uk<mailto:noa.zilberman@cl.cam.ac.uk>) wrote:
Hi,

I would suggest that we need to find ways to incentivize academics to engage with COIN.

Some ideas that I can think of are:
1. Clearly list challenges on the wiki. These may be accompanied by drafts, but not necessarily, and can be something that was discussed on the mailing list,
   a presentation from a meeting etc. Ideally those will be accompanied by one or two lines to describe the challenge (+pointers). This helps not only to identify gaps, but also if there's a graduate student looking for a project in in-network computing, there may be a "go to page" hosted by COINRG with potential research challenges, and potential collaborators.

This is at good idea for the Github - if we phase out the wiki - as it is easier to collaborate. I think challenges could be discussed on the mailing list then uploaded and I would love for people involved (the collaborators) to edit the challenge as things progress - or at least send us the updates As for the “go to page” it’s for me part of the description like you say “the posters”..

2. Invite postdocs and students to talk at the meetings. They are usually the first authors of papers so they know the tech side well, are more likely to have the time to travel, and are eager to discuss their research.

In my mind when we invite someone any member of the team can come :) Of course there are the issues of travel, registration etc. Sadly we do not have a budget.

3. Make data available (this was briefly mentioned in the meeting). These may be use cases, datasets, traces etc.  Research is better if it is driven by real world data (and more likely to get published).

Yes! Data from real world sets and librairies I would say. Or at least real-world use cases.

4. List collaboration opportunities, internships etc that fall within COINRG domain.

Of course!



mjm

Kind Regards,
Noa

On Tue, Oct 8, 2019 at 4:55 PM Marie-Jose Montpetit <marie@mjmontpetit.com<mailto:marie@mjmontpetit.com>> wrote:
Today at the Interim Noa Zilberman raised the issue on how to help academics contribute to COIN (thanks Noa!).

Obviously drafts are not the right vehicle for most academics and Colin Perkins added that we could have other mechanisms.

Some inputs:
- academic presentations at the meeting with appropriate papers stored in the Github and datatracker (we already have done some of this)
- if a topic could lead to a RFC support academic collaborators in writing a draft
- keeping a list of related conferences and try to have mini-PRG meetings there

But I am sure there is much more. So what are the list’s ideas?

The minutes of the meeting will be issued and I have a recording I will upload to the GitHub.

Thanks all!

mjm

Marie-José Montpetit, Ph.D.
Research Affiliate, MIT Media Laboratory
mariejose@mjmontpetit.com<mailto:mariejose@mjmontpetit.com>
mariejo@mit.edu<mailto:mariejo@mit.edu>
--
Coin mailing list
Coin@irtf.org<mailto:Coin@irtf.org>
https://www.irtf.org/mailman/listinfo/coin