BFD Stability
draft-ietf-bfd-stability-01
|
| Document |
Type |
|
Active Internet-Draft (bfd WG)
|
|
Last updated |
|
2018-03-30
(latest revision 2017-11-21)
|
|
Replaces |
|
draft-ashesh-bfd-stability
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
xml
html
bibtex
|
| Stream |
WG state
|
|
In WG Last Call
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group A. Mishra
Internet-Draft O3b Networks
Intended status: Standards Track M. Jethanandani
Expires: May 25, 2018 Cisco Systems
A. Saxena
Ciena Corporation
S. Pallagatti
Juniper Networks
M. Chen
Huawei
P. Fan
China Mobile
November 21, 2017
BFD Stability
draft-ietf-bfd-stability-01
Abstract
This document describes extensions to the Bidirectional Forwarding
Detection (BFD) protocol to measure BFD stability. Specifically, it
describes a mechanism for detection of BFD frame loss.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 25, 2018.
Mishra, et al. Expires May 25, 2018 [Page 1]
Internet-Draft BFD Stability November 2017
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. BFD Null-Authentication TLV . . . . . . . . . . . . . . . . . 3
4. Theory of Operations . . . . . . . . . . . . . . . . . . . . 3
4.1. Loss Measurement . . . . . . . . . . . . . . . . . . . . 3
5. IANA Requirements . . . . . . . . . . . . . . . . . . . . . . 4
6. Security Consideration . . . . . . . . . . . . . . . . . . . 4
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 4
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
9. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
The Bidirectional Forwarding Detection (BFD) [RFC5880] protocol
operates by transmitting and receiving control frames, generally at
high frequency, over the datapath being monitored. In order to
prevent significant data loss due to a datapath failure, the
tolerance for lost or delayed frames in the Detection Time, as
defined in BFD [RFC5880] is set to the smallest feasible value.
This document proposes a mechanism to detect lost frames in a BFD
session in addition to the datapath fault detection mechanisms of
BFD. Such a mechanism presents significant value to measure the
stability of BFD sessions and provides data to the operators for the
cause of a BFD failure.
This document does not propose BFD extension to measure data traffic
loss or delay on a link or tunnel and the scope is limited to BFD
frames.
Mishra, et al. Expires May 25, 2018 [Page 2]
Internet-Draft BFD Stability November 2017
2. Use Cases
Legacy BFD cannot detect any BFD frame loss if loss does not last for
Show full document text