<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2629 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2629.xml">
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" ipr="trust200902" docName="draft-mmbb-nvo3-geneve-oam-00">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<front>
	<title abbrev="OAM in GENEVE">OAM for use in GENEVE</title>

	<author initials="G." surname="Mirsky" fullname="Greg Mirsky">
		<organization>ZTE Corp.</organization>
		<address>
			<email>gregimirsky@gmail.com</email>
		</address> 
	</author>
	
	    <author fullname="Xiao Min" initials="X." surname="Min">
      <organization>ZTE Corp.</organization>

      <address>
        <postal>
          <street/>

          <city/>

          <code/>

          <country/>
        </postal>

        <email>xiao.min2@zte.com.cn</email>
      </address>
    </author>
	
	<author initials="S" surname="Boutros" fullname="Sami Boutros">
		<organization>VmWare, Inc.</organization>
		<address>
			<email>sboutros@vmware.com</email>
		</address> 
	</author>
	
		<author initials="D" surname="Black" fullname="David Black">
		<organization>Dell EMC</organization>
		<address>

        <postal>
          <street>176 South Street</street>

          <city>Hopkinton, MA</city>

          <code>01748</code>

          <country>United States of America</country>
        </postal>
			<email>david.black@dell.com</email>
		</address> 
	</author>
<!--
	<author initials="M" surname="Bocci" fullname="Matthew Bocci">
		<organization>Nokia</organization>
		<address>
        <postal>
          <street>Shoppenhangers Road</street>          
          <city>Maidenhead, Berks </city>          
          <country>UK</country>
        </postal>

			<email>	matthew.bocci@nokia.com</email>
		</address> 
	</author>
-->
    <date year="2019"/>

    <area>Routing</area>

    <workgroup>NVO3  Working Group</workgroup>

    <keyword>Internet-Draft</keyword>
   
   <keyword>OAM</keyword>
	
	<abstract>
	<t>
          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.
	 </t> 
	</abstract>
</front>

<middle>
  <section anchor="intro" title="Introduction">
        <t>
 Geneve <xref target="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 <xref target="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.
</t>
<t>
This document describes several options for encapsulation of active OAM protocols in Geneve.
These are intended to facilitate the discussion among experts and all interested in both OAM and Geneve
subjects. The goal of such analysis is the selection of one encapsulation method and providing
</t>
<t>
Also, a set of generic requirements for active OAM protocols in Geneve overlay network introduced in this
document. These should be used in selecting the most suitable encapsulation for active OAM in Geneve.
</t>

         
     <section title="Conventions used in this document">
         <section title="Terminology">

 
 <t>CC                Continuity Check </t>
 <t>CV                 Connectivity Verification </t>
 <t>FM                 Fault Management </t>
 <t>GAL               Generic Associated Channel Label</t>
 <t>G-ACh            Generic Associated Channel Header</t>
 <t>Geneve        Generic Network Virtualization Encapsulation </t>
 <t>NVO3            Network Virtualization Overlays </t>                
 <t>OAM                Operations, Administration, and Maintenance</t>
 <t>ACh                 Associated Channel</t>
 <!--
 <t>NTP              Network Time Protocol</t>
 <t>PTP              Precision Time Protocol</t>
 -->
</section>    
         
        <section title="Requirements Language">
        <t>
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
   NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
   "MAY", and "OPTIONAL" in this document are to be interpreted as
   described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> 
   when, and only when, they appear in all capitals, as shown here.
    </t>
          </section>

      </section>
     </section>
<section anchor="requirements" title="OAM Protocols Encapsulation in Geneve Networks">
<t>
OAM protocols, whether it is part of fault management or performance monitoring, intended to provide
reliable information that can be used to detect a failure,
identify the defect, localize it, thus helping to apply corrective actions to minimize the negative impact on service.
Several OAM protocols will be used to perform these functions,
protocols that require demultiplexing at the receiving instance of Geneve.
To improve the accuracy of
the correlation between the condition experienced by the monitored Geneve tunnel and
the state of the OAM protocol the OAM encapsulation is required
to comply with the following requirements:
<list>
<t>
   REQ#1:   Geneve OAM packets SHOULD share the
   fate with data traffic of the monitored Geneve tunnel,
            i.e., be in-band with the monitored traffic, follow precisely
            the same overlay and transport path as packets with data payload,
            in the forward direction, i.e. from ingress toward egress endpoint(s) of the OAM test.
</t>
<t>
   REQ#2:   Encapsulation of OAM control message and data packets in 
            underlay network MUST be indistinguishable from the underlay 
            network forwarding point of view.
</t>
<t>
   REQ#3:   Presence of OAM control message in Geneve packet MUST 
            be unambiguously identifiable.
</t>
<t>
   REQ#4:   It MUST be possible to express entropy for underlay
            Equal Cost Multipath
            in Geneve encapsulation to avoid using data 
            packet content by underlay transient nodes.
</t>
</list>
</t>

