<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Good points. We should probably go over these at some point on Thursday…</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>—keith</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"<a href="mailto:Jeremy.Mayer@dlr.de">Jeremy.Mayer@dlr.de</a>" <<a href="mailto:Jeremy.Mayer@dlr.de">Jeremy.Mayer@dlr.de</a>><br>
<span style="font-weight:bold">Date: </span>Monday, April 4, 2016 at 5:46 PM<br>
<span style="font-weight:bold">To: </span>"Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>>, "<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>" <<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: [dtn] high level summary<br>
</div>
<div><br>
</div>
<div 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">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Just to keep it at the forefront of the SIS-DTN hivemind, the “significant changes from RFC5050” section of BPBis is listed below. Items which may
cause an issue or should otherwise be noted are bolded.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">12. Significant Changes from RFC 5050<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> Points on which this draft significantly differs from RFC 5050<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> include the following:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Clarify the difference between transmission and forwarding.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Amplify discussion of custody transfer. Move current custodian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> to an extension block, of which there can be multiple<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> occurrences (possible support for the MITRE idea of multiple<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> concurrent custodians, from several years ago); define that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> block in this specification.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> .
<b>Introduce the concept of "node ID" as functionally distinct<o:p></o:p></b></span></p>
<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> from endpoint ID, while having the same syntax.
<i>JPM: We’ll need to check our use of Node ID Vs. endpoint ID in documents<o:p></o:p></i></span></b></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">
<b>. Restructure primary block, making it immutable. Add optional<o:p></o:p></b></span></p>
<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> CRC.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Add optional CRCs to non-primary blocks.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Add block ID number to canonical block format (to support<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> streamlined BSP).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Add bundle age extension block, defined in this specification.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Add previous node extension block, defined in this<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> specification.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> .
<b>Add flow label extension block, *not* defined in this<o:p></o:p></b></span></p>
<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> specification.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Add manifest extension block, *not* defined in this<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> specification.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Add hop count extension block, defined in this specification.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> . Clean up a conflict between fragmentation and custody transfer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> that Ed Birrane pointed out.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> .<b></b>Remove representation specifications from the document, making<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> the protocol specification representation-neutral.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">In addition, please note that class of service has been removed from BPBis, which causes a few issues: First, it (sort-of) flies afoul of section
3.3 of the BP Blue Book: Conformant implementations of the CCSDS Bundle Protocol shall implement the ‘Extended Class of Service (ECOS)’ block defined in annex C”. While the Extended Class of Service block as it is defined in the annex can be added to a BPBis-based
implementation, it isn’t extending anything. The idea from IETF is that a new document will be created which defines a representation-agnostic CoS implementation.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Second, in section 4.3.5, the “class-of-service parameter” is specified, which is no longer in the BP primary block. These changes will also create
a change to Annex F: BP Managed Information. In F2.2, there’s a table of bundle state information which must be collected. In that list, we specify that the collection of bundle counts for bulk, normal, and expedited priorities is mandated. If I were to implement
a BPBis system today, there would be no way to collect these values.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Jeremy<o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">
<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">sis-dtn-bounces@mailman.ccsds.org</a> [<a href="mailto:sis-dtn-bounces@mailman.ccsds.org">mailto:sis-dtn-bounces@mailman.ccsds.org</a>]
<b>On Behalf Of </b>Scott, Keith L.<br>
<b>Sent:</b> Montag, 4. April 2016 23:10<br>
<b>To:</b> <a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a><br>
<b>Subject:</b> [Sis-dtn] FW: [dtn] high level summary<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I highlighted the bpbis going to last call in what’s below. This will essentially complete the IETF update to BP so the time to ensure that the new protocol
is compatible with what we envision for the future of CCSDS (I think it is, but encourage a vigorous review) is now.<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">—keith<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">[thanks to Marc for the notes!]<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">---------- Forwarded message ----------<br>
From: <b><span style="color:black">Marc Blanchet</span></b> <span style="color:black">
<<a href="mailto:marc.blanchet@viagenie.ca">marc.blanchet@viagenie.ca</a>></span><br>
Date: Mon, Apr 4, 2016 at 3:53 PM<br>
Subject: Re: [dtn] high level summary<br>
To: DTN WG <<a href="mailto:dtn@ietf.org"><span style="color:black">dtn@ietf.org</span></a>><br>
Cc: <a href="mailto:dtn-chairs@ietf.org"><span style="color:black">dtn-chairs@ietf.org</span></a><br>
<br>
<br>
hello,<br>
while we will be publishing meeting notes, I thought that it would be useful for people to get a high-level super short summary of next steps following today’s meeting. Specially given the difficulties with the audio we had. Obviously, nuances are not detailed
here.<br>
<br>
Hope this is useful.<br>
<br>
Marc.<br>
<br>
====<br>
Summary of next steps following today’s meeting<br>
<br>
<b><span style="color:red">bpbis: start a 4 weeks wg last call around April 18th<br>
</span></b>bpsec: possibly move CMS to a separate doc. Ed to start a thread on ML. Need to talk to CCSDS about needs.<br>
pkdn: we need to work on a requirement document, including assumptions, separating typical pki requirements with the ones that are specific or influenced by a dtn environment. Most likely need to be discussed with pkix experts.<br>
ama: publish new version of requirements. start a discussion with OPS<br>
ip neighbour: need to step back and write a more generic neighbour/local services discovery architecture document.<br>
static routing: need addressing before. need editors for addressing.<br>
<br>
_______________________________________________<br>
dtn mailing list<br>
<a href="mailto:dtn@ietf.org" target="_blank"><span style="color:black">dtn@ietf.org</span></a><br>
<a href="https://www.ietf.org/mailman/listinfo/dtn" target="_blank"><span style="color:black">https://www.ietf.org/mailman/listinfo/dtn</span></a><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>