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

Document Type Active Internet-Draft (nvo3 WG)
Authors Xiao Min  , Greg Mirsky  , Santosh Pallagatti  , Jeff Tantsura 
Last updated 2021-02-21
Replaces draft-xiao-nvo3-bfd-geneve
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
On Agenda nvo3 at IETF-110
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
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: August 25, 2021                                   S. Pallagatti
                                                                  VMware
                                                             J. Tantsura
                                                        Juniper Networks
                                                       February 21, 2021

                             BFD for Geneve
                     draft-ietf-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 used to make 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 August 25, 2021.

Copyright Notice

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

Min, et al.              Expires August 25, 2021                [Page 1]
Internet-Draft               BFD for Geneve                February 2021

   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.  Abbreviations . . . . . . . . . . . . . . . . . . . . . .   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
   4.  Reception of BFD packet from Geneve Tunnel  . . . . . . . . .   8
     4.1.  Demultiplexing of the BFD packet  . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   "Generic Network Virtualization Encapsulation" (Geneve) [RFC8926]
   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.  Specifically, the asynchronous mode of BFD, as defined in
   [RFC5880], is used to monitor a p2p Geneve tunnel, and support for
   BFD Echo function is outside the scope of this document.  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 3 of [RFC8971] ("Bidirectional
Show full document text