INTERNET-DRAFT "Ethernet over UDP/IP", Alexey Eromenko, 2015-12-28, expiration date: 2016-06-28 Intended status: Standards Track A.Eromenko December 2015 Ethernet over UDP/IP Tunnel ============================= Specification draft Abstract This technique is simple to implement, and provides an effective tunnel between two LAN segments (Ethernet Broadcast Domains). Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Introduction In Ethernet-over-UDP, no fragmentation or reassembly occur of the inner traffic. No retransmission or security provided. It was built as a quick and simple way to inter-connect various systems, and it is intended where maximum performance and simplicity required. It is very effective tunnel for both legacy software, which requires non-IP protocols, such as NETBIOS or IPX/SPX, as well as for development of new network protocols. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 4| Source UDP port | Destination UDP port | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 8| UDP Length | UDP checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +++ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 12| Destination MAC Address | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 16| | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 20| Source MAC Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 22| EtherType or Length | Data... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ . . . . Data... . . . +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 26| Frame Check Sequence | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (bytes) There is no "default UDP port" to listen to incoming sessions, and it must be manually configured by the admin. This protocol adds 26 bytes of overhead. Implementations Multiple inter-operable Open-Source implementations exist, including VirtualBox, Qemu/KVM and Virtual Distributed Ethernet (VDE). Security Considerations Traffic sent over a UDP Tunnel is not encrypted. When using on the public Internet, you can either encrypt it on the outter network level (with IPsec or SSH), or use encrypted protocols in the inner network (TLS or SSH). The security properties are similar to Ethernet. Author Contacts Alexey Eromenko Israel Skype: Fenix_NBK_ EMail: al4321@gmail.com Facebook: https://www.facebook.com/technologov INTERNET-DRAFT Alexey expiration date: 2016-06-28