| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 09:56:03 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=6B.L.YNQua1UjSlN9_hd4JyHADTmXsIQRNBYCn9wrT4-1760176563-1.0.1.1-zMP77pkbhe0pUVddMg2HE67b._ISHtLape9eY6P77ltB8rUKid9nI9gVzPEhXCozGUGweBwl2j.AcsfPenos9UUdMS_a7uCpjv0B_1a7D7s; path=/; expires=Sat, 11-Oct-25 10:26:03 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd7c3d1d32a45e-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 2775 » RFC Editor
Search RFCs
RFC 2775
Internet Transparency, February 2000
- File formats:
- Status:
- INFORMATIONAL
- Author:
- B. Carpenter
- Stream:
- [Legacy]
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC2775
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 2775
Abstract
This document describes the current state of the Internet from the architectural viewpoint, concentrating on issues of end-to-end connectivity and transparency.
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