<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Segoe UI","sans-serif";}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:Consolas;}
p.HTMLVorformatiert, li.HTMLVorformatiert, div.HTMLVorformatiert
{mso-style-name:"HTML Vorformatiert";
mso-style-link:"HTML Vorformatiert Zchn";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.SprechblasentextZchn
{mso-style-name:"Sprechblasentext Zchn";
mso-style-priority:99;
mso-style-link:Sprechblasentext;
font-family:"Tahoma","sans-serif";}
p.Sprechblasentext, li.Sprechblasentext, div.Sprechblasentext
{mso-style-name:Sprechblasentext;
mso-style-link:"Sprechblasentext Zchn";
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle29
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 56.7pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></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="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Keith,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Just two comments from my side. In the Red book of the CCSDS BP, in Annex A, DTN BP is referred to be the specification given in RFC 5050, on top of which the
red book provides extensions/adaptations. If now, we have a pointer to a “DTN BP” in another book stating something different I think this can be a source of confusion. Further to this, I don’t know if it is really necessary to specify DTN BP meaning that
the DTN refer to the architecture and BP to the protocol, since BP or LTP automatically point to the DTN architecture.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Concerning the fact that CFDP can work on top of LTP, this is certainly an option. But not existing any LTP UT for CFDP at the moment, I would keep it open
instead of stating that CFDP can work over LTP.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Tomaso<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">————————————————————————</span><span style="color:#1F497D">
<br>
</span><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Deutsches Zentrum für Luft- und Raumfahrt</span></b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray"> (DLR)</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">German Aerospace Center</span><span style="color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany</span><span style="color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Tomaso de Cola, Ph.D.</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<br>
</span><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:dimgray">Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 |</span><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="mailto:tomaso.decola@dlr.de"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif"">tomaso.decola@dlr.de</span></a></span><span lang="DE" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><a href="http://www.dlr.de/kn/institut/abteilungen/san"><span lang="DE">http://www.dlr.de/kn/institut/abteilungen/san</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
<span lang="DE"><o:p></o:p></span></span></p>
</div>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> sis-dtn-bounces@mailman.ccsds.org [mailto:sis-dtn-bounces@mailman.ccsds.org]
<b>On Behalf Of </b>Scott, Keith L.<br>
<b>Sent:</b> Tuesday, November 25, 2014 13:39<br>
<b>To:</b> Peinado, Osvaldo Luis; Gian.Paolo.Calzolari@esa.int<br>
<b>Cc:</b> sis-dtn@mailman.ccsds.org; sis-mia@mailman.ccsds.org<br>
<b>Subject:</b> [Sis-dtn] RE: Quick comments: [CESG] SIS Resolution to submit Voice and Audio Communications Red Book for processing and CESG Polling for Agency Review (SIS-R-2014-11-003)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">I’m pulling in the MIA and DTN lists here.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#44546A">Ø</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">My responses to some of Gian Paolo’s comments inline below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"> --keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a> [<a href="mailto:osvaldo.peinado@dlr.de">mailto:osvaldo.peinado@dlr.de</a>]
<br>
<b>Sent:</b> Tuesday, November 25, 2014 5:36 AM<br>
<b>To:</b> <a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>; Scott, Keith L.<br>
<b>Cc:</b> <a href="mailto:tomg@aiaa.org">tomg@aiaa.org</a><br>
<b>Subject:</b> AW: Quick comments: [CESG] SIS Resolution to submit Voice and Audio Communications Red Book for processing and CESG Polling for Agency Review (SIS-R-2014-11-003)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Gian Paolo,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you very much for your inputs. The DTN part was written by the DTN group, but I will check it with them.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks also for all the others recommendations, I will fix/check all of them.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best Regards<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Osvaldo<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a> [<a href="mailto:Gian.Paolo.Calzolari@esa.int">mailto:Gian.Paolo.Calzolari@esa.int</a>]
<br>
<b>Gesendet:</b> Montag, 24. November 2014 17:30<br>
<b>An:</b> Scott, Keith L.; Peinado, Osvaldo Luis<br>
<b>Cc:</b> Tom Gannett<br>
<b>Betreff:</b> Quick comments: [CESG] SIS Resolution to submit Voice and Audio Communications Red Book for processing and CESG Polling for Agency Review (SIS-R-2014-11-003)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Keith, Osvaldo
</span><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif""> here below a few preliminary quick comments.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">You may want to consider them before CESG poll starts.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Regards</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Gian Paolo</span>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">In section 2.1 I would reword this sentence from:</span>
<br>
CFDP supports two classes. Each of the classes can be supported over the DTN Bundle Protocol (reference [19]) and DTN Licklider Transport Protocol (LTP) (reference [18]).
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">To e.g.:</span> <br>
CFDP supports two classes. Each of the classes can be supported over the DTN Bundle Protocol (reference [19]). DTN may eventually operate over the Licklider Transport Protocol (LTP) (reference [18]).
<span style="color:#44546A"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#44546A">Ø</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">I think the question here is how we think voice might be layered (specifically, if we think voice might run DIRECTLY over LTP or not). From the fact that CFDP seems to be
the important bit here, we might say something like:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.5in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#44546A">§</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">CFDP supports the following classes, both of which can be supported by the DTN Bundle Protocol (reference [19]).<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#44546A">Ø</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">And leave it to the mission designer to decide exactly what CFDP runs over (BP, Encapsulation, …)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Is the terminology <</span>DTN Bundle Protocol
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">>, <</span>DTN Licklider Transport Protocol<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">> correct?</span>
<span style="color:#44546A"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.25in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#44546A">Ø</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">I hadn’t really thought about it too much, but I think this terminology is pretty good (though the reference to LTP was removed in my suggested text above). DTN is the label
for ‘the stack’ and Bundle Protocol identifies the particular protocol. We could say something like ‘Bundle Protocol for CCSDS’ (the name of the BP for CCSDS Book) but I think the context, coupled with the reference, make it clear what we’re talking about.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Clause 4.2.2.2.2 </span>
Advanced Orbiting Systems (AOS) Virtual Channel Access (VCA), AOS [24] Bitstream, and AOS [24] Insert services should be used to transmit voice and audio data.
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">I think that this clause should be reworded to be clearer to e.g.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">The following services of AOS [24] should be used to transmit voice and audio data: Virtual Channell Access (VCA), Bitstream, and Insert.</span>
<span style="color:#44546A"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.25in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#44546A">Ø</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">I might have said something like<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.75in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:"Courier New";color:#44546A">o</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">Voice and audio data should be transferred using
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:red">(one or more of ???)
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">the following services: Advanced Orbiting Systems (AOS, [24]) Virtual Channel Access (VCA), AOS Bitstream Service, and AOS Insert.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.75in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:"Courier New";color:#44546A">o</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">Not sure about ‘using one of the following’ vs. ‘using the following’ – if we’re thinking these types of transmissions are typically single-hop then ‘one of…’ will work.
If a single voice transmission might use multiple transmission mechanisms then ‘using the following’ (or using one or more of the following) is probably better.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Note also that the VCA Service is also offered by Telemetry (CCSDS 132.0-B) and Telecommand (CCSDS 232.0-B), therefore a user willing to use VCA should not be limited to AOS.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Clause 4.3.5 </span>Files may be transmitted by any general file transmission protocol, e.g., via CFDP Class 1 or Class 2 (reference [17]), over CCSDS links or over DTN protocol (references [18]
and [19]). <br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">I think here reference 18 should be removed as CFDP would never interface LTP directly.</span>
<span style="color:#44546A"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.25in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#44546A">Ø</span><span style="font-size:7.0pt;color:#44546A">
</span><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">Why not? Once could do CFDP unreliable over LTP Red, for example, in order to write a very small and simple (if non-class-1-supporting) CFDP implementation. I don’t feel
too strongly about this one way or the other, especially since this text is in the ‘example’ clause of the sentence and is therefore (the way I would read the document) not normative. It might be better even to separate the example into a NOTE (NOTE: File
transfer may for example use CFDP ….) We also don’t have a CFDP over LTP UT layer spec.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Clause 4.5.5 </span>Frequencies and channelization: If a direct space link to spacecraft is available or if the MCC communicates using a space link to other MCC, the CCSDS standard frequency (reference
[20][21][22]) should be used. <br>
The 3 references mentioned there are the 3 books for Proximity-1. Only [20] addresses the physical layer for "proximity space-to-space links". Since MCC is mentioned I guess that Proximity-1 is not the only candidate.
<br>
Please clarify which scenarios are really addressed by this clause and coordinate with Enrico Vassalo (SLS-RFM chair) for the applicable standards.
<br>
Moreover, is it correct to address frequencies in normative clause without identifying the complete stack from the voice/audio application down to the physical layer?
<br>
Note that if you want to consider the complete stack there are at least Encapsulation Service, TM, TC, AOS to be cited.
<br>
<br>
In 5.1 the sentence <In cases involving landers, rovers, orbiting constellations, and orbiting relays, proximity links should be considered (references [20], [21], [22].) > is correct but how is this visible to the voice/audio application that is recommended
to run over IPoC, DTN or File Xfer? Can the voice/audio application be really aware of the details of the layers immediately below those of the expected services (i.e. IPoC, DTN, CFDP, etc.)?
<br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"<a href="mailto:Secretariat@mailman.ccsds.org">Secretariat@mailman.ccsds.org</a>" <<a href="mailto:Secretariat@mailman.ccsds.org">Secretariat@mailman.ccsds.org</a>>,
"Thomas Gannett" <<a href="mailto:tomg@aiaa.org">tomg@aiaa.org</a>>, </span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"<a href="mailto:sis-mia@mailman.ccsds.org">sis-mia@mailman.ccsds.org</a>" <<a href="mailto:sis-mia@mailman.ccsds.org">sis-mia@mailman.ccsds.org</a>>,
"CCSDS Engineering Steering Group - CESG Exec \(<a href="mailto:cesg@mailman.ccsds.org\">cesg@mailman.ccsds.org\</a>)" <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>, "Osvaldo Peinado \(<a href="mailto:osvaldo.peinado@dlr.de\">osvaldo.peinado@dlr.de\</a>)"
<<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a>></span> <br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">24/11/2014 14:54</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">[CESG] SIS Resolution to submit Voice and Audio Communications Red Book for processing and CESG
Polling for Agency Review (SIS-R-2014-11-003)</span> <br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif""><a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a></span>
<o:p></o:p></p>
<div style="margin-left:.5in">
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
<br>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E">CCSDS Secretariat,</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E">The SIS Area, on the recommendation of the Voice and Audio Communications Working Group, resolves (via SIS resolution SIS-R-2014-11-003) to submit the attached Red Book for document
processing and CESG polling to release the document for agency review.</span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E">I believe that Cynthia Sachs-Bustos should have the sources for the drawing in the book. If not then we can provide them.</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> Very respectfully,</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> --keith</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<b><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Dr. Keith Scott</span></b><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">
Office: +1.703.983.6547</span> <br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Chief Engineer, J86A Fax: +1.703.983.7142</span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Communications Network Engineering & Analysis Email:
<a href="mailto:kscott@mitre.org">kscott@mitre.org</a></span> <br>
<a href="http://www.mitre.org/"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">The MITRE Corporation</span></a><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">
M/S H300</span> <br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">7515 Colshire Drive</span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">McLean, VA 22102</span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F"> </span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Area Director,</span><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#37605E">
</span><a href="http://www.ccsds.org/"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">CCSDS</span></a><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#37605E">
</span><a href="http://cwe.ccsds.org/sis/default.aspx"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">Space Internetworking Services</span></a>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">MITRE self-signs its own certificates. Information about the MITRE PKI Certificate Chain is available from
</span><a href="http://www.mitre.org/tech/mii/pki/"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">http://www.mitre.org/tech/mii/pki/</span></a>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#37605E"> </span>
<br>
<b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif""> Keith Scott [</span><a href="mailto:keithlscott@gmail.com"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">mailto:keithlscott@gmail.com</span></a><span style="font-size:10.0pt;font-family:"Calibri","sans-serif"">]
<b><br>
Sent:</b> Wednesday, November 19, 2014 6:44 PM<b><br>
To:</b> Scott, Keith L.<b><br>
Subject:</b> Fwd: Voice and audio communication book for CESG review</span> <br>
<br>
---------- Forwarded message ----------<br>
From: <<a href="mailto:osvaldo.peinado@dlr.de">osvaldo.peinado@dlr.de</a>><br>
Date: Nov 19, 2014 5:29 AM<br>
Subject: Voice and audio communication book for CESG review<br>
To: <<a href="mailto:tomg@aiaa.org">tomg@aiaa.org</a>><br>
Cc: <<a href="mailto:aid@mcc.rsa.ru">aid@mcc.rsa.ru</a>>, <<a href="mailto:keithlscott@gmail.com">keithlscott@gmail.com</a>>, <<a href="mailto:cynthia@sachs-bustos.com">cynthia@sachs-bustos.com</a>><br>
<br>
Hi Tom <br>
As we talk with Keith, here is the book ready for your magic. <br>
We have several review cycles with Cynthia before the meeting in London and I got today all the final inputs from the WG member.
<br>
Thanks a lot for your support <br>
Best Regards <br>
Osvaldo <br>
<br>
<br>
<br>
<b><span style="font-family:"Arial","sans-serif"">Dr. Osvaldo Peinado</span></b> <br>
<span style="font-family:"Arial","sans-serif"">Ground Operations Manager</span> <br>
<span style="font-family:"Arial","sans-serif"">German Space Operations Center (GSOC)<br>
Tel: </span><a href="tel:%2B49%208153%2028%203010" target="_blank"><span style="font-family:"Arial","sans-serif"">+49 8153 28 3010</span></a><span style="font-family:"Arial","sans-serif""><br>
Fax: </span><a href="tel:%2B49%208153%2028%201456" target="_blank"><span style="font-family:"Arial","sans-serif"">+49 8153 28 1456</span></a>
<br>
<span style="font-family:"Arial","sans-serif"">Mobile: </span><a href="tel:%2B491729410099" target="_blank"><span style="font-family:"Arial","sans-serif"">+491729410099</span></a>
<br>
<span style="font-family:"Arial","sans-serif"">German Aerospace Center (DLR)<br>
Oberpfaffenhofen<br>
82234 Wessling<br>
Germany</span> <br>
[attachment "CCSDS 766.2-R-0-november.doc" deleted by Gian Paolo Calzolari/esoc/ESA]
<tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>CESG mailing list</tt><br>
<tt><a href="mailto:CESG@mailman.ccsds.org">CESG@mailman.ccsds.org</a></tt><br>
</span><a href="http://mailman.ccsds.org/mailman/listinfo/cesg"><tt><span style="font-size:10.0pt">http://mailman.ccsds.org/mailman/listinfo/cesg</span></tt></a><o:p></o:p></p>
<pre style="margin-left:.5in">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre style="margin-left:.5in">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre style="margin-left:.5in">content is not permitted.<o:p></o:p></pre>
<pre style="margin-left:.5in">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre style="margin-left:.5in">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
<pre style="margin-left:.5in">Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</div>
</body>
</html>