IETF Logo Mail Archive

shared mesh restoration - e2e recovery signaling draft

"Payam Torab" <ptorab@lopsys.com> Tue, 25 July 2006 22:15 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5VBL-00012E-08 for ccamp-archive@ietf.org; Tue, 25 Jul 2006 18:15:15 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5VBJ-0006IV-JJ for ccamp-archive@ietf.org; Tue, 25 Jul 2006 18:15:14 -0400
Received: from majordom by psg.com with local (Exim 4.60 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1G5V7z-000PdC-LY for ccamp-data@psg.com; Tue, 25 Jul 2006 22:11:47 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO,HTML_MESSAGE autolearn=ham version=3.1.1
Received: from [12.47.115.93] (helo=mailsrv01.vasw) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from <ptorab@lopsys.com>) id 1G5V7y-000Pcq-Oq for ccamp@ops.ietf.org; Tue, 25 Jul 2006 22:11:47 +0000
Received: from NETPTORAB (net-torab.vasw [192.168.254.48]) by mailsrv01.vasw (8.13.1/8.13.1) with ESMTP id k6PMAnsr012412; Tue, 25 Jul 2006 18:10:49 -0400
From: Payam Torab <ptorab@lopsys.com>
To: ccamp@ops.ietf.org
Cc: 'Dave Walters' <dwalters@lopsys.com>
Subject: shared mesh restoration - e2e recovery signaling draft
Date: Tue, 25 Jul 2006 18:11:01 -0400
Organization: Lambda OpticalSystems
Message-ID: <009001c6b037$368d5640$30fea8c0@NETPTORAB>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0091_01C6B015.AF7BB640"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
In-Reply-To: <0901D1988E815341A0103206A834DA07F1A2D4@mdmxm02.ciena.com>
Importance: Normal
X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on localhost
X-Virus-Status: Clean
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1

In the e2e recovery signaling draft
(draft-ietf-ccamp-gmpls-recovery-e2e-signaling-03.txt), there is a procedure
defined for a node on the shared restoration path to notify other nodes
regarding the working LSPs that become vulnerable as a result of switching
to the shared restoration path.
 
It seems there is a similar need to notify these nodes once the shared
restoration path becomes available again. Is this mechanism defined
anywhere?
 
Thanks,
Payam

v2.46.0 | Report a Bug | By Email | System Status