| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 09:53:02 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=7X9yHn9q9NlPTrqFr27gO1tOPMo5ngiPCd371C7ha2Y-1760176382-1.0.1.1-NUsUHvsRRFLsG.oEcHGM1n1VW0wlNMRcav3aSU00BEPlinT7MO8h2zi8gzM77GshR1hz56r_dLCO0afCUqkHw.LWsekr4kGR99fAlKxB.1E; path=/; expires=Sat, 11-Oct-25 10:23:02 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd77d17d53f470-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 768 » RFC Editor
Search RFCs
- File formats:
- Status:
- INTERNET STANDARD
- Updated by:
- RFC 9868
- Author:
- J. Postel
- Stream:
- [Legacy]
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC0768
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 768
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