RE: [Dcpel] Purpose of a diffserv control plane

"Roy, Radhika \(AEAD\)" <RoyR@saic-abingdon.com> Mon, 14 November 2005 19:58 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EbkTH-0001Zk-AR; Mon, 14 Nov 2005 14:58:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZYsi-0002LZ-7y for dcpel@megatron.ietf.org; Tue, 08 Nov 2005 14:11:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26664 for <dcpel@ietf.org>; Tue, 8 Nov 2005 14:11:17 -0500 (EST)
Received: from mclmx2.mail.saic.com ([149.8.64.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZZ8X-0005E0-Q2 for dcpel@ietf.org; Tue, 08 Nov 2005 14:28:08 -0500
Received: from 0015-its-ieg02.mail.saic.com ([149.8.64.21] [149.8.64.21]) by mclmx2.mail.saic.com; Tue, 8 Nov 2005 14:11:22 -0500
Received: from mclmx2.mail.saic.com ([149.8.64.32]) by 0015-its-ieg02.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id M2005110814112208467 ; Tue, 08 Nov 2005 14:11:22 -0500
Received: from bh-exchangefe.saic-abingdon.com ([149.8.64.21] [149.8.64.21]) by mclmx2.mail.saic.com with ESMTP; Tue, 8 Nov 2005 14:11:22 -0500
Received: from bh-exchange02.saic-abingdon.com ([10.42.81.226]) by bh-exchangefe.saic-abingdon.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 Nov 2005 14:15:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Dcpel] Purpose of a diffserv control plane
Date: Tue, 8 Nov 2005 14:15:14 -0500
Message-Id: <2FE23D25B7292B489A217D1965CDA866089929@bh-exchange02.saic-abingdon.com>
Thread-Topic: [Dcpel] Purpose of a diffserv control plane
Thread-Index: AcXkkulgz1x4zWgwSPWPdjPNRAyQugABUYgQ
From: "Roy, Radhika \(AEAD\)" <RoyR@saic-abingdon.com>
To: "Hancock, Robert" <robert.hancock@roke.co.uk>, "Pulliam, Jeffrey S" <jeffrey.s.pulliam@lmco.com>, "Kathleen Nichols" <nichols@pollere.com>, <dcpel@ietf.org>
X-OriginalArrivalTime: 08 Nov 2005 19:15:17.0985 (UTC) FILETIME=[C157DD10:01C5E498]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 90e8b0e368115979782f8b3d811b226b
X-Mailman-Approved-At: Mon, 14 Nov 2005 14:58:27 -0500
Cc:
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>
Content-Type: multipart/mixed; boundary="===============2013795356=="
Sender: dcpel-bounces@ietf.org
Errors-To: dcpel-bounces@ietf.org

Hi, all:

 

It seems to be that 5 points articulated by Robert may describe the
overall DCPEL schemes. The only other point that may need to be added:
"Specific to DiffServ services."

 

Cheers!

Radhika

 

________________________________

From: dcpel-bounces@ietf.org [mailto:dcpel-bounces@ietf.org] On Behalf
Of Hancock, Robert
Sent: Tuesday, November 08, 2005 1:28 PM
To: Pulliam, Jeffrey S; Kathleen Nichols; dcpel@ietf.org
Subject: RE: [Dcpel] Purpose of a diffserv control plane

 

Hi Jeff, Kathie, 

I think the problem that I am having (and maybe some others) in 
following this discussion is that the problem scope is potentially 
so enormous that it is difficult to work out how to start 
discussing it, and commonplace for discussions to proceed at cross 
purposes because people are talking about different bits of it. 

Kathie's prior mail described this activity as the diffserv analogy 
of moving from static routes to RIP. However, if the model is of 
network-level controller nodes which manage groups of routers, a 
closer analogy (to my mind) would be moving from static routes to 
inter-domain MPLS. (I'm not saying this approach is wrong, just 
trying to stress that it is quite a leap.) There is also a
terminological 
problem, that words like 'signaling' or 'control function' mean 
very specific things to some people, but to others are extremely 
broad. 

My very crude take on what Jeff describes below is that one can 
imagine 5 different components to the problem, i.e. 
1) a language for describing the services that are requested 
2) logic for deciding whether and how to implement the requests 
3) a protocol mechanism for initiating requests with domains 
and carrying requests between them 
4) interaction with AAA (especially authorisation/accounting) 
functions to support the decision process 
5) protocol mechanisms to implement the decision in the forwarding 
plane 

Now my question is whether the purpose of DCPEL is to work specifically 
on some or all of these, or whether initially it is to work on 
understanding how they fit together (or on some similar decomposition). 
Note that at least (3), (4) and (5) could all be described as 
'signalling', and (2)-(4) as 'control functions'; OTOH I got the 
impression last night (maybe incorrectly) that Scott at least was 
mainly interested in (1). 

Or have I missed the point entirely? 

Robert H. 

ps. see you at lunch :-) 

_______________________________________________
Dcpel mailing list
Dcpel@ietf.org
https://www1.ietf.org/mailman/listinfo/dcpel