Re: AW: AW: [Dcpel] FWD: [Re: proposed charter]

Paulo Mendes <mendes@docomolab-euro.com> Mon, 13 March 2006 10:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIjrY-0007dv-B7; Mon, 13 Mar 2006 05:01:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FIjrX-0007dq-1C for dcpel@ietf.org; Mon, 13 Mar 2006 05:01:15 -0500
Received: from deprox.docomolab-euro.com ([212.119.9.186]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FIjrW-0008IO-GM for dcpel@ietf.org; Mon, 13 Mar 2006 05:01:15 -0500
Received: from 172.27.10.3 by deprox.docomolab-euro.com (InterScan E-Mail VirusWall NT); Mon, 13 Mar 2006 11:00:25 +0100
Received: from [172.27.100.57] ([172.27.100.57]) by deex.docomolab-euro.com with Microsoft SMTPSVC(5.0.2195.4905); Mon, 13 Mar 2006 11:00:25 +0100
Message-ID: <441542C7.8020100@docomolab-euro.com>
Date: Mon, 13 Mar 2006 11:00:39 +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: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
Subject: Re: AW: AW: [Dcpel] FWD: [Re: proposed charter]
References: <ECDC9C7BC7809340842C0E7FCF48C393A807C1@MCHP7IEA.ww002.siemens.net>
In-Reply-To: <ECDC9C7BC7809340842C0E7FCF48C393A807C1@MCHP7IEA.ww002.siemens.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 13 Mar 2006 10:00:25.0131 (UTC) FILETIME=[F2E43FB0:01C64684]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
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 Hannes,

All the questions that you mention are some of the reasons to have a WG 
looking at what do we need to operate a DiffServ network. Even if we 
focus on protocols, as you did in your e-mail, all your questions show 
that although we have a set of protocols available in IETF we still 
don't know our to inter-operate them for a common goal. The control of 
Diffserv networks, in this case.

About what comes first, protocols or service control, IMO a protocol is 
only useful if we know why do we need it. Transporting data-control 
packets among network devices serves the goal of controlling some 
network functionality. In the case of DiffServ, it is not clear what 
protocols (and what content semantic) do we need and how will they 
interact to control DiffServ operations.

I see this as a very good opportunity to stress the cooperation between 
different IETF WGs with  a common goal in mind. So, DCPEL is all about 
cooperation and not about competition between WGs.

Paulo


Tschofenig, Hannes wrote:

>Hi Kathie, 
>
>your mail points to an aspect that a number of us have never really understood. 
>I think we have a terminology problem here. 
>
>Just as an example, let us take a look at Figure 1 of <draft-vandenberghe-dcpel-basics-00.txt>:
>
>                    +-DCP-----------------------------+
>                    |                                 |
>                    | +---------------+  +-----+      |
>                    | |Domain Policies|  | AAA |      |
>                    | +--------||-----+  +-----+      |
>                    |          ||          ||         |
>                    |    +-----||----------|+         |
>   QoS Announce(*) <=====|                  |=========> QoS Announce (*)
>   QoS Request  ========>|                  |=========> QoS Request
>   QoS Response <========|        DCP       |<========= QoS Response
>   QoS Query(*) ========>|                  |=========> QoS Query(*)
>   QoS Status   <========|                  |<========= QoS Status
>                    |    +----||------------+         |
>                    |         ||          ||          |
>                    | +-------||------+ +-||--------+ |
>                    | | Enforcement   | | Monitoring| |
>                    | +---------------+ +-----------+ |
>                    |                                 |
>                    +---------------------------------+
>
>A few protocol interactions that come to my mind when I see this figure are: 
>
>a) How does the AAA infrastructure interact with the DCP node? 
>b) Isn't a protocol required in order to provide the interaction between different DCP nodes? (e.g., for QoS Announce, Request, Response, Query, Status)?
>c) How does the DCP node communicate with the enforcement (points)?
>d) How does the interaction between DCP and the monitoring entities looks like? 
>e) Where do the Domain Policies come from? 
>
>For (a) you mention "access to the AAA information". This might be RADIUS or Diameter since this stuff is used today. 
>For (b) you mention "external protocol/mechanism sends a QoS Query, .... to the DCP" 
>For (c) you mention COPS, Netconf, SNMP 
>For (d) you mention "needs access to a wide range of information about the operational conditions of its network."
>For (e) you mention "A DCP must either contain these or have access to them, perhaps a combination." 
>
>The draft also talks about other protocols like SIP and NSIS.
>
>Having briefly looked at these aspects of your draft please explain what you mean by:
>
>* "... infrastructure that is capable of realizing services on an IP network before we worry overly much about what is being sent."
>
>* "Particularly since signaling is not required for all services."
>
>(Note that the term 'service' is not really well defined in the IETF nor in any other organization.)
>
>* "It seems
>  
>
>>to be all about signaling. In my opinion, this has been a big
>>problem in the QoS area in general and particularly at the IETF.
>>That is, spending time talking about what information is going to
>>be sent around and in what sort of containers rather than how to
>>manage and control IP differentiated services."
>>    
>>
>
>If you do not have these protocols and if you don't worry about the content that is sent around (with the associated semantic) then it might be a 'little bit difficult' to dynamically manage and control QoS.
>
>What term do you use for this dynamic information exchange? 
>
>Ciao
>Hannes
>
>  
>
>>-----Ursprüngliche Nachricht-----
>>Von: Kathleen Nichols [mailto:nichols@pollere.com] 
>>Gesendet: Donnerstag, 9. März 2006 16:56
>>An: Tschofenig, Hannes; dcpel@ietf.org
>>Betreff: Re: AW: [Dcpel] FWD: [Re: proposed charter]
>>
>>
>>So, I really must reply, in brief, to Hannes's email. It seems
>>to be all about signaling. In my opinion, this has been a big
>>problem in the QoS area in general and particularly at the IETF.
>>That is, spending time talking about what information is going to
>>be sent around and in what sort of containers rather than how to
>>manage and control IP differentiated services. If the right
>>information is being sent, then a useful control and management
>>structure should be able to use it. But it seems like we need to
>>have an infrastructure that is capable of realizing services on
>>an IP network before we worry overly much about what is being
>>sent. Particularly since signaling is not required for all
>>services.
>>
>>	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
>
>  
>


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