Hi Smith,
I'm working on the IETF RFC references and checking the US NIST references
for the hash algorithms in Table 10 of EPX.
I downloaded the MS Word source "wd-ippepx20-20201029.docx" just now. My
copy of MS Word 2019 cannot open it - says it contains "unreadable" content
and
suggests a recovery attempt - I didn't try it.
OTOH, the MS Word source "wd-ippepx20-20201029-rev.docx" does open OK
without warnings.
I'm not sure what version of MS Word you're using or what OS platform. But
the
source of the eventual published version needs to be stable and readable for
future maintenance.
More later on the hash algorithm references.
Cheers,
- Ira
*Ira McDonald (Musician / Software Architect)*
*Chair - SAE Trust Anchors and Authentication TF*
*Co-Chair - TCG Trusted Mobility Solutions WG*
*Co-Chair - TCG Metadata Access Protocol SG*
*Chair - Linux Foundation Open Printing WGSecretary - IEEE-ISTO Printer
Working GroupCo-Chair - IEEE-ISTO PWG Internet Printing Protocol WGIETF
Designated Expert - IPP & Printer MIBBlue Roof Music / High North
Inchttp://sites.google.com/site/blueroofmusic
<http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc
<http://sites.google.com/site/highnorthinc>mailto: blueroofmusic at gmail.com
<blueroofmusic at gmail.com>(permanent) PO Box 221 Grand Marais, MI 49839
906-494-2434*
On Thu, Dec 17, 2020 at 3:36 PM Ira McDonald <blueroofmusic at gmail.com>
wrote:
> Hi Smith,
>> Crossed wires here.
>> All US NIST documents (FIPS, SP800, SP500, etc.) are free and have durable
> URLs.
> I think there was a delusion that, because of *not* using the equivalent
> ISO specs
> (which are behind paywalls), we needed to shift to IETF RFCs. Since our
> references
> are specifically relative to hash algorithms or encryption algorithms, I
> suggest that we
> should have both US NIST and IETF references to free standards. NIST has
> written
> about implementation details much more deeply for most hash algorithms
> (i.e., I would
> not want to implement based only on the IETF RFCs).
>> I'll look at your IPP standard draft for the details and recommend
> (probably) a few more
> US NIST standards (updated ones) and associated IETF RFCs.
>> Cheers,
> - Ira
>>> *Ira McDonald (Musician / Software Architect)*
>> *Chair - SAE Trust Anchors and Authentication TF*
> *Co-Chair - TCG Trusted Mobility Solutions WG*
>> *Co-Chair - TCG Metadata Access Protocol SG*
>>>>>>>>> *Chair - Linux Foundation Open Printing WGSecretary - IEEE-ISTO Printer
> Working GroupCo-Chair - IEEE-ISTO PWG Internet Printing Protocol WGIETF
> Designated Expert - IPP & Printer MIBBlue Roof Music / High North
>Inchttp://sites.google.com/site/blueroofmusic> <http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc> <http://sites.google.com/site/highnorthinc>mailto: blueroofmusic at gmail.com> <blueroofmusic at gmail.com>(permanent) PO Box 221 Grand Marais, MI 49839
> 906-494-2434*
>>> On Thu, Dec 17, 2020 at 3:17 PM Kennedy, Smith (Wireless & IPP Standards) <
>smith.kennedy at hp.com> wrote:
>>> Hi Ira,
>>>> 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.
>>>> Thanks for any help!
>>>> Smith
>>>> /**
>> Smith Kennedy
>> HP Inc.
>> */
>>>>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20201221/8f219bc1/attachment.html>