attachment-0001
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1336223669;
mso-list-type:hybrid;
mso-list-template-ids:-2135390118 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Ira et al,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A few thoughts.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If I get it correctly, the change is in:<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:14.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>a.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Suggesting
that IPP Everywhere will need new operations as well as attributes (I think we
all expected that)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span style='font-size:14.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><span style='mso-list:Ignore'>b.<span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Documenting
these new operations and attributes in yet another IPP Extension document
rather than in the IPP Everywhere specification, with the intent of making
these additions available to other IPP implementations as well.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>My first reaction (indeed when it was first proposed) was that a
charter change is really not necessary. You are now doing the same thing in
three steps rather than two. But I understand that there may be some who will
cry that the additional document exceeds that permitted by the charter.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>However, with the additional Extension Set 3 identifying
operations and attributes needed for IPP Everywhere, it would seem that
logically one must establish extension set 3 before the IPP Everywhere spec. For
example, the new goal ’c’ should be stated second, and the IPP
Everywhere Definition should refer to Extension Set 3 as well as the IPP/2.0
Specification and other documents.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Finally, unless there is a new IPP/X.X specification, (I don’t
think a third edition would be a reasonable approach…I am seeing much
confusion with IPP/2.0 Second Edition), there would be no standard tying
Extension set 3 into non IPP Everywhere implementations. Actually, I thought the
idea of holding off six months on IPP/2.0 Second Edition and including Extension
Set 3 was a good idea. At this point, we are losing the objective of
having a single cohesive IPP document defining compliance.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bill Wagner<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sc-bounces@pwg.org
[mailto:sc-bounces@pwg.org] <b>On Behalf Of </b>Ira McDonald<br>
<b>Sent:</b> Monday, September 27, 2010 6:07 PM<br>
<b>To:</b> PWG Steering Committee; Ira McDonald<br>
<b>Subject:</b> Fwd: [SC] Revised IPP Everywhere Charter (27 Sept 2010)<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Hi PWG SC folks,<br>
<br>
Please take a look right away at this slightly revised IPP <br>
Everywhere charter (see note w/ change log below).<br>
<br>
For review and approval at *this* Thursday's SC meeting.<br clear=all>
<br>
Cheers,<br>
- Ira<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>---------- Forwarded message ----------<br>
From: <b>Ira McDonald</b> <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>><br>
Date: Mon, Sep 27, 2010 at 6:04 PM<br>
Subject: Revised IPP Everywhere Charter (27 Sept 2010)<br>
To: <a href="mailto:ipp@pwg.org">ipp@pwg.org</a>, Michael R Sweet <<a
href="mailto:msweet@apple.com">msweet@apple.com</a>>, Ira McDonald <<a
href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>><br>
<br>
<br>
Hi,<br>
<br>
Per my action at today's IPP WG teleconference, a revised draft of<br>
the IPP Everywhere charter is available at:<br>
<br>
<a
href="ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20100927.pdf"
target="_blank">ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippeverywhere-charter-20100927.pdf</a>
/ doc<br>
- with line numbers and redlines from July approved version<br>
<br>
Please send comments promptly!<br>
<br>
The PWG Steering Committee plans to approve this revised charter<br>
at their meeting this Thursday 30 September.<br>
<br>
Cheers,<br>
- Ira (IPP co-editor)<br>
<br clear=all>
-------------------------------<br>
Change Log<br>
<br>
- Changed Status from Approved back to Stable Draft<br>
- Changed filename and directory path according<br>
- Added a third specification IPP Job and Printer Extensions - Set 3 (JPS3)<br>
- Revised OBJ-4 to reference new OBJ-8 below<br>
- Added OBJ-8 to define IPPS URI Scheme (IPP over HTTPS)<br>
- Added OBJ-9 to define IPP access to SNMP MIBs<br>
- Added CH-4 and CH-5 new Milestones (revise charter)<br>
- Added JPS3-1 and JPS3-2 new Milestones (write JPS3)<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>,
and is <br>
believed to be clean. <o:p></o:p></p>
</div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>
</html>