RE: Can Multihop BFD be protected using RLFA backup?

<> Thu, 17 January 2019 09:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CAEF1130F4A for <>; Thu, 17 Jan 2019 01:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uZjGdRL9dbRB for <>; Thu, 17 Jan 2019 01:57:16 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 35742130F30 for <>; Thu, 17 Jan 2019 01:57:16 -0800 (PST)
Received: from (unknown [xx.xx.xx.66]) by (ESMTP service) with ESMTP id 43gKHZ55zSzCrCY; Thu, 17 Jan 2019 10:57:14 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.42]) by (ESMTP service) with ESMTP id 43gKHZ42bfz8sYR; Thu, 17 Jan 2019 10:57:14 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM41.corporate.adroot.infra.ftgroup ([fe80::c845:f762:8997:ec86%19]) with mapi id 14.03.0415.000; Thu, 17 Jan 2019 10:57:14 +0100
From: <>
To: Muthu Arul Mozhi Perumal <>, "" <>
Subject: RE: Can Multihop BFD be protected using RLFA backup?
Thread-Topic: Can Multihop BFD be protected using RLFA backup?
Thread-Index: AQHUrkVUEHIodsCu2E63t3a7nbVDx6WzN9nw
Date: Thu, 17 Jan 2019 09:57:13 +0000
Message-ID: <25009_1547719034_5C40517A_25009_420_1_9E32478DFA9976438E7A22F69B08FF924B78E8A2@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9E32478DFA9976438E7A22F69B08FF924B78E8A2OPEXCLILMA4corp_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 17 Jan 2019 09:57:19 -0000


I think that the fact that “control” packets can benefit of FRR is really implementation dependent. It is also linked to the place where BFD packets are created (RP or LC).
From a theoretical point of view, nothing prevents FRR to be used as for any packet generated by the router itself.
Regarding the encapsulation, if your BFD client is using RFC5883, this will not change during FRR, the FRR will just push labels on top independently.

Again, the possibility to get FRR is really implementation dependent, as the forwarding decision of the BFD packet may not be taken by the network processor of the LC.


From: Rtg-bfd [] On Behalf Of Muthu Arul Mozhi Perumal
Sent: Thursday, January 17, 2019 10:16
Subject: Can Multihop BFD be protected using RLFA backup?

Hi All,

Multihop BFD (RFC 5883) packets are sent over UDP/IP. The encapsulation used is identical to single hop BFD (RFC 5881) except that the UDP destination port is set to 4784.

Now, suppose on the ingress node there is no IP/LFA backup path for the destination address tracked by multihop BFD, but there exists an an RLFA backup path to that destination. In this case, is multihop BFD expected to be protected using the RLFA backup path i.e should multihop BFD packets be sent over the RLFA backup path if the primary path goes down?

If multihop BFD packets are to be sent over the RLFA backup path, what encapsulation should the ingress use? The encapsulation specified in RFC 5883 or the encapsulation specified in RFC 5884 (MPLS BFD)?

Please let me know you opinion.



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.