[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 3654 on Requirements for Separation of IP Control and Forwarding
A new Request for Comments is now available in online RFC libraries.
Title: Requirements for Separation of IP Control and
Author(s): H. Khosravi, T. Anderson, Eds.
Date: November 2003
I-D Tag: draft-ietf-forces-requirements-10.txt
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.
This document is a product of the Forwarding and Control Element
Separation Working Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.