attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Ira,<div><br><div><div><div>On Dec 9, 2013, at 5:36 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr"><div><font color="#000000">...</font></div><div>I also don't think that System Control Service should get into this business<br></div><div>- or maybe I'm crazy and that actually is the *right* place? Should SCS,<br>
</div><div>rather than an individual service, be the target of this device-level operation?<br></div></div></blockquote><div><br></div>I don't think so. Clients are talking to a particular service, not generally the system control service. Sending an Identify-Printer means "identify the device(s) used by this service".</div><div><br></div><div><blockquote type="cite"><div dir="ltr"><div>Someday, we need a lightweight IPP registration for whole new attributes<br></div><div>(in an existing attribute group), I suspect.<br></div></div></blockquote><div><br></div>Technically that process is defined in RFC 2911 as "submit a registration through the IANA web site", which lands the registration in our hands. And of course WG discussion, just as we do for MIB registrations.</div><div><br></div><div>However, PWG Process/3.0 already provides us with the required process for us (vs. the IETF):</div><div><br></div><div>
<div class="page" title="Page 16">
<div class="layoutArea">
<div class="column">
<ol start="0" style="list-style-type: none">
<li><p><span style="font-size: 11.000000pt; font-family: 'Arial'; font-weight: 700">9.2 Registration of Keywords and Values
</span></p><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">Proposals for registrations of new keywords and values for existing elements shall follow the following process:
</span></p>
<ol style="list-style-type: none">
<li><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">1) Each Working Group will appoint a Maintenance Editor for their PWG Standard.
</span></p>
</li>
<li><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">2) Anyone can initiate a proposal by starting an e-mail discussion on the appropriate Working Group mailing list or
submitting a Technical Brief describing the request.
</span></p>
</li>
<li><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">3) After there is general agreement on the mailing list for the proposal, the Working Group Chair or the proposer
issues a Call for Objection (see below) on the pwg-announce mailing list with a description of the proposal that
includes:
</span></p>
<ul style="list-style-type: none">
<li><p><span style="font-size: 10.000000pt; font-family: 'SymbolMT'">⎯ </span><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">A description of the requirement being met or the problem being solved.
</span></p>
</li>
<li><p><span style="font-size: 10.000000pt; font-family: 'SymbolMT'">⎯ </span><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">A description of the proposed solution.
</span></p>
</li>
<li><p><span style="font-size: 10.000000pt; font-family: 'SymbolMT'">⎯ </span><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">A detailed description of the changes to the standard or schemas which are proposed to be integrated into the
standard at a future date.
</span></p>
</li>
</ul>
</li>
</ol>
</li>
</ol></div>
</div>
</div></div></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div><div><div class="page" title="Page 16"><div class="layoutArea"><div class="column"><p><span style="font-family: TimesNewRomanPSMT; font-size: 10pt;">4) To make the status of proposed registrations clear to PWG participants and others, the Working Group Chair will
ensure that approved registrations are documented in the following Working Group directory:</span></p></div></div></div></div></div></div></blockquote></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div><div class="page" title="Page 17"><div class="layoutArea"><div class="column"><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'"><a href="ftp://ftp.pwg.org/pub/pwg/[working">ftp://ftp.pwg.org/pub/pwg/[working</a> group]/approved-addenda
</span></p></div></div></div></div></div></blockquote></blockquote></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div><div class="page" title="Page 17"><div class="layoutArea"><div class="column"><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">where [working group] is the project acronym. When the standard is revised and re-approved, any relevant
registrations or extensions that were included in the revision will be removed from the addenda directory.
</span></p></div></div></div></div></div></blockquote></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div><div class="page" title="Page 17"><div class="layoutArea"><div class="column"><p><span style="font-size: 11.000000pt; font-family: 'Arial'; font-weight: 700">9.3 Registration of New Operations and Semantic Elements
</span></p></div></div></div></div></div><div><div><div class="page" title="Page 17"><div class="layoutArea"><div class="column"><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">Proposals for registration or extension of a standard to include new operations or semantic elements for existing groups shall
adhere to the following process:
</span></p></div></div></div></div></div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">1) Anyone can initiate a proposal by submitting a Technical Brief to the appropriate Working Group describing the
registration or extension. The Technical Brief should be able to function as a complete, standalone technical
description of the proposed extension with formal references to the relevant standard.</span></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">2) After there is general agreement in the Working Group, the Working Group Chair will issue a Last Call for
comments on the proposal. Upon successful Last Call completion, the Working Group Chair may issue a Call for
Objection on the pwg-announce mailing list or continue with PWG Formal Approval for a Technical Brief.</span></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">3) To make the existence and status of the approved Technical Brief clear to PWG participants and others, the
Working Group Chair will ensure that approved registrations are documented in the following Working Group
directory: <a href="ftp://ftp.pwg.org/pub/pwg[working">ftp://ftp.pwg.org/pub/pwg[working</a> group]/approved-addenda, where [working group] is the project
acronym.
</span></blockquote></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div><div class="page" title="Page 17"><div class="layoutArea"><div class="column"><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">When the standard is revised and re-approved, any relevant registrations or extensions that were included in the revision will be
removed from the addenda directory.
</span></p></div></div></div></div></div><div><div><div class="page" title="Page 17"><div class="layoutArea"><div class="column"><p><span style="font-size: 11.000000pt; font-family: 'Arial'; font-weight: 700">9.4 Compatible Extension of a Standard that Includes Major New Element Groups or Objects
</span></p></div></div></div></div></div><div><div><div class="page" title="Page 17"><div class="layoutArea"><div class="column"><p><span style="font-size: 10.000000pt; font-family: 'TimesNewRomanPSMT'">Any extension to a PWG standard that includes the addition of major new element groups or objects will be treated as a revision
of the standard and shall follow the Formal PWG Standards-track Process. </span></p></div></div></div></div></div></blockquote><div><div><br></div><div>_______________________________________________________________</div><div apple-content-edited="true"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div>
</div>
<br></div></body></html>