RFC 1486 (rfc1486) - Page 3 of 14

An Experiment in Remote Printing

RFC 1486           An Experiment in Remote Printing            July 1993


   (3)  With the "application/postscript" content-type, the remote
        printer server should evaluate the contents in a safe execution
        environment.

   (4)  With the "multipart" content-type the subordinate contents will
        be processed recursively: for a "multipart/mixed" or
        "multipart/digest" content, each subordinate content will start
        on a new page, whilst for a "multipart/parallel" content, all
        subordinate contents will, if possible, start on the same page.
        Naturally, when processing a "multipart/alternative" content,
        only one subordinate content will be printed.

   When the remote printer server finishes its processing, a message is
   returned to the originator, indicating either success or failure.

2.1.  Naming, Addressing, and Routing

   A printer is identified by a telephone number which corresponds to a
   G3-facsimile device connected to the international telephone network,
   e.g.,

        +1 415 968 2510

   where "+1" indicates the IDDD country code, and the remaining string
   is a telephone number within that country.  This number is used to
   construct the address of a remote printer server, which forms the
   recipient address for the message, e.g.,

        

   That is, the local-part of the remote printer server's address is
   ALWAYS "remote-printer", and the domain-part is constructed by
   reversing the telephone number, converting each digit to a domain-
   label, and being placed under "tpc.int."

   The message is routed in exactly the same fashion as all other
   electronic mail, i.e., using the MX algorithm [3].  Since a remote
   printer server might be able to access many printers, the wildcarding
   facilities of the DNS [4,5] are used accordingly.  For example, if a
   remote printer server residing at "dbc.mtview.ca.us" was willing to
   access any printer with a telephone number prefix of

        +1 415 968

      then this resource record might be present

        *.8.6.9.5.1.4.1.tpc.int.    IN MX 10 dbc.mtview.ca.us.




Rose & Malamud