| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 12:42:18 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=dQykzUNKRipPFD5PrYS5e2VDbZ7cPN7f64AstISfAMI-1760186538-1.0.1.1-wElLtVGc1TuNWQvdYsUnLEBTnn0BAInVhE2y.PF9cWLgPWJmapVqFLoiAUXriHFrWG0BiXRuE9SU3cQlmvMSxxZHpQvLbMprDdBI03PEm8A; path=/; expires=Sat, 11-Oct-25 13:12:18 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ce6fc03b2cc1c7-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 38 » RFC Editor
Search RFCs
RFC 38
Comments on Network Protocol from NWG/RFC #36, March 1970
- File formats:
- Status:
- UNKNOWN
- Author:
- S.M. Wolfe
- Stream:
- [Legacy]
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC0038
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 38
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