%% You should probably cite draft-ietf-nvo3-encap-12 instead of this revision.
@techreport{ietf-nvo3-encap-06,
    number =    {draft-ietf-nvo3-encap-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/06/},
    author =    {Sami Boutros and Donald E. Eastlake 3rd},
    title =     {{NVO3 Encapsulation Considerations}},
    pagetotal = 24,
    year =      2021,
    month =     jun,
    day =       9,
    abstract =  {As communicated by the 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 recommends Geneve with a few modifications as the common encapsulation. This document provides more details, particularly in Section 7.},
}