IETF Logo Mail Archive

Re: [core] Fwd: New Version Notification for draft-gomez-core-coap-space-00.txt

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 22 December 2023 16:02 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E2D4C14F6B8 for <core@ietfa.amsl.com>; Fri, 22 Dec 2023 08:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.807
X-Spam-Level:
X-Spam-Status: No, score=-2.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RyKbd-2Ye8Za for <core@ietfa.amsl.com>; Fri, 22 Dec 2023 08:02:24 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DEA2C090381 for <core@ietf.org>; Fri, 22 Dec 2023 07:29:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id ACB991800F; Fri, 22 Dec 2023 10:29:54 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kX83y7BmgTI4; Fri, 22 Dec 2023 10:29:53 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1E30B1800C; Fri, 22 Dec 2023 10:29:53 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1703258993; bh=qSzyA75PMmRpLuSleIlfH+tM5+7//LEa7bbKr/yjB4A=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=KMPdKah1CVtOIMHaQFGKogAT7DkRVtGU7Ev2+WuV8gwYxaARX7XqIfjbWu8lT6vH8 JCIh4CPHAqBwC4dXX9QLPdCgj56YTSaqMT+VXWqpp5GiqZOd5pRLbTptQAOKrKrA0j rkkXlsjiKtRtk9GnPsR8ClHirjGMunxMazwlqiQjYRufVzP1PlCVObIzuuIovcKSec 7gchdC+wUOKNuVO6iU0zqiqI8dwfch8YdaNVkw0lPopbDMGyxTOJXCgX3khxzEnpo8 LzSHKy8iUG+AVbGhZFv5MzEZTFqx2+F9gXb3iAVVcRjPEXuO1dqeTVLQEfead15Yrf d7OYMSWYjkYPg==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 19C2816E; Fri, 22 Dec 2023 10:29:53 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
cc: Carles Gomez Montenegro <carles.gomez@upc.edu>, core@ietf.org
In-Reply-To: <ZYQHihJ7yGgXum_D@hephaistos.amsuess.com>
References: <170305483701.55313.10459564268148308635@ietfa.amsl.com> <CAAUO2xyqRj_hcD=SvC+5J_Tp=Cr7vD-cw-eiS2246qw_GJGuNg@mail.gmail.com> <ZYQHihJ7yGgXum_D@hephaistos.amsuess.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 22 Dec 2023 10:29:53 -0500
Message-ID: <22845.1703258993@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/UN-Ng-1cVLDoKNcfynUV--giOWs>
Subject: Re: [core] Fwd: New Version Notification for draft-gomez-core-coap-space-00.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Dec 2023 16:02:28 -0000

Christian Amsüss <christian@amsuess.com> wrote:
    > One aspect that was discussed there was the choice of transmission
    > sequence and sharding, where memory and code complexity requirements are
    > traded against robustness of the protocol. Another trade-off to be
    > considered is fast forwarding: For the applications that have been
    > discussed previously, relaying through a proxy was highly relevant, and
    > that proxy can not only terminate retransmissions, but also participate
    > in FEC. If the proxy can not spool the whole resource, a wider spread of
    > FEC (which is desirable for robustness) leads to the proxy being unable
    > to participate in FEC. (As a complete space layperson, I imagine that
    > such a proxy would be highly capable though, and could easily do all FEC
    > recovery -- images of space stations receiving transmissions and
    > forwarding them to ground stations once they pass over them comes to
    > mind).

Outside of block mode with FEC, CoAP messages could be routed through
different proxies.  They could even be forwarded simultaneously through
multiple paths.  Space systems might want to do that.

I think that if ones want proxies that can participate in FEC, that it needs
to happen above the block mode.  More like $HTTP_PROXY with the application
aware that it's talking to that proxy.

Finally, I want to dissuade people from thinking that deepspace IP is just
about talking to ground stations.  I think that nobody wants to hairpin traffic between a
satellite orbitting Io and Ganymede through Earth.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email