<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=utf-8">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-GB;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
--></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" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Dear SLP WG,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Forwarding the results of Matt Cosby’s action item on to all – please see the Word attachment.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Greg Kazz<o:p></o:p></p>
<p class="MsoNormal">Chairman SLP WG<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Greg,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I have attached the review of the ‘Givens’. Each one characterised and should be enough to close the RID with the re-wording from John.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Cheers and speak on Monday.<o:p></o:p></p>
<p class="MsoNormal">Matt.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal"><b>Matthew Cosby</b><o:p></o:p></p>
<p class="MsoNormal"><b>Chief Technology Officer </b><o:p></o:p></p>
<p class="MsoNormal"><b>Goonhilly Earth Station Ltd</b><o:p></o:p></p>
<p class="MsoNormal"><b><img width="801" height="87" style="width:8.3437in;height:.9062in" id="_x0000_i1029" src="cid:image001.jpg@01D74895.38F423D0"></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Kazz, Greg J (US 312B) <greg.j.kazz@jpl.nasa.gov>
<br>
<b>Sent:</b> 27 April 2021 15:40<br>
<b>To:</b> Matthew Cosby <Matt.Cosby@Goonhilly.org>; Gian.Paolo.Calzolari@esa.int<br>
<b>Cc:</b> Moury Gilles <Gilles.Moury@cnes.fr><br>
<b>Subject:</b> Re: [EXTERNAL] RE: NASA RIDs against USLP Version 2 Blue Book 732.1-B<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Matt,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Brilliant. Thanks for doing the check as well.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Aloha,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Matthew Cosby <<a href="mailto:Matt.Cosby@Goonhilly.org">Matt.Cosby@Goonhilly.org</a>><br>
<b>Date: </b>Friday, April 23, 2021 at 12:25 AM<br>
<b>To: </b>"Kazz, Greg J (US 312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>, "<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>" <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<b>Cc: </b>Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><br>
<b>Subject: </b>RE: [EXTERNAL] RE: NASA RIDs against USLP Version 2 Blue Book 732.1-B</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">Greg,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">So this is how I had read John’s RID – and happy to go with his suggestion of :<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">FROM:<o:p></o:p></p>
<p class="MsoNormal">“no valid TFDF is available for transmission at release time for a given VC”<o:p></o:p></p>
<p class="MsoNormal">TO:<o:p></o:p></p>
<p class="MsoNormal">“none of the VCs on the physical channel has a TFDF available for transmission at release time.”<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I also agree about the other “Givens” in the doc, that this is now moot. However for completeness, I will just review the other list of “Givens” so we have a paper trail that shows that no other changes are required in respect to this is
RID. It should not take me too long and I can be attached to the RID disposition before the meeting.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Cheers, <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Matt.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal"><b>Matthew Cosby</b><o:p></o:p></p>
<p class="MsoNormal"><b>Chief Technology Officer </b><o:p></o:p></p>
<p class="MsoNormal"><b>Goonhilly Earth Station Ltd</b><o:p></o:p></p>
<p class="MsoNormal"><b><img border="0" width="801" height="87" style="width:8.3437in;height:.9062in" id="Picture_x0020_1" src="cid:image002.jpg@01D74895.38F423D0"></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>
<br>
<b>Sent:</b> 22 April 2021 22:43<br>
<b>To:</b> Matthew Cosby <<a href="mailto:Matt.Cosby@Goonhilly.org">Matt.Cosby@Goonhilly.org</a>>;
<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a><br>
<b>Cc:</b> Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><br>
<b>Subject:</b> Re: [EXTERNAL] RE: NASA RIDs against USLP Version 2 Blue Book 732.1-B<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Below is a rewrite of NASA RID #12, by John after we talked about the issue below. I believe he has it right now. Also I don’t think it will cause any other changes in this book or other books.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">John’s email to me follows:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">Let me try to clarify what I was trying to address with the RID on 4.1.4.1.5 (a). “A given VC” is sort of like an algebraic expression in which “a given VC” is the independent variable. I.e.,
“for a given VC” is another way of saying “for VC X”. So the sentence “ For a given VC there is a managed parameter that specifies the truncated frame length” states the assertion that for each of VC 1, VC 2, … there is an associated truncated frame length.
“For a given VC” is a single-VC criterion.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">However, in 4.1.4.1.5 (a) - “no valid TFDF is available for transmission at release time for a given VC.” - this single-VC implication is incorrect. If it were implemented as stated, the logic
would be:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.25in"><span style="font-size:14.0pt;color:#1F4E79">-</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">Look
at the queue for <u>a</u> VC (presumably the VC that is next up in the multiplexing scheme)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.25in"><span style="font-size:14.0pt;color:#1F4E79">-</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">Does
it have a frame ready to send?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#1F4E79">n</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">If
yes, send that frame</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#1F4E79">n</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">If
no, send an OID frame</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.25in"><span style="font-size:14.0pt;color:#1F4E79">-</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">Loop</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">But this is wrong. It makes the sending of OID frames based solely on whether the current (“given”) VC has a frame or not, regardless of whether other VCs have frames available.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">The correct logic should be something like</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.25in"><span style="font-size:14.0pt;color:#1F4E79">-</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">Look
at the queue for the VC (again, presumably the VC that is next up in the multiplexing scheme)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.25in"><span style="font-size:14.0pt;color:#1F4E79">-</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79"> Does
it have a frame ready to send?</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#1F4E79">n</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">If
yes, send that frame</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in;text-indent:-.25in"><span style="font-size:14.0pt;font-family:Wingdings;color:#1F4E79">n</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">If
no, see if there are any other VCs that have a frame ready to send (presumably checked in mux scheme order)</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in"><span style="font-size:14.0pt;color:#1F4E79">--- If another VC has a frame ready, send that frame</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.25in"><span style="font-size:14.0pt;color:#1F4E79">--- Only if no VC has a frame available at release time, send an OID frame</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.25in"><span style="font-size:14.0pt;color:#1F4E79">-</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F4E79"> </span><span style="font-size:14.0pt;color:#1F4E79">Loop</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">By proposing to substitute “any VC” for “a given VC”, I was attempting to say that only if none of the VCs on the physical channel have a frame ready at transmission should an OID frame be released.
Obviously my intent was not clear, and I apologize for chewing up so many people’s time thinking about it.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">In light of that, I think a better rephrasing of my RID recommendation is:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">FROM:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">“no valid TFDF is available for transmission at release time for a given VC”</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">TO:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">“none of the VCs on the physical channel has a TFDF available for transmission at release time.”</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">Regarding the question about changing the other instances of “a given” to “any”, hopefully my clarification above will render that a moot point. But in any case I did a search for instances of
the phrase “a given”. I think that those other uses are okay as they are, in that they refer to single instances of the things being addressed, e.g., “a given MC” and “a given service instance”. In response to Gian Paolo’s concern about opening up the issue
for the other books that use the “a given XYZ” construct, I would advise not changing those other instances in the USLP or other books (unless, of course, it turns out that it is being used inappropriately (as it is in 4.1.4.1.5) to refer to something that
is beyond the scope of a single instance of a thing – i.e., the “given” thing).</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:#1F4E79">I hope this helps clarify the intent and scope of the RID, and again I apologize for any confusion that it created.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Greg<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Matthew Cosby <<a href="mailto:Matt.Cosby@Goonhilly.org">Matt.Cosby@Goonhilly.org</a>><br>
<b>Date: </b>Thursday, April 22, 2021 at 3:26 AM<br>
<b>To: </b>"<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>" <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<b>Cc: </b>Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>>, "Kazz, Greg J (US 312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br>
<b>Subject: </b>[EXTERNAL] RE: NASA RIDs against USLP Version 2 Blue Book 732.1-B</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">You are right – a quick search has revealed about 8 – 10 times that would fit in this category (assuming that this is what John meant). It would not be too difficult to propose
a solution to each one. Given is mentioned 24 times – the majority used acceptability.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Happy to collate these and propose a solution – I will do so if people agree this is what John was referring to.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Cheers, Matt.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Matthew Cosby</b><o:p></o:p></p>
<p class="MsoNormal"><b>Chief Technology Officer </b><o:p></o:p></p>
<p class="MsoNormal"><b>Goonhilly Earth Station Ltd</b><o:p></o:p></p>
<p class="MsoNormal"><b><img border="0" width="801" height="87" style="width:8.3437in;height:.9062in" id="Picture_x0020_7" src="cid:image003.jpg@01D74895.38F423D0"></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a> <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>
<br>
<b>Sent:</b> 22 April 2021 09:46<br>
<b>To:</b> Matthew Cosby <<a href="mailto:Matt.Cosby@Goonhilly.org">Matt.Cosby@Goonhilly.org</a>><br>
<b>Cc:</b> Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>>; Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br>
<b>Subject:</b> RE: NASA RIDs against USLP Version 2 Blue Book 732.1-B<o:p></o:p></p>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Matt,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> I did not open the RIDs yet, however I guess the formulation
</span> "For a given VC”<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> is widely used within SDLP books.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">If we change it in a place, we should try to be consistent also in other docs.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Just to give a warning :o)</span>
<br>
<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>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Matthew Cosby" <<a href="mailto:Matt.Cosby@Goonhilly.org">Matt.Cosby@Goonhilly.org</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Kazz, Greg J (US 312B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>, "<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>"
<<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>, "Moury Gilles" <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">22-04-21 10:22</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">RE: NASA RIDs against USLP Version 2 Blue Book 732.1-B</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<p style="margin:0in">All,<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">I will review the others in detail during the day – but addressing RID-12.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">I can see what John is referring to with not liking the statement : "For a given VC”. He has interpreted that “given” is a state with in the protocol. When actually the word “given” in this sentence means “any”. I would be happy to
suggest to John, that we replace “given” with “any”.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Cheers, Matt.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b>Matthew Cosby</b><o:p></o:p></p>
<p style="margin:0in"><b>Chief Technology Officer </b><o:p></o:p></p>
<p style="margin:0in"><b>Goonhilly Earth Station Ltd</b><o:p></o:p></p>
<p style="margin:0in"><img border="0" width="801" height="87" style="width:8.3437in;height:.9062in" id="Picture_x0020_2" src="cid:image003.jpg@01D74895.38F423D0"><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b>From:</b> Kazz, Greg J (US 312B) <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>>
<b><br>
Sent:</b> 21 April 2021 23:54<b><br>
To:</b> <a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>; Matthew Cosby <<a href="mailto:Matt.Cosby@Goonhilly.org">Matt.Cosby@Goonhilly.org</a>>; Moury Gilles <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>><b><br>
Subject:</b> NASA RIDs against USLP Version 2 Blue Book 732.1-B<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Dear G.P./Gilles/Matt,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Attached are the NASA RIDs that I have received to date. They mostly come from John Pietrus and one RID from Craig Biggerstaff.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">I believe they all have merit and as a preliminary proposal I have written my proposed concurrence into the last column of the spreadsheet. Of course, all of these RIDs need to be discussed and agreed to
at our SLP virtual meeting on May 17-18. The only RID I found controversial is RID 12. I do not understand very well the fine distinction that John is attempting to make in the word changes he is advocating.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Please let me know your thoughts about these RIDs.
</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">If you have received any ESA or CNES RIDs I would appreciate it, if you could share them with me as well.</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Thanks and best regards,</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt">Greg</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p style="margin:0in">Greg Kazz<o:p></o:p></p>
<p style="margin:0in">Principal Engineer<o:p></o:p></p>
<p style="margin:0in">Technical Group Supervisor,<o:p></o:p></p>
<p style="margin:0in">PSSE/EEISE/PPSE (312B)<o:p></o:p></p>
<p style="margin:0in">Jet Propulsion Laboratory<o:p></o:p></p>
<p style="margin:0in">4800 Oak Grove Dr., M/S 301-490<o:p></o:p></p>
<p style="margin:0in">Pasadena, CA 91109<o:p></o:p></p>
<p style="margin:0in">1+(818)393 6529(voice)<o:p></o:p></p>
<p style="margin:0in">1+(818)393 6871(fax)<o:p></o:p></p>
<p style="margin:0in">email: <a href="mailto:greg.j.kazz@jpl.nasa.gov"><span style="color:#0082BF">greg.j.kazz@jpl.nasa.gov</span></a>
<o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</body>
</html>