IETF Logo Mail Archive

Re: [mpls] Last Call: draft-ietf-mpls-tp-survive-fwk (Multiprotocol Label Switching Transport Profile Survivability Framework) to Informational RFC

"Shahram Davari" <davari@broadcom.com> Mon, 26 April 2010 17:36 UTC

Return-Path: <davari@broadcom.com>
X-Original-To: mpls@core3.amsl.com
Delivered-To: mpls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B82373A6B01; Mon, 26 Apr 2010 10:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level:
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[AWL=0.255, 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 3ZTuMWxGBzqU; Mon, 26 Apr 2010 10:35:59 -0700 (PDT)
Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by core3.amsl.com (Postfix) with ESMTP id 0BD6A3A6AC3; Mon, 26 Apr 2010 10:35:57 -0700 (PDT)
Received: from [10.16.192.224] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 26 Apr 2010 10:35:33 -0700
X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201
Received: from SJEXCHCCR02.corp.ad.broadcom.com ([10.16.192.130]) by SJEXCHHUB01.corp.ad.broadcom.com ([10.16.192.224]) with mapi; Mon, 26 Apr 2010 10:35:33 -0700
From: Shahram Davari <davari@broadcom.com>
To: "mpls@ietf.org" <mpls@ietf.org>, "mpls-tp@ietf.org" <mpls-tp@ietf.org>
Date: Mon, 26 Apr 2010 10:35:32 -0700
Thread-Topic: Last Call: draft-ietf-mpls-tp-survive-fwk (Multiprotocol Label Switching Transport Profile Survivability Framework) to Informational RFC
Thread-Index: AcrlEKMJKW4co4rgQzWwQkyryVUYFgAVcNFg
Message-ID: <2C2F1EBA8050E74EA81502D5740B4BD693F03BB408@SJEXCHCCR02.corp.ad.broadcom.com>
References: <FD5A8004D1C845CE852F2349DAA15935@your029b8cecfe> <OF7C053C4F.50B60391-ON48257711.0027594D-48257711.0027B4F9@zte.com.cn>
In-Reply-To: <OF7C053C4F.50B60391-ON48257711.0027594D-48257711.0027B4F9@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 67CB116F31G104468192-01-01
Content-Type: multipart/alternative; boundary="_000_2C2F1EBA8050E74EA81502D5740B4BD693F03BB408SJEXCHCCR02co_"
Subject: Re: [mpls] Last Call: draft-ietf-mpls-tp-survive-fwk (Multiprotocol Label Switching Transport Profile Survivability Framework) to Informational RFC
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2010 17:36:01 -0000

Hi,

I have a comment regarding this draft.

This draft states that an MPLS-TP tunnel can be protected in one of its segments without use of a PST. This I assume is something similar to FRR detour protection. What is not clear in the draft is how is OAM (and not control plane) used to detect failure so that an intermediate node can perform protection. As we know an intermediate node can't initiate BFD.

Thanks,
Shahram

v2.23.0 | Report a Bug | By Email