<html 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=iso-8859-1">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">We need to discuss the caveats below. Please look these over prior to this meeting.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">CONDITIONS/COMMENTS:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"> Erik Barkley (Approve with Conditions): A couple of conditions:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">1) Minor editorial comment, but I think somewhat important - section <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">1.2, change "proposed" to "recommended" in "...This document provides <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">an overview and proposed methods for transmission of video over DTN using RTP"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">2) Figure 2-4, please correct "RTC 3550" to read "RFC 3550" -- <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">rationale, both RTP and RTCP are defined in RFC 3550.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"> Peter Shames (Approve with Conditions): While this document <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">should be very useful for that class of missions that requires the <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">support of video over RTP over BP, the document, as written, is <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">rather casual in form and does not conform to the usual CCSDS norms <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">for Utilization Profile or Adaptation Profile style of Blue <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Books. It is certainly "Blue-ish" in nature, but needs to be edited <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">and tightened up. It reads rather more like an agency research paper <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">than a CCSDS Blue Book.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">For examples of what I would have expected to see in terms of clear <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">presentation of protocol stacks, PDU & end to end diagrams, etc <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">please review IP Over CCSDS, 702.1-B-1. Some of the text and <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">figures, such as sec 2.5.3 and fig 2-10, mix protocol and <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">implementation details. This is not a CCSDS norm.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">I recommend that you look at the SCCS-ARD, CCSDS 901.1-M-1, which is, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">in fact, referenced in the test report, but not here, for some <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">end-to-end and protocol stack examples. You are, in essence, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">layering this on top of DTN, but these will give you some protocol <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">stack and deployments examples to follow for clarity. Also think <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">about what support might be needed in relay nodes, ground stations, <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">and other nodes along the way to support these high rate flows.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">There are a number of standards mentioned in Sec 3 that do not appear <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">in the references (SDP, RTCP, SBS/PPS, H264, MPEG, MIME, and BPV7 (to <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">pair with BPSec). As noted by Wilmot, the ICS is rather abbreviated <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">in nature compared to the details in the text itself.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Finally, I believe that the provisioning of such video services, both <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">in space nodes and in ground systems, deserves creation of the <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">relevant entries in the SANA Service Site and Aperture and Roles <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">registries. See also recent discussions in the DTN WG about DTN registries.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"> Ignacio Aguilar Sanchez (Approve with Conditions): 1. Simplify <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">section 2 Overview. Move and expand, if need be, selected topics in <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">an accompanying Green Book.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">2. Introduce managed information as for instance done in Annex F of <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">the Bundle Protocol BB.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"> Jonathan Wilmot (Approve with Conditions): 1) Some optional <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">features do not have documented interoperability tests per CCSDS <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">A02.1-Y-4 "in cases in which one or more options or features have not <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">been demonstrated in at least two interoperable prototypes or <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">implementations, the specification may advance to the CCSDS <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Recommended Standard level only if those options or features are removed;"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">2) Tests should include a range of delays, disruption durations, and <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">out-of-order packets to simulate space use cases. If the standard <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">only applies to near earth scenarios, then that should be stated.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<div style="width:100%;height: 20px;"><span style="white-space:nowrap;color:#5F5F5F;opacity:.36;">________________________________________________________________________________</span>
</div>
<div class="me-email-text" style="color:#252424;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" lang="en-US">
<div style="margin-top: 24px; margin-bottom: 20px;"><span style="font-size: 24px; color:#252424">Microsoft Teams meeting</span>
</div>
<div style="margin-bottom: 20px;">
<div style="margin-top: 0px; margin-bottom: 0px; font-weight: bold"><span style="font-size: 14px; color:#252424">Join on your computer, mobile app or room device</span>
</div>
<a class="me-email-headline" style="font-size: 14px;font-family:'Segoe UI Semibold','Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;text-decoration: underline;color: #6264a7;" href="https://teams.microsoft.com/l/meetup-join/19%3ameeting_YzIyMTM4Y2MtNGVlMi00YWY2LTk0YmMtMGFjNGUzNmFjYzA5%40thread.v2/0?context=%7b%22Tid%22%3a%227005d458-45be-48ae-8140-d43da96dd17b%22%2c%22Oid%22%3a%228e6bc989-2a07-4ebb-9f55-8d213415cdd2%22%7d" target="_blank" rel="noreferrer noopener">Click
here to join the meeting</a> </div>
<div style="margin-bottom:20px; margin-top:20px">
<div style="margin-bottom:4px"><span data-tid="meeting-code" style="font-size: 14px; color:#252424;">Meeting ID:
<span style="font-size:16px; color:#252424;">273 851 737 585</span> </span><br>
<span style="font-size: 14px; color:#252424;">Passcode: </span><span style="font-size: 16px; color:#252424;">uJe2a8
</span>
<div style="font-size: 14px;"><a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" target="_blank" href="https://www.microsoft.com/en-us/microsoft-teams/download-app" rel="noreferrer noopener">Download
Teams</a> | <a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" target="_blank" href="https://www.microsoft.com/microsoft-teams/join-a-meeting" rel="noreferrer noopener">
Join on the web</a></div>
</div>
</div>
<div style="margin-bottom: 4px;">
<div style="margin-bottom: 4px;"><span style="font-size: 14px; color:#252424; font-weight: bold">Or call in (audio only)</span>
</div>
<div style="margin-bottom: 4px;"><a style="font-size: 14px;text-decoration: underline;color: #6264a7;" href="tel:+12567159946,,682047113# ">+1 256-715-9946,,682047113#</a>
<span style="font-size: 14px; color:#252424;"> United States, Huntsville </span>
</div>
</div>
<span style="font-size: 14px; color:#252424;">Phone Conference ID: </span><span style="font-size: 16px; color:#252424;">682 047 113#
</span>
<div style="margin-bottom: 20px;"><a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" target="_blank" href="https://dialin.teams.microsoft.com/19c0a492-90c6-4dcc-b305-a553fc69dc5b?id=682047113" rel="noreferrer noopener">Find
a local number</a> | <a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;" target="_blank" href="https://dialin.teams.microsoft.com/usp/pstnconferencing" rel="noreferrer noopener">
Reset PIN</a> </div>
<div style="font-size: 14px; margin-bottom: 4px;">ALERT: All meeting participants consent to, and will abide by, the terms and conditions viewable at the LEGAL link below. No ITAR/EAR content display or sharing without consent from Export Control.
</div>
<div style="margin-bottom: 24px;margin-top: 20px;"><a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" target="_blank" href="https://aka.ms/JoinTeamsMeeting" rel="noreferrer noopener">Learn
More</a> | <a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" target="_blank" href="https://nasa.sharepoint.com/sites/TeamsSupport" rel="noreferrer noopener">
Help</a> | <a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" target="_blank" href="https://teams.microsoft.com/meetingOptions/?organizerId=8e6bc989-2a07-4ebb-9f55-8d213415cdd2&tenantId=7005d458-45be-48ae-8140-d43da96dd17b&threadId=19_meeting_YzIyMTM4Y2MtNGVlMi00YWY2LTk0YmMtMGFjNGUzNmFjYzA5@thread.v2&messageId=0&language=en-US" rel="noreferrer noopener">
Meeting options</a> | <a class="me-email-link" style="font-size: 14px;text-decoration: underline;color: #6264a7;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;" target="_blank" href="https://www.nasa.gov/content/microsoft-teams-disclaimer" rel="noreferrer noopener">
Legal</a> </div>
</div>
<div style="font-size: 14px; margin-bottom: 4px;font-family:'Segoe UI','Helvetica Neue',Helvetica,Arial,sans-serif;">
</div>
<div style="font-size: 12px;"></div>
<div></div>
<div style="width:100%;height: 20px;"><span style="white-space:nowrap;color:#5F5F5F;opacity:.36;">________________________________________________________________________________</span>
</div>
</body>
</html>