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

["LE ROUX Jean-Louis RD-CORE-LAN" <jeanlouis.leroux@francetelecom.com>]

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
> 
>