rfc1528.txt
来自「RFC 的详细文档!」· 文本 代码 · 共 675 行 · 第 1/2 页
TXT
675 行
RFC 1528 Remote Printing -- Technical Procedures October 1993
4.2 Implicit Cover Sheet
To:remote-printer.Arlington_Hewes/Room_403@0.1.5.2.8.6.9.5.1.4.1.tpc.int
cc: Marshall Rose <mrose@dbc.mtview.ca.us>
From: Carl Malamud <carl@malamud.com>
Date: Thu, 22 Jul 1993 08:38:00 -0800
Subject: Second example
Message-ID: <19930722163800.2@malamud.com>
MIME-Version: 1.0
Content-Type: application/postscript
%!
Note that in this latter example, both remote printing and e-mail
recipients can be identified in the same message.
4.3 Minimal, Text-only
To:remote-printer.Arlington_Hewes/Room_403@0.1.5.2.8.6.9.5.1.4.1.tpc.int
cc: Marshall Rose <mrose@dbc.mtview.ca.us>
From: Carl Malamud <carl@malamud.com>
Date: Thu, 22 Jul 1993 08:38:00 -0800
Subject: Third example
Message-ID: <19930722163800.3@malamud.com>
Here are my comments...
5. Prototype Implementation
A prototype implementation is openly available. The MIME
instructions for retrieval are:
Malamud & Rose [Page 7]
RFC 1528 Remote Printing -- Technical Procedures October 1993
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----- =_aaaaaaaaaa0"
Content-Description: pointers to ftp and e-mail access
------- =_aaaaaaaaaa0
Content-Type: message/external-body;
access-type="mail-server";
server="archive-server@ftp.ics.uci.edu"
Content-Type: application/octet-stream; type="tar";
x-conversions="x-compress"
Content-ID: <4599.735726126.1@dbc.mtview.ca.us>
mimesend mrose/tpc/rp.tar.Z
------- =_aaaaaaaaaa0
Content-Type: message/external-body;
access-type="anon-ftp"; name="rp.tar.Z";
directory="mrose/tpc"; site="ftp.ics.uci.edu"
Content-Type: application/octet-stream; type="tar";
x-conversions="x-compress"
Content-ID: <4599.735726126.2@dbc.mtview.ca.us>
------- =_aaaaaaaaaa0--
This package contains software for UNIX-based systems, and was
developed and tested under SunOS, with an openly-available facsimile
package (Sam Leffler's FlexFAX package), and contains information for
sites acting as either client or server participants, and zone
administrators.
Malamud & Rose [Page 8]
RFC 1528 Remote Printing -- Technical Procedures October 1993
6. Future Issues
Note that several issues are not addressed, e.g.,
o determining which content-types and character sets are
supported by a remote printer server;
o introduction of authentication, integrity, privacy,
authorization, and accounting services;
o preferential selection of a remote printer server; and,
o aggregation of multiple print recipients in a single
message.
Subsequent work might consider these issues in detail.
7. Security Considerations
Internet mail may be subject to monitoring by third parties, and in
particular, message relays.
8. Acknowledgements
This document is based on RFC 1486, "An Experiment in Remote
Printing".
9. References
[1] Crocker, D., "Standard for the Format of ARPA Internet Text
Messages", STD 11, RFC 822, UDEL, August 1982.
[2] Partridge, C., "Mail Routing and the Domain System" STD 14, RFC
974, CSNET CIC BBN, January 1986.
[3] Mockapetris, P., "Domain Names -- Concepts and Facilities", STD
13, RFC 1034, USC/Information Sciences Institute, November 1987).
[4] Mockapetris, P., "Domain Names -- Implementation and
Specification", STD 13, RFC 1035, USC/Information Sciences
Institute, November 1987.
[5] Borenstein, N., and N. Freed, "MIME (Multipurpose Internet Mail
Extensions) Part One: Mechanisms for Specifying and Describing
the Format of Internet Message Bodies", RFC 1521, Bellcore,
Innosoft, September 1993.
Malamud & Rose [Page 9]
RFC 1528 Remote Printing -- Technical Procedures October 1993
10. Authors' Addresses
Carl Malamud
Internet Multicasting Service
Suite 1155, The National Press Building
Washington, DC 20045
US
Phone: +1 202 628 2044
Fax: +1 202 628 2042
Email: carl@malamud.com
Marshall T. Rose
Dover Beach Consulting, Inc.
420 Whisman Court
Mountain View, CA 94043-2186
US
Phone: +1 415 968 1052
Fax: +1 415 968 2510
Email: mrose@dbc.mtview.ca.us
Malamud & Rose [Page 10]
RFC 1528 Remote Printing -- Technical Procedures October 1993
Appendix A. The application/remote-printing Content-Type
(1) MIME type name: application
(2) MIME subtype name: remote-printing
(3) Required parameters: none
(4) Optional parameters: none
(5) Encoding considerations: 7bit preferred
(6) Security considerations: none
(7) Specification:
The "application/remote-printing" content-type contains originator
and recipient information used when generating a cover-sheet. Using
the ABNF notation of RFC 822, the syntax for this content is:
<content> ::= <recipient-info> CRLF
<originator-info>
[CRLF <cover-info>]
<recipient-info> ::= "Recipient" ":" <value> CRLF
<address-info>
<originator-info> ::= "Originator" ":" <value> CRLF
<address-info>
<address-info> ::= ["Title" ":" <value> CRLF]
["Department" ":" <value> CRLF]
["Organization" ":" <value> CRLF]
["Mailstop" ":" <value> CRLF]
["Address" ":" <value> CRLF]
["Telephone" ":" <value> CRLF]
"Facsimile" ":" <value> CRLF
["Email" ":" <value> CRLF]
<value> ::= *text
[CRLF LWSP-char <value> ]
<cover-info> ::= *(*text CRLF)
Note that the value of the "Email" field is an RFC 822 mailbox
address.
Malamud & Rose [Page 11]
RFC 1528 Remote Printing -- Technical Procedures October 1993
Appendix B. The image/tiff Content-Type
(1) MIME type name: image
(2) MIME subtype name: tiff
(3) Required parameters: none
(4) Optional parameters: none
(5) Encoding considerations: base64
(6) Security considerations: none
(7) Published specification: TIFF class F, as defined in:
Tag Image File Format (TIFF) revision 6.0
Developer's Desk
Aldus Corporation
411 First Ave. South
Suite 200
Seattle, WA 98104
206-622-5500
Malamud & Rose [Page 12]
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?