attachment
<div dir="ltr"><div>Hi Smith,</div><div><br></div><div>I'm working on the IETF RFC references and checking the US NIST references</div><div>for the hash algorithms in Table 10 of EPX.</div><div><br></div><div>I downloaded the MS Word source "wd-ippepx20-20201029.docx" just now. My</div><div>copy of MS Word 2019 cannot open it - says it contains "unreadable" content and</div><div>suggests a recovery attempt - I didn't try it. <br></div><div><br></div><div>OTOH, the MS Word source "wd-ippepx20-20201029-rev.docx" does open OK</div><div>without warnings.</div><div><br></div><div>I'm not sure what version of MS Word you're using or what OS platform. But the</div><div>source of the eventual published version needs to be stable and readable for</div><div>future maintenance.</div><div><br></div><div>More later on the hash algorithm references.</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><i><font size="1">Ira McDonald (Musician / Software Architect)</font></i></div><div><i><font size="1">Chair - SAE Trust Anchors and Authentication TF<br></font></i></div><div dir="ltr"><i><font size="1">Co-Chair - TCG Trusted Mobility Solutions WG</font></i></div><div><i><font size="1">Co-Chair - TCG Metadata Access Protocol SG<br></font></i></div><div dir="ltr"><i><font size="1">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 & 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>(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434</font></i></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 17, 2020 at 3:36 PM Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Smith,</div><div><br></div><div>Crossed wires here.</div><div><br></div><div>All US NIST documents (FIPS, SP800, SP500, etc.) are free and have durable URLs.</div><div>I think there was a delusion that, because of *not* using the equivalent ISO specs</div><div>(which are behind paywalls), we needed to shift to IETF RFCs. Since our references</div><div>are specifically relative to hash algorithms or encryption algorithms, I suggest that we</div><div>should have both US NIST and IETF references to free standards. NIST has written</div><div>about implementation details much more deeply for most hash algorithms (i.e., I would</div><div>not want to implement based only on the IETF RFCs).</div><div><br></div><div>I'll look at your IPP standard draft for the details and recommend (probably) a few more</div><div>US NIST standards (updated ones) and associated IETF RFCs.</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div><br></div><div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><i><font size="1">Ira McDonald (Musician / Software Architect)</font></i></div><div><i><font size="1">Chair - SAE Trust Anchors and Authentication TF<br></font></i></div><div dir="ltr"><i><font size="1">Co-Chair - TCG Trusted Mobility Solutions WG</font></i></div><div><i><font size="1">Co-Chair - TCG Metadata Access Protocol SG<br></font></i></div><div dir="ltr"><i><font size="1">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 & 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>(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434</font></i></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 17, 2020 at 3:17 PM Kennedy, Smith (Wireless & IPP Standards) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Ira,<br>
<br>
Can you suggest specifications that we might reference for the hashing algorithm keywords defined for "job-password-encryption"? We currently reference FIPS180-4 and FIPS202 but it was suggested that those were not suitable as references in a PWG specification, because of inaccessibility because of paywalls, etc.<br>
<br>
Thanks for any help!<br>
<br>
Smith<br>
<br>
/**<br>
Smith Kennedy<br>
HP Inc.<br>
*/<br>
<br>
</blockquote></div>
</blockquote></div>