Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Requirements for Separation of IP Control and Forwarding (RFC3654)

IP.com Disclosure Number: IPCOM000020554D
Original Publication Date: 2003-Nov-01
Included in the Prior Art Database: 2003-Nov-27
Document File: 19 page(s) / 40K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Khosravi: AUTHOR [+4]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Network Working Group H. Khosravi, Ed.

Request for Comments: 3654 T. Anderson, Ed.

Category: Informational Intel

November 2003

Requirements for Separation of IP Control and Forwarding

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

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.

Table of Contents

1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2

2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 2

3. Architecture. . . . . . . . . . . . . . . . . . . . . . . . . 4

4. Architectural Requirements. . . . . . . . . . . . . . . . . . 5

5. FE Model Requirements . . . . . . . . . . . . . . . . . . . . 7

5.1. Types of Logical Functions. . . . . . . . . . . . . . . 8

5.2. Variations of Logical Functions . . . . . . . . . . . . 8

5.3. Ordering of Logical Functions . . . . . . . . . . . . . 8

5.4. Flexibility . . . . . . . . . . . . . . . . . . . . . . 8

5.5 Minimal Set of Logical Functions. . . . . . . . . . . . 9

6. ForCES Protocol Requirements. . . . . . . . . . . . . . . . . 10

7. References. . . . . . . . . . . . . . . . . . . . . . . . . . 14

7.1. Normative References. . . . . . . . . . . . . . . . . . 14

7.2. Informative References. . . . . . . . . . . . . . . . . 15

8. Security Considerations . . . . . . . . . . . . . . . . . . . 15

9. Authors' Addresses & Acknowledgments. . . . . . . . . . . . . 15

10. Editors' Contact Information. . . . . . . . . . . . . . . . . 17

11. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 18

Khosravi & Anderson Informational [Page 1]

RFC 3654 ForCES Requirements November 2003

1. Introduction

An IP network element is composed of numerous logically separate

entities that cooperate to provide a given functionality (such as a

routing or IP switching) and yet appear as a normal integrated

network element to external entities. Two primary types of network

element components exist: control-plane components and forwarding-

plane components. In general, forwarding-plane components are ASIC,

network-processor, or general-purpose processor-based devices that

handle all data path operations. Conversely, control-plane

components are typically based on general-purpose processors that

provide control functionality such as the processing of routing or

signaling protocols. A standard set of mechanisms for connecting

these components provides increased scalability and allows the

control and forwarding planes to evolve independently, thus promoting

faster innovation.

For the purpose of illustration, le...