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

Nic Neate <Nic.Neate@dataconnection.com> Fri, 21 November 2008 16:19 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 BEA7B3A69F0; Fri, 21 Nov 2008 08:19:57 -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 94C7E3A6A40 for <pce@core3.amsl.com>; Fri, 21 Nov 2008 08:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level:
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=0.263, 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 pqyDWM8wOC1z for <pce@core3.amsl.com>; Fri, 21 Nov 2008 08:19:55 -0800 (PST)
Received: from enfiets2.dataconnection.com (enfiets2.dataconnection.com [192.91.191.39]) by core3.amsl.com (Postfix) with ESMTP id 623583A697A for <pce@ietf.org>; Fri, 21 Nov 2008 08:19:55 -0800 (PST)
Received: from ENFIMBOX1.ad.datcon.co.uk (172.18.10.27) by enfiets2.dataconnection.com (172.18.4.22) with Microsoft SMTP Server (TLS) id 8.1.311.2; Fri, 21 Nov 2008 16:20:41 +0000
Received: from ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) by ENFIMBOX1.ad.datcon.co.uk ([172.18.10.27]) with mapi; Fri, 21 Nov 2008 16:19:59 +0000
From: Nic Neate <Nic.Neate@dataconnection.com>
To: "saquibk@huawei.com" <saquibk@huawei.com>
Date: Fri, 21 Nov 2008 16:19:58 +0000
Thread-Topic: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions
Thread-Index: AclKiHqezXI/YPsdRbqX5Q6CAL9jFQAolHqQAACFhuAAFiej0AAbwgaw
Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4FECF0@ENFIMBOX1.ad.datcon.co.uk>
References: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3209@ENFIMBOX1.ad.datcon.co.uk> <009201c94b86$89e11420$3905120a@china.huawei.com>
In-Reply-To: <009201c94b86$89e11420$3905120a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "pce@ietf.org" <pce@ietf.org>
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

Hi Saquib,

In S2L sub-path diversity, it is allowed for the sub-path to leaf A in the first tree to share resources with the sub-path to leaf B in the second tree.  So the complete trees are not (necessarily) diverse.

Nic

-----Original Message-----
From: saquib khan [mailto:saquibk@huawei.com]
Sent: 21 November 2008 03:09
To: Nic Neate; 'Quintin Zhao'; Aria - Adrian Farrel Personal
Cc: Jeanlouis.Leroux@orange-ftgroup.com; 'Mohamad CHAITOU'; pce@ietf.org; daniel@olddog.co.uk
Subject: RE: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions



Hi Nic,
If we consider S2L diversity for all the leaves in the tree, automatically the complete tree will become diverse, then why do we require a new diversity option?


-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of Nic Neate
Sent: Thursday, November 20, 2008 10:04 PM
To: Quintin Zhao; Aria - Adrian Farrel Personal
Cc: Jeanlouis.Leroux@orange-ftgroup.com; 'Mohamad CHAITOU'; pce@ietf.org; daniel@olddog.co.uk
Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

Hi Quintin,

I don't think "partial path diversity for certain leaves" is quite the point I was suggesting.

The idea of S2L sub-path diversity is that, when you're doing 1+1 protection, you don't need complete tree diversity.  It is sufficient just to ensure that, for any given leaf, the S2L sub-paths to that leaf in the two trees are diverse.  Then, following some network failure, traffic will still be delivered to all leaves on at least one of the two trees.

Two P2MP LSPs going in opposite ways around a ring is the easiest way to picture this.

Nic

-----Original Message-----
From: Quintin Zhao [mailto:qzhao@huawei.com]
Sent: 20 November 2008 16:16
To: Aria - Adrian Farrel Personal; Nic Neate
Cc: Jeanlouis.Leroux@orange-ftgroup.com; pce@ietf.org; daniel@olddog.co.uk; 'Mohamad CHAITOU'; fabien.verhaeghe@marben-products.com; zali@cisco.com; takeda.tomonori@lab.ntt.co.jp
Subject: RE: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions

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

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