<br><font size=2 face="sans-serif">FYI</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Nestor
Peccia/esoc/ESA on 14/03/2011 09:34 -----</font>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">"Hooke, Adrian J (9000)" <adrian.j.hooke@jpl.nasa.gov></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">CCSDS Engineering Steering Group - CESG
Exec <cesg@mailman.ccsds.org></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">11/03/2011 21:22</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">[CESG] Implementation of new CCSDS Patent
Policy</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">cesg-bounces@mailman.ccsds.org</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=3 face="Calibri"><b>Area Directors</b>: the CCSDS Management
Council has adopted a new policy concerning the standardization of patented
technologies. The full instructions are attached below, but here is the
essence of how the policy will affect the operations of your BOFs and Working
Groups:</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">1. The ISO patent policy
of 2006 has been adopted. You can find information at </font><a href="http://isotc.iso.org/livelink/livelink/fetch/2000/2122/3770791/customview.html?func=ll&objId=3770791&objAction=browse"><font size=3 face="Calibri">http://isotc.iso.org/livelink/livelink/fetch/2000/2122/3770791/customview.html?func=ll&objId=3770791&objAction=browse</font></a>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">2. The basic requirement
is that if a proposed Standards-track (Blue or Magenta) document depends
on a patented technology, that fact must be disclosed as soon as a BOF
or Working Group is aware of the existence of the patent or patents.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">3. If a Standards-track
document is known to depend on patented technology, an Annex must be added
which states clearly which patents apply and where to apply for a license.
The Annex must also contain the signed ISO patent statement and licensing
declaration form(s).</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">4. A statement must
also be added the introduction to each proposed Standards-track document
stating whether there are any patent liens. If there are, this text must
point to the Annex and must state: “In the event that any user of this
standard is unable to obtain a license under what they consider to be reasonable
and non-discriminatory terms, they are requested to contact the CCSDS Secretariat
at the address shown on the AUTHORITY page of this document”.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">5. This policy shall
be applied to all new CCSDS projects during the chartering process.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">6. This policy is retroactive
to all current CCSDS projects and to all standards-track (Blue, Magenta)
documents that have not yet been approved.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">In implementing this policy, it is critical
that impact on future users of the Standard should be considered. Basically,
if you are aware of the existence of a patent that could potentially expose
someone implementing the standard to being liable for infringement, then
you must disclose it. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>The immediate impact of this policy
falls onto the three proposed new channel codes which are known to have
patent issues:</b> LDPC; SCCC and DVB-S. In each case, all patents must
be disclosed via addition of the above statement and Annex, and a signed
ISO Patent Statement and Licensing Declaration Form (attached) must be
included in the Annex. This form should have the “ISO Deliverable” box
checked in the “Document Type” field and the CCSDS document number and
title added. The patent holder must check either Box 1, 2 or 3 in the Licensing
Declaration <b>and must sign the form</b>. In addition, the Patent Information
section on page-3 must be completed. <b>No document will be sent to the
CMC for final approval without this statement, Annex and signed declaration</b>.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">The Procedures Manual will be updated soon
to reflect this policy. However, it is now in effect and it must be followed
for all CCSDS Standards-track documents. Please give this your fullest
attention.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Best regards</font>
<br><font size=3 face="Calibri">Adrian</font>
<br><font size=3 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Adrian J. Hooke</font>
<br><img src=cid:_2_07B4EB1C07B4E6E0002F3942C1257853><font size=2 color=#004080 face="Calibri"><br>
Chairman, CCSDS Engineering Steering Group (CESG)</font>
<br><font size=2 color=#004080 face="Calibri">Space Communications and
Navigation Office (SCaN)</font>
<br><font size=2 color=#004080 face="Calibri">Space Operations Mission
Directorate<br>
NASA Headquarters<br>
Washington DC 20024-3210</font>
<br><font size=3 color=#004080 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>From:</b> Kearney, Mike W. (MSFC-EO01)
[</font><a href=mailto:mike.kearney@nasa.gov><font size=3 face="Calibri">mailto:mike.kearney@nasa.gov</font></a><font size=3 face="Calibri">]
<b><br>
Sent:</b> Friday, March 11, 2011 12:10 PM<b><br>
To:</b> Hooke, Adrian J (9000); Nestor.Peccia@esa.int<b><br>
Cc:</b> cmc@mailman.ccsds.org<b><br>
Subject:</b> CCSDS Patent Policy - Actions to CESG</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Dear Adrian and Nestor: This is a
message from the CMC to you as CESG chair and deputy with instructions
to implement the new CCSDS Patent Policy across the CCSDS organization.
</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">In recent teleconferences, the CMC has
reached consensus on the standardization of patented technologies within
CCSDS. In summary the key points are that CCSDS will: </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">(1) Change the patent licensing
terminology from “fair and non discriminator” to “reasonable and non-discriminatory”.
</font>
<br><font size=3 face="Calibri">(2) Follow the ISO process and require
the ISO declaration form to be filled out and signed by the patent holder.
</font>
<br><font size=3 face="Calibri">(3) Add standardized text to our
documents that explains the patent situations for that document. </font>
<br><font size=3 face="Calibri">(4) Beyond the ISO process, WG chairs
should be required to *<b>attempt</b>* to secure the license terms from
patent-holders. However that would not be required in order to develop
or approve a standard. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">To encode that consensus in CCSDS policy,
the CMC has adopted two resolutions, and assigned some actions to the CESG.
</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">The first resolution: </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>The CCSDS Management Council: </b><br>
<b><br>
CONSIDERING</b> that there is an increase in the usage of Patented Technology
in CCSDS standardization efforts, and a CCSDS policy on the topic is needed;
<br>
<b><br>
and RECOGNIZING</b> that ISO has place requirements on CCSDS and SC13 to
follow ISO processes for documents processed as ISO standards; <br>
<b><br>
and NOTING</b> that ISO and other standards organizations generally apply
“Reasonable And Non-Discriminatory” (RAND) requirements to license fees;
<br>
<b><br>
ADOPTS</b> the 2006 ISO patent policy and requires that this policy be
implemented during the process of chartering a working group;</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>And REQUIRES</b> that the ISO patent
statement and licensing declaration form must be completed before any CCSDS
document can be submitted to the CMC for potential approval on the Standards
track.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">The second resolution:</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>The CCSDS Management Council</b>: <br>
<b><br>
CONSIDERING</b> that the CCSDS policy for patented technology must be implemented
in the CCSDS processes; <br>
<b><br>
and RECOGNIZING</b> the importance of communicating patent license requirements
to the users of CCSDS documentation; <br>
<b><br>
and NOTING</b> that ISO guidance must be urgently communicated to the CCSDS
working groups currently developing standards affected by this policy;
<br>
<b><br>
REQUIRES </b>that an Annex covering patent issues must be added to each
Standards track document. The annex must state clearly which patents
apply, where to apply for a license and provide the ISO patent statement
and licensing declaration form(s). A statement must also be added the introduction
to each proposed Standards-track document addressing any licensing issues,
pointing to the Annex, and stating: “In the event that any user of this
standard is unable to obtain a license under what they consider to be reasonable
and non-discriminatory terms, they are requested to contact the CCSDS Secretariat
at the address shown on the AUTHORITY page of this document”.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"><b>And REQUIRES</b> that this policy shall
be applied to all documents that are currently in the CCSDS approval process.
</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">There is one important clarification that
is needed on the resolution above: </font>
<br><font size=3 color=#004080 face="Calibri"> </font>
<br><font size=3 face="Wingdings">Ø </font><font size=3 face="Calibri">“And
REQUIRES that the ISO patent statement and licensing declaration form must
be completed before any CCSDS document can be submitted to the CMC for
potential approval on the Standards track.” </font>
<br><font size=3 color=#004080 face="Calibri"> </font>
<br><font size=3 face="Calibri">That resolution addresses the worst-case
scenario stating that documents using patented technologies will not be
approved without patent-holder signature on the ISO declaration form and
it is phrased in a way that will not stop currently ongoing work. However,
the CMC also requires that: </font>
<br><font size=3 face="Calibri">(1) New charters and document projects
must state if patented technology is used</font>
<br><font size=3 face="Calibri">(2) Document projects must have
the ISO declaration form signed before they can be added to a WG’s work
plan</font>
<br><font size=3 face="Calibri">(3) Existing charters and document
projects must be updated to indicate their patented technology status,
and approved by the CMC. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">To implement the policies of those resolutions,
the CMC has assigned the following action items to the CESG: </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">The CESG shall implement the CMC Resolutions
on Patent Policy with the following actions: </font>
<br><font size=3 color=#004080 face="Calibri"> </font>
<br><font size=3 face="Calibri">1. Investigate and
declare where patented technologies apply to any technology used by CCSDS
standards, past, present and future; </font>
<br><font size=3 face="Calibri">2. Update all WG charters
and Projects to reflect the existence (or lack thereof) for any such patent
issues; </font>
<br><font size=3 face="Calibri">3. Begin the process
of using the ISO patent policy, including securing the license declaration
form; </font>
<br><font size=3 face="Calibri">4. Familiarize the
WG chairs with the ISO Patent database so that they can research patents
that are already in the ISO database; </font>
<br><font size=3 face="Calibri">5. When possible, secure
written information from the patent holders about their intended terms
(including royalties and fee schedule, when possible) for granting licenses
for the use of their technologies; </font>
<br><font size=3 face="Calibri">6. These new policies
shall be immediately applied to documents currently in work. In particular,
the LDPC and SCCC documents in the SLS area have a requirement to have
the ISO declaration signed by the patent holder, and a goal to get more
specific information from the patent holder to allow CCSDS to evaluate
the "Reasonable and Non-Discriminatory" status of the patent
licensing policy. </font>
<br><font size=3 face="Calibri">Action: CESG Chair and Deputy Chair</font>
<br><font size=3 face="Calibri">Due Date: Spring 2011 meeting</font>
<br><font size=3 face="Calibri">Status: Open</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">To enable the updating and approval of
Charters and Projects within the CCSDS Framework system, the Secretariat
is making modifications to the online framework. These modifications
will be complete on Monday, March 14. At that time the teams will
be able to update their charters and projects. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">We anticipate that this will not be much
added work for our WG teams, because the technical experts in most working
groups will immediately be able to respond with “no patented technologies
apply”. However, as you know, there are several SLS efforts underway
that very much need to line up their efforts with this new policy, especially
securing the ISO licensing declaration form with the patent-holder signature.
</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Further, the CMC is considering draft text
to update the procedures manual for compatibility with the policy stated
above. This should be complete within a few weeks. However,
that should not hold up the actions as assigned above. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Thanks for your swift implementation of
this important policy. </font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri"> -=- Mike</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Mike Kearney</font>
<br><font size=3 face="Calibri">CCSDS Chairman and General Secretary </font>
<br><a href=www.ccsds.org><font size=3 face="Calibri">www.ccsds.org</font></a>
<br><img src=cid:_2_0A0843200A084014002F3942C1257853 alt=cid:3303993661_5210558>
<br><font size=3 face="Calibri">****************</font>
<br><font size=3 face="Calibri">Mail Code EO-01</font>
<br><font size=3 face="Calibri">NASA Marshall Space Flight Center</font>
<br><font size=3 face="Calibri">Huntsville, Alabama 35803, USA</font>
<br><font size=3 face="Calibri">+1-256-544-2029</font>
<br><a href=mailto:Mike.Kearney@nasa.gov><font size=3 color=blue face="Calibri">Mike.Kearney@nasa.gov</font></a>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href=http://mailman.ccsds.org/mailman/listinfo/cesg><tt><font size=2>http://mailman.ccsds.org/mailman/listinfo/cesg</font></tt></a><tt><font size=2><br>
</font></tt>
<br>