| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 15:40:25 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=OJYFVI9JwRvLVpTI.IXyDKSUrnRkUVfeECsfo.ZedhU-1760197225-1.0.1.1-cOMsiJ2wHuKzNyV_emhZ.Nfeg6j5McZjhW9Dm4DfV.k7nViL4rZ8mlhDtmB5BqjHuZNIJdm00EbvL6oyouoP23ewBDf7ayTXtIH8zsnWq3M; path=/; expires=Sat, 11-Oct-25 16:10:25 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cf74a9ea852ffb-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 3378 » RFC Editor
Search RFCs
RFC 3378
EtherIP: Tunneling Ethernet Frames in IP Datagrams, September 2002
- File formats:
- Status:
- INFORMATIONAL
- Authors:
- R. Housley
S. Hollenbeck - Stream:
- [Legacy]
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3378
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 3378
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