RFC 7047: The Open vSwitch Database Management Protocol
In plain English — editorial summary, not part of the RFC
Open vSwitch is an open-source software switch designed to be used as a vswitch (virtual switch) in virtualized server environments. A vswitch forwards traffic between different virtual machines (VMs) on the same physical host and also forwards traffic between VMs and the physical network. Open vSwitch is open to programmatic extension and control using OpenFlow and the OVSDB (Open vSwitch Database) management protocol. This document defines the OVSDB management protocol. The Open vSwitch project includes open-source OVSDB client and server implementations.
Document record
- Document ID
- RFC7047
- Published
- December 2013
- Authors
- B. Pfaff; B. Davie
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8763Deployment Considerations for Information-Centric Networking (ICN)Current
April 2020
- RFC 7018Auto-Discovery VPN Problem Statement and RequirementsCurrent
September 2013
- RFC 7086Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)Current
January 2014
- RFC 7729Forwarding and Control Element Separation (ForCES) Logical Functional Block (LFB) Subsidiary ManagementCurrent
December 2015
- RFC 7782Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC AttachmentsCurrent
February 2016
- RFC 5765Security Issues and Solutions in Peer-to-Peer Systems for Realtime CommunicationsCurrent
February 2010
- RFC 8926Geneve: Generic Network Virtualization EncapsulationCurrent
November 2020
- RFC 9386IPv6 Deployment StatusCurrent
April 2023
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?