Re: [Dcpel] questions related to DCPEL scope

Paulo Mendes <mendes@docomolab-euro.com> Fri, 03 March 2006 13:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FFAet-0007Fz-V0; Fri, 03 Mar 2006 08:49:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FFAes-0007Fu-PD for dcpel@ietf.org; Fri, 03 Mar 2006 08:49:27 -0500
Received: from deprox.docomolab-euro.com ([212.119.9.186]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FFAes-0005yN-AJ for dcpel@ietf.org; Fri, 03 Mar 2006 08:49:26 -0500
Received: from 172.27.10.3 by deprox.docomolab-euro.com (InterScan E-Mail VirusWall NT); Fri, 03 Mar 2006 14:49:03 +0100
Received: from [172.27.100.57] ([172.27.100.57]) by deex.docomolab-euro.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 3 Mar 2006 14:49:03 +0100
Message-ID: <44084954.8090201@docomolab-euro.com>
Date: Fri, 03 Mar 2006 14:49:08 +0100
From: Paulo Mendes <mendes@docomolab-euro.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Georgios Karagiannis <karagian@cs.utwente.nl>
Subject: Re: [Dcpel] questions related to DCPEL scope
References: <PeqVqMLX.1140676112.7795150.karagian@ewi.utwente.nl> <43FE2D61.8050307@pollere.com> <007d01c63940$ae5df080$4c0d5982@dynamic.ewi.utwente.nl>
In-Reply-To: <007d01c63940$ae5df080$4c0d5982@dynamic.ewi.utwente.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Mar 2006 13:49:03.0187 (UTC) FILETIME=[3B5BFA30:01C63EC9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: dcpel@ietf.org
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>
Errors-To: dcpel-bounces@ietf.org

Hi Georgios,

IMO, a state of the art study about centralized approaches should not 
have an impact on the DCPEL BOF/WG charter. The major reason is that the 
internetworking approach followed by IETF and other organizations, such 
as 3GPP, is different: IETF vision of internetworking was always more 
close to a distributed approach, while other organizations have been 
following a more centralized approach.

Nevertheless, I agree that existing centralized resource management 
approaches should be analyzed. But, IMO, this should be done against the 
DCPEL requirements I-D. This is, if some of those approaches fulfill the 
requirements agreed within DCPEL, they (intact, changed or simplified) 
may be candidates to integrate a DiffServ control plane.

But, I also want to stress that the DCPEL requirements I-D mention also 
distributed control approaches as suitable for the DiffServ control 
plane, following a more IETF way of doing internetworking.

Cheers
Paulo

Georgios Karagiannis wrote:

> Hi Kathie
>
> Please do not understand me wrong!
> I am in favour of starting the DCPEL WG.
> My concerns are related to the match between the DCPEL charter activities
> and the work that has been by theITU-t, ETSI-tispan, DSL, packetcable, 
> 3gpp, 3gpp2,
> ipshere, wimax  goups on the area of centralized control plane 
> architectures.
> I think that it is useful to start the work in DCPEL WG considering as 
> starting point
> the work that has been done already in the other groups.
>
> Best Regards,
> Georgios
>
>
>
> ----- Original Message ----- From: "Kathleen Nichols" 
> <nichols@pollere.com>
> To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
> Cc: <dcpel@ietf.org>
> Sent: Thursday, February 23, 2006 10:47 PM
> Subject: Re: [Dcpel] questions related to DCPEL scope
>
>
>>
>> Trimmed to reply (in-line) to your comments:
>>
>> Georgios Karagiannis wrote:
>> ...
>>
>>>>
>> [G]>>> Could you specify what do you mean by a distributed Difsserv 
>> control
>>
>>>>> plane approach? Will this distributed approach impact an individual
>>>>> Diffserv router, e.g., a Diffserv core router?
>>>>
>> [K]>> I'm just giving a short answer here. A distributed DiffServ 
>> control
>>
>>>> plane is one where the control plane actions do not reside in
>>>> one physical location and probably not in one logical location.
>>>> We would expect an impact on DiffServ edge routers, but probably
>>>> not DiffServ core routers.
>>>
>>>
>>> Georgios: But I suppose that this will of depend on the specified PDBs.
>>> What if a PDB requires a control plane support for a core Diffserv 
>>> router?
>>>
>>
>> If by core Diffserv router you mean a diffserv router interior to a
>> domain, one would not normally expect the need for control of
>> classifiers and policers, but just configuration of the PHBs as
>> realized by queues and their scheduler, as described in RFC 2475
>> and other diffserv documents. However, this doesn't preclude an
>> operator from using the diffserv "edge" functions interior to a
>> network if desired.
>>
>> ...
>>
>>> Georgios: Maybe it is very useful to perform an extensive state of the
>>> art study on the area of centralized control plane architectures that
>>> are developed in ITU-t, ETSI-tispan, DSL, packetcable, 3gpp, 3gpp2, 
>>> ipshere, wimax. The outcome of this state of the art study could then
>>> help to define
>>> the final charter of the DCPEL BOF/WG.
>>>
>>
>> Do you believe that the work of these groups obviates an IETF DCPEL WG?
>>
>> regards,
>> Kathie
>>
>
>
>
> _______________________________________________
> Dcpel mailing list
> Dcpel@ietf.org
> https://www1.ietf.org/mailman/listinfo/dcpel
>



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