Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Quintin Zhao <qzhao@huawei.com> Thu, 20 November 2008 16:16 UTC

Return-Path: <pce-bounces@ietf.org>
X-Original-To: pce-archive@megatron.ietf.org
Delivered-To: ietfarch-pce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 754183A698C; Thu, 20 Nov 2008 08:16:24 -0800 (PST)
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4D513A67B5 for <pce@core3.amsl.com>; Thu, 20 Nov 2008 08:16:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0Qo-EP8BWS1 for <pce@core3.amsl.com>; Thu, 20 Nov 2008 08:16:22 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 15AF43A6980 for <pce@ietf.org>; Thu, 20 Nov 2008 08:16:22 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KAN0099A3V8JL@usaga01-in.huawei.com> for pce@ietf.org; Thu, 20 Nov 2008 08:16:20 -0800 (PST)
Received: from Z73671a ([130.129.29.115]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KAN00EQA3V3XH@usaga01-in.huawei.com> for pce@ietf.org; Thu, 20 Nov 2008 08:16:20 -0800 (PST)
Date: Thu, 20 Nov 2008 11:16:21 -0500
From: Quintin Zhao <qzhao@huawei.com>
In-reply-to: <76626FC9B3DE41E5AA7EB3813C817EB2@your029b8cecfe>
To: 'Adrian Farrel' <adrian@olddog.co.uk>, 'Nic Neate' <Nic.Neate@dataconnection.com>
Message-id: <000f01c94b2b$54558ee0$731d8182@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Thread-index: AclKiHqezXI/YPsdRbqX5Q6CAL9jFQAolHqQ
References: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B2B48@ENFIMBOX1.ad.datcon.co.uk> <76626FC9B3DE41E5AA7EB3813C817EB2@your029b8cecfe>
Cc: Jeanlouis.Leroux@orange-ftgroup.com, 'Mohamad CHAITOU' <mohamad.chaitou@gmail.com>, pce@ietf.org, daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pce-bounces@ietf.org
Errors-To: pce-bounces@ietf.org

Nic and Adrian,

Thanks for your suggestions!
 
By using the existing SVEC functionality, PCC can request the secondary P2MP
LSP path computation to protect the whole P2MP path tree by specifying the
S/N/L bit in the SVEC object. 

If we understand the new requirements you suggested for S2L sub-path
diversity, you want the PCC to be able to ask the PCE to compute secondary
P2MP path tree with partial path diversity for certain leaves or certain S2L
sub-path. 

We will address these new requirements in our next version of the draft.
 
Quintin

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Wednesday, November 19, 2008 3:49 PM
To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Ah, that is an interesting and valid point, Nic.

And I think one might also consider "directional diversity" for your ring 
example.

A
----- Original Message ----- 
From: "Nic Neate" <Nic.Neate@dataconnection.com>
To: <qzhao@huawei.com>; <Mohamad.Chaitou@orange-ftgroup.com>
Cc: <Jeanlouis.Leroux@orange-ftgroup.com>; <pce@ietf.org>; 
<daniel@olddog.co.uk>
Sent: Wednesday, November 19, 2008 8:28 PM
Subject: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions


Hi,

I have a suggestion for a small extension to the PCEP P2MP draft.

I believe the base PCEP specification currently has three options for 
calculating diverse protection paths: link diverse, node diverse and SRLG 
diverse (draft-ietf-pce-pcep section 7.13.2).

In P2MP, S2L sub-path diverse is another important case.  I think it would 
be good to allow the PCC to request computation of S2L sub-path diverse 
protection paths.

This is useful when doing 1+1 protection in a ring topology, for example.

Nic




----------------------------------------------------------------------------
----


> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
> 



_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce