Talk:Control plane

Balance between this article and Routing Table

Obviously, there needs to be a balance between the two. Here, I focused on how information gets into the routing table(s). I see routing table as a description of the RIB structure and perhaps organization.

If anyone can see what is wrong with the Nortel RS reference, please fix it so the URL doesn't appear in the References section. Howard C. Berkowitz 14:40, 1 July 2007 (UTC)

Minor page move

I think Control Plane and Forwarding Plane should be moved to Control plane and Forwarding plane, respectively, to match common usage. --Nethgirb 06:47, 9 July 2007 (UTC)

outside of routing

Currently the opening paragraph effectively starts with 'in routing'

Ideally, the page should start off with something more generic. Perhaps something like:

The control plane is the network layer which allows for network connections to be established and released, for dynamic forwarding configuration based on current network topology, for billing, and other automated tasks that the network performs which do not involve human interaction.

The control plane is distinguished from the data plane (which carries the network payload) and the management plane (which allows for configuration of the network nodes)

The basis for the common telephony network control plane is defined in the Common Channel Signalling System nr 7 (CCS7), which specifies protocols and implementations which segregate the protocol from the data plane. Telephone companies often have a policy regarding which control messages are allowed to pass at the interconnection point with other telephone companies.

And then include something like:

MPLS uses a tag or label distribution protocol for the dynamic network topology information aspects of the control plane, while isolating this control plane from its managed protocols using MPLS framing. MPLS control plane interconnection is discussed in RFC4364.

Within TCP/IP the dynamic topology control plane function is provided by routing protocols such as BGP, ISIS, OSPF, RIP. The control plane functionality is not segregated from the data or management plane. Control plane security methods include TCP-MD5 and route redistribution controls. [rfc4354]

I hesitate adding this to the main page, as I feel I need to do more reading first. —Preceding unsigned comment added by 206.47.249.251 (talk) 22:12, 22 May 2008 (UTC)

I want to think more as well, but I like this. Howard C. Berkowitz (talk) 23:13, 22 May 2008 (UTC)