CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 21:33:23 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
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
set-cookie: __cf_bm=yQuVeOEPCzW270G0_QzGS1rhxyAJcKmGJfn.GuLeFyY-1760045603-1.0.1.1-E8R0c2eqUdAIHTLe2xlco_7ycPdTRXTjp7dWs0XGYhN8SLgYzKebbXnGtURs.4Fw2Tuicp9D2mIsGZNPW14WMryTl6VCVoHBzWyDvtgiWoE; path=/; expires=Thu, 09-Oct-25 22:03:23 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c0fefa0b08a403-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2525 » RFC Editor
Search RFCs
RFC 2525
Known TCP Implementation Problems, March 1999
- File formats:
- Status:
- INFORMATIONAL
- Authors:
- V. Paxson
M. Allman
S. Dawson
W. Fenner
J. Griner
I. Heavens
K. Lahey
J. Semke
B. Volz - Stream:
- IETF
- Source:
- tcpimpl (tsv)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2525
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 2525
Abstract
This memo catalogs a number of known TCP implementation problems. This memo provides information for the Internet community.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us