<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.dt-nvo3-encap" target="https://datatracker.ietf.org/doc/html/draft-dt-nvo3-encap-01">
   <front>
      <title>NVO3 Encapsulation Considerations</title>
      <author initials="S." surname="Boutros" fullname="Sami Boutros">
         <organization>Ed.</organization>
      </author>
      <author initials="S." surname="Aldrin" fullname="Sam Aldrin">
         <organization>Google</organization>
      </author>
      <author initials="U." surname="Elzur" fullname="Uri Elzur">
         <organization>Intel</organization>
      </author>
      <author initials="I." surname="Ganga" fullname="Ilango Ganga">
         <organization>Intel</organization>
      </author>
      <author initials="R." surname="Manur" fullname="Rajeev Manur">
         <organization>Broadcom</organization>
      </author>
      <author initials="D." surname="Mozes" fullname="David Mozes">
         <organization>Mellanox</organization>
      </author>
      <author initials="M." surname="Smith" fullname="Michael Smith">
         <organization>Cisco</organization>
      </author>
      <date month="March" day="13" year="2017" />
      <abstract>
	 <t>   As communicated by WG Chairs, the IETF NVO3 chairs and Routing Area
   director have chartered a design team to take forward the
   encapsulation discussion and see if there is potential to design a
   common encapsulation that addresses the various technical concerns.

   There are implications of different encapsulations in real
   environments consisting of both software and hardware implementations
   and spanning multiple data centers. For example, OAM functions such
   as path MTU discovery become challenging with multiple encapsulations
   along the data path.

   The design team recommend Geneve with few modifications as the common
   encapsulation, more details are described in section 7.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-dt-nvo3-encap-01" />
   
</reference>
