CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 02:49:36 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=ual59vj69td4aihh2meapfmi5u; path=/
set-cookie: __cf_bm=ElepIM5IPEKSuSTPGIfrKWIsit4v.fuRHH6sGSCPwfI-1759978176-1.0.1.1-V.JFxoVvEFIpbDsOHT8yoCSSgZn4onSrhEUmnzLtX1EzqEsyB8Siyz.gx3SGGaWi3uJHFOUTADR5E1JMporDf1GA0aOBSHq.4ccwIRoSIzc; path=/; expires=Thu, 09-Oct-25 03:19:36 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 98ba90ba39f6c16d-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Area Assignment: tsv
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
RFC 793, "Transmission Control Protocol", September 1981
Note: This RFC has been obsoleted by RFC 9293
Note: This RFC has been updated by RFC 1122, RFC 3168, RFC 6093, RFC 6528
Source of RFC: LegacyArea Assignment: tsv
Errata ID: 2297
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Vishwas Manral
Date Reported: 2010-06-03
Held for Document Update by: Wes Eddy
Section 3.8 says:
Any lower level protocol will have to provide the source address, destination address, and protocol fields, and some way to determine the "TCP length", both to provide the functional equivlent service of IP and to be used in the TCP checksum.
It should say:
Any lower level protocol will have to provide the source address, destination address, and protocol fields, and some way to determine the "TCP length", both to provide the functional equivalent service of IP and to be used in the TCP checksum.
Notes:
s/equivlent/equivalent/
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us