<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>Gippo,</div>
<div><br>
</div>
<div>I do not believe that we got to this topic in today's CESG telecon. We have not, to my knowledge, ever had to deal with this kind of question before, I.e. The creation of a registry or changes to a registry by an Orange Book. We had to deal with something
similar back when SCPS was published as an Orange Book, but at that point we did not have a SANA and the "registry" was just the published documents.</div>
<div><br>
</div>
<div>I general I think we should consider this sort of request, but I think we need to do an engineering analysis in the general case to see if it is acceptable. My reasoning is that if we have a lot of Orange Books (and we seem to be creating more of them
now) we could use up valuable "ID" real estate quickly, as in Protocol ID and Reserved APIDs. The Extended Protocol Ids are not so much of an issue.</div>
<div><br>
</div>
<div>In the normal SANA course of things each registry has an associated policy and means of managing the registry entries. Given the limited number space it does not seem reasonable to me to allow an experimental spec to use up one of the limited number of
protocol identifiers defined in 135.0-B-4, table 7-7a,, but it does seem acceptable to use one of the extended protocol identifiers defined in 133.1-b-2. </div>
<div><br>
</div>
<div>Furthermore, the policy on both of these registries is "CCSDSBlue", which means that only a Blue Book update is acceptable. Perhaps that policy should be re-stated for the Extended Protocol Identifiers (<a href="http://sanaregistry.org/r/extended_protocol_id/extended_protocol_id.html">http://sanaregistry.org/r/extended_protocol_id/extended_protocol_id.html</a>),
to allow such more liberal assignments, but surely not for the protocol identifiers (<a href="http://sanaregistry.org/r/protocol_id/protocol_id.html">http://sanaregistry.org/r/protocol_id/protocol_id.html</a>).</div>
<div><br>
</div>
<div>In any event, I think that this is something that the SLS should take up and bring to the SSG (and/or CESG) for further discussion after the technical options and implications have been deliberated.</div>
<div><br>
</div>
<div>Regards, Peter</div>
<div><br>
</div>
<div><br>
</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>Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<span style="font-weight:bold">Date: </span>Monday, September 1, 2014 12:07 AM<br>
<span style="font-weight:bold">To: </span>Nestor Peccia <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>><br>
<span style="font-weight:bold">Cc: </span>Tom Gannett <<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>><br>
<span style="font-weight:bold">Subject: </span>[CESG] Topic for telecon: Defining SANA registries on Orange book request<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><font size="2" face="sans-serif">Nestor, I would like to add a topic for next telecon.</font><br>
<font size="2" face="sans-serif">As you know CESG is voting for the pblication of an Orange Book on Erasure Codes.</font><br>
<font size="2" face="sans-serif">This draft book states:</font> <br>
<font size="2" face="Arial">This document requests that SANA perform the following actions:<br>
1. define a new reserved APID...<br>
2. define a new Protocol Identifier...<br>
3, define a new Extended Protocol Identifier...</font>
<p><br>
<font size="2" face="sans-serif">In general I think a (published) book should not contain those requests but simply reference the registries that should be created "as part of the approval process.</font><br>
<font size="2" face="sans-serif">However in this case we are speaking about an Orange Book.
</font><br>
<font size="2" face="sans-serif">Is it acceptable to create registries for Orange Books?</font><br>
<br>
<font size="2" face="sans-serif">Regards</font> <br>
<br>
<font size="2" face="sans-serif">Gian Paolo</font> <br>
</p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</pre>
</div>
</div>
</blockquote>
</span>
</body>
</html>