RE: Question about Reoptimization draft-ietf-ccamp-loose-path-reopt

"LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@francetelecom.com> Tue, 15 November 2005 13:42 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ec153-0002Li-R9 for ccamp-archive@megatron.ietf.org; Tue, 15 Nov 2005 08:42:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24992 for <ccamp-archive@ietf.org>; Tue, 15 Nov 2005 08:42:05 -0500 (EST)
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ec1MC-0004di-Cd for ccamp-archive@ietf.org; Tue, 15 Nov 2005 09:00:27 -0500
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD)) id 1Ec0wt-000GZM-2t for ccamp-data@psg.com; Tue, 15 Nov 2005 13:34:11 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0
Received: from [195.101.245.15] (helo=p-mail1.rd.francetelecom.com) by psg.com with esmtp (Exim 4.52 (FreeBSD)) id 1Ec0wr-000GZ8-RL for ccamp@ops.ietf.org; Tue, 15 Nov 2005 13:34:10 +0000
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Tue, 15 Nov 2005 14:34:02 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Question about Reoptimization draft-ietf-ccamp-loose-path-reopt
Date: Tue, 15 Nov 2005 14:34:01 +0100
Message-ID: <D109C8C97C15294495117745780657AE03956C62@ftrdmel1.rd.francetelecom.fr>
Thread-Topic: Question about Reoptimization draft-ietf-ccamp-loose-path-reopt
Thread-Index: AcXp6H4AXImXS1+9Tn+I7+nXh2bqZwAAFLWw
From: LE ROUX Jean-Louis RD-CORE-LAN <jeanlouis.leroux@francetelecom.com>
To: faisal@telecom.lth.se, faisal@lums.edu.pk, ccamp@ops.ietf.org
X-OriginalArrivalTime: 15 Nov 2005 13:34:02.0285 (UTC) FILETIME=[3DC43DD0:01C5E9E9]
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: quoted-printable

Hi Faisal,

Make before break reoptimization requires a new LSP id,  which is under control of the head-end LSR.

Regards,

JL

> -----Message d'origine-----
> De : owner-ccamp@ops.ietf.org 
> [mailto:owner-ccamp@ops.ietf.org] De la part de Faisal Aslam
> Envoyé : mardi 15 novembre 2005 13:17
> À : ccamp@ops.ietf.org
> Objet : Question about Reoptimization 
> draft-ietf-ccamp-loose-path-reopt
> 
> Hi,
> 
> I want to know that if a border router is working in 
> "Mid-point explicit notification mode" and a link or node has 
> to go down due to maintenance reasons. Then why not the 
> mid-point can reoptimize the (sub portion of) path  locally 
> "without" notifying to the ingress node?
> The draft says in above case ingress MUST decided to 
> reoptimize (no other choice) then why to wait for ingress 
> decision in the first place and not to perform reoptimization locally?
> I think that the local node can remember the next-loose-hop 
> node with which the path was originally signaled and later, 
> in the event of local maintenance it should reoptimized 
> without involving ingress (hence save signaling/time).
> 
> Faisal
> 
>