From pwg-announce-owner@pwg.org  Mon Mar  3 07:05:55 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8ECEA3A68C4;
	Mon,  3 Mar 2008 07:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.631
X-Spam-Level: 
X-Spam-Status: No, score=0.631 tagged_above=-999 required=5 tests=[AWL=0.371,
	BAYES_20=-0.74, HTML_MESSAGE=1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IDkGQB04R-yh; Mon,  3 Mar 2008 07:05:50 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 05E6F3A69A3;
	Mon,  3 Mar 2008 07:05:49 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m23F5ZMd027299;
	Mon, 3 Mar 2008 10:05:37 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m23F5ZVU027296;
	Mon, 3 Mar 2008 10:05:35 -0500
Received: by pwg.org (bulk_mailer v1.13); Mon, 3 Mar 2008 10:03:38 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m23F3YON026758
	for <pwg-announce-out@pwg.org>; Mon, 3 Mar 2008 10:03:36 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m23F3Y4B026755
	for pwg-announce-out; Mon, 3 Mar 2008 10:03:34 -0500
To: pwg-announce@pwg.org
Subject: PWG-ANNOUNCE> April 16-18, 2008 Face to Face meeting reminder 
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF77D31618.5B10E36F-ON85257401.005276DF-85257401.00528609@lexmark.com>
From: thrasher@lexmark.com
Date: Mon, 3 Mar 2008 10:03:27 -0500
X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark(Release 6.5.5|November 30, 2005) at
 03/03/2008 10:03:29,
	Serialize complete at 03/03/2008 10:03:29
Content-Type: multipart/alternative; boundary="=_alternative 0052860385257401_="
Sender: owner-pwg-announce@pwg.org

This is a multipart message in MIME format.
--=_alternative 0052860385257401_=
Content-Type: text/plain; charset="US-ASCII"

The agenda for the April 16-18 is now set and available at the link below.

Please make your hotel arrangements and register through the ISTO ASAP.

BTW, so only two people have registered for the meeting.....in a couple of 
weeks
this becomes a HUGE problem for the PWG.


Jerry Thrasher
PWG Chair
Senior Engineer, WW Corporate Standards
Lexmark International Inc.
Ph:859-825-4056, Fax:859-232-7628
Email:thrasher(at)lexmark(dot)com
----- Forwarded by Jerry Thrasher/Lex/Lexmark on 03/03/2008 09:58 AM -----

Jerry Thrasher/Lex/Lexmark 
02/19/2008 10:08 AM

To
pwg-announce@pwg.org
cc

Subject
April 16-18, 2008 Face to Face meeting reminder





Reminder that the April 16-18, F2F meeting (IEEE P2600 meetings on April 
14-15) is being held
at a hotel venue and not hosted by a PWG member company. Hence those 
attending need
to deal with registration pages, hotel block cut-off dates etc.

The detailed agenda for this meeting will posted soon, but for those 
members that plan to attend
the entire session, I encourage you to go ahead and make your hotel 
arrangements, registration
etc. ASAP.  The cut-off date for the PWG/P2600 hotel block is March 21.

The following link has details on the registration, and a link to the 
hotel reservation page specifically
set up for the PWG:

http://www.pwg.org/chair/meeting-info/April_2008_Phoenix.html

Jerry Thrasher
Senior Engineer, WW Corporate Standards
Lexmark International Inc.
Ph:859-825-4056, Fax:859-232-7628
Email:thrasher(at)lexmark(dot)com
--=_alternative 0052860385257401_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">The agenda for the April 16-18 is now
set and available at the link below.</font>
<br>
<br><font size=2 face="sans-serif">Please make your hotel arrangements
and register through the ISTO ASAP.</font>
<br>
<br><font size=2 face="sans-serif">BTW, so only two people have registered
for the meeting.....in a couple of weeks</font>
<br><font size=2 face="sans-serif">this becomes a HUGE problem for the
PWG.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Jerry Thrasher</font>
<br><font size=2 face="sans-serif">PWG Chair<br>
Senior Engineer, WW Corporate Standards<br>
Lexmark International Inc.<br>
Ph:859-825-4056, Fax:859-232-7628<br>
Email:thrasher(at)lexmark(dot)com</font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Jerry
Thrasher/Lex/Lexmark on 03/03/2008 09:58 AM -----</font>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Jerry Thrasher/Lex/Lexmark</b>
</font>
<p><font size=1 face="sans-serif">02/19/2008 10:08 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">pwg-announce@pwg.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">April 16-18, 2008 Face to Face meeting
reminder</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br><font size=2 face="sans-serif">Reminder that the April 16-18, F2F meeting
(IEEE P2600 meetings on April 14-15) is being held</font>
<br><font size=2 face="sans-serif">at a hotel venue and not hosted by a
PWG member company. Hence those attending need</font>
<br><font size=2 face="sans-serif">to deal with registration pages, hotel
block cut-off dates etc.</font>
<br>
<br><font size=2 face="sans-serif">The detailed agenda for this meeting
will posted soon, but for those members that plan to attend</font>
<br><font size=2 face="sans-serif">the entire session, I encourage you
to go ahead and make your hotel arrangements, registration</font>
<br><font size=2 face="sans-serif">etc. ASAP. &nbsp;The cut-off date for
the PWG/P2600 hotel block is March 21.</font>
<br>
<br><font size=2 face="sans-serif">The following link has details on the
registration, and a link to the hotel reservation page specifically</font>
<br><font size=2 face="sans-serif">set up for the PWG:</font>
<br>
<br><font size=2 face="sans-serif">http://www.pwg.org/chair/meeting-info/April_2008_Phoenix.html</font>
<br>
<br><font size=2 face="sans-serif">Jerry Thrasher<br>
Senior Engineer, WW Corporate Standards<br>
Lexmark International Inc.<br>
Ph:859-825-4056, Fax:859-232-7628<br>
Email:thrasher(at)lexmark(dot)com</font>
--=_alternative 0052860385257401_=--


From pwg-announce-owner@pwg.org  Mon Mar  3 07:51:14 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 867A83A6858;
	Mon,  3 Mar 2008 07:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5Hmbu0dlDWQE; Mon,  3 Mar 2008 07:51:12 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 7ECE728C10A;
	Mon,  3 Mar 2008 07:51:12 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m23Fp0Tj004614;
	Mon, 3 Mar 2008 10:51:02 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m23Fp0gX004611;
	Mon, 3 Mar 2008 10:51:00 -0500
Received: by pwg.org (bulk_mailer v1.13); Mon, 3 Mar 2008 10:49:19 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m23FnHM3004028
	for <pwg-announce-out@pwg.org>; Mon, 3 Mar 2008 10:49:19 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m23FnHMJ004024
	for pwg-announce-out; Mon, 3 Mar 2008 10:49:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
        bh=Mp4xKADqCzhL61E90mPEUBAPBUKpUcoS7UmbR58bGcA=;
        b=iFRJZVkESWFNnwRDI9RkYjpOHMG83BSj7mEK/eYLvVZ6mc60EveNQWY7vtmkOrxh7zMFfZtIeO9bBcsNUXlNmSWI8RKeVRg/WTy+m3tEQjD3oj0H31Qn4/XK8tQ0miCAmpc1Z9zBls1gSDQN0kj2R06yPxdla5ojt+0kU6R6TjA=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=aSVQ9mg6KnNNomp7o8TFCXu1tuAkOTXnY0EK2n6iotPa6Adcz6AIOFQU2u6xrHVgqnClvaWoZlA8g3QNqjBdSe9A9upCWIiS3/4y/qXB5KDPkIGZWHZ1RIrs+AYUd2B4oOqx9WMCD0zuQpYS+C8w5Bf4biA4rPNf3UQmM73ql/M=
Message-ID: <e395be80803030744y3bd6c695jc7e23fa30f0c388b@mail.gmail.com>
Date: Mon, 3 Mar 2008 10:44:12 -0500
From: "Ira McDonald" <blueroofmusic@gmail.com>
To: "Harry Lewis" <harryl@us.ibm.com>,
        "Ira McDonald" <blueroofmusic@gmail.com>
Subject: PWG-ANNOUNCE> Ends Tue 18 March - Vote on Imaging State & Counter MIB v2
Cc: pwg-announce@pwg.org
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id m23FnG6Z004019
Sender: owner-pwg-announce@pwg.org

Hi,

Weekly reminder - please cast your company's vote on the
Counter MIB v2.

Thanks,
- Ira (editor of Counter MIB)

On Fri, Feb 22, 2008 at 1:14 PM, Harry Lewis <harryl@us.ibm.com> wrote:
>
> PWG Formal Approval commencement for the Imaging State & Counter MIB v2 –
> Voting ends Tuesday March 18, 2008
>
> On Feb 21, 2008 the PWG Steering Committee approved WIMS working group Last
> Call exit for the Imaging State & Counter MIB v2. At the request of the WIMS
> working group Chairman, Bill Wagner – TIC, and according to my duties as
> Secretary of the PWG, I hereby initiate the Formal Approval process for
> advancing this work product to PWG Candidate Standard.
>
> Formal Approval occurs by vote of the PWG membership. The voting period will
> open on Monday February 25, 2008 and close at 10PM (Pacific Time) on Tuesday
> March 18, 2008.
>
> Valid votes are: Yes, No, No (with strong objection), Abstain.
>
> Any No vote requires that the voter state the reason for the No vote and a
> description of the changes required for turning the No vote to a Yes.
>
> Representatives from PWG member companies are strongly encouraged to submit
> a vote.
>
> To cast a vote, please send an email with the following subject line format:
>
> "Counter MIB v2 Formal Vote-<company name>-<last name of
> voter>-<yes/no/abstain>"
>
> Example: Counter MIB v2 Formal Vote-InfoPrint-lewis-yes
>
> No votes MUST contain a reason in the body of the email.
>
> Please send your vote to the following email addresses:
>  (Replacing "dot" with . and "at" with @):
>
> thrasher"at"lexmark"dot"com
>  wamwagner"at"comcast"dot"net
>  harryl"at"us"dot"ibm"dot"com
>
> REFERENCE MATERIAL
>
> Because there were no last call comments, there is no need for a LCRC
> document or for a revision of the document put up for last call. The
> document is at
> ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.pdf.
>
> Associated documents that assist in understanding the primary document are:
> ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.mib
> - Plaintext ASN.1 MIB
> ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123-mib.pdf
> - Color highlighted ASN.1 MIB
> These MIB documents are not normative and are not in themselves to be voted
> on. However, the WIMS working group would welcome any comments members would
> like to make on these ancillary documents.
>
> Specific information on the changes from the previously approved
> informational document was presented at the February Plenary, and is
> available at
> ftp://ftp.pwg.org/pub/pwg/wims/white/wims-countmib20-pwg-last-call-20080207.pdf.
>
> Note:
>  The PWG Definition of the Standards Development Process Version 2.0
>  located at:
>
> ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf
>
> A list of Primary and Alternate representatives from PWG member companies
> will be provided to the working group chair in case "reminder" notices are
> necessary to meet the voting requirements listed in the process document.
>
> Harry Lewis
>
> PWG Secretary
>
>
>  Harry Lewis
>  Program Manager - Intellectual Property & Standards
>  Phone: 303-924-5337
>  e-mail: harryl@us.ibm.com
>  infoprint.com
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434



From pwg-announce-owner@pwg.org  Tue Mar  4 06:44:00 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1D0F13A68DF;
	Tue,  4 Mar 2008 06:44:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.411
X-Spam-Level: 
X-Spam-Status: No, score=0.411 tagged_above=-999 required=5 tests=[AWL=0.590,
	BAYES_00=-2.599, HTML_MESSAGE=1, SARE_GIF_ATTACH=1.42]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id GAXW9-afjvBm; Tue,  4 Mar 2008 06:43:47 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 722373A6F08;
	Tue,  4 Mar 2008 06:43:37 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m24EhOlZ009835;
	Tue, 4 Mar 2008 09:43:26 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m24EhO7f009832;
	Tue, 4 Mar 2008 09:43:24 -0500
Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Mar 2008 09:41:23 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m24EfJHq009314
	for <pwg-announce-out@pwg.org>; Tue, 4 Mar 2008 09:41:21 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m24EfJwx009311
	for pwg-announce-out; Tue, 4 Mar 2008 09:41:19 -0500
X-Authority-Analysis: v=1.0 c=1 a=CZyEzZ738CUA:10 a=51RRrcYvAAAA:8
 a=M-8pqlsqAAAA:8 a=vHGh4_OLkVCYkJTdW5sA:9 a=K99pZHwzP_d_00tfxJcA:7
 a=UM7sbQsQI2MmEA1_EJTBuCOF1tAA:4 a=516orNCffQoA:10 a=dWlHpMHThpAA:10
 a=Fvp7veO-YfEA:10 a=k2hRk6oQ7VkA:10 a=eq2vAplpWwkA:10 a=4l0bdYPz_H0A:10
 a=XF7b4UCPwd8A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=gtWjicfJkoAQ7BdQgN4A:9
 a=uQkVTuYhPycwnof8aoEA:7 a=mwchexkN-cmFCI5NptHvSkN9lY0A:4 a=dcp46DZ-3hIA:10
 a=37WNUvjkh6kA:10 a=XzfvRcsXm3CLQWlxceAA:9 a=-_4TS1h0NtEL9UP_eMY4kyUOMnoA:4
 a=1Vq_FK4TplAA:10 a=CxA2Utj4LuEA:10 a=J0QQm793ZazUCAUsCP0A:9
 a=EqZJtLFTDleTJ1kt:18 a=b51SsU6wOJQQPAgM:18 a=s1dN97_79NHBPn_Q:18
From: "William A Wagner" <wamwagner@comcast.net>
To: <pwg-announce@pwg.org>
References: <OFA2AC0281.F228E239-ON872573F7.0069DD13-872573F7.006450E1@us.ibm.com>
In-Reply-To: <OFA2AC0281.F228E239-ON872573F7.0069DD13-872573F7.006450E1@us.ibm.com>
Subject: RE: PWG-ANNOUNCE> PWG Formal Approval commencement for the Imaging State & Counter MIB v2
Date: Tue, 4 Mar 2008 09:38:57 -0500
Message-ID: <001401c87e05$7be153c0$73a3fb40$@net>
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0015_01C87DDB.930B4BC0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ach1krVzF5Ca8g/jQ/uGzhGyEC2JxAIcSaag
Content-Language: en-us
Sender: owner-pwg-announce@pwg.org

This is a multipart message in MIME format.

------=_NextPart_000_0015_01C87DDB.930B4BC0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0016_01C87DDB.930B4BC0"


------=_NextPart_001_0016_01C87DDB.930B4BC0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

This is just to remind PWG members that balloting for advancement of the
Imaging State & Counter MIB v2 is in progress. This MIB was originally
approved as a binding of the Counter Spec. It has recently been upgraded to
include Imaging state information, in lieu of generating an additional MIB
for MFD/MFP state reporting. It has been prototyped by Samsung, some text
has been clarified, and has gone though PWG last call with no comments.

 

If possible, please give some time to considering this specification and
cast your vote.

 

Many thanks.

 

Bill Wagner, CoChairman, WIMS WG 

 

From: owner-pwg-announce@pwg.org [mailto:owner-pwg-announce@pwg.org] On
Behalf Of Harry Lewis
Sent: Friday, February 22, 2008 1:14 PM
To: pwg-announce@pwg.org
Subject: PWG-ANNOUNCE> PWG Formal Approval commencement for the Imaging
State & Counter MIB v2

 


PWG Formal Approval commencement for the Imaging State & Counter MIB v2 -
Voting ends Tuesday March 18, 2008 

On Feb 21, 2008 the PWG Steering Committee approved WIMS working group Last
Call exit for the Imaging State & Counter MIB v2. At the request of the WIMS
working group Chairman, Bill Wagner - TIC, and according to my duties as
Secretary of the PWG, I hereby initiate the Formal Approval process for
advancing this work product to PWG Candidate Standard. 

Formal Approval occurs by vote of the PWG membership. The voting period will
open on Monday February 25, 2008 and close at 10PM (Pacific Time) on Tuesday
March 18, 2008. 

Valid votes are: Yes, No, No (with strong objection), Abstain. 

Any No vote requires that the voter state the reason for the No vote and a
description of the changes required for turning the No vote to a Yes. 

Representatives from PWG member companies are strongly encouraged to submit
a vote. 

To cast a vote, please send an email with the following subject line format:


"Counter MIB v2 Formal Vote-<company name>-<last name of
voter>-<yes/no/abstain>" 

Example: Counter MIB v2 Formal Vote-InfoPrint-lewis-yes 

No votes MUST contain a reason in the body of the email. 

Please send your vote to the following email addresses: 
(Replacing "dot" with . and "at" with @): 

thrasher"at"lexmark"dot"com 
wamwagner"at"comcast"dot"net 
harryl"at"us"dot"ibm"dot"com 

REFERENCE MATERIAL 

Because there were no last call comments, there is no need for a LCRC
document or for a revision of the document put up for last call. The
document is at
<ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.pdf_>
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.pdf. 
  
Associated documents that assist in understanding the primary document are: 
 <ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.mib_>
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.mib 
- Plaintext ASN.1 MIB 
 <ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123-mib.pdf_>
ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123-mib.pdf 
- Color highlighted ASN.1 MIB 
These MIB documents are not normative and are not in themselves to be voted
on. However, the WIMS working group would welcome any comments members would
like to make on these ancillary documents. 
  
Specific information on the changes from the previously approved
informational document was presented at the February Plenary, and is
available at
<ftp://ftp.pwg.org/pub/pwg/wims/white/wims-countmib20-pwg-last-call-20080207
.pdf_>
ftp://ftp.pwg.org/pub/pwg/wims/white/wims-countmib20-pwg-last-call-20080207.
pdf. 

Note: 
The PWG Definition of the Standards Development Process Version 2.0 
located at: 

 <ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf>
ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf 

A list of Primary and Alternate representatives from PWG member companies
will be provided to the working group chair in case "reminder" notices are
necessary to meet the voting requirements listed in the process document. 

Harry Lewis 

PWG Secretary




Harry Lewis
Program Manager - Intellectual Property & Standards
Phone: 303-924-5337
e-mail: harryl@us.ibm.com
 <http://www.infoprint.com/> infoprint.com

 


------=_NextPart_001_0016_01C87DDB.930B4BC0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This is just to remind PWG members that balloting for
advancement of the </span><b><span =
style=3D'font-family:"Arial","sans-serif"'>Imaging
State &amp; Counter MIB v2 </span></b><span =
style=3D'font-size:10.0pt;font-family:
"Arial","sans-serif"'>is in progress. This MIB was originally approved =
as a
binding of the Counter Spec. It has recently been upgraded to include =
Imaging state
information, in lieu of generating an additional MIB for MFD/MFP state
reporting. It has been prototyped by Samsung, some text has been =
clarified, and
has gone though PWG last call with no comments.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</=
o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>If
possible, please give some time to considering this specification and =
cast your
vote.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</=
o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Many
thanks.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</=
o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Bill
Wagner, CoChairman, WIMS WG </span><span =
style=3D'font-size:10.0pt;font-family:
"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
owner-pwg-announce@pwg.org
[mailto:owner-pwg-announce@pwg.org] <b>On Behalf Of </b>Harry Lewis<br>
<b>Sent:</b> Friday, February 22, 2008 1:14 PM<br>
<b>To:</b> pwg-announce@pwg.org<br>
<b>Subject:</b> PWG-ANNOUNCE&gt; PWG Formal Approval commencement for =
the
Imaging State &amp; Counter MIB v2<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><br>
<b><span style=3D'font-family:"Arial","sans-serif"'>PWG Formal Approval
commencement for the Imaging State &amp; Counter MIB v2 &#8211; Voting =
ends
Tuesday March 18, 2008</span></b> <o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>On Feb 21, 2008 the =
PWG
Steering Committee approved WIMS working group Last Call exit for the =
<b>Imaging
State &amp; Counter MIB v2</b>. At the request of the WIMS working group
Chairman, Bill Wagner &#8211; TIC, and according to my duties as =
Secretary of
the PWG, I hereby initiate the Formal Approval process for advancing =
this work
product to PWG Candidate Standard. </span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>Formal Approval =
occurs by
vote of the PWG membership. The voting period will open on Monday =
February 25,
2008 and close at 10PM (Pacific Time) on Tuesday March 18, 2008. =
</span><o:p></o:p></p>

<p><b><span style=3D'font-family:"Arial","sans-serif"'>Valid votes are: =
Yes, No,
No (with strong objection), Abstain. </span></b><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>Any No vote requires =
that the
voter state the reason for the No vote and a description of the changes
required for turning the No vote to a Yes. </span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>Representatives from =
PWG
member companies are strongly encouraged to submit a vote. =
</span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>To cast a vote, =
please send
an email with the following subject line format: </span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>&quot;Counter MIB v2 =
Formal
Vote-&lt;company name&gt;-&lt;last name of
voter&gt;-&lt;yes/no/abstain&gt;&quot; </span><o:p></o:p></p>

<p><b><span style=3D'font-family:"Arial","sans-serif"'>Example: Counter =
MIB v2
Formal Vote-InfoPrint-lewis-yes </span></b><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>No votes MUST =
contain a
reason in the body of the email. </span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>Please send your =
vote to the
following email addresses: <br>
(Replacing &quot;dot&quot; with . and &quot;at&quot; with @): =
</span><o:p></o:p></p>

<p><b><span =
style=3D'font-family:"Arial","sans-serif"'>thrasher&quot;at&quot;lexmark&=
quot;dot&quot;com
<br>
wamwagner&quot;at&quot;comcast&quot;dot&quot;net <br>
harryl&quot;at&quot;us&quot;dot&quot;ibm&quot;dot&quot;com =
</span></b><o:p></o:p></p>

<p><b><span style=3D'font-family:"Arial","sans-serif"'>REFERENCE =
MATERIAL</span></b>
<o:p></o:p></p>

<p><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Because
there were no last call comments, there is no need for a LCRC document =
or for a
revision of the document put up for last call. The document is at =
</span><a
href=3D"ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.pdf_=
"><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>ftp://ftp.pwg=
.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.pdf</span></a><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>. =
</span><br>
<span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span>=
 <br>
<span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Associated
documents that assist in understanding the primary document are:</span> =
<br>
<a =
href=3D"ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.mib_=
"><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>ftp://ftp.pwg=
.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123.mib</span></a><u><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> =
</span></u><br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>- =
Plaintext
ASN.1 MIB</span> <br>
<a =
href=3D"ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123-mib.=
pdf_"><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>ftp://ftp.pwg=
.org/pub/pwg/wims/wd/wd-wimscountmib20-20080123-mib.pdf</span></a><u><spa=
n
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'> =
</span></u><br>
<u><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>- =
Color
highlighted ASN.1 MIB</span></u> <br>
<span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>These =
MIB
documents are not normative and are not in themselves to be voted on. =
However,
the WIMS working group would welcome any comments members would like to =
make on
these ancillary documents.</span> <br>
<span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span>=
 <br>
<span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Specific
information on the changes from the previously approved informational =
document
was presented at the February Plenary, and is available at </span><a
href=3D"ftp://ftp.pwg.org/pub/pwg/wims/white/wims-countmib20-pwg-last-cal=
l-20080207.pdf_"><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>ftp://ftp.pwg=
.org/pub/pwg/wims/white/wims-countmib20-pwg-last-call-20080207.pdf</span>=
</a><span
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>.</span> =
<o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>Note: <br>
The PWG Definition of the Standards Development Process Version 2.0 <br>
located at: </span><o:p></o:p></p>

<p><a =
href=3D"ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20.pdf"><spa=
n
style=3D'font-family:"Arial","sans-serif"'>ftp://ftp.pwg.org/pub/pwg/gene=
ral/process/pwg-process20.pdf</span></a><span
style=3D'font-family:"Arial","sans-serif"'> </span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>A list of Primary =
and
Alternate representatives from PWG member companies will be provided to =
the
working group chair in case &quot;reminder&quot; notices are necessary =
to meet
the voting requirements listed in the process document. =
</span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>Harry Lewis =
</span><o:p></o:p></p>

<p><span style=3D'font-family:"Arial","sans-serif"'>PWG =
Secretary</span><o:p></o:p></p>

<table class=3DMsoNormalTable border=3D1 cellpadding=3D0>
 <tr>
  <td style=3D'background:white;padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><img =
border=3D0
  width=3D90 height=3D26 id=3D"_x0000_i1025" =
src=3D"cid:image001.gif@01C87DDA.8BA666E0"><o:p></o:p></p>
  </td>
  <td style=3D'background:#EFEFEF;padding:.75pt .75pt .75pt .75pt'>
  <p class=3DMsoNormal><b><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>Harry
  Lewis</span></b><span =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";
  color:gray'><br>
  Program Manager - Intellectual Property &amp; Standards<br>
  Phone: 303-924-5337<br>
  e-mail: harryl@us.ibm.com</span><span =
style=3D'font-size:7.5pt;font-family:
  "Arial","sans-serif";color:blue'><br>
  </span><a href=3D"http://www.infoprint.com/"><span =
style=3D'font-size:7.5pt;
  =
font-family:"Arial","sans-serif"'>infoprint.com</span></a><o:p></o:p></p>=

  </td>
 </tr>
</table>

<p><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_001_0016_01C87DDB.930B4BC0--

------=_NextPart_000_0015_01C87DDB.930B4BC0
Content-Type: image/gif;
	name="image001.gif"
Content-Transfer-Encoding: base64
Content-ID: <image001.gif@01C87DDA.8BA666E0>

R0lGODlhWgAaALMAAPnJypu06PFvdGOK3MHQ8PWrrfOJjO9JT7m5ufbn5XGT3lR+2OwcJAAAAP//
/wAAACH5BAAAAAAALAAAAABaABoAAAT/0MlJq704a9m210AoAl8iJpUZot/VVYFCOLFi27NUB9PO
/EBgQSL4HSaGQ5BxICWUwcNQAiRRf5YXRbGYBRbgcFfCXSgmZQXwYDAUf6T30fFmCO6HYwF4rwuu
DFYOQFkWXF4LPDpmZAsDCxOOZoQTbwZ0Rg57cCwsQAYoCZuBg3ATlBRaaGNfig4EjA5ch69mk1gO
olWYTA5QlxWjLLm/CWt5UAyFFbRfCgHQjzlcrTSJtwwGS8Byvj/AFKMV3UtLy1usYmHTXYwKA7Bq
WNpMgt1QfxUAQMPe2aXZCghENUFVI0QyCBD4AklWFy4OzMSjRI/BlG4Vp0hI8ORHPk27+3YBOrcK
kSuHMw61SjQRl4OMvI4kqMNGgBJdRtwIySUSIMmD1lwlkIYyXpeWyjZWBNAtV4FkHgGYqGNEY0+C
HAylG3ADzBmUEcHU+tqCAscV/Tiq6Fc2K7N06sjSmjW2rd27P/Hq3cvXbd+/gAMLHky4sOHDiBMr
Xsy4sEEEqhpIRpCqghbIBjP71YA5cIfJDjpApvzis+jQDRB0Dj1hNOvPnSm7Bg3Z7+zUqVFTDk06
t+nXvD+j9p1V+GXixoEDT66l+fLnpJ9Llq7cLXPL1IVnt15we+nko6/Prgz9u2zirmuLRs5bQmz2
pkmrZx06R2PFBl3cZ5wfu4MIADs=

------=_NextPart_000_0015_01C87DDB.930B4BC0--



From ipp-owner@pwg.org  Tue Mar  4 14:31:07 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F073D3A683D
	for <ietfarch-ipp-archive@core3.amsl.com>; Tue,  4 Mar 2008 14:31:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level: 
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=0.383,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4yOmGZ-yE-oC for <ietfarch-ipp-archive@core3.amsl.com>;
	Tue,  4 Mar 2008 14:31:07 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 364A13A6A56
	for <ipp-archive@ietf.org>; Tue,  4 Mar 2008 14:31:07 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m24MUssC001526
	for <ipp-archive@ietf.org>; Tue, 4 Mar 2008 17:30:56 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m24MUsss001523
	for <ipp-archive@lists.ietf.org>; Tue, 4 Mar 2008 17:30:54 -0500
Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Mar 2008 17:29:50 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m24MTe8Q001231
	for <ipp-outgoing@pwg.org>; Tue, 4 Mar 2008 17:29:42 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m24MTeJX001228
	for ipp-outgoing; Tue, 4 Mar 2008 17:29:40 -0500
Received: from njwcntas37.us.ricoh.ds (host150.ricoh-usa.com [208.252.21.150])
	by pwg.org  with ESMTP id m24MTbKI001224
	for <ipp@pwg.org>; Tue, 4 Mar 2008 17:29:39 -0500
X-SEF-Processed: 5_0_0_816__2008_03_04_17_29_37
Received: from Unknown [172.16.19.238] by njwcntas37.us.ricoh.ds - SurfControl E-mail Filter ; Tue, 04 Mar 2008 17:29:37 -0500
Subject: IPP> Reminder, IPPv2 Conference Call March 6 @ 11:00 AM EST
To: ipp@pwg.org
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF19EFF770.A33A4BB4-ON88257402.0079FE6F-88257402.007B8E06@ricoh-usa.com>
From: Ron.Bergman@ricoh-usa.com
Date: Tue, 4 Mar 2008 14:29:32 -0800
X-MIMETrack: Serialize by Router on NJWC02/RCUS(Release 7.0.2FP1|January 10, 2007) at 03/04/2008
 05:29:37 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-ipp@pwg.org


IPPv2 WG Conference Call:

Thursday, March 6, 2008, 11:00 AM EST  (8:00 AM PST)

Toll Free:     1-866-365-4406
International: 00+1+303-248-9655
Passcode:      2635888#

Agenda:

1. Identify Minute Taker
2. Approval of minutes from 2/21 Conference Call
3. Review of Action Items
   Ira - Obtain a list of the IPP operations supported by Open Solaris
   Ron - Create a list of IPP Specifications indicating the v2 proposal by
Mike Sweet
   Ira - Invite Norm Jacobs to participate
   Ron - Update the list of IPP Opearation to indicate the requirements per
the spec
4. Continue the discussion of the proposal from Mike Sweet
5. What operations should be changed from 'optional' to 'required'?
6. Next steps




From ipp-owner@pwg.org  Tue Mar  4 16:33:26 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D29BA3A6995
	for <ietfarch-ipp-archive@core3.amsl.com>; Tue,  4 Mar 2008 16:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id HbHfdvpA663f for <ietfarch-ipp-archive@core3.amsl.com>;
	Tue,  4 Mar 2008 16:33:25 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 09CD128C605
	for <ipp-archive@ietf.org>; Tue,  4 Mar 2008 16:32:54 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m250WgO2023402
	for <ipp-archive@ietf.org>; Tue, 4 Mar 2008 19:32:44 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m250WgQk023399
	for <ipp-archive@lists.ietf.org>; Tue, 4 Mar 2008 19:32:42 -0500
Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Mar 2008 19:31:41 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m250VbiP023066
	for <ipp-outgoing@pwg.org>; Tue, 4 Mar 2008 19:31:39 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m250Vbxa023063
	for ipp-outgoing; Tue, 4 Mar 2008 19:31:37 -0500
Received: from wbmler1.mail.xerox.com (wbmler1.mail.xerox.com [13.13.138.216])
	by pwg.org  with ESMTP id m250VYbW023053
	for <ipp@pwg.org>; Tue, 4 Mar 2008 19:31:36 -0500
Received: from wbmlir2.mail.xerox.com (wbmlir2.mail.xerox.com [13.131.8.222])
	by wbmler1.mail.xerox.com (8.13.8/8.13.8) with ESMTP id m250VW5m008406;
	Tue, 4 Mar 2008 19:31:32 -0500
Received: from wbmlir2.mail.xerox.com (localhost [127.0.0.1])
	by wbmlir2.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m250VRYH012962;
	Tue, 4 Mar 2008 19:31:27 -0500
Received: from USA0300GW002.na.xerox.net (usa0300gw002.na.xerox.net [13.135.210.15])
	by wbmlir2.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m250VQ70012952;
	Tue, 4 Mar 2008 19:31:27 -0500
X-Xerox-Source-Ip: 13.135.210.15
X-Xerox-Source-Name: usa0300gw002.na.xerox.net
X-Xerox-Reported-Name: USA0300GW002.na.xerox.net
Received: from usaesm1mf01.na.xerox.net ([13.241.1.17]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 4 Mar 2008 19:31:26 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: IPP> Teleconference call minutes [mailto: notification methods]
Date: Tue, 4 Mar 2008 16:31:25 -0800
Message-ID: <559BCC0E42F1AA409F7603081DDB2C34B4984E@usaesm1mf01.na.xerox.net>
In-Reply-To: <e395be80802221552i7f155548r5532813edae39614@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IPP> Teleconference call minutes [mailto: notification methods]
thread-index: Ach1s/+kKUPe9a2PSWiIZf1XXrLbrQIo6spA
References: <OF51CB4E7D.4D641DCA-ON882573EF.007C74CC-882573EF.007CD44E@ricoh-usa.com> <2DB650784C0A9649B560DE38F68DA744288BA6@wabex2.sharpamericas.com> <47BF5401.4060909@apple.com> <e395be80802221552i7f155548r5532813edae39614@mail.gmail.com>
From: "Hastings, Tom N" <Tom.Hastings@xerox.com>
To: "Ira McDonald" <blueroofmusic@gmail.com>,
        "Michael R Sweet" <msweet@apple.com>
Cc: "Whittle, Craig" <cwhittle@sharplabs.com>, <Ron.Bergman@ricoh-usa.com>,
        <ipp@pwg.org>
X-OriginalArrivalTime: 05 Mar 2008 00:31:26.0734 (UTC) FILETIME=[3F7B82E0:01C87E58]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id m250VbbW023061
Sender: owner-ipp@pwg.org

Ira wrote:

The lack of standards-track email notification is unfortunate,
because it's the ubiquitous proprietary notification method
supported by the majority of network printers.


I have a .doc file for an Internet-Draft for a standard track IETF
document.  Does someone want to turn that into an IEEE-ISTO draft
standard?

Here is the start of it:

Internet Printing Protocol WG                             Robert Herriot
INTERNET-DRAFT                                              Tom Hastings
<draft-ietf-ipp-notify-mailto-04.txt>                    Carl-Uno Manros
Updates:  RFC 2911                                           Xerox Corp.
[Target Category:  standards track]                         Henrik Holst
Expires:  January 17, 2002                      i-data international a/s
                                                           July 17, 2001

                     Internet Printing Protocol (IPP):
           The 'mailto' Delivery Method for Event Notifications

      Copyright (C) The Internet Society (2000). All Rights Reserved.
Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of [RFC2026].  Internet-Drafts are
   working documents of the Internet Engineering Task Force (IETF), its
   areas, and its working groups.  Note that other groups may also
   distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress".

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed as
   http://www.ietf.org/shadow.html.

Abstract

   This document describes an extension to the Internet Printing
   Protocol/1.0 (IPP) [RFC2566, RFC2565] and IPP/1.1 [RFC2911, RFC2910].
   This document specifies the 'mailto' Delivery Method for use with the
   "IPP Event Notifications and Subscriptions" specification [ipp-ntfy].
   When IPP Notification [ipp-ntfy] is supported, the Delivery Method
   defined in this document is one of the RECOMMENDED Delivery Methods
   for Printers to support.

   For this Delivery Method, when an Event occurs, the Printer
   immediately sends an Event Notification via an email message to the
   Notification Recipient specified in the Subscription Object.  The
   message body of the email consists of Human Consumable text that is
   not intended to be parsed by a machine.  The Notification Recipient
   receives the Event Notification in the same way as it receives any
   other email message.

Thanks,
Tom

-----Original Message-----
From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of Ira
McDonald
Sent: Friday, February 22, 2008 15:52
To: Michael R Sweet; Ira McDonald
Cc: Whittle, Craig; Ron.Bergman@ricoh-usa.com; ipp@pwg.org
Subject: Re: IPP> Teleconference call minutes

Hi Mike,

Yes - notification by polling means ippget.

The lack of standards-track email notification is unfortunate,
because it's the ubiquitous proprietary notification method
supported by the majority of network printers.

Cheers,
- Ira

On Fri, Feb 22, 2008 at 6:00 PM, Michael R Sweet <msweet@apple.com>
wrote:
> Whittle, Craig wrote:
>  > All:
>  >
>  > The minutes from this week's teleconference call can be found at:
>  >
ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-minutes/IPPv2-ConCall-Minutes-200802
>  > 21.pdf
>
>  Comments (and hopefully I'll be able to "attend" next week's
telecon):
>
>   > Need to find out what is in CUPS 1.3 and what will be in CUPS 1.4.
>
>  CUPS 1.3:
>
>
>
http://svn.easysw.com/public/cups/branches/branch-1.3/doc/help/spec-ipp.
html
>
>  CUPS 1.4:
>
>      http://svn.easysw.com/public/cups/trunk/doc/help/spec-ipp.html
>
>  Right now the only difference between 1.3 and 1.4 is the addition of
>  a new CUPS-specific "get document" operation.
>
>   > Notification by polling should be considered.  E-mail notification
>   > is dead as an IPP specification.
>
>  Presumably polling == ippget/RFC 3996?
>
>  --
>
______________________________________________________________________
>  Michael R Sweet                        Senior Printing System
Engineer
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434



From ipp-owner@pwg.org  Tue Mar  4 16:46:28 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 962443A6D5C
	for <ietfarch-ipp-archive@core3.amsl.com>; Tue,  4 Mar 2008 16:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wTxzU1wyX5o0 for <ietfarch-ipp-archive@core3.amsl.com>;
	Tue,  4 Mar 2008 16:46:27 -0800 (PST)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id B00A73A6CFD
	for <ipp-archive@ietf.org>; Tue,  4 Mar 2008 16:46:27 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m250kFkQ026785
	for <ipp-archive@ietf.org>; Tue, 4 Mar 2008 19:46:17 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m250kFha026782
	for <ipp-archive@lists.ietf.org>; Tue, 4 Mar 2008 19:46:15 -0500
Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Mar 2008 19:45:19 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m250jE6f026260
	for <ipp-outgoing@pwg.org>; Tue, 4 Mar 2008 19:45:16 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m250jE5v026257
	for ipp-outgoing; Tue, 4 Mar 2008 19:45:14 -0500
Received: from wbmler1.mail.xerox.com (wbmler1.mail.xerox.com [13.13.138.216])
	by pwg.org  with ESMTP id m250jCea026246
	for <ipp@pwg.org>; Tue, 4 Mar 2008 19:45:14 -0500
Received: from wbmlir2.mail.xerox.com (wbmlir2.mail.xerox.com [13.131.8.222])
	by wbmler1.mail.xerox.com (8.13.8/8.13.8) with ESMTP id m250jB90027200;
	Tue, 4 Mar 2008 19:45:12 -0500
Received: from wbmlir2.mail.xerox.com (localhost [127.0.0.1])
	by wbmlir2.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m250ixNP020370;
	Tue, 4 Mar 2008 19:44:59 -0500
Received: from USA7061GW002.na.xerox.net (usa7061gw002.na.xerox.net [13.151.210.15])
	by wbmlir2.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m250ixjO020365;
	Tue, 4 Mar 2008 19:44:59 -0500
X-Xerox-Source-Ip: 13.151.210.15
X-Xerox-Source-Name: usa7061gw002.na.xerox.net
X-Xerox-Reported-Name: USA7061GW002.na.xerox.net
Received: from usaesm1mf01.na.xerox.net ([13.241.1.17]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.3959);
	 Tue, 4 Mar 2008 16:44:58 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: IPP> IPPv2 Statement Of Work Update
Date: Tue, 4 Mar 2008 16:44:57 -0800
Message-ID: <559BCC0E42F1AA409F7603081DDB2C34B4984F@usaesm1mf01.na.xerox.net>
In-Reply-To: <OFCBFCD77A.61938A74-ON882573F6.006230DF-882573F6.00628AA8@ricoh-usa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IPP> IPPv2 Statement Of Work Update
thread-index: Ach02psu8ZDurcynToehYyoqZ02ySgJfte5A
References: <OFCBFCD77A.61938A74-ON882573F6.006230DF-882573F6.00628AA8@ricoh-usa.com>
From: "Hastings, Tom N" <Tom.Hastings@xerox.com>
To: <Ron.Bergman@ricoh-usa.com>, <ipp@pwg.org>
X-OriginalArrivalTime: 05 Mar 2008 00:44:58.0711 (UTC) FILETIME=[23755E70:01C87E5A]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id m250jEea026255
Sender: owner-ipp@pwg.org

The statement of work says:

*  OBJ-1 Include a reference to all IPP Standards Track documents,
starting from version 1.1.
*  OBJ-2 All current IPP features are to be included as a requirement or
an option.
*  OBJ-3 All features are to be classified as Mandatory, Conditionally
Mandatory, or Optional.

What is a "feature"?  What is the level of granularity of a feature?  An
operation, an object, an attribute, or an attribute value?

In other words, at what level of detail will the "Mandatory",
"Conditionally Mandatory" or "Optional" be specified at: an operation,
an object, an attribute, or an attribute value?

The PWG Semantic model lists all of the operations, objects, attributes,
and values (though spelled "funny"), along with the documents in which
they are defined, if that is a help is compiling a profile template.

Tom

-----Original Message-----
From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
Ron.Bergman@ricoh-usa.com
Sent: Thursday, February 21, 2008 09:56
To: ipp@pwg.org
Subject: IPP> IPPv2 Statement Of Work Update


The IPPv2 Charter has been converted into a Statement of Work.

Send any comments to the mail list.


ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-docs/wd-ippv2-statement-of-work-2008
0221.pdf
  (.doc)





From ipp-owner@pwg.org  Tue Mar  4 17:15:39 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9B1B428C4C1
	for <ietfarch-ipp-archive@core3.amsl.com>; Tue,  4 Mar 2008 17:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Dkafobzvs7Oz for <ietfarch-ipp-archive@core3.amsl.com>;
	Tue,  4 Mar 2008 17:15:38 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 45E6628C5CD
	for <ipp-archive@ietf.org>; Tue,  4 Mar 2008 17:15:38 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m251FPOM000823
	for <ipp-archive@ietf.org>; Tue, 4 Mar 2008 20:15:27 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m251FPrJ000820
	for <ipp-archive@lists.ietf.org>; Tue, 4 Mar 2008 20:15:25 -0500
Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Mar 2008 20:14:25 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2518sVO032329
	for <ipp-outgoing@pwg.org>; Tue, 4 Mar 2008 20:14:23 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m250sQfQ028005
	for ipp-outgoing; Tue, 4 Mar 2008 19:54:26 -0500
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177])
	by pwg.org  with ESMTP id m250rswq027919
	for <ipp@pwg.org>; Tue, 4 Mar 2008 19:53:56 -0500
Received: by wa-out-1112.google.com with SMTP id j37so1100314waf.7
        for <ipp@pwg.org>; Tue, 04 Mar 2008 16:53:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=+nAyf3kddMs9nzsOsxdA2p2iryNQdziL+PSCp5ulgcs=;
        b=sgby4oZY/A7PfTdCo8bLM0UmpxgzxObFHjvngnLFRo7/iwgqfi2Cviv3AuexowdY9WTu25X/clImfhJwQfqtONWUW5T/FkRtAd1tZjoT37+S5T1loA99/vHH3TpAyCqR96PWfc8WnYxTre97gNVHtRDcJm1JcSJCbsWx8cgQCw0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=rnV0MZFpiJ6yJQ4UIS0zuuVW6GuLHtnZzaWNAlzfNMLVNpgRY9+gPGUkJqlaYqpZv2LE7z2PMCnuI1wodUngBxpuHHM5kZoKAt6WcySo6b6QrzupJz+dNr7Pf8yhnq3qZJGpV88HbE/Yp3gyozY64qTzHhKYBjVK15idDfI5Hy0=
Received: by 10.114.27.20 with SMTP id a20mr3254580waa.101.1204678046017;
        Tue, 04 Mar 2008 16:47:26 -0800 (PST)
Received: by 10.115.17.1 with HTTP; Tue, 4 Mar 2008 16:47:25 -0800 (PST)
Message-ID: <e395be80803041647m2d18f237ud6ba1548753b7358@mail.gmail.com>
Date: Tue, 4 Mar 2008 19:47:25 -0500
From: "Ira McDonald" <blueroofmusic@gmail.com>
To: "Hastings, Tom N" <Tom.Hastings@xerox.com>,
        "Ira McDonald" <blueroofmusic@gmail.com>
Subject: Re: IPP> Teleconference call minutes [mailto: notification methods]
Cc: "Michael R Sweet" <msweet@apple.com>,
        "Whittle, Craig" <cwhittle@sharplabs.com>, Ron.Bergman@ricoh-usa.com,
        ipp@pwg.org
In-Reply-To: <559BCC0E42F1AA409F7603081DDB2C34B4984E@usaesm1mf01.na.xerox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <OF51CB4E7D.4D641DCA-ON882573EF.007C74CC-882573EF.007CD44E@ricoh-usa.com>
	 <2DB650784C0A9649B560DE38F68DA744288BA6@wabex2.sharpamericas.com>
	 <47BF5401.4060909@apple.com>
	 <e395be80802221552i7f155548r5532813edae39614@mail.gmail.com>
	 <559BCC0E42F1AA409F7603081DDB2C34B4984E@usaesm1mf01.na.xerox.net>
Sender: owner-ipp@pwg.org

Hi Tom,

That document (IPP Email Notifications) was formally abandoned after
Ricoh stated that they held relevant patents and would NOT license
those patents.  The PWG will never take up IPP Email Notifications
again.  That's the way the cookie crumbles.

Cheers,
- Ira

