<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div style="font-family: sans-serif;">
<div class="markdown" style="white-space: normal;">
<p dir="auto">Hi Michael</p>
</div>
<div class="plaintext" style="white-space: normal;">
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">Did you consider rechartering dtnrg ?</p>
</blockquote>
</div>
<div class="markdown" style="white-space: normal;">
<p dir="auto">IMHO most of the LEO stuff is quite far from DTNRG and needs its own home; although strong overlaps exist between some of the bundle protocol ideas and DTN. (There was also Kevin Fall’s
<a href="https://spectrum.ieee.org/the-interplanetary-internet" style="color: #3983C4;">
Interplanetary Internet</a> and <a href="https://www.ipnsig.org/" style="color: #3983C4;">
IPNSIG</a>).</p>
</div>
<div class="plaintext" style="white-space: normal;">
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">It seems to me that there is research needed in predictable routing flaps. Most routing protocols today assume that failures are random.</p>
</blockquote>
</div>
<div class="markdown" style="white-space: normal;">
<p dir="auto">Totally agree!</p>
<p dir="auto">Best Wishes<br>
nishanth</p>
<p dir="auto">On 6 Mar 2025, at 18:48, Michael Richardson wrote:</p>
</div>
<div class="plaintext" style="white-space: normal;">
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">Nishanth Sastry via Starlink <starlink@lists.bufferbloat.net> wrote:
<br>
> Great question. One clear and easy answer is that this is meant to be <br>
> an IRTF group rather than an IETF group, so with more of a focus on <br>
> identifying long-term research issues (that are of interest to the IETF <br>
> community) rather than on forming standards. We think there is a need <br>
> for an IRTF-lens to draw clear boundaries, identify overlaps, and <br>
> connect interfaces across architectures (e.g., Bundle Protocol/IP), <br>
> different variants the space domain (LEO/DeepSpace), phenomena <br>
> (Delay/Disruptions down to relativistic effects), and entities (IETF, <br>
> CCSDS, IOAG, but also the private players in the space, like <br>
> Starlink).</p>
<p dir="auto">Did you consider rechartering dtnrg ?</p>
<p dir="auto">> That said, the meeting is really to figure out what the community
<br>
> thinks there is a need for, and indeed, whether there is a need for <br>
> something like this. Why not come to the meeting (virtually or in <br>
> person) to provide your views and inputs on things we could/should do? <br>
> Of course, appreciate that the Bangkok timezone may not work out for <br>
> some, but if we manage to get this going, we are hoping to have regular <br>
> activities in other IETF meetings which will be in other time zones.</p>
<p dir="auto">It seems to me that there is research needed in predictable routing flaps.
<br>
Most routing protocols today assume that failures are random.</p>
<p dir="auto">There is some work in RPL (RFC6550) as related to 6TISCH (TSCH) where
<br>
channels come and go already, but that is multiple times/second vs multiple <br>
times/hour.</p>
<p dir="auto">-- <br>
] Never tell me the odds! | ipv6 mesh networks [ <br>
] Michael Richardson, Sandelman Software Works | IoT architect [</p>
</blockquote>
</div>
<div class="markdown" style="white-space: normal;">
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">] <a href="mailto:mcr@sandelman.ca" style="color: #777777;">mcr@sandelman.ca</a>
<a href="http://www.sandelman.ca/" style="color: #777777;">http://www.sandelman.ca/</a> | ruby on rails [</p>
</blockquote>
</div>
</div>
</body>
</html>