[Dcpel] Comments on draft-mendes-dcpel-requirements-00.txt

Olivier Dugeon <Olivier.Dugeon@francetelecom.com> Mon, 16 January 2006 17:27 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 1EyY8X-0006zO-1w; Mon, 16 Jan 2006 12:27:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EyY8T-0006xv-Tw for dcpel@megatron.ietf.org; Mon, 16 Jan 2006 12:27:19 -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 MAA29874 for <dcpel@ietf.org>; Mon, 16 Jan 2006 12:25:53 -0500 (EST)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EyYGQ-0002YC-On for dcpel@ietf.org; Mon, 16 Jan 2006 12:35:32 -0500
Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Mon, 16 Jan 2006 18:27:14 +0100
Received: from [10.193.11.122] ([10.193.11.122]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Mon, 16 Jan 2006 18:27:14 +0100
Message-ID: <43CBD772.7070004@francetelecom.com>
Date: Mon, 16 Jan 2006 18:27:14 +0100
From: Olivier Dugeon <Olivier.Dugeon@francetelecom.com>
Organization: France Telecom R&D
User-Agent: Thunderbird 1.5 (X11/20051201)
MIME-Version: 1.0
To: dcpel@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jan 2006 17:27:14.0325 (UTC) FILETIME=[17489C50:01C61AC2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Subject: [Dcpel] Comments on draft-mendes-dcpel-requirements-00.txt
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

Hi Paulo and all,

Following the last draft sent by Kathleen, here it is some comments 
about your draft:

On page 2, do you think it is suitable to mention application (or 
customer) request as an example of service which need DS Control Plane ?

On page 6, you mention that DCP must support heterogeneous network 
including mobile. Do you think that DCP must support mobility or just 
nomadic. In case of mobility, how do you think that handover could be 
support ? I think it's a very huge problem.

On page 7, like on draft-vandenberghe-dcepl-basis-00.txt, I think that 
the monitoring should include network topology acquisition in order to 
the DCP to be path aware. In fact, globaly speaking regarding NSIS, 
which are path coupled, the DCP should be path-decoupled, but, in the 
same time be path awareness. I understand that, stating like this, it is 
a little bit disappointed, but, in order to correctly handle a DS domain 
and perform admission control, the DCP must know a minimu about the 
network it control. This include at least the topology.

On page 8, you describe the SLS, but not mention the function necessary 
to manipulate the SLSs. I think it could be include:
Request, Delete, Modify, Announce, Query as basis functions and 
certainly need some maintenance functions like GetAll, DeleteAll ...

On page 9, about the inter-domain (bullet point 2). You mention packet 
re-marking at the inter-domain boundary. Do you think that this 
statement must be extend to policy (in fact, all DS actions: classify, 
policy, marking/dropping and scheduling) ? Operator wants to control 
what is entering their network despite that there is a contract with the 
sender. In any case the traffic is control, mark and shaped or spaced if 
necessary. Packet dropping could occur if the contract is not respected.

I also note some mis-spelling (like double section) and generally wants 
to propose some sentence adjustment. Did you directly write the draft in 
plain text or do you use another format ? If yes, is it possible to get 
the original file in order to propose my corrections ?

Finally, as the other proposed draft, I'm in favor of this draft and 
think it is in good shape to provide material for a DCPEL BoF.

Best regards,

Olivier

-- 
Project Manager for Network architecture and switching Division
 & FT/DR&D/CORE/M2I           | mailto:Olivier.Dugeon@francetelecom.com
 2, Avenue Pierre Marzin      | Phone/Fax:  +(33) 296 05 2880/1470
 F-22307 LANNION              | Mobile:     +(33) 6 82 90 37 85


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