RFC 1728: Resource Transponders
In plain English — editorial summary, not part of the RFC
This paper describes an automatic mechanism, the resource transponder, for maintaining resource location information. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1728
- Published
- December 1994
- Authors
- C. Weider
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- usv
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1727A Vision of an Integrated Internet Information ServiceCurrent
December 1994
- RFC 2224NFS URL SchemeCurrent
October 1997
- RFC 2079Definition of an X.500 Attribute Type and an Object Class to Hold Uniform Resource Identifiers (URIs)Current
January 1997
- RFC 2141URN SyntaxObsoleted
May 1997
- RFC 2255The LDAP URL FormatObsoleted
December 1997
- RFC 2541DNS Security Operational ConsiderationsObsoleted
March 1999
- RFC 2611URN Namespace Definition MechanismsObsoleted
June 1999
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
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?