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

Marie-Jose Montpetit <marie@mjmontpetit.com> Thu, 25 July 2019 19:13 UTC

Return-Path: <marie@mjmontpetit.com>
X-Original-To: loops@ietfa.amsl.com
Delivered-To: loops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 508531201A0 for <loops@ietfa.amsl.com>; Thu, 25 Jul 2019 12:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.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 k1hAZCl_2jPt for <loops@ietfa.amsl.com>; Thu, 25 Jul 2019 12:13:30 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 B09141201C5 for <loops@ietf.org>; Thu, 25 Jul 2019 12:13:30 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id h6so13021844iom.7 for <loops@ietf.org>; Thu, 25 Jul 2019 12:13:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=gnRtr6ZSX8hTCxFxStqTw892EbNTRunDsno7OaypUwU=; b=Sfe/9hPIRyMvoKpGwlL7cDX6OZSVabh2xyY5fo9AlmBEdoF1OLji4AZGPys2OCOt7X bOxGzcR+yN8eBRMXVF6a1grxl4CnmM5tk4CUPQRqEu9ufAJX5C5ptaz2RSgBlGH3FFkj ltR4ovHA6nOmQ7Ras8lurdF8P0njHCRJxvoTugPRY2WJVAafH2BJ6b6hmmv04jDyWBfq PcpgVsKlZavzb6daBy9gLfkIQ+jmfo+6KFgxprICywciMTUi+mTp6I27+g69NcFUZRto gAuWe09rKw6XWJjY5BzY7DkRRjrGzlfQvB+8qLaSLlebKbGExCgE25Afj5w3ivCsfVf8 kTxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=gnRtr6ZSX8hTCxFxStqTw892EbNTRunDsno7OaypUwU=; b=lGxh8NzirmXz5Sx80/w6jQsFhb5kfrNSJBXGPxHjFy3+fqL21Tgn0ox1lfyrSx84ET rCfPAocuiVGdGss8xz8HXeMAqMxNXMuET/QtfKGMqCWPHaWloX5fndalFiQxpvbJMK7p Vj2adWQpX/w9FF/q0c0sAQ5tYuilAF5J6H1BUFTsmtaKnl8YLNI/a/J8/CbJIGP59ssc ucoZHyoA6Vgv45HFWPYhgeZoUn7v2iU8pzJMoLA9aPqRl3QwuLdoEAy7q+huBQX588RE ZT/ept625VfKr84HaBZosshFa7oPN//JG61WcovvOeRgEN1pkRZ4Gf5n0xWi9P6lkyrr UcXg==
X-Gm-Message-State: APjAAAVEP+/0+OyKnc3LHJgZcCAaVVQAD4htTMPwaL6pp7RdwUKxPy27 deRP/0fbec+qtacD+gDHm+jkOpTsEAPP/2HsqDU=
X-Google-Smtp-Source: APXvYqysci1MALZ2Ebj9YVzExnOXdAeGbwlN3bKuslE3VOAPiJkbcx+LfJxb7+YpS9DSaeMh20zTWFK8jIMaKIT9D/s=
X-Received: by 2002:a6b:3b03:: with SMTP id i3mr83459760ioa.302.1564082009958; Thu, 25 Jul 2019 12:13:29 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 25 Jul 2019 12:13:29 -0700
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
In-Reply-To: <5A453FDB-79D2-4E70-A384-AEDC82547FF8@tzi.org>
References: <CAKKJt-eRGJe+9PtEC7xgFz+HA0zsr_sR0NUgKRmJ-P5Q3XBg-A@mail.gmail.com> <CAPjWiCSbPioTHkYBpX73qxzO=H1sJDZpCMCKzBKoU4rZLLhwMQ@mail.gmail.com> <E6659E42-D6D7-4033-B4D6-9305823063D2@tzi.org> <CAKKJt-c24RdPyZRoK-B6fXuN0xABUsU=p7Y6UFwAcENfjE3oOQ@mail.gmail.com> <5A453FDB-79D2-4E70-A384-AEDC82547FF8@tzi.org>
MIME-Version: 1.0
Date: Thu, 25 Jul 2019 12:13:29 -0700
Message-ID: <CAPjWiCTSyi8Gm6AaAV_YWMjO0JnTxB28V0=a28vTiWA-gzoirw@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Carsten Bormann <cabo@tzi.org>
Cc: Suresh Krishnan <suresh@kaloom.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Mirja Kuehlewind <ietf@kuehlewind.net>, loops@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009a8298058e8638c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/loops/6mBARLPRlwwGJ70mbGYCZg7GCZM>
Subject: Re: [LOOPS] BOF co-chairs thinking on LOOPS next steps
X-BeenThere: loops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Local Optimizations on Path Segments <loops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/loops>, <mailto:loops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/loops/>
List-Post: <mailto:loops@ietf.org>
List-Help: <mailto:loops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/loops>, <mailto:loops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 19:13:33 -0000

Which begs the question if the retransmission delay will kill the
application.

mjm

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

On July 25, 2019 at 3:10:39 PM, Carsten Bormann (cabo@tzi.org) wrote:

On Jul 25, 2019, at 14:59, Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:
>
> […] If the LOOPS community can’t live without host-to-node, the community
should add it. If the community can make use of LOOPS without host-to-node
and add it later, the community might consider whether that reduces the
scope of the initial proposed charter enough to help Magnus approve it :-)

Right. One other place where we can structure the milestones further is by
starting with retransmission mode only and add FEC mode in a second step.

So this would give us a nice and small first deliverable (retransmission
mode for node-to-node) that we can then recharter from. If we do this
right, this doesn’t even need to increase the time up to when we deliver
the whole protocol including both host-to-node and FEC.

Grüße, Carsten