<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Good point, Brian. As someone on the call this morning pointed out, the transmission ID in BIBE (as per the most recent I-D) serves a similar purpose.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Scott<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Sipos, Brian J. <Brian.Sipos@jhuapl.edu> <br><b>Sent:</b> Thursday, April 24, 2025 11:22 AM<br><b>To:</b> sis-dtn@mailman.ccsds.org<br><b>Cc:</b> sburleig.sb@gmail.com<br><b>Subject:</b> Possible structure and logic for BIBE segmentation<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All,<o:p></o:p></p><p class=MsoNormal>As I mentioned on the call today, the draft UDPCL update contains a portion which defines a unidirectional segmentation mechanism [1] that has a slight optimization for single-segment transfers. I’m offering this as an example of a mechanism that is simple and has already had some amount of prototyping done although in a different context.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The Transfer ID behaves as Felix had suggested on the call, which is that it has no relationship to the bundle ID being segmented, it is purely a unique correlator created by the encapsulating node. A receiver a windowed log of seen Transfer IDs serves a secondary purpose for dropping duplicate encapsulating bundles at the CLA before they reach the BPA. The rest of the fields behave similarly to existing fragmentation/segmentation mechanisms.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Brian S.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[1] <a href="https://www.ietf.org/archive/id/draft-ietf-dtn-udpcl-00.html#section-3.5.2">https://www.ietf.org/archive/id/draft-ietf-dtn-udpcl-00.html#section-3.5.2</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>