<span style=" font-size:10pt;font-family:sans-serif">Hi,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">the situations
regarding UDPCL is unfortunately a bit messy. We have:</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">1) Annex B4 in
CCSDS 734.2-B-1</span>
<br><span style=" font-size:10pt;font-family:sans-serif">2) there is RfC
7122 in I<b>R</b>TF</span>
<br><span style=" font-size:10pt;font-family:sans-serif">3) expired UDPCL
draft in IETF </span><a href="https://datatracker.ietf.org/doc/draft-sipos-dtn-udpcl/"><span style=" font-size:12pt;color:blue"><u>draft-sipos-dtn-udpcl-01
- Delay-Tolerant Networking UDP Convergence Layer Protocol (ietf.org)</u></span></a><span style=" font-size:12pt">
</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">In terms of BP
encoding, they are basically the same (just put a bundle in UDP datagram
payload, called unframed transfer in the IETF draft). 3) goes beyond that
as it also includes DTLS / Keep-alive / CL-Layer fragmentation).</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I think we really
need to understand the 'space use cases' to make a good decision what to
include (or wait for UDPCL in IETF). In general, it does not appear to
me to useful in (most) space scenarios (besides testing) as at least the
simple approach has some limitation (bundle sizes should be small to avoid
IP fragmentation, need for explicit congestion control). I think what we
should try to avoid is that we get protocol stacks like BP / UDPCL / UDP
/ IPE / EPP when BP / EPP would be enough.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Regards,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Felix</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Tomaso
de Cola via SIS-DTN" <sis-dtn@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif"><beau.t.blanding@nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">sis-dtn@mailman.ccsds.org</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">13/05/2022
09:59</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
[Sis-dtn] Clean version of the CCSDS BPv7 Red Book draft</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"SIS-DTN"
<sis-dtn-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Dear
Beau,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thank
you for sharing the clean version. Just a few quick comments on the CLA
annex:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<br><span style=" font-size:10pt;font-family:sans-serif">1.
</span><span style=" font-size:11pt;font-family:Calibri">For
UDPCLA, shall we point to RFC 7122?</span>
<br><span style=" font-size:10pt;font-family:sans-serif">2.
</span><span style=" font-size:11pt;font-family:Calibri">As
mentioned by Felix, we should have dedicated text for EPP and SPP. Let’s
take also into account (probably with a note) that with the new version
of SPP there exists no dedicated APID for BP or LTP. On the contrary, EPP
has dedicated protocol identifiers (available also in SANA) for pointing
to BP or LTP.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">3.
</span><span style=" font-size:11pt;font-family:Calibri">I’m
not quite sure that we can add a USLPCLA since so far (i.e. for what available
in the current USLP spec), the UPID defined in USLP TFZ points only to
EPP or SPP. Then BP/LTP has to be encapsulated over either of these two,
but cannot go directly into USLP. If we see relevant to have direct encapsulation,
I think we should pass this requirement to Greg and the SLP folks to see
if they can accommodate this into a new version of USLP. After that we
can have a dedicated USLPCLA, otherwise I’m afraid the BPv7 would be inconsistent
with the current USLP spec in this respect. </span>
<br><span style=" font-size:10pt;font-family:sans-serif">4.
</span><span style=" font-size:11pt;font-family:Calibri">It
is stated that the largest bundle over LTP cannot be more than 4GB: where
does this requirement come from?</span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thank
you for the clarification,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Tomaso</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
SIS-DTN <sis-dtn-bounces@mailman.ccsds.org> <b>On Behalf Of </b>Blanding,
Beau T. (MSFC-HP27)[HOSC SERVICES CONTRACT] via SIS-DTN<b><br>
Sent:</b> Donnerstag, 12. Mai 2022 21:43<b><br>
To:</b> sis-dtn@mailman.ccsds.org<b><br>
Subject:</b> [Sis-dtn] Clean version of the CCSDS BPv7 Red Book draft</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hello
all,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Attached
is the clean version of the BPv7 Red Book, where most of the changes present
have been accepted. I unfortunately do not have access to the google box
right now, so there is one place that has not been completely cleaned up
according to the edits that were made on the google box version (beginning
of section 2.1). I was able to take the proper notes on everything else
and apply it to the clean version.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thank
you,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:16pt;font-family:Calibri">Beau
Blanding</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">HOSC
Systems Engineer</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">MSFC
4663, Office C121</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><a href=mailto:beau.t.blanding@nasa.gov><span style=" font-size:11pt;color:#0082bf;font-family:Calibri"><u>beau.t.blanding@nasa.gov</u></span></a></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span><tt><span style=" font-size:10pt">_______________________________________________<br>
SIS-DTN mailing list<br>
SIS-DTN@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>
<p style="margin-top:0px;margin-Bottom:0px"></p>