attachment
<div dir="ltr"><div><div><div><div><div><div><div>Hi Mike,<br><br></div>You're right. Lost my mind.<br><br>Handle them w/ new values for existing attributes (same way <br>we handle Printer MIB TC updates for existing datatypes).<br>
</div></div><br></div>So we need to work out that process (I agree with you that a <br></div>durable pointer into the PWG email archives is sufficient).<br><br></div>Cheers,<br></div>- Ira<br><br></div><div class="gmail_extra">
<br clear="all"><div><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 & 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>
<br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 4:17 PM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Ira,<div><br><div><div class="im"><div>On Dec 9, 2013, at 3:04 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite">
<div dir="ltr"><div><div><div><div><div><div><div><div>Hi Mike,<br><br></div>I like your clarifications as suggested.<br><br></div>Are you suggesting a *tiny* document that updates JPS3 and extends<br></div>Identify-Printer?<br>
</div></div></div></div></div></div></blockquote><div><br></div></div>No, I really don't want to open up that can of worms.</div><div class="im"><div><br><blockquote type="cite"><div dir="ltr"><div><div><div><div>It seems like it would be nice to handle this as a minor release update<br>
</div>to JPS3 (so that everyone sees it). I know, process...process. But this<br></div>seems like the cleaner fix to me.<br></div></div></div></blockquote><div><br></div></div></div><div>I know I don't have the cycles or the energy to update JPS3 right now. Given our recent move to start accepting value registrations on the mailing list (with the mailing list serving as the durable source of information), I was hoping we could simply treat these as new value registrations for existing attributes and do the registration. Both attributes are type2 and permit extension without full standards backing them...</div>
<div class="im"><div><br></div><div>
<div style="text-indent:0px;letter-spacing:normal;text-align:start;text-transform:none;white-space:normal;word-wrap:break-word;word-spacing:0px">_______________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
</div>
</div>
<br></div></div></div></blockquote></div><br></div>