<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:st1="urn:schemas-microsoft-com:office:smarttags" 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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</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;}
tt
{font-family:"Courier New";}
span.EmailStyle18
{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'>All,<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'>For discussion at the SLS-SLP WG
meeting on Friday AM April 24 at <st1:place w:st="on"><st1:City w:st="on">Colorado
Springs</st1:City>, <st1:State w:st="on">CO</st1:State></st1:place><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'>best regards,<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'> <st1:PersonName
w:st="on">Gian.Paolo.Calzolari@esa.int</st1:PersonName> [mailto:<st1:PersonName
w:st="on">Gian.Paolo.Calzolari@esa.int</st1:PersonName>] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Sunday, March 22, 2009 11:15
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Kazz, Greg J<br>
<b><span style='font-weight:bold'>Cc:</span></b> Chris.Taylor@esa.int; <st1:PersonName
w:st="on">Jean-Luc.Gerner@esa.int</st1:PersonName>; <st1:PersonName w:st="on">Marjorie
de Lande Long</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> ESA input for: [SLS-SLP]
JAXA RIDs on AOS + TM Pink Sheets</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 style='margin-bottom:12.0pt'><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'>
the following responses to Jaxa RIDs have been discussed
with Chris and Marjorie.</span></font> <br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>Please
consider these responses as ESA input for the discussion of the RIDs.</span></font>
<br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>Ciao</span></font>
<br>
<br>
<font size=2 face=sans-serif><span style='font-size:10.0pt;font-family:sans-serif'>Gian
Paolo</span></font> <br>
<font size=2 face="Courier New"><span style='font-size:10.0pt;font-family:"Courier New"'><br>
<tt><font face="Courier New">========================================================================</font></tt><br>
<br>
<tt><font face="Courier New">RID JAXA-RPA830-01</font></tt><br>
<tt><font face="Courier New">1) An Idle Packet carries no useful data: This
applies to an Idle Space</font></tt><br>
<tt><font face="Courier New">Packet and to an Idle (or Fill) Encapsulation
Packet (see below).</font></tt><br>
<tt><font face="Courier New">However, the AOS Insert Service uses the Insert
Field of every Transfer</font></tt><br>
<tt><font face="Courier New">Frame on the Physical Channel, including the Idle
Frames. Therefore, an</font></tt><br>
<tt><font face="Courier New">Idle Frame can carry useful data so the name
"Idle Frame" is not fully</font></tt><br>
<tt><font face="Courier New">appropriate. The Pink Sheets provide the new name
"OID Frame".</font></tt><br>
<tt><font face="Courier New">2) The term "OID Frame" is being
introduced to AOS Space Data Link</font></tt><br>
<tt><font face="Courier New">Protocol for consistency with the existing term
used for the TM Space</font></tt><br>
<tt><font face="Courier New">Data Link Protocol. See section 4.1.2.7.6.5
of CCSDS 132.0-B-1,</font></tt><br>
<tt><font face="Courier New">September 2003.</font></tt><br>
<tt><font face="Courier New">3) The term "Idle Frame" was first
introduced for AOS by the publication</font></tt><br>
<tt><font face="Courier New">of the restructured Blue Book CCSDS 732.0-B-1 in
September 2003: see</font></tt><br>
<tt><font face="Courier New">Table C-1.</font></tt><br>
<tt><font face="Courier New">4) There is a related editorial error in
4.1.4.2.4.4. The Note 4 at the</font></tt><br>
<tt><font face="Courier New">end of 4.1.4.2.4.4 contains a reference to [4]
(Space Link IDs) which</font></tt><br>
<tt><font face="Courier New">should be [6] (Space Packet Protocol) for the
specification of the Idle</font></tt><br>
<tt><font face="Courier New">Packet.</font></tt><br>
<tt><font face="Courier New">5) The change to section 4.2.2.5 mentions the
"Fill Encapsulation</font></tt><br>
<tt><font face="Courier New">Packet". The Pink Sheets for the
Encapsulation Service will change the</font></tt><br>
<tt><font face="Courier New">name to "Idle Encapsulation Packet".
Therefore, 4.2.2.5 could also use</font></tt><br>
<tt><font face="Courier New">the new name.</font></tt><br>
<br>
<tt><font face="Courier New">Idle Packets</font></tt><br>
<tt><font face="Courier New">1) Idle Packet for Space Packet Protocol: In
133.0-B-1, section</font></tt><br>
<tt><font face="Courier New">4.1.2.3.3.4 says that the Secondary Header Flag
must be 0 for Idle</font></tt><br>
<tt><font face="Courier New">Packets. And a note in 4.1.3.2.1.4 says "The
Packet Secondary Header is</font></tt><br>
<tt><font face="Courier New">not allowed for Idle Packets."</font></tt><br>
<tt><font face="Courier New">2) Idle (or Fill) Encapsulation Packet: The data
area (Encapsulated Data</font></tt><br>
<tt><font face="Courier New">Field) contains idle data. The Encapsulation
Packet Header has no</font></tt><br>
<tt><font face="Courier New">optional secondary fields for carrying extra data.</font></tt><br>
<br>
<br>
<tt><font face="Courier New">RID JAXA-RPA830-02</font></tt><br>
<tt><font face="Courier New">1) The RID says the descriptive phrase is
unnecessary. But the phrase</font></tt><br>
<tt><font face="Courier New">is in a Note, so there is no formal duplication.
The phrase could help</font></tt><br>
<tt><font face="Courier New">the reader understand the meaning of
"OID" and it provides a reference</font></tt><br>
<tt><font face="Courier New">to the location of the formal specification of the
OID Frame.</font></tt><br>
<tt><font face="Courier New">2) It would be an improvement if the text was
changed from "see 4.1.4"</font></tt><br>
<tt><font face="Courier New">to "see 4.1.4.1.5".</font></tt><br>
<br>
<br>
<tt><font face="Courier New">RID JAXA-RPA830-03</font></tt><br>
<tt><font face="Courier New">1) Section 4.1.4.2.4.2 does not define the term
"idle pattern". It uses</font></tt><br>
<tt><font face="Courier New">the term "idle pattern" in order to
define the meaning of "Idle Data". </font></tt><br>
<tt><font face="Courier New">2) Apart from the "OID" name change, the
new Note 3 is the only change</font></tt><br>
<tt><font face="Courier New">introduced to section 4.1.4.1.5. Note 3 does
not alter the</font></tt><br>
<tt><font face="Courier New">specification of "Idle Data", but adds a
suggestion that it should</font></tt><br>
<tt><font face="Courier New">have a random pattern, and it explains why.
This does not conflict</font></tt><br>
<tt><font face="Courier New">with the other details specified for the Idle
Data, in 4.1.4.1.5 or</font></tt><br>
<tt><font face="Courier New">elsewhere in 732.0-B. </font></tt><br>
<br>
<br>
<tt><font face="Courier New">RID JAXA-RPA830-04</font></tt><br>
<tt><font face="Courier New">1) The name change in TM and AOS protocols
(132.0-B and 732.0-B) from</font></tt><br>
<tt><font face="Courier New">"Packet Service" to "Virtual
Channel Packet Service" is consistent with</font></tt><br>
<tt><font face="Courier New">the "Virtual Channel Packet Service" of
the TC protocol (232.0-B). The</font></tt><br>
<tt><font face="Courier New">TM and AOS protocols do not use MAPs, so their
renamed Virtual Channel</font></tt><br>
<tt><font face="Courier New">Packet Services place the packets into frames.</font></tt><br>
<tt><font face="Courier New">2) In 732.0-B (AOS), it might be helpful to remove
GMAP ID, MAP ID, MAP,</font></tt><br>
<tt><font face="Courier New">MAPA and MAPP from the list of acronyms in Annex
A, because they are not</font></tt><br>
<tt><font face="Courier New">used for the AOS protocol.</font></tt><br>
<tt><font face="Courier New">3) In 132.0-B (TM), it might be helpful to remove
GMAP ID from the list</font></tt><br>
<tt><font face="Courier New">of acronyms in Annex A, because it is not used for
the TM protocol.</font></tt><br>
<br>
<br>
<tt><font face="Courier New">RID JAXA-RPA830-05</font></tt><br>
<tt><font face="Courier New">The RID says it could be confusing to continue to
use the term "Packet</font></tt><br>
<tt><font face="Courier New">Service" in AOS and TM protocols (there is a
note about this at the end</font></tt><br>
<tt><font face="Courier New">of Table 2-1). The intention of the Pink
Sheets has been to replace all</font></tt><br>
<tt><font face="Courier New">instances of "Packet Service" in the
text of 132.0-B and 732.0-B to</font></tt><br>
<tt><font face="Courier New">"Virtual Channel Packet Service" or
"VCP Service". However, there are</font></tt><br>
<tt><font face="Courier New">some Figures containing the words "Packet
Service", and these have not</font></tt><br>
<tt><font face="Courier New">been changed. The note was added to Table 2-1 as
explanation. </font></tt><br>
<tt><font face="Courier New">Therefore, it would be a good idea to ask the
CCSDS Editor to replace</font></tt><br>
<tt><font face="Courier New">"Packet Service" with "VCP
Service" in the Figures, and to remove the</font></tt><br>
<tt><font face="Courier New">note from Table 2-1. [This suggested change
applies to 132.0-B and to</font></tt><br>
<tt><font face="Courier New">732.0-B.]</font></tt><br>
<br>
<tt><font face="Courier New">===========================================================================</font></tt><br>
<br>
<br>
</span></font><o:p></o:p></p>
</div>
</body>
</html>