BFD for Geneve
draft-xiao-nvo3-bfd-geneve-01

Document Type Active Internet-Draft (individual)
Last updated 2019-10-22
Replaces draft-xiao-bfd-geneve
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda nvo3 at IETF-106
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NVO3 Working Group                                                X. Min
Internet-Draft                                                 G. Mirsky
Intended status: Standards Track                               ZTE Corp.
Expires: April 24, 2020                                    S. Pallagatti
                                                                  VMware
                                                        October 22, 2019

                             BFD for Geneve
                     draft-xiao-nvo3-bfd-geneve-01

Abstract

   This document describes the use of the Bidirectional Forwarding
   Detection (BFD) protocol in point-to-point Generic Network
   Virtualization Encapsulation (Geneve) 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 April 24, 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
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Min, et al.              Expires April 24, 2020                 [Page 1]
Internet-Draft               BFD for Geneve                 October 2019

   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.  BFD Packet Transmission over Geneve Tunnel  . . . . . . . . .   3
     3.1.  BFD Encapsulation With Inner Ethernet/IP/UDP Header . . .   3
     3.2.  BFD Encapsulation With Inner IP/UDP Header  . . . . . . .   6
     3.3.  BFD Encapsulation With Inner MPLS Header  . . . . . . . .   8
   4.  Reception of BFD packet from Geneve Tunnel  . . . . . . . . .  10
     4.1.  Demultiplexing of the BFD packet  . . . . . . . . . . . .  11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   "Generic Network Virtualization Encapsulation" (Geneve)
   [I-D.ietf-nvo3-geneve] 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.

   This document describes the use of Bidirectional Forwarding Detection
   (BFD) protocol [RFC5880] to enable monitoring continuity of the path
   between two Geneve tunnel endpoints, which may be NVE (Network
   Virtualization Edge) or other device acting as a Geneve tunnel
   endpoint.  For simplicity, in this document, NVE is used to represent
   Geneve tunnel endpoint, TS (Tenant System) is used to represent the
   physical or virtual device attached to a Geneve tunnel endpoint from
   the outside.  VAP (Virtual Access Point) is the NVE side of the
   interface between the NVE and the TS, and a VAP is a logical network
   port (virtual or physical) into a specific virtual network.  For
   detailed definitions and descriptions of NVE, TS and VAP, please
   refer to [RFC7365] and [RFC8014].

   The use cases and the deployment of BFD for Geneve are consistent
   with what's described in Section 1 and Section 3 of
   [I-D.ietf-bfd-vxlan].  The major difference between Geneve and
   "Virtual eXtensible Local Area Network" (VXLAN) [RFC7348]
   encapsulation is that Geneve supports multi-protocol payload and
   variable length options.

Min, et al.              Expires April 24, 2020                 [Page 2]
Internet-Draft               BFD for Geneve                 October 2019
Show full document text