IPP> Revised IPP WG Charter - please comment ASAP

Hi folks,                                        Thursday (3 March 2005)

Based on our discussion at today's PWG Steering Committee telecon, I've
revised the proposed PWG IPP WG charter and posted it at:

    ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp-charter-20050303.htm

The significant change is that EVERY revision to an existing IETF or PWG
IPP document or development of a new IETF or PWG IPP document requires a
work item has first been approved by the PWG Steering Committee (in
response to Lee Farrell's excellent criticism of the previous draft).

The PWG Steering Committee should adopt this PWG IPP WG charter at their
next telecon on Thursday (17 March 2005), unless further revisions are
necessary after comments on the IPP mailing list.

Below is some text to justify accelerated adoption of this charter by
PWG Steering Committee variance rather than by PWG Formal Approval.

Comments?

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald <at> sharplabs.com

PWG-ANNOUNCE> Reminder / RSVP - April PWG meeting in Tokyo

PWG-ANNOUNCE> FW: [Printing-sc] FSG OpenPrinting Job Ticket API Version 1.00 - Stable available

_______________________________________________
Printing-sc mailing list
Printing-sc <at> mail.freestandards.org
http://mail.freestandards.org/mailman/listinfo/printing-sc

PWG-ANNOUNCE> RE: Reminder / RSVP - April PWG meeting in Tokyo

IPP> PWG IPP WG Charter - approved by PWG Steering Committee Variance

Hi folks,                                         Friday (18 March 2005)

At yesterday's IEEE/ISTO PWG Steering Committee telecon, the PWG IPP WG
charter was unanimously approved.

The final text is now posted at:

    ftp://ftp.pwg.org/pub/pwg/ipp/charter/ch-ipp-charter-20050317.htm

The significant change is that EVERY revision to an existing IETF or PWG
IPP document or development of a new IETF or PWG IPP spec requires that
a work item has first been approved by the PWG Steering Committee (in
response to Lee Farrell's excellent criticism of earlier drafts).

In conformance with PWG Process/2.0, below is our rationale for approval
of this charter by PWG Steering Committee Variance rather than by PWG
Formal Approval (voting by all PWG members).

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald <at> sharplabs.com
------------------------------------------------------------------------

Rationale for approval of the PWG IPP WG charter by PWG SC Variance:

(1) Over the past eight years the IETF-chartered IPP WG developed IETF
standards-track and informational documents in collaboration with the
IEEE/ISTO Printer Working Group.

(2) Over the past five years the IEEE/ISTO PWG has developed and adopted
seven PWG IPP Candidate Standards (i.e., the 5100.x series).

(3) Therefore, by approving this PWG IPP WG charter, the IEEE/ISTO PWG
Steering Committee is formalizing the existing defacto PWG IPP WG.

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

RE: PWG-ANNOUNCE> RE: Reminder / RSVP - April PWG meeting in Toky o

PWG-ANNOUNCE> Last Call for the Port Monitor MIB

PWG-ANNOUNCE> RFC 3995-3998 - final IETF IPP specs published

Hi folks,

The final four IETF IPP documents were posted yesterday:

3995 Internet Printing Protocol (IPP): Event Notifications and
     Subscriptions. R. Herriot, T. Hastings. March 2005. (Format:
     TXT=223294 bytes) (Updates RFC2911, RFC2910) (Status: PROPOSED
     STANDARD)

3996 Internet Printing Protocol (IPP): The 'ippget' Delivery Method
     for Event Notifications. R. Herriot, T. Hastings, H. Lewis. March
     2005. (Format: TXT=73638 bytes) (Updates RFC2911) (Status: PROPOSED
     STANDARD)

3997 Internet Printing Protocol (IPP): Requirements for IPP
     Notifications. T. Hastings, Ed., R. K. deBry, H. Lewis. March 2005.
     (Format: TXT=38185 bytes) (Status: INFORMATIONAL)

3998 Internet Printing Protocol (IPP): Job and Printer Administrative
     Operations. C. Kugler, H. Lewis, T. Hastings, Ed.. March 2005.
     (Format: TXT=109658 bytes) (Status: PROPOSED STANDARD)

You can fetch them by FTP at:

  ftp://ftp.isi.edu/in-notes/

Thanks to our IETF AD's and the document editors.

Please note the related work-in-progress on an email delivery
method for IPP event notifications in an IEEE/ISTO PWG draft:

  ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-isto-mailto10-20050222.pdf

Cheers,
- Ira

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald <at> sharplabs.com

RFC 3996 on Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications

A new Request for Comments is now available in online RFC libraries.

        RFC 3996

        Title:      Internet Printing Protocol (IPP):
                    The 'ippget' Delivery Method for Event
                    Notifications
        Author(s):  R. Herriot, T. Hastings, H. Lewis
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    bob <at> herriot.com, hastings <at> cp10.es.xerox.com,
                    harryl <at> us.ibm.com
        Pages:      31
        Characters: 73638
        Updates:    2911

        I-D Tag:    draft-ietf-ipp-notify-get-10.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3996.txt

This document describes an extension to the Internet Printing
Protocol 1.1: Model and Semantics (RFC 2911, RFC 2910).  This
document specifies the 'ippget' Pull Delivery Method for use with the
"Internet Printing Protocol (IPP): Event Notifications and
Subscriptions" specification (RFC 3995).  This IPPGET Delivery Method
is REQUIRED for all clients and Printers that support RFC 3995.  The
Notification Recipient, acting as a client, fetches (pulls) Event
Notifications by using the Get-Notifications operation defined in
this document.

This document is a product of the Internet Printing Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

RFC 3997 on Internet Printing Protocol (IPP): Requirements for IPP Notifications

A new Request for Comments is now available in online RFC libraries.

        RFC 3997

        Title:      Internet Printing Protocol (IPP):
                    Requirements for IPP Notifications
        Author(s):  T. Hastings, Ed., R. K. deBry, H. Lewis
        Status:     Informational
        Date:       March 2005
        Mailbox:    hastings <at> cp10.es.xerox.com, debryro <at> uvsc.edu,
                    harryl <at> us.ibm.com
        Pages:      17
        Characters: 38185
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipp-not-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3997.txt

This document is one of a set of documents that together describe
all aspects of the Internet Printing Protocol (IPP).  IPP is an
application-level protocol that can be used for distributed printing
on the Internet.  There are multiple parts to IPP, but the primary
architectural components are the Model, the Protocol, and an interface
to Directory Services.  This document provides a statement of the
requirements for notifications as an optional part of an IPP Service.

This document is a product of the Internet Printing Protocol Working
Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST <at> IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST <at> RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info <at> RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info <at> RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager <at> RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR <at> RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce