attachment
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for the feedback, Mike. I'd love to hear from some others in the group as well. </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif" dir="ltr" id="divtagdefaultwrapper">
</div>
<div style="direction: ltr; font-family: wf_segoe-ui_semibold, "Segoe UI Semibold", "Segoe WP Semibold", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif, serif, EmojiFont; font-size: 15px; color: rgb(33, 33, 33);">
<span style="font-family: arial, Helvetica, sans-serif; font-size: 13px; color: rgb(50, 50, 60);"><b>Jeremy Leber</b></span><br>
<span style="font-family: arial, Helvetica, sans-serif; font-size: 13px; color: rgb(50, 50, 60);">Product Owner, Connectivity Firmware</span></div>
<div style="direction: ltr; font-family: arial, Helvetica, sans-serif; font-size: 13px; color: rgb(50, 50, 60);">
Chair, IEEE-ISTO Printer Working Group</div>
<div style="direction: ltr; font-family: arial, Helvetica, sans-serif; font-size: 13px; color: rgb(50, 50, 60);">
<br>
</div>
<div style="direction: ltr; font-family: wf_segoe-ui_semibold, "Segoe UI Semibold", "Segoe WP Semibold", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif, serif, EmojiFont; font-size: 15px; color: rgb(33, 33, 33);">
<span style="font-family: arial, Helvetica, sans-serif; font-size: 10px; color: rgb(28, 100, 180);"><b>O</b></span><span style="font-family: arial, Helvetica, sans-serif; font-size: 13px; color: rgb(50, 50, 60);">
</span><span style="font-family: arial, Helvetica, sans-serif; font-size: 12px; color: rgb(50, 50, 60);">+1 859 825-4505</span><br>
<span style="font-family: arial, Helvetica, sans-serif; font-size: 12px;"><a href="mailto:jeremy.leber@lexmark.com" target="_blank">jeremy.leber@lexmark.com</a></span></div>
<div style="direction: ltr; font-family: wf_segoe-ui_semibold, "Segoe UI Semibold", "Segoe WP Semibold", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif, serif, EmojiFont; font-size: 15px; color: rgb(33, 33, 33);">
<span style="font-family: arial, Helvetica, sans-serif; font-size: 12px; background-color: rgb(255, 255, 255);"><a href="mailto:jeremy.leber@lexmark.com" target="_blank" style="margin: 0px; background-color: rgb(255, 255, 255);">chair@pwg.org</a></span><br>
<br>
<span style="font-family: arial, Helvetica, sans-serif; font-size: 13px;"><a href="http://www.lexmark.com/" target="_blank"><img src="http://www.lexmark.com/common/images/email/lexmark-logo-email-signature.png"></a></span><br>
<span style="font-family: arial, Helvetica, sans-serif; font-size: 12px;"><a href="http://www.lexmark.com/" target="_blank">www.lexmark.com</a></span></div>
</div>
<div id="appendonsend"></div>
<br>
<p style="font-family:Calibri;font-size:10pt;color:#000000;margin:5pt;font-style:normal;font-weight:normal;text-decoration:none;" align="Center">
Lexmark Confidential<br>
</p>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> ids <ids-bounces@pwg.org> on behalf of Michael Sweet via ids <ids@pwg.org><br>
<b>Sent:</b> Tuesday, September 17, 2024 9:49 AM<br>
<b>To:</b> ISTO-PWG Imaging Device Security workgroup discussion forum <ids@pwg.org><br>
<b>Cc:</b> Michael Sweet <msweet@msweet.org><br>
<b>Subject:</b> Re: [IDS] IDS WG Meetings</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Alan,<br>
<br>
> On Sep 16, 2024, at 3:59 PM, Alan Sukert via ids <ids@pwg.org> wrote:<br>
> ...<br>
> So, I'd like to here back from you - the people of the IDS reflector and on this DL -by this Wednesday your choice of the following three options:<br>
> • Maintain the regular IDS WG Meetings for now. We would have a meeting this Thursday at the normal time of 3PM ET / 12 N PT. The agenda would be a review of the recent HCD iTC and HIT Meetings and a special topic that is currntly TBD,<br>
> • Have a special IDS WG Meeting this Thursday at the at the normal time of 3PM ET / 12 N PT. The sole topic would be an open discussion of the future of IDS and where it should be going.<br>
> • Stop having the IDS WG Meetings every two weeks and just have the IDS Session at the PWS Face-to-Face Meetings. The PWG SC can determine when to restart the IDS WG Meetings<br>
> Please let me know what your thoughts are here. If I don't here anything I will assume it is business as usual and go with Option 1. Below is the link to the meeting if we do have it.<br>
<br>
Except for the time that Joe Murdock roped me into doing the IDS Common Log spec I've only ever participated at the IDS F2F meetings. I have no skin in the HCD iTC game, so while I understand its importance I can't really say whether stopping regular IDS meetings
will hurt/affect that effort.<br>
<br>
I *do* think that we need the IDS WG to stick around because IPP ultimately depends on it as a resource for all things security - we've adopted a number of properties/elements from the IDS Attributes spec and use IDS log for anything requiring a log. Plus
Smith's latest firmware update registration and "strong identity" work will likewise depend on IDS or IDS-endorsed solutions/specifications/standards.<br>
<br>
*If* concall attendance is an issue, there is no sense you wasting your time as chair to prepare for and hold a call every two weeks. *If* there is an urgent topic that requires discussion, call a special meeting during the IDS time slot when you know the
interested parties will attend. The key is to have a place/time for printing security professionals to be able to get together to discuss things and inform/guide the PWG at-large.<br>
<br>
In short, I guess I'm saying that I, as an IPP WG officer and former PWG chair, prefer option 3 to keep IDS alive but reduce unnecessary meetings for you.<br>
<br>
________________________<br>
Michael Sweet<br>
<br>
</div>
</span></font></div>
</body>
</html>