[mpls-tp] Comment on http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt

Maarten Vissers <maarten.vissers@huawei.com> Thu, 17 December 2009 07:45 UTC

Return-Path: <maarten.vissers@huawei.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 2B0B43A6835; Wed, 16 Dec 2009 23:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[AWL=0.354, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 ObU-8AABAKQG; Wed, 16 Dec 2009 23:45:48 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id F03B23A6831; Wed, 16 Dec 2009 23:45:47 -0800 (PST)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KUS00C1QDJLY4@szxga01-in.huawei.com>; Thu, 17 Dec 2009 15:45:21 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KUS00JXVDJLOM@szxga01-in.huawei.com>; Thu, 17 Dec 2009 15:45:21 +0800 (CST)
Received: from M00900002 (vissersm.demon.nl [83.160.252.43]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KUS00JBFDJGMR@szxml02-in.huawei.com>; Thu, 17 Dec 2009 15:45:21 +0800 (CST)
Date: Thu, 17 Dec 2009 08:45:15 +0100
From: Maarten Vissers <maarten.vissers@huawei.com>
In-reply-to: <4B29B534.8040906@pi.nu>
To: 'Loa Andersson' <loa@pi.nu>, mpls-tp@ietf.org, mpls@ietf.org, ccamp@ietf.org, pwe3@ietf.org
Message-id: <001901ca7eec$e2179b60$6c02a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acp+0nx4dPl6Lc1rTuiovDVmelzglwAFWAQg
Subject: [mpls-tp] Comment on http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt
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, 17 Dec 2009 07:45:49 -0000

Some comments on the content of this draft:

In section 2.1 it is stated: 
"  <..>
   For example an AIS message may be sent during a protection switching
   event and would cease being sent if the protection switch was
   successful in restoring the link.

   Its primary purpose is to suppress alarms in the MPLS-TP layer
   network above the level at which the defect occurs.  The AIS message
   MAY be used to trigger recovery mechanisms.  It should be noted that
   such use would be subject to false positives, e.g. unnecessary
   protection switching events in the client layer."

It is not correct to state that AIS sending is stopped if the protection
switch was succesful. The reason is that the AIS insertion is done by a MEP
Sink function that is upstream of the protection switch selector process,
and this MEP Sink function is as such unaware of the presence of a
protection switch process and of the state of the protection switch process.

AIS in packet transport networks must **not** used to trigger recovery
mechanisms. Reason is that AIS OAM messages in packet transport network are
to be generated within 1 second after the detection of the signal fail type
defect detection and be generated with a periodicity of 1 second. These
times are much too long to trigger any recovery mechanism.

The 1 second time requirement to generate the first AIS message is derived
from the 2.5 +/- 0.5 second fault cause to failure integration timer as
specified in G.7710. Generation of the first AIS message within a period of
1 second will leave enough time to reach the downstream MEP Sink function
and suppress the fault cause that report the interruption of the connection.

Protection switching in packet transport networks is triggered by e.g. loss
of continuity and misconnection defects.

In section 2.2 it is stated:
"  The LDI message is generated in response to detecting a fatal failure
   in the server layer.  The LDI message MUST NOT be sent until the
   defect has been determined to be fatal.  For example during a
   protection switching event LDI messages are not sent.  However if the
   protection switch was unsuccessful in restoring the link within the
   expected repair time, an LDI message MUST be sent."
and in section 2.1 it is stated:
"  The MPLS-TP Alarm Indication Signal (AIS) message is generated in
   response to detecting defects in the server layer.  The AIS message
   SHOULD be sent as soon is the condition is detected, that is before
   any determination has been made as to whether the condition is fatal."

This draft suggest that it is possible for a MEP Sink function to determine
if the fault is *fatal* or *not fatal*. This is not possible for a MEP Sink
function. The reason is that a MEP Sink function has no knowledge of the
presence or state of a protection switch process associated with the
connection. E.g. the protection switch process may be in a downstream node.

It is also not necessary to make AIS generation conditional on e.g.
protection switch actions. Reason is that a protection switch process will
select traffic from either a working connection input port, or a protection
connection input port. Any traffic present on the not selected input port
will drop at this input port and not be forwarded to the protection switch
process output port. At the output port AIS messages will be present as long
as the protection switch process selects its traffic from the failed
connection; once the protection switch process selects its traffic from the
non-failed connection AIS messages will not longer be forwarded to the
output port.

This draft should as such not become a WG document.

Regards,
Maarten

-----Original Message-----
From: mpls-tp-bounces@ietf.org [mailto:mpls-tp-bounces@ietf.org] On Behalf
Of Loa Andersson
Sent: donderdag 17 december 2009 5:36
To: mpls-tp@ietf.org; mpls@ietf.org; ccamp@ietf.org; pwe3@ietf.org
Subject: [mpls-tp] Poll om making
http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt a working group
document

All,

this is to start a two week poll on making

http://www.ietf.org/id/draft-sfv-mpls-tp-fault-01.txt

an MPLS working group document.

Send a mail to the mpls-tp@ietf.org mailing list, indicating "yes/support"
or "no/do not support".

Comments on the content of the draft should be sent to the same mailing list
with a different subject line.

The poll ends Friday 15 Jan, 2010.

/Loa
-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13
_______________________________________________
mpls-tp mailing list
mpls-tp@ietf.org
https://www.ietf.org/mailman/listinfo/mpls-tp