[Dcpel] Purpose of a diffserv control plane

"Pulliam, Jeffrey S" <jeffrey.s.pulliam@lmco.com> Tue, 08 November 2005 11:25 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZRbg-0003cU-Bo; Tue, 08 Nov 2005 06:25:40 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZRbe-0003a8-Um for dcpel@megatron.ietf.org; Tue, 08 Nov 2005 06:25:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29536 for <dcpel@ietf.org>; Tue, 8 Nov 2005 06:25:12 -0500 (EST)
Received: from mailgw2a.lmco.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZRrO-0000B5-9Q for dcpel@ietf.org; Tue, 08 Nov 2005 06:41:58 -0500
Received: from emss01g01.ems.lmco.com (relay1.ems.lmco.com []) by mailgw2a.lmco.com (8.12.10/8.12.10) with ESMTP id jA8BPOhq016859; Tue, 8 Nov 2005 06:25:24 -0500 (EST)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30875) id <0IPM00J01VQC52@lmco.com>; Tue, 08 Nov 2005 03:25:24 -0800 (PST)
Received: from EMSS01I00.us.lmco.com ([]) by lmco.com (PMDF V6.1-1X6 #30875) with ESMTP id <0IPM00C6EVQB8A@lmco.com>; Tue, 08 Nov 2005 03:25:23 -0800 (PST)
Received: from EMSS01M10.us.lmco.com ([]) by EMSS01I00.us.lmco.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 08 Nov 2005 03:25:24 -0800
Date: Tue, 08 Nov 2005 03:25:24 -0800
From: "Pulliam, Jeffrey S" <jeffrey.s.pulliam@lmco.com>
Subject: [Dcpel] Purpose of a diffserv control plane
To: Kathleen Nichols <nichols@pollere.com>, dcpel@ietf.org
Message-id: <CF127EA649E2804ABF97FD457A9FD4B308AE7AF2@emss01m10.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: 7BIT
Thread-Topic: [Dcpel] moving into a diffserv control plane
Thread-Index: AcXkKrCmwHJVr9f/QCalkivtUFdizQAIw4wt
content-class: urn:content-classes:message
X-OriginalArrivalTime: 08 Nov 2005 11:25:24.0296 (UTC) FILETIME=[1C985480:01C5E457]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7BIT
X-BeenThere: dcpel@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for possible diffserv control plane elements WG <dcpel.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dcpel>, <mailto:dcpel-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/dcpel>
List-Post: <mailto:dcpel@ietf.org>
List-Help: <mailto:dcpel-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dcpel>, <mailto:dcpel-request@ietf.org?subject=subscribe>
Sender: dcpel-bounces@ietf.org
Errors-To: dcpel-bounces@ietf.org

A couple of things - 

- For those interested in follow up, I want to repeat the offer of lunch at the IETF on Tuesday November 8 at 11:30 - in the MacKenzie room.  The room is on the first floor near the meeting registration tables.   

- In hopes of starting a discussion, I would like to try out the following as a starting position for discussion:

The purpose of a diffserv control plane is to provide automated control of the diffserv domain, governed and constrained by policy.  Control functions configure the diffserv domain to deliver services in response to requests.  Requests to the control function are made by users, network operations, and  network management.  The control plane contains necessary  rules and logic to respond to the requests automatically, with resulting actions including actions to configure the network to accept (or reject) the request, and actions to respond to the requestor with status of the request.

Request can originate internal to the diffserv domain, or originate from other network domains. Actions in response to the requests are either actions affecting the internal diffserv domains, or are actions that cross domain boundaries (in the form of requests?).  A quick and dirty simple picture showing the contexts (lots of room for improvement).
Requestors     Control         Actions

User<------>*         *<----->Network Configuration
            * Control *
Net Op<---->*  Plane  *
            *         *<----->Response to Requestor
Net mgt<--->***********

What is the role, functions, and constraints of signaling within the diffserv domain?  I would like to revise (or replace) the above to accurately reflect the role of signaling within a diffserv domain.  


Jeff Pulliam

Dcpel mailing list