On Tue, Mar 4, 2008 at 7:31 PM, Hastings, Tom N <Tom.Hastings@xerox.com> wrote:
> Ira wrote:
>
>  The lack of standards-track email notification is unfortunate,
>  because it's the ubiquitous proprietary notification method
>  supported by the majority of network printers.
>
>
>  I have a .doc file for an Internet-Draft for a standard track IETF
>  document.  Does someone want to turn that into an IEEE-ISTO draft
>  standard?
>
>  Here is the start of it:
>
>  Internet Printing Protocol WG                             Robert Herriot
>  INTERNET-DRAFT                                              Tom Hastings
>  <draft-ietf-ipp-notify-mailto-04.txt>                    Carl-Uno Manros
>  Updates:  RFC 2911                                           Xerox Corp.
>  [Target Category:  standards track]                         Henrik Holst
>  Expires:  January 17, 2002                      i-data international a/s
>                                                            July 17, 2001
>
>                      Internet Printing Protocol (IPP):
>            The 'mailto' Delivery Method for Event Notifications
>
>       Copyright (C) The Internet Society (2000). All Rights Reserved.
>  Status of this Memo
>
>    This document is an Internet-Draft and is in full conformance with
>    all provisions of Section 10 of [RFC2026].  Internet-Drafts are
>    working documents of the Internet Engineering Task Force (IETF), its
>    areas, and its working groups.  Note that other groups may also
>    distribute working documents as Internet-Drafts.
>
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress".
>
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt
>
>    The list of Internet-Draft Shadow Directories can be accessed as
>    http://www.ietf.org/shadow.html.
>
>  Abstract
>
>    This document describes an extension to the Internet Printing
>    Protocol/1.0 (IPP) [RFC2566, RFC2565] and IPP/1.1 [RFC2911, RFC2910].
>    This document specifies the 'mailto' Delivery Method for use with the
>    "IPP Event Notifications and Subscriptions" specification [ipp-ntfy].
>    When IPP Notification [ipp-ntfy] is supported, the Delivery Method
>    defined in this document is one of the RECOMMENDED Delivery Methods
>    for Printers to support.
>
>    For this Delivery Method, when an Event occurs, the Printer
>    immediately sends an Event Notification via an email message to the
>    Notification Recipient specified in the Subscription Object.  The
>    message body of the email consists of Human Consumable text that is
>    not intended to be parsed by a machine.  The Notification Recipient
>    receives the Event Notification in the same way as it receives any
>    other email message.
>
>  Thanks,
>  Tom
>
>  -----Original Message-----
>  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of Ira
>  McDonald
>  Sent: Friday, February 22, 2008 15:52
>  To: Michael R Sweet; Ira McDonald
>  Cc: Whittle, Craig; Ron.Bergman@ricoh-usa.com; ipp@pwg.org
>  Subject: Re: IPP> Teleconference call minutes
>
>  Hi Mike,
>
>  Yes - notification by polling means ippget.
>
>  The lack of standards-track email notification is unfortunate,
>  because it's the ubiquitous proprietary notification method
>  supported by the majority of network printers.
>
>  Cheers,
>  - Ira
>
>  On Fri, Feb 22, 2008 at 6:00 PM, Michael R Sweet <msweet@apple.com>
>  wrote:
>  > Whittle, Craig wrote:
>  >  > All:
>  >  >
>  >  > The minutes from this week's teleconference call can be found at:
>  >  >
>  ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-minutes/IPPv2-ConCall-Minutes-200802
>  >  > 21.pdf
>  >
>  >  Comments (and hopefully I'll be able to "attend" next week's
>  telecon):
>  >
>  >   > Need to find out what is in CUPS 1.3 and what will be in CUPS 1.4.
>  >
>  >  CUPS 1.3:
>  >
>  >
>  >
>  http://svn.easysw.com/public/cups/branches/branch-1.3/doc/help/spec-ipp.
>  html
>  >
>  >  CUPS 1.4:
>  >
>  >      http://svn.easysw.com/public/cups/trunk/doc/help/spec-ipp.html
>  >
>  >  Right now the only difference between 1.3 and 1.4 is the addition of
>  >  a new CUPS-specific "get document" operation.
>  >
>  >   > Notification by polling should be considered.  E-mail notification
>  >   > is dead as an IPP specification.
>  >
>  >  Presumably polling == ippget/RFC 3996?
>  >
>  >  --
>  >
>  ______________________________________________________________________
>  >  Michael R Sweet                        Senior Printing System
>  Engineer
>  >
>
>
>
>  --
>  Ira McDonald (Musician / Software Architect)
>  Chair - Linux Foundation Open Printing WG
>  Blue Roof Music/High North Inc
>  email: blueroofmusic@gmail.com
>  winter:
>   579 Park Place  Saline, MI  48176
>   734-944-0094
>  summer:
>   PO Box 221  Grand Marais, MI 49839
>   906-494-2434
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434


From ipp-owner@pwg.org  Tue Mar  4 19:45:27 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C021C3A6D39
	for <ietfarch-ipp-archive@core3.amsl.com>; Tue,  4 Mar 2008 19:45:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id awoNTaI803ZH for <ietfarch-ipp-archive@core3.amsl.com>;
	Tue,  4 Mar 2008 19:45:17 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 92DFE28C6D1
	for <ipp-archive@ietf.org>; Tue,  4 Mar 2008 19:43:46 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m253hYMw015759
	for <ipp-archive@ietf.org>; Tue, 4 Mar 2008 22:43:36 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m253hYwG015756
	for <ipp-archive@lists.ietf.org>; Tue, 4 Mar 2008 22:43:34 -0500
Received: by pwg.org (bulk_mailer v1.13); Tue, 4 Mar 2008 22:42:33 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m253gSfZ015480
	for <ipp-outgoing@pwg.org>; Tue, 4 Mar 2008 22:42:30 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m253gSMA015477
	for ipp-outgoing; Tue, 4 Mar 2008 22:42:28 -0500
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.180])
	by pwg.org  with ESMTP id m253gQCO015469
	for <ipp@pwg.org>; Tue, 4 Mar 2008 22:42:28 -0500
Received: by el-out-1112.google.com with SMTP id s27so1517509ele.1
        for <ipp@pwg.org>; Tue, 04 Mar 2008 19:42:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=fg1ZBBMs4oUZPy/NJetyQ0pgWdPtLRGN6ECi0hMBPQk=;
        b=ukaw34luswKYEf/lxOlVtLsQHwHjdNpJw77TE1/UOMT+2Gt5vB8odvyaTn1fjwv+z0jdubyqFGx17ndp0Q3IyatQIgK8SdB3m0bJrT62F7j/ZkHyfEGlA0bNfPysk2WGUpTkJaClqBj6KUiZIgdnvQFtkIZ4dTXjKc1P2hzA+4o=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=GBqAgZ2PvnyOFsdXpY7t8vagVlKh1C4kt9PIcIlb5H1XfH7B8kHlIt5JkpFdVXrxJyhqxvTu+I3vN9hgbb9cQErpCyBdgnsoO1J8zLfjTL6aGitNAoOEeVsfw+FR6oOKXQr1RIzboZUAtMSN3RnA/H0uj5G7AvCOzlbg41hh+f0=
Received: by 10.114.125.2 with SMTP id x2mr3446573wac.119.1204688544972;
        Tue, 04 Mar 2008 19:42:24 -0800 (PST)
Received: by 10.115.17.1 with HTTP; Tue, 4 Mar 2008 19:42:24 -0800 (PST)
Message-ID: <e395be80803041942j133c813y6603374994dc1577@mail.gmail.com>
Date: Tue, 4 Mar 2008 22:42:24 -0500
From: "Ira McDonald" <blueroofmusic@gmail.com>
To: "Hastings, Tom N" <Tom.Hastings@xerox.com>,
        "Ira McDonald" <blueroofmusic@gmail.com>
Subject: Re: IPP> IPPv2 Statement Of Work Update
Cc: Ron.Bergman@ricoh-usa.com, ipp@pwg.org
In-Reply-To: <559BCC0E42F1AA409F7603081DDB2C34B4984F@usaesm1mf01.na.xerox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <OFCBFCD77A.61938A74-ON882573F6.006230DF-882573F6.00628AA8@ricoh-usa.com>
	 <559BCC0E42F1AA409F7603081DDB2C34B4984F@usaesm1mf01.na.xerox.net>
Sender: owner-ipp@pwg.org

Hi Tom,

My two cents - these profiles (i.e., version 2.0, 2.1, 2.2, etc.) should ONLY
make whole IPP standards specs (IETF or PWG) mandatory, conditionally
mandatory, or optional.

Although there has been speculation that individual operations (but NOT
attributes) might be raised in requirements level from their original specs,
I'm opposed to doing so.

The sole function of the IPP/2.x effort should be simply to encourage more
widespread implementation of the many IPP extensions (a set of content
much larger than the entire original IPP/1.1 protocol).  And to simplify the
description of such higher implementation functionality for end users.

Changing specific requirements levels *within* particular IPP specs is a
slippery slope that would destroy the IPP/2.x effort (and violate the PWG
Process/2.0 rules).

Bear in mind that the PWG Process/2.0 is much more rigorous than past
PWG practice.  Actual prototypes are REQUIRED before a document can
even enter PWG Last Call, much less be adopted.  It remains to be seen
if this can be achieved for IPP/2.x.

Cheers,
- Ira

On Tue, Mar 4, 2008 at 7:44 PM, Hastings, Tom N <Tom.Hastings@xerox.com> wrote:
> The statement of work says:
>
>  *  OBJ-1 Include a reference to all IPP Standards Track documents,
>  starting from version 1.1.
>  *  OBJ-2 All current IPP features are to be included as a requirement or
>  an option.
>  *  OBJ-3 All features are to be classified as Mandatory, Conditionally
>  Mandatory, or Optional.
>
>  What is a "feature"?  What is the level of granularity of a feature?  An
>  operation, an object, an attribute, or an attribute value?
>
>  In other words, at what level of detail will the "Mandatory",
>  "Conditionally Mandatory" or "Optional" be specified at: an operation,
>  an object, an attribute, or an attribute value?
>
>  The PWG Semantic model lists all of the operations, objects, attributes,
>  and values (though spelled "funny"), along with the documents in which
>  they are defined, if that is a help is compiling a profile template.
>
>  Tom
>
>
>
>  -----Original Message-----
>  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
>  Ron.Bergman@ricoh-usa.com
>  Sent: Thursday, February 21, 2008 09:56
>  To: ipp@pwg.org
>  Subject: IPP> IPPv2 Statement Of Work Update
>
>
>  The IPPv2 Charter has been converted into a Statement of Work.
>
>  Send any comments to the mail list.
>
>
>  ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-docs/wd-ippv2-statement-of-work-2008
>  0221.pdf
>   (.doc)
>
>
>
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434


From ipp-owner@pwg.org  Wed Mar  5 10:20:11 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7C74F28C2AB
	for <ietfarch-ipp-archive@core3.amsl.com>; Wed,  5 Mar 2008 10:20:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OQEqeSW60hLA for <ietfarch-ipp-archive@core3.amsl.com>;
	Wed,  5 Mar 2008 10:20:06 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 51A4328C305
	for <ipp-archive@ietf.org>; Wed,  5 Mar 2008 10:20:06 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25IJrFu004972
	for <ipp-archive@ietf.org>; Wed, 5 Mar 2008 13:19:55 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m25IJrK9004969
	for <ipp-archive@lists.ietf.org>; Wed, 5 Mar 2008 13:19:53 -0500
Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Mar 2008 13:18:44 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25IIYbC004531
	for <ipp-outgoing@pwg.org>; Wed, 5 Mar 2008 13:18:36 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m25IIYIV004528
	for ipp-outgoing; Wed, 5 Mar 2008 13:18:34 -0500
Received: from wvmler3.mail.xerox.com (wvmler3.mail.xerox.com [13.8.138.218])
	by pwg.org  with ESMTP id m25IIUeF004513
	for <ipp@pwg.org>; Wed, 5 Mar 2008 13:18:33 -0500
Received: from wvmlir2.mail.xerox.com (wvmlir2.mail.xerox.com [13.147.8.222])
	by wvmler3.mail.xerox.com (8.13.8/8.13.8) with ESMTP id m25IIC31014031;
	Wed, 5 Mar 2008 10:18:18 -0800
Received: from wvmlir2.mail.xerox.com (localhost [127.0.0.1])
	by wvmlir2.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m25II5wf017238;
	Wed, 5 Mar 2008 10:18:05 -0800
Received: from USA0300GW002.na.xerox.net (usa0300gw002.na.xerox.net [13.135.210.15])
	by wvmlir2.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m25IHQK0016707;
	Wed, 5 Mar 2008 10:18:05 -0800
X-Xerox-Source-Ip: 13.135.210.15
X-Xerox-Source-Name: usa0300gw002.na.xerox.net
X-Xerox-Reported-Name: USA0300GW002.na.xerox.net
Received: from usaesm1mf01.na.xerox.net ([13.241.1.17]) by USA0300GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 5 Mar 2008 13:18:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define what a "feature" is]
Date: Wed, 5 Mar 2008 10:18:02 -0800
Message-ID: <559BCC0E42F1AA409F7603081DDB2C34B49851@usaesm1mf01.na.xerox.net>
In-Reply-To: <e395be80803041942j133c813y6603374994dc1577@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define what a "feature" is]
thread-index: Ach+cvmfDdBnNBGDQ7SsRWCiPH6gaQAdwdPQ
References: <OFCBFCD77A.61938A74-ON882573F6.006230DF-882573F6.00628AA8@ricoh-usa.com> <559BCC0E42F1AA409F7603081DDB2C34B4984F@usaesm1mf01.na.xerox.net> <e395be80803041942j133c813y6603374994dc1577@mail.gmail.com>
From: "Hastings, Tom N" <Tom.Hastings@XEROX.COM>
To: "Ira McDonald" <blueroofmusic@gmail.com>
Cc: <Ron.Bergman@ricoh-usa.com>, <ipp@pwg.org>
X-OriginalArrivalTime: 05 Mar 2008 18:18:03.0453 (UTC) FILETIME=[407FDED0:01C87EED]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id m25IIXeF004526
Sender: owner-ipp@pwg.org

Ira,

The problem that I have with your view that the IPPv2 Profiles just
lists IPP Standards is that most of the additional IPP standards define
additional operations, attributes, and values which are all OPTIONAL to
support.  In other words, they are just shopping lists of operations or
attributes (and attribute values).

For example, here is the abstract from RFC 3998: Job and Printer
Administrative Operations:

This document specifies the following 16 additional OPTIONAL system
administration operations for use with the Internet Printing
Protocol/1.1 (IPP) [RFC2910, RFC2911], plus a few associated attributes,
values, and status codes and using the IPP Printer object to manage
printer fan-out and fan-in.

As another example, here is the abstract from IEEE-ISTO PWG 5100.7-2003:
Standard for The Internet Printing Protocol (IPP): Job Extensions

Abstract: This IPP specification extends the Job semantics of the IPP
Model and Semantics [rfc2911] object model.  This specification defines
some new Operation attributes for use in Job Creation and Document
Creation operations.  The Printer copies these Operation attributes to
the corresponding Job Description attributes, which the clients may
query.  The Document Creation Operation attributes describe the Document
Content and permit the Printer to reject requests that it cannot process
correctly.  Some corresponding "xxx-default" and "xxx-supported" Printer
attributes are defined.  This specification defines some Job Template
attributes that apply to a multi-document Job as a whole and the
"output-device" Job Template attribute that can apply to Documents and
to Sheets as well as Jobs.  This specification also defines some
additional values for the "job-state-reasons" Job Description attribute.
Each of the attributes defined in this specification are independent of
each other and are OPTIONAL for a Printer to support.

All of the attributes defined are OPTIONAL for a Printer to support!

My recollection is that most of the extension IPP standards are like
this. Thus I think it would really help if each profile listed the
operations and attributes (any maybe attribute values) that are
MANDATORY, CONDITIONALLY MANDATORY (with their condition), and
OPTIONAL).


Back to my comment on the Statement of Work:

The ISSUE with the Statement of Work is to agree on what the undefined
term: "feature".  One interpretation (mine) is that each operation is a
"feature" and each attribute is a "feature".  Whether an attribute value
is also a feature needs to be clarified.  Without such an agreement on
what the term "feature" is, I think that people will have widely
differing understandings on what the IPPv2 project is about.

BTW, I like the idea of the IPPv2 project NOT trying to re-write,
clarify, or augment, the published standards.  I'm just questioning the
value of having a profile that points to set of IPP standards where each
IPP standard just contains a list of operations or attributes that are
all OPTIONAL. 

Tom

-----Original Message-----
From: Ira McDonald [mailto:blueroofmusic@gmail.com] 
Sent: Tuesday, March 04, 2008 19:42
To: Hastings, Tom N; Ira McDonald
Cc: Ron.Bergman@ricoh-usa.com; ipp@pwg.org
Subject: Re: IPP> IPPv2 Statement Of Work Update

Hi Tom,

My two cents - these profiles (i.e., version 2.0, 2.1, 2.2, etc.) should
ONLY
make whole IPP standards specs (IETF or PWG) mandatory, conditionally
mandatory, or optional.

Although there has been speculation that individual operations (but NOT
attributes) might be raised in requirements level from their original
specs,
I'm opposed to doing so.

The sole function of the IPP/2.x effort should be simply to encourage
more
widespread implementation of the many IPP extensions (a set of content
much larger than the entire original IPP/1.1 protocol).  And to simplify
the
description of such higher implementation functionality for end users.

Changing specific requirements levels *within* particular IPP specs is a
slippery slope that would destroy the IPP/2.x effort (and violate the
PWG
Process/2.0 rules).

Bear in mind that the PWG Process/2.0 is much more rigorous than past
PWG practice.  Actual prototypes are REQUIRED before a document can
even enter PWG Last Call, much less be adopted.  It remains to be seen
if this can be achieved for IPP/2.x.

Cheers,
- Ira

On Tue, Mar 4, 2008 at 7:44 PM, Hastings, Tom N <Tom.Hastings@xerox.com>
wrote:
> The statement of work says:
>
>  *  OBJ-1 Include a reference to all IPP Standards Track documents,
>  starting from version 1.1.
>  *  OBJ-2 All current IPP features are to be included as a requirement
or
>  an option.
>  *  OBJ-3 All features are to be classified as Mandatory,
Conditionally
>  Mandatory, or Optional.
>
>  What is a "feature"?  What is the level of granularity of a feature?
An
>  operation, an object, an attribute, or an attribute value?
>
>  In other words, at what level of detail will the "Mandatory",
>  "Conditionally Mandatory" or "Optional" be specified at: an
operation,
>  an object, an attribute, or an attribute value?
>
>  The PWG Semantic model lists all of the operations, objects,
attributes,
>  and values (though spelled "funny"), along with the documents in
which
>  they are defined, if that is a help is compiling a profile template.
>
>  Tom
>
>
>
>  -----Original Message-----
>  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
>  Ron.Bergman@ricoh-usa.com
>  Sent: Thursday, February 21, 2008 09:56
>  To: ipp@pwg.org
>  Subject: IPP> IPPv2 Statement Of Work Update
>
>
>  The IPPv2 Charter has been converted into a Statement of Work.
>
>  Send any comments to the mail list.
>
>
>
ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-docs/wd-ippv2-statement-of-work-2008
>  0221.pdf
>   (.doc)
>
>
>
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434



From ipp-owner@pwg.org  Wed Mar  5 12:12:01 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB29D3A6F5E
	for <ietfarch-ipp-archive@core3.amsl.com>; Wed,  5 Mar 2008 12:12:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.258
X-Spam-Level: 
X-Spam-Status: No, score=-2.258 tagged_above=-999 required=5 tests=[AWL=0.341,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 7jcl7-hShsXS for <ietfarch-ipp-archive@core3.amsl.com>;
	Wed,  5 Mar 2008 12:12:00 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 52B7328C8BB
	for <ipp-archive@ietf.org>; Wed,  5 Mar 2008 12:10:46 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25K6E1u001292
	for <ipp-archive@ietf.org>; Wed, 5 Mar 2008 15:10:34 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m25Jganb026586
	for <ipp-archive@lists.ietf.org>; Wed, 5 Mar 2008 14:42:36 -0500
Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Mar 2008 14:41:51 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25JflBp026254
	for <ipp-outgoing@pwg.org>; Wed, 5 Mar 2008 14:41:49 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m25JflXQ026251
	for ipp-outgoing; Wed, 5 Mar 2008 14:41:47 -0500
Received: from njwcntas37.us.ricoh.ds (host150.ricoh-usa.com [208.252.21.150])
	by pwg.org  with ESMTP id m25JfiFp026239
	for <ipp@pwg.org>; Wed, 5 Mar 2008 14:41:46 -0500
X-SEF-Processed: 5_0_0_816__2008_03_05_14_41_43
Received: from Unknown [172.16.19.238] by njwcntas37.us.ricoh.ds - SurfControl E-mail Filter ; Wed, 05 Mar 2008 14:41:39 -0500
In-Reply-To: <559BCC0E42F1AA409F7603081DDB2C34B49851@usaesm1mf01.na.xerox.net>
Subject: RE: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define what a "feature" is]
To: "Hastings, Tom N" <Tom.Hastings@XEROX.COM>
Cc: "Ira McDonald" <blueroofmusic@gmail.com>, ipp@pwg.org
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF7706C10D.16082B24-ON88257403.006A0B32-88257403.006C2C69@ricoh-usa.com>
From: Ron.Bergman@ricoh-usa.com
Date: Wed, 5 Mar 2008 11:41:32 -0800
X-MIMETrack: Serialize by Router on NJWC02/RCUS(Release 7.0.2FP1|January 10, 2007) at 03/05/2008
 02:41:39 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-ipp@pwg.org


Hi Tom,

You have a good point which we need to consider.  Also, note that the
Notifications (RFC3995), ippget (RFC3996), and the Document Object (5100.5)
do have required operations.  Only the Set Operations (RFC3380) and the
Admin Operations (RFC3998) list just optional operations.

I don't know if we will need to dig deeper than the operations if do decide
to make some of the Set and Admin operations required.  The attributes and
values may not need to be addressed.  This will certainly be investigated
in the very near future.

Ron



                                                                           
             "Hastings, Tom N"                                             
             <Tom.Hastings@XER                                             
             OX.COM>                                                    To 
                                       "Ira McDonald"                      
             03/05/2008 10:18          <blueroofmusic@gmail.com>           
             AM                                                         cc 
                                       <Ron.Bergman@ricoh-usa.com>,        
                                       <ipp@pwg.org>                       
                                                                   Subject 
                                       RE: IPP> IPPv2 Statement Of Work    
                                       Update [ISSUE: need to define what  
                                       a "feature" is]                     
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Ira,

The problem that I have with your view that the IPPv2 Profiles just
lists IPP Standards is that most of the additional IPP standards define
additional operations, attributes, and values which are all OPTIONAL to
support.  In other words, they are just shopping lists of operations or
attributes (and attribute values).

For example, here is the abstract from RFC 3998: Job and Printer
Administrative Operations:

This document specifies the following 16 additional OPTIONAL system
administration operations for use with the Internet Printing
Protocol/1.1 (IPP) [RFC2910, RFC2911], plus a few associated attributes,
values, and status codes and using the IPP Printer object to manage
printer fan-out and fan-in.

As another example, here is the abstract from IEEE-ISTO PWG 5100.7-2003:
Standard for The Internet Printing Protocol (IPP): Job Extensions

Abstract: This IPP specification extends the Job semantics of the IPP
Model and Semantics [rfc2911] object model.  This specification defines
some new Operation attributes for use in Job Creation and Document
Creation operations.  The Printer copies these Operation attributes to
the corresponding Job Description attributes, which the clients may
query.  The Document Creation Operation attributes describe the Document
Content and permit the Printer to reject requests that it cannot process
correctly.  Some corresponding "xxx-default" and "xxx-supported" Printer
attributes are defined.  This specification defines some Job Template
attributes that apply to a multi-document Job as a whole and the
"output-device" Job Template attribute that can apply to Documents and
to Sheets as well as Jobs.  This specification also defines some
additional values for the "job-state-reasons" Job Description attribute.
Each of the attributes defined in this specification are independent of
each other and are OPTIONAL for a Printer to support.

