draft-ietf-bfd-stability-01.txt   draft-ietf-bfd-stability-02.txt 
Network Working Group A. Mishra Network Working Group A. Mishra
Internet-Draft O3b Networks Internet-Draft O3b Networks
Intended status: Standards Track M. Jethanandani Intended status: Standards Track M. Jethanandani
Expires: May 25, 2018 Cisco Systems Expires: November 26, 2018
A. Saxena A. Saxena
Ciena Corporation Ciena Corporation
S. Pallagatti S. Pallagatti
Juniper Networks Juniper Networks
M. Chen M. Chen
Huawei Huawei
P. Fan P. Fan
China Mobile China Mobile
November 21, 2017 May 25, 2018
BFD Stability BFD Stability
draft-ietf-bfd-stability-01 draft-ietf-bfd-stability-02
Abstract Abstract
This document describes extensions to the Bidirectional Forwarding This document describes extensions to the Bidirectional Forwarding
Detection (BFD) protocol to measure BFD stability. Specifically, it Detection (BFD) protocol to measure BFD stability. Specifically, it
describes a mechanism for detection of BFD frame loss. describes a mechanism for detection of BFD frame loss.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 25, 2018. This Internet-Draft will expire on November 26, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. BFD Null-Authentication TLV . . . . . . . . . . . . . . . . . 3 3. BFD Null-Authentication TLV . . . . . . . . . . . . . . . . . 3
4. Theory of Operations . . . . . . . . . . . . . . . . . . . . 3 4. Theory of Operations . . . . . . . . . . . . . . . . . . . . 3
4.1. Loss Measurement . . . . . . . . . . . . . . . . . . . . 3 4.1. Loss Measurement . . . . . . . . . . . . . . . . . . . . 3
5. IANA Requirements . . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Security Consideration . . . . . . . . . . . . . . . . . . . 4 6. Security Consideration . . . . . . . . . . . . . . . . . . . 4
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 4 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 4
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
9. Normative References . . . . . . . . . . . . . . . . . . . . 4 9. Normative References . . . . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
The Bidirectional Forwarding Detection (BFD) [RFC5880] protocol The Bidirectional Forwarding Detection (BFD) [RFC5880] protocol
operates by transmitting and receiving control frames, generally at operates by transmitting and receiving control frames, generally at
skipping to change at page 4, line 5 skipping to change at page 4, line 5
otherwise) in successive BFD CC frames. The Sequence Number in each otherwise) in successive BFD CC frames. The Sequence Number in each
successive control frame generated on a BFD session by the successive control frame generated on a BFD session by the
transmitter is incremented by one. transmitter is incremented by one.
The first BFD NULL-Auth TLV processed by the receiver that has a non- The first BFD NULL-Auth TLV processed by the receiver that has a non-
zero sequence number is used for bootstrapping the logic. When using zero sequence number is used for bootstrapping the logic. When using
secure sequence numbers, if the expected values are pre-calculated, secure sequence numbers, if the expected values are pre-calculated,
the matched value must be appropriately recorded to detect lost the matched value must be appropriately recorded to detect lost
frames. frames.
5. IANA Requirements 5. IANA Considerations
N/A This document has no actions for IANA.
6. Security Consideration 6. Security Consideration
Other than concerns raised in BFD [RFC5880] there are no new concerns Other than concerns raised in BFD [RFC5880] there are no new concerns
with this proposal. with this proposal.
7. Contributors 7. Contributors
Manav Bhatia Manav Bhatia
skipping to change at page 4, line 29 skipping to change at page 4, line 29
Authors would like to thank Nobo Akiya, Jeffery Haas, Peng Fan, Authors would like to thank Nobo Akiya, Jeffery Haas, Peng Fan,
Dileep Singh, Basil Saji, Sagar Soni and Mallik Mudigonda who also Dileep Singh, Basil Saji, Sagar Soni and Mallik Mudigonda who also
contributed to this document. contributed to this document.
9. Normative References 9. Normative References
[I-D.ietf-bfd-optimizing-authentication] [I-D.ietf-bfd-optimizing-authentication]
Jethanandani, M., Mishra, A., Saxena, A., and M. Bhatia, Jethanandani, M., Mishra, A., Saxena, A., and M. Bhatia,
"Optimizing BFD Authentication", draft-ietf-bfd- "Optimizing BFD Authentication", draft-ietf-bfd-
optimizing-authentication-03 (work in progress), June optimizing-authentication-04 (work in progress), November
2017. 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
<https://www.rfc-editor.org/info/rfc5880>. <https://www.rfc-editor.org/info/rfc5880>.
Authors' Addresses Authors' Addresses
Ashesh Mishra Ashesh Mishra
O3b Networks O3b Networks
Email: mishra.ashesh@gmail.com Email: mishra.ashesh@gmail.com
Mahesh Jethanandani Mahesh Jethanandani
Cisco Systems CA
170 W. Tasman Drive
San Jose, CA 95134
USA USA
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
URI: www.cisco.com
Ankur Saxena Ankur Saxena
Ciena Corporation Ciena Corporation
3939 North 1st Street 3939 North 1st Street
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: ankurpsaxena@gmail.com Email: ankurpsaxena@gmail.com
URI: www.ciena.com URI: www.ciena.com
 End of changes. 11 change blocks. 
13 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/