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

Document Type Active Internet-Draft (bfd WG)
Last updated 2018-11-23
Replaces draft-spallagatti-bfd-vxlan
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call (wg milestone: Dec 2018 - Submit BFD for VxLAN... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
BFD                                                   S. Pallagatti, Ed.
Internet-Draft                                                   Rtbrick
Intended status: Standards Track                             S. Paragiri
Expires: May 27, 2019                                   Juniper Networks
                                                             V. Govindan
                                                            M. Mudigonda
                                                                   Cisco
                                                               G. Mirsky
                                                               ZTE Corp.
                                                       November 23, 2018

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

Abstract

   This document describes the use of the Bidirectional Forwarding
   Detection (BFD) protocol in Virtual eXtensible Local Area Network
   (VXLAN) overlay networks.

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 27, 2019.

Copyright Notice

   Copyright (c) 2018 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 27, 2019                  [Page 1]
Internet-Draft                BFD for VXLAN                November 2018

   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 . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Deployment  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  BFD Packet Transmission over VXLAN Tunnel . . . . . . . . . .   5
     5.1.  BFD Packet Encapsulation in VXLAN . . . . . . . . . . . .   6
   6.  Reception of BFD packet from VXLAN Tunnel . . . . . . . . . .   7
     6.1.  Demultiplexing of the BFD packet  . . . . . . . . . . . .   7
   7.  Use of reserved VNI . . . . . . . . . . . . . . . . . . . . .   8
   8.  Echo BFD  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   8
   11. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   9
   12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     13.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     13.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.

   VXLAN is typically deployed in data centers interconnecting
   virtualized hosts 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, discussed in section 3
   [RFC7348], by providing Layer 2 overlay scheme on a Layer 3 network.

   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 VXLAN
   Tunnel End Point (VTEP) (hypervisor/TOR).  VTEPs (hypervisor/TOR) are
   responsible for encapsulating and decapsulating frames exchanged
   among VMs.
Show full document text