All of the attributes defined are OPTIONAL for a Printer to support!

My recollection is that most of the extension IPP standards are like
this. Thus I think it would really help if each profile listed the
operations and attributes (any maybe attribute values) that are
MANDATORY, CONDITIONALLY MANDATORY (with their condition), and
OPTIONAL).


Back to my comment on the Statement of Work:

The ISSUE with the Statement of Work is to agree on what the undefined
term: "feature".  One interpretation (mine) is that each operation is a
"feature" and each attribute is a "feature".  Whether an attribute value
is also a feature needs to be clarified.  Without such an agreement on
what the term "feature" is, I think that people will have widely
differing understandings on what the IPPv2 project is about.

BTW, I like the idea of the IPPv2 project NOT trying to re-write,
clarify, or augment, the published standards.  I'm just questioning the
value of having a profile that points to set of IPP standards where each
IPP standard just contains a list of operations or attributes that are
all OPTIONAL.

Tom

-----Original Message-----
From: Ira McDonald [mailto:blueroofmusic@gmail.com]
Sent: Tuesday, March 04, 2008 19:42
To: Hastings, Tom N; Ira McDonald
Cc: Ron.Bergman@ricoh-usa.com; ipp@pwg.org
Subject: Re: IPP> IPPv2 Statement Of Work Update

Hi Tom,

My two cents - these profiles (i.e., version 2.0, 2.1, 2.2, etc.) should
ONLY
make whole IPP standards specs (IETF or PWG) mandatory, conditionally
mandatory, or optional.

Although there has been speculation that individual operations (but NOT
attributes) might be raised in requirements level from their original
specs,
I'm opposed to doing so.

The sole function of the IPP/2.x effort should be simply to encourage
more
widespread implementation of the many IPP extensions (a set of content
much larger than the entire original IPP/1.1 protocol).  And to simplify
the
description of such higher implementation functionality for end users.

Changing specific requirements levels *within* particular IPP specs is a
slippery slope that would destroy the IPP/2.x effort (and violate the
PWG
Process/2.0 rules).

Bear in mind that the PWG Process/2.0 is much more rigorous than past
PWG practice.  Actual prototypes are REQUIRED before a document can
even enter PWG Last Call, much less be adopted.  It remains to be seen
if this can be achieved for IPP/2.x.

Cheers,
- Ira

On Tue, Mar 4, 2008 at 7:44 PM, Hastings, Tom N <Tom.Hastings@xerox.com>
wrote:
> The statement of work says:
>
>  *  OBJ-1 Include a reference to all IPP Standards Track documents,
>  starting from version 1.1.
>  *  OBJ-2 All current IPP features are to be included as a requirement
or
>  an option.
>  *  OBJ-3 All features are to be classified as Mandatory,
Conditionally
>  Mandatory, or Optional.
>
>  What is a "feature"?  What is the level of granularity of a feature?
An
>  operation, an object, an attribute, or an attribute value?
>
>  In other words, at what level of detail will the "Mandatory",
>  "Conditionally Mandatory" or "Optional" be specified at: an
operation,
>  an object, an attribute, or an attribute value?
>
>  The PWG Semantic model lists all of the operations, objects,
attributes,
>  and values (though spelled "funny"), along with the documents in
which
>  they are defined, if that is a help is compiling a profile template.
>
>  Tom
>
>
>
>  -----Original Message-----
>  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
>  Ron.Bergman@ricoh-usa.com
>  Sent: Thursday, February 21, 2008 09:56
>  To: ipp@pwg.org
>  Subject: IPP> IPPv2 Statement Of Work Update
>
>
>  The IPPv2 Charter has been converted into a Statement of Work.
>
>  Send any comments to the mail list.
>
>
>
ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-docs/wd-ippv2-statement-of-work-2008
>  0221.pdf
>   (.doc)
>
>
>
>



--
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434






From ipp-owner@pwg.org  Wed Mar  5 12:15:30 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 76B303A6850
	for <ietfarch-ipp-archive@core3.amsl.com>; Wed,  5 Mar 2008 12:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nNgTsvAnVvvN for <ietfarch-ipp-archive@core3.amsl.com>;
	Wed,  5 Mar 2008 12:15:29 -0800 (PST)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 0870E28C19A
	for <ipp-archive@ietf.org>; Wed,  5 Mar 2008 12:14:56 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25K6E2g001292
	for <ipp-archive@ietf.org>; Wed, 5 Mar 2008 15:14:46 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m25JFp5s018878
	for <ipp-archive@lists.ietf.org>; Wed, 5 Mar 2008 14:15:51 -0500
Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Mar 2008 14:15:25 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25JFKfh018565
	for <ipp-outgoing@pwg.org>; Wed, 5 Mar 2008 14:15:22 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m25JFKtc018561
	for ipp-outgoing; Wed, 5 Mar 2008 14:15:20 -0500
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183])
	by pwg.org  with ESMTP id m25JFHIb018518
	for <ipp@pwg.org>; Wed, 5 Mar 2008 14:15:19 -0500
Received: by wa-out-1112.google.com with SMTP id j37so1547153waf.7
        for <ipp@pwg.org>; Wed, 05 Mar 2008 11:15:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=M5KHb2/XgncCgfuruj9ST/gLvFCRp9Ay/APMhNzqtCc=;
        b=osYeZXMo7yOXT8Pown1GIn2QYpbYX+PVPMv+06nsQJ5TFm2qoHRsmqbEQOqWP5OUUHcwISDWvY8+e++tne9yakRr3Gjsdvo/46e0ztqOz2rtI5fPQNCuwPUocD1mwyYGCA+PLwPOrwEdohFQR3nWuCfETMsTPoZpWEQJow3JOeE=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=G7x67n3eVMfWQel0W5kV1XtQsEoZdXjVfawgWtgB+zqHry+R5D5Ig5iQxrvVjzzLCLs62qjm1IcfQ4LwPZlabWjGF6JAMTf5P4cdWeRVjVE6FG7xNPf1gXYEr7X3lVw+sn9H3ACsCLhH88DIT9IPhW57y2camTfn3Lcad0jJC2E=
Received: by 10.114.193.1 with SMTP id q1mr5129300waf.75.1204744515601;
        Wed, 05 Mar 2008 11:15:15 -0800 (PST)
Received: by 10.115.17.1 with HTTP; Wed, 5 Mar 2008 11:15:10 -0800 (PST)
Message-ID: <e395be80803051115v5e1ff558m4d5c672b15b69c79@mail.gmail.com>
Date: Wed, 5 Mar 2008 14:15:10 -0500
From: "Ira McDonald" <blueroofmusic@gmail.com>
To: "Hastings, Tom N" <Tom.Hastings@XEROX.COM>,
        "Ira McDonald" <blueroofmusic@gmail.com>
Subject: Re: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define what a "feature" is]
Cc: Ron.Bergman@ricoh-usa.com, ipp@pwg.org
In-Reply-To: <559BCC0E42F1AA409F7603081DDB2C34B49851@usaesm1mf01.na.xerox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <OFCBFCD77A.61938A74-ON882573F6.006230DF-882573F6.00628AA8@ricoh-usa.com>
	 <559BCC0E42F1AA409F7603081DDB2C34B4984F@usaesm1mf01.na.xerox.net>
	 <e395be80803041942j133c813y6603374994dc1577@mail.gmail.com>
	 <559BCC0E42F1AA409F7603081DDB2C34B49851@usaesm1mf01.na.xerox.net>
Sender: owner-ipp@pwg.org

Hi Tom,

The PWG cannot change an IETF standard, EXCEPT through the formal
IETF standards process (none of us are young enough to attempt this
anymore).

The fact that all the operations in IPP System Admin (RFC 3998) are
OPTIONAL  to implement (within that spec itself) is a *defect* that the
IETF would have caught if anyone was watching, but the IETF published
that spec years late just to close "old business".

By contrast, the IPP Document Object (PWG 5100.5) has a good solid
set of REQUIRED operations defined in section 13.  Most PWG IPP specs
are appropriately rigorous.

Revising IETF or PWG IPP specs is out of the question - no manpower.

In IETF and W3C parlance, a "feature" is a set of one or more Operations
and any Attributes/Values required by those Operations.

Going down to the level of the complete set of Attributes is not feasible.

There's still a four-year-old action to register with IANA all of the IPP
Operations and Attributes/Values in PWG IPP specs - none have ever
been registered!

For the admittedly deficient IETF IPP extension specs, I'd would support
an effort to develop on a short list of Operations (per spec) that are
REQUIRED by (one of) the IPP/2.x profiles.

Cheers,
- Ira

PS - Agreeing on *which* IPP system admin operations should be
REQUIRED is very likely to be a fruitless debate, but we can try.

On Wed, Mar 5, 2008 at 1:18 PM, Hastings, Tom N <Tom.Hastings@xerox.com> wrote:
> Ira,
>
>  The problem that I have with your view that the IPPv2 Profiles just
>  lists IPP Standards is that most of the additional IPP standards define
>  additional operations, attributes, and values which are all OPTIONAL to
>  support.  In other words, they are just shopping lists of operations or
>  attributes (and attribute values).
>
>  For example, here is the abstract from RFC 3998: Job and Printer
>  Administrative Operations:
>
>  This document specifies the following 16 additional OPTIONAL system
>  administration operations for use with the Internet Printing
>  Protocol/1.1 (IPP) [RFC2910, RFC2911], plus a few associated attributes,
>  values, and status codes and using the IPP Printer object to manage
>  printer fan-out and fan-in.
>
>  As another example, here is the abstract from IEEE-ISTO PWG 5100.7-2003:
>  Standard for The Internet Printing Protocol (IPP): Job Extensions
>
>  Abstract: This IPP specification extends the Job semantics of the IPP
>  Model and Semantics [rfc2911] object model.  This specification defines
>  some new Operation attributes for use in Job Creation and Document
>  Creation operations.  The Printer copies these Operation attributes to
>  the corresponding Job Description attributes, which the clients may
>  query.  The Document Creation Operation attributes describe the Document
>  Content and permit the Printer to reject requests that it cannot process
>  correctly.  Some corresponding "xxx-default" and "xxx-supported" Printer
>  attributes are defined.  This specification defines some Job Template
>  attributes that apply to a multi-document Job as a whole and the
>  "output-device" Job Template attribute that can apply to Documents and
>  to Sheets as well as Jobs.  This specification also defines some
>  additional values for the "job-state-reasons" Job Description attribute.
>  Each of the attributes defined in this specification are independent of
>  each other and are OPTIONAL for a Printer to support.
>
>  All of the attributes defined are OPTIONAL for a Printer to support!
>
>  My recollection is that most of the extension IPP standards are like
>  this. Thus I think it would really help if each profile listed the
>  operations and attributes (any maybe attribute values) that are
>  MANDATORY, CONDITIONALLY MANDATORY (with their condition), and
>  OPTIONAL).
>
>
>  Back to my comment on the Statement of Work:
>
>  The ISSUE with the Statement of Work is to agree on what the undefined
>  term: "feature".  One interpretation (mine) is that each operation is a
>  "feature" and each attribute is a "feature".  Whether an attribute value
>  is also a feature needs to be clarified.  Without such an agreement on
>  what the term "feature" is, I think that people will have widely
>  differing understandings on what the IPPv2 project is about.
>
>  BTW, I like the idea of the IPPv2 project NOT trying to re-write,
>  clarify, or augment, the published standards.  I'm just questioning the
>  value of having a profile that points to set of IPP standards where each
>  IPP standard just contains a list of operations or attributes that are
>  all OPTIONAL.
>
>  Tom
>
>  -----Original Message-----
>  From: Ira McDonald [mailto:blueroofmusic@gmail.com]
>  Sent: Tuesday, March 04, 2008 19:42
>  To: Hastings, Tom N; Ira McDonald
>  Cc: Ron.Bergman@ricoh-usa.com; ipp@pwg.org
>  Subject: Re: IPP> IPPv2 Statement Of Work Update
>
>  Hi Tom,
>
>  My two cents - these profiles (i.e., version 2.0, 2.1, 2.2, etc.) should
>  ONLY
>  make whole IPP standards specs (IETF or PWG) mandatory, conditionally
>  mandatory, or optional.
>
>  Although there has been speculation that individual operations (but NOT
>  attributes) might be raised in requirements level from their original
>  specs,
>  I'm opposed to doing so.
>
>  The sole function of the IPP/2.x effort should be simply to encourage
>  more
>  widespread implementation of the many IPP extensions (a set of content
>  much larger than the entire original IPP/1.1 protocol).  And to simplify
>  the
>  description of such higher implementation functionality for end users.
>
>  Changing specific requirements levels *within* particular IPP specs is a
>  slippery slope that would destroy the IPP/2.x effort (and violate the
>  PWG
>  Process/2.0 rules).
>
>  Bear in mind that the PWG Process/2.0 is much more rigorous than past
>  PWG practice.  Actual prototypes are REQUIRED before a document can
>  even enter PWG Last Call, much less be adopted.  It remains to be seen
>  if this can be achieved for IPP/2.x.
>
>  Cheers,
>  - Ira
>
>  On Tue, Mar 4, 2008 at 7:44 PM, Hastings, Tom N <Tom.Hastings@xerox.com>
>  wrote:
>  > The statement of work says:
>  >
>  >  *  OBJ-1 Include a reference to all IPP Standards Track documents,
>  >  starting from version 1.1.
>  >  *  OBJ-2 All current IPP features are to be included as a requirement
>  or
>  >  an option.
>  >  *  OBJ-3 All features are to be classified as Mandatory,
>  Conditionally
>  >  Mandatory, or Optional.
>  >
>  >  What is a "feature"?  What is the level of granularity of a feature?
>  An
>  >  operation, an object, an attribute, or an attribute value?
>  >
>  >  In other words, at what level of detail will the "Mandatory",
>  >  "Conditionally Mandatory" or "Optional" be specified at: an
>  operation,
>  >  an object, an attribute, or an attribute value?
>  >
>  >  The PWG Semantic model lists all of the operations, objects,
>  attributes,
>  >  and values (though spelled "funny"), along with the documents in
>  which
>  >  they are defined, if that is a help is compiling a profile template.
>  >
>  >  Tom
>  >
>  >
>  >
>  >  -----Original Message-----
>  >  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
>  >  Ron.Bergman@ricoh-usa.com
>  >  Sent: Thursday, February 21, 2008 09:56
>  >  To: ipp@pwg.org
>  >  Subject: IPP> IPPv2 Statement Of Work Update
>  >
>  >
>  >  The IPPv2 Charter has been converted into a Statement of Work.
>  >
>  >  Send any comments to the mail list.
>  >
>  >
>  >
>  ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-docs/wd-ippv2-statement-of-work-2008
>  >  0221.pdf
>  >   (.doc)
>  >
>  >
>  >
>  >
>
>
>
>  --
>  Ira McDonald (Musician / Software Architect)
>  Chair - Linux Foundation Open Printing WG
>  Blue Roof Music/High North Inc
>  email: blueroofmusic@gmail.com
>  winter:
>   579 Park Place  Saline, MI  48176
>   734-944-0094
>  summer:
>   PO Box 221  Grand Marais, MI 49839
>   906-494-2434
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434


From ipp-owner@pwg.org  Wed Mar  5 13:01:14 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DEA473A6B8B
	for <ietfarch-ipp-archive@core3.amsl.com>; Wed,  5 Mar 2008 13:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id t7mUdgKr1TX2 for <ietfarch-ipp-archive@core3.amsl.com>;
	Wed,  5 Mar 2008 13:01:13 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 617273A6A0D
	for <ipp-archive@ietf.org>; Wed,  5 Mar 2008 13:01:13 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25L10u5009607
	for <ipp-archive@ietf.org>; Wed, 5 Mar 2008 16:01:02 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m25L1056009603
	for <ipp-archive@lists.ietf.org>; Wed, 5 Mar 2008 16:01:00 -0500
Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Mar 2008 15:59:55 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m25KxpYi009287
	for <ipp-outgoing@pwg.org>; Wed, 5 Mar 2008 15:59:53 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m25KxpIA009284
	for ipp-outgoing; Wed, 5 Mar 2008 15:59:51 -0500
Received: from wbmler3.mail.xerox.com (wbmler3.mail.xerox.com [13.13.138.218])
	by pwg.org  with ESMTP id m25KxmNW009280
	for <ipp@pwg.org>; Wed, 5 Mar 2008 15:59:50 -0500
Received: from wbmlir1.mail.xerox.com (wbmlir1.mail.xerox.com [13.131.8.221])
	by wbmler3.mail.xerox.com (8.13.8/8.13.8) with ESMTP id m25KxjDG006968;
	Wed, 5 Mar 2008 15:59:45 -0500
Received: from wbmlir1.mail.xerox.com (localhost [127.0.0.1])
	by wbmlir1.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m25Kxawh023534;
	Wed, 5 Mar 2008 15:59:36 -0500
Received: from USA7061GW002.na.xerox.net (usa7061gw002.na.xerox.net [13.151.210.15])
	by wbmlir1.mail.xerox.com (8.13.8/8.13.6) with ESMTP id m25KxTcJ023301;
	Wed, 5 Mar 2008 15:59:35 -0500
X-Xerox-Source-Ip: 13.151.210.15
X-Xerox-Source-Name: usa7061gw002.na.xerox.net
X-Xerox-Reported-Name: USA7061GW002.na.xerox.net
Received: from usaesm1mf01.na.xerox.net ([13.241.1.17]) by USA7061GW002.na.xerox.net with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 5 Mar 2008 12:59:35 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define what a "feature" is]
Date: Wed, 5 Mar 2008 12:59:34 -0800
Message-ID: <559BCC0E42F1AA409F7603081DDB2C34B49852@usaesm1mf01.na.xerox.net>
In-Reply-To: <e395be80803051115v5e1ff558m4d5c672b15b69c79@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define what a "feature" is]
thread-index: Ach+/tWX3dR6m5/xQFajZ7NOExVmDwABIDbA
References: <OFCBFCD77A.61938A74-ON882573F6.006230DF-882573F6.00628AA8@ricoh-usa.com> <559BCC0E42F1AA409F7603081DDB2C34B4984F@usaesm1mf01.na.xerox.net> <e395be80803041942j133c813y6603374994dc1577@mail.gmail.com> <559BCC0E42F1AA409F7603081DDB2C34B49851@usaesm1mf01.na.xerox.net> <e395be80803051115v5e1ff558m4d5c672b15b69c79@mail.gmail.com>
From: "Hastings, Tom N" <Tom.Hastings@xerox.com>
To: "Ira McDonald" <blueroofmusic@gmail.com>
Cc: <Ron.Bergman@ricoh-usa.com>, <ipp@pwg.org>
X-OriginalArrivalTime: 05 Mar 2008 20:59:35.0261 (UTC) FILETIME=[D14468D0:01C87F03]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id m25KxoNW009282
Sender: owner-ipp@pwg.org

Ira,

I agree that we should not revise any existing standard.  However, I see
no problem with a new standard profile that this IPPv2 project is
developing saying that operation XYZ from standard mno is REQUIRED in
order to conform to the profile that is being defined by the new
standard, even if operation XYZ is OPTIONAL in standard mno.

What's wrong with that?

Tom

-----Original Message-----
From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of Ira
McDonald
Sent: Wednesday, March 05, 2008 11:15
To: Hastings, Tom N; Ira McDonald
Cc: Ron.Bergman@ricoh-usa.com; ipp@pwg.org
Subject: Re: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define
what a "feature" is]

Hi Tom,

The PWG cannot change an IETF standard, EXCEPT through the formal
IETF standards process (none of us are young enough to attempt this
anymore).

The fact that all the operations in IPP System Admin (RFC 3998) are
OPTIONAL  to implement (within that spec itself) is a *defect* that the
IETF would have caught if anyone was watching, but the IETF published
that spec years late just to close "old business".

By contrast, the IPP Document Object (PWG 5100.5) has a good solid
set of REQUIRED operations defined in section 13.  Most PWG IPP specs
are appropriately rigorous.

Revising IETF or PWG IPP specs is out of the question - no manpower.

In IETF and W3C parlance, a "feature" is a set of one or more Operations
and any Attributes/Values required by those Operations.

Going down to the level of the complete set of Attributes is not
feasible.

There's still a four-year-old action to register with IANA all of the
IPP
Operations and Attributes/Values in PWG IPP specs - none have ever
been registered!

For the admittedly deficient IETF IPP extension specs, I'd would support
an effort to develop on a short list of Operations (per spec) that are
REQUIRED by (one of) the IPP/2.x profiles.

Cheers,
- Ira

PS - Agreeing on *which* IPP system admin operations should be
REQUIRED is very likely to be a fruitless debate, but we can try.

On Wed, Mar 5, 2008 at 1:18 PM, Hastings, Tom N <Tom.Hastings@xerox.com>
wrote:
> Ira,
>
>  The problem that I have with your view that the IPPv2 Profiles just
>  lists IPP Standards is that most of the additional IPP standards
define
>  additional operations, attributes, and values which are all OPTIONAL
to
>  support.  In other words, they are just shopping lists of operations
or
>  attributes (and attribute values).
>
>  For example, here is the abstract from RFC 3998: Job and Printer
>  Administrative Operations:
>
>  This document specifies the following 16 additional OPTIONAL system
>  administration operations for use with the Internet Printing
>  Protocol/1.1 (IPP) [RFC2910, RFC2911], plus a few associated
attributes,
>  values, and status codes and using the IPP Printer object to manage
>  printer fan-out and fan-in.
>
>  As another example, here is the abstract from IEEE-ISTO PWG
5100.7-2003:
>  Standard for The Internet Printing Protocol (IPP): Job Extensions
>
>  Abstract: This IPP specification extends the Job semantics of the IPP
>  Model and Semantics [rfc2911] object model.  This specification
defines
>  some new Operation attributes for use in Job Creation and Document
>  Creation operations.  The Printer copies these Operation attributes
to
>  the corresponding Job Description attributes, which the clients may
>  query.  The Document Creation Operation attributes describe the
Document
>  Content and permit the Printer to reject requests that it cannot
process
>  correctly.  Some corresponding "xxx-default" and "xxx-supported"
Printer
>  attributes are defined.  This specification defines some Job Template
>  attributes that apply to a multi-document Job as a whole and the
>  "output-device" Job Template attribute that can apply to Documents
and
>  to Sheets as well as Jobs.  This specification also defines some
>  additional values for the "job-state-reasons" Job Description
attribute.
>  Each of the attributes defined in this specification are independent
of
>  each other and are OPTIONAL for a Printer to support.
>
>  All of the attributes defined are OPTIONAL for a Printer to support!
>
>  My recollection is that most of the extension IPP standards are like
>  this. Thus I think it would really help if each profile listed the
>  operations and attributes (any maybe attribute values) that are
>  MANDATORY, CONDITIONALLY MANDATORY (with their condition), and
>  OPTIONAL).
>
>
>  Back to my comment on the Statement of Work:
>
>  The ISSUE with the Statement of Work is to agree on what the
undefined
>  term: "feature".  One interpretation (mine) is that each operation is
a
>  "feature" and each attribute is a "feature".  Whether an attribute
value
>  is also a feature needs to be clarified.  Without such an agreement
on
>  what the term "feature" is, I think that people will have widely
>  differing understandings on what the IPPv2 project is about.
>
>  BTW, I like the idea of the IPPv2 project NOT trying to re-write,
>  clarify, or augment, the published standards.  I'm just questioning
the
>  value of having a profile that points to set of IPP standards where
each
>  IPP standard just contains a list of operations or attributes that
are
>  all OPTIONAL.
>
>  Tom
>
>  -----Original Message-----
>  From: Ira McDonald [mailto:blueroofmusic@gmail.com]
>  Sent: Tuesday, March 04, 2008 19:42
>  To: Hastings, Tom N; Ira McDonald
>  Cc: Ron.Bergman@ricoh-usa.com; ipp@pwg.org
>  Subject: Re: IPP> IPPv2 Statement Of Work Update
>
>  Hi Tom,
>
>  My two cents - these profiles (i.e., version 2.0, 2.1, 2.2, etc.)
should
>  ONLY
>  make whole IPP standards specs (IETF or PWG) mandatory, conditionally
>  mandatory, or optional.
>
>  Although there has been speculation that individual operations (but
NOT
>  attributes) might be raised in requirements level from their original
>  specs,
>  I'm opposed to doing so.
>
>  The sole function of the IPP/2.x effort should be simply to encourage
>  more
>  widespread implementation of the many IPP extensions (a set of
content
>  much larger than the entire original IPP/1.1 protocol).  And to
simplify
>  the
>  description of such higher implementation functionality for end
users.
>
>  Changing specific requirements levels *within* particular IPP specs
is a
>  slippery slope that would destroy the IPP/2.x effort (and violate the
>  PWG
>  Process/2.0 rules).
>
>  Bear in mind that the PWG Process/2.0 is much more rigorous than past
>  PWG practice.  Actual prototypes are REQUIRED before a document can
>  even enter PWG Last Call, much less be adopted.  It remains to be
seen
>  if this can be achieved for IPP/2.x.
>
>  Cheers,
>  - Ira
>
>  On Tue, Mar 4, 2008 at 7:44 PM, Hastings, Tom N
<Tom.Hastings@xerox.com>
>  wrote:
>  > The statement of work says:
>  >
>  >  *  OBJ-1 Include a reference to all IPP Standards Track documents,
>  >  starting from version 1.1.
>  >  *  OBJ-2 All current IPP features are to be included as a
requirement
>  or
>  >  an option.
>  >  *  OBJ-3 All features are to be classified as Mandatory,
>  Conditionally
>  >  Mandatory, or Optional.
>  >
>  >  What is a "feature"?  What is the level of granularity of a
feature?
>  An
>  >  operation, an object, an attribute, or an attribute value?
>  >
>  >  In other words, at what level of detail will the "Mandatory",
>  >  "Conditionally Mandatory" or "Optional" be specified at: an
>  operation,
>  >  an object, an attribute, or an attribute value?
>  >
>  >  The PWG Semantic model lists all of the operations, objects,
>  attributes,
>  >  and values (though spelled "funny"), along with the documents in
>  which
>  >  they are defined, if that is a help is compiling a profile
template.
>  >
>  >  Tom
>  >
>  >
>  >
>  >  -----Original Message-----
>  >  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
>  >  Ron.Bergman@ricoh-usa.com
>  >  Sent: Thursday, February 21, 2008 09:56
>  >  To: ipp@pwg.org
>  >  Subject: IPP> IPPv2 Statement Of Work Update
>  >
>  >
>  >  The IPPv2 Charter has been converted into a Statement of Work.
>  >
>  >  Send any comments to the mail list.
>  >
>  >
>  >
>
ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-docs/wd-ippv2-statement-of-work-2008
>  >  0221.pdf
>  >   (.doc)
>  >
>  >
>  >
>  >
>
>
>
>  --
>  Ira McDonald (Musician / Software Architect)
>  Chair - Linux Foundation Open Printing WG
>  Blue Roof Music/High North Inc
>  email: blueroofmusic@gmail.com
>  winter:
>   579 Park Place  Saline, MI  48176
>   734-944-0094
>  summer:
>   PO Box 221  Grand Marais, MI 49839
>   906-494-2434
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434



From ipp-owner@pwg.org  Wed Mar  5 16:44:31 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED3EE28C285
	for <ietfarch-ipp-archive@core3.amsl.com>; Wed,  5 Mar 2008 16:44:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id aGmU4VSXG6lI for <ietfarch-ipp-archive@core3.amsl.com>;
	Wed,  5 Mar 2008 16:44:30 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 2BC9128C7F1
	for <ipp-archive@ietf.org>; Wed,  5 Mar 2008 16:43:50 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m260hbNF003508
	for <ipp-archive@ietf.org>; Wed, 5 Mar 2008 19:43:39 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m260havl003505
	for <ipp-archive@lists.ietf.org>; Wed, 5 Mar 2008 19:43:37 -0500
Received: by pwg.org (bulk_mailer v1.13); Wed, 5 Mar 2008 19:42:22 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m260gHOA003241
	for <ipp-outgoing@pwg.org>; Wed, 5 Mar 2008 19:42:19 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m260gH7j003238
	for ipp-outgoing; Wed, 5 Mar 2008 19:42:17 -0500
Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.230])
	by pwg.org  with ESMTP id m260gE0a003230
	for <ipp@pwg.org>; Wed, 5 Mar 2008 19:42:16 -0500
Received: by qb-out-0506.google.com with SMTP id e11so1579799qba.1
        for <ipp@pwg.org>; Wed, 05 Mar 2008 16:42:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=Q3Xrg3hCg4cvW0pB3cF/iy7meDWs9A9t/jojzXnlHo4=;
        b=vKeS0DE//jLtBzhkLSQbph2IQ25+KOiX5SZWnfRWl1bh33k8Sdys3Z2ndypVXnSfpuYIriC3E49IK9/B2Vi92fYpspAh6/XTBs5kE1DDkWpG4FoUydJ2ZMi0sEuzSHfEXnQcwcsmWwyjRdkdsR+p+/wQdM2eeZjmDZua4IlCbdg=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=eEXibMXgmjN+QYABllGj9UTUZKSvUWnBFAleeN28hUjBEGOhzr6Nvj1COz1Yfko0h8ipXuCdEe6xzFw1RWEV/azcjMQyffH5vKWArAc8dLlHXdAVixYVBadozYteSvYrg6SStVM3YDO9GGk3um6qu53f++SXTIJuyThlwgwCALk=
Received: by 10.114.125.2 with SMTP id x2mr5670513wac.119.1204764133374;
        Wed, 05 Mar 2008 16:42:13 -0800 (PST)
Received: by 10.115.17.1 with HTTP; Wed, 5 Mar 2008 16:42:13 -0800 (PST)
Message-ID: <e395be80803051642j289e15bdm82ac623cd31874b@mail.gmail.com>
Date: Wed, 5 Mar 2008 19:42:13 -0500
From: "Ira McDonald" <blueroofmusic@gmail.com>
To: "Hastings, Tom N" <Tom.Hastings@xerox.com>,
        "Ira McDonald" <blueroofmusic@gmail.com>
Subject: Re: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define what a "feature" is]
Cc: Ron.Bergman@ricoh-usa.com, ipp@pwg.org
In-Reply-To: <559BCC0E42F1AA409F7603081DDB2C34B49852@usaesm1mf01.na.xerox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <OFCBFCD77A.61938A74-ON882573F6.006230DF-882573F6.00628AA8@ricoh-usa.com>
	 <559BCC0E42F1AA409F7603081DDB2C34B4984F@usaesm1mf01.na.xerox.net>
	 <e395be80803041942j133c813y6603374994dc1577@mail.gmail.com>
	 <559BCC0E42F1AA409F7603081DDB2C34B49851@usaesm1mf01.na.xerox.net>
	 <e395be80803051115v5e1ff558m4d5c672b15b69c79@mail.gmail.com>
	 <559BCC0E42F1AA409F7603081DDB2C34B49852@usaesm1mf01.na.xerox.net>
Sender: owner-ipp@pwg.org

Hi Tom,

I agree with you that we can raise OPTIONAL operations (from source
standards) to REQUIRED in an IPP/2.x profile.

I hoped to avoid this, but it seems necessary - or system admin, in
particular, is meaningless.

Now to see if many IPP implementations all chose the same operations
(ah, I see a pig flying...).

Cheers,
- Ira

On Wed, Mar 5, 2008 at 3:59 PM, Hastings, Tom N <Tom.Hastings@xerox.com> wrote:
> Ira,
>
>  I agree that we should not revise any existing standard.  However, I see
>  no problem with a new standard profile that this IPPv2 project is
>  developing saying that operation XYZ from standard mno is REQUIRED in
>  order to conform to the profile that is being defined by the new
>  standard, even if operation XYZ is OPTIONAL in standard mno.
>
>  What's wrong with that?
>
>  Tom
>
>
>  -----Original Message-----
>  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of Ira
>  McDonald
>  Sent: Wednesday, March 05, 2008 11:15
>  To: Hastings, Tom N; Ira McDonald
>  Cc: Ron.Bergman@ricoh-usa.com; ipp@pwg.org
>
> Subject: Re: IPP> IPPv2 Statement Of Work Update [ISSUE: need to define
>  what a "feature" is]
>
>
>
> Hi Tom,
>
>  The PWG cannot change an IETF standard, EXCEPT through the formal
>  IETF standards process (none of us are young enough to attempt this
>  anymore).
>
>  The fact that all the operations in IPP System Admin (RFC 3998) are
>  OPTIONAL  to implement (within that spec itself) is a *defect* that the
>  IETF would have caught if anyone was watching, but the IETF published
>  that spec years late just to close "old business".
>
>  By contrast, the IPP Document Object (PWG 5100.5) has a good solid
>  set of REQUIRED operations defined in section 13.  Most PWG IPP specs
>  are appropriately rigorous.
>
>  Revising IETF or PWG IPP specs is out of the question - no manpower.
>
>  In IETF and W3C parlance, a "feature" is a set of one or more Operations
>  and any Attributes/Values required by those Operations.
>
>  Going down to the level of the complete set of Attributes is not
>  feasible.
>
>  There's still a four-year-old action to register with IANA all of the
>  IPP
>  Operations and Attributes/Values in PWG IPP specs - none have ever
>  been registered!
>
>  For the admittedly deficient IETF IPP extension specs, I'd would support
>  an effort to develop on a short list of Operations (per spec) that are
>  REQUIRED by (one of) the IPP/2.x profiles.
>
>  Cheers,
>  - Ira
>
>  PS - Agreeing on *which* IPP system admin operations should be
>  REQUIRED is very likely to be a fruitless debate, but we can try.
>
>  On Wed, Mar 5, 2008 at 1:18 PM, Hastings, Tom N <Tom.Hastings@xerox.com>
>  wrote:
>  > Ira,
>  >
>  >  The problem that I have with your view that the IPPv2 Profiles just
>  >  lists IPP Standards is that most of the additional IPP standards
>  define
>  >  additional operations, attributes, and values which are all OPTIONAL
>  to
>  >  support.  In other words, they are just shopping lists of operations
>  or
>  >  attributes (and attribute values).
>  >
>  >  For example, here is the abstract from RFC 3998: Job and Printer
>  >  Administrative Operations:
>  >
>  >  This document specifies the following 16 additional OPTIONAL system
>  >  administration operations for use with the Internet Printing
>  >  Protocol/1.1 (IPP) [RFC2910, RFC2911], plus a few associated
>  attributes,
>  >  values, and status codes and using the IPP Printer object to manage
>  >  printer fan-out and fan-in.
>  >
>  >  As another example, here is the abstract from IEEE-ISTO PWG
>  5100.7-2003:
>  >  Standard for The Internet Printing Protocol (IPP): Job Extensions
>  >
>  >  Abstract: This IPP specification extends the Job semantics of the IPP
>  >  Model and Semantics [rfc2911] object model.  This specification
>  defines
>  >  some new Operation attributes for use in Job Creation and Document
>  >  Creation operations.  The Printer copies these Operation attributes
>  to
>  >  the corresponding Job Description attributes, which the clients may
>  >  query.  The Document Creation Operation attributes describe the
>  Document
>  >  Content and permit the Printer to reject requests that it cannot
>  process
>  >  correctly.  Some corresponding "xxx-default" and "xxx-supported"
>  Printer
>  >  attributes are defined.  This specification defines some Job Template
>  >  attributes that apply to a multi-document Job as a whole and the
>  >  "output-device" Job Template attribute that can apply to Documents
>  and
>  >  to Sheets as well as Jobs.  This specification also defines some
>  >  additional values for the "job-state-reasons" Job Description
>  attribute.
>  >  Each of the attributes defined in this specification are independent
>  of
>  >  each other and are OPTIONAL for a Printer to support.
>  >
>  >  All of the attributes defined are OPTIONAL for a Printer to support!
>  >
>  >  My recollection is that most of the extension IPP standards are like
>  >  this. Thus I think it would really help if each profile listed the
>  >  operations and attributes (any maybe attribute values) that are
>  >  MANDATORY, CONDITIONALLY MANDATORY (with their condition), and
>  >  OPTIONAL).
>  >
>  >
>  >  Back to my comment on the Statement of Work:
>  >
>  >  The ISSUE with the Statement of Work is to agree on what the
>  undefined
>  >  term: "feature".  One interpretation (mine) is that each operation is
>  a
>  >  "feature" and each attribute is a "feature".  Whether an attribute
>  value
>  >  is also a feature needs to be clarified.  Without such an agreement
>  on
>  >  what the term "feature" is, I think that people will have widely
>  >  differing understandings on what the IPPv2 project is about.
>  >
>  >  BTW, I like the idea of the IPPv2 project NOT trying to re-write,
>  >  clarify, or augment, the published standards.  I'm just questioning
>  the
>  >  value of having a profile that points to set of IPP standards where
>  each
>  >  IPP standard just contains a list of operations or attributes that
>  are
>  >  all OPTIONAL.
>  >
>  >  Tom
>  >
>  >  -----Original Message-----
>  >  From: Ira McDonald [mailto:blueroofmusic@gmail.com]
>  >  Sent: Tuesday, March 04, 2008 19:42
>  >  To: Hastings, Tom N; Ira McDonald
>  >  Cc: Ron.Bergman@ricoh-usa.com; ipp@pwg.org
>  >  Subject: Re: IPP> IPPv2 Statement Of Work Update
>  >
>  >  Hi Tom,
>  >
>  >  My two cents - these profiles (i.e., version 2.0, 2.1, 2.2, etc.)
>  should
>  >  ONLY
>  >  make whole IPP standards specs (IETF or PWG) mandatory, conditionally
>  >  mandatory, or optional.
>  >
>  >  Although there has been speculation that individual operations (but
>  NOT
>  >  attributes) might be raised in requirements level from their original
>  >  specs,
>  >  I'm opposed to doing so.
>  >
>  >  The sole function of the IPP/2.x effort should be simply to encourage
>  >  more
>  >  widespread implementation of the many IPP extensions (a set of
>  content
>  >  much larger than the entire original IPP/1.1 protocol).  And to
>  simplify
>  >  the
>  >  description of such higher implementation functionality for end
>  users.
>  >
>  >  Changing specific requirements levels *within* particular IPP specs
>  is a
>  >  slippery slope that would destroy the IPP/2.x effort (and violate the
>  >  PWG
>  >  Process/2.0 rules).
>  >
>  >  Bear in mind that the PWG Process/2.0 is much more rigorous than past
>  >  PWG practice.  Actual prototypes are REQUIRED before a document can
>  >  even enter PWG Last Call, much less be adopted.  It remains to be
>  seen
>  >  if this can be achieved for IPP/2.x.
>  >
>  >  Cheers,
>  >  - Ira
>  >
>  >  On Tue, Mar 4, 2008 at 7:44 PM, Hastings, Tom N
>  <Tom.Hastings@xerox.com>
>  >  wrote:
>  >  > The statement of work says:
>  >  >
>  >  >  *  OBJ-1 Include a reference to all IPP Standards Track documents,
>  >  >  starting from version 1.1.
>  >  >  *  OBJ-2 All current IPP features are to be included as a
>  requirement
>  >  or
>  >  >  an option.
>  >  >  *  OBJ-3 All features are to be classified as Mandatory,
>  >  Conditionally
>  >  >  Mandatory, or Optional.
>  >  >
>  >  >  What is a "feature"?  What is the level of granularity of a
>  feature?
>  >  An
>  >  >  operation, an object, an attribute, or an attribute value?
>  >  >
>  >  >  In other words, at what level of detail will the "Mandatory",
>  >  >  "Conditionally Mandatory" or "Optional" be specified at: an
>  >  operation,
>  >  >  an object, an attribute, or an attribute value?
>  >  >
>  >  >  The PWG Semantic model lists all of the operations, objects,
>  >  attributes,
>  >  >  and values (though spelled "funny"), along with the documents in
>  >  which
>  >  >  they are defined, if that is a help is compiling a profile
>  template.
>  >  >
>  >  >  Tom
>  >  >
>  >  >
>  >  >
>  >  >  -----Original Message-----
>  >  >  From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
>  >  >  Ron.Bergman@ricoh-usa.com
>  >  >  Sent: Thursday, February 21, 2008 09:56
>  >  >  To: ipp@pwg.org
>  >  >  Subject: IPP> IPPv2 Statement Of Work Update
>  >  >
>  >  >
>  >  >  The IPPv2 Charter has been converted into a Statement of Work.
>  >  >
>  >  >  Send any comments to the mail list.
>  >  >
>  >  >
>  >  >
>  >
>  ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-docs/wd-ippv2-statement-of-work-2008
>  >  >  0221.pdf
>  >  >   (.doc)
>  >  >
>  >  >
>  >  >
>  >  >
>  >
>  >
>  >
>  >  --
>  >  Ira McDonald (Musician / Software Architect)
>  >  Chair - Linux Foundation Open Printing WG
>  >  Blue Roof Music/High North Inc
>  >  email: blueroofmusic@gmail.com
>  >  winter:
>  >   579 Park Place  Saline, MI  48176
>  >   734-944-0094
>  >  summer:
>  >   PO Box 221  Grand Marais, MI 49839
>  >   906-494-2434
>  >
>
>
>
>  --
>  Ira McDonald (Musician / Software Architect)
>  Chair - Linux Foundation Open Printing WG
>  Blue Roof Music/High North Inc
>  email: blueroofmusic@gmail.com
>  winter:
>   579 Park Place  Saline, MI  48176
>   734-944-0094
>  summer:
>   PO Box 221  Grand Marais, MI 49839
>   906-494-2434
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434


From pwg-announce-owner@pwg.org  Thu Mar  6 12:24:59 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2319328C94C;
	Thu,  6 Mar 2008 12:24:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.244
X-Spam-Level: 
X-Spam-Status: No, score=0.244 tagged_above=-999 required=5 tests=[AWL=0.317,
	BAYES_00=-2.599, HTML_IMAGE_ONLY_16=1.526, HTML_MESSAGE=1]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Rl019MAvSCCi; Thu,  6 Mar 2008 12:24:57 -0800 (PST)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 3838B28C998;
	Thu,  6 Mar 2008 12:24:49 -0800 (PST)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m26KOaBI017842;
	Thu, 6 Mar 2008 15:24:38 -0500
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m26KOZmq017839;
	Thu, 6 Mar 2008 15:24:35 -0500
Received: by pwg.org (bulk_mailer v1.13); Thu, 6 Mar 2008 15:22:38 -0500
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m26KMYYZ017361
	for <pwg-announce-out@pwg.org>; Thu, 6 Mar 2008 15:22:36 -0500
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m26KMYJ1017358
	for pwg-announce-out; Thu, 6 Mar 2008 15:22:34 -0500
To: pwg-announce@pwg.org
MIME-Version: 1.0
Subject: PWG-ANNOUNCE> PLEASE VOTE - PWG Imaging State and Counter MIB v2
X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006
Message-ID: <OFB6866AD8.259015D1-ON87257404.006F7066-87257404.0069F29D@us.ibm.com>
From: Harry Lewis <harryl@us.ibm.com>
Date: Thu, 6 Mar 2008 12:17:37 -0700
X-MIMETrack: Serialize by Router on D03NM132/03/M/IBM(Release 7.0.2FP2HF300 | September
 14, 2007) at 03/06/2008 13:22:29,
	Serialize complete at 03/06/2008 13:22:29
Content-Type: multipart/related; boundary="=_related 0069F29C87257404_="
Sender: owner-pwg-announce@pwg.org

This is a multipart message in MIME format.
--=_related 0069F29C87257404_=
Content-Type: multipart/alternative; boundary="=_alternative 0069F29C87257404_="


--=_alternative 0069F29C87257404_=
Content-Type: text/plain; charset="US-ASCII"

There remains a little over 1 week until voting closes on Formal Approval 
for the PWG Imaging State and Counter MIBv2. 

To cast a vote, please send an email with the following subject line 
format: 
"Counter MIB v2 Formal Vote-<company name>-<last name of 
voter>-<yes/no/abstain>" 
Example: Counter MIB v2 Formal Vote-InfoPrint-lewis-yes 
As a reminder, here is a link to the Feb 22 announcement commencing Formal 
Approval. 
http://www.pwg.org/hypermail/pwg-announce/1500.html
YOUR VOTE IS NEEDED!!
Regards,
Harry


Harry Lewis
Program Manager - Intellectual Property & Standards
Phone: 303-924-5337
e-mail: harryl@us.ibm.com
infoprint.com

--=_alternative 0069F29C87257404_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3 face="Arial">There remains a little over <b>1 week</b>
until voting closes on Formal Approval for the PWG Imaging State and Counter
MIBv2. </font>
<br>
<br><font size=3 face="Arial">To cast a vote, please send an email with
the following subject line format: </font>
<p><font size=3 face="Arial">&quot;Counter MIB v2 Formal Vote-&lt;company
name&gt;-&lt;last name of voter&gt;-&lt;yes/no/abstain&gt;&quot; </font>
<p><font size=3 face="Arial"><b>Example: Counter MIB v2 Formal Vote-InfoPrint-lewis-yes
</b></font>
<p><font size=2 face="sans-serif">As a reminder, here is a link to the
Feb 22 announcement commencing Formal Approval. </font>
<br><a href="http://www.pwg.org/hypermail/pwg-announce/1500.html"><font size=2 color=blue face="sans-serif">http://www.pwg.org/hypermail/pwg-announce/1500.html</font></a>
<p><font size=2 face="sans-serif">YOUR VOTE IS NEEDED!!</font>
<p><font size=2 face="sans-serif">Regards,</font>
<p><font size=2 face="sans-serif">Harry<br>
</font>
<table border>
<tr>
<td bgcolor=white>
<div align=center><img src=cid:_1_0746FFC00746FBD80069F29C87257404></div>
<td bgcolor=#efefef><font size=1 face="Arial"><b>Harry Lewis</b></font><font size=1 color=#808080 face="Arial"><br>
Program Manager - Intellectual Property &amp; Standards<br>
Phone: 303-924-5337<br>
e-mail: harryl@us.ibm.com</font><font size=1 color=blue face="Arial"><br>
</font><a href=http://www.infoprint.com/><font size=1 color=blue face="Arial">infoprint.com</font></a></table>
<br>
--=_alternative 0069F29C87257404_=--
--=_related 0069F29C87257404_=
Content-Type: image/gif
Content-ID: <_1_0746FFC00746FBD80069F29C87257404>
Content-Transfer-Encoding: base64

