[mpls-tp] Comments on draft-ietf-mpls-tp-fault-01
"Rafi Ram" <RafiR@orckit.com> Thu, 24 June 2010 08:45 UTC
Return-Path: <RafiR@orckit.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 943693A680B for <mpls-tp@core3.amsl.com>;
Thu, 24 Jun 2010 01:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level:
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[AWL=1.300,
BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 z5fmmWKJLNh0 for
<mpls-tp@core3.amsl.com>; Thu, 24 Jun 2010 01:44:57 -0700 (PDT)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [213.31.203.2]) by
core3.amsl.com (Postfix) with ESMTP id 2DBEB3A67EB for <mpls-tp@ietf.org>;
Thu, 24 Jun 2010 01:44:55 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01CB1379.89D9CC84"
Date: Thu, 24 Jun 2010 11:45:02 +0300
Message-ID: <45A67426326F814AAC27DBEC3FC7EEC2037F0D30@tlvmail1>
In-reply-to: <45A67426326F814AAC27DBEC3FC7EEC2037F0D2E@tlvmail1>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Comments on draft-ietf-mpls-tp-fault-01
Thread-Index: AcsTeORebMCAtIzlQO+CuH4XhHLhRgAAI+hQ
References: <45A67426326F814AAC27DBEC3FC7EEC2037F0D2E@tlvmail1>
From: "Rafi Ram" <RafiR@orckit.com>
To: <mpls-tp@ietf.org>
Subject: [mpls-tp] Comments on draft-ietf-mpls-tp-fault-01
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: Thu, 24 Jun 2010 08:45:00 -0000
Dear Authors, I would like to propose addition of a new message type "Link Condition Indication" (LCI). The LCI message can have the following impairment flags (in the spirit of draft-dunbar-so-mpls-detect-impair-mplsping-01 <http://tools.ietf.org/html/draft-dunbar-so-mpls-detect-impair-mplsping- 01.txt> ) : (1) Link performance is reduced (i.e. signal degraded) (2) Link is congested (3) Link rate is reduced A possible motivation for this message may be based on signal degrade detection at LSR (e.g. based on SONET/SDH/OTN link FEC indications), and relay of this condition to the LSP protection state machine (APS). Using the existing LDI message for conveying SD may have the following drawbacks : 1. It does not allow the flexibility to report of various impairment conditions 2. Need to differentiate between "link down" condition (equivalent to SF) and "link reduced" (equivalent to SD), since for APS state machine SF has higher priority than SD Best regards, Rafi