IETF Logo Mail Archive

Re: [Bier] WG adoption call for draft-chen-bier-frr-02

Michael Menth <menth@uni-tuebingen.de> Tue, 16 March 2021 19:03 UTC

Return-Path: <menth@uni-tuebingen.de>
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 3292D3A089C for <bier@ietfa.amsl.com>; Tue, 16 Mar 2021 12:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 9LhK4A1UhEZH for <bier@ietfa.amsl.com>; Tue, 16 Mar 2021 12:03:14 -0700 (PDT)
Received: from mx04.uni-tuebingen.de (mx04.uni-tuebingen.de [IPv6:2001:7c0:300c:3105::8602:5d6]) (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 828483A08EA for <bier@ietf.org>; Tue, 16 Mar 2021 12:02:44 -0700 (PDT)
Received: from [192.168.0.69] (HSI-KBW-078-043-000-193.hsi4.kabel-badenwuerttemberg.de [78.43.0.193]) by mx04.uni-tuebingen.de (Postfix) with ESMTPSA id 8E997209AB31; Tue, 16 Mar 2021 20:02:39 +0100 (CET)
To: Huaimo Chen <huaimo.chen@futurewei.com>, "bier@ietf.org" <bier@ietf.org>
References: <202103161440487606255@zte.com.cn> <CA+wi2hPLG_Og=rDerVqK7hMjkjUGxzjpQnZMSFMf965UVLCxNA@mail.gmail.com> <54b33eef-31c1-5ceb-0bcf-051149d7e876@uni-tuebingen.de> <MN2PR13MB40870D62A90DBC972AE31B48F26B9@MN2PR13MB4087.namprd13.prod.outlook.com>
From: Michael Menth <menth@uni-tuebingen.de>
Message-ID: <5e30061a-68fd-6141-fe73-258a2e03d2cb@uni-tuebingen.de>
Date: Tue, 16 Mar 2021 20:02:40 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <MN2PR13MB40870D62A90DBC972AE31B48F26B9@MN2PR13MB4087.namprd13.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/HmgZiB93I3V5n7lb9Fxt7yYFO0g>
Subject: Re: [Bier] WG adoption call for draft-chen-bier-frr-02
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: Tue, 16 Mar 2021 19:03:16 -0000

Hi Huaimo,

Am 16.03.2021 um 17:02 schrieb Huaimo Chen:

> [HC]: When the routing underlay supports IP FRR, the BIER should also 
> provide BIER FRR since the BIER packets are forwarded using the BIFTs. 
> When failures happen in the network, the BIER packets are still forwarded 
> using the old BIFTs until the old BIFTs are updated according to the 
> updated network topology after the failures.

Right. Some form of BIER-FRR is helpful. But just tunnelling the traffic
over the underlay in case of a failure (that may be the frr action) let
the traffic benefit from the underlay's frr mechanism. That's what
tunnel-based bier-frr is about.

Regards

Michael

-- 
Prof. Dr. habil. Michael Menth
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505
fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de
http://kn.inf.uni-tuebingen.de

v2.46.0 | Report a Bug | By Email | System Status