Commit 04a2cdc2 authored by Martin Stiemerling's avatar Martin Stiemerling 💬
Browse files

A bit more stuff about information models

still not yet there.
parent bb55dc33
Pipeline #68680 passed with stage
in 12 seconds
# Yang Models
## Abstraction of Network Elements
There are various network elements in different "flavors" mentioned in the introduction to this memo. We propose two basic types for our discussion here in order to have to concrete examples:
* a FreeBSD-based software router on a commercial off-the-shelf (COTS) PC
* and an Arista-based hardware switch, e.g., a DCS-7050TX-48.
Both are different network elements, e.g.:
* the software router does forwarding of packets in software vs. the Arista does forwarding in specialized forwarding hardware
* the software router is a server-based element vs. the Arista is a special-build element.
Nonetheless both share network concepts, for instance:
* interfaces: both type have hardware interfaces, but packet processing is handled differently (e.g., packets are passed to the operating system on PC-based systems while on a switch packets are in most cases handled in hardware)
* forwarding: forwarding of packets has to be performed in both types
* routing: selection of a routing protocol and determination of the necessary parameters.
This leads to the fact that one can create an information model of a network element, based on the building blocks of a specific network element. The information model would define that a network element has 1 to n interfaces, where an interface has a name, an identifier, a hardware-address, 0 to m IP addresses etc.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment