I disagree with the progression of IPP V1.1 at this time. I do not believe it
is appropriate to even consider "last call" on this until some time after the
publication of IPP V1.0. Since V1.0 has been approved as an "experimental"
protocol, I would like to get some time on the V1.0 implementations to see what
we have learned before we go charging off with V1.1. I know some companies have
a misguided belief that everything must be standards track before they implement
it; however, that is clearly not a concern of this group or of the IETF in
general. Rather than churning version after version of IPP for everything
little thing we learn (because we are in such a hurry for a standards track
document), let's take a deep breath and measure our success with V1.0 and then
take the time to do V1.1 right and include that learning.
Bottom line... let's put V1.1 on the shelf for a bit before we push it through
the IETF process.
**********************************************
* Don Wright don at lexmark.com *
* Director, Strategic & Technical Alliances *
* Lexmark International *
* 740 New Circle Rd *
* Lexington, Ky 40550 *
* 606-232-4808 (phone) 606-232-6740 (fax) *
**********************************************
cmanros%cp10.es.xerox.com at interlock.lexmark.com on 03/02/99 03:05:12 PM
To: ipp%pwg.org at interlock.lexmark.com
cc: moore%CS.UTK.EDU at interlock.lexmark.com, paf%swip.net at interlock.lexmark.com
(bcc: Don Wright/Lex/Lexmark)
Subject: IPP> ADM - IPP Working Group Last Call for "Internet Printing Protocol
/1.1 - Model and Semantics" and the "Internet Printing Protocol/1.1 - Enc
oding and Transport"
All,
This is a working group Last Call for the "Internet Printing Protocol/1.1 -
Model and Semantics" and the "Internet Printing Protocol/1.1 - Encoding and
Transport". Versions of these documents have been forwarded to the Internet
Draft directory as <draft-ietf-ipp-model-v11-01.txt> and
<draft-ietf-ipp-protocol-v11-00.txt>.
PDF and Word versions of the drafts are also posted at the ietf-ipp web
site:
ftp://ftp.pwg.org/pub/pwg/ipp/
The Last Call notice follows:
This is a formal request for final comments within the IETF IPP
working group for two documents. The documents are "Internet Printing
Protocol/1.1 - Model and Semantics" and the "Internet Printing Protocol/1.1
- Encoding and Transport" which are being proposed for forwarding on to the
IESG for consideration as Standards Track RFCs. This is a working group
product, which has been thoroughly discussed since mid 1998.
The document has undergone considerable review and revisions during the past
month and I believe that we now have working group consensus on its
adequacy.
The purpose of a working group Last Call is in the style of "speak now or
forever hold your peace" in case there are fundamental objections which have
not gotten previous or adequate discussion, or minor errors which need
correction.
Last Calls are for a minimum of 2 weeks. To give ample time for comments
from our Bake-off meeting on March 9-12 and the IETF-44 meeting on March
15-19, the period for working group comments will close on Friday, 19 March
(US Pacific time reference).
The relevant documents are:
Title : Internet Printing Protocol/1.1: Model and
Semantics
Author(s) : R. de Bry, T. Hastings, R. Herriot,
S. Isaacson, P. Powell
Filename : draft-ietf-ipp-model-v11-01.txt
Pages : 165
Date : 25-Feb-99
This document is one of a set of documents, which together describe all
aspects of a new Internet Printing Protocol (IPP). IPP is an
application level protocol that can be used for distributed printing
using Internet tools and technologies. This document describes a
simplified model consisting of abstract objects, their attributes, and
their operations that is independent of encoding and transport. The
model consists of a Printer and a Job object. A Job optionally supports
multiple documents. IPP 1.1 semantics allow end-users and operators to
query printer capabilities, submit print jobs, inquire about the status
of print jobs and printers, cancel, hold, release, and restart print
jobs. IPP 1.1 semantics allow operators to pause, resume, and purge
(jobs from) Printer objects. This document also addresses security,
internationalization, and directory issues.
Title : Internet Printing Protocol/1.1: Encoding and
Transport
Author(s) : R. Herriot, S. Butler, P. Moore,
R. Turner, J. Wenn
Filename : draft-ietf-ipp-protocol-v11-00.txt
Pages : 34
Date : 22-Feb-99
This document is one of a set of documents, which together describe all
aspects of a new Internet Printing Protocol (IPP). IPP is an application
level protocol that can be used for distributed printing using Internet
tools and technologies. This document defines the rules for encoding IPP
operations and IPP attributes into a new Internet mime media type called
'application/ipp'. This document also defines the rules for
transporting over HTTP a message body whose Content-Type is
'application/ipp'. This document defines a new scheme named 'ipp' for
identifying IPP printers and jobs. Finally, this document defines rules
for supporting IPP/1.0 clients
For retrieval:
URLs for these Internet-Drafts are:
http://www.ietf.org/internet-drafts/draft-ietf-ipp-model-v11-01.txthttp://www.ietf.org/internet-drafts/draft-ietf-ipp-protocol-v11-00.txt
Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
"get draft-ietf-ipp-protocol-v11-00.txt".
A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
Internet-Drafts can also be obtained by e-mail.
Send a message to:
mailserv at ietf.org.
In the body type:
"FILE /internet-drafts/draft-ietf-ipp-protocol-v11-00.txt".
NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Different MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.
Sincerely,
Carl-Uno Manros
Principal Engineer - Xerox Architecture Center - Xerox Corporation
701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
Phone +1-310-333 8273, Fax +1-310-333 5514
Email: manros at cp10.es.xerox.com