<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: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Is there a reason people don’t like:</div>
<div><br>
</div>
<div>TFDZ: 3 bits</div>
<div>Reserved: 5 bits</div>
<div>ProtoID: 8 bits</div>
<div>First Header pointer: 16 bits</div>
<div><br>
</div>
<div>?</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></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>Gian Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<span style="font-weight:bold">Date: </span>Friday, February 5, 2016 at 8:03 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>" <<a href="mailto:Tomaso.deCola@dlr.de">Tomaso.deCola@dlr.de</a>><br>
<span style="font-weight:bold">Cc: </span>Edward Greenberg <<a href="mailto:edward.greenberg@jpl.nasa.gov">edward.greenberg@jpl.nasa.gov</a>>, Greg Kazz <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>, "Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>>,
Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, "<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>" <<a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>RE: [Sls-slp] CCSDS definition of Protocol IDs<br>
</div>
<div><br>
</div>
<span style="color: rgb(0, 0, 0); font-family: monospace; font-size: small; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;">I
think you raised an important point: compactness vs. processing complexity. I think that however we should see this trade-off looking at the entire Transfer frame data field header, which contains the protocol field (s). At the moment it is 32-bit aligned
(TFDZ:3 bits, ProtoID: 5 bits, Extended ProtoID: 8 bits, first header pointer: 16 bits) for a total of 32 bits, which is something always desirable. If we reduce the protocol IDs from a total of 13 down to 8, the header becomes of 27 bits. If we reduce from
13 to 6, it becomes 25 bits.<span class="Apple-converted-space"> </span></span><br style="color: rgb(0, 0, 0); font-family: monospace; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
</span>
</body>
</html>