IPP> RFC 2910 on IPP/1.1: Encoding and Transport

IPP> RFC 2910 on IPP/1.1: Encoding and Transport

IPP> RFC 2910 on IPP/1.1: Encoding and Transport

RFC Editor rfc-ed at ISI.EDU
Wed Oct 4 18:39:16 EDT 2000

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

        RFC 2910

        Title:	    Internet Printing Protocol/1.1: Encoding and
        Author(s):  R. Herriot, S. Butler, P. Moore, R. Turner,
                    J. Wenn 
        Status:     Standards Track 
	Date:       September 2000
        Mailbox:    Robert.Herriot at pahv.xerox.com, sbutler at boi.hp.com,
                    pmoore at peerless.com, jwenn at cp10.es.xerox.com
        Pages:      46
        Characters: 100599
        Obsoletes:  2565

        I-D Tag:    draft-ietf-ipp-protocol-v11-06.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2910.txt

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 Hypertext Transfer Protocol (HTTP) a
message body whose Content-Type is "application/ipp".  This document
defines a new scheme named 'ipp' for identifying IPP printers and

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

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.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the Ipp mailing list