RFC 3378: EtherIP: Tunneling Ethernet Frames in IP Datagrams
In plain English — editorial summary, not part of the RFC
This document describes EtherIP, an early tunneling protocol, to provide informational and historical context for the assignment of IP protocol 97. EtherIP tunnels Ethernet and IEEE 802.3 media access control frames in IP datagrams so that non-IP traffic can traverse an IP internet. The protocol is very lightweight, and it does not provide protection against infinite loops.
Document record
- Document ID
- RFC3378
- Published
- September 2002
- Authors
- R. Housley; S. Hollenbeck
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3387Considerations from the Service Management Research Group (SMRG) on Quality of Service (QoS) in the IP NetworkCurrent
October 2002
- RFC 3330Special-Use IPv4 AddressesObsoleted
October 2002
- RFC 3021Using 31-Bit Prefixes on IPv4 Point-to-Point LinksCurrent
December 2000
- RFC 2917A Core MPLS IP VPN ArchitectureCurrent
September 2000
- RFC 2764A Framework for IP Based Virtual Private NetworksCurrent
February 2000
- RFC 2638A Two-bit Differentiated Services Architecture for the InternetCurrent
July 1999
- RFC 2523Photuris: Extended Schemes and AttributesCurrent
March 1999
- RFC 2522Photuris: Session-Key Management ProtocolCurrent
March 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?