Re: [nwcrg] [LOOPS] BOF co-chairs thinking on LOOPS next steps

Marie-Jose Montpetit <> Thu, 25 July 2019 12:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 827E31200A4 for <>; Thu, 25 Jul 2019 05:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BWKilJWlGAmF for <>; Thu, 25 Jul 2019 05:34:56 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3ABF012016A for <>; Thu, 25 Jul 2019 05:34:56 -0700 (PDT)
Received: by with SMTP id k8so96906151iot.1 for <>; Thu, 25 Jul 2019 05:34:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=PC3A+1B3wjsVi5L1AqT3rzZ4/qcTaLOcpzgC97RoBa0=; b=duLMJmZjSP1fxMTRk4EQAbIn0YfiKyuzWX6qNfOVAPyDOabvUHM+2Sa0pPbgEqN5eV Vcu+Dtfe5j92Fd4s9qJWfWCXuRV8hczll0RFXX0pLa8Q6X4xtF1jgnPS3JBwJEXZyewk piouLY1otkW/s58drXaBqDWtVcc5himOu1O3lsHYi8Kp0vQb0Os+cZvyMg0n8EbAjyuB ECqzYZqW+7tYuME/7uU5t0uf39bdpc2quhaRFmDK++h1UOZA4S/Zsfx8qwEirUZ1EJWU YQ2wkkqKFeeCKP4T1xPLslS1cIvl4h1/P1Zmc4hAO5pHmJTJclJ2LNK4JExGwB+jOXjT 2tpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=PC3A+1B3wjsVi5L1AqT3rzZ4/qcTaLOcpzgC97RoBa0=; b=BxQpYUpzvQrNQBbyApldUy9M15wgrw/VqakVksQXhAsf1/awTafWOrlDLIUJvfk0jh JBvDxyzE76v7TQJ4qpWtReTtlZ/FkrZaWF7r4YazPuPeFVDpsGTNoIxV9JwQTGPsHKZl ENBarJWAMAX5KyXnY0dxZV5gyeGzTic1rhH2FicFfqBMKiI5JRbAq76rqiHNhIaE/Hmg WWvQBC8/VWvrwmhGTNF9rq4gYnTWyrhI0NGvo/jCT29+pezyd/r7oKR6Ub3UfnRmq4mt 1xYzlG2bUr8hm5r7JdNwIwahCff9aqPx+fRBsI4r2FupcHJD3mY+6GZq2KzceXCpKN8o cJ3g==
X-Gm-Message-State: APjAAAWiQaq1OYq2sfc2+PbHQi1XlnXKXmwrFba6c9J3IslgWUxgmatW 6/pBZuSkOCPYXnYXXwvX60ZtYoZJZHshFy11azBMVXnm
X-Google-Smtp-Source: APXvYqzdwQpt39IIZ+ReUu328eg5s1aoP7G494dU9WP7lwXcXpayfkPtEzPiioqdr3g1o2qBzSK/Lyi3QqR0hdnFruY=
X-Received: by 2002:a02:8814:: with SMTP id r20mr94766607jai.115.1564058095453; Thu, 25 Jul 2019 05:34:55 -0700 (PDT)
Received: from 1058052472880 named unknown by with HTTPREST; Thu, 25 Jul 2019 05:34:55 -0700
From: Marie-Jose Montpetit <>
In-Reply-To: <>
References: <> <> <>
MIME-Version: 1.0
Date: Thu, 25 Jul 2019 05:34:54 -0700
Message-ID: <>
To: Carsten Bormann <>
Cc:, Suresh Krishnan <>, Magnus Westerlund <>, Spencer Dawkins at IETF <>, Mirja Kuehlewind <>, "" <>
Content-Type: multipart/alternative; boundary="000000000000301181058e80a7ac"
Archived-At: <>
Subject: Re: [nwcrg] [LOOPS] BOF co-chairs thinking on LOOPS next steps
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 25 Jul 2019 12:34:59 -0000

Adding the nwcrg list to list thread. And with my NWCRG co-chair hat on.

Like I mentioned the WIFI to node hop was one of the original successes of
network coding as Prof. Médard and her team can attest to. A lot of the
LOOPS use cases for per hop network optimization have been not only
*researched* but *implemented* with running code by many of the nwcrg

NWCRG-ites; there was a LOOPS BOF on Monday to address the issues of
performance in multiple hop networks and Carsten is pointing to the related

Marie-José Montpetit, Ph.D.
Research Affiliate, MIT Media Laboratory

On July 25, 2019 at 12:56:37 AM, Carsten Bormann ( wrote:

On Jul 24, 2019, at 18:17, Marie-Jose Montpetit <>
> Standardisation of what? The architecture? The protocols (beware there is
already FECFRAME and others)? The proxies?

Hi Marie-José,

details of the thinking that was developed in the side meetings that
happened at the previous two IETF meetings can be found at

The BOF actually added one piece of information I didn’t previously
perceive that way:
People seem to really want to tackle the host-to-node case (as needed,
e.g., for going through WiFi access clouds) right away, not just the
in-network (node-to-node) case. That would be the one thing I would change
based on my recollection of the BOF. But of course there may be other
things; it may be worth to now have another round of discussion of the
proposed charter.

Grüße, Carsten