A Data Model for Network Instances in Service Provider Networks
draft-openconfig-rtgwg-network-instance-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Rob Shakir | ||
| Last updated | 2016-05-06 (Latest revision 2015-11-03) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-openconfig-rtgwg-network-instance-01.txt
Abstract
This document defines a YANG data model for configuring and managing forwarding instances on a network device - focused primarily on deployments in service provider networks. The model is vendor- neutral and based on operational requirements expressed by operators. A 'network instance' is defined to be a discrete forwarding table on a network element, which contains Layer 3 and/or Layer 2 forwarding entries. Each network instance may instantiate its own sets of protocols which control installation of forwarding entries into one or more tables (which may be Layer 2 FIBs, or Layer 3 RIBs).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)