Re: [mpls] New Draft Notification: draft-dong-mpls-rsvp-te-plr-designation-00

venkatesan mahalingam <venkatflex@gmail.com> Tue, 20 July 2010 11:59 UTC

Return-Path: <venkatflex@gmail.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 093333A68F1 for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 04:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 EdP4LK3oL7yh for <mpls@core3.amsl.com>; Tue, 20 Jul 2010 04:59:33 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 225A53A6872 for <mpls@ietf.org>; Tue, 20 Jul 2010 04:59:33 -0700 (PDT)
Received: by pvd12 with SMTP id 12so3085393pvd.31 for <mpls@ietf.org>; Tue, 20 Jul 2010 04:59:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=3cr8N9gWh0zuTLu1S2Df3ZqblX6rB6YKEt3JEnIiAlM=; b=kWZ2ZtPPMfweauIrU4l5wEXPGrF0l4E29MhDbSeCacHuvzg4TcqM8N0E6g383I0Hzj jAYhi6U4sNvmDN2U5iuBffU+VLnwk2WS5vMAvTMIpFOTkdemO78pY1XsnnS5sq0Nkc2s jXAsR/JT4C9w7apNCAdMNlynIde1fYdw1ji7Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VnPSImPlaImXY+NX91bCVhZ5c9F7IBErA7rbVKU7+b+TuHdpAS1ZlrJw5jU12PLTkq 016YcHURKFsYwvfjBf+DQ1XZ4KIxJeFdgoshvKLV3gNv/zFxGWi1x7FTshe/1E62A+WN rgUgq4GWR0yyYLZMWGbl+iCoKMtnu1QJZMgpI=
MIME-Version: 1.0
Received: by 10.142.215.7 with SMTP id n7mr6577190wfg.194.1279627188210; Tue, 20 Jul 2010 04:59:48 -0700 (PDT)
Received: by 10.142.77.1 with HTTP; Tue, 20 Jul 2010 04:59:48 -0700 (PDT)
In-Reply-To: <007101cb27b0$5b3c58c0$82626e0a@china.huawei.com>
References: <007101cb27b0$5b3c58c0$82626e0a@china.huawei.com>
Date: Tue, 20 Jul 2010 17:29:48 +0530
Message-ID: <AANLkTim7PAn8b-K0dq-i-k6Qx3LJkm5HwaV02QHDFFQo@mail.gmail.com>
From: venkatesan mahalingam <venkatflex@gmail.com>
To: Jie Dong <dongjie_dj@huawei.com>, mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="000e0cd3039effab4b048bd06bb0"
Subject: Re: [mpls] New Draft Notification: draft-dong-mpls-rsvp-te-plr-designation-00
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 11:59:34 -0000

Hi,
This draft is good in selecting the PLRs in the initial LSP setup itself.
But can this draft handle the dynamic PLR node change?
Do you have any thought on constrcuting the new TLVs to send the new EROs in
the established LSP to indicate the new PLR nodes?

Do you really think that administrator should know about all the transit
nodes of the LSP? I think, this is possible with the help of CSPF but
collecting the informations about transit node's resources and other
informations may be tough.

Thanks,
Venkat.
On Tue, Jul 20, 2010 at 7:37 AM, Jie Dong <dongjie_dj@huawei.com> wrote:

>
> Dear all,
>
> We have submitted a new internet draft "Designation of PLRs in RSVP-TE Fast
> Reroute"
>
> The URL is:
> http://tools.ietf.org/html/draft-dong-mpls-rsvp-te-plr-designation-00
>
> The abstract is as follows:
>
> This document defines RSVP-TE extensions which enable the ingress node to
> designate particular LSRs along the path as Points of Local Repair (PLRs)
> of
> the protected LSP, and further indicate the protection type of each PLR.
> These mechanisms could enhance the control over the establishment of backup
> LSPs, and also could save the resources needed for establishing and
> maintaining unnecessary backup LSPs.
>
> Any comments and suggestions are appreciated.
>
>
> Best regards,
> Jie
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>



-- 
Best Regards,
Venkatesan Mahalingam.