Jerry Thrasher | 2 Sep 2008 19:57
Favicon

PWG-ANNOUNCE> FYI, (New Printer Working Group IP Policy) notifications sent.


PWG Members,

The following email note was sent to the primary/designated representatives of all currently
PWG member companies.  The attachement (a .zip file with the extension changed to .piz)
that is removed in this email, is roughly 2.5 MBytes therefore some email systems may
quaranteen the email.

If you did not receive this email, and think you should have, please let me know..

Jerry Thrasher
Printer Working Group 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 09/02/2008 01:51 PM -----


Greetings:

As the primary, or designated, contact for the Printer Working Group.
I am sending you this announcement regarding an upcoming change in
the operating procedures and intellectual property policy for
membership in the Printer Working Group.

Background:
The PWG's IP policy was originally drafted more than ten years ago
before the PWG became affiliated with the IEEE-ISTO.
Since then there have been many changes to the language used in IP policies
of peer organizations to the PWG and other standards setting organizations
to increase the precision of the language used in the policy.

The PWG Officers and Steering Committee have determined that the
PWG's IP Policy needs to be updated to reflect the current
generally accepted language used in the industry. In fact
the new IP Policy is EXACTLY the same as the IEEE Standards
Association (used with permission).

Note: The basic intent of the PWG's policy is NOT changing.
The PWG has operated with the ability for a PWG member to
choose whether they will license IP or not and under what
"reasonable" terms if they choose.
 
Attached is a (zip) file (please rename the extension from
piz to zip), that contains the following:

1. A presentation (PWG_IP_Policy_Update_Overview.pdf) that
describes what changes are being made to the PWG Process and
the PWG IP Policy.

2. The NEW IP Policy (pwg-ip-policy-20080827.pdf)

3. The Updated PWG Process (pwg-process30-20080827, clean
and changebar,.pdf)

4. The NEW PWG Letter of Assurance (PWG_LOA_20080827.pdf)

5. The updated PWG membership form (pwg_membership_form_20080827.pdf)

6. The original PWG Process 2.0 (pwg-process20.pdf) that contains
the PWG's original IP Policy (Section 10).

This (zip) file can also be downloaded from the PWG's FTP site at:

ftp://ftp.pwg.org/pub/pwg/general/New_PWG_IP.zip

It is EXTREMELY important that you review the new IP Policy,LOA, and
PWG Process document with your companies legal staff, and respond with
any issues.  Note: Since the IP Policy was adopted verbatim from the IEEE's, only
issues that would cause your company to withdraw from the PWG should be
raised.

Please try to complete this review by the end of October 2008.  
In November, when the ISTO sends out invoices for PWG membership renewal
for 2009, a new membership agreement acknowledging the new IP policy
and PWG Process 3.0 will also be required.

Please send any questions or issues to the PWG Officers.

<email addresses removed>

Thank you for your prompt action:

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

[attachment "New_PWG_IP.piz" deleted by Jerry Thrasher/Lex/Lexmark]
Michael R Sweet | 3 Sep 2008 02:18
Picon
Favicon

IPP> Complete list of required IPP attributes

All,

Attached are CSV files listing the attributes required for IPP v2.x.

Some comments for discussion:

1. IPP v2.1 requires RFC 3381 (Job Progress Attributes), however all
    of the attributes defined by 3381 are OPTIONAL.  Do we want to make
    them REQUIRED?

2. IPP v2.2 requires RFC 3382 (The 'collection' attribute syntax),
    and while the media-color and media-size attributes of the media-col
    attribute are REQUIRED, the wording of section 5 does not
    specifically require media-col, and in fact says that the examples
    in the spec are only provided to illustrate how to define
    collections in their own spec:

       All of the example attribute definitions in this document are
       illustrative examples, rather than actual definitions.  These
       examples are intended to illustrate how to define collection
       attributes.  Other documents MUST define collection attributes for
       use in actual interchange.  Such definitions may be very similar
       to the examples in this document, since we attempted to pick
       useful examples.

    I've included media-col and the corresponding printer description
    attributes (-default, -ready, and -supported) as required attributes,
    however even "media" is not required by our current IPP/2.x specs...

3. IPP v2.2 requires several PWG 5100.3, but all attributes are
    OPTIONAL.  Do we want to make them REQUIRED?

4. IPP v2.2 requires several PWG 5100.8, but all attributes are
    OPTIONAL.  Do we want to make them REQUIRED?

-- 
______________________________________________________________________
Michael R Sweet                        Senior Printing System Engineer

Attribute,Min Version,Specification
notify-subscribed-event,2.1,RFC 3995
notify-text,2.1,RFC 3995
Attribute,Min Version,Specification
compression-supplied,2.1,PWG 5100.7
document-job-id,2.2,PWG 5100.5
document-job-url,2.2,PWG 5100.5
document-number,2.2,PWG 5100.5
document-printer-uri,2.2,PWG 5100.5
document-state,2.2,PWG 5100.5
document-state-reasons,2.2,PWG 5100.5
job-id,2.0,RFC 2911
job-name,2.0,RFC 2911
job-originating-user-name,2.0,RFC 2911
job-printer-up-time,2.0,RFC 2911
job-printer-uri,2.0,RFC 2911
job-state,2.0,RFC 2911
job-state-reasons,2.0,RFC 2911
job-uri,2.0,RFC 2911
media-col,2.1,RFC 3282
number-of-documents,2.2,PWG 5100.5
time-at-completed,2.0,RFC 2911
time-at-creation,2.0,RFC 2911
time-at-processing,2.0,RFC 2911
Attribute,Min Version,Specification
multiple-document-handling,2.2,PWG 5100.5
overrides,2.2,PWG 5100.6
Attribute,Min Version,Specification
attributes-charset,2.0,RFC 2911
attributes-natural-language,2.0,RFC 2911
compression,2.0,RFC 2911
document-format,2.0,RFC 2911
document-name,2.0,RFC 2911
document-number,2.2,PWG 5100.5
ipp-attribute-fidelity,2.0,RFC 2911
job-hold-until,2.1,RFC 2911
job-id,2.0,RFC 2911
job-mandatory-attributes,2.2,PWG 5100.5
job-uri,2.0,RFC 2911
last-document,2.1,RFC 2911
limit,2.0,RFC 2911
my-jobs,2.0,RFC 2911
notify-sequence-numbers,2.1,RFC 3996
notify-subscription-ids,2.1,RFC 3996
notify-wait,2.1,RFC 3996
printer-uri,2.0,RFC 2911
requested-attributes,2.0,RFC 2911
requesting-user-name,2.0,RFC 2911
which-jobs,2.0,RFC 2911
Attribute,Min Version,Specification
charset-configured,2.0,RFC 2911
charset-supported,2.0,RFC 2911
compression-supported,2.0,RFC 2911
document-format-default,2.0,RFC 2911
document-format-supported,2.0,RFC 2911
generated-natural-language-supported,2.0,RFC 2911
ipp-versions-supported,2.0,RFC 2911
ippget-event-life,2.1,RFC 3996
job-hold-until-default,2.1,RFC 2911
job-hold-until-supported,2.1,RFC 2911
job-settable-attributes-supported,2.1,RFC 3380
media-col-default,2.1,RFC 3382
media-col-ready,2.1,RFC 3382
media-col-supported,2.1,RFC 3382
natural-language-configured,2.0,RFC 2911
notify-events-default,2.1,RFC 3995
notify-events-supported,2.1,RFC 3995
notify-lease-duration-default,2.1,RFC 3995
notify-lease-duration-supported,2.1,RFC 3995
notify-max-events-supported,2.1,RFC 3995
notify-pull-method-supported,2.1,RFC 3995
operations-supported,2.0,RFC 2911
pdl-override-supported,2.0,RFC 2911
printer-is-accepting-jobs,2.0,RFC 2911
printer-name,2.0,RFC 2911
printer-settable-attributes-supported,2.1,RFC 3380
printer-state,2.0,RFC 2911
printer-state-reasons,2.0,RFC 2911
printer-up-time,2.0,RFC 2911
printer-uri-supported,2.0,RFC 2911
queued-job-count,2.0,RFC 2911
uri-authentication-supported,2.0,RFC 2911
uri-security-supported,2.0,RFC 2911
,2.1,RFC 3995
Attribute,Min Version,Specification
notify-get-interval,2.1,RFC 3996
notify-job-id,2.1,RFC 3995
notify-lease-expiration-time,2.1,RFC 3995
notify-printer-up-time,2.1,RFC 3995
notify-printer-uri,2.1,RFC 3995
notify-sequence-number,2.1,RFC 3995
notify-subscriber-user-name,2.1,RFC 3995
notify-subscription-id,2.1,RFC 3995
Attribute,Min Version,Specification
notify-charset,2.1,RFC 3995
notify-events,2.1,RFC 3995
notify-lease-duration,2.1,RFC 3995
notify-natural-language,2.1,RFC 3995
notify-pull-method,2.1,RFC 3995
notify-time-interval,2.1,RFC 3995
notify-user-data,2.1,RFC 3995
Ron.Bergman | 8 Sep 2008 16:54
Favicon

