RFC 1805: Location-Independent Data/Software Integrity Protocol
In plain English — editorial summary, not part of the RFC
This memo describes a protocol for adding integrity assurance to files that are distributed across the Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1805
- Published
- June 1995
- Authors
- A. Rubin
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 5091Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 CryptosystemsUpdated
December 2007
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 8387Practical Considerations and Implementation Experiences in Securing Smart Object NetworksCurrent
May 2018
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8937Randomness Improvements for Security ProtocolsCurrent
October 2020
- RFC 9323A Profile for RPKI Signed Checklists (RSCs)Current
November 2022
- RFC 9691A Profile for Resource Public Key Infrastructure (RPKI) Trust Anchor Keys (TAKs)Current
December 2024
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?