draft-ietf-bfd-seamless-use-case-07.txt   draft-ietf-bfd-seamless-use-case-08.txt 
Network Working Group S. Aldrin Network Working Group S. Aldrin
Internet-Draft Google, Inc Internet-Draft Google, Inc
Intended status: Informational C. Pignataro Intended status: Informational C. Pignataro
Expires: November 5, 2016 Cisco Expires: November 7, 2016 Cisco
G. Mirsky G. Mirsky
Ericsson Ericsson
N. Kumar N. Kumar
Cisco Cisco
May 4, 2016 May 6, 2016
Seamless Bidirectional Forwarding Detection (S-BFD) Use Cases Seamless Bidirectional Forwarding Detection (S-BFD) Use Cases
draft-ietf-bfd-seamless-use-case-07 draft-ietf-bfd-seamless-use-case-08
Abstract Abstract
This document describes various use cases for a Seamless This document describes various use cases for a Seamless
Bidirectional Forwarding Detection (S-BFD), and provides requirements Bidirectional Forwarding Detection (S-BFD), and provides requirements
such that protocol mechanisms allow for a simplified detection of such that protocol mechanisms allow for a simplified detection of
forwarding failures. forwarding failures.
These use cases support S-BFD, as a simplified mechanism to use These use cases support S-BFD, as a simplified mechanism to use
Bidirectional Forwarding Detection (BFD) with large portions of Bidirectional Forwarding Detection (BFD) with large portions of
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 November 5, 2016. This Internet-Draft will expire on November 7, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 11, line 45 skipping to change at page 11, line 45
resiliency in distributed router architectures. The mapping resiliency in distributed router architectures. The mapping
between BFD discriminators and particular entities (e.g., between BFD discriminators and particular entities (e.g.,
ECMP paths, or Line Cards) is out the scope of the S-BFD ECMP paths, or Line Cards) is out the scope of the S-BFD
specification. specification.
REQ#9: The S-BFD protocol MUST provide mechanisms for loop REQ#9: The S-BFD protocol MUST provide mechanisms for loop
detection and prevention, protecting against malicious detection and prevention, protecting against malicious
attacks attempting to create packet loops. attacks attempting to create packet loops.
REQ#10: S-BFD MUST incorporate robust security protections against REQ#10: S-BFD MUST incorporate robust security protections against
impersonators, malicions actors, and various attacks. The impersonators, malicions actors, and various active and
simple and accelerated establishment of an S-BFD session passive attacks. The simple and accelerated establishment
should not negatively affect security. of an S-BFD session should not negatively affect security.
5. Security Considerations 5. Security Considerations
This document details the use cases and identifies various associated This document details the use cases and identifies various associated
requirements. Some of these requirements are security related. The requirements. Some of these requirements are security related. The
use cases herein described do not expose a system to abuse or to use cases herein described do not expose a system to abuse or to
additional security risks. Since some negotiation aspects are additional security risks. Since some negotiation aspects are
eliminated, a misconfiguration can result in S-BFD packets being sent eliminated, a misconfiguration can result in S-BFD packets being sent
to an incorrect node. If this receiving node runs S-BFD, the packet to an incorrect node. If this receiving node runs S-BFD, the packet
will be discarted because of the discriminator mismatch. If the node will be discarted because of the discriminator mismatch. If the node
 End of changes. 5 change blocks. 
7 lines changed or deleted 7 lines changed or added

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