Overlay Management Protocol
draft-sthoria-omp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Samir Thoria , Satish Mahadevan , Prab Radhakrishnan | ||
| Last updated | 2024-02-02 (Latest revision 2023-08-01) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes Cisco's Overlay Management Protocol (OMP). OMP is a routing information management and distribution protocol that enables overlay networks by separating service from transport. OMP is closely modeled and related to BGP. Primary usage for OMP is in Software Defined Networks, where all the routers are in the same administrative domain. OMP is used as the routing protocol in Cisco's Software Defined WAN (SD-WAN) solution.
Authors
Samir Thoria
Satish Mahadevan
Prab Radhakrishnan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)