<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; font-size: 14px; font-family: Calibri, sans-serif;">
<div style="color: rgb(0, 0, 0);">
<div>
<div>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.</div>
</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>—keith</div>
<div><br>
</div>
<div>[thanks to Marc for the notes!]</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir="ltr"><br>
<div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername" style="color: rgb(0, 0, 0);">Marc Blanchet</b> <span dir="ltr" style="color: rgb(0, 0, 0);">
<<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" style="color: rgb(0, 0, 0);">dtn@ietf.org</a>><br>
Cc: <a href="mailto:dtn-chairs@ietf.org" style="color: rgb(0, 0, 0);">dtn-chairs@ietf.org</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>
<font color="#ff0000"><b>bpbis: start a 4 weeks wg last call around April 18th<br>
</b></font>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" style="color: rgb(0, 0, 0);">dtn@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/dtn" rel="noreferrer" target="_blank" style="color: rgb(0, 0, 0);">https://www.ietf.org/mailman/listinfo/dtn</a><br>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>