<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</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>Dear CESG Colleagues,</div>
<div><br>
</div>
<div>Attached is the latest version of the CCSDS Org & Procs doc () I got from Tom, with the agreed set of changes. I used Track Changes to signal what has changed, which were only edits to the agreed sections. Please be aware that what look like formatting
changes appear in other parts of the document, but the actual text changes were only done to these sections:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>2.3.1.1: brief explicit statement about CMC use of consensus, refers to 5.1.2</div>
<div>2.3.2.2.b: some text CESG procedures removed and put into Sec 5.1.2</div>
<div><span class="Apple-style-span">2.3.3.2: </span> brief explicit statement<span class="Apple-style-span"> about consensus added to WG procedures</span>, refers to 5.1.2</div>
<div>5.1.2: text from CESG moved here. Reference to Annex G added.</div>
<div>5.3.1: changes to voting text to reflect that CMC & CESG both vote</div>
<div>5.3.5.4.4.1: agreed changes to voting / disapproval text</div>
<div>Annex G: new annex with description of consensus process and flow chart (2 page version)</div>
<div><br>
</div>
</blockquote>
<div>Please review so we can get closure on this and send it to the CMC. </div>
<div><br>
</div>
<div>I will now begin review of the SANA Yellow Book.</div>
<div><br>
</div>
<div>Cheers, Peter</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; 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>Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, October 23, 2014 6:09 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>><br>
<span style="font-weight:bold">Subject: </span>Re: Changes to CCSDS Org & Proc Doc<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>Peter:<br>
<br>
I do not believe any change is needed with respect to SANA. All document-related SANA requirements reside in the Publications Manual, and the applicable specifications there are:<br>
<br>
<quote><br>
<b>3.5.2.2.2<x-tab> </x-tab> Security, SANA, and Patent Considerations Annex<br>
<br>
3.5.2.2.2.1<x-tab> </x-tab>General<br>
<br>
3.5.2.2.2.1.1<x-tab> </x-tab></b>Recommended Standards, Recommended Practices, and Experimental Specifications shall contain an informative annex that addresses one or more of the following considerations:<br>
<br>
-<x-tab> </x-tab>Security;<br>
<br>
-<x-tab> </x-tab>Space Assigned Numbers Authority (SANA);<br>
<br>
-<x-tab> </x-tab>Patents.<br>
<br>
<b>3.5.2.2.2.1.2<x-tab> </x-tab></b>The title of the annex shall reflect its content; i.e.; if the annex contains only security considerations, then its title shall be 'Security Considerations'.<br>
<br>
. . .<br>
<br>
<b>3.5.2.2.2.3<x-tab> </x-tab>SANA Considerations<br>
<br>
</b>Recommended Standards shall contain SANA considerations as defined in reference [1].<br>
</quote><br>
<br>
So all that needs to be done with the Org&Procs book is addition of the concensus material. Since you can lay your hands on that more quickly than I, it's probably easiest/quickest if you update the book, which I attach.<br>
<br>
Tom<br>
<br>
<br>
At 07:51 PM 10/21/2014, Shames, Peter M (312B) wrote:<br>
<blockquote type="cite" class="cite" cite="">Tom,<br>
<br>
My notes from the CESG meeting say that you and I will produce the needed draft updates to the CCSDS Org & Proc YB. These are for:
<ul>
<li>Consensus </li><li>SANA </li></ul>
Do you want to do them based on what we discussed? Do you want to send me the .doc file for me to hack (track changes)? These changes are modest enough that I should not be able to screw too much up. But it's your call.<br>
<br>
Peter<br>
<br>
<br>
From: <Shames>, Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov"> peter.m.shames@jpl.nasa.gov</a>><br>
Date: Monday, October 20, 2014 8:06 AM<br>
To: Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov"> peter.m.shames@jpl.nasa.gov</a>><br>
Subject: FW: [CESG] Topic for telecon: Defining SANA registries on Orange book request<br>
<br>
<dl><dd>CESG Notes </dd><dd>Create update of YB for Consensus changes, send to CESG first </dd><dd>Consider adding a sentence to the CCSDS Proc YB </dd><dd>Do not allow any OB to use or modify an existing SANA registry </dd><dd>Do not allow an OB to create it's own registries in SANA, they may be private
</dd><dd>Need to revise SANA YB to recognize the appropriate policies, review (all) updates with Tom & Marc
</dd><dd>Need a SANA policy change to deal with colliding or overlaping registries </dd><dd>Look at SLS reply to SEA from Gippo, review conditions by COB Tues, 21 Oct
<ul>
</ul>
<ul>
</ul>
</dd></dl>
</blockquote>
</div>
</div>
</blockquote>
</span>
</body>
</html>