Ira,
After reading through this, I’d say we have already adopted a user-centric view - we engage with our user community through trade shows and other organizations (e.g., OpenPrinting) that represent the users of our standards work, and our most recent privacy and accounting documents clearly put the privacy and explicit consent of end users front and center. And clearly we have several client implementations that do not need vendor specific software (as opposed to other IoT protocols/technologies)
Certainly there are improvements we can make, but I think we already are pointed in the “right” direction...
Sent from my iPhone
> On Dec 4, 2020, at 11:37 AM, Ira McDonald via ipp <ipp at pwg.org> wrote:
>>
> Hi,
>> From the IAB (Internet Architecture Board) in August 2020:
>>https://tools.ietf.org/html/rfc8890>>https://icannwiki.org/Internet_Architecture_Board>> Just referenced in a fascinating thread on the TLS mailing list. An interesting
> and provocative position.
>> If the IAB believes End User concerns and requirements should trump other
> considerations in IETF standards, perhaps the PWG should also consider this
> perspective in developing PWG standards for networked Imaging Systems?
>> 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 WG
> Secretary - IEEE-ISTO Printer Working Group
> Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
> IETF Designated Expert - IPP & Printer MIB
> Blue Roof Music / High North Inc
>http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc> mailto: blueroofmusic at gmail.com> (permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434
> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20201204/27576549/attachment.html>