Re: [Bier] draft-zhang-bier-source-protection

<zhang.zheng@zte.com.cn> Mon, 21 October 2019 09:30 UTC

Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDEC12008A; Mon, 21 Oct 2019 02:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rY8d2ysfkGyx; Mon, 21 Oct 2019 02:30:43 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 F19541201DB; Mon, 21 Oct 2019 02:30:38 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id B90DF6953667E86B9434; Mon, 21 Oct 2019 17:30:34 +0800 (CST)
Received: from njxapp03.zte.com.cn ([10.41.132.202]) by mse-fl2.zte.com.cn with SMTP id x9L9UF93076426; Mon, 21 Oct 2019 17:30:15 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid203; Mon, 21 Oct 2019 17:30:14 +0800 (CST)
Date: Mon, 21 Oct 2019 17:30:14 +0800
X-Zmail-TransId: 2afb5dad7aa664e33ae9
X-Mailer: Zmail v1.0
Message-ID: <201910211730144408211@zte.com.cn>
In-Reply-To: <93425EF9-97C5-4431-8DEF-15F3C6F797ED@cisco.com>
References: 93425EF9-97C5-4431-8DEF-15F3C6F797ED@cisco.com
Mime-Version: 1.0
From: zhang.zheng@zte.com.cn
To: mankamis@cisco.com
Cc: draft-zhang-bier-source-protection@ietf.org, bier@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn x9L9UF93076426
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/A9YNgUwNz_ITA9uS7qMQv7tQ3m8>
Subject: Re: [Bier] draft-zhang-bier-source-protection
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Oct 2019 09:30:46 -0000

Hi Mankamana,






Thanks for your comments.


Yes. The source can be protected by multihoming to two BFIRs. The situation is one of the protection deployment. 


If one of the link between BFIR and some BFERs brokes, IGP convergence will help the recovering. There is no need to switch to the other BFIR.


But if the choosed BFIR is not longer live, BFER will not switch to the other BFIR until the timeout of BFIR. This may be a long breaking.


So the dection function can fasten the switchover procedure.






Best regards,


Sandy







原始邮件



发件人:MankamanaMishra(mankamis) <mankamis@cisco.com>
收件人:draft-zhang-bier-source-protection@ietf.org <draft-zhang-bier-source-protection@ietf.org>;
抄送人:bier@ietf.org <bier@ietf.org>;
日 期 :2019年10月20日 03:11
主 题 :[Bier] draft-zhang-bier-source-protection




Authors, 
Wondering if we really need this procedure for source protection. I am assuming you are considering the case where source ie behind LAN. It is correct, that join can land any where and possibly different set of Egress routers would join different ingress router. But if there is any failure, will IGP not take care of it ? If reachability to source changes, why does Egress router need to know this and try to join some other ingress router ? 

Mankamana
_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier