A VPN Library for use with the ForCES Protocol and Model
draft-halpern-forces-lfblibrary-vpn-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Joel M. Halpern , Huanyuan Ma | ||
| Last updated | 2007-01-18 | ||
| 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
The forwarding and Control Element Separation (ForCES) protocol defines a standard communication and control mechanism through which a Control Element (CE) can control the behavior of a Forwarding Element (FE). That control is accomplished through manipulating attributes of Logical Function Blocks (LFBs), whose structure is defined in a model RFC produced by the working group. In order to build an actual solution based on this protocol, defining a set of Logical Function Block definitions that can be instantiated by FEs and controlled by CEs is welcome. A base library definition of LFBs is already given in library [5]. VPN (Virtual Private Network) services, as a kind of important services widely employed in Internet, will certainly be implemented in routers using this protocol. This document provides an initial set of VPN LFB definitions in particular, a set of tunnel encapsulator and decapsulator LFBs. It is anticipated that additional VPN-related LFB definitions like L2VPN, L3VPN can be defined over time.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)