IPP> Reminder, IPPv2 Conference Call Monday (9/8) <at> 4:00 PM EDT (1:00 PM PDT)


IPPv2 WG Conference Call:

Monday, September 8, 2008, 4:00 PM EDT  (1:00 PM PDT)

Note the NEW Teleconference number and access code.
Contact me if you do not have the new information.

Agenda:
1. Identify Minute Taker
2. Approval of minutes from 8/25 teleconference
3. Review action items.
4. Any new business

Action Items:

1. Text for section 7 (IANA and PWG registrations) Ron & Ira
2. Text for section 9 (Security Considerations) Ron and Ira
3. Discuss Mike Sweet's List of Required Attributes (email dated 9/2/2008)

Whittle, Craig | 8 Sep 2008 23:23
Favicon

IPP> Teleconference minutes posted

All:

 

The minutes from this week's teleconference have been posted (see ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-minutes/IPPv2-ConCall-Minutes-20080908.pdf).

 

Best regards,

 

**CW

 

 

 

Zehler, Peter | 11 Sep 2008 22:38
Picon

PWG-ANNOUNCE> Last Call for MFD specification: Network Scan Service Semantic Model and Service Interface

All,

 

This is the announcement to begin the Last Call process for the "Network Scan Service Semantic Model and Service Interface" specification.  The Last Call will close on October 9. At the upcoming PWG Face to Face in LexingtonKY we will review and resolve all comments during the MFD session.

 

Please review the specification listed below and send comments to the MFD reflector <mailto:mfd <at> pwg.org>.  I will collect the comments for subsequent resolution.

Thanks,

Pete

 

The Last Call version of the "Network Scan Service Semantic Model and Service Interface" specification is now available at:

<ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdscanmodel10-20080911.pdf>

(As usual the .doc version as well as –rev.pdf and –rev.doc are available in the same directory.)

 

 

Peter Zehler

Xerox ResearchCenter Webster
Email: Peter.Zehler <at> 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

 

Zehler, Peter | 11 Sep 2008 23:46
Picon

RE: PWG-ANNOUNCE> Last Call for MFD specification: Network Scan Service Semantic Model and Service Interface

All,

Please also send any comments you have directly to me at the email listed below.

Thanks,

Pete

 

Peter Zehler

Xerox ResearchCenter Webster
Email: Peter.Zehler <at> 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

 

From: owner-pwg-announce <at> pwg.org [mailto:owner-pwg-announce <at> pwg.org] On Behalf Of Zehler, Peter
Sent: Thursday, September 11, 2008 4:38 PM
To: pwg-announce <at> pwg.org
Subject: PWG-ANNOUNCE> Last Call for MFD specification: Network Scan Service Semantic Model and Service Interface

 

All,

 

This is the announcement to begin the Last Call process for the "Network Scan Service Semantic Model and Service Interface" specification.  The Last Call will close on October 9. At the upcoming PWG Face to Face in LexingtonKY we will review and resolve all comments during the MFD session.

 

Please review the specification listed below and send comments to the MFD reflector <mailto:mfd <at> pwg.org>.  I will collect the comments for subsequent resolution.

Thanks,

Pete

 

The Last Call version of the "Network Scan Service Semantic Model and Service Interface" specification is now available at:

<ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdscanmodel10-20080911.pdf>

(As usual the .doc version as well as –rev.pdf and –rev.doc are available in the same directory.)

 

 

Peter Zehler

Xerox ResearchCenter Webster
Email: Peter.Zehler <at> 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

 

Jerry Thrasher | 12 Sep 2008 20:58
Favicon

IPP> Status of IPP WG after the October PWG F2F (ON-HOLD!!)


IPP WG interested parties.

So far there have been no volunteers willing to committ to taking on the IPP Working Group
chair position after the current chair leaves at the end of October 2008.

During the Thursday (9/11) PWG Steering Committee conference call, the SC decided that the
IPP Working Group will be put on hold after the October F2F meeting in Lexington if there still
is not a chair (or co-chiars) in place.  This will result in the suspension of ALL work that is currently
being performed by the IPP Working Group.

One option that I'd like to encourage the "regular" IPP WG  participants to consider is the possibility
of a co-chair structure; potentially one member chairing the conference calls and another member
agreeing to run the F2F meeting sessions, either in person or by phone.

Otherwise, the work efforts which have shown to be of interest to more than a few PWG members will
have to be put on hold until the chair position os filled.

Jerry Thrasher
Printer Working Group Chair
Senior Engineer, WW Corporate Standards
Lexmark International Inc.
Ph:859-825-4056, Fax:859-232-7628
Email:thrasher(at)lexmark(dot)com
Ira McDonald | 19 Sep 2008 03:57
Picon

IPP> IPPv2 I18N and Security sections

Hi,

Please see proposed text for IPPv2 Internationalization and Security
sections below and attached.

Cheers,
- Ira

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

--------------------------------------------------------

8. Internationalization Considerations

For interoperability and basic support for multiple languages, IPP/1.1
conforming Printer implementations MUST support the UTF-8 [RFC3629]
encoding of Unicode [UNICODE] [ISO10646].

For interoperability and best practice support for multiple languages,
IPP/2.0 conforming Printer implementations SHOULD support Network
Unicode [RFC5198] - which REQUIRES transmission of well-formed UTF-8
strings and RECOMMENDS transmission of normalized UTF-8 strings in
Normalization Form C (NFC) [UAX15].

NFC is defined as the result of performing Canonical Decomposition (into
base characters and combining marks) followed by Canonical Composition
(into canonical composed characters wherever Unicode has assigned them).

NOTE WELL - Performing normalization on UTF-8 strings received from IPP
clients and subsequently storing the results (e.g., in IPP Job objects)
could cause false negatives in IPP client searches and failed access
(e.g., to IPP Printers with percent-encoded UTF-8 URIs now 'hidden').

9. Security Considerations

For interoperability and basic support for security, IPP/1.1 conforming
Printer implementations SHOULD support TLS/1.0 [RFC2246] with a
mandatory cipher suite of TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA.

For interoperability and better support for security, IPP/2.0 conforming
Printer implementations SHOULD support TLS/1.1 [RFC4346] with a
mandatory cipher suite of TLS_RSA_WITH_3DES_EDE_CBC_SHA.

For interoperability and best practice for security, IPP/2.0 conforming
Printer implementations SHOULD support TLS/1.2 [RFC5246] with a
mandatory cipher suite of TLS_RSA_WITH_AES_128_CBC_SHA.

For interoperability and best practice for security, IPP/2.2 conforming
Printer implementations MUST support TLS/1.2 [RFC5246] with a mandatory
cipher suite of TLS_RSA_WITH_AES_128_CBC_SHA.

10.1 Normative References

[ISO10646] "Information Technology - Universal Multiple-octet Coded
    Character Set (UCS)", ISO/IEC Standard 10646, 2006.

[RFC2246] T.Dierks, C. Allen, "Transport Layer Security 1.0", RFC 2246,
    January 1999, http://www.ietf.org/rfc/rfc2246.txt

[RFC3629] F. Yergeau, "UTF-8 Transformation of ISO 10646", RFC 3629,
    November 2003, http://www.ietf.org/rfc/rfc3629.txt

[RFC4346] T.Dierks, E. Rescorla, "Transport Layer Security 1.1",
    RFC 4346, April 2006, http://www.ietf.org/rfc/rfc4346.txt

[RFC5246] T.Dierks, E. Rescorla, "Transport Layer Security 1.2",
    RFC 5246, August 2008, http://www.ietf.org/rfc/rfc5246.txt

[UAX15] M. Davis, M. Duerst, "Unicode Normalization Forms", Unicode
    Standard Annex 15, March 2008, http://www.unicode.org/reports/tr15/

[UNICODE] M. Davis, et al, "Unicode Standard v5.1.0", Unicode Standard,
    April 2008, http://www.unicode.org/versions/Unicode5.1.0/


8. Internationalization Considerations

For interoperability and basic support for multiple languages, IPP/1.1
conforming Printer implementations MUST support the UTF-8 [RFC3629]
encoding of Unicode [UNICODE] [ISO10646].

For interoperability and best practice support for multiple languages,
IPP/2.0 conforming Printer implementations SHOULD support Network
Unicode [RFC5198] - which REQUIRES transmission of well-formed UTF-8
strings and RECOMMENDS transmission of normalized UTF-8 strings in
Normalization Form C (NFC) [UAX15].

NFC is defined as the result of performing Canonical Decomposition (into
base characters and combining marks) followed by Canonical Composition
(into canonical composed characters wherever Unicode has assigned them).

NOTE WELL - Performing normalization on UTF-8 strings received from IPP
clients and subsequently storing the results (e.g., in IPP Job objects)
could cause false negatives in IPP client searches and failed access
(e.g., to IPP Printers with percent-encoded UTF-8 URIs now 'hidden').


9. Security Considerations

For interoperability and basic support for security, IPP/1.1 conforming
Printer implementations SHOULD support TLS/1.0 [RFC2246] with a
mandatory cipher suite of TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA.

For interoperability and better support for security, IPP/2.0 conforming
Printer implementations SHOULD support TLS/1.1 [RFC4346] with a
mandatory cipher suite of TLS_RSA_WITH_3DES_EDE_CBC_SHA.

For interoperability and best practice for security, IPP/2.0 conforming
Printer implementations SHOULD support TLS/1.2 [RFC5246] with a
mandatory cipher suite of TLS_RSA_WITH_AES_128_CBC_SHA.

For interoperability and best practice for security, IPP/2.2 conforming
Printer implementations MUST support TLS/1.2 [RFC5246] with a mandatory
cipher suite of TLS_RSA_WITH_AES_128_CBC_SHA.


10.1 Normative References


[ISO10646] "Information Technology - Universal Multiple-octet Coded
    Character Set (UCS)", ISO/IEC Standard 10646, 2006.

[RFC2246] T.Dierks, C. Allen, "Transport Layer Security 1.0", RFC 2246,
    January 1999, http://www.ietf.org/rfc/rfc2246.txt


[RFC3629] F. Yergeau, "UTF-8 Transformation of ISO 10646", RFC 3629,
    November 2003, http://www.ietf.org/rfc/rfc3629.txt


[RFC4346] T.Dierks, E. Rescorla, "Transport Layer Security 1.1",
    RFC 4346, April 2006, http://www.ietf.org/rfc/rfc4346.txt


[RFC5246] T.Dierks, E. Rescorla, "Transport Layer Security 1.2",
    RFC 5246, August 2008, http://www.ietf.org/rfc/rfc5246.txt


[UAX15] M. Davis, M. Duerst, "Unicode Normalization Forms", Unicode
    Standard Annex 15, March 2008, http://www.unicode.org/reports/tr15/


[UNICODE] M. Davis, et al, "Unicode Standard v5.1.0", Unicode Standard,
    April 2008, http://www.unicode.org/versions/Unicode5.1.0/


Ron.Bergman | 19 Sep 2008 22:41
Favicon

IPP> Reminder: IPPv2 Teleconference Monday, September 22 at 4:00PM EDT


IPPv2 WG Conference Call:

Monday, September 22, 2008, 4:00 PM EDT  (1:00 PM PDT)

Note the NEW Teleconference number and access code.
Contact me if you do not have the new information.

Agenda:
1. Identify Minute Taker
2. Approval of minutes from 9/8 teleconference
3. Review action items.
4. Review changes in updated document.
    ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-wd/wd-ippv2-spec20-20080919.pdf
(.doc)
  a pdf showing revisions is also available at:
    ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-wd/wd-ippv2-spec20-20080919-rev.pdf
5. Any new business

Action Items:

1. Text for section 7 (IANA and PWG registrations) - Ron & Ira
2. Text for section 9 (Security Considerations) - Ron and Ira
3. New text for section 8 (Internationalization) - Ira
4. List of Required Attributes to be added to section 6 - Ron
5. List of optional attributes that may become required - Mike

Whittle, Craig | 22 Sep 2008 23:58
Favicon

IPP> Teleconference minutes posted

All:

 

The minutes from this week's teleconference have been posted (see ftp://ftp.pwg.org/pub/pwg/ipp/ippv2-minutes/IPPv2-ConCall-Minutes-20080922.pdf).

 

Best regards,

 

**CW

 

 

 


Gmane