ForCES Architectural Framework and FE Functional Model
draft-anderson-forces-model-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Todd A. Anderson | ||
Last updated | 2008-04-16 (Latest revision 2001-11-16) | ||
Replaced by | draft-ietf-forces-model | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-forces-model | |
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 defines an architecture for ForCES network elements and a functional model for ForCES forwarding elements. This model is used to describe the capabilities of ForCES forwarding elements within the context of the ForCES protocol. The architecture and forwarding element model defined herein is intended to satisfy the requirements specified in the ForCES requirements draft [FORCES- REQ].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)