RFC 1936: Implementing the Internet Checksum in Hardware
In plain English — editorial summary, not part of the RFC
This memo presents a techniques for efficiently implementing the Internet Checksum in hardware. It includes PLD code for programming a single, low cost part to perform checksumming at 1.26 Gbps. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1936
- Published
- April 1996
- Authors
- J. Touch; B. Parham
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 7663Report from the IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI)Current
October 2015
- RFC 1858Security Considerations for IP Fragment FilteringUpdated
October 1995
- RFC 2053The AM (Armenia) DomainCurrent
October 1996
- RFC 2197SMTP Service Extension for Command PipeliningObsoleted
September 1997
- RFC 2229A Dictionary Server ProtocolCurrent
October 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?