Forwarded one more time, now with correct subject
Carl-Uno Manros
10701 S Eastern Ave #1117
Henderson, NV 89052, USA
Tel +1-702-617-9414
Fax +1-702-617-9417
Mob +1-702-525-0727
Email carl at manros.com
Message-Id: <200210022253.g92MrkD13454 at gamma.isi.edu>
To: IETF-Announce: ;
Subject: RFC 3381 on Internet Printing Protocol (IPP): Job Progress
Attributes
Cc: rfc-editor at rfc-editor.org, ipp at pwg.org
From: rfc-editor at rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 02 Oct 2002 15:53:46 -0700
Sender: rfc-ed at ISI.EDU
--NextPart
A new Request for Comments is now available in online RFC libraries.
RFC 3381
Title: Internet Printing Protocol (IPP): Job Progress
Attributes
Author(s): T. Hastings, H. Lewis, R. Bergman
Status: Standards Track
Date: September 2002
Mailbox: hastings at cp10.es.xerox.com, harryl at us.ibm.com,
rbergma at hitachi-hkis.com
Pages: 16
Characters: 34859
Updates: 2910
I-D Tag: draft-ietf-ipp-job-prog-03.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3381.txt
This document defines four new Job Description attributes for
monitoring job progress to be registered as OPTIONAL extensions to the
Internet Printing Protocol (IPP/1.0 and IPP/1.1). These attributes
are drawn from the PWG Job Monitoring MIB. This document also defines
a new "sheet-collate" Job Template attribute to control sheet
collation and to help with the interpretation of the job progress
attributes.
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.echo
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.
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
--OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="RFC-INFO at RFC-EDITOR.ORG"
Content-Type: text/plain
Content-ID: <021002155058.RFC at RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc3381
--OtherAccess
Content-Type: Message/External-body;
name="rfc3381.txt";
site="ftp.isi.edu";
access-type="anon-ftp";
directory="in-notes"
Content-Type: text/plain
Content-ID: <021002155058.RFC at RFC-EDITOR.ORG>
--OtherAccess--
--NextPart--