IETF Logo Mail Archive

Re: [mpls-tp] Alarm Reporting (aka AIS)

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Wed, 08 December 2010 19:03 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: mpls-tp@core3.amsl.com
Delivered-To: mpls-tp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1466B3A686A for <mpls-tp@core3.amsl.com>; Wed, 8 Dec 2010 11:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.159
X-Spam-Level:
X-Spam-Status: No, score=-2.159 tagged_above=-999 required=5 tests=[AWL=-0.160, BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XTc8hxFfLE2W for <mpls-tp@core3.amsl.com>; Wed, 8 Dec 2010 11:03:11 -0800 (PST)
Received: from ilptbmg01.ecitele.com (ilptbmg01-out.ecitele.com [147.234.242.234]) by core3.amsl.com (Postfix) with ESMTP id E9AD03A6823 for <mpls-tp@ietf.org>; Wed, 8 Dec 2010 11:03:10 -0800 (PST)
X-AuditID: 93eaf2e7-b7b0bae000000a12-d9-4cffd6c7fb04
Received: from ILPTEXCH02.ecitele.com ( [147.234.245.181]) by ilptbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id E9.9C.02578.7C6DFFC4; Wed, 8 Dec 2010 21:04:39 +0200 (IST)
Received: from ILPTMAIL02.ecitele.com ([147.234.244.213]) by ILPTEXCH02.ecitele.com ([147.234.245.181]) with mapi; Wed, 8 Dec 2010 21:05:55 +0200
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: t.petch <ietfc@btconnect.com>
Date: Wed, 8 Dec 2010 21:01:07 +0200
Thread-Topic: [mpls-tp] Alarm Reporting (aka AIS)
Thread-Index: AcuXAoDrxoecr7xlRhqRBnas9B6VGgAB8QpG
Message-ID: <A3C5DF08D38B6049839A6F553B331C76D6B78ED55A@ILPTMAIL02.ecitele.com>
References: <077E41CFFD002C4CAB7DFA4386A532640308F66E@DEMUEXC014.nsn-intra.net> <6D3D47CB84BDE349BC23BF1C94E316E44003B2D47B@EMV62-UKRD.domain1.systemhost.net>, <006201cb96f9$c440df40$4001a8c0@gateway.2wire.net>
In-Reply-To: <006201cb96f9$c440df40$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
Cc: "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Subject: Re: [mpls-tp] Alarm Reporting (aka AIS)
X-BeenThere: mpls-tp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MPLS-TP Mailing list <mpls-tp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls-tp>
List-Post: <mailto:mpls-tp@ietf.org>
List-Help: <mailto:mpls-tp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls-tp>, <mailto:mpls-tp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2010 19:03:12 -0000

Tom,
... snipping to the key statement in your email...
==============================
     Perhaps we should note that in a packet layer network, there is no signal and so 
     signal fail can never be asserted so AIS is a null condition.  
     In which case, G.tpoam is spot on.
==============================
... snipped to the end ...

Support!!!

My 2c,
     Sasha

v2.8.7 | Report a Bug | By Email