<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 20px; font-family: Calibri, sans-serif; ">
<div>Dear SLP,</div>
<div><br>
</div>
<div>Attached is a word document from Enrico Vassallo asking that you <span class="Apple-style-span" style="background-color: rgb(255, 255, 0);">
reply back to me</span> if you have any comments concerning the RID resolutions on the Physical Layer Prox-1 Blue book in 5-year review that impacts any of the Prox-1 Data Link Layer Blue book.</div>
<div><br>
</div>
<div>My review has yielded the following remarks:</div>
<div><br>
</div>
<div>Item 1: Prefer the second option. Rationale – prefer to keep titles of sections, diagrams, tables, etc as short as possible and not be verbose. Therefore clarifying upfront in the definitions section that the word "forward" is an abreviation in these documents
for "forward link" and visa versa for "return" should provide ample guidance to the user.</div>
<div><br>
</div>
<div>Item 2: Agree with Enrico's RID resolution here.</div>
<div><br>
</div>
<div>Item 3: Agree with the RID resolution, but change the phrase "being provided" to "provided". Rationale: It is verbose.</div>
<div><br>
</div>
<div>Item 4: Agree with the RID resolution, but remember I am a "bloody colonist".</div>
<div><br>
</div>
<div>Item 5: Agree with the RID resolution, but also change the word, "communications" to "communication" as in the previous RID. Let's be consistent.</div>
<div><br>
</div>
<div>Item 6: Agree with Enrico's RID resolution and text here.</div>
<div><br>
</div>
<div>Items 7,8,9, 10: Not part of SLP purview – no comment.</div>
<div><br>
</div>
<div>Looking forward to your views!</div>
<div><br>
</div>
<div>Greg Kazz</div>
<div>Chairman CCSDS SLS-SLP WG</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>" <<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, September 6, 2012 5:21 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>" <<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</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>>, "Kazz, Greg J (313B)" <<a href="mailto:greg.j.kazz@jpl.nasa.gov">greg.j.kazz@jpl.nasa.gov</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:sls-rfm@mailman.ccsds.org">sls-rfm@mailman.ccsds.org</a>" <<a href="mailto:sls-rfm@mailman.ccsds.org">sls-rfm@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>CCSDS Review of CCSDS 211.1-P-3.1, Proximity-1 Space Link Protocol--Physical Layer - RFM WG RID Disposition<br>
</div>
<div><br>
</div>
<div>
<div><font size="2" face="sans-serif">Dear All,</font> <br>
<br>
<font size="2" face="sans-serif">please find attached the RFM WG disposition of the above mentioned RIDs. Given that we are trying to achieve consistency among the 3 books, I am kindly asking you to review our proposals within your WGs and to let us know if
these changes are possible for the 3 books. I believe that the mutual issues are limited to the first two RIDs (ESA-GPC-101 and 102) but please do not hesitate to check also the others for areas of cross interest.</font><br>
<br>
<font size="2" face="sans-serif">Please also let us know if any of the RIDs assigned to your groups may have an impact on our book.
</font><br>
<br>
<font size="2" face="sans-serif">To avoid avalanche effects on emails, please do not ask your WG members to send their individual comments to the RFM WG but collect them all and send us one consolidated input per WG,</font><br>
<br>
<font size="2" face="sans-serif">Once agreement on all items is reached, we will edit the PL book and submit to the Editor.</font><br>
<br>
<br>
<font size="2" face="sans-serif">Regards, Enrico</font> <br>
<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>
</div>
</div>
</span>
</body>
</html>