<font size=2 face="sans-serif">Well, the two new recommends do not specify
any number ..... It's just a word of caution for new entrants in the field.</font>
<br>
<br><font size=2 face="sans-serif">I am still of the opinion that they
are editorials but I can go with your formal approach if really needed.</font>
<br>
<br><font size=2 face="sans-serif">Enrico</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Thomas Gannett"
<thomas.gannett@tgannett.net></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif"><Gian.Paolo.Calzolari@esa.int>,
<Enrico.Vassallo@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif"><sls-rfm@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">22/05/2017 16:31</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">RE: [Sls-rfm]
Request for publication as blue recs</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Sorry--I missed "that I will submit as separate
email."<br>
<br>
<br>
Thomas Gannett<br>
thomas.gannett@tgannett.net<br>
+1 443 472 0805<br>
<br>
<br>
-----Original Message-----<br>
From: Thomas Gannett [</font></tt><a href=mailto:thomas.gannett@tgannett.net><tt><font size=2>mailto:thomas.gannett@tgannett.net</font></tt></a><tt><font size=2>]
<br>
Sent: Monday, May 22, 2017 10:23 AM<br>
To: 'Gian.Paolo.Calzolari@esa.int'; 'Enrico.Vassallo@esa.int'<br>
Cc: 'sls-rfm@mailman.ccsds.org'<br>
Subject: RE: [Sls-rfm] Request for publication as blue recs<br>
<br>
If they were simply editorial, I would simply make the changes in the main<br>
document and record that they were made under the Document Control. However,<br>
since the changes add specifications to the normative "recommends"<br>
subsections, they really need to go to review with the next set of Red/Pink<br>
Sheets. (And I don't recall receiving a new rec 2.6.11A--did I miss<br>
something?)<br>
<br>
Thomas Gannett<br>
thomas.gannett@tgannett.net<br>
+1 443 472 0805<br>
<br>
-----Original Message-----<br>
From: Gian.Paolo.Calzolari@esa.int [</font></tt><a href=mailto:Gian.Paolo.Calzolari@esa.int><tt><font size=2>mailto:Gian.Paolo.Calzolari@esa.int</font></tt></a><tt><font size=2>]
<br>
Sent: Monday, May 22, 2017 9:49 AM<br>
To: Enrico.Vassallo@esa.int<br>
Cc: Thomas Gannett; sls-rfm@mailman.ccsds.org<br>
Subject: Re: [Sls-rfm] Request for publication as blue recs<br>
<br>
<br>
How do we deal with the editorial changes to the 10 existing rec's?<br>
<br>
Editorial corrigendum or inside the agency review package for new rec<br>
2.6.11A ?<br>
<br>
Sent from my iPhone<br>
<br>
> On 22. May 2017, at 15:21, Enrico.Vassallo@esa.int wrote:<br>
><br>
> Dear Tom,<br>
><br>
> please find attached the revised 401.0-P-26.1 recommendations <br>
> following disposition of agency review's RIDs. As you may notice,
the <br>
> only RID received dealt with rec. 2.5.6B.<br>
><br>
> However, we have also fixed two editorial problems with rec. 2.4.18.
<br>
> The changes in both recs are shown with rev marks and yellow highlighting.<br>
><br>
> Disposition of the RID is also attached.<br>
><br>
> Additionally, I am adding a batch of 10 existing recommendations on
<br>
> Transponder Turnaround Frequency Ratios that need to be editorially
<br>
> aligned with themselves and with the new rec 2.6.11A that I will <br>
> submit as separate email.<br>
><br>
> As usual, I am confident that Gian Paolo will issue the relevant <br>
> resolution.<br>
><br>
> Best Regards, Enrico<br>
><br>
><br>
> This message and any attachments are intended for the use of the <br>
> addressee<br>
or addressees only.<br>
> The unauthorised disclosure, use, dissemination or copying (either
in <br>
> whole<br>
or in part) of its<br>
> content is not permitted.<br>
> If you received this message in error, please notify the sender and
<br>
> delete<br>
it from your system.<br>
> Emails can be altered and their integrity cannot be guaranteed by
the<br>
sender.<br>
><br>
> Please consider the environment before printing this email.<br>
><br>
><br>
> _______________________________________________<br>
> SLS-RFM mailing list<br>
> SLS-RFM@mailman.ccsds.org<br>
> </font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-rfm"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-rfm</font></tt></a><tt><font size=2><br>
> <401x0p26x1_after RID dispos.doc><br>
> <Disposition of RIDs to 401x0p26x1.docx> <TTFR Recs Editorials.docx><br>
<br>
<br>
This message and any attachments are intended for the use of the addressee<br>
or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole<br>
or in part) of its content is not permitted.<br>
If you received this message in error, please notify the sender and delete<br>
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the<br>
sender.<br>
<br>
Please consider the environment before printing this email.<br>
<br>
<br>
<br>
This message and any attachments are intended for the use of the addressee
or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete
it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
<br>
<br>
</font></tt>
<br>
<br><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>