BFD for VXLAN
draft-spallagatti-bfd-vxlan-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-18
Replaced by draft-ietf-bfd-vxlan
Stream (None)
Intended RFC status (None)
Formats plain text 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                                                   B. Saji
Intended status: Standards Track                             S. Paragiri
Expires: April 20, 2016                                 Juniper Networks
                                                             V. Govindan
                                                            M. Mudigonda
                                                                   Cisco
                                                               G. Mirsky
                                                                Ericsson
                                                        October 18, 2015

                             BFD for VXLAN
                     draft-spallagatti-bfd-vxlan-02

Abstract

   This document describes use of Bidirectional Forwarding Detection
   (BFD) protocol for VXLAN .

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

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 April 20, 2016.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Pallagatti, et al.       Expires April 20, 2016                 [Page 1]
Internet-Draft                BFD for VXLAN                 October 2015

   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
   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.  Use cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Deployment  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  BFD Packet Transmission . . . . . . . . . . . . . . . . . . .   5
     4.1.  BFD Packet Encapsulation  . . . . . . . . . . . . . . . .   5
   5.  Reception of BFD packet . . . . . . . . . . . . . . . . . . .   6
     5.1.  Demultiplexing of the BFD packet  . . . . . . . . . . . .   6
   6.  Use of reserved VNI . . . . . . . . . . . . . . . . . . . . .   6
   7.  Echo BFD  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   7
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   12. Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   "Virtual eXtensible Local Area Network (VXLAN)" has been defined in
   [RFC7348] that provides an encapsulation scheme which allows VM's to
   communicate in 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 virtual machine (VM) can communicate with a VM in other host only
   if they are on same VXLAN.  VM's 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 VM's.

   Since underlay is a L3 network, continuity check for these tunnels
   becomes important.  BFD as defined in [RFC5880] can be used to

Pallagatti, et al.       Expires April 20, 2016                 [Page 2]
Show full document text