BFD for VXLAN
draft-ietf-bfd-vxlan-08

Document Type Active Internet-Draft (bfd WG)
Last updated 2019-11-01
Replaces draft-spallagatti-bfd-vxlan
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jeffrey Haas
Shepherd write-up Show (last changed 2019-01-02)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Yes
Telechat date
Responsible AD Martin Vigoureux
Send notices to Jeffrey Haas <jhaas@pfrc.org>
IANA IANA review state Version Changed - Review Needed
BFD                                                   S. Pallagatti, Ed.
Internet-Draft                                                    VMware
Intended status: Standards Track                             S. Paragiri
Expires: May 4, 2020                              Individual Contributor
                                                             V. Govindan
                                                            M. Mudigonda
                                                                   Cisco
                                                               G. Mirsky
                                                               ZTE Corp.
                                                        November 1, 2019

                             BFD for VXLAN
                        draft-ietf-bfd-vxlan-08

Abstract

   This document describes the use of the Bidirectional Forwarding
   Detection (BFD) protocol in point-to-point Virtual eXtensible Local
   Area Network (VXLAN) tunnels forming up an 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 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 4, 2020.

Copyright Notice

   Copyright (c) 2019 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

Pallagatti, et al.         Expires May 4, 2020                  [Page 1]
Internet-Draft                BFD for VXLAN                November 2019

   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.  Deployment  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  BFD Packet Transmission over VXLAN Tunnel . . . . . . . . . .   5
   5.  Reception of BFD Packet from VXLAN Tunnel . . . . . . . . . .   7
     5.1.  Demultiplexing of the BFD Packet  . . . . . . . . . . . .   8
   6.  Use of the Specific VNI . . . . . . . . . . . . . . . . . . .   8
   7.  Echo BFD  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   9
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     12.2.  Informational References . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   "Virtual eXtensible Local Area Network" (VXLAN) [RFC7348] provides an
   encapsulation scheme that allows building an overlay network by
   decoupling the address space of the attached virtual hosts from that
   of the network.

   One use of VXLAN is in data centers interconnecting virtual machines
   (VMs) of a tenant.  VXLAN addresses requirements of the Layer 2 and
   Layer 3 data center network infrastructure in the presence of VMs in
   a multi-tenant environment by providing a Layer 2 overlay scheme on a
   Layer 3 network [RFC7348].  Another use is as an encapsulation for
   Ethernet VPN [RFC8365].

   This document is written assuming the use of VXLAN for virtualized
   hosts and refers to VMs and VXLAN Tunnel End Points (VTEPs) in
   hypervisors.  However, the concepts are equally applicable to non-
   virtualized hosts attached to VTEPs in switches.

   In the absence of a router in the overlay, a VM can communicate with
   another VM only if they are on the same VXLAN segment.  VMs are
   unaware of VXLAN tunnels as a VXLAN tunnel is terminated on a VTEP.
Show full document text