Re: [Pce] Pce Digest, Vol 51, Issue 13
Young Lee <ylee@huawei.com> Thu, 20 November 2008 20:09 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 585623A69A1; Thu, 20 Nov 2008 12:09:33 -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 4711F3A6992 for <pce@core3.amsl.com>; Thu, 20 Nov 2008 12:09:32 -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 dnhN3Qu0oH-T for <pce@core3.amsl.com>; Thu, 20 Nov 2008 12:09:30 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id 814D83A677D for <pce@ietf.org>; Thu, 20 Nov 2008 12:09:30 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KAN00IGEENQ5K@usaga03-in.huawei.com> for pce@ietf.org; Thu, 20 Nov 2008 14:09:27 -0600 (CST)
Received: from L73682 ([130.129.78.81]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KAN00M3YENNC5@usaga03-in.huawei.com> for pce@ietf.org; Thu, 20 Nov 2008 14:09:26 -0600 (CST)
Date: Thu, 20 Nov 2008 14:09:17 -0600
From: Young Lee <ylee@huawei.com>
In-reply-to: <mailman.1813.1227206477.4916.pce@ietf.org>
To: pce@ietf.org
Message-id: <001001c94b4b$de4760e0$514e8182@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: AclLP5fiReFej4c2Qp6XWw1QNG2GdgADDWrg
References: <mailman.1813.1227206477.4916.pce@ietf.org>
Subject: Re: [Pce] Pce Digest, Vol 51, Issue 13
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
In favor of both drafts. Young Lee -----Original Message----- From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of pce-request@ietf.org Sent: Thursday, November 20, 2008 12:41 PM To: pce@ietf.org Subject: Pce Digest, Vol 51, Issue 13 Send Pce mailing list submissions to pce@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www.ietf.org/mailman/listinfo/pce or, via email, send a message with subject or body 'help' to pce-request@ietf.org You can reach the person managing the list at pce-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Pce digest..." Today's Topics: 1. Re: Adoption of two new Working Documents ? (Dean Cheng (dcheng)) 2. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions (Quintin Zhao) 3. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions (Nic Neate) 4. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions (Fabien Verhaeghe) 5. Re: Comment on draft-ietf-pce-pcep-p2mp-extensions (Nic Neate) ---------------------------------------------------------------------- Message: 1 Date: Thu, 20 Nov 2008 07:21:30 -0800 From: "Dean Cheng (dcheng)" <dcheng@cisco.com> Subject: Re: [Pce] Adoption of two new Working Documents ? To: "Jean Philippe Vasseur (jvasseur)" <jvasseur@cisco.com>, <pce@ietf.org> Message-ID: <70BC84B185C3EE448EDB7AB8956D3B0E06E9EA3B@xmb-sjc-234.amer.cisco.com> Content-Type: text/plain; charset="us-ascii" Support both. ________________________________ From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of JP Vasseur (jvasseur) Sent: Wednesday, November 19, 2008 3:05 AM To: pce@ietf.org Subject: [Pce] Adoption of two new Working Documents ? Dear WG, Are you in favor or opposed to the adoption of the two following documents as PCE WG documents ? draft-farrel-pce-vendor-constraints-02.txt draft-kkoushik-pce-pcep-mib-02.txt Thanks. JP. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.ietf.org/pipermail/pce/attachments/20081120/87420629/attachment- 0001.htm> ------------------------------ Message: 2 Date: Thu, 20 Nov 2008 11:16:21 -0500 From: Quintin Zhao <qzhao@huawei.com> Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions To: 'Adrian Farrel' <adrian@olddog.co.uk>, 'Nic Neate' <Nic.Neate@dataconnection.com> Cc: Jeanlouis.Leroux@orange-ftgroup.com, 'Mohamad CHAITOU' <mohamad.chaitou@gmail.com>, pce@ietf.org, daniel@olddog.co.uk Message-ID: <000f01c94b2b$54558ee0$731d8182@china.huawei.com> Content-Type: text/plain; charset=us-ascii 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 > ------------------------------ Message: 3 Date: Thu, 20 Nov 2008 16:33:33 +0000 From: Nic Neate <Nic.Neate@dataconnection.com> Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions To: Quintin Zhao <qzhao@huawei.com>, Aria - Adrian Farrel Personal <adrian@olddog.co.uk> Cc: "Jeanlouis.Leroux@orange-ftgroup.com" <Jeanlouis.Leroux@orange-ftgroup.com>, 'Mohamad CHAITOU' <mohamad.chaitou@gmail.com>, "pce@ietf.org" <pce@ietf.org>, "daniel@olddog.co.uk" <daniel@olddog.co.uk> Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3209@ENFIMBOX1.ad.datcon.co.uk> Content-Type: text/plain; charset="us-ascii" 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 > ------------------------------ Message: 4 Date: Thu, 20 Nov 2008 17:59:37 +0100 From: "Fabien Verhaeghe" <fabien.verhaeghe@marben-products.com> Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions To: "'Nic Neate'" <Nic.Neate@dataconnection.com>, <qzhao@huawei.com>, <Mohamad.Chaitou@orange-ftgroup.com> Cc: pce@ietf.org, Jeanlouis.Leroux@orange-ftgroup.com, daniel@olddog.co.uk Message-ID: <000001c94b31$64fd1c80$0714a8c0@marbenproducts.com> Content-Type: text/plain; charset="iso-8859-1" Hi Nic, Just to be sure we understand, can you please confirm that the following definition corresponds to what you name ?S2L sub-path diversity?: For each leaf Ln the path from S to Ln in the primary P2MP LSP is Link (or node or SRLG) diverse with the S to Ln path in the secondary P2MP LSP. If this is correct I also think this is a good suggestion that would be easily fulfilled by defining a new bit in the SVEC object in next draft version. BR Fabien _____ De : Nic Neate [mailto:Nic.Neate@dataconnection.com] Envoy? : mercredi 19 novembre 2008 21:29 ? : qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com Cc : daniel@olddog.co.uk; fabien.verhaeghe@marben-products.com; takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com; zali@cisco.com; pce@ietf.org Objet : 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.ietf.org/pipermail/pce/attachments/20081120/e04e83bb/attachment- 0001.htm> ------------------------------ Message: 5 Date: Thu, 20 Nov 2008 18:41:09 +0000 From: Nic Neate <Nic.Neate@dataconnection.com> Subject: Re: [Pce] Comment on draft-ietf-pce-pcep-p2mp-extensions To: Fabien Verhaeghe <fabien.verhaeghe@marben-products.com>, "qzhao@huawei.com" <qzhao@huawei.com>, "Mohamad.Chaitou@orange-ftgroup.com" <Mohamad.Chaitou@orange-ftgroup.com> Cc: "pce@ietf.org" <pce@ietf.org>, "Jeanlouis.Leroux@orange-ftgroup.com" <Jeanlouis.Leroux@orange-ftgroup.com>, "daniel@olddog.co.uk" <daniel@olddog.co.uk> Message-ID: <11DE3EEC54A8A44EAD99D8C0D3FD72075C6A4B3321@ENFIMBOX1.ad.datcon.co.uk> Content-Type: text/plain; charset="iso-8859-1" Exactly. I agree that a new bit in the SVEC object is the way to do this. Thanks, Nic ________________________________ From: Fabien Verhaeghe [mailto:fabien.verhaeghe@marben-products.com] Sent: 20 November 2008 17:00 To: Nic Neate; qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com Cc: daniel@olddog.co.uk; takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com; zali@cisco.com; pce@ietf.org Subject: RE: Comment on draft-ietf-pce-pcep-p2mp-extensions Hi Nic, Just to be sure we understand, can you please confirm that the following definition corresponds to what you name "S2L sub-path diversity": For each leaf Ln the path from S to Ln in the primary P2MP LSP is Link (or node or SRLG) diverse with the S to Ln path in the secondary P2MP LSP. If this is correct I also think this is a good suggestion that would be easily fulfilled by defining a new bit in the SVEC object in next draft version. BR Fabien ________________________________ De : Nic Neate [mailto:Nic.Neate@dataconnection.com] Envoy? : mercredi 19 novembre 2008 21:29 ? : qzhao@huawei.com; Mohamad.Chaitou@orange-ftgroup.com Cc : daniel@olddog.co.uk; fabien.verhaeghe@marben-products.com; takeda.tomonori@lab.ntt.co.jp; Jeanlouis.Leroux@orange-ftgroup.com; zali@cisco.com; pce@ietf.org Objet : 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.ietf.org/pipermail/pce/attachments/20081120/267cb277/attachment. htm> ------------------------------ _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce End of Pce Digest, Vol 51, Issue 13 *********************************** _______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
- Re: [Pce] Pce Digest, Vol 51, Issue 13 Young Lee