<section anchor="oam-encap-option" title="OAM Encapsulation in Geneve">
<t>
One of the options is to use IP/UDP encapsulation for active OAM. In this case OAM protocols are 
identified by destination UDP port number. This approach is well-known and has been used, for example, in MPLS networks.
To use IP/UDP encapsulation for an active OAM protocol the Protocol Type field of the Geneve header
MUST be set to IPv4 (0x0800) or IPv6 (0x86DD) value.
But extra IP/UDP headers that immediately follow the Geneve header adds to processing of OAM message,
further disassociates OAM message from the Geneve header, all of which may cause false negative or positive failure reports.
Also, the additional IP/UDP header adds noticeable overhead, especially if the underlay is the IPv6 network. 
</t>

<t>
Another option is to use the Protocol Type field to demultiplex an active OAM protocols directly. Such method
avoids the use of additional intermediate header but requires that each active OAM protocol be
assigned unique identifier from the Ether Types registry maintained by IANA.
</t>

<t>
The alternative to using the Protocol Type directly is to use a shim that, in turn, identifies
the OAM Protocol and, optionally, includes additional information. <xref target="RFC5586"/>
defines how the Generic Associated Channel Label (GAL) can be used to identify that the
Associated Channel Header (ACH), defined in <xref target="RFC4385"/>, immediately follows the
Bottom-of-the-Stack label. Thus the MPLS Generic Associated Channel can be identified, and protocols
are demultiplexed based on the value of the Channel Type field. Number of channel types, e.g., for
continuity check and performance monitoring, already
have been defined and are listed in IANA MPLS Generalized Associated Channel (G-ACh)
Types (including Pseudowire Associated Channel Types) registry. To use this approach,
the value of the Protocol Type field in the Geneve header MUST be set to MPLS. The Geneve
header MUST be immediately followed by the GAL label with the S flag set to indicate that GAL is the
Bottom-of-the-stack label. Then ACH MUST follow the GAL label and the value of the Channel Type
identifies which of active OAM protocols being encapsulated in the packet.
</t>

<t>
Lastly, an associated channel can be defined directly for a Geneve tunnel.
This document defines the shim for Geneve is presented in <xref target="geneve-ach-header-pic"/> 
      to demultiplex Geneve OAM protocols without much of the overhead.
The value of the Protocol Type MAY be set to 0x8902, the value assigned to IEEE 802.1ag
Connectivity Fault Management protocol as part of <xref target="IEEE.8021Q"/>
and shared by ITU-T G.8013/Y.1731
OAM functions and mechanisms for Ethernet-based networks <xref target="ITU-T.1731"/>.
Alternatively, the new value MAY be requested from the Ether Types registry.
</t>
</section>

</section>

<section anchor="ach-overlay" title="Associated Channel in Geneve Networks">
<t>
An associated channel in the Geneve network is the channel that, by using the same encapsulation
as user traffic, follows the same path through the underlay network as user traffic. In other words,
the associated channel is in-band with user traffic. Creating the notion of the associated channel (ACh)
in the Geneve network ensures that packets of active OAM protocols 
carried in the ACh are in-band with user traffic.
</t>
</section>

  <section anchor="ooam-header" title="Associate Channel Header in Geneve">
