<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: 12px; font-family: Courier, sans-serif;">
<div>
<div><br>
</div>
<div>All:</div>
<div><br>
</div>
<div>I too consider Peter's dispositions to RIDs on the SANA RMP acceptable. </div>
<div><br>
</div>
<div>I do recommend an update to the Organization and Processes document when convenient.</div>
<div><br>
</div>
<div>Regards,</div>
<div>David Berry</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></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>"Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, February 8, 2016 at 8:47 AM<br>
<span style="font-weight:bold">To: </span>"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, David Berry <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Cc: </span>CCSDS Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>, "<a href="mailto:Secretariat@mailman.ccsds.org">Secretariat@mailman.ccsds.org</a>" <<a href="mailto:Secretariat@mailman.ccsds.org">Secretariat@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: RID processing for SANA RMP and related documents, CESG Polls closing 21 January 2016<br>
</div>
<div><br>
</div>
<div>
<div 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>Sorry, yes. I concur with Peter’s dispositions.</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>—keith</div>
<div><br>
</div>
<div>
<div>
<div id="">
<div><span class="Apple-tab-span" style="white-space: pre;"><u></u></span></div>
<div>
<div id="">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<b><span style="font-size: 9pt; color: rgb(89, 89, 89);">Dr. Keith Scott</span></b><span style="font-size: 9pt; color: rgb(89, 89, 89);"> <span class="Apple-tab-span" style="white-space: pre;">
</span>Office: +1.703.983.6547<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt; color: rgb(89, 89, 89);">Chief Engineer, J86A <span class="Apple-tab-span" style="white-space: pre;">
</span>Fax: +1.703.983.7142<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt; color: rgb(89, 89, 89);">Communications Network Engineering & Analysis<span class="Apple-tab-span" style="white-space: pre;">
</span>Email: <a href="mailto:kscott@mitre.org" style="color: rgb(149, 79, 114);">kscott@mitre.org</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt;"><a href="http://www.mitre.org/" style="color: rgb(149, 79, 114);">The MITRE Corporation</a></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt;"><span style="color: rgb(89, 89, 89);">M/S H300<o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt; color: rgb(89, 89, 89);">7515 Colshire Drive<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt; color: rgb(89, 89, 89);">McLean, VA 22102<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt; color: rgb(89, 89, 89);"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt; color: rgb(89, 89, 89);">Area Director,</span><span style="font-size: 9pt;"> <a href="http://www.ccsds.org/" style="color: rgb(149, 79, 114);">CCSDS</a> <a href="http://cwe.ccsds.org/sis/default.aspx" style="color: rgb(149, 79, 114);">Space
Internetworking Services</a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt;"> </span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
<span style="font-size: 9pt; color: rgb(89, 89, 89);">MITRE self-signs its own certificates. Information about the MITRE PKI Certificate Chain is available from <a href="http://www.mitre.org/tech/mii/pki/" style="color: rgb(149, 79, 114);">http://www.mitre.org/tech/mii/pki/</a></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri;">
</p>
<p class="inlinegraphic" style="margin: 12pt 0in; line-height: 12pt; font-size: 11pt; font-family: Calibri;">
<span style="color: windowtext; text-decoration: none;"><a href="http://www.mitre.org/"><img border="0" width="168" height="29" src="cid:28B0EC32-9137-45BD-BC66-E589BC8DC7E5" v:shapes="_x0000_i1025" type="image/png"></a></span></p>
<p class="inlinegraphic" style="margin: 12pt 0in; line-height: 12pt; font-size: 11pt; font-family: Calibri;">
<br>
</p>
</div>
</div>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 9pt; color: rgb(89, 89, 89);"></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt;"><span style="font-size: 9pt; color: rgb(89, 89, 89);"></span></p>
</div>
</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>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Monday, February 8, 2016 at 11:44 AM<br>
<span style="font-weight:bold">To: </span>"Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>>, David Berry <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Subject: </span>Re: RID processing for SANA RMP and related documents, CESG Polls closing 21 January 2016<br>
</div>
<div><br>
</div>
<div>
<div 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>Would both of you guys please signal your agreement with the dispositioning of the RIDs, as proposed, to the CESG and Secretariat?</div>
<div><br>
</div>
<div>They need to hear this directly from you.</div>
<div><br>
</div>
<div>Thanks guys, Peter</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div id=""></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>Keith Scott <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, February 8, 2016 at 8:20 AM<br>
<span style="font-weight:bold">To: </span>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, David Berry <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Subject: </span>Re: RID processing for SANA RMP and related documents, CESG Polls closing 21 January 2016<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div 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>So, the next time we crack open the O&P document, I think we should fix it (and maybe MOVE some of the requirements fro the RMP document to it). Until then, ok.</div>
<div><br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>—keith</div>
<div>
<div id=""></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>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, February 7, 2016 at 12:59 PM<br>
<span style="font-weight:bold">To: </span>David Berry <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>>, "Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: RID processing for SANA RMP and related documents, CESG Polls closing 21 January 2016<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div style="color: rgb(0, 0, 0);">Hi David (and Keith),</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">As I said in my note, your careful reading of the doc and feedback were very useful. As much as I grumbled in my head about you submitting 55 RIDS when the whole CESG only submitted 44 in total, I was glad of the care you
took, you caught stuff no one else did.</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">As for the RMP vs the Org & Proc, I do get where you guys are coming from. We all use the Org & Proc as the “Bible” for CCSDS procedures and it is extremely useful for that purpose. But if you look at it and analyze how it
is written, it is essentially in a prose style, and has little in the way of procedures (althought it does have some). It also does not have a lot of “requirements” language, but it does have some.</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">For example, look on pgs 4-1 and 4-2 for the definitions of Member Agency and Observer Agency. Look at the following language from Sec 4.1.2:</div>
<blockquote style="color: rgb(0, 0, 0); margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>
<div class="page" title="Page 35">
<div class="layoutArea">
<div class="column">
<p><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">No more than one agency representing a given country or multinational organization may participate as a Member Agency of the CCSDS. However, the number of such national or multinational
agencies that may participate as Observer Agencies is not limited. </span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div style="color: rgb(0, 0, 0);">This is easy enough to parse, and it uses the word “may”, but it is not as direct, crisp, or actionable as the following language from the RMP. I greyed out the registry specific parts to focus on the Member Agency requirements,
as stated:</div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>
<div class="page" title="Page 28">
<div class="layoutArea">
<div class="column">
<p><font color="#7f7f7f"><span style="font-size: 12pt; font-family: TimesNewRomanPS; font-weight: 700;">3.3.1.1.1
</span><span style="font-size: 12pt; font-family: TimesNewRomanPSMT;">The SANA shall implement a CCSDS Agency Registry as part of the CCSDS Organization Registry.
</span></font></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.2
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The Registration Authority for the CCSDS Agency Registry shall be the CCSDS Secretariat.
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.3
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The Registration Policy for the CCSDS Agency Registry shall be c) Change requires no engineering review, but the request must come from the CCSDS Secretariat, the HoD, or the appointed
AR for that Agency (cf. reference [5]). </span></p>
<p><font color="#7f7f7f"><span style="font-size: 12pt; font-family: TimesNewRomanPS; font-weight: 700;">3.3.1.1.4
</span><span style="font-size: 12pt; font-family: TimesNewRomanPSMT;">Each CCSDS Member Agency shall be registered in the CCSDS Agency registry. </span></font></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.5
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Each Member Agency entry in the CCSDS Agency registry shall have the role
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">‘Member Agency’.
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.6
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Each CCSDS Member Agency entry shall include agency name, abbreviation, logo, address, country, type=‘member’, HoD name, and a unique OID for the agency.
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.7
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">CCSDS Member Agency participation is subject to approval by the CMC (see subsection 4.1.1 in reference [4]).
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.8
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Each country shall have only one CCSDS Member Agency. </span></p>
<p><font color="#7f7f7f"><span style="font-size: 12pt; font-family: TimesNewRomanPS; font-weight: 700;">3.3.1.1.9
</span><span style="font-size: 12pt; font-family: TimesNewRomanPSMT;">The SANA shall provide a unique OID for each Member Agency.
</span></font></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.10
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The SANA shall update the Organization Registry by synchronizing with the CCSDS Secretariat registry.
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.11
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The SANA shall update Member Agency entries in the CCSDS Agency registry only after approval by the CCSDS Secretariat.
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.12
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">A CCSDS Member may act as the sponsor for one or more Associate Organizations in its country.
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.13
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">The CCSDS Member Agency HoD for each Member Agency shall act as the Agency CCSDS Management Council (CMC) member.
</span></p>
<p style="color: rgb(0, 0, 0);"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-weight: 700">3.3.1.1.14
</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">Only persons from CCSDS Member Agencies may be CMC members. </span></p>
</div>
</div>
</div>
</div>
</blockquote>
<div style="color: rgb(0, 0, 0);">I think that the difference between these is vast and telling. The Org & Proc tells a part of the story in more or less prose form. It offers no clarity as to who approves member agencies or manages the process. The RMP
provides discrete requirements and direct guidance as to who does what, what the procedures are, and what the approvals are. The RMP is directly actionable, the Org & Proc has to be interpreted and it is only after you consult the CCSDS website that you understand
that the Secretariat does the “official registration” and the approvals for Member Agencies.</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">From <a href="http://public.ccsds.org/participation/default.aspx">http://public.ccsds.org/participation/default.aspx</a></div>
<blockquote style="color: rgb(0, 0, 0); margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><font style="font-size: 9pt" color="#29375B"><font style="font-size: 9pt" color="#29375B">
<p class="MsoNormal"><font face="Verdana">A CCSDS <a href="http://public.ccsds.org/participation/member_agencies.aspx">
<font color="#29375B">Member Agency</font></a> is a governmental or quasi-governmental organization that fully participates in all CCSDS activities and provides a commensurate level of support. Only one agency representing a given country or multinational
organization may participate as a Member Agency of the CCSDS. A Member Agency shall adopt the Charter and must make best efforts to ensure the adherence of their agency’s internal standards to the applicable CCSDS Recommended Standards. Each CCSDS Agency
must formally appoint its delegates to the <a target="_blank" href="http://cwe.ccsds.org/">
<font color="#29375B">CCSDS technical Working Groups</font></a> which that Agency supports. Member Agencies are also invited and encouraged to submit concept or position papers for discussion within the working groups.
</font></p>
<p class="MsoNormal"><font face="Verdana">Perhaps most importantly, Member Agencies have CCSDS voting rights, which are exercised through Member Agency Representatives. Member Agency Representatives make up the CCSDS Management Council (CMC), and meet twice
a year to decide on the business and direction of the CCSDS. </font></p>
<p class="MsoNormal"><font face="Verdana">For more information about becoming a CCSDS Member Agency, please contact the
<font color="black"><a target="_blank" href="mailto:Secretariat@mailman.ccsds.org?subject=CCSDS%20Member%20Agency%20Request"><font color="#29375B">CCSDS Secretariat</font></a></font>. </font></p>
</font></font></div>
</blockquote>
<div style="color: rgb(0, 0, 0);">I think it is indisputable that the website adds info that is not in the Org & Proc doc. It is also indisputable that the requirements as to who does what to whom are vague here as well. What I did in the RMP was to assemble
all of the relevant requirements, state them in appropriate language, and cast them in a form that was actionable by the parties who have the responsibility. </div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">I do agree that we could add more material into the Org & Proc to make things clearer. Perhaps we should do that, but I note that there is often relunctance to change this doc too quickly or too much. I would support that
position if Keith and or others wanted to argue for it, but I would urge that we not stop the momentum that we now seem to have to get the RMP out the door. We need this set of procedures and policies to be in place so that everyone understands them.</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">Thanks, Peter</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<div style="color: rgb(0, 0, 0);">
<div id=""></div>
</div>
</div>
</div>
<div style="color: rgb(0, 0, 0);"><br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0);">
<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>David Berry <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Saturday, February 6, 2016 at 5:00 PM<br>
<span style="font-weight:bold">To: </span>Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Subject: </span>Re: RID processing for SANA RMP and related documents, CESG Polls closing 21 January 2016<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 12px; font-family: Courier, sans-serif;">
<div>
<div><br>
</div>
<div>Peter:</div>
<div><br>
</div>
<div>I'm OK with your dispositions, though I do still think that the requirements on the CCSDS organization are out of place (as does Keith Scott)... I just don't think anyone would look in the SANA RMP document to understand how the CCSDS is organized. But
I can live with the result.</div>
<div><br>
</div>
<div>Thanks for taking my comments into consideration... I appreciate it. Given that they arrived in your inbox after the CESG Review had started, you could have just as well ignored them entirely.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>David</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div id=""></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>"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Date: </span>Saturday, February 6, 2016 at 1:52 PM<br>
<span style="font-weight:bold">To: </span>CCSDS Secretariat <<a href="mailto:tomg@aiaa.org">tomg@aiaa.org</a>>, CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>, David Berry <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>>,
Jean-Marc Soula <<a href="mailto:Jean-Marc.Soula@cnes.fr">Jean-Marc.Soula@cnes.fr</a>><br>
<span style="font-weight:bold">Subject: </span>RID processing for SANA RMP and related documents, CESG Polls closing 21 January 2016<br>
</div>
<div><br>
</div>
<div>
<div 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>Dear CESG, CCSDS Secretariat, and other RID submitters,</div>
<div><br>
</div>
<div>Attached please find the edited versions of the three documents reviewed in CESG-P-2015-12-004, 005, and 006 and the dispositioned sets of RIDs. All of the RIDs were dispositioned and the documents updated in accordance with the RIDs that were submitted.
Archove files with the RIDs are attached, as is an archive file with the updated figures for inclusion in the RMP, CCSDS 313.1-Y-1. Aside from the required changes to the SANA registries, the only other outstanding issues are the following:</div>
<ol>
<li>The update to Fig A-1 that I have asked Erik to deal with, since the issues are directly related to registry entries that CSS is directly responsible for.</li><li>The open question of whether the RMP should be the controlling document, since it does include requirements language for guidance that is otherwise stated in prose form in the CCSDS Org and Proc, or in the CCSDS website.</li></ol>
<div>The last two documents that are attached are the RMP RIDs from David Berry (CRM) and the Glossary of terms for the RMP that he requested. David caught a lot of typos and inconsistent use of terminology. Thanks for the careful reading.</div>
<div><br>
</div>
<div>Most of the RIDs that were submitted were relatively minor technical issues, or terminology ambiguities, or editorial in nature. Resolving them has lead to a much better set of documents, and the diligence of all the reviewers who responded is really
appreciated. </div>
<div><br>
</div>
<div>Please review these RIDs and the proposed dispositions and send an acknowledgement if they are acceptable, or indicate if there are still further issues to be resolved. I’d like to do this no later than 12 Feb 2016. We need to get these documents into
the CMC review queue and then start the work to actually re-engineer the SANA (and CCSDS website)registries.</div>
<div><br>
</div>
<div>Best regards, Peter</div>
<div><br>
</div>
<div>
<div id=""></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:cesg-all-bounces@mailman.ccsds.org">cesg-all-bounces@mailman.ccsds.org</a>> on behalf of Tom Gannett <<a href="mailto:tomg@aiaa.org">tomg@aiaa.org</a>><br>
<span style="font-weight:bold">Date: </span>Friday, January 22, 2016 at 1:15 PM<br>
<span style="font-weight:bold">To: </span>CCSDS Engineering Steering Group - CESG All <<a href="mailto:cesg-all@mailman.ccsds.org">cesg-all@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>[Cesg-all] Results of CESG Polls closing 21 January 2016<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div> * * * * * * * * * * * * * * * * * * * * * * *</div>
<div><br>
</div>
<div>CESG E-Poll Identifier: CESG-P-2015-12-004 </div>
<div>Approval to publish CCSDS 313.0-Y-2, Space </div>
<div>Assigned Numbers Authority (SANA)—Role, </div>
<div>Responsibilities, Policies, and Procedures Yellow Book, Issue 2)</div>
<div>Results of CESG poll beginning 18 December 2015 and ending 21 January 2016:</div>
<div><br>
</div>
<div> Abstain: 0 (0%)</div>
<div> Approve Unconditionally: 6 (75%) (Behal, Shames, Scott, Cola, Suess, Barton)</div>
<div> Approve with Conditions: 2 (25%) (Barkley, Merri)</div>
<div> Disapprove with Comment: 0 (0%)</div>
<div><br>
</div>
<div>CONDITIONS/COMMENTS:</div>
<div><br>
</div>
<div>Erik Barkley (Approve with Conditions): 1) From: </div>
<div>"Third Generation Project" To: "Third Generation </div>
<div>Partnership Project"; Rationale: Proper defintion of acronym per 3GPP website</div>
<div><br>
</div>
<div>2) Either a) from "registration authority" to </div>
<div>"review authority" or b) revise all existing SANA </div>
<div>registry to revise existing meta data</div>
<div><br>
</div>
<div>3) From: "SANA manages only the protocol </div>
<div>registries of the CCSDS," to some phrase that is </div>
<div>consistent with registry classifications in the </div>
<div>RMP. Rationale: The RMP does not formally define </div>
<div>"protocol registries" but defines, "enterprise", </div>
<div>"global", and "local/WG" classes of registries. </div>
<div>Use of RMP classification will help to reduce ambiguity.</div>
<div><br>
</div>
<div>4) From: "Programmatic access to the SANA </div>
<div>registries shall be provided via an HTTP/REST </div>
<div>query interface." to some sentence indicating the </div>
<div>HTTP Methods to be supported. Rationale: </div>
<div>Technically, REST is not a protocol, but rather a </div>
<div>style of utilization of HTTP. I suspect that a </div>
<div>"full REST"/Restful web-services capability is </div>
<div>not truly desired, at least not at this time. </div>
<div>"Full REST type capability" allows for HTTP </div>
<div>methods such PUT and POST. I suspect that </div>
<div>probably methods such as GET are really only </div>
<div>intended here. Suggest including a reference in </div>
<div>the document to RFC 2616 and restricting access </div>
<div>to those HTTP methods to be allowed for SANA.</div>
<div><br>
</div>
<div>5) From: "Expert Groups are not intended to </div>
<div>require significant resources nor meeting rooms </div>
<div>at bi-annual meetings" to some sort of allowance </div>
<div>for at least a meeting room. Rationale: it is </div>
<div>conceivable that an expert group will have to </div>
<div>meet face-to-face to resolve an issue and agency </div>
<div>budgets/allowance outside of the bi-annual meeting cycle are typically lacking.</div>
<div><br>
</div>
<div>6) Remove Annex A. Rationale: the list of </div>
<div>candidate registries is orthogonal to the roles </div>
<div>and responsibility defined herein and is properly identified in the RMP.</div>
<div>1</div>
<div><br>
</div>
<div>Mario Merri (Approve with Conditions): I suggest </div>
<div>to add in sec 3.16 also "backup system" or </div>
<div>something similar. Backup must be a mandatory functionality.</div>
<div><br>
</div>
<div><br>
</div>
<div>Total Respondents: 8</div>
<div>No response was received from the following Area(s):</div>
<div><br>
</div>
<div>SLS</div>
<div><br>
</div>
<div>SECRETARIAT INTERPRETATION OF RESULTS: Approved with Conditions</div>
<div>PROPOSED SECRETARIAT ACTION: Generate </div>
<div>CMC poll after conditions have been addressed</div>
<div><br>
</div>
<div>* * * * * * * * * * * * * * * * * * * * * * * *</div>
<div><br>
</div>
<div>CESG E-Poll Identifier: CESG-P-2015-12-005 </div>
<div>Approval to publish CCSDS 313.1-Y-1, CCSDS SANA </div>
<div>Registry Management Policy (Yellow Book, Issue 1)</div>
<div>Results of CESG poll beginning 18 December 2015 and ending 21 January 2016:</div>
<div><br>
</div>
<div> Abstain: 0 (0%)</div>
<div> Approve Unconditionally: 4 (50%) (Shames, Cola, Suess, Barton)</div>
<div> Approve with Conditions: 4 (50%) (Barkley, Merri, Behal, Scott)</div>
<div> Disapprove with Comment: 0 (0%)</div>
<div><br>
</div>
<div>CONDITIONS/COMMENTS:</div>
<div><br>
</div>
<div>Erik Barkley (Approve with Conditions): Summary of conditions:</div>
<div><br>
</div>
<div>1) Minor editorial RIDs</div>
<div>2) Lack of purge policy</div>
<div>3) IOAG RF Assets registry appears to be </div>
<div>duplicative of Sites and Apertures registry in </div>
<div>contradiction to general policy of not having duplicative registries</div>
<div><br>
</div>
<div>Detailed conditions are in the attached file.</div>
<div><br>
</div>
<div>Mario Merri (Approve with Conditions): 3.4.6.5 </div>
<div>Refers to a "CCSDS Common Schema" registries yet </div>
<div>no further reference is made to this or an explanation of what this is.</div>
<div><br>
</div>
<div>3.4.6.5 Refers to the use of the "CCSDS </div>
<div>Terminology Registry", it should be made clear </div>
<div>that this shall only be applied to new XML Schema </div>
<div>and only where that would not break </div>
<div>compatibility, or backward compatibility, with </div>
<div>existing relevant XML Schema. For example, a new </div>
<div>revision of a MOIMS Navigation XML Schema shall </div>
<div>not be required to adopt terms if that adoption </div>
<div>would break backwards compatibility with the previous revisions of the schema.</div>
<div><br>
</div>
<div>Bigette Behal (Approve with Conditions): The </div>
<div>process to take care of "obsolete" information in </div>
<div>the cross cutting registries should be clarified </div>
<div>(For instance when the "entity" that was the </div>
<div>source/maintainer of the information is no longer active)</div>
<div><br>
</div>
<div>Keith Scott (Approve with Conditions): See attached</div>
<div><br>
</div>
<div><br>
</div>
<div>Total Respondents: 8</div>
<div>No response was received from the following Area(s):</div>
<div><br>
</div>
<div>SLS</div>
<div><br>
</div>
<div>SECRETARIAT INTERPRETATION OF RESULTS: Approved with Conditions</div>
<div>PROPOSED SECRETARIAT ACTION: Generate </div>
<div>CMC poll after conditions have been addressed</div>
<div><br>
</div>
<div>* * * * * * * * * * * * * * * * * * * * * * * *</div>
<div><br>
</div>
<div>CESG E-Poll Identifier: CESG-P-2015-12-006 </div>
<div>Approval to publish CCSDS 313.2-Y-1, Procedures </div>
<div>for SANA Registry Specification (Yellow Book, Issue 1)</div>
<div>Results of CESG poll beginning 18 December 2015 and ending 21 January 2016:</div>
<div><br>
</div>
<div> Abstain: 0 (0%)</div>
<div> Approve Unconditionally: 6 (75%) (Merri, Behal, Shames, Cola, Suess, Barton)</div>
<div> Approve with Conditions: 2 (25%) (Barkley, Scott)</div>
<div> Disapprove with Comment: 0 (0%)</div>
<div><br>
</div>
<div>CONDITIONS/COMMENTS:</div>
<div><br>
</div>
<div>Erik Barkley (Approve with Conditions): One </div>
<div>condition: From: "Registry Authority" To: "Review </div>
<div>Authority". Rationale: Registries currently </div>
<div>available via the SANA website do not list </div>
<div>Registry Authorities, but rather "Review </div>
<div>Authorities". The change makes the procedures and </div>
<div>SANA metadata extant consistent.</div>
<div><br>
</div>
<div>A suggestion: CESG verification criteria </div>
<div>guidelines for different classes of registries </div>
<div>(enterprise, global, etc.) will be useful.</div>
<div><br>
</div>
<div>A side note for CESG consideration: WGs are often </div>
<div>listed as the SANA Review authorities, however </div>
<div>WGs, are suppose to go out of existence once </div>
<div>their charter has been addressed; it might make </div>
<div>sense to indicate the area rather than the WG as </div>
<div>the review authority as Areas are constituted as standing bodies within CCSDS.</div>
<div><br>
</div>
<div>Keith Scott (Approve with Conditions): See attached.</div>
<div><br>
</div>
<div><br>
</div>
<div>Total Respondents: 8</div>
<div>No response was received from the following Area(s):</div>
<div><br>
</div>
<div>SLS</div>
<div><br>
</div>
<div>SECRETARIAT INTERPRETATION OF RESULTS: Approved with Conditions</div>
<div>PROPOSED SECRETARIAT ACTION: Generate </div>
<div>CMC poll after conditions have been addressed</div>
<div><br>
</div>
<div>* * * * * * * * * * * * * * * * * * * * * * * *</div>
<div><br>
</div>
</blockquote>
</span></div>
</div>
</span></div>
</div>
</blockquote>
</span></div>
</div>
</span></div>
</div>
</blockquote>
</span></div>
</div>
</span></div>
</div>
</span>
</body>
</html>