RFC 1529: Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Administrative Policies
In plain English — editorial summary, not part of the RFC
This document defines the administrative policies for the operation of remote printer facilities within the context of the tpc.int subdomain. The document describes different approaches to resource recovery for remote printer server sites and includes discussions of issues pertaining to auditing, security, and denial of access. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1529
- Published
- October 1993
- Authors
- C. Malamud; M. Rose
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
- Obsoletes:
- RFC 1486
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 1486 (1993)
- RFC 1528 (1993)
- RFC 1529 (1993)
- RFC 9121 (2023) ✓
Read the full history of Deprecating Infrastructure "int" Domains →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1528Principles of Operation for the TPC.INT Subdomain: Remote Printing -- Technical ProceduresObsoleted
October 1993
- RFC 1530Principles of Operation for the TPC.INT Subdomain: General Principles and PolicyCurrent
October 1993
- RFC 1314A File Format for the Exchange of Images in the InternetCurrent
April 1992
- RFC 2301File Format for Internet FaxObsoleted
March 1998
- RFC 2304Minimal FAX address format in Internet MailObsoleted
March 1998
- RFC 2532Extended Facsimile Using Internet MailCurrent
March 1999
- RFC 3192Minimal FAX address format in Internet MailCurrent
October 2001
- RFC 3249Implementers Guide for Facsimile Using Internet MailCurrent
September 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?