<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=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
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";
color:black;}
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;
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{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:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1989505681;
mso-list-type:hybrid;
mso-list-template-ids:1223969814 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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 bgcolor="white" 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">Reading this exchange it strikes me that would could even take a different approach (devil’s advocate) and excise all of the introductory material – I say this
in gest to be sure, but there is supposed to be the CCSDS “terse” style in place and if in fact all of this is addressed in the SLE model, and/or other green book material then, really should this not come down to saying something like “this is the ROCF service
formal specification – please read the reference model to understand the ROCF use cases..” ?<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">In any case, I tend to agree with Wolfgang that the CLCW is not the only use case and that constrained bandwidth is an important factor to note. And if that
can be succinctly stated in one sentence or maybe two I am okay with that. Adding multiple paragraphs strikes me as compounding the problem and not really helping the reader – again, the normative recommendations should be just that – no more, no less.
<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">I would also have to wonder about the other SLE books and then I also keep in mind that despite the perceived shortcoming in introductory material SLE has nonetheless
be successfully implemented. Are these “improved” introductions worth the cost? Will this affect SLE adoption and/or upgrades to existing implementations?
<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">So in summary:<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">Can fairly short introductory material be provided consistently for all the SLE books (if needed) without any significant effort? If so, let’s put it in. If
not, let’s not expend our scant resources on something that has no significant return on investment.
<o:p></o:p></span></p>
<p class="MsoListParagraph"><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"><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">-Erik<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>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> Wolfgang Hell [mailto:Wolfgang_._Hell@t-online.de]
<br>
<b>Sent:</b> Thursday, May 21, 2015 9:29 AM<br>
<b>To:</b> Shames, Peter M (312B); Margherita.di.Giulio@esa.int; Barkley, Erik J (3970)<br>
<b>Cc:</b> css-csts@mailman.ccsds.org; Holger.Dreihahn@esa.int; John Pietras (pietras@gst.com); CCSDS Secretariat (thomas.gannett@tgannett.net)<br>
<b>Subject:</b> Re: An update to the ROCF SLE recommendation that can be done by the scretariat<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Peter,<br>
<br>
thanks for your prompt reply. in general terms we are on the same page and I was just trying to backup your position. In more specific terms I wanted to convey the message that imho just adding the sentence<br>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">"TC defines and uses the CLCW, which is carried in the TM (or AOS) OCF field for use in COP re-transmission operations. The ROCF service is used to provide this CLCW to the user so that these
re-transmission operations may be implemented in the user MOC."</span><span style="font-size:10.5pt">
</span> <br>
<br>
won't cure the problem. As I tried to explain in my previous email, talking of the CLCW as the only OCF use case might be very confusing to the reader the latest when he/she gets to all the ROCF-START options. My second concern is that without addressing the
potential terrestrial comms bandwidth limitations and the potential operational low latency requirements for the OCF delivery it is difficult to understand why ROCF is needed on top of RAF and RCF. All I'm suggesting is that these aspects are taken into account
when we create the modest introductory material. This should put the reader on the right track from the beginning.<br>
<br>
Best regards,<br>
Wolfgang <br>
<br>
<br>
<br>
Am 21.05.2015 um 16:46 schrieb Shames, Peter M (312B):<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Thanks Wolfgang. I was not in any way suggesting that we add voluminous Green Book materials, nor that we slight any of the key features, such as those you mentioned in the OCF section.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What I was doing was proposing that we add a modest paragraph or two (or even three) to the introductory sections of these documents. In many cases, as in OCF, that sort of simple "here is what this does and why it is important" intro
was missing. Right now the ROCF devotes page after page of introductory "Green Book material" to definitions of the service itself, to the SLE reference model, service management, return frame and OCF production and provisioning, scheduling, underlying services,
buffering, security aspects, etc, etc. These introductory materials are the first 47 pages of the spec.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I think we can do beter by our users, without being unnecessarily duplicative by including too much Green Book material in a Blue Book.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt"><o:p> </o:p></span></p>
</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:11.0pt;font-family:"Calibri",sans-serif">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Wolfgang Hell <</span><a href="mailto:Wolfgang_._Hell@t-online.de"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Wolfgang_._Hell@t-online.de</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Date: </b>Thursday, May 21, 2015 at 3:21 AM<br>
<b>To: </b>"</span><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Margherita.di.Giulio@esa.int</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">" <</span><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Margherita.di.Giulio@esa.int</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>,
Erik Barkley <</span><a href="mailto:Erik.J.Barkley@jpl.nasa.gov"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Erik.J.Barkley@jpl.nasa.gov</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Cc: </b>CSTS-WG <</span><a href="mailto:css-csts@mailman.ccsds.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">css-csts@mailman.ccsds.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>, "</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">"
<</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Holger.Dreihahn@esa.int</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>, Peter Shames <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>,
"John Pietras (</span><a href="mailto:pietras@gst.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">pietras@gst.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">)" <</span><a href="mailto:pietras@gst.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">pietras@gst.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>,
Tom Gannett <</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">thomas.gannett@tgannett.net</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Subject: </b>Re: An update to the ROCF SLE recommendation that can be done by the scretariat<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt"><o:p> </o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt">Dear All,<br>
<br>
I'm in favor of promoting whenever possible the use of CCSDS standards and if we can do something that helps the reader and therefore potential "customer" to digest the sometimes fairly complex material, I won't object. However, given that the SLE services
extend the space link by providing a standard mechanism to access space link data, in my mind it is implied that understanding SLE services requires familiarity with the space link protocols which define the data that SLE services deal with. In fact, all SLE
books have been written with that understanding in mind. I completely agree with Peter's analysis that the ROCF book contains all relevant references to the space link protocols and as such is complete. I also completely agree that in CCSDS we deal with other
relevant standards by reference rather than inclusion. I'm sure we all agree that SLE books are not the right place to present Green Book type material related to space link protocols.<br>
<br>
In the spirit of helping the reader I do not mind adding a sentence or two regarding why the ROCF service got "invented". However, my concern regarding the sentence proposed by Peter is that it might create the impression that the only purpose of the OCF is
carrying the CLCW. While undoubtedly in most cases this is what the OCF is used for, other OCF types exist as well and are covered in detail in the ROCF-START operation. Therefore, if we add any material explaining what the OCF is, we shall not limit it to
the CLCW case. Even if we add some explanation of what the OCF is, the reader may still fail to grasp why we cared to "invent" the ROCF service, given that via RAF and/or RCF we can get the frames that contain the OCFs of interest as well. We should add a
few words regarding the potential need for low-latency delivery of the OCFs also in cases where the total space link data rate (significantly) exceeds the terrestrial communications bandwidth.<br>
<br>
Best regards,<br>
Wolfgang <br>
<br>
Am 20.05.2015 um 12:18 schrieb </span><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-size:10.5pt">Margherita.di.Giulio@esa.int</span></a><span style="font-size:10.5pt">:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Erik and All,</span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I managed to read the sequence of e-mails on this subject only today, as I am on mission for the whole week, I have no problem with instructing Secretariat about the introduction of the suggested
sentence. However, one should first look into the R-OCF Recommendation and think of the appropriate place where to put it. Also, one may want to check if analogous sentences need to be introduced in other SLE Recommendations.</span><span style="font-size:10.5pt"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I will have time to look into this only next week ( and I will coordinate with Wolfgang).
</span><span style="font-size:10.5pt"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">I do not know how far the editor is with the Pink Books ( may be Tom can tell us), If there is still a chance to introduce this change, say by the end of next week, then it is all right.
Otherwise, we can keep this change in mind as a RID to be issued during the agency Review, as somebody suggested in one of the pervious e-mails.</span><span style="font-size:10.5pt"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Kind regards,<br>
Margherita</span><span style="font-size:10.5pt"> <br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif">-------------------------------------------------------------<br>
Margherita di Giulio<br>
Ground Station Back-end Section (HSO-GIB)<br>
European Space Agency ESA/ESOC<br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49-6151-902779<br>
e-mail: </span><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Margherita.di.Giulio@esa.int</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
</span><span style="font-size:10.5pt"><br>
<br>
<br>
<br>
</span><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">"Barkley, Erik J (3970)"
</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><erik.j.barkley@jpl.nasa.gov></span></a><span style="font-size:10.5pt"><br>
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Margherita.di.Giulio@esa.int"</span></a><a href="mailto:Margherita.di.Giulio@esa.int"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><Margherita.di.Giulio@esa.int></span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">,
</span><a href="mailto:Wolfgang_._Hell@t-online.de"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Wolfgang_._Hell@t-online.de"</span></a><a href="mailto:Wolfgang_._Hell@t-online.de"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><Wolfgang_._Hell@t-online.de></span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">,
</span><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Holger.Dreihahn@esa.int"</span></a><a href="mailto:Holger.Dreihahn@esa.int"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><Holger.Dreihahn@esa.int></span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">,
</span><span style="font-size:10.5pt"><br>
</span><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">"Shames, Peter M (312B)"
</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><peter.m.shames@jpl.nasa.gov></span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">, "CCSDS Secretariat (</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">thomas.gannett@tgannett.net</span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">)"
</span><a href="mailto:thomas.gannett@tgannett.net"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><thomas.gannett@tgannett.net></span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">, "John Pietras (</span><a href="mailto:pietras@gst.com"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">pietras@gst.com</span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">)"
</span><a href="mailto:pietras@gst.com"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><pietras@gst.com></span></a><span style="font-size:7.5pt;font-family:"Arial",sans-serif">,
</span><a href="mailto:css-csts@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"css-csts@mailman.ccsds.org"</span></a><a href="mailto:css-csts@mailman.ccsds.org"><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><css-csts@mailman.ccsds.org></span></a><span style="font-size:10.5pt"><br>
</span><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">13/05/2015 21:03</span><span style="font-size:10.5pt"><br>
</span><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">An update to the ROCF SLE recommendation that can be done by the scretariat</span><span style="font-size:10.5pt"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:10.5pt">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:10.5pt"><br>
<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Margherita, Wolfgang, Holger,</span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">With regard to the SLE books about to have pink sheet reviews, a question (please see previous email today) arose about adding an editorial sentence to the SLE blue books. Peter has suggested
the following addition to the ROCF blue book:</span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">"TC defines and uses the CLCW, which is carried in the TM (or AOS) OCF field for use in COP re-transmission operations. The ROCF service is used to provide this CLCW to the user so that
these re-transmission operations may be implemented in the user MOC."</span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">We can issue specific instructions to the secretariat as to exactly where to add this type of sentence. It seems reasonable to me. I would appreciate your comments on doing this, and if
you concur I see no reason why this could not be included as part of the pink sheets going out for agency review.
</span><span style="font-size:10.5pt"><br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Best regards,</span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif">-Erik</span><span style="font-size:10.5pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><span style="font-size:10.5pt">
<o:p></o:p></span></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="font-size:10.5pt"><o:p> </o:p></span></p>
</div>
</div>
</blockquote>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>