<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Great! Although I do see _one_ issue -
      the use of the words "Commercial" and "CCSDS" to delineate things.
      If we write a Blue, isn't that now a CCSDS PHY/MAC? It seems to
      promulgate the idea of "CCSDS" standards as special homespun
      solutions for spaceflight, which really needs to end...<br>
      <br>
                                                                     
      Steve<br>
      <br>
      On 2014-10-22, 6:53 AM, Barton, Richard J. (JSC-EV811) wrote:<br>
    </div>
    <blockquote cite="mid:D06D20F1.1BCBA%25richard.j.barton@nasa.gov"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>
        <div>
          <div>Yay! Tell Chris we all owe him a beer or two.</div>
          <div><br>
          </div>
          <div>Rick</div>
          <div><br>
          </div>
          <div>
            <div>Richard J. Barton, Ph.D.</div>
            <div>Wireless and Communication Systems Branch</div>
            <div>NASA Johnson Space Center</div>
            <div>2101 NASA Parkway</div>
            <div>Mail Code EV811</div>
            <div>Houston, TX 77058</div>
            <div>281-483-1444 (office)</div>
            <div>281-483-5830 (fax)</div>
            <div>713-818-4076 (cell)</div>
            <div><br>
            </div>
          </div>
        </div>
      </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
            moz-do-not-send="true"
            href="mailto:Jean-Francois.Dufour@esa.int">Jean-Francois.Dufour@esa.int</a>"
          <<a moz-do-not-send="true"
            href="mailto:Jean-Francois.Dufour@esa.int">Jean-Francois.Dufour@esa.int</a>><br>
          <span style="font-weight:bold">Date: </span>Wednesday,
          October 22, 2014 at 7:36 AM<br>
          <span style="font-weight:bold">To: </span>"<a
            moz-do-not-send="true"
            href="mailto:sois-wir@mailman.ccsds.org">sois-wir@mailman.ccsds.org</a>"
          <<a moz-do-not-send="true"
            href="mailto:sois-wir@mailman.ccsds.org">sois-wir@mailman.ccsds.org</a>><br>
          <span style="font-weight:bold">Subject: </span>[Sois-wir]
          CCSDS: Agreement between SOIS Wireless and SLS Placom working
          groups<br>
        </div>
        <div><br>
        </div>
        <div>
          <div><font face="sans-serif" size="2">Dear Colleagues,</font>
            <br>
            <br>
            <font face="sans-serif" size="2">Please take note of the
              agreement below between CCSDS SOIS-Wireless and the PLACOM
              group.</font><br>
            <br>
            <font face="sans-serif" size="2">Regards,</font> <br>
            <br>
            <font face="sans-serif" size="2">Jean-Francois Dufour</font>
            <br>
            <font face="sans-serif" size="2">Chairman of the CCSDS SOIS
              Wireless Working Group</font><br>
            <br>
            <br>
            <br>
            <font color="#800080" face="sans-serif" size="1">-----
              Forwarded by Chris Taylor/estec/ESA on 22/10/2014 14:19
              -----</font><br>
            <br>
            <font color="#5f5f5f" face="sans-serif" size="1">From:      
               </font><font face="sans-serif" size="1"><a
                moz-do-not-send="true"
                href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a></font><br>
            <font color="#5f5f5f" face="sans-serif" size="1">To:        </font><font
              face="sans-serif" size="1">"CCSDS CESG --" <<a
                moz-do-not-send="true"
                href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>,
            </font><br>
            <font color="#5f5f5f" face="sans-serif" size="1">Date:      
               </font><font face="sans-serif" size="1">21/10/2014 18:01</font><br>
            <font color="#5f5f5f" face="sans-serif" size="1">Subject:  
                   </font><font face="sans-serif" size="1">[CESG] Nuntio
              Vobis Gaudium Magnum (from SOIS and SLS)</font><br>
            <font color="#5f5f5f" face="sans-serif" size="1">Sent by:  
                   </font><font face="sans-serif" size="1"><a
                moz-do-not-send="true"
                href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a></font><br>
            <hr noshade="noshade">
            <br>
            <br>
            <br>
            <font face="sans-serif" size="2">Dear All,</font><font
              size="3"> </font><font face="sans-serif" size="2"><br>
                     I would like to inform you that, with respect to
              the overlap issue discussed in the CESG, today SOIS and
              SLS Area have agreed today the following split of
              responsibilities:</font><font size="3"><br>
            </font><font face="sans-serif" size="2"><br>
              __________________</font><font size="3"> </font><font
              face="sans-serif" size="2"><br>
              SLS Responsibilities include:<br>
              1) point-to-point links for Planetary Communications<br>
              2) multi-point links for Planetary Communications
              utilising CCSDS data link and physical layer protocols<br>
              3) consideration of usage of Radio Frequency bands over
              space-ground and space-space links
            </font><font size="3"><br>
            </font><font face="sans-serif" size="2"><br>
              SLS can therefore define mission scenarios/profiles for
              Planetary Communications, as well as functional &
              performance requirements and develop the pertinent
              Standards (Magenta or Blue Books) according to the points
              1..3 listed above.</font><font size="3"><br>
            </font><font face="sans-serif" size="2"><br>
              SOIS Responsibilities include:<br>
              A) networked multi-point links utilising commercial
              wireless network technologies for Communications onboard a
              space vehicle or habitat and/or surface links within the
              proximity of that vehicle or habitat.<br>
              B) cooperation with the SLS Area for matters related to
              usage of Radio Frequency bands
            </font><font size="3"><br>
            </font><font face="sans-serif" size="2"><br>
              SOIS can therefore define mission scenarios/profiles for
              Vehicle and vicinity Communications, as well as functional
              & performance requirements and develop the pertinent
              Standards (Magenta or Blue Books) according to the points
               A..B listed above.</font><font size="3"><br>
            </font><font face="sans-serif" size="2"><br>
              Charters and CWE Projects of the affected WGs in SLS and
              SOIS Areas are to be made consistent with the above set of
              responsibilities (if not consistent now).<br>
              __________________</font><font size="3"> <br>
            </font><font face="sans-serif" size="2"><br>
              Best regards to you all and my particular thanks to Chris
              and Gilles for the pro active collaboration.</font><font
              size="3"><br>
              <br>
            </font><font face="sans-serif" size="2"><br>
              Gian Paolo</font><font size="3"> </font><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>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Sois-wir mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sois-wir@mailman.ccsds.org">Sois-wir@mailman.ccsds.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sois-wir">http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sois-wir</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Stephen P. Braham, BSc, PhD, ARCS       Director, PolyLAB
<a class="moz-txt-link-abbreviated" href="mailto:warp@polylab.sfu.ca">warp@polylab.sfu.ca</a>                   TIME Centre 
(tel) 778 782-7981                      Simon Fraser University 
(fax) 778 782-7980                      Harbour Centre Campus
<a class="moz-txt-link-freetext" href="http://team.polylab.sfu.ca/~warp/">http://team.polylab.sfu.ca/~warp/</a> Vancouver, BC, Canada
Twitter: warp
Callsign: VA7TMI

   PolyLAB: From the Classroom to Space, <a class="moz-txt-link-freetext" href="http://polylab.sfu.ca/">http://polylab.sfu.ca/</a>
</pre>
  </body>
</html>