OAM for use in GENEVE
draft-mmbb-nvo3-geneve-oam-02

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
NVO3  Working Group                                            G. Mirsky
Internet-Draft                                                    X. Min
Intended status: Standards Track                               ZTE Corp.
Expires: September 10, 2020                                   S. Boutros
                                                                   Ciena
                                                                D. Black
                                                                Dell EMC
                                                      S. Pallagatti, Ed.
                                                                  VMware
                                                           March 9, 2020

                         OAM for use in GENEVE
                     draft-mmbb-nvo3-geneve-oam-02

Abstract

   This document defines encapsulation for active Operations,
   Administration, and Maintenance protocols in Geneve protocol.  Also,
   the format and operation of the Echo Request and Echo Reply mechanism
   in Geneve are defined.

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 September 10, 2020.

Copyright Notice

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

Mirsky, et al.         Expires September 10, 2020               [Page 1]
Internet-Draft                OAM in GENEVE                   March 2020

   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
     1.1.  Conventions used in this document . . . . . . . . . . . .   3
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   3
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   3
   2.  Active OAM Protocols in Geneve Networks . . . . . . . . . . .   3
     2.1.  A Control Channel in the Geneve Network . . . . . . . . .   4
     2.2.  OAM Encapsulation in Geneve . . . . . . . . . . . . . . .   4
   3.  Associated Control Channel in Geneve Networks . . . . . . . .   5
   4.  Associated Control Channel Header in Geneve . . . . . . . . .   5
     4.1.  Use of the Geneve ACC Header in Active OAM  . . . . . . .   6
   5.  Echo Request and Echo Reply in Geneve Tunnel  . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Geneve Associated Channel Protocol Types  . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Additional Considerations for OAM Encapsulation
                Method in Geneve . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Geneve [I-D.ietf-nvo3-geneve] is intended to support various
   scenarios of network virtualization.  In addition to carrying multi-
   protocol payload, e.g., Ethernet, IPv4/IPv6, the Geneve message
   includes metadata.  Operations, Administration, and Maintenance (OAM)
   protocols support fault management and performance monitoring
   functions necessary for comprehensive network operation.  Active OAM
   protocols, as defined in [RFC7799], use specially constructed
   packets, that are injected into the network.  To ensure that the
   measured performance metric or the detected failure of the transport
   layer are related to the particular Geneve flow, it is critical that
   these test packets share fate with overlay data packets when
   traversing the underlay network.
Show full document text