<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=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@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:0in;
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dear CESG members,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Approval conditions against the CESG poll CESG-P-2016-06-001 Approval to release CCSDS 732.1-R-1, Unified Space Link Protocol (Red Book, Issue 1) for CCSDS Agency review have been addressed to the satisfaction of the AD who voted to approve with conditions. The Secretariat will therefore proceed with the CMC poll.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><span style='color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'>Thomas Gannett<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>thomas.gannett@tgannett.net<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>+1 443 472 0805<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Shames, Peter M (312B) [mailto:peter.m.shames@jpl.nasa.gov] <br><b>Sent:</b> Wednesday, July 27, 2016 1:47 PM<br><b>To:</b> Gian.Paolo.Calzolari@esa.int; CCSDS CESG --<br><b>Cc:</b> Tom Gannett; Massimo.Bertinelli@esa.int; Kazz, Greg J (312B)<br><b>Subject:</b> Re: [CESG] SLS Area Dispositions for SEA Condition on CESG Polls CESG-P-2016-06-001 & CESG-P-2016-05-004<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Gippo, Gilles, et al,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In the interest of moving these documents into agency review I am going to accept the current resolution of conditions and agree to sending these out to the agencies.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>That said, I do want to go on the record that I am concerned that what appears to be a very strict adherence to a policy of “we can’t change that, it’s in older documents” is a sure fire way to stifle creativity and forward progress. If the Internet took that approach we would not have IP v6, nor the van Jacobsen performance mods to TCP, nor SMTP with MIME types, nor HTTPS and HTML5, nor … The same sort of progression can be seen in Ethernet evolution (was 1 Mbps, now over 1 Gbps), for USB (was 1.1 Mbps, now on version 3 and 480 Mbps). There is a very long list of improvements that other standards organizations have been able to make that have moved them ahead in performance and features. But we seem to be getting continual push back that things can’t evolve, nor descriptions be clarified, because of some choices made 15 (or more) years ago. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I will point out that if we had used this same approach 15 years ago when those SLP docs had a major revision that we never would have had the improved SLP protocols docs we now have; we would have stuck with the original versions from the 1980’s. I do believe that we must be careful about what we change, so as to preserve backward compatibility and not break existing infrastructure (see Architecture Principles, “A4 MINIMIZE DISRUPTIONS Statement: Minimize Disruptions to Existing Standards and Installed Systems”). But note that this does not say “don’t change anything”. It does say “… there will also be situations where unforecasted mission requirements or operating modes will mandate consideration of otherwise disruptive approaches.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>When we are developing major new capabilities, such as USLP surely represents, we should be more bold just because we are defining something that is explicitly intended to move us into the future. And, because this is nowhere implemented, just because it is brand new, we should have no fear of breaking anything because there is no existing infrastructure that supports this protocol nor the data rates it is capable of sustaining.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Regards, Peter<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-family:"Calibri","sans-serif";color:black'>From: </span></b><span style='font-family:"Calibri","sans-serif";color:black'>CESG <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>> on behalf of Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br><b>Date: </b>Wednesday, July 27, 2016 at 3:37 AM<br><b>To: </b>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br><b>Cc: </b>Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>, "<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>" <<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>>, Greg Kazz <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br><b>Subject: </b>[CESG] SLS Area Dispositions for SEA Condition on CESG Polls CESG-P-2016-06-001 & CESG-P-2016-05-004<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt' id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Dear Peter,</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> please find in the attached file the SLS Area Dispositions for SEA Condition on CESG Poll CESG-P-2016-06-001.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The SLS Area Dispositions for SEA Condition on CESG Poll CESG-P-2016-05-004 are already available as per </span><a href="https://mailman.ccsds.org/pipermail/cesg/2016-July/000991.html"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>https://mailman.ccsds.org/pipermail/cesg/2016-July/000991.html</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> .</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>All SLS Area dispositions have been coordinated with the relevant WG Chairs.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SLS Area AD and DAD are confident we can proceed for both CMC Polls with acceptance of the dispositions by SEA Area as soon as the CCSDS Editors implements the agreed changes.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Best regards</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Gian Paolo & Gilles</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SLS AD and DAD</span> <o:p></o:p></p><pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre><pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre><pre>content is not permitted.<o:p></o:p></pre><pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre><pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Please consider the environment before printing this email.<o:p></o:p></pre></div></div></blockquote></div></body></html>