[mpls] Fast Reroute - Path message onto a bypass tunnel

Harish Kumtakar <harishk16@yahoo.co.in> Fri, 01 October 2004 16:33 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21900; Fri, 1 Oct 2004 12:33:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CDQTY-0002ZE-4q; Fri, 01 Oct 2004 12:41:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDP8V-0000fu-DH; Fri, 01 Oct 2004 11:15:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CDKcE-0003aX-KU for mpls@megatron.ietf.org; Fri, 01 Oct 2004 06:26:18 -0400
Received: from web8502.mail.in.yahoo.com (web8502.mail.in.yahoo.com [202.43.219.164]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA14638 for <mpls@lists.ietf.org>; Fri, 1 Oct 2004 06:26:15 -0400 (EDT)
Message-ID: <20041001102524.74202.qmail@web8502.mail.in.yahoo.com>
Received: from [203.200.200.162] by web8502.mail.in.yahoo.com via HTTP; Fri, 01 Oct 2004 11:25:24 BST
Date: Fri, 01 Oct 2004 11:25:24 +0100
From: Harish Kumtakar <harishk16@yahoo.co.in>
To: mpls@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [mpls] Fast Reroute - Path message onto a bypass tunnel
X-BeenThere: mpls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mpls>
List-Post: <mailto:mpls@lists.ietf.org>
List-Help: <mailto:mpls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@lists.ietf.org?subject=subscribe>
Sender: mpls-bounces@ietf.org
Errors-To: mpls-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 8bit

I've a question on draft
'draft-ietf-mpls-rsvp-lsp-fastreroute-07.txt'
The question is related to the Path message handling
sent over the bypass tunnel (facility backup) for the
protected LSP before/after failure. 

Consider the following example,

               [R1]---[R2]----[R3]----[R4]---[R5]
                          \\         //
                           [R6]===[R7]

                Protected LSP : [R1->R2->R3->R4->R5]
                Bypass LSP Tunnel: [R2->R6->R7->R4]

Section 7.4.4 of the draft says,

   More specifically, the PLR MUST:

     - remove all the sub-objects proceeding the first
address belonging
        to the MP.

     - replace this first MP address with an IP
address of the MP.
        (Note that this could be same address that was
just removed.)

So, the ERO of the Path message sent over the bypass
tunnel contains the IP address of MP (i.e R4) as its
sub-object. (My understanding is that, all the
sub-objects that appear before MP's address are
removed from ERO)

Now, when R6 recieves this Path message, as per the
ERO processing rules specified in Section 4.3.4 of RFC
3209:Extensions to RSVP for LSP Tunnels, should it not
return "Bad initial subobject" error to PLR R2? I know
I'm definitely missing something here OR my
understanding of the draft itself is partially
incorrect.

Please clear the grey area,

TIA, Regards,
-Harish


=====

 

________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls