EtherIP: Tunneling Ethernet Frames in IP Datagrams
draft-housley-etherip-04

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3378.
Authors Russ Housley , Scott Hollenbeck
Last updated 2015-10-14 (Latest revision 2002-07-29)
RFC stream Legacy
Intended RFC status Informational
Formats
txt htmlized bibtex bibxml
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3378 (Informational)
Action Holders
(None)
Telechat date (None)
Responsible AD Dr. Thomas Narten
IESG note
Send notices to <housley@vigilsec.com>
Email authors IPR References Referenced by Nits Search email archive
draft-housley-etherip-04 
A new Request for Comments is now available in online RFC libraries.

        RFC 3378

        Title:      EtherIP: Tunneling Ethernet Frames in IP Datagrams
        Author(s):  R. Housley, S. Hollenbeck
        Status:     Informational
        Date:       September 2002
        Mailbox:    rhousley@rsasecurity.com, shollenbeck@verisign.com
        Pages:      9
        Characters: 18803
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-housley-etherip-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3378.txt

This document describes the 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.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.