-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Management Plane vs. Control Plane #3
Comments
I don't recall seeing discussion or consensus on this. Based on the intended functionalities of this component, I personally like the term Management Plane better. I think you should remove the "TBD..." part. Both the architecture draft and IM draft currently use the term Control Plane. They need the corresponding change to be consistent. |
Additional comments from the SACM list: On 06/30/2015 10:13 PM, Natale, Bob (RNATALE@mitre.org) wrote:
On 06/30/2015 11:26 PM, Jarrett Lu (jarrett.lu@oracle.com) wrote:
On 06/30/2015 11:27 PM, Ira McDonald (blueroofmusic@gmail.com) wrote:
|
It remains an open issue to define these terms in the context of SACM. Definitions will probably be very close to existing definitions. Examples (as a point of reference):
Are these examples considered correct and appropriate enough by the group to provide a basis for further discussion? Additionally, it could be considered to define interfaces between planes (e.g. a control plane building block could steer a specific data plane building block in a SACM component) and direction of these interfaces (northbound/southbound). If this is out of scope in SACM, a short reference highlighting this in e.g. architecture could be included. |
Terms as defined in RFC 7276 ("An Overview of Operations, Administration, and Maintenance (OAM) Tools") Data PlaneThe data plane is the set of functions used to transfer data in the stratum or layer under consideration [1]. Control PlaneThe control plane is the set of protocols and mechanisms that enable routers to efficiently learn how to forward packets towards their final destination (based on [2]). Management PlaneThe term "Management Plane", as described in [3], is used to describe the exchange of management messages through management protocols (often transported by IP and by IP transport protocols) between management applications and the managed entities such as network nodes. [1] ITU-R/ITU-T, "ITU-R/ITU-T Terms and Definitions", 2013, http://www.itu.int/pub/R-TER-DB. |
I do not know if there is any benefit at this point to separating the control plane and the management plane in the terms that have been summarized in this issue so far. I don't know that I have a preference between the two terms, however in terms of what we have discussed so far in the architecture we have be looking at what is deemed to be control plane functions. Protocols like broker protocol and agents like access control points are doing things "inside" of the system and not external terms. Functions like publishing guidance might be termed as management in terms of what is discussed, but I tend to look at that as just one more piece of data that is moving around the system. It does not matter to me how it gets published into the system at this point. |
Per the 1/25 virtual interim discussion, I suggest dropping the quoted RFC6192 content in the Control Plane and Data Plane entries and revising those entries to something along the lines of: |
addressed in the draft. |
The current definition of the term Management Plane includes the comment “TBD per list; was "Control Plane””.
Is there already a consensus about which term to use? This should be decided soon (and then fixed consistently).
The text was updated successfully, but these errors were encountered: