RFC 912: Authentication service
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 931.
Current document in this lineage: RFC 1413 — Identification Protocol
In plain English — editorial summary, not part of the RFC
This memo describes a proposed authentication protocol for verifying the identity of a user of a TCP connection. Given a TCP port number pair, it returns a character string which identifies the owner of that connection on the server's system. Suggested uses include automatic identification and verification of a user during an FTP session, additional verification of a TAC dial up user, and access verification for a generalized network file server.
Document record
- Document ID
- RFC912
- Published
- September 1984
- Authors
- M. St. Johns
- Status
- UNKNOWN
- Stream
- Legacy
- Area
- —
- Pages
- 3
- Also known as
- —
- Obsoleted by:
- RFC 931
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 912 (1984)
- RFC 931 (1985)
- RFC 1413 (1993) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
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?