BFD for VXLAN
draft-spallagatti-bfd-vxlan-05
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-04-19
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force S. Pallagatti, Ed.
Internet-Draft Independent Contributor
Intended status: Standards Track S. Paragiri
Expires: October 21, 2017 Juniper Networks
V. Govindan
M. Mudigonda
Cisco
G. Mirsky
ZTE Corp.
April 19, 2017
BFD for VXLAN
draft-spallagatti-bfd-vxlan-05
Abstract
This document describes use of Bidirectional Forwarding Detection
(BFD) protocol in Virtual eXtensible Local Area Network (VXLAN)
overlay network.
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 http://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 October 21, 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
(http://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
Pallagatti, et al. Expires October 21, 2017 [Page 1]
Internet-Draft BFD for VXLAN April 2017
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. Conventions used in this document . . . . . . . . . . . . . . 3
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. BFD Packet Transmission over VXLAN Tunnel . . . . . . . . . . 6
5.1. BFD Packet Encapsulation in VXLAN . . . . . . . . . . . . 6
6. Reception of BFD packet from VXLAN Tunnel . . . . . . . . . . 6
6.1. Demultiplexing of the BFD packet . . . . . . . . . . . . 7
7. Use of reserved VNI . . . . . . . . . . . . . . . . . . . . . 7
8. Echo BFD . . . . . . . . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
10. Security Considerations . . . . . . . . . . . . . . . . . . . 7
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
13. Normative References . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction
"Virtual eXtensible Local Area Network (VXLAN)" has been described in
[RFC7348]. VXLAN provides an encapsulation scheme that allows
virtual machines (VMs) to communicate in a data center network.
VXLAN is typically deployed in data centers interconnecting
virtualized hosts, which may be spread across multiple racks. The
individual racks may be part of a different Layer 3 network or they
could be in a single Layer 2 network. The VXLAN segments/overlay
networks are overlaid on top of these Layer 2 or Layer 3 networks.
A VM can communicate with another VM only if they are on the same
VXLAN. VMs are unaware of VXLAN tunnels as VXLAN tunnel is
terminated on VXLAN Tunnel End Point (VTEP) (hypervisor/TOR). VTEPs
(hypervisor/TOR) are responsible for encapsulating and decapsulating
frames exchanged among VMs.
Since underlay is a L3 network, ability to monitor path continuity,
Show full document text