RFC 8014: An Architecture for Data-Center Network Virtualization over Layer 3 (NVO3)
In plain English — editorial summary, not part of the RFC
This document presents a high-level overview architecture for building data-center Network Virtualization over Layer 3 (NVO3) networks. The architecture is given at a high level, showing the major components of an overall system. An important goal is to divide the space into individual smaller components that can be implemented independently with clear inter-component interfaces and interactions. It should be possible to build and implement individual components in isolation and have them interoperate with other independently implemented components. That way, implementers have flexibility in implementing individual components and can optimize and innovate within their respective components without requiring changes to other components.
Document record
- Document ID
- RFC8014
- Published
- December 2016
- Authors
- D. Black; J. Hudson; L. Kreeger; M. Lasserre; T. Narten
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8012Label Switched Path (LSP) and Pseudowire (PW) Ping/Trace over MPLS Networks Using Entropy Labels (ELs)Current
November 2016
- RFC 8024Multi-Chassis Passive Optical Network (MC-PON) Protection in MPLSCurrent
November 2016
- RFC 8001RSVP-TE Extensions for Collecting Shared Risk Link Group (SRLG) InformationCurrent
January 2017
- RFC 8029Detecting Multiprotocol Label Switched (MPLS) Data-Plane FailuresUpdated
March 2017
- RFC 8036Applicability Statement for the Routing Protocol for Low-Power and Lossy Networks (RPL) in Advanced Metering Infrastructure (AMI) NetworksCurrent
January 2017
- RFC 7988Ingress Replication Tunnels in Multicast VPNUpdated
October 2016
- RFC 7987IS-IS Minimum Remaining LifetimeCurrent
October 2016
- RFC 8042OSPF Two-Part MetricCurrent
December 2016
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?