<t>
ACh Header immediately follows the Geneve header defined in <xref target="I-D.ietf-nvo3-geneve"/>
and identifies the type of message carried over the Geneve ACh.
The format  of the Geneve ACh Header is:
        <figure align="left" anchor="geneve-ach-header-pic" title="Format of the Associated Channel Header in Geneve Network">
          <artwork><![CDATA[    
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| V |           Msg Type        |           Length              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>
	
  </t>

<t>
The ACh Header consists of the following fields:
<list style="symbols">
<t>V - two bits long field indicates the current version of the ACh Header. The current value is 0b00;</t>

<t>Msg Type - 14 bits long field identifies a protocol. In the case of active OAM, these could be Echo Request/Reply, BFD, Performance Measurement;</t>

<t>Length - two octets long field that is the length of the packet in octets;</t>

</list>
</t>
<!--
<t>
The OOAM header may be followed by the Timestamp control block <xref target="ooam-timestamp-pic"/> and then by 
OOAM Control Packet identified by the Msg Type field. 

          <figure align="left" anchor="ooam-timestamp-pic" title="Timestamp block format">
          <artwork><![CDATA[    
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|  QTF  |  RTF  |                   Reserved                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           Timestamp 1                         |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~                                                               ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                           Timestamp 4                         |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       ]]></artwork>
        </figure>
  </t>
        <t>where:
        <list>
        <t>QTF - Querier timestamp format        </t>
        <t>RTF - Responder timestamp format         </t>
        <t>Timestamp 1-4 - 64-bit timestamp values        </t>
        </list>
        Network Time Protocol (NTP), described in <xref target="RFC5905"/>, 
        is widely used and has a long history of deployment. But it is the IEEE 1588 Precision
        Time Protocol (PTP) <xref target="IEEE.1588.2008"/> that is being broadly used to achieve high-quality
        clock synchronization. Converging between NTP and PTP time formats is possible but is not trivial and 
        does come with a cost, particularly when it is required to be performed in real time without loss of accuracy.
        And recently protocols that supported only NTP time format, like One-Way Active Measurement Protocol <xref target="RFC4656"/>
        and Two-Way Active Measurement Protocol <xref target="RFC5357"/>,
        have been enhanced to support the PTP time format as well <xref target="RFC8186"/>.
        This document proposes to select PTP time format as default time format for Overlay OAM performance 
        measurement. Hence QTF, RTF fields MUST be set to 0 if querier or responder use PTP time format respectively.
        If the querier or responder use the NTP time format, then QTF and/or RTF MUST be set to 1. Use of other values MUST be
        considered as an error and MAY be reported.
        </t>
-->
<section anchor="ooamh-active-oam" title="Use of the Geneve ACh Header in Active OAM">

<t>
Active OAM methods, whether used for fault management or performance monitoring, 
generate dedicated test packets <xref target="RFC7799"/>. Format of an OAM test packet
in Geneve network presented in <xref target="geneve-oam-header-active"/>.

        <figure align="left" anchor="geneve-oam-header-active" title="Geneve OAM Header in Active OAM Packet">
          <artwork><![CDATA[    
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~              Underlay network encapsulation                   ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+------
|Ver|  Opt Len  |O|C|    Rsvd.  |          Protocol Type        |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Geneve
|        Virtual Network Identifier (VNI)       |    Reserved   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Header
|                    Variable Length Options                    |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+------
| V |           Msg Type        |           Length              | ACh
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+------
~                    Active OAM message                          ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>
	
  </t>

</section>

 </section>
 
 <section anchor="geneve-echo-sec" title="Echo Request and Echo Reply in Geneve Tunnel">
 <t>
 [Ed.note] Will be expanded in the future versions.
 </t>
 </section>
 
  <section anchor="iana-considerations" title="IANA Considerations">
  <t>IANA is requested to create a new registry called "Geneve Associated Channel".
  </t>
  
<section anchor="iana-geneve-oam-types" title="Geneve Associated Channel Protocol Types">
  <t>
    IANA is requested to create new sub-registry called "Geneve Associated Channel Protocol Types" in the
    "Geneve Associated Channel" registry.
    All code points in the range 1 through 15615 in this registry shall be allocated
    according to the "IETF Review" procedure as specified in <xref target="RFC8126"/>.

    Remaining code points are allocated according to <xref target="iana-geneve-ach-header-type-tbl"/>:
  </t>
    <texttable anchor="iana-geneve-ach-header-type-tbl" title="Geneve OAM Protocol type">
    <ttcol align="left">Value</ttcol>
    <ttcol align="center">Description</ttcol>
    <ttcol align="left">Reference</ttcol>
     <c>0</c>
    <c>Reserved</c>
    <c/>
     <c>1 - 15615</c>
    <c>Unassigned</c>
    <c>IETF Review</c>
     <c>15616 - 16127</c>
    <c>Unassigned</c>
    <c>First Come First Served</c>
     <c>16128 - 16143</c>
    <c>Experimental</c>
    <c>This document</c>
     <c>16144 - 16382</c>
    <c>Private Use</c>
    <c>This document</c>
         <c>16383</c>
    <c>Reserved</c>
    <c>This document</c>
   </texttable> 
   
   
</section>
  
  </section>
 
   <section anchor="security-considerations" title="Security Considerations">
   <t>
   TBD
   </t>
   </section> 

   <section anchor="ack" title="Acknowledgment">
   <t>
   TBD
   </t>
   </section>
  
  </middle>
  
    <back>
    <references title="Normative References">
     
  <?rfc include="reference.RFC.2119"?>

  <?rfc include="reference.RFC.8174"?>

    <?rfc include="reference.I-D.ietf-nvo3-geneve"?>
      <?rfc include="reference.RFC.5586"?>
        <?rfc include="reference.RFC.4385"?>
    </references>

    <references title="Informative References">
    
  <?rfc include="reference.RFC.8126"?>

    <?rfc include="reference.RFC.7799"?>
      

   <reference anchor="ITU-T.1731">
<front>
<title>Operations, administration and maintenance (OAM) functions and mechanisms for Ethernet-based networks</title>
<author>
<organization>ITU-T</organization>
</author>
<date month="August" year="2015"/>
</front>
<seriesInfo name="ITU-T" value="G.8013/Y.1731"/>
</reference> 

   <reference anchor="IEEE.8021Q">
<front>
<title>IEEE Standard for Local and metropolitan area networks -- Bridges and Bridged Networks</title>
<author>
<organization>IEEE</organization>
</author>
<date month="December" year="2014"/>
</front>
<seriesInfo name="IEEE" value="Std 802.1Q"/>
</reference> 
    </references>

 </back>
 </rfc>
