[Pce] We welcome your comments and suggestions about it//FW: New Version Notification for draft-kondreddy-pce-frr-boundary-node-app-00.txt
KONDREDDY VENUGOPAL REDDY <venugopalreddyk@huawei.com> Wed, 18 July 2012 13:01 UTC
Return-Path: <venugopalreddyk@huawei.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64C6721F86DA for <pce@ietfa.amsl.com>; Wed, 18 Jul 2012 06:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EfBl2+qD9-sH for <pce@ietfa.amsl.com>; Wed, 18 Jul 2012 06:01:54 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 8848321F86D1 for <pce@ietf.org>; Wed, 18 Jul 2012 06:01:54 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AID04070; Wed, 18 Jul 2012 09:02:44 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 18 Jul 2012 06:00:31 -0700
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by dfweml408-hub.china.huawei.com (10.193.5.134) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 18 Jul 2012 06:00:29 -0700
Received: from blrprnc09ns (10.18.96.98) by szxeml424-hub.china.huawei.com (10.82.67.163) with Microsoft SMTP Server id 14.1.323.3; Wed, 18 Jul 2012 21:00:24 +0800
From: KONDREDDY VENUGOPAL REDDY <venugopalreddyk@huawei.com>
To: pce@ietf.org
Date: Wed, 18 Jul 2012 18:30:23 +0530
Message-ID: <000301cd64e5$4bb90f00$e32b2d00$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1d4IBJTImivNrQRzGNnZ5SB0xFagG/qjLQ
Content-Language: en-us
X-Originating-IP: [10.18.96.98]
X-CFilter-Loop: Reflected
Subject: [Pce] We welcome your comments and suggestions about it//FW: New Version Notification for draft-kondreddy-pce-frr-boundary-node-app-00.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 18 Jul 2012 13:01:55 -0000
Hi, We have written a new draft about PCE's applicability and its role in boundary node protection. It has covered the aspects of finding merge point in case of facility backup for FRR in various cases and to compute bypass path. It is complex for a point of local repair(PLR) node to find the merge point(MP) in case of boundary node protection, because the PLR doesn't have the full TED visibility. And, It becomes more complicated to find merge point when confidentiality(path key) is enabled. Draft addresses about these cases. Request you to have a look at draft. We welcome your comments and suggestions. Thanks. Venu -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: Monday, July 09, 2012 8:08 PM To: dhruv.dhody@huawei.com Cc: venugopalreddyk@huawei.com Subject: New Version Notification for draft-kondreddy-pce-frr-boundary-node-app-00.txt A new version of I-D, draft-kondreddy-pce-frr-boundary-node-app-00.txt has been successfully submitted by Dhruv Dhody and posted to the IETF repository. Filename: draft-kondreddy-pce-frr-boundary-node-app Revision: 00 Title: Applicability of Path Computation Element (PCE) for Fast Reroute (FRR) Boundary Node protection. Creation date: 2012-07-09 WG ID: Individual Submission Number of pages: 14 URL: http://www.ietf.org/internet-drafts/draft-kondreddy-pce-frr-boundary-node-app-00.txt Status: http://datatracker.ietf.org/doc/draft-kondreddy-pce-frr-boundary-node-app Htmlized: http://tools.ietf.org/html/draft-kondreddy-pce-frr-boundary-node-app-00 Abstract: Path computation element (PCE) can be used to compute a label switched path that spans across multiple domains. This document explain the mechanism of Fast Re-Route (FRR) where a point of local repair (PLR) needs to find the appropriate merge point (MP) to do bypass path computation using PCE. In case of boundary node protection when PCE confidentiality (path key) is enabled, new mechanisms are suggested in this document. The IETF Secretariat
- [Pce] We welcome your comments and suggestions ab… KONDREDDY VENUGOPAL REDDY