RFC 1413: Identification Protocol
In plain English — editorial summary, not part of the RFC
The Identification Protocol was formerly called the Authentication Server Protocol. It has been renamed to better reflect its function. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1413
- Published
- February 1993
- Authors
- M. St. Johns
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
- Obsoletes:
- RFC 931
Topics
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)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1353Definitions of Managed Objects for Administration of SNMP PartiesCurrent
July 1992
- RFC 1352SNMP Security ProtocolsCurrent
July 1992
- RFC 1351SNMP Administrative ModelCurrent
July 1992
- RFC 1828IP Authentication using Keyed MD5Current
August 1995
- RFC 1928SOCKS Protocol Version 5Current
March 1996
- RFC 1929Username/Password Authentication for SOCKS V5Current
March 1996
- RFC 1938A One-Time Password SystemObsoleted
May 1996
- RFC 2065Domain Name System Security ExtensionsObsoleted
January 1997
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?