attachment

<div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>Good news about HCD-TNC.<br clear="all"><br></div>Dr. Andreas Steffen at HSR (in Switzerland) had completed a prototype<br></div>implementation, including multiple PA subtypes (i.e., Printer MIB subunits).<br><br></div>All - please take a look at the code and release notes.  We&#39;ll talk more about <br>this prototype effort in two weeks at our August PWG F2F.<br><br></div><div>Cheers,<br></div><div>- Ira<br><br><br></div><div><div><div><div><div><div><div><div class="gmail_signature"><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP &amp; Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Winter  579 Park Place  Saline, MI  48176  734-944-0094<br>Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Andreas Steffen</b> <span dir="ltr">&lt;<a href="mailto:andreas.steffen@hsr.ch">andreas.steffen@hsr.ch</a>&gt;</span><br>Date: Sun, Jul 26, 2015 at 7:13 AM<br>Subject: Re: Query about prototype of IEEE-ISTO PWG Hardcopy Device Health AssessmentTNC Binding<br>To: Ira McDonald &lt;<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;<br><br><br>Hi Ira,<br>
<br>
I&#39;ve just completed a prototype implementing the latest PWG HCD-TNC<br>
spec including support of multiple PA subtypes. You can find the<br>
[partially] commented configuration and log files of the<br>
tnccs-20-hcd-eap example scenario using a HCD IMC/IMV pair under<br>
the link<br>
<br>
<a href="https://wiki.strongswan.org/projects/strongswan/wiki/TrustedNetworkConnect#Hardcopy-Device-Health-Assessment" rel="noreferrer" target="_blank">https://wiki.strongswan.org/projects/strongswan/wiki/TrustedNetworkConnect#Hardcopy-Device-Health-Assessment</a><br>
<br>
If you need a walkthrough through the architecture of the prototype<br>
and or the test results then we can arrange a telco sometime next<br>
week.<br>
<br>
Currently the source code of the prototype is kept in a separate<br>
branch on the strongSwan git server<br>
<br>
<a href="https://git.strongswan.org/?p=strongswan.git;a=shortlog;h=refs/heads/pwg-hcd-tnc" rel="noreferrer" target="_blank">https://git.strongswan.org/?p=strongswan.git;a=shortlog;h=refs/heads/pwg-hcd-tnc</a><br>
<br>
Best regards<br>
<br>
Andreas<br>
<span class=""><br>
On 07/02/2015 05:21 PM, Ira McDonald wrote:<br>
&gt; Hi Dr. Steffen,<br>
&gt;<br>
&gt; Just a reminder that we (PWG) would like to hear back from you when<br>
&gt; you get a chance about a refined cost estimate for a prototype of our<br>
&gt; HCD-TNC spec.<br>
&gt;<br>
&gt; Also, whatever form of RFP (from us) or simply a Proposal (from you).<br>
&gt; The less superfluous paperwork, the better for all of us.<br>
&gt;<br>
&gt; Cheers,<br>
&gt; - Ira (PWG Secretary)<br>
&gt;<br>
&gt;<br>
&gt; Ira McDonald (Musician / Software Architect)<br>
&gt; Co-Chair - TCG Trusted Mobility Solutions WG<br>
&gt; Chair - Linux Foundation Open Printing WG<br>
&gt; Secretary - IEEE-ISTO Printer Working Group<br>
&gt; Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>
&gt; IETF Designated Expert - IPP &amp; Printer MIB<br>
&gt; Blue Roof Music / High North Inc<br>
&gt; <a href="http://sites.google.com/site/blueroofmusic" rel="noreferrer" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
</span>&gt; <a href="http://sites.google.com/site/highnorthinc" rel="noreferrer" target="_blank">http://sites.google.com/site/highnorthinc</a><br>
&gt; mailto: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a> &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;<br>
&gt; Winter  579 Park Place  Saline, MI  48176  <a href="tel:734-944-0094" value="+17349440094">734-944-0094</a><br>
&gt; Summer  PO Box 221  Grand Marais, MI 49839  <a href="tel:906-494-2434" value="+19064942434">906-494-2434</a><br>
<span class="">&gt;<br>
&gt;<br>
&gt; On Mon, Jun 8, 2015 at 7:06 PM, Ira McDonald &lt;<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>
&gt; &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;     Hello Dr. Steffen,<br>
&gt;<br>
&gt;     Here is a link to the HCD TNC draft (with change bars) where I<br>
&gt;     attempted<br>
&gt;     to address all of your comments:<br>
&gt;<br>
&gt;       <a href="http://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20150530-rev.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20150530-rev.pdf</a><br>
&gt;<br>
</span><span class="">&gt;     That draft was reviewed last Monday by the PWG IDS WG - so I just sent<br>
&gt;     another HCD TNC draft (with change bars) where I attempted to address<br>
&gt;     all of the IDS WG member comments and discussion:<br>
&gt;<br>
&gt;       <a href="http://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20150608-rev.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20150608-rev.pdf</a><br>
&gt;<br>
</span><span class="">&gt;     Note especially that, by IDS WG consensus, I added a series of<br>
&gt;     HCD-specific<br>
&gt;     PA subtypes that map one-to-one to all of the components of an HCD<br>
&gt;     defined<br>
&gt;     in the abstract model in the PWG Imaging System State and Counter<br>
&gt;     MIB v2:<br>
&gt;<br>
&gt;<br>
&gt;     <a href="http://ftp.pwg.org/pub/pwg/candidates/cs-wimscountmib20-20080318-5106.3.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/candidates/cs-wimscountmib20-20080318-5106.3.pdf</a><br>
&gt;<br>
&gt;<br>
</span><div><div class="h5">&gt;     <a href="http://ftp.pwg.org/pub/pwg/candidates/cs-wimscountmib20-20080318-5106.3.mib" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/candidates/cs-wimscountmib20-20080318-5106.3.mib</a><br>
&gt;<br>
&gt;     IDS WG members strongly feel that firmware for the System (main board),<br>
&gt;     Console, Finisher, Interface, Marker, and Scanner components should be<br>
&gt;     labeled with the relevant HCD component type (since each of these major<br>
&gt;     components typically has a unique boot ROM, a unique OS, and a unique<br>
&gt;     firmware image - also each of these major components are typically built<br>
&gt;     by different suppliers).<br>
&gt;<br>
&gt;     I realize that the TCG face-to-face meeting in Edinburgh will be<br>
&gt;     next week,<br>
&gt;     but please take a look at the change logs and redlines in these two<br>
&gt;     versions<br>
&gt;     at your convenience.<br>
&gt;<br>
&gt;     PWG Steering Committee members are unanimously in favor of proceeding<br>
&gt;     with our discussion of a strongSWAN prototype effort and refinement<br>
&gt;     of your<br>
&gt;     original cost estimate (we do realize that we just made it a bit<br>
&gt;     more complex,<br>
&gt;     although in practice a single HCD IMV should normally be sufficient - an<br>
&gt;     exception might be for high-end Finishers built by third parties).<br>
&gt;<br>
&gt;     Cheers,<br>
&gt;     - Ira (IEEE-ISTO PWG Secretary, HCD TNC Binding editor)<br>
&gt;<br>
&gt;     Ira McDonald (Musician / Software Architect)<br>
&gt;     Co-Chair - TCG Trusted Mobility Solutions WG<br>
&gt;     Chair - Linux Foundation Open Printing WG<br>
&gt;     Secretary - IEEE-ISTO Printer Working Group<br>
&gt;     Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>
&gt;     IETF Designated Expert - IPP &amp; Printer MIB<br>
&gt;     Blue Roof Music / High North Inc<br>
&gt;     <a href="http://sites.google.com/site/blueroofmusic" rel="noreferrer" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
</div></div>&gt;     <a href="http://sites.google.com/site/highnorthinc" rel="noreferrer" target="_blank">http://sites.google.com/site/highnorthinc</a><br>
&gt;     mailto: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a> &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;<br>
&gt;     Winter  579 Park Place  Saline, MI  48176  <a href="tel:734-944-0094" value="+17349440094">734-944-0094</a><br>
&gt;     &lt;tel:<a href="tel:734-944-0094" value="+17349440094">734-944-0094</a>&gt;<br>
&gt;     Summer  PO Box 221  Grand Marais, MI 49839  <a href="tel:906-494-2434" value="+19064942434">906-494-2434</a><br>
&gt;     &lt;tel:<a href="tel:906-494-2434" value="+19064942434">906-494-2434</a>&gt;<br>
<span class="">&gt;<br>
&gt;<br>
&gt;     On Mon, May 18, 2015 at 9:22 PM, Ira McDonald<br>
</span><span class="">&gt;     &lt;<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a> &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;         Hi Andreas,<br>
&gt;<br>
&gt;         More background:<br>
&gt;<br>
&gt;         There are NO implementations of this HCD TNC Binding in any real<br>
&gt;         printer.<br>
&gt;<br>
&gt;         The PWG Process 3.0 requires that, when aworking draft has<br>
&gt;         reached the<br>
&gt;         &quot;Prototype&quot; draft state, then it MUST be prototyped (at some<br>
&gt;         level) by at<br>
&gt;         least one vendor before the document can advance to a &quot;Stable&quot;<br>
&gt;         draft state<br>
&gt;         and pass on through WG last call, then PWG last call, and<br>
&gt;         finally PWG formal<br>
&gt;         vote for a PWG Candidate Standard (published).<br>
&gt;<br>
&gt;           <a href="http://ftp.pwg.org/pub/pwg/general/pwg-process-30.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/general/pwg-process-30.pdf</a><br>
&gt;<br>
</span><span class="">&gt;         The point of asking for your help for a prototype is to get this<br>
&gt;         document<br>
&gt;         moving forward again on the PWG standards process.<br>
&gt;<br>
&gt;         You already found several discrepancies (I&#39;ll take them to the<br>
&gt;         IDS WG for<br>
&gt;         review and updated text).  Unfortunately, I can&#39;t choose to<br>
&gt;         restructure the<br>
&gt;         Firmware/ResidentApplication/UserApplication* tuples into single<br>
&gt;         attributes.<br>
&gt;         Note that IETF NEA did not do so for the similar attributes<br>
&gt;         either (our main<br>
&gt;         source for structure).<br>
&gt;<br>
&gt;         I look forward to your further thoughts and reply.<br>
&gt;<br>
&gt;         Cheers,<br>
&gt;         - Ira<br>
&gt;<br>
&gt;         Ira McDonald (Musician / Software Architect)<br>
&gt;         Co-Chair - TCG Trusted Mobility Solutions WG<br>
&gt;         Chair - Linux Foundation Open Printing WG<br>
&gt;         Secretary - IEEE-ISTO Printer Working Group<br>
&gt;         Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>
&gt;         IETF Designated Expert - IPP &amp; Printer MIB<br>
&gt;         Blue Roof Music / High North Inc<br>
&gt;         <a href="http://sites.google.com/site/blueroofmusic" rel="noreferrer" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
</span>&gt;         <a href="http://sites.google.com/site/highnorthinc" rel="noreferrer" target="_blank">http://sites.google.com/site/highnorthinc</a><br>
&gt;         mailto: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a> &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;<br>
&gt;         Winter  579 Park Place  Saline, MI  48176  <a href="tel:734-944-0094" value="+17349440094">734-944-0094</a><br>
&gt;         &lt;tel:<a href="tel:734-944-0094" value="+17349440094">734-944-0094</a>&gt;<br>
&gt;         Summer  PO Box 221  Grand Marais, MI 49839  <a href="tel:906-494-2434" value="+19064942434">906-494-2434</a><br>
&gt;         &lt;tel:<a href="tel:906-494-2434" value="+19064942434">906-494-2434</a>&gt;<br>
<span class="">&gt;<br>
&gt;<br>
&gt;         On Sun, May 17, 2015 at 2:05 PM, Andreas Steffen<br>
</span><span class="">&gt;         &lt;<a href="mailto:andreas.steffen@hsr.ch">andreas.steffen@hsr.ch</a> &lt;mailto:<a href="mailto:andreas.steffen@hsr.ch">andreas.steffen@hsr.ch</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;             Hi Ira,<br>
&gt;<br>
&gt;             I think 2&#39;000 USD should be sufficient to fund the<br>
&gt;             implementation of<br>
&gt;             the PWG HCD PA-TNC attributes and to build a demo HCD<br>
&gt;             IMC/IMV pair<br>
&gt;             since the structure of the attributes types is quite simple.<br>
&gt;<br>
&gt;             Concerning the PWG HCD Health Assessment TNC Binding draft I<br>
&gt;             have<br>
&gt;             the following remarks/questions:<br>
&gt;<br>
&gt;             - The attribute type 0x50 (23) of the TimeSource attribute<br>
&gt;             is wrong.<br>
&gt;               0x50 (80) has been assigned to ResidentApplicationName.<br>
&gt;             The correct<br>
&gt;               attribute type of TimeSource probably is 0x32 (50).<br>
&gt;<br>
&gt;<br>
&gt;         &lt;ira&gt;  Thanks for catching the TimeSource typo.  Actually the<br>
&gt;         decimal value of &#39;23&#39;<br>
&gt;         is correct and the hex value of &#39;0x50&#39; is wrong and should be<br>
&gt;         &#39;0x17&#39; per this<br>
&gt;         table of assigned values from the Imaging Device Security WG:<br>
&gt;<br>
&gt;         <a href="http://ftp.pwg.org/pub/pwg/ids/wd/ids-attributes-2012-04-20.txt" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/ids/wd/ids-attributes-2012-04-20.txt</a><br>
&gt;<br>
&gt;<br>
</span><div><div class="h5">&gt;             - How is the 128 bit binary blob of the *Version attributes<br>
&gt;             to be<br>
&gt;               interpreted? The draft says that it MAY conform to section<br>
&gt;             4.2.3<br>
&gt;               “Numeric Version” of IETF PA-TNC [RFC5792]:<br>
&gt;<br>
&gt;<br>
&gt;         &lt;ira&gt; The version block is opaque and (per Lexmark and Ricoh input)<br>
&gt;         was not standardized (i.e., you can&#39;t interpret it, any more<br>
&gt;         than you can<br>
&gt;         interpret the equivalent NEA attribute). You just do a binary<br>
&gt;         compare for<br>
&gt;         equality.  Not my choice, because the PWG model spec (whose link<br>
&gt;         I also<br>
&gt;         sent is authoritative but ambiguous).<br>
&gt;<br>
&gt;              *                       1                   2<br>
&gt;                  3<br>
&gt;              *   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7<br>
&gt;             8 9 0 1<br>
&gt;              *<br>
&gt;             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;              *  |                        Major Version Number<br>
&gt;                    |<br>
&gt;              *<br>
&gt;             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;              *  |                        Minor Version Number<br>
&gt;                    |<br>
&gt;              *<br>
&gt;             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;              *  |                            Build Number<br>
&gt;                    |<br>
&gt;              *<br>
&gt;             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;              *  |      Service Pack Major       |      Service Pack<br>
&gt;             Minor       |<br>
&gt;              *<br>
&gt;             +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
&gt;<br>
&gt;                If another representation is chosen by a printer vendor then<br>
&gt;                interoperability will be very difficult. Shall the demo<br>
&gt;                implementation just do a hex dump of the 128 bit blob?<br>
&gt;<br>
&gt;<br>
&gt;         &lt;ira&gt; Yes - pure 128-bit dump.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;             - Section 5.4 Correlated Attributes (Name, Patches,<br>
&gt;             StringVersion,<br>
&gt;               Version) has a note saying: Each ordered set of Correlated<br>
&gt;             Attributes<br>
&gt;               MUST include an empty string if there is no known value<br>
&gt;             for one of<br>
&gt;               the Correlated Attributes. This cannot be true for the Version<br>
&gt;               attribute because it has a fixed size of 16 bytes. It<br>
&gt;             would make<br>
&gt;               sense to set the 128 bit binary blob to all zeroes.<br>
&gt;<br>
&gt;<br>
&gt;         &lt;ira&gt; Agreed - this is a bug in this binding and the PWG model spec.<br>
&gt;         This will take some grief to fix (PWG Process to adopt an errata of<br>
&gt;         the model spec).  Yes, zero&#39;s would be appropriate for the<br>
&gt;         fixed-length<br>
&gt;         attributes.  I&#39;ll raise the issue in the IDS WG.<br>
&gt;<br>
&gt;<br>
&gt;             - Because of the Correlated Attributes requirement it would<br>
&gt;             make much<br>
&gt;               more sense to pack Name, Patches, StringVersion and<br>
&gt;             Version into<br>
&gt;               a single attribute. The reason this isn&#39;t done is probably<br>
&gt;             due to<br>
&gt;               the size restrictions of PT-EAP transport. I&#39;d like to<br>
&gt;             mention that<br>
&gt;               all strongSwan IMCs and IMVs support the IF-M Segmentation<br>
&gt;               Specification proposal being drafted by the TNC Endpoint<br>
&gt;             Compliance<br>
&gt;               Subgroup which allows to transfer huge attributes<br>
&gt;             (&gt;100&#39;000 kB) in<br>
&gt;               chunks as small as several hundred bytes over<br>
&gt;             size-restricted PB-TNC<br>
&gt;               batches.<br>
&gt;<br>
&gt;<br>
&gt;         &lt;ira&gt; The PWG model spec was adopted years earlier - we CANNOT<br>
&gt;         make any such structural changes at this point to defined<br>
&gt;         attributes<br>
&gt;         (because as SEPARATE attributes they&#39;re already in the approved<br>
&gt;         parallel PWG MS-NAP Binding).<br>
&gt;<br>
&gt;<br>
&gt;             - For the demo it would be helpful to have some real-world<br>
&gt;             examples<br>
&gt;               taken from actual printers for all of the 25 PWG HCD<br>
&gt;             attribute types.<br>
&gt;<br>
&gt;<br>
&gt;         &lt;ira&gt; There are NO real-world examples or implementations.  See my<br>
&gt;         note above.<br>
&gt;<br>
&gt;<br>
&gt;             Best regards<br>
&gt;<br>
&gt;             Andreas<br>
&gt;<br>
&gt;             On 05/15/2015 08:50 PM, Ira McDonald wrote:<br>
&gt;             &gt; Hi Andreas,<br>
&gt;             &gt;<br>
&gt;             &gt; We spoke several years ago at a TCG face-to-face meeting about your<br>
&gt;             &gt; wonderful open<br>
&gt;             &gt; source TNC protocol stack.<br>
&gt;             &gt;<br>
&gt;             &gt; Two weeks ago, I attended the annual joint meeting of IEEE-ISTO Printer<br>
&gt;             &gt; Working roup<br>
&gt;             &gt; (I&#39;m the Secretary) and Linux Foundation Open Printing<br>
&gt;             Summit (I&#39;m the<br>
&gt;             &gt; Chair), where we<br>
&gt;             &gt; reviewed minor editorial changes to a work-in-progress PWG<br>
&gt;             Hardcopy<br>
&gt;             &gt; Device Health<br>
&gt;             &gt; Assessment TNC Binding spec which has been waiting in<br>
&gt;             Prototype Draft<br>
&gt;             &gt; state for awhile.<br>
&gt;             &gt;<br>
&gt;             &gt;   <a href="http://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20150419.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/ids/wd/wd-idstnc10-20150419.pdf</a><br>
&gt;             &gt;<br>
&gt;             &gt;<br>
&gt;             &gt;<br>
</div></div><div><div class="h5">&gt;             <a href="http://ftp.pwg.org/pub/pwg/candidates/cs-idsattributes11-20140529-5110.1.pdf" rel="noreferrer" target="_blank">http://ftp.pwg.org/pub/pwg/candidates/cs-idsattributes11-20140529-5110.1.pdf</a><br>
&gt;             &gt;<br>
&gt;             &gt; Mike Sweet (Apple, PWG Chair) suggested that I ask if you<br>
&gt;             would be<br>
&gt;             &gt; interested in PWG<br>
&gt;             &gt; funding for a graduate student to use your TNC stack and<br>
&gt;             do a desktop<br>
&gt;             &gt; prototype (not<br>
&gt;             &gt; hosted in an actual printer) of these 20+ PWG extension<br>
&gt;             health attributes.<br>
&gt;             &gt;<br>
&gt;             &gt; If you are interested, would you take a quick look at our<br>
&gt;             spec and think<br>
&gt;             &gt; about what kind<br>
&gt;             &gt; of funding level would be appropriate to build a desktop<br>
&gt;             prototype of a<br>
&gt;             &gt; &quot;printer&quot; reporting<br>
&gt;             &gt; its own health attributes as a TNC Client.<br>
&gt;             &gt;<br>
&gt;             &gt; Cheers,<br>
&gt;             &gt; - Ira (PWG Secretary, IPP WG Co-Chair, HCD-TNC Editor)<br>
&gt;             &gt;<br>
&gt;             &gt;<br>
&gt;             &gt; Ira McDonald (Musician / Software Architect)<br>
&gt;             &gt; Co-Chair - TCG Trusted Mobility Solutions WG<br>
&gt;             &gt; Chair - Linux Foundation Open Printing WG<br>
&gt;             &gt; Secretary - IEEE-ISTO Printer Working Group<br>
&gt;             &gt; Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>
&gt;             &gt; IETF Designated Expert - IPP &amp; Printer MIB<br>
&gt;             &gt; Blue Roof Music / High North Inc<br>
&gt;             &gt; <a href="http://sites.google.com/site/blueroofmusic" rel="noreferrer" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
</div></div><span class="">&gt;             &gt; <a href="http://sites.google.com/site/highnorthinc" rel="noreferrer" target="_blank">http://sites.google.com/site/highnorthinc</a><br>
&gt;             &gt; mailto: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>
&gt;             &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;<br>
</span>&gt;             &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>
&gt;             &lt;mailto:<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>&gt;&gt;<br>
&gt;             &gt; Winter  579 Park Place  Saline, MI  48176  <a href="tel:734-944-0094" value="+17349440094">734-944-0094</a><br>
&gt;             &lt;tel:<a href="tel:734-944-0094" value="+17349440094">734-944-0094</a>&gt;<br>
&gt;             &gt; Summer  PO Box 221  Grand Marais, MI 49839  906-494-2434<br>
&gt;             &lt;tel:906-494-2434&gt;<br>
<span class="">&gt;             &gt;<br>
&gt;<br>
&gt;             --<br>
&gt;             ======================================================================<br>
&gt;             Andreas Steffen                         e-mail:<br>
</span>&gt;             <a href="mailto:andreas.steffen@hsr.ch">andreas.steffen@hsr.ch</a> &lt;mailto:<a href="mailto:andreas.steffen@hsr.ch">andreas.steffen@hsr.ch</a>&gt;<br>
<span class="">&gt;             Institute for Internet Technologies and Applications<br>
</span>&gt;             Hochschule fuer Technik Rapperswil      phone:  +41 55 222<br>
&gt;             42 68 &lt;tel:%2B41%2055%20222%2042%2068&gt;<br>
&gt;             CH-8640 Rapperswil (Switzerland)        mobile: +41 76 340<br>
&gt;             25 56 &lt;tel:%2B41%2076%20340%2025%2056&gt;<br>
&gt;             ===========================================================[ITA-HSR]==<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
--<br>
======================================================================<br>
Andreas Steffen                         e-mail: <a href="mailto:andreas.steffen@hsr.ch">andreas.steffen@hsr.ch</a><br>
<span class="">Institute for Internet Technologies and Applications<br>
</span>Hochschule fuer Technik Rapperswil      phone:  +41 55 222 42 68<br>
CH-8640 Rapperswil (Switzerland)        mobile: +41 76 340 25 56<br>
===========================================================[ITA-HSR]==<br>
<br>
</div><br></div></div></div></div></div></div></div>