R0lGODlhWgAaALMAAPnJypu06PFvdGOK3MHQ8PWrrfOJjO9JT7m5ufbn5XGT3lR+2OwcJAAAAP//
/wAAACH5BAAAAAAALAAAAABaABoAAAT/0MlJq704a9m210AoAl8iJpUZot/VVYFCOLFi27NUB9PO
/EBgQSL4HSaGQ5BxICWUwcNQAiRRf5YXRbGYBRbgcFfCXSgmZQXwYDAUf6T30fFmCO6HYwF4rwuu
DFYOQFkWXF4LPDpmZAsDCxOOZoQTbwZ0Rg57cCwsQAYoCZuBg3ATlBRaaGNfig4EjA5ch69mk1gO
olWYTA5QlxWjLLm/CWt5UAyFFbRfCgHQjzlcrTSJtwwGS8Byvj/AFKMV3UtLy1usYmHTXYwKA7Bq
WNpMgt1QfxUAQMPe2aXZCghENUFVI0QyCBD4AklWFy4OzMSjRI/BlG4Vp0hI8ORHPk27+3YBOrcK
kSuHMw61SjQRl4OMvI4kqMNGgBJdRtwIySUSIMmD1lwlkIYyXpeWyjZWBNAtV4FkHgGYqGNEY0+C
HAylG3ADzBmUEcHU+tqCAscV/Tiq6Fc2K7N06sjSmjW2rd27P/Hq3cvXbd+/gAMLHky4sOHDiBMr
Xsy4sEEEqhpIRpCqghbIBjP71YA5cIfJDjpApvzis+jQDRB0Dj1hNOvPnSm7Bg3Z7+zUqVFTDk06
t+nXvD+j9p1V+GXixoEDT66l+fLnpJ9Llq7cLXPL1IVnt15we+nko6/Prgz9u2zirmuLRs5bQmz2
pkmrZx06R2PFBl3cZ5wfu4MIADs=
--=_related 0069F29C87257404_=--


From ipp-owner@pwg.org  Mon Mar 10 08:54:03 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B364328C324
	for <ietfarch-ipp-archive@core3.amsl.com>; Mon, 10 Mar 2008 08:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id vX1xNdAqDmyw for <ietfarch-ipp-archive@core3.amsl.com>;
	Mon, 10 Mar 2008 08:53:58 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 7A21A28C85D
	for <ipp-archive@ietf.org>; Mon, 10 Mar 2008 08:32:05 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2AFTgCf006130
	for <ipp-archive@ietf.org>; Mon, 10 Mar 2008 11:29:44 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2AFTgOF006127
	for <ipp-archive@lists.ietf.org>; Mon, 10 Mar 2008 11:29:42 -0400
Received: by pwg.org (bulk_mailer v1.13); Mon, 10 Mar 2008 11:28:35 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2AFSPZT005838
	for <ipp-outgoing@pwg.org>; Mon, 10 Mar 2008 11:28:27 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2AFSP0O005835
	for ipp-outgoing; Mon, 10 Mar 2008 11:28:25 -0400
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179])
	by pwg.org  with ESMTP id m2AFSMKo005827
	for <ipp@pwg.org>; Mon, 10 Mar 2008 11:28:25 -0400
Received: by wa-out-1112.google.com with SMTP id j37so1899230waf.7
        for <ipp@pwg.org>; Mon, 10 Mar 2008 08:28:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=7r2TFq8BqsPNkl3ot9ulVET1FHtTQUuPiQAWltjDcFc=;
        b=i2GizTBgNKH0AfgwwpkuAGi5DvF28lODVtoVNJEjB1KBngERM8NYaUKyoTKb7i4XQK0MwQ9KNvFnRfDWxXEbazNfigDoUW1yr3YcOl1yCQuWFODrHDJlOoJC2g8zTmQbsx83Jj+uKPJC5nCkpe9ruVsSHBzYbuG+iacjCc4s4oM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Ee5Yk+vb0A1Whm/meB32smPZVx8UlfuE7s+i2VC1d3alHPsc/bcBeOBoUZ+6wyUPW48z6V3PcLNVHrQCaNzkEcxG6UfShwTax7BXjsPFLOBdofNXeM4m2+gldqHjAuZmsgSxJKSdreqIuMmjSqcdUMEHEtf8uh3Gpxk7FhY6fG8=
Received: by 10.114.174.2 with SMTP id w2mr5853763wae.17.1205162902108;
        Mon, 10 Mar 2008 08:28:22 -0700 (PDT)
Received: by 10.115.17.1 with HTTP; Mon, 10 Mar 2008 08:28:22 -0700 (PDT)
Message-ID: <e395be80803100828sd332ffevc3d907e62481dd0b@mail.gmail.com>
Date: Mon, 10 Mar 2008 11:28:22 -0400
From: "Ira McDonald" <blueroofmusic@gmail.com>
To: "Norm Jacobs" <Norm.Jacobs@sun.com>, ipp@pwg.org,
        "Ira McDonald" <blueroofmusic@gmail.com>
Subject: IPP> IPP operations implemented in mod_ipp on Solaris
In-Reply-To: <47D4E498.7060408@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <47D4E498.7060408@Sun.COM>
Sender: owner-ipp@pwg.org

Hi,

Thanks to Norm Jacobs (Sun Open Solaris Printing Team) for the following list
of operations supported by the Open Solaris IPP Server.

Cheers,
- Ira


On Mon, Mar 10, 2008 at 3:34 AM, Norm Jacobs <Norm.Jacobs@sun.com> wrote:
> Buried somewhere in the docs is the list of IPP operations implemented
>  on Solaris under the mod_ipp Apache module.  I expect that if you tried
>  to search docs.sun.com, you might find it.  That being said, the
>  implementation
>  of the IPP server side support is available in source from
>  src.opensolaris.org.  In ipp-listener.c, there is a dispatch table that
>  maps IPP operations, name, function, and "grouping". a function pointer
>  of NULL means not implemented.
>  http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/print/libipp-listener/common/ipp-listener.c#103
>
>  The contents are as follows:
>
>         /* Printer Operations */
>         { 0x0002, "print-job",                  ipp_print_job,  OP_REQUIRED },
>         { 0x0003, "print-uri",                  NULL,           OP_OPTIONAL },
>         { 0x0004, "validate-job",               ipp_validate_job,
>                                                                 OP_REQUIRED },
>         { 0x0005, "create-job",                 ipp_create_job, OP_OPTIONAL },
>         { 0x000a, "get-jobs",                   ipp_get_jobs,   OP_REQUIRED },
>         { 0x000b, "get-printer-attributes",     ipp_get_printer_attributes,
>                                                                 OP_REQUIRED },
>         { 0x0010, "pause-printer",              ipp_pause_printer,
>                                                                 OP_OPTIONAL },
>         { 0x0011, "resume-printer",             ipp_resume_printer,
>                                                                 OP_OPTIONAL },
>         { 0x0012, "purge-jobs",                 ipp_purge_jobs, OP_OPTIONAL },
>         { 0x0013, "set-printer-attributes",     ipp_set_printer_attributes,
>                                                                 OP_OPTIONAL },
>         { 0x0014, "set-job-attributes",         ipp_set_job_attributes,
>                                                                 OP_OPTIONAL },
>         { 0x0022, "enable-printer",             ipp_enable_printer,
>                                                                 OP_OPTIONAL },
>         { 0x0023, "disable-printer",            ipp_disable_printer,
>                                                                 OP_OPTIONAL },
>         /* Job Operations */
>         { 0x0006, "send-document",              ipp_send_document,
>                                                                 OP_OPTIONAL },
>         { 0x0007, "send-uri",                   NULL,           OP_OPTIONAL },
>         { 0x0008, "cancel-job",                 ipp_cancel_job, OP_REQUIRED },
>         { 0x0009, "get-job-attributes",         ipp_get_job_attributes,
>                                                                 OP_REQUIRED },
>         { 0x000c, "hold-job",                   ipp_hold_job,   OP_OPTIONAL },
>         { 0x000d, "release-job",                ipp_release_job,
>                                                                 OP_OPTIONAL },
>         { 0x000e, "restart-job",                ipp_restart_job,
>                                                                 OP_OPTIONAL },
>         /* Other Operations */
>         { 0x4001, "cups-get-default",           cups_get_default,
>                                                                 OP_VENDOR },
>         { 0x4002, "cups-get-printers",          cups_get_printers,
>                                                                 OP_VENDOR },
>         { 0x4005, "cups-get-classes",           cups_get_classes,
>                                                                 OP_VENDOR },
>         { 0x4008, "cups-accept-jobs",           cups_accept_jobs,
>                                                                 OP_VENDOR },
>         { 0x4009, "cups-reject-jobs",           cups_reject_jobs,
>                                                                 OP_VENDOR },
>         { 0x400D, "cups-move-job",              cups_move_job,  OP_VENDOR },
>         { 0, NULL, NULL, OP_VENDOR }
>
>
>



-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
  579 Park Place  Saline, MI  48176
  734-944-0094
summer:
  PO Box 221  Grand Marais, MI 49839
  906-494-2434


From ipp-owner@pwg.org  Mon Mar 10 09:51:32 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DDC83A6E94
	for <ietfarch-ipp-archive@core3.amsl.com>; Mon, 10 Mar 2008 09:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id xEJzgwi98a6c for <ietfarch-ipp-archive@core3.amsl.com>;
	Mon, 10 Mar 2008 09:51:31 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id B6B0B3A6F50
	for <ipp-archive@ietf.org>; Mon, 10 Mar 2008 09:38:08 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2AGZj12017087
	for <ipp-archive@ietf.org>; Mon, 10 Mar 2008 12:35:47 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2AGZjIs017084
	for <ipp-archive@lists.ietf.org>; Mon, 10 Mar 2008 12:35:45 -0400
Received: by pwg.org (bulk_mailer v1.13); Mon, 10 Mar 2008 12:34:47 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2AGYhhB016766
	for <ipp-outgoing@pwg.org>; Mon, 10 Mar 2008 12:34:45 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2AGYhsX016763
	for ipp-outgoing; Mon, 10 Mar 2008 12:34:43 -0400
Received: from njwcntas37.us.ricoh.ds (host150.ricoh-usa.com [208.252.21.150])
	by pwg.org  with ESMTP id m2AGYemX016750
	for <IPP@pwg.org>; Mon, 10 Mar 2008 12:34:42 -0400
X-SEF-Processed: 5_0_0_816__2008_03_10_12_34_40
Received: from Unknown [172.16.19.238] by njwcntas37.us.ricoh.ds - SurfControl E-mail Filter ; Mon, 10 Mar 2008 12:34:40 -0400
Subject: IPP> IPPV2 Conference Call Minutes 20080306
To: IPP@pwg.org
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OFBF04DD25.1D971CCE-ON88257408.005A78C7-88257408.005B0E82@ricoh-usa.com>
From: Ron.Bergman@ricoh-usa.com
Date: Mon, 10 Mar 2008 09:34:34 -0700
X-MIMETrack: Serialize by Router on NJWC02/RCUS(Release 7.0.2FP1|January 10, 2007) at 03/10/2008
 12:34:40 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-ipp@pwg.org


The minutes can be found at:

ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-minutes/IPPv2-ConCall-Minutes-20080306.pdf
    (.doc)




From ipp-owner@pwg.org  Mon Mar 10 10:08:42 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0BD3C3A6EC7
	for <ietfarch-ipp-archive@core3.amsl.com>; Mon, 10 Mar 2008 10:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 9jWsxHiGqZFW for <ietfarch-ipp-archive@core3.amsl.com>;
	Mon, 10 Mar 2008 10:08:40 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id E87AF28C4BE
	for <ipp-archive@ietf.org>; Mon, 10 Mar 2008 10:02:50 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2AH0SKZ023514
	for <ipp-archive@ietf.org>; Mon, 10 Mar 2008 13:00:30 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2AH0Sjf023511
	for <ipp-archive@lists.ietf.org>; Mon, 10 Mar 2008 13:00:28 -0400
Received: by pwg.org (bulk_mailer v1.13); Mon, 10 Mar 2008 12:59:31 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2AGxRl0023191
	for <ipp-outgoing@pwg.org>; Mon, 10 Mar 2008 12:59:29 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2AGxRuH023188
	for ipp-outgoing; Mon, 10 Mar 2008 12:59:27 -0400
Received: from lucius.provo.novell.com (lucius.provo.novell.com [137.65.248.127])
	by pwg.org  with ESMTP id m2AGxKxb023173
	for <IPP@pwg.org>; Mon, 10 Mar 2008 12:59:26 -0400
Received: from INET-PRV1-MTA by lucius.provo.novell.com
	with Novell_GroupWise; Mon, 10 Mar 2008 10:59:20 -0600
Message-Id: <47D514FD.196D.00A2.0@novell.com>
X-Mailer: Novell GroupWise Internet Agent 7.0.3 
Date: Mon, 10 Mar 2008 10:59:03 -0600
From: "Ted Tronson" <TTRONSON@novell.com>
To: <IPP@pwg.org>, <Ron.Bergman@ricoh-usa.com>
Subject: Re: IPP> IPPV2 Conference Call Minutes 20080306
References: 
 <OFBF04DD25.1D971CCE-ON88257408.005A78C7-88257408.005B0E82@ricoh-usa.com>
In-Reply-To: <OFBF04DD25.1D971CCE-ON88257408.005A78C7-88257408.005B0E82@ricoh-usa.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__Part5573CAC7.0__="
Sender: owner-ipp@pwg.org

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=__Part5573CAC7.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Sorry, I could not make the meeting again.  Here is the list of supported =
operations in Novell iPrint:
=20
0x0002 print-job
0x0008 cancel-job
0x0009 get-job-attributes
0x000A get-jobs
0x000B get-printer-attributes
0x000C hold-job
0x000D release-job
0x000E restart-job
0x0010 pause-printer
0x0011 resume-printer
0x0012 purge-jobs
=20
0x0021 get-client-print-support-files   (driver download spec from Ted and =
Hugo)
=20
Novell operations
0x401A novell-list-printers
0x401B novell-list-drivers
0x401C novell-mgmt-interface
0x401D novell-resource-add
0x401E novell-resource-list
0x401F novell-resource-delete
0x4020 novell-resource-download
0x4021 novell-get-driver-profile (similar to 0x0021 spec for downloading =
driver)
0x4022
0x4023
0x4024
0x4025
=20
For job notifications we poll the server (doing a get-job-attributes)
=20
=20
Ted Tronson
Sr. Software Engineer
iPrint Engineering
ttronson@novell.com=20
801-861-333


>>> <Ron.Bergman@ricoh-usa.com> 3/10/2008 10:34 AM >>>

The minutes can be found at:

ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-minutes/IPPv2-ConCall-Minutes-20080306.=
pdf=20
    (.doc)



--=__Part5573CAC7.0__=
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-15=
">
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px">
<DIV>Sorry, I could not make the meeting again.&nbsp; Here is the list of =
supported operations in Novell iPrint:</DIV>
<DIV>&nbsp;</DIV>
<DIV>0x0002 print-job</DIV>
<DIV>
<DIV>0x0008 cancel-job</DIV>
<DIV>0x0009 get-job-attributes</DIV>0x000A get-jobs</DIV>
<DIV>0x000B get-printer-attributes</DIV>
<DIV>
<DIV>0x000C hold-job</DIV>
<DIV>0x000D release-job</DIV>
<DIV>0x000E restart-job</DIV>0x0010 pause-printer</DIV>
<DIV>0x0011 resume-printer</DIV>
<DIV>0x0012 purge-jobs</DIV>
<DIV>&nbsp;</DIV>
<DIV>0x0021 get-client-print-support-files&nbsp;&nbsp; (driver download =
spec from Ted and Hugo)</DIV>
<DIV>&nbsp;</DIV>
<DIV><STRONG>Novell operations</STRONG></DIV>
<DIV>0x401A novell-list-printers</DIV>
<DIV>0x401B novell-list-drivers</DIV>
<DIV>0x401C novell-mgmt-interface</DIV>
<DIV>0x401D novell-resource-add</DIV>
<DIV>0x401E novell-resource-list</DIV>
<DIV>0x401F novell-resource-delete</DIV>
<DIV>0x4020 novell-resource-download</DIV>
<DIV>0x4021 novell-get-driver-profile (similar to 0x0021 spec for =
downloading driver)</DIV>
<DIV>0x4022</DIV>
<DIV>0x4023</DIV>
<DIV>0x4024</DIV>
<DIV>0x4025</DIV>
<DIV>&nbsp;</DIV>
<DIV>For job notifications we poll the server (doing a get-job-attributes)<=
/DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV>Ted Tronson<BR>Sr. Software Engineer<BR>iPrint Engineering<BR>ttronson=
@novell.com<BR>801-861-333</DIV><BR><BR>&gt;&gt;&gt; &lt;Ron.Bergman@ricoh-=
usa.com&gt; 3/10/2008 10:34 AM &gt;&gt;&gt;<BR><BR>The minutes can be =
found at:<BR><BR><A href=3D"ftp://ftp.pwg.org/pub/pwg/ipp/ippv2">ftp://ftp.=
pwg.org/pub/pwg/ipp/ippv2</A>-minutes/IPPv2-ConCall-Minutes-20080306.pdf<BR=
>&nbsp;&nbsp;&nbsp; (.doc)<BR><BR><BR></DIV></BODY></HTML>

--=__Part5573CAC7.0__=--


From pwg-announce-owner@pwg.org  Mon Mar 17 09:24:38 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07C503A6C1A;
	Mon, 17 Mar 2008 09:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id kJvS7G1JPsgX; Mon, 17 Mar 2008 09:24:37 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id BB3433A6B9C;
	Mon, 17 Mar 2008 09:24:36 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2HGAl9T001946;
	Mon, 17 Mar 2008 12:22:17 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2HEj6ii017128;
	Mon, 17 Mar 2008 10:45:06 -0400
Received: by pwg.org (bulk_mailer v1.13); Mon, 17 Mar 2008 10:44:04 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2HEhx01016622
	for <pwg-announce-out@pwg.org>; Mon, 17 Mar 2008 10:44:01 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2HEhxld016619
	for pwg-announce-out; Mon, 17 Mar 2008 10:43:59 -0400
X-Authority-Analysis: v=1.0 c=1 a=xDDF3Kts6TQA:10
 a=RDVkIgxKtvS5Q3Z4H+f/1A==:17 a=51RRrcYvAAAA:8 a=AhZ9i0hGuAcsokX4H10A:9
 a=eVEoDFloSo7rchkJCkQA:7 a=-LkudkACs0prv-EXrS6WrBwjHYoA:4 a=3I_whO4B8K8A:10
 a=lfS3Pc3lgfTdtaoXdtEA:9 a=A7b0rqfY2rnP-BoiKVkA:7
 a=rX3fhWN3A3J95UN4vNwfNkMXfQUA:4 a=37WNUvjkh6kA:10
From: wamwagner@comcast.net
To: pwg-announce@pwg.org (PWG announce)
Subject: PWG-ANNOUNCE> PLEASE VOTE - PWG Imaging State and Counter MIB v2
Date: Mon, 17 Mar 2008 14:43:49 +0000
Message-Id: <031720081443.11864.47DE83A5000775D800002E5822070215739D0A02090E99030E99@comcast.net>
X-Mailer: AT&T Message Center Version 1 (Oct 30 2007)
X-Authenticated-Sender: d2Ftd2FnbmVyQGNvbWNhc3QubmV0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_11864_1205765029_0"
Sender: owner-pwg-announce@pwg.org


--NextPart_Webmail_9m3u9jl4l_11864_1205765029_0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

Just a reminder for those company representatives that have not yet cast their ballot.  Voting on the Imaging State and Counter MIB V2 for Candidate standard level (the highest level of any current PWG standard) nominally ends  tomorrow. Note that this MIB both advances the Counter MIB, based on the prototyping effort by Samsung, and includes state reporting elements deemed  desirable, particularly for MFDs.

It is important that PWG standards reflect the intent of the majority of the membership. So please  vote,  regardless of whether your preference is yes, no or abstain.

To cast a vote, please send an email with the following subject line format: 
"Counter MIB v2 Formal Vote-<company name>-<last name of voter>-<yes/no/abstain>" 
Example: Counter MIB v2 Formal Vote-InfoPrint-lewis-yes 
As a reminder, here is a link to the Feb 22 announcement commencing Formal Approval. 
http://www.pwg.org/hypermail/pwg-announce/1500.html 
Many thanks,

Bill Wagner, CoChairman PWG WIMS WG.
--NextPart_Webmail_9m3u9jl4l_11864_1205765029_0
Content-Type: text/html
Content-Transfer-Encoding: 8bit

<html><body>
<DIV><FONT face=Arial>Just a reminder for those&nbsp;company representatives that&nbsp;have not yet cast their ballot.&nbsp; Voting on the Imaging State and Counter MIB V2 for Candidate standard level&nbsp;(the highest level of any current PWG standard) nominally ends&nbsp; tomorrow. Note that this MIB both advances the Counter MIB, based on the prototyping effort by Samsung, and includes state reporting elements deemed&nbsp; desirable,&nbsp;particularly for MFDs.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>It is important that PWG standards reflect the intent of the majority of the membership. So please&nbsp; vote,&nbsp; regardless of whether&nbsp;your preference is yes, no or abstain.</FONT></DIV>
<DIV><FONT face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial>To cast a vote, please send an email with the following subject line format: </FONT></DIV>
<P><FONT face=Arial size=3>"Counter MIB v2 Formal Vote-&lt;company name&gt;-&lt;last name of voter&gt;-&lt;yes/no/abstain&gt;" </FONT>
<P><FONT face=Arial size=3><B>Example: Counter MIB v2 Formal Vote-InfoPrint-lewis-yes </B></FONT>
<P><FONT face=sans-serif size=2>As a reminder, here is a link to the Feb 22 announcement commencing Formal Approval. </FONT><BR><A href="http://www.pwg.org/hypermail/pwg-announce/1500.html"><FONT face=sans-serif color=blue size=2>http://www.pwg.org/hypermail/pwg-announce/1500.html</FONT></A> </P>
<DIV><FONT face="Arial, Helvetica, sans-serif">Many thanks,</FONT></DIV>
<DIV><FONT face="Arial, Helvetica, sans-serif"></FONT>&nbsp;</DIV>
<DIV><FONT face="Arial, Helvetica, sans-serif">Bill Wagner, CoChairman PWG WIMS WG.</FONT></DIV></body></html>

--NextPart_Webmail_9m3u9jl4l_11864_1205765029_0--


From pwg-announce-owner@pwg.org  Mon Mar 17 11:19:23 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C8C63A6E5B;
	Mon, 17 Mar 2008 11:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
	tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OMBRMmiiZ-0g; Mon, 17 Mar 2008 11:19:22 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 947AC3A6DB0;
	Mon, 17 Mar 2008 11:19:22 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2HIAlbO024063;
	Mon, 17 Mar 2008 14:17:05 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2HHveSO021669;
	Mon, 17 Mar 2008 13:57:40 -0400
Received: by pwg.org (bulk_mailer v1.13); Mon, 17 Mar 2008 13:56:09 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2HHu6Rg021127
	for <pwg-announce-out@pwg.org>; Mon, 17 Mar 2008 13:56:08 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2HHu67Y021124
	for pwg-announce-out; Mon, 17 Mar 2008 13:56:06 -0400
Subject: PWG-ANNOUNCE> URGENT!!!!!  April 16-18, 2008 Face to Face meeting reminder 
To: pwg-announce@pwg.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OFAB5CFB8B.C264DC52-ON8525740F.0061D5BD-8525740F.00622FFF@lexmark.com>
From: thrasher@lexmark.com
Date: Mon, 17 Mar 2008 13:52:28 -0400
X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark(Release 6.5.5|November 30, 2005) at
 03/17/2008 13:53:45
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-pwg-announce@pwg.org

Thanks to those (few) who've already made hotel reservations and registered
with the ISTO
for the upcoming PWG F2F meeting,

However, we still have not come close to receiving reservations from even
half
of the "normal" PWG F2F meeting attendees.  The PWG will be subject to a
rather
large financial penalty from the hotel attendance stays at the current
level.

Please make your hotel and meeting reservations this week.

Jerry Thrasher
PWG Chair.
----- Forwarded by Jerry Thrasher/Lex/Lexmark on 03/03/2008 09:58 AM -----
                                                                           
             Jerry                                                         
             Thrasher/Lex/Lexm                                             
             ark                                                        To 
                                       pwg-announce@pwg.org                
             02/19/2008 10:08                                           cc 
             AM                                                            
                                                                   Subject 
                                       April 16-18, 2008 Face to Face      
                                       meeting reminder                    
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           



Reminder that the April 16-18, F2F meeting (IEEE P2600 meetings on April
14-15) is being held
at a hotel venue and not hosted by a PWG member company. Hence those
attending need
to deal with registration pages, hotel block cut-off dates etc.

The detailed agenda for this meeting will posted soon, but for those
members that plan to attend
the entire session, I encourage you to go ahead and make your hotel
arrangements, registration
etc. ASAP.  The cut-off date for the PWG/P2600 hotel block is March 21.

The following link has details on the registration, and a link to the hotel
reservation page specifically
set up for the PWG:

http://www.pwg.org/chair/meeting-info/April_2008_Phoenix.html

Jerry Thrasher
Senior Engineer, WW Corporate Standards
Lexmark International Inc.
Ph:859-825-4056, Fax:859-232-7628
Email:thrasher(at)lexmark(dot)com



From pwg-announce-owner@pwg.org  Tue Mar 18 10:12:41 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3B5323A683E;
	Tue, 18 Mar 2008 10:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id bDRY7scAJOyJ; Tue, 18 Mar 2008 10:12:37 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 6D3B33A69B2;
	Tue, 18 Mar 2008 10:12:37 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2IHAH00010791;
	Tue, 18 Mar 2008 13:10:19 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2IHAHDZ010788;
	Tue, 18 Mar 2008 13:10:17 -0400
Received: by pwg.org (bulk_mailer v1.13); Tue, 18 Mar 2008 13:08:25 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2IH8KK5010256
	for <pwg-announce-out@pwg.org>; Tue, 18 Mar 2008 13:08:22 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2IH8Kd7010253
	for pwg-announce-out; Tue, 18 Mar 2008 13:08:20 -0400
Message-ID: <2F7D63A21DB2C74EB8EB8C09AF667DB0152D335C@eitc220.eitc.epson.com>
From: "Petrie, Glen" <glen.petrie@eitc.epson.com>
To: pwg-announce@pwg.org
Subject: PWG-ANNOUNCE> Will there be dial/call  in for the April F2F Meeting?
Date: Tue, 18 Mar 2008 10:08:06 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8891A.A2696FE8"
Sender: owner-pwg-announce@pwg.org

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C8891A.A2696FE8
Content-Type: text/plain

Will there be dial/call  in for the April F2F Meeting at Mesa Az?


------_=_NextPart_001_01C8891A.A2696FE8
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Will there be dial/call&nbsp; in for the April F2F =
Meeting at <st1:place
w:st=3D"on"><st1:City w:st=3D"on">Mesa</st1:City> <st1:State =
w:st=3D"on">Az</st1:State></st1:place>?<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C8891A.A2696FE8--


From pwg-announce-owner@pwg.org  Tue Mar 18 14:01:46 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F29628C5EC;
	Tue, 18 Mar 2008 14:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rX4yT4xTi0vm; Tue, 18 Mar 2008 14:01:43 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id BD38B28C5A1;
	Tue, 18 Mar 2008 14:01:34 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2IKxFfd016676;
	Tue, 18 Mar 2008 16:59:17 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2IKxF2f016673;
	Tue, 18 Mar 2008 16:59:15 -0400
Received: by pwg.org (bulk_mailer v1.13); Tue, 18 Mar 2008 16:57:21 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2IKvJqp016110
	for <pwg-announce-out@pwg.org>; Tue, 18 Mar 2008 16:57:21 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2IKvJIm016107
	for pwg-announce-out; Tue, 18 Mar 2008 16:57:19 -0400
Subject: PWG-ANNOUNCE> April 14,15 P2600 meetings with the PWG, April 16-18, 2008 (hotel link
 problem)
To: stds-2600@ieee.org, pwg-announce@pwg.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OFF60D58E2.52DDC412-ON85257410.0072068E-85257410.00723752@lexmark.com>
From: thrasher@lexmark.com
Date: Tue, 18 Mar 2008 16:47:32 -0400
X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark(Release 6.5.5|November 30, 2005) at
 03/18/2008 16:55:07
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-pwg-announce@pwg.org

FYI,

There appears to be a problem with the web reservation system at the hotel
for the April F2F meetings.
The hotel is working on this but until this is fixed......

The web link for the hotel contains both direct and toll free telephone
numbers that you can use.
http://cwp.marriott.com/phxme/ieeeisto/

Ask for the ISTO, or IEEE, or PWG group rate.

Jerry Thrasher
Senior Engineer, WW Corporate Standards
Lexmark International Inc.
Ph:859-825-4056, Fax:859-232-7628
Email:thrasher(at)lexmark(dot)com



From ipp-owner@pwg.org  Tue Mar 18 17:32:26 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0EB913A63EC
	for <ietfarch-ipp-archive@core3.amsl.com>; Tue, 18 Mar 2008 17:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id DeBF1VmG1-H5 for <ietfarch-ipp-archive@core3.amsl.com>;
	Tue, 18 Mar 2008 17:32:25 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 3BDA03A6951
	for <ipp-archive@ietf.org>; Tue, 18 Mar 2008 17:32:25 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2J0U5oi018956
	for <ipp-archive@ietf.org>; Tue, 18 Mar 2008 20:30:07 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2J0U5jY018953
	for <ipp-archive@lists.ietf.org>; Tue, 18 Mar 2008 20:30:05 -0400
Received: by pwg.org (bulk_mailer v1.13); Tue, 18 Mar 2008 20:29:04 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2J0St7F018672
	for <ipp-outgoing@pwg.org>; Tue, 18 Mar 2008 20:28:57 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2J0StYP018669
	for ipp-outgoing; Tue, 18 Mar 2008 20:28:55 -0400
Received: from njwcntas37.us.ricoh.ds (host150.ricoh-usa.com [208.252.21.150])
	by pwg.org  with ESMTP id m2J0SrdN018663
	for <IPP@PWG.ORG>; Tue, 18 Mar 2008 20:28:55 -0400
X-SEF-Processed: 5_0_0_816__2008_03_18_20_13_20
Received: from Unknown [172.16.19.238] by njwcntas37.us.ricoh.ds - SurfControl E-mail Filter ; Tue, 18 Mar 2008 20:11:42 -0400
Subject: IPP> Reminder, Next IPPv2 Teleconference on Thurs (March 20) at 11:00 AM EDT
To: IPP@pwg.org
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF6C72C727.AA90CE5B-ON88257410.00837B54-88257411.00011052@ricoh-usa.com>
From: Ron.Bergman@ricoh-usa.com
Date: Tue, 18 Mar 2008 17:11:37 -0700
X-MIMETrack: Serialize by Router on NJWC02/RCUS(Release 7.0.2FP1|January 10, 2007) at 03/18/2008
 08:11:42 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-ipp@pwg.org


IPPv2 WG Conference Call:

Thursday, March 20, 2008, 11:00 AM EDT  (8:00 AM PDT)

Toll Free:     1-866-365-4406
International: 00+1+303-248-9655
Passcode:      2635888#

Agenda:

1. Identify Minute Taker
2. Approval of minutes from 3/6 Conference Call
3. Review of Action Items
   Ira - Obtain a list of the IPP operations supported by Open Solaris -
Completed
   Ron - Generate a spread sheet similar to the one used in the WIMS/CIM
work, to
         collect inputs from the group as to which operations should be
made required.
5. Glen Petrie's Summary Of IPP Operations Supported document.
6. Next steps




From pwg-announce-owner@pwg.org  Wed Mar 19 09:25:54 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D737428C1D4;
	Wed, 19 Mar 2008 09:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id tgbDpc-1Y6+Z; Wed, 19 Mar 2008 09:25:54 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 0E4003A6D11;
	Wed, 19 Mar 2008 09:25:49 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2JGNTa5000808;
	Wed, 19 Mar 2008 12:23:31 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2JGNTRI000805;
	Wed, 19 Mar 2008 12:23:29 -0400
Received: by pwg.org (bulk_mailer v1.13); Wed, 19 Mar 2008 12:21:38 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2JGLXt4032658
	for <pwg-announce-out@pwg.org>; Wed, 19 Mar 2008 12:21:35 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2JGLXTq032655
	for pwg-announce-out; Wed, 19 Mar 2008 12:21:33 -0400
Subject: PWG-ANNOUNCE> Fw: April 14,15 P2600 meetings with the PWG, April 16-18, 2008 (hotel link
 problem)
To: stds-2600@ieee.org, pwg-announce@pwg.org
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
Message-ID: <OF0B63E72D.E5C4008C-ON85257411.0059C0EF-85257411.0059B7FB@lexmark.com>
From: thrasher@lexmark.com
Date: Wed, 19 Mar 2008 12:19:58 -0400
X-MIMETrack: Serialize by Router on smtp5b/Lex/Lexmark(Release 6.5.5|November 30, 2005) at
 03/19/2008 12:21:14
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-pwg-announce@pwg.org

The problem with the registration link, (and the group code for call-ins)
should now be fixed.


Jerry Thrasher
Senior Engineer, WW Corporate Standards
Lexmark International Inc.
Ph:859-825-4056, Fax:859-232-7628
Email:thrasher(at)lexmark(dot)com
----- Forwarded by Jerry Thrasher/Lex/Lexmark on 03/19/2008 12:19 PM -----
                                                                           
             Jerry                                                         
             Thrasher/Lex/Lexm                                             
             ark                                                        To 
                                       stds-2600@ieee.org,                 
             03/18/2008 04:47          pwg-announce@pwg.org                
             PM                                                         cc 
                                                                           
                                                                   Subject 
                                       April 14,15 P2600 meetings with the 
                                       PWG, April 16-18, 2008 (hotel link  
                                       problem)                            
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           



FYI,

There appears to be a problem with the web reservation system at the hotel
for the April F2F meetings.
The hotel is working on this but until this is fixed......

The web link for the hotel contains both direct and toll free telephone
numbers that you can use.
http://cwp.marriott.com/phxme/ieeeisto/

Ask for the ISTO, or IEEE, or PWG group rate.

Jerry Thrasher
Senior Engineer, WW Corporate Standards
Lexmark International Inc.
Ph:859-825-4056, Fax:859-232-7628
Email:thrasher(at)lexmark(dot)com



From ipp-owner@pwg.org  Thu Mar 20 07:30:10 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4C343A6B0B
	for <ietfarch-ipp-archive@core3.amsl.com>; Thu, 20 Mar 2008 07:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QAP-7JTQLiHG for <ietfarch-ipp-archive@core3.amsl.com>;
	Thu, 20 Mar 2008 07:30:08 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 4DE0C3A6CD0
	for <ipp-archive@ietf.org>; Thu, 20 Mar 2008 07:30:07 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2KERjsT011305
	for <ipp-archive@ietf.org>; Thu, 20 Mar 2008 10:27:47 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2KERiqV011302
	for <ipp-archive@lists.ietf.org>; Thu, 20 Mar 2008 10:27:45 -0400
Received: by pwg.org (bulk_mailer v1.13); Thu, 20 Mar 2008 10:26:37 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2KEQRMT010929
	for <ipp-outgoing@pwg.org>; Thu, 20 Mar 2008 10:26:29 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2KEQRUJ010926
	for ipp-outgoing; Thu, 20 Mar 2008 10:26:27 -0400
Received: from eitc220.eitc.epson.com (eitcmail.eitc.epson.com [12.104.142.220] (may be forged))
	by pwg.org  with ESMTP id m2KEQPjM010912
	for <IPP@pwg.org>; Thu, 20 Mar 2008 10:26:27 -0400
Received: by eitc220.eitc.epson.com with Internet Mail Service (5.5.2653.19)
	id <G0MCPKVG>; Thu, 20 Mar 2008 07:26:24 -0700
Message-ID: <2F7D63A21DB2C74EB8EB8C09AF667DB0152D33BC@eitc220.eitc.epson.com>
From: "Petrie, Glen" <glen.petrie@eitc.epson.com>
To: IPP@pwg.org
Subject: RE: IPP> Reminder, Next IPPv2 Teleconference on Thurs (March 20) 
	at  11:00 AM EDT
Date: Thu, 20 Mar 2008 07:26:24 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ipp@pwg.org

Please see the following document in reference to Item 5.0 below

 
ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-info/IPP-Operations-Supported-By-Solutio
ns.pdf (doc)

glen


> -----Original Message-----
> From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
> Ron.Bergman@ricoh-usa.com
> Sent: Tuesday, March 18, 2008 5:12 PM
> To: IPP@pwg.org
> Subject: IPP> Reminder, Next IPPv2 Teleconference on Thurs (March 20) at
> 11:00 AM EDT
> 
> 
> IPPv2 WG Conference Call:
> 
> Thursday, March 20, 2008, 11:00 AM EDT  (8:00 AM PDT)
> 
> Toll Free:     1-866-365-4406
> International: 00+1+303-248-9655
> Passcode:      2635888#
> 
> Agenda:
> 
> 1. Identify Minute Taker
> 2. Approval of minutes from 3/6 Conference Call
> 3. Review of Action Items
>    Ira - Obtain a list of the IPP operations supported by Open Solaris -
> Completed
>    Ron - Generate a spread sheet similar to the one used in the WIMS/CIM
> work, to
>          collect inputs from the group as to which operations should be
> made required.
> 5. Glen Petrie's Summary Of IPP Operations Supported document.
> 6. Next steps



From ipp-owner@pwg.org  Thu Mar 20 09:07:49 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B384528C30C
	for <ietfarch-ipp-archive@core3.amsl.com>; Thu, 20 Mar 2008 09:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rmSxNd6J9Urh for <ietfarch-ipp-archive@core3.amsl.com>;
	Thu, 20 Mar 2008 09:07:48 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id A70E128C26C
	for <ipp-archive@ietf.org>; Thu, 20 Mar 2008 09:07:48 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2KG5QoJ028988
	for <ipp-archive@ietf.org>; Thu, 20 Mar 2008 12:05:28 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2KG5QFJ028985
	for <ipp-archive@lists.ietf.org>; Thu, 20 Mar 2008 12:05:26 -0400
Received: by pwg.org (bulk_mailer v1.13); Thu, 20 Mar 2008 12:04:29 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2KG4Ok4028707
	for <ipp-outgoing@pwg.org>; Thu, 20 Mar 2008 12:04:26 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2KG4OW6028704
	for ipp-outgoing; Thu, 20 Mar 2008 12:04:24 -0400
Received: from eitc220.eitc.epson.com (eitcmail.eitc.epson.com [12.104.142.220] (may be forged))
	by pwg.org  with ESMTP id m2KG4Lnr028671
	for <IPP@pwg.org>; Thu, 20 Mar 2008 12:04:24 -0400
Received: by eitc220.eitc.epson.com with Internet Mail Service (5.5.2653.19)
	id <G0MCPKZ2>; Thu, 20 Mar 2008 09:04:18 -0700
Message-ID: <2F7D63A21DB2C74EB8EB8C09AF667DB0152D33BE@eitc220.eitc.epson.com>
From: "Petrie, Glen" <glen.petrie@eitc.epson.com>
To: IPP@pwg.org
Subject: RE: IPP> Reminder, Next IPPv2 Teleconference on Thurs (March 20) 
	at 11:00 AM EDT
Date: Thu, 20 Mar 2008 09:04:18 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ipp@pwg.org

All,

I have updated the document I put out earlier with all of CUPS IPP codes
supported.

ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-info/IPP-Operations-Supported-By-Solutio
ns.pdf  (doc)

glen

> -----Original Message-----
> From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of Petrie,
> Glen
> Sent: Thursday, March 20, 2008 7:26 AM
> To: IPP@pwg.org
> Subject: RE: IPP> Reminder, Next IPPv2 Teleconference on Thurs (March 20)
> at 11:00 AM EDT
> 
> Please see the following document in reference to Item 5.0 below
> 
> 
> ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-info/IPP-Operations-Supported-By-
> Solutio
> ns.pdf (doc)
> 
> glen
> 
> 
> > -----Original Message-----
> > From: owner-ipp@pwg.org [mailto:owner-ipp@pwg.org] On Behalf Of
> > Ron.Bergman@ricoh-usa.com
> > Sent: Tuesday, March 18, 2008 5:12 PM
> > To: IPP@pwg.org
> > Subject: IPP> Reminder, Next IPPv2 Teleconference on Thurs (March 20) at
> > 11:00 AM EDT
> >
> >
> > IPPv2 WG Conference Call:
> >
> > Thursday, March 20, 2008, 11:00 AM EDT  (8:00 AM PDT)
> >
> > Toll Free:     1-866-365-4406
> > International: 00+1+303-248-9655
> > Passcode:      2635888#
> >
> > Agenda:
> >
> > 1. Identify Minute Taker
> > 2. Approval of minutes from 3/6 Conference Call
> > 3. Review of Action Items
> >    Ira - Obtain a list of the IPP operations supported by Open Solaris -
> > Completed
> >    Ron - Generate a spread sheet similar to the one used in the WIMS/CIM
> > work, to
> >          collect inputs from the group as to which operations should be
> > made required.
> > 5. Glen Petrie's Summary Of IPP Operations Supported document.
> > 6. Next steps


From ipp-owner@pwg.org  Thu Mar 20 18:07:50 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA4D93A67EB
	for <ietfarch-ipp-archive@core3.amsl.com>; Thu, 20 Mar 2008 18:07:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id S1G1WW1+f+SI for <ietfarch-ipp-archive@core3.amsl.com>;
	Thu, 20 Mar 2008 18:07:48 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 931ED3A68FD
	for <ipp-archive@ietf.org>; Thu, 20 Mar 2008 18:07:48 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2L15RI7015447
	for <ipp-archive@ietf.org>; Thu, 20 Mar 2008 21:05:29 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2L15L0E015439
	for <ipp-archive@lists.ietf.org>; Thu, 20 Mar 2008 21:05:27 -0400
Received: by pwg.org (bulk_mailer v1.13); Thu, 20 Mar 2008 21:04:20 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2L14FAv015047
	for <ipp-outgoing@pwg.org>; Thu, 20 Mar 2008 21:04:17 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2L14FWU015044
	for ipp-outgoing; Thu, 20 Mar 2008 21:04:15 -0400
Received: from mail2.sharplabs.com (mail2.sharplabs.com [216.65.151.51])
	by pwg.org  with ESMTP id m2L14Deh015032
	for <ipp@pwg.org>; Thu, 20 Mar 2008 21:04:15 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail2.sharplabs.com (Postfix) with ESMTP id A85791E13DE
	for <ipp@pwg.org>; Thu, 20 Mar 2008 18:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at sharplabs.com
Received: from mail2.sharplabs.com ([127.0.0.1])
	by localhost (mail2.sharplabs.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rBPWu6sZS9ak for <ipp@pwg.org>;
	Thu, 20 Mar 2008 18:04:11 -0700 (PDT)
Received: from wabex1.enet.sharplabs.com (wabex1.sharpamericas.com [172.29.224.8])
	by mail2.sharplabs.com (Postfix) with ESMTP
	for <ipp@pwg.org>; Thu, 20 Mar 2008 18:04:11 -0700 (PDT)
Received: from wabex2.sharpamericas.com ([172.29.224.9]) by wabex1.enet.sharplabs.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 20 Mar 2008 18:03:59 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject:  IPP> Teleconference call minutes
Date: Thu, 20 Mar 2008 18:03:59 -0700
Message-ID: <2DB650784C0A9649B560DE38F68DA744288C68@wabex2.sharpamericas.com>
In-Reply-To: <2DB650784C0A9649B560DE38F68DA744288BA6@wabex2.sharpamericas.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic:  IPP> Teleconference call minutes
Thread-Index: AchvXEXXHeBA66wORWC9OqlJeQlOfgGKpY/gBVoYM/A=
References: <OF51CB4E7D.4D641DCA-ON882573EF.007C74CC-882573EF.007CD44E@ricoh-usa.com> <2DB650784C0A9649B560DE38F68DA744288BA6@wabex2.sharpamericas.com>
From: "Whittle, Craig" <cwhittle@sharplabs.com>
To: <ipp@pwg.org>
X-OriginalArrivalTime: 21 Mar 2008 01:04:00.0033 (UTC) FILETIME=[72594910:01C88AEF]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pwg.org id m2L14Feh015042
Sender: owner-ipp@pwg.org

All:

The minutes from this week's teleconference call can be found at:
ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-minutes/IPPv2-ConCall-Minutes-200803
20.pdf  

Best regards,
 
**CW




From pwg-announce-owner@pwg.org  Fri Mar 21 11:41:57 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1DCD53A6BC7;
	Fri, 21 Mar 2008 11:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6TJfTPAS-8iS; Fri, 21 Mar 2008 11:41:56 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 2CE2C3A68BE;
	Fri, 21 Mar 2008 11:41:56 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2LISKag009494;
	Fri, 21 Mar 2008 14:39:34 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2LHCS1K029847;
	Fri, 21 Mar 2008 13:12:34 -0400
Received: by pwg.org (bulk_mailer v1.13); Fri, 21 Mar 2008 13:07:37 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2LH6xfO028830
	for <pwg-announce-out@pwg.org>; Fri, 21 Mar 2008 13:07:01 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2LH6xhj028827
	for pwg-announce-out; Fri, 21 Mar 2008 13:06:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        bh=1j8HE5tct95HhwC1yoHM5czT5ZaTBTM9rDMLNg8nZoo=;
        b=XsRrHRMc/M3CIdN0ydWP3sP5SUs8vHymEgxy7q5RQ0v9TIrPoMCAxNjs5F352Y/N8IeoLqjV4vI3okMQZW9BEaqz6LCc5rHvYQZgF2BSYxTURF07QNGquIadbr+/Lmd96oUr4P1V8T8X5B9etuHu56kbfLKfZtm9icRIWXDy9Ns=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=qlP9Ph8pprLEBoGEkRc/wxOZeUaxHarF06bWvPWsF8OrsbuaOzXzfoa7kbHywhZHTaRTxa6OzX21h7co4REhHZtVUmY8/r4/MhxaCUNEjj3kA5W2jn7nUAuO+iql57JNB5BqC3MlBNBj5QbFZ2pQ8wgdeVzTu17eRUmd7NM451k=
Message-ID: <e395be80803211006k176dce88id7bc50cf0796095f@mail.gmail.com>
Date: Fri, 21 Mar 2008 13:06:27 -0400
From: "Ira McDonald" <blueroofmusic@gmail.com>
To: pwg-announce@pwg.org, "Ira McDonald" <blueroofmusic@gmail.com>
Subject: PWG-ANNOUNCE> PWG Candidate Standard - PWG Counter MIB v2!
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-pwg-announce@pwg.org

Hi,

At yesterday's PWG Steering Committee meeting, the process and votes
were reviewed and approved by the SC.

The final result:
YES - 10
NO - 0
ABSTAIN - 0

Harry Lewis (InfoPrint, PWG Secretary) and I have the action item to
fix up boilerplate, dates, etc. and get the final text published on the
PWG server.  This may take a few weeks yet.

Cheers,
- Ira (editor of PWG Counter MIB v2)

-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
 579 Park Place Saline, MI 48176
 734-944-0094
summer:
 PO Box 221 Grand Marais, MI 49839
 906-494-2434


From pwg-announce-owner@pwg.org  Fri Mar 21 13:46:12 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81C1F28C0FC;
	Fri, 21 Mar 2008 13:46:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.037
X-Spam-Level: 
X-Spam-Status: No, score=-1.037 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_IMAGE_ONLY_28=1.561, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JOHs19WTsAiJ; Fri, 21 Mar 2008 13:46:11 -0700 (PDT)
Received: from pwg.org (www.pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 6D2413A6BF5;
	Fri, 21 Mar 2008 13:46:11 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2LKhojg002367;
	Fri, 21 Mar 2008 16:43:52 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2LKhi7S002350;
	Fri, 21 Mar 2008 16:43:50 -0400
Received: by pwg.org (bulk_mailer v1.13); Fri, 21 Mar 2008 16:37:09 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2LKaYUF001233
	for <pwg-announce-out@pwg.org>; Fri, 21 Mar 2008 16:36:36 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2LKaYdA001230
	for pwg-announce-out; Fri, 21 Mar 2008 16:36:34 -0400
In-Reply-To: <e395be80803211006k176dce88id7bc50cf0796095f@mail.gmail.com>
To: "Ira McDonald" <blueroofmusic@gmail.com>
Cc: pwg-announce@pwg.org
MIME-Version: 1.0
Subject: Re: PWG-ANNOUNCE> PWG Candidate Standard - PWG Counter MIB v2!
X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006
Message-ID: <OF44EAA6F0.8D630A9F-ON87257413.007080D9-87257413.0071259D@us.ibm.com>
From: Harry Lewis <harryl@us.ibm.com>
Date: Fri, 21 Mar 2008 14:35:51 -0600
X-MIMETrack: Serialize by Router on D03NM132/03/M/IBM(Release 7.0.2FP2HF300 | September
 14, 2007) at 03/21/2008 14:35:53,
	Serialize complete at 03/21/2008 14:35:53
Content-Type: multipart/related; boundary="=_related 0071259B87257413_="
Sender: owner-pwg-announce@pwg.org

This is a multipart message in MIME format.
--=_related 0071259B87257413_=
Content-Type: multipart/alternative; boundary="=_alternative 0071259B87257413_="


--=_alternative 0071259B87257413_=
Content-Type: text/plain; charset="US-ASCII"

Indeed, the Imaging State and Counter MIB v2 has received final approval 
as a PWG Candidate Standard. Thanks to everyone who contributed for their 
hard work and thanks, Ira, for further helping get the word out!

Regards,
Harry - PWG Secretary


Harry Lewis
Program Manager - Intellectual Property & Standards
Phone: 303-924-5337
e-mail: harryl@us.ibm.com
infoprint.com




"Ira McDonald" <blueroofmusic@gmail.com> 
Sent by: owner-pwg-announce@pwg.org
03/21/2008 11:06 AM

To
pwg-announce@pwg.org, "Ira McDonald" <blueroofmusic@gmail.com>
cc

Subject
PWG-ANNOUNCE> PWG Candidate Standard - PWG Counter MIB v2!






Hi,

At yesterday's PWG Steering Committee meeting, the process and votes
were reviewed and approved by the SC.

The final result:
YES - 10
NO - 0
ABSTAIN - 0

Harry Lewis (InfoPrint, PWG Secretary) and I have the action item to
fix up boilerplate, dates, etc. and get the final text published on the
PWG server.  This may take a few weeks yet.

Cheers,
- Ira (editor of PWG Counter MIB v2)

-- 
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic@gmail.com
winter:
 579 Park Place Saline, MI 48176
 734-944-0094
summer:
 PO Box 221 Grand Marais, MI 49839
 906-494-2434


--=_alternative 0071259B87257413_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Indeed, the Imaging State and Counter
MIB v2 has received final approval as a PWG Candidate Standard. Thanks
to everyone who contributed for their hard work and thanks, Ira, for further
helping get the word out!</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Harry - PWG Secretary<br>
</font>
<table border>
<tr>
<td bgcolor=white>
<div align=center><img src=cid:_1_07B7347007B730B40071259B87257413></div>
<td bgcolor=#efefef><font size=1 face="Arial"><b>Harry Lewis</b></font><font size=1 color=#808080 face="Arial"><br>
Program Manager - Intellectual Property &amp; Standards<br>
Phone: 303-924-5337<br>
e-mail: harryl@us.ibm.com</font><font size=1 color=blue face="Arial"><br>
</font><a href=http://www.infoprint.com/><font size=1 color=blue face="Arial">infoprint.com</font></a></table>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>&quot;Ira McDonald&quot;
&lt;blueroofmusic@gmail.com&gt;</b> </font>
<br><font size=1 face="sans-serif">Sent by: owner-pwg-announce@pwg.org</font>
<p><font size=1 face="sans-serif">03/21/2008 11:06 AM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">pwg-announce@pwg.org, &quot;Ira McDonald&quot;
&lt;blueroofmusic@gmail.com&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">PWG-ANNOUNCE&gt; PWG Candidate Standard
- PWG Counter MIB v2!</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hi,<br>
<br>
At yesterday's PWG Steering Committee meeting, the process and votes<br>
were reviewed and approved by the SC.<br>
<br>
The final result:<br>
YES - 10<br>
NO - 0<br>
ABSTAIN - 0<br>
<br>
Harry Lewis (InfoPrint, PWG Secretary) and I have the action item to<br>
fix up boilerplate, dates, etc. and get the final text published on the<br>
PWG server. &nbsp;This may take a few weeks yet.<br>
<br>
Cheers,<br>
- Ira (editor of PWG Counter MIB v2)<br>
<br>
-- <br>
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Blue Roof Music/High North Inc<br>
email: blueroofmusic@gmail.com<br>
winter:<br>
 579 Park Place Saline, MI 48176<br>
 734-944-0094<br>
summer:<br>
 PO Box 221 Grand Marais, MI 49839<br>
 906-494-2434<br>
</font></tt>
<br>
--=_alternative 0071259B87257413_=--
--=_related 0071259B87257413_=
Content-Type: image/gif
Content-ID: <_1_07B7347007B730B40071259B87257413>
Content-Transfer-Encoding: base64

R0lGODlhWgAaALMAAPnJypu06PFvdGOK3MHQ8PWrrfOJjO9JT7m5ufbn5XGT3lR+2OwcJAAAAP//
/wAAACH5BAAAAAAALAAAAABaABoAAAT/0MlJq704a9m210AoAl8iJpUZot/VVYFCOLFi27NUB9PO
/EBgQSL4HSaGQ5BxICWUwcNQAiRRf5YXRbGYBRbgcFfCXSgmZQXwYDAUf6T30fFmCO6HYwF4rwuu
DFYOQFkWXF4LPDpmZAsDCxOOZoQTbwZ0Rg57cCwsQAYoCZuBg3ATlBRaaGNfig4EjA5ch69mk1gO
olWYTA5QlxWjLLm/CWt5UAyFFbRfCgHQjzlcrTSJtwwGS8Byvj/AFKMV3UtLy1usYmHTXYwKA7Bq
WNpMgt1QfxUAQMPe2aXZCghENUFVI0QyCBD4AklWFy4OzMSjRI/BlG4Vp0hI8ORHPk27+3YBOrcK
kSuHMw61SjQRl4OMvI4kqMNGgBJdRtwIySUSIMmD1lwlkIYyXpeWyjZWBNAtV4FkHgGYqGNEY0+C
HAylG3ADzBmUEcHU+tqCAscV/Tiq6Fc2K7N06sjSmjW2rd27P/Hq3cvXbd+/gAMLHky4sOHDiBMr
Xsy4sEEEqhpIRpCqghbIBjP71YA5cIfJDjpApvzis+jQDRB0Dj1hNOvPnSm7Bg3Z7+zUqVFTDk06
t+nXvD+j9p1V+GXixoEDT66l+fLnpJ9Llq7cLXPL1IVnt15we+nko6/Prgz9u2zirmuLRs5bQmz2
pkmrZx06R2PFBl3cZ5wfu4MIADs=
--=_related 0071259B87257413_=--


From ipp-owner@pwg.org  Tue Mar 25 14:07:10 2008
Return-Path: <ipp-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B5EB23A689E
	for <ietfarch-ipp-archive@core3.amsl.com>; Tue, 25 Mar 2008 14:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5
	tests=[AWL=-1.300, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id FKyHV+v-d+S8 for <ietfarch-ipp-archive@core3.amsl.com>;
	Tue, 25 Mar 2008 14:07:09 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 68A863A68E3
	for <ipp-archive@ietf.org>; Tue, 25 Mar 2008 14:07:02 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2PL4NeB028388
	for <ipp-archive@ietf.org>; Tue, 25 Mar 2008 17:04:25 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2PL4Fk9028365
	for <ipp-archive@lists.ietf.org>; Tue, 25 Mar 2008 17:04:23 -0400
Received: by pwg.org (bulk_mailer v1.13); Tue, 25 Mar 2008 17:02:09 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2PL1xgR028063
	for <ipp-outgoing@pwg.org>; Tue, 25 Mar 2008 17:02:01 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2PL1xXD028060
	for ipp-outgoing; Tue, 25 Mar 2008 17:01:59 -0400
Received: from njwcntas37.us.ricoh.ds (host150.ricoh-usa.com [208.252.21.150])
	by pwg.org  with ESMTP id m2PL1rjx028050
	for <ipp@pwg.org>; Tue, 25 Mar 2008 17:01:57 -0400
X-SEF-Processed: 5_0_0_816__2008_03_25_17_01_52
Received: from Unknown [172.16.19.238] by njwcntas37.us.ricoh.ds - SurfControl E-mail Filter ; Tue, 25 Mar 2008 17:01:52 -0400
Subject: IPP> IPPv2 Conference Call on April 3rd is Canceled.
To: ipp@pwg.org
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF5928B3DD.DA6C4365-ON88257417.00730A1E-88257417.00738514@ricoh-usa.com>
From: Ron.Bergman@ricoh-usa.com
Date: Tue, 25 Mar 2008 14:01:47 -0700
X-MIMETrack: Serialize by Router on NJWC02/RCUS(Release 7.0.2FP1|January 10, 2007) at 03/25/2008
 05:01:52 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Sender: owner-ipp@pwg.org


The next IPPv2 discussion will be at the IPP face-to-face meeting in Mesa,
Arizona on Thursday afternoon (April 10).  See the PWG web sit for exact
times.




From pwg-announce-owner@pwg.org  Wed Mar 26 12:36:55 2008
Return-Path: <pwg-announce-owner@pwg.org>
X-Original-To: ietfarch-ipp-archive@core3.amsl.com
Delivered-To: ietfarch-ipp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DD4728C0F7;
	Wed, 26 Mar 2008 12:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.261
X-Spam-Level: 
X-Spam-Status: No, score=0.261 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YQ+MBdCCmduj; Wed, 26 Mar 2008 12:36:54 -0700 (PDT)
Received: from pwg.org (pwg.org [192.146.101.49])
	by core3.amsl.com (Postfix) with ESMTP id 6F8DD28C6E3;
	Wed, 26 Mar 2008 12:36:54 -0700 (PDT)
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2QJYVMd030780;
	Wed, 26 Mar 2008 15:34:33 -0400
Received: from localhost (mail@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) with SMTP id m2QJYV5G030777;
	Wed, 26 Mar 2008 15:34:31 -0400
Received: by pwg.org (bulk_mailer v1.13); Wed, 26 Mar 2008 15:32:26 -0400
Received: from pwg.org (localhost.localdomain [127.0.0.1])
	by pwg.org  with ESMTP id m2QJWLft029920
	for <pwg-announce-out@pwg.org>; Wed, 26 Mar 2008 15:32:23 -0400
Received: (from majordom@localhost)
	by pwg.org (8.13.1/8.13.1/Submit) id m2QJWLLG029917
	for pwg-announce-out; Wed, 26 Mar 2008 15:32:21 -0400
X-Xerox-Source-Ip: 13.151.210.15
X-Xerox-Source-Name: usa7061gw002.na.xerox.net
X-Xerox-Reported-Name: USA7061GW002.na.xerox.net
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----_=_NextPart_001_01C88F77.F9867131"
Subject: PWG-ANNOUNCE> Last Call - Network Scan Service Use Cases and Requirements v1.0 
Date: Wed, 26 Mar 2008 15:31:22 -0400
Message-ID: <1E8895E89BED824DBEDD47CDCA8CC28C02F168CF@USA0300MS04.na.xerox.net>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call - Network Scan Service Use Cases and Requirements v1.0 
Thread-Index: AciPd/kkn7oBbqBLTnCKLYLRw5gwGQ==
From: "Zehler, Peter" <Peter.Zehler@xerox.com>
To: <pwg-announce@pwg.org>
Cc: <mfd@pwg.org>
X-OriginalArrivalTime: 26 Mar 2008 19:31:48.0292 (UTC) FILETIME=[08957840:01C88F78]
Sender: owner-pwg-announce@pwg.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C88F77.F9867131
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C88F77.F9867131"


------_=_NextPart_002_01C88F77.F9867131
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

The Network Scan Service Use Cases and Requirements v1.0 has completed
MFD Working Group Last Call.  The document is now being submitted to all
members of the PWG for review and comments.=20

The document can be found at: <
ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdscanreq10-20080324.pdf>.=20

The last call will end on April 17, 2008.=20

Send any comments or suggestions to mfd@pwg.org=20

Peter Zehler=20
Chairman MFD Working Group=20



=20

Peter Zehler
=20
Xerox Research Center Webster
Email: Peter.Zehler@Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701=20

=20


------_=_NextPart_002_01C88F77.F9867131
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Impact;
	panose-1:2 11 8 6 3 9 2 5 2 4;}
@font-face
	{font-family:XeroxPeopleNet;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p><font size=3D3 color=3Dblack face=3D"Times New Roman"><span lang=3DEN
style=3D'font-size:12.0pt;color:black'>All,<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblack face=3D"Times New Roman"><span lang=3DEN
style=3D'font-size:12.0pt;color:black'>The Network Scan Service Use =
Cases and
Requirements v1.0 has completed MFD Working Group Last Call. &nbsp;The =
document
is now being submitted to all members of the PWG for review and =
comments. <o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblack face=3D"Times New Roman"><span lang=3DEN
style=3D'font-size:12.0pt;color:black'>The document can be found at: =
&lt;<a
href=3D"ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdscanreq10-20080324.pdf">=
ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdscanreq10-20080324.pdf</a></span=
></font><span
lang=3DEN>&gt;.<font color=3Dblack><span style=3D'color:black'> =
<o:p></o:p></span></font></span></p>

<p><font size=3D3 color=3Dblack face=3D"Times New Roman"><span lang=3DEN
style=3D'font-size:12.0pt;color:black'>The last call will end on April =
17, 2008. <o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblack face=3D"Times New Roman"><span lang=3DEN
style=3D'font-size:12.0pt;color:black'>Send any comments or suggestions =
to <a
href=3D"mailto:mfd@pwg.org">mfd@pwg.org</a> =
<o:p></o:p></span></font></p>

<p><font size=3D3 color=3Dblack face=3D"Times New Roman"><span lang=3DEN
style=3D'font-size:12.0pt;color:black'>Peter Zehler <br>
Chairman MFD Working Group <br>
<br>
<o:p></o:p></span></font></p>

<!-- body=3D"end" -->

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3DImpact><span =
style=3D'font-size:
12.0pt;font-family:Impact;color:navy'>Peter <st1:PlaceName =
w:st=3D"on">Zehler</st1:PlaceName></span></font><br>
<font color=3Dred face=3DXeroxPeopleNet><span =
style=3D'font-family:XeroxPeopleNet;
color:red'><img border=3D0 width=3D120 height=3D40 id=3D"_x0000_i1025"
src=3D"cid:image002.jpg@01C88F56.720E2C30"></span></font><br>
<st1:place w:st=3D"on"><st1:PlaceName w:st=3D"on"><font size=3D2 =
color=3Dnavy
  face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;color:navy'>Xerox</span></fo=
nt></st1:PlaceName><font
 size=3D2 color=3Dnavy face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
 color:navy'> <st1:PlaceName w:st=3D"on">Research</st1:PlaceName> =
<st1:PlaceType
 w:st=3D"on">Center</st1:PlaceType></span></font></st1:place><font =
size=3D2
color=3Dnavy face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma;
color:navy'> Webster<br>
</span></font><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:navy'>Email: =
Peter.Zehler@Xerox.com</span></font><br>
<font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>Voice: (585) 265-8755</span></font><br>
<font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>FAX: (585) 265-7441</span></font><br>
<font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>US Mail: Peter Zehler</span></font><br>
<font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>Xerox Corp.</span></font><br>
<font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>800 Phillips Rd.</span></font><br>
<font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>M/S 128-25E</span></font><br>
<font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:navy'>Webster NY, 14580-9701</span></font> <o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_002_01C88F77.F9867131--

------_=_NextPart_001_01C88F77.F9867131
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01C88F56.720E2C30>
Content-Description: image002.jpg
Content-Location: image002.jpg

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8lJCIf
IiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIoOzs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAARCAAoAHgDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD2aisD
xP4oPho27PYPcRT5G9XC7SMcdPT+Rp+ueK7LRdIg1AD7SLnHkIrYLgjJP0A/mB3qeZK/kdEcNVko
tR+LY3KKwtT8VWujaRbXmoQvFPcoGW1UguDgEg9OmeTWVD8QhFPEuq6LdafBMfkmfJGPXBUcfTNJ
zit2VDB15x5ox0/rbv8AI7KisrXfENloOnrd3BaQSHbEkeCZDjPHtjvWXpHjKbUZWe60aewsVhaY
3krHZtGO+0A5z2NNySdiY4arKn7RLT+vvOporim+IrSmSWw0G8urWI/PPyNvuQFIH4kVrW/i21v/
AA9c6tp8LztbLmW2JCuvr69skHvikpxfUueCrwSco+XT8e3zN+isLQ/FdlrGkT6gw+yi2J85HbOw
YyDn0I/rTvDPiI+JLae5Wxe2hjfYjO4O84ye3GOPzpqSdrGc8PVhzOSty6M26oarrWn6LAst/cCI
OcIoBZnPso5NW7iZbe3kmb7qKWNcpGbTVL5riVLW4uH46xyMo7KOCcfhTZEEm7yTt5Ei+OBM/wDo
2kzsnrJKiE/gCa3NO1aPUIQ7QyWzlivlyEE5+oJFZp0DT7hTm2ETj+KL5CPyAH5rVrTNIext5IZJ
hMC5KErg4wOD+VSua+pvVeHcP3aaZr0Vg+H9Rb7ZdaRNIZDbktbuxyzR7sYJ7lTgZ9CvfJoqk7nP
ODhKzDxmdO/4Rm5GpEhCP3W0fN5n8O33/pntXnfhzyItd0wa8swttm61En3BliVPP8O7PTvjPFeg
+I/Cz+Ir+zkmvvLs7Y5a3EWTJzz827jIAHTjn1p/ifwtB4isYYBKtrJA2Y5BHuwuMFcZHHT8hWM4
OUr9vxPXwmKo0aKpSfxXu/5emn6nIeM2u28fWqxiIuqRfZxN9wnJxn/gVX9X0vxtrlibO9h04xbw
4KNggj3rZ1LwZFrGj2lrfXbPe2kexbxUwWH+0pJz+fX0zWcPAmrTp9nvvFV3La9DGobkfi5H6Gk4
Su/M1hi6PJC0knDTWLfzX/BMbxtbXFnonh6zuyDLDEyPg5GQEHWum+Ifmr4SkWIYTzYw+P7uf8cV
N4n8Jt4iWyUX5g+y7gS0W8vnHuMHj9a3bu0gvrSW1uYxJDKpV0PcVXI/e8zleLgo0ZbuLba9XcyP
BQhHhHT/ACcYMZL4/vZO79c1y3gjYnjPWFtyBZhZf93Ak+X9M/hV8eAL+18yDTfElxbWcpJaIoc8
/RgCfwFaMXgyKy8OXOlafdmCa7wJrp03Mw7jAIwMZGPc0rSdtNjR1aEfaWnf2nk9Nb3fp5HnGpiL
7ZqT6N9o/skyKrleFwTkD6ZB259q9b8PNpzaFaHSuLTZ8gPUeu73znPvUGl+GbPT/DraM+JklVhO
+3aZCep747Y9MCoPCvhq48NQ3ED6iLuGVgyr5OzY3Qn7x6jH5U4QcX6hjMXSxFLlTs4vT+8trvz/
AEKnxIZx4QlVfuvNEr/TcD/MCvJnHPTpXuXiDShrWhXWn5CtKmUY9A4IZT+YFeMz2rgskiGOWNik
iMOVYdQayrp3TPQySpH2UqfW9zU0Hxrq+lTRwszX9uSFEMhy/wDwBuoPscivYFYlQcbT6HqK8t8E
eHy96urXa4ihObdSPvv/AHseg7erfQ10/iTxguhvbQwhZZWcPKmfuxd8H1PQfQnuK0ptxheRwY+l
CtiVSw8detiG2tpdO+INvAGLJMkrqx7oRkg/RgP0ororO3hu7yHVR822FkhbsVfaSf8Ax0YorWKs
eZWqOo03ulY06KKKowCiiigAooooAKKKKACiiigArG1XwtpmrXYvJodtyBguCQHx03AfexRRSaT3
KhOUHeLsyjd6TrcMWzTks5GxgNLKyKvb7oU5+n4dOKybD4cSXF6174ivxdOzbnhhJCufdjg49gBR
RScU9zenialKLUHa+76/ed3HGkMaxRoqIgCqqjAUDoAKKKKo5j//2Q==

------_=_NextPart_001_01C88F77.F9867131--


