Re: Service Redundancy using BFD

Sami Boutros <> Tue, 28 November 2017 18:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 77A04126CE8 for <>; Tue, 28 Nov 2017 10:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ABBRi_S_NIGn for <>; Tue, 28 Nov 2017 10:34:13 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 363F0126557 for <>; Tue, 28 Nov 2017 10:34:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-vmware-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=5RzQDlCwcUm+m6R4IYR+gZRjK6VsIzx9i9Pi4+Y6EJc=; b=qfSkdgYx/sgbR3H4FGDXbxwNHLqTsJslBv+Tm72+dAMGz823tV0QGgYqCSNZ6W3atx8r0J3zYIuRQPDXuYHR6hOGXM9Qm+I88I30N2RjMR9M0L1bx4L02wT6g2Gs8P2/mD6GUTSrJr18Fm7xhg9UAg34ySS3+/SAtpqWLz7Vd4E=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id; Tue, 28 Nov 2017 18:34:10 +0000
Received: from ([]) by ([]) with mapi id 15.20.0282.002; Tue, 28 Nov 2017 18:34:09 +0000
From: Sami Boutros <>
To: Greg Mirsky <>, Ankur Dubey <>
CC: "" <>, Reshad Rahman <>
Subject: Re: Service Redundancy using BFD
Thread-Topic: Service Redundancy using BFD
Thread-Index: AQHTZ/M82vlye4FAgk+FmQYa86ul9aMp+JeA//+gWIA=
Date: Tue, 28 Nov 2017 18:34:09 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR05MB3231; 20:A3KcnampU/k+ekyGS1/M1rrqSx+RgbwBC7xyw9b7eo1oHqoaBOx+WfGCYzB22YZV3UJ2GGDDQ1QuP0ThXCLInAu7U1J0SR5k8LKcaayZGFjP3U7rQW6wcj/oOMBOh2uAKevcQr9EtslXZYtR27Z9ZgKQMUPiVEw31C0Eys4qX1E=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;SSOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10009020)(346002)(376002)(39860400002)(366004)(199003)(189002)(24454002)(53754006)(86362001)(66066001)(76176999)(50986999)(68736007)(81166006)(99286004)(4326008)(101416001)(53936002)(3480700004)(81156014)(53546010)(2900100001)(39060400002)(6246003)(236005)(189998001)(6306002)(229853002)(606006)(54896002)(82746002)(83716003)(316002)(2906002)(54356999)(966005)(6512007)(8676002)(36756003)(8936002)(2950100002)(478600001)(33656002)(6636002)(97736004)(6506006)(77096006)(3280700002)(105586002)(106356001)(5660300001)(14454004)(7736002)(3846002)(25786009)(6436002)(6486002)(6116002)(54906003)(110136005)(102836003)(3660700001); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR05MB3231;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
x-ms-office365-filtering-correlation-id: 2ac31819-ff76-4f7d-054e-08d5368e9d34
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603199); SRVR:MWHPR05MB3231;
x-ms-traffictypediagnostic: MWHPR05MB3231:
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(61668805478150)(10436049006162)(120809045254105)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(5005006)(8121501046)(3002001)(3231022)(93006095)(93001095)(10201501046)(6041248)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123564025)(20161123562025)(20161123558100)(6072148)(201708071742011); SRVR:MWHPR05MB3231; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:MWHPR05MB3231;
x-forefront-prvs: 0505147DDB
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_A28D43043AC4478FAAEB9BC97585E76Evmwarecom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2ac31819-ff76-4f7d-054e-08d5368e9d34
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2017 18:34:09.1137 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b39138ca-3cee-4b4a-a4d6-cd83d9dd62f0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB3231
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 28 Nov 2017 18:34:16 -0000

Hi Greg,

The network in which the draft apply is neither an MPLS-TP or a G.8031 network.
It is for an IP packet network, and the mechanism described that we beleive is useful is when a BFD session used to monitor liveness between 2 nodes (doing active/standby redundancy for L2/L3 or L4-L7 services) goes down, it is useful when the BFD session comes back up that the node that didn’t fail tell the other node. This notification will allow non-preemptive services to continue to run on the node that didn’t fail.


From: Greg Mirsky <<>>
Date: Tuesday, November 28, 2017 at 8:16 AM
To: Ankur Dubey <<>>
Cc: "<>" <<>>, Reshad Rahman <<>>, Sami Boutros <<>>
Subject: Re: Service Redundancy using BFD

Hi Ankur,
usually this problem, as I understand it from the document, is handled by the special protection coordination protocol as, for example, in RFC 6378 or G.8031. PSC or APS reflect roles of working and protecting paths and communicate over the protecting path.


On Mon, Nov 27, 2017 at 6:47 PM, Ankur Dubey <<>> wrote:
Hi all,

Please review and provide comments for the following draft:<>

Summary of draft:

This draft proposes a new BFD diag code via which a node running a BFD session with another node, can inform the other node after a BFD session times out, that it didn’t go down and did live through the failure.

Such notification is useful for a set of nodes providing Active/Standby redundancy. When these nodes are running multiple L2/L3/L4-L7 services  in non-revertive mode of redundancy, the standby node taking over as active for non-revertive services after BFD times out needs to indicate in the BFD packet that it outlived the other failed old active node. The new diag code will be used for this purpose. When this diag code is set in the BFD packets, it will provide an indication to the failed old active node that it MUST NOT activate the non-revertive services when it comes up.

For providing a per service level failover, a node activating certain non-revertive services needs to indicate that it is Active ONLY for those non-revertive services. This can be done by using a unique bitmap where each bit position is uniquely identifying a service. This unique bitmap is configured on all nodes by a network controller. When there is at least one non-revertive service for which a node is not active AND it is active for at least 1 non-revertive service, this node will set bits identifying the active services in the bitmap and send it in the payload of the BFD packet.