<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="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
tt
{font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</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 lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>G.P.,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>But a Space Packet can contain a Secondary
Header, which could contain useful data as well. So in that sense, OID Packet
also makes sense. In other words, discarding an “Idle Packet” can have a
drawback or unintended consequence. CCSDS needs to use consistent terminology
across the board and I think that is what this JAXA rid is pointing out. I am
looking forward to Marjorie’s responses to those rids as well.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>thanks,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Greg<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Gian.Paolo.Calzolari@esa.int
[mailto:Gian.Paolo.Calzolari@esa.int] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, March 03, 2009 1:26
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Kazz, Greg J<br>
<b><span style='font-weight:bold'>Cc:</span></b> Greenberg, Edward;
gilles.moury@cnes.fr; Jean-Luc.Gerner@esa.int; sls-slp@mailman.ccsds.org;
sls-slp-bounces@mailman.ccsds.org; Takahiro Yamada<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [Sls-slp] JAXA RID
against OID Frame</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
</span></font><font size=2 face=sans-serif><span style='font-size:10.0pt;
font-family:sans-serif'>Greg,</span></font> <br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>
In Packet Telemetry the term "idle frame" was
deprecated because it is posible that frame is not completely idle (opposite to
the idle packet).</span></font> <br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>An
idle frame can in fact contain a valid CLCW or a valid secondary header.</span></font>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>In
such a sense:</span></font> <br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>1)
discarding an idle frame may imply loosing valid data while</span></font>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>2)
discarding an idle packet has no drawback.</span></font> <br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>In
CCSDS 732.0-B-2 I can read:</span></font> <br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>--------------------------------------------</span></font>
<o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<b><span style='font-weight:bold'>4.1.2.3.2 </span></b>The Virtual Channel
Identifier shall be used to identify the Virtual Channel. <br>
NOTES <br>
........... <br>
3 A Transfer Frame on the ‘Idle’ Virtual Channel may not contain any valid user
data within its Transfer Frame Data Field, but it must contain the Insert Zone
if the Insert Service is supported. <br>
</span></font><font size=2 face=sans-serif><span style='font-size:10.0pt;
font-family:sans-serif'>--------------------------------------------</span></font>
<o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<b><span style='font-weight:bold'>4.1.4.1.5 </span></b>In the case where at
release time </span></font><font size=2 face=sans-serif><span style='font-size:
10.0pt;font-family:sans-serif'>.....................</span></font> <br>
NOTES <br>
1 Transfer Frames containing Idle Data in their
Data Fields are sent to maintain synchronization at the receiver and also to
transmit data in the Transfer Frame Insert Zone when there is no Data Field to
send. <br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>--------------------------------------------</span></font>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>Looking
at </span></font><b><span style='font-weight:bold'>Figure 4-1: AOS Transfer
Frame Structural Components </span></b><font size=2 face=sans-serif><span
style='font-size:10.0pt;font-family:sans-serif'>we see that an AOS frame may
contain both an Insert Zone (equivalent to the Secondary header, I understand)
and an Operational Control Field. Therefore the same reasoning of Packet TM do
apply: </span></font><br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>
An "idle frame" can contain (also) valid data
(but not in the Data Field) while an Idle Packet does not contain any valid
data</span></font> <br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>--------------------------------------------</span></font>
<o:p></o:p></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br>
<br>
</span></font><font size=2 face=sans-serif><span style='font-size:10.0pt;
font-family:sans-serif'>Marjorie is preparing a coordinate ESA position with
respect to all those RIDs.</span></font> <br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>Best
regards</span></font> <br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>Gian
Paolo</span></font> <o:p></o:p></p>
<p><font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>(*)
Clearly for the CLCW - since the same CLCW is likely to be inserted in several
frames - this would not happen if you have just one OID frame, but it could
happen in a situation (that cannot be excluded a priori) where several OID
frames are sent in sequence. In addition for the Secondary Header even a single
frame could contain important data.</span></font> <o:p></o:p></p>
<p style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><br>
<br>
<o:p></o:p></span></font></p>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><b><font size=1 face=sans-serif><span style='font-size:
7.5pt;font-family:sans-serif;font-weight:bold'>"Kazz, Greg J"
<greg.j.kazz@jpl.nasa.gov></span></font></b><font size=1
face=sans-serif><span style='font-size:7.5pt;font-family:sans-serif'> </span></font><br>
<font size=1 face=sans-serif><span style='font-size:7.5pt;font-family:sans-serif'>Sent
by: sls-slp-bounces@mailman.ccsds.org</span></font> <o:p></o:p></p>
<p><font size=1 face=sans-serif><span style='font-size:7.5pt;font-family:
sans-serif'>03-03-2009 01:23</span></font> <o:p></o:p></p>
</td>
<td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'>
<table class=MsoNormalTable border=0 cellpadding=0 width="100%"
style='width:100.0%'>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><font size=1
face=sans-serif><span style='font-size:7.5pt;font-family:sans-serif'>To</span></font><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=1 face=sans-serif><span style='font-size:
7.5pt;font-family:sans-serif'>"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int></span></font> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><font size=1
face=sans-serif><span style='font-size:7.5pt;font-family:sans-serif'>cc</span></font><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=1 face=sans-serif><span style='font-size:
7.5pt;font-family:sans-serif'>"Greenberg, Edward"
<edward.greenberg@jpl.nasa.gov>, "sls-slp@mailman.ccsds.org"
<sls-slp@mailman.ccsds.org>, "Jean-Luc.Gerner@esa.int"
<Jean-Luc.Gerner@esa.int>, Takahiro Yamada
<tyamada@pub.isas.jaxa.jp>, "gilles.moury@cnes.fr"
<gilles.moury@cnes.fr></span></font> <o:p></o:p></p>
</td>
</tr>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal align=right style='text-align:right'><font size=1
face=sans-serif><span style='font-size:7.5pt;font-family:sans-serif'>Subject</span></font><o:p></o:p></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=1 face=sans-serif><span style='font-size:
7.5pt;font-family:sans-serif'>[Sls-slp] JAXA RID against OID Frame</span></font><o:p></o:p></p>
</td>
</tr>
</table>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<table class=MsoNormalTable border=0 cellpadding=0>
<tr>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</td>
<td valign=top style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</td>
</tr>
</table>
<p class=MsoNormal><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><o:p></o:p></span></font></p>
</td>
</tr>
</table>
<p style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'><br>
<br>
<br>
</span></font><font face=Arial><span style='font-family:Arial'>G.P.</span></font>
<br>
<font face=Arial><span style='font-family:Arial'> </span></font> <br>
<font face=Arial><span style='font-family:Arial'>I think JAXA has a valid
concern in the attached RID concerning the use of the term, OID, only idle
data. I thought the purpose of using OID frame was to use the same terminology
across all CCSDS space data link documents. But as pointed out in the rid, when
we have an “Idle packet” it isn’t called an OID packet, but rather and idle
packet. So I am not sure that the term OID frame is consistent enough. Not that
I am advocating the use of the term, OID packet at all. What do you think? </span></font><br>
<font face=Arial><span style='font-family:Arial'>JAXA rid below.</span></font> <br>
<font face=Arial><span style='font-family:Arial'> </span></font> <br>
<font face=Arial><span style='font-family:Arial'>thanks,</span></font> <br>
<font face=Arial><span style='font-family:Arial'> </span></font> <br>
<font face=Arial><span style='font-family:Arial'>Greg</span></font> <br>
<font face=Arial><span style='font-family:Arial'> </span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>REVIEW
ITEM DISPOSITION (RID):</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
RED BOOK RID
INITIATION FORM</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>AGENCY
RID NUMBER: JAXA-RPA830-01</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>SUBMITTING
ORGANIZATION (Agency, Center): JAXA</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>------------------------------------------------------------------</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>REVIEWER'S
NAME: Shigeyuki Furushima</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>CODE:
Mitsubishi Electric Corporation</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>E-MAIL
ADDRESS: jaxa.ccsds@jaxa.jp</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>TELEPHONE:
29-868-2587</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>------------------------------------------------------------------</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>DOCUMENT
NUMBER: CCSDS 732.0-P-2.1 Pink Sheets, Issue
2.1</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>DOCUMENT
NAME: AOS Space Data Link Protocol</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>DATE
ISSUED: December 2008</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>PAGE
NUMBER:
PARAGRAPH NUMBER: </span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>RID
SHORT TITLE: The cange from "Idle Frame" to "OID
Frame" (1)</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>------------------------------------------------------------------</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>DESCRIPTION
OF REQUESTED CHANGE: (Use From: "..." To "..."
format)</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>It's
not necessary to change "Idele frame" to "OID Frame" .</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>The
basis of suggestion is given below.</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>1.
There is no change of definition in the recomendation.</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
Changing word without changing definition will give rise to the
confusion.</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>2.
The purpose of this pink sheet is to clearfy the meaning of "idle." </span></font><br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
However, "Idle Packet" is not changed to "OID Packet."</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
(See Page C-3, Table C-1)</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>------------------------------------------------------------------</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>CATEGORY
OF REQUESTED CHANGE:</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>
Technical Fact ___ Recommended _X_
Editorial ___</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>NOTES:</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>TECHNICAL
FACT: Major technical change of sufficient magnitude as to</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> render
the Recommendation inaccurate and unacceptable if not</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> corrected.
(Supporting analysis/rationale is essential.)</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>RECOMMENDED:
Change of a nature that would, if incorporated, produce</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> a
marked improvement in document quality and acceptance.</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>EDITORIAL:
Typographical or other factual error needing correction.</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> (This
type of change will be made without feedback to submitter.)</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>------------------------------------------------------------------</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>SUPPORTING
ANALYSIS:</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'> </span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>------------------------------------------------------------------</span></font>
<br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'>DISPOSITION:</span></font>
<br>
<font face=Arial><span style='font-family:Arial'> </span></font><tt><font
size=2 face="Courier New"><span style='font-size:10.0pt'>_______________________________________________</span></font></tt><font
size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face="Courier New">Sls-slp mailing list</font></tt><br>
<tt><font face="Courier New">Sls-slp@mailman.ccsds.org</font></tt><br>
<tt><font face="Courier New">http://mailman.ccsds.org/mailman/listinfo/sls-slp</font></tt></span></font><o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>