|
|
|
|
|
|
|
|
|
|
| Last Update: May 26, 2010
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC3549
07/2003
(33 p.)
pdf(2p)
|
J. Salim
H. Khosravi
A. Kleen
A. Kuznetsov |
|
Linux Netlink as an IP Services Protocol |
|
This document describes Linux Netlink, which is used in Linux both as
an intra-kernel messaging system as well as between kernel and user
space. The focus of this document is to describe Netlink's
functionality as a protocol between a Forwarding Engine Component
(FEC) and a Control Plane Component (CPC), the two components that
define an IP service. As a result of this focus, this document
ignores other uses of Netlink, including its use as a intra-kernel
messaging system, as an inter-process communication scheme (IPC), or
as a configuration tool for other non-networking or non-IP network
services (such as decnet, etc.).
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC3654
11/2003
(18 p.)
pdf(2p)
|
H. Khosravi
T. Anderson |
|
Requirements for Separation of IP Control and Forwarding |
|
This document introduces the Forwarding and Control Element
Separation (ForCES) architecture and defines a set of associated
terminology. This document also defines a set of architectural,
modeling, and protocol requirements to logically separate the control
and data forwarding planes of an IP (IPv4, IPv6, etc.) networking
device.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC5810
03/2010
(124 p.)
pdf(2p)
|
A. Doria
J. Hadi Salim
R. Haas
H. Khosravi
W. Wang
L. Dong
R. Gopal
J. Halpern |
|
Forwarding and Control Element Separation (ForCES) Protocol Specification |
|
This document specifies the Forwarding and Control Element Separation
(ForCES) protocol. The ForCES protocol is used for communications
between Control Elements (CEs) and Forwarding Elements (FEs) in a
ForCES Network Element (ForCES NE). This specification is intended
to meet the ForCES protocol requirements defined in RFC 3654.
Besides the ForCES protocol, this specification also defines the
requirements for the Transport Mapping Layer (TML).
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5812
03/2010
(134 p.)
pdf(2p)
|
J. Halpern
J. Hadi Salim |
|
Forwarding and Control Element Separation (ForCES) Forwarding Element Model |
|
This document defines the forwarding element (FE) model used in the
Forwarding and Control Element Separation (ForCES) protocol. The
model represents the capabilities, state, and configuration of
forwarding elements within the context of the ForCES protocol, so
that control elements (CEs) can control the FEs accordingly. More
specifically, the model describes the logical functions that are
present in an FE, what capabilities these functions support, and how
these functions are or can be interconnected. This FE model is
intended to satisfy the model requirements specified in RFC 3654.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5813
03/2010
(17 p.)
pdf(2p)
|
R. Haas |
|
Forwarding and Control Element Separation (ForCES) MIB |
|
This memo defines a Management Information Base (MIB) module for use
with network management protocols in the Internet community. In
particular, it defines managed objects for the Forwarding and Control
Element Separation (ForCES) Network Element (NE).
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
