[Sls-rfm] Request for publication as blue recs

[Enrico.Vassallo at esa.int]

Well, the two new recommends do not specify any number ..... It's just a 
word of caution for new entrants in the field.

I am still of the opinion that they are editorials but I can go with your 
formal approach if really needed.

Enrico



From:   "Thomas Gannett" <thomas.gannett at tgannett.net>
To:     <Gian.Paolo.Calzolari at esa.int>, <Enrico.Vassallo at esa.int>
Cc:     <sls-rfm at mailman.ccsds.org>
Date:   22/05/2017 16:31
Subject:        RE: [Sls-rfm] Request for publication as blue recs



Sorry--I missed "that I will submit as separate email."


Thomas Gannett
thomas.gannett at tgannett.net
+1 443 472 0805


-----Original Message-----
From: Thomas Gannett [mailto:thomas.gannett at tgannett.net] 
Sent: Monday, May 22, 2017 10:23 AM
To: 'Gian.Paolo.Calzolari at esa.int'; 'Enrico.Vassallo at esa.int'
Cc: 'sls-rfm at mailman.ccsds.org'
Subject: RE: [Sls-rfm] Request for publication as blue recs

If they were simply editorial, I would simply make the changes in the main
document and record that they were made under the Document Control. 
However,
since the changes add specifications to the normative "recommends"
subsections, they really need to go to review with the next set of 
Red/Pink
Sheets. (And I don't recall receiving a new rec 2.6.11A--did I miss
something?)

Thomas Gannett
thomas.gannett at tgannett.net
+1 443 472 0805

-----Original Message-----
From: Gian.Paolo.Calzolari at esa.int [mailto:Gian.Paolo.Calzolari at esa.int] 
Sent: Monday, May 22, 2017 9:49 AM
To: Enrico.Vassallo at esa.int
Cc: Thomas Gannett; sls-rfm at mailman.ccsds.org
Subject: Re: [Sls-rfm] Request for publication as blue recs


How do we deal with the editorial changes to the 10 existing rec's?

Editorial corrigendum or inside the agency review package for new rec
2.6.11A ?

Sent from my iPhone

> On 22. May 2017, at 15:21, Enrico.Vassallo at esa.int wrote:
>
> Dear Tom,
>
> please find attached the revised 401.0-P-26.1 recommendations 
> following disposition of agency review's RIDs. As you may notice, the 
> only RID received dealt with rec. 2.5.6B.
>
> However, we have also fixed two editorial problems with rec. 2.4.18. 
> The changes in both recs are shown with rev marks and yellow 
highlighting.
>
> Disposition of the RID is also attached.
>
> Additionally, I am adding a batch of 10 existing recommendations on 
> Transponder Turnaround Frequency Ratios that need to be editorially 
> aligned with themselves and with the new rec 2.6.11A that I will 
> submit as separate email.
>
> As usual, I am confident that Gian Paolo will issue the relevant 
> resolution.
>
> Best Regards, Enrico
>
>
> 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.
>
>
> _______________________________________________
> SLS-RFM mailing list
> SLS-RFM at mailman.ccsds.org
> https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-rfm
> <401x0p26x1_after RID dispos.doc>
> <Disposition of RIDs to 401x0p26x1.docx> <TTFR Recs Editorials.docx>


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.



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.





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.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sls-rfm/attachments/20170522/1e9230f9/attachment.html>