BFD Multipoint Active Tails.
draft-ietf-bfd-multipoint-active-tail-06
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (bfd WG)
|
|
Last updated |
|
2018-01-03
(latest revision 2017-12-21)
|
|
Replaces |
|
draft-spallagatti-bfd-multipoint-active-tail
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
|
|
Document shepherd |
|
Reshad Rahman
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Reshad Rahman <rrahman@cisco.com>
|
Internet Engineering Task Force D. Katz
Internet-Draft Juniper Networks
Intended status: Standards Track D. Ward
Expires: June 22, 2018 Cisco Systems
S. Pallagatti, Ed.
Individual Contributor
G. Mirsky, Ed.
ZTE Corp.
December 19, 2017
BFD Multipoint Active Tails.
draft-ietf-bfd-multipoint-active-tail-06
Abstract
This document describes active tail extensions to the Bidirectional
Forwarding Detection (BFD) protocol for multipoint and multicast
networks.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
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 June 22, 2018.
Katz, et al. Expires June 22, 2018 [Page 1]
Internet-Draft BFD Multipoint Active Tails December 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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Details . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Multipoint Client Session . . . . . . . . . . . . . . . . 4
3.2. Multipoint Client Session Failure . . . . . . . . . . . . 5
3.3. State Variables . . . . . . . . . . . . . . . . . . . . . 5
3.3.1. New State Variables . . . . . . . . . . . . . . . . . 5
3.3.2. State Variable Initialization and Maintenance . . . . 6
3.4. Controlling Multipoint BFD Options . . . . . . . . . . . 7
3.5. State Machine . . . . . . . . . . . . . . . . . . . . . . 8
3.6. Session Establishment . . . . . . . . . . . . . . . . . . 8
3.7. Discriminators and Packet Demultiplexing . . . . . . . . 8
3.8. Controlling Tail Packet Transmission . . . . . . . . . . 8
3.9. Soliciting the Tails . . . . . . . . . . . . . . . . . . 9
3.10. Verifying Connectivity to Specific Tails . . . . . . . . 9
3.11. Detection Times . . . . . . . . . . . . . . . . . . . . . 10
3.12. MultipointClient Down/AdminDown Sessions . . . . . . . . 11
3.13. Base BFD Specification Text Replacement . . . . . . . . . 11
3.13.1. Reception of BFD Control Packets . . . . . . . . . . 11
3.13.2. Demultiplexing BFD Control Packets . . . . . . . . . 12
3.13.3. Transmitting BFD Control Packets . . . . . . . . . . 12
4. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 13
5. Operational Scenarios . . . . . . . . . . . . . . . . . . . . 13
5.1. No Head Notification . . . . . . . . . . . . . . . . . . 14
5.2. Unreliable Head Notification . . . . . . . . . . . . . . 14
5.3. Semi-reliable Head Notification and Tail Solicitation . . 14
5.4. Reliable Head Notification . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16
Show full document text