------_=_NextPart_000_01BE6B89.B6CD2C86
Content-Type: text/plain;
charset="iso-8859-1"
FYI,
Somewhat disappointing that this document, which claims to also cover Print,
has made it all the way to Proposed Standard without any consideration for
IPP or significant input from the IPP WG.
Carl-Uno
-----Original Message-----
From: RFC Editor [mailto:rfc-ed@ISI.EDU]
Sent: Wednesday, March 10, 1999 5:02 PM
Cc: rfc-ed@ISI.EDU
Subject: RFC 2534 on Media Features for Display, Print, and Fax
A new Request for Comments is now available in online RFC libraries.
RFC 2534:
Title: Media Features for Display, Print, and Fax
Author(s): L. Masinter, D. Wing, A. Mutz, K. Holtman
Status: Proposed Standard
Date: March 1999
Mailbox: masinter@parc.xerox.com, dwing@cisco.com,
mutz@alum.mit.edu, koen@win.tue.nl
Pages: 9
Characters: 15466
Updates/Obsoletes/See Also: None
I-D Tag: draft-ietf-conneg-media-features-05.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2534.txt
This specification defines some common media features for
describing image resolution, size, color, and image representation
methods that are common to web browsing, printing, and facsimile
applications.
This document is a product of the Content Negotiation 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@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@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@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@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Alegre Ramos
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_000_01BE6B89.B6CD2C86
Content-Type: message/rfc822
Content-Location: ATT-0-EF19C5B569D7D211A2D200805F15CE85
To:
Subject:
Date: Wed, 10 Mar 1999 22:16:01 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: multipart/mixed;
boundary="----_=_NextPart_002_01BE6B89.B6CD2C86"
------_=_NextPart_002_01BE6B89.B6CD2C86
Content-Type: text/plain
------_=_NextPart_002_01BE6B89.B6CD2C86
Content-Type: application/octet-stream;
name="ATT04503.txt"
Content-Disposition: attachment;
filename="ATT04503.txt"
Content-Location: ATT-0-ED19C5B569D7D211A2D200805F15CE85-A
TT04503.txt
Content-type: message/external-body;
access-type="mail-server";
server="RFC-INFO@RFC-EDITOR.ORG"
Content-Type: text/plain
Content-ID: <990310165834.RFC@RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc2534
------_=_NextPart_002_01BE6B89.B6CD2C86
Content-Type: message/external-body;
site="in-notes";
dir="rfc2534.txt";
mode="ftp.isi.edu";
access-type="anon-ftp"
Content-Location: ATT-1-EE19C5B569D7D211A2D200805F15CE85-r
fc2534.url
------_=_NextPart_002_01BE6B89.B6CD2C86--
------_=_NextPart_000_01BE6B89.B6CD2C86--