[Teas] Fw: New Version Notification for draft-lin-teas-gmpls-proactive-protection-00.txt

"Linyi (Yi)" <yi.lin@huawei.com> Fri, 24 April 2020 02:32 UTC

Return-Path: <yi.lin@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 40C9F3A0DEF for <teas@ietfa.amsl.com>; Thu, 23 Apr 2020 19:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ancCrhD-iPlC for <teas@ietfa.amsl.com>; Thu, 23 Apr 2020 19:32:54 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 935713A0DED for <teas@ietf.org>; Thu, 23 Apr 2020 19:32:54 -0700 (PDT)
Received: from lhreml717-chm.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 41502FAE03E8AD8B082A; Fri, 24 Apr 2020 03:32:52 +0100 (IST)
Received: from lhreml717-chm.china.huawei.com ( by lhreml717-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Fri, 24 Apr 2020 03:32:52 +0100
Received: from DGGEMM423-HUB.china.huawei.com ( by lhreml717-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Fri, 24 Apr 2020 03:32:51 +0100
Received: from DGGEMM533-MBS.china.huawei.com ([]) by dggemm423-hub.china.huawei.com ([]) with mapi id 14.03.0487.000; Fri, 24 Apr 2020 10:32:42 +0800
From: "Linyi (Yi)" <yi.lin@huawei.com>
To: Matt Hartley <mhartley.ietf@gmail.com>
CC: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: New Version Notification for draft-lin-teas-gmpls-proactive-protection-00.txt
Thread-Index: AdYZ0YXKekXDdsdDQsy05kCkWwTutw==
Date: Fri, 24 Apr 2020 02:32:42 +0000
Message-ID: <1E1CAD9B89D1B348A942E121648E58DCE1DE221B@DGGEMM533-MBS.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/14K9H5Je0hKbIn17uRJYR4p4psQ>
Subject: [Teas] Fw: New Version Notification for draft-lin-teas-gmpls-proactive-protection-00.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2020 02:32:57 -0000

Hi Matt,

Thank you for your question. Sorry about having not enough time to answer you on line.

If I understand your question correctly, you wander if there is enough time to create the protecting LSP after the failure was predicted and before real failure happens.

Actually we've done a lot of tests, and found that the "failure indication" can be detected at least 500ms ~ several seconds before it becomes a real failure. This time (500ms - 1s) is enough to create the protecting LSP.

This is because:
1) the fiber cable enveloping the fibers can protect them against mechanical stresses. It's very difficult to cut it off within a very short time (e.g., <500ms).
2) some of the parameters of a fiber (e.g., SOP) are very sensitive to the shake of the fiber / fiber cable, even if a digger is just working near the fiber cable without touching it. This makes the early prediction possible.

There are also some other research in the industry which shares very similar conclusions as what we found (please see the example paper we are referring in the slides).


HUAWEI Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian Longgang
Shenzhen 518129, P.R.China
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!

发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
发送时间: 2020年3月9日 20:42
收件人: Bin Yeong Yoon <byyun@etri.re.kr>kr>; Linyi (Yi) <yi.lin@huawei.com>om>; Bin-Yeong Yoon <byyun@etri.re.kr>
主题: New Version Notification for draft-lin-teas-gmpls-proactive-protection-00.txt

A new version of I-D, draft-lin-teas-gmpls-proactive-protection-00.txt
has been successfully submitted by Yi Lin and posted to the IETF repository.

Name:		draft-lin-teas-gmpls-proactive-protection
Revision:	00
Title:		RSVP-TE Extensions in Support of Proactive Protection
Document date:	2020-03-09
Group:		Individual Submission
Pages:		15
URL:            https://www.ietf.org/internet-drafts/draft-lin-teas-gmpls-proactive-protection-00.txt
Status:         https://datatracker.ietf.org/doc/draft-lin-teas-gmpls-proactive-protection/
Htmlized:       https://tools.ietf.org/html/draft-lin-teas-gmpls-proactive-protection-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-lin-teas-gmpls-proactive-protection

   This document describes protocol-specific procedures and extensions
   for Generalized Multi-Protocol Label Switching (GMPLS) Resource
   ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling to
   support Label Switched Path (LSP) Proactive Protection, which create
   the protecting LSP after a failure is predicted and before it
   becomes a real failure.


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat