Re: [Mter] Any news?

"Diego Caviglia" <Diego.Caviglia@marconi.com> Wed, 15 March 2006 13:09 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJVkM-00009A-KE; Wed, 15 Mar 2006 08:09:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FJVkL-000095-UC for mter@ietf.org; Wed, 15 Mar 2006 08:09:01 -0500
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FJVkL-0000KB-Sg for mter@ietf.org; Wed, 15 Mar 2006 08:09:01 -0500
Received: from smtpoutuk01.marconi.com ([128.87.251.112]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FJVkK-0007yH-1R for mter@ietf.org; Wed, 15 Mar 2006 08:09:01 -0500
Received: from cvdgwy01.uk.marconicomms.com (cvis26.uk.marconicomms.com [128.87.251.109]) by smtpoutuk01.marconi.com (8.12.11/8.12.11) with ESMTP id k2FCuAC3024657; Wed, 15 Mar 2006 13:08:53 GMT (envelope-from Diego.Caviglia@marconi.com)
Sensitivity:
Subject: Re: [Mter] Any news?
To: "Didier Colle <didier.colle" <didier.colle@intec.UGent.be>
X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003
Message-ID: <OFD1E5F107.67EED27C-ONC1257132.0046E792-C1257132.00478556@uk.marconicomms.com>
From: "Diego Caviglia" <Diego.Caviglia@marconi.com>
Date: Wed, 15 Mar 2006 14:01:11 +0100
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1(5012HF354 | August 26, 2003) at 15/03/2006 13:08:52
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Spam-Score: -2.0 (--)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: mter <mter@ietf.org>
X-BeenThere: mter@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multi-TEchnology Recovery <mter.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mter>, <mailto:mter-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mter>
List-Post: <mailto:mter@ietf.org>
List-Help: <mailto:mter-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mter>, <mailto:mter-request@ietf.org?subject=subscribe>
Errors-To: mter-bounces@ietf.org

Hi Didier,
            that is more or less the same idea I had to solve this issue.

What I'm concerned with is that this usage of TCM prevent carries to use
TCM for 'normal' purposes.

Regards

Diego

[cut]
> You are right this is an issue. However, I believe the typical solution
> to overcome this problem is establishing a tandem connection in each of
> the three segments and making use of the sublayer supervision function
> in order to allow detecting whether the failure occured ON or UPSTREAM
> OF the tandem connection.
> For example: when a failure occurs in segment 1 (thus a<---->D) then D
> will translate the the AU_AIS into a IncAIS (N-bytes in the path
> overhead of the tandem connection D->G). G will detect this IncAIS and
> will simply generate AIS downstream. However, when segment 2 fails (thus
> D<--->G), then G may receive an AU_AIS (and not a IncAIS) implying that
> it has to trigger the GMPLS P&R.
>
> Kind regards,
>
> Didier






_______________________________________________
MTER mailing list
MTER@ietf.org
https://www1.ietf.org/mailman/listinfo/mter