<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I think this is super interesting and we should try to have the presentation in the common session with the Security WG.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Regarding message loss detection, is there some overlap with the sequence numbering we are seeking to introduce in the Compressed Bundle Reporting / Custody transfer Orange Book (<a href="https://docs.google.com/document/d/1YPTwJ7_3az5WliWspg0F0M2FsoPoCoVS/edit">https://docs.google.com/document/d/1YPTwJ7_3az5WliWspg0F0M2FsoPoCoVS/edit</a>)?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">In its simplest form, the CREB just contains a bundle sequence number (‘scoped’ by the source node) with sequences according to the bundle’s destination endpoint IDs. This CREB actually does not
request any reporting (maybe we should work on terminology) but allows the destination node to detect gaps in sequences of bundles (and do re-ordering if required).
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="mso-ligatures:none">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-ligatures:none">Felix<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none">From:</span></b><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none"> SIS-DTN <sis-dtn-bounces@mailman.ccsds.org>
<b>On Behalf Of </b>Tian, Xisen (LT) via SIS-DTN<br>
<b>Sent:</b> Tuesday, September 24, 2024 3:23 AM<br>
<b>To:</b> sis-dtn@mailman.ccsds.org<br>
<b>Cc:</b> Hale, Britta (CIV) <britta.hale@nps.edu>; Bhagya Wimalasiri <b.m.wimalasiri@sheffield.ac.uk>; Benjamin Dowling <dowling.bj@gmail.com><br>
<b>Subject:</b> [Sis-dtn] Spring Meeting Agenda Add: BPSec Analysis and Improvements<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Hello, <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">I’m Xisen Tian, I’m a PhD student being advised by Dr. Britta Hale and Scott Burleigh at the Naval Postgraduate School researching cryptographic analysis of DTN protocols. My co-authors (cc’d)
and I have completed a formal analysis of BPSec with recommendations for improvements which we are ready to present to the DTN WG at the upcoming fall meeting in London. We would like to request a 30-45 minute time slot in the agenda to do a presentation of
our work followed by discussion on how our improvements could be adopted (if at all). Our full paper is forthcoming: it has been submitted to a journal and we are currently going through the review/revision process. I’ve pasted our abstract below:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">ABSTRACT: Space networking has become an increasing area of development with the advent of commercial satellite networks such as those hosted by Starlink and Kuiper, and increased satellite
and space presence by governments around the world. Yet, historically such network designs have not been made public, leading to limited formal cryptographic analysis of the security offered by them. One of the few public protocols used in space networking
is the Bundle Protocol, which is secured by Bundle Protocol Security (BPSec), an Internet Engineering Task Force (IETF) standard. We undertake a first analysis of BPSec, building a model of the secure channel security goals stated in the IETF standard, and
note issues therein with message loss detection. We prove security of BPSec under a limited model and also provide a stronger construction, one that supports the Bundle Protocol’s functionality goals while also ensuring destination awareness of missing messages
components.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US">Please let me know if you have questions, concerns, or feedback. Thank you.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none">Very Respectfully,
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none">Xisen Tian<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none">LT USN
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none">PhD Student<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none">Applied Cryptography<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-family:"Calibri",sans-serif;mso-ligatures:none">Naval Postgraduate School<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify
the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</